Abstract: ABSTRACT METHOD AND SYSTEM FOR INTELLIGENT POWER SAVING FOR NB-IOT System and method for selection of a power-saving mode for an NB-IoT device. A data collection unit [202] collects an activity information from the at least one NB-IoT device [102]. A decision-making unit [204] connected to the data collection unit [202], identifies at least one sleep time of the at least one NB-IoT device [102] based on the first data. The decision-making unit [204] selects at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102]. The decision-making unit [204] updates the selection of the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102] at a home subscriber server [106].
FORM 2
THE PATENTS ACT, 1970
(39 OF 1970)
AND
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR INTELLIGENT POWER SAVING FOR NB-IOT”
We, Reliance Jio Infocomm Limited, an Indian National of, 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad-380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.
FIELD OF INVENTION
The embodiments of the present invention generally relate to wireless communication networks, and more particularly relates to selection of a power-saving mode for at least one NB-IoT device connected to a network.
BACKGROUND OF THE INVENTION
The following description of 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 present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
Narrow Band-Internet of Things (NB-IoT) has recently emerged as a promising radio access connectivity solution for the low-powered end-user IoT devices. The NB-IoT technology has been implemented in licensed bands, for instance, the licensed bands of LTE are used for implementing this technology. The NB-IoT technology utilizes a minimum system bandwidth of 180 kHz, i.e., one PRB (Physical Resource Block). The NB-IoT can be deployed in 3 modes as described in the figure 2 below: “in-band”, “guard band” and “standalone”. In the “in-band” operation, resource blocks present within LTE carrier are used. The inner resource blocks are not used as they are allotted for synchronization of LTE signals. In “guard band” operation, resource blocks between LTE carriers that are not utilized by any operator are used. In “standalone” operation, GSM frequencies are used, or possibly unused LTE bands are used. Release 13 of 3GPP contains important refinements like discontinuous reception (eDRX) and power save mode. The PSM (Power Save Mode) ensures battery longevity in release 12 and is completed by eDRX for devices that need to receive data more frequently.
The NB-IoT technology addresses some of the key IoT requirements, for instance, the battery lifetime of the devices increases, improved network coverage, cost of the devices is reduced, multiplexing of devices met for capacity requirements, and supporting a massive number of devices. The NB-IoT technology support low power consumption, use of low-cost devices and provides excellent coverage. For example, in an NB-IoT deployment, the NB-IoT cells have a 20 dB gain over other categories
like CAT 4/3/1 cells. As such, the NB-IoT Carrier can support much larger areas when compared to a CAT 4/3/1 base station or channel. Typically, in NB-IOT scenario, the same base station provides the NB-IoT channels for a device. The same or a different base station can provide a channel for a CAT-1 or a CAT 3/4 operation due to the difference in the NB-IoT and other category cell coverage areas.
Another key benefit of NB-IoT devices includes energy optimization feature for operating the NB-IoT device on low-power consumption during a sleep mode as well as when the NB-IoT device is transmitting over the network. While other cellular technologies like LTE-M focus on saving power by sleeping and limiting their transmit time and frequency, the NB-IoT focus on its ability to sleep (with support for Extended Discontinuous Reception (eDRX)) and minimize power consumption during data transmission, primarily due to the simplified data transmission method and lower data rate, which reduces the need to do power-hungry signal processing and improves the overall efficiency of the system. Secondly, NB-IoT possesses less complex radio design with a single antenna and are, accordingly, less expensive than other cellular technologies, reducing the barrier to integrate low-power cellular technology into their solutions. And thirdly, NB-IoT also provides improved range and obstacle penetration. Along with its reduced data rates and simplified radio design, NB-IoT has stronger link budgets than other cellular technologies, leading to greater coverage and strong building penetration, great for applications with devices deployed in difficult to reach places.
The NB-IoT devices also support power-saving feature to further increase the efficiency. The NB-IoT devices are primarily known to support two modes of power-saving, i.e., a Power Saving Mode (PSM) and an Extended Discontinuous Reception (eDRX) mode. For both the PSM and eDRX modes, the trigger point for activating the modes is based on an active time or a paging time window, which kicks off immediately after device moves to Radio Resource Control (RRC) idle mode. For instance, upon expiry of an active time, the NB-IoT device enters the PSM and if paging time window expires, the device enters eDRX sleep. However, since the trigger mechanisms for both the PSM and the eDRX modes are closely tied up with RRC idle mode, in instances of terminating access towards device during a particular time window (say, Active Window) and deep sleep might be required just after the
active window for terminating access. Accordingly, as the access cannot be terminated during PSM or eDRX Sleep Mode, it may become difficult to decide whether to implement the PSM or the eDRX mode for such NB-IoT device. In such scenarios, the service operators are also unable to use modes for power saving in low-powered IoT devices due to partially unpredictable terminated device access and due to closely tying up of PSM/eDRX with RRC idle mode.
In the existing art, solutions exist for managing negotiation of power-saving mode parameters between an NB-IoT device and a core network device by reducing data processing and power consumption by the network on the PSM where PSM parameters include LPM and eLPM timer values. Another existing solution provides managing negotiation of extended idle mode discontinuous reception parameters between an NB-IoT device and a core network device by reducing data processing and power consumption by the network on the eDRX where eDRX parameters include eDRX timer values which will control the duration of eDRX periods. Yet another existing solution provides enabling low power mode in a mobile device for switching from one power mode to a second power mode for different band used by the device to reduce device power consumption based on monitoring of the required number of sub-carriers in the RRC idle mode for different bandwidth. However, all the above prior arts fail to disclose a solution to optimize dynamically deployment of power-saving modes (for both PSM and eDRX) based on specific requirements for devices. While it is not currently allowable to initiate a terminating access towards the device in power saving mode i.e. PSM-Sleep or eDRX-Sleep, this makes it difficult for service owner to suggest sleep configurations to be implemented leading to less power saving. Further, the existing solutions fail to define auto defining of rules and actions based on IoT devices usage and to trigger power saving actions based on usage events from the IoT device. As the numbers grow for the IoT devices in the future, there needs to be an efficient architecture to optimally define rules and actions based on the IoT devices owned by users and automatic triggering for power saving actions based on events from device to save the power of the battery and provide improved coverage. Therefore, there’s a need for a system and a method for automatic selection of a power-saving mode for at least one NB-IoT device.
SUMMARY
This section is provided to introduce certain objects and aspects of the present invention 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.
In order to overcome at least a few problems associated with the known solutions as provided in the previous section, an object of the present invention is to provide a method and a system for selection of a power-saving mode for at least one NB-IoT device connected to a network. Another object of the present invention is to provide a method and a system for automatic optimally defining rules and actions based on the usage of IoT devices. Yet another object of the present invention is to provide a method and a system for triggering power saving actions on IoT devices based on usage events to save the power of the battery and provide improved coverage. Yet another object of the present invention is to provide a method and a system for selecting a power-saving mode for IoT devices based on a dynamic usage of the IoT devices.
In order to achieve the aforementioned objectives, the present invention provides a method and system for selection of a power-saving mode for at least one NB-IoT device connected to a network. A first aspect of the present invention relates to a method for selection of a power-saving mode for at least one NB-IoT device connected to a network, the method comprising collecting, by a data collection unit, a first data from the at least one NB-IoT device, wherein the first data comprises an activity information of the at least one NB-IoT device. A decision-making unit identifies at least one sleep time of the at least one NB-IoT device based on the first data. The decision-making unit selects at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device. The decision-making unit updates the selection of the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device at a home subscriber server. Another aspect of the present invention relates to a system for selection of a power-saving mode for at least one NB-IoT device connected to a network. The system comprises a data collection unit connected to a decision-making unit. The data collection unit configured to collect a first data from the at least one NB-IoT device,
wherein the first data comprises an activity information of the at least one NB-IoT device. The decision-making unit configured to identify at least one sleep time of the at least one NB-IoT device based on the first data. The decision-making unit is further configured to select at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device. The decision-making unit is further configured to update the selection of the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device at a home subscriber server.
BRIEF DESCRIPTION OF DRAWINGS
The accompanying drawings, which are incorporated herein, and constitute a part of this invention, illustrate exemplary embodiments 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 present invention. 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 invention of such drawings includes the invention of electrical components, electronic components or circuitry commonly used to implement such components.
FIG.1 illustrates an exemplary block diagram representation of a communication network architecture [100], in accordance with exemplary embodiments of the present invention.
FIG.2 illustrates an exemplary block diagram representation of a server [200] of the communication network, in accordance with exemplary embodiments of the present invention.
FIG.3 illustrates exemplary at least one power-saving modes for at least one NB-IoT device [102], in accordance with exemplary embodiments of the present invention. FIG.3A illustrates an exemplary Power Saving Mode (PSM) for the at least one NB-IoT device [102] an NB-IoT user device, in accordance with exemplary embodiments of the present invention. FIG.3B illustrates an exemplary Extended idle-mode Discontinuous Reception (eDRX) mode for an NB-IoT user device, in accordance with exemplary embodiments of the present invention.
FIG.4 illustrates an exemplary block diagram of an exemplary eNodeB [400] of the communication network, in accordance with exemplary embodiments of the present invention.
FIG.5 illustrates an exemplary block diagram of a home subscriber server [500] of the communication network, in accordance with exemplary embodiments of the present invention.
FIG.6 illustrates an exemplary block diagram of an exemplary at least one NB-IoT device [600] connected to the communication network, in accordance with exemplary embodiments of the present invention.
FIG.7 illustrates an exemplary method flow diagram depicting a method [700] for selection of a power-saving mode for at least one NB-IoT device [102] connected to a network, in accordance with exemplary embodiments of the present invention. FIG.8 illustrates an exemplary signal exchange diagram depicting a method for selection of at least one power-saving mode for at least one NB-IoT device [102] connected to a network, in accordance with exemplary embodiments of the present invention.
FIG.9 illustrates an exemplary signal flow diagram depicting the working of the data collection unit [202], in accordance with exemplary embodiments of the present invention.
FIG.10 illustrates an exemplary signal flow diagram depicting working of a decision-making unit [204], in accordance with exemplary embodiments of the present invention.
The foregoing shall be more apparent from the following more detailed description of the invention.
BRIEF DESCRIPTION OF INVENTION
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 present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed
above. Some of the problems discussed above might not be fully addressed by any of the features described herein.
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 invention as set forth.
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, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
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 can 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. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
Furthermore, embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware or microcode, the program code or code segments to perform the necessary tasks (e.g., a computer-
program product) may be stored in a machine-readable medium. A processor(s) may perform the necessary tasks.
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.
Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.
As used herein, the term “infers” or “inference” refers generally to the process of reasoning about or inferring states of the system, environment, user, and/or intent from a set of observations as captured via events and/or data. Captured data and events can include user data, device data, environment data, data from sensors, sensor data, application data, implicit data, explicit data, etc. Inference can be employed to identify a specific context or action or can generate a probability distribution over states of interest based on a consideration of data and events, for example. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources. Various classification schemes and/or systems (e.g., support vector machines, neural networks, expert systems, Bayesian belief networks, fuzzy logic, and data fusion engines) can be employed in connection with performing automatic and/or inferred action in connection with the disclosed subject matter.
In addition, the disclosed subject matter may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, computer-readable carrier, or computer-readable media. For example, computer-readable media can include, but are not limited to, magnetic storage devices, e.g., hard disk; floppy disk; magnetic strip(s); optical disk (e.g., compact disk (CD), digital video disc (DVD), Blu-ray Disc™ (BD); smart card(s), flash memory device(s) (e.g., card, stick, key drive).
As used herein, “user device” or "user equipment“, “mobile station,” “mobile subscriber station,” “access terminal,” “terminal,” “handset,” and similar terminology refers to any electrical, electronic, electromechanical and computing wireless device utilized by a subscriber or user of a wireless communication service to receive and/or convey data associated with voice, video, sound, and/or
substantially any data-stream or signalling-stream. Further, the foregoing terms are utilized interchangeably in the subject specification and related drawings. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices and transmitting data to the other user devices. The user device may have a processor, a display, a memory unit, a battery and an input-means such as a hard keypad and/or a soft keypad. The input interface also comprises touch/acoustic/video components for touch/sound/video input and output. The output interface may comprise a microphone, a speaker, camera and additionally audio/video I/O ports in an accessories interface, wherein the speaker normally serves to provide acoustic output in the form of human speech, ring signals, music, etc. The user device may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, NB-IoT etc. For instance, the user devices may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, pager, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art.
The terms “node”, “local wireless communications cite,” “access point” (AP), “base station”, “Node B”, “evolved Node B (eNodeB)”, “home Node B” (HNB), “home access point” (HAP), and the like are utilized interchangeably in the subject specification and drawings and refer to devices that can receive and transmit signal(s) from and to wireless devices through one or more antennas, or act as a wireless network component or apparatus that sends and/or receives data associated with voice, video, sound, and/or substantially any data-stream or signalling-stream between a set of subscriber stations—unless context warrants particular distinction(s) among the terms. Further, the data and signalling streams can be packetized or frame-based flows. As used herein, “at least one NB-IoT cell” may refer to one or more base stations or cells which provide a network coverage to a geographic coverage area, thus the geographic area served by the one or more cells is termed as coverage area of the one or more cells.
Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,” “agent,”, “owner,” and the like are employed interchangeably throughout the subject specification and related drawings, unless context warrants particular distinction(s) among the terms. It should be appreciated that such terms can refer to human entities, or automated components supported through artificial intelligence, e.g., a capacity to make inference based on complex mathematical formulations, that can provide simulated vision, sound recognition, decision making, etc. In addition, the terms “wireless network” and “network” are used interchangeable in the subject application, unless context warrants particular distinction(s) among the terms. As used herein, a “processor” or “processing unit” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, a low-end microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
As used herein, a “communication unit” or a “transceiver unit” may include at least one of a “transmitter unit” configured to transmit at least one data and/or signals to one or more destination and a “receiver unit” configured to receive at least one data and/or signals from one or more source. The “communication unit” or the “transceiver unit” may also be configured to process the at least one data and/or signal received or transmitted at the “communication unit” or the “transceiver unit”. Also, the “communication unit” or the “transceiver unit” may further include, any other similar units obvious to a person skilled in the art, required to implement the features of the present invention.
As used herein, “memory unit”, “storage unit” and/or “memory” 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.
As used herein, a “controller” or “control unit” includes at least one controller, wherein the controller refers to any logic circuitry for processing instructions. A controller may be a general-purpose controller, a special-purpose controller, a conventional controller, a digital signal controller, a plurality of microcontrollers, at least one microcontroller in association with a DSP core, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The controller may perform signal coding, data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the controller or control unit is a hardware processor that comprises a memory and a processor. The memory is configured to store the modules and the processor is specifically configured to execute said modules to perform one or more processes which are described further below.
Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily carry out the present disclosure.
Embodiments of the present disclosure relate to a method and a system for selection of a power-saving mode for at least one NB-IoT device connected to a network. The subject invention relates to a method and a system for introducing an efficient power saving solution to save the power of the battery of the NB-IoT devices and to provide improved coverage. The solution discloses a mechanism for automatically determining a power-saving mode for the NB-IoT device based on a usage of the NB-IoT device, and to trigger power saving actions based on usage events. The conventional techniques do not provide an efficient way of selecting a power-saving mode for the NB-IoT device based on dynamic usage. Compared to such techniques, various methods and apparatus described herein facilitate selection of a power-saving mode for at least one NB-IoT device.
Referring to FIG.1 illustrates an exemplary block diagram representation of a communication network architecture [100], in accordance with exemplary
embodiments of the present invention. As shown in Fig. 1, the wireless communication network [100] comprises at least one NB-IoT device [102], an eNodeB [104], a home subscriber server (HSS) [106], a mobility management unit (MMU) [108], a service capability exposure function (SCEF) [110] and a server [112], all the components are connected to each other and work in conjunction to achieve the objects of the present invention.
As used herein, “at least one NB-IoT device” refers to one or more such user device operating on NB-IoT radio access technology. In an instance of the invention, the at least one NB-IoT device [102] is a chipset-based device, capable of supporting at least one power-saving mode. For example, the at least one NB-IoT device [102, 600] is capable of supporting the Power Saving Mode (PSM) and the extended idle-mode discontinuous reception (eDRX). The NB-IoT devices encompassed by the present invention inlcude, but are not limited to, people tracking devices, smart measuring devices, bike locking devices, etc. or any other NB-IoT sdevice known to a person skilled in the art.
Referring to FIG.6 illustrates an exemplary block diagram of an exemplary at least one NB-IoT device [600] connected to the communication network, in accordance with exemplary embodiments of the present invention. The at least one NB-IoT device [600] comprises of a processor [602], a memory [604], a power module [606], a bus [608] and a chipset [610] further comprising a power mode detection unit [612] and a power information database [614]. The memory [604] is configured to store computer-executable commands and instructions. The processor [602] are configured to execute commands/ instructions provided to the at least one NB-IoT device [600] to implement the functionalities of the at least one NB-IoT device [600]. The power module [606] is configured to manage the power requirement and supply at the at least one NB-IoT device [600]. The power mode detection unit [612] is configured to process information received from the network to implement at least one of a power mode at the at least one NB-IoT device [600]. For example, the power mode detection unit [612] processes eDRX/ PSM information comprising eDRX/PSM parameters along with timing details provided by core network. The power information database [614] is configured to store pre-defined eDRX/ PSM
values. In an instance, the pre-defined values are configured by at least one of an original device manufacturer and an original equipment manufacturer.
The wireless communication network may include a local wireless communication site (or base station), which can use a licensed radio spectrum operated and controlled by a wireless service provider. In another instance of the present invention, the network may be a wired network, a wireless network, or a combination thereof. The network may be a single network or a combination of two or more networks.
The invention encompasses that the at least one NB-IoT device [102] is operated by a subscriber within a coverage area typically communicates with the network via an eNodeB [104]. The eNodeB [104, 400] is configured to perform radio interface transmission and reception, and including, but not limited to, radio channel modulation/ demodulation, channel coding/ decoding and multiplexing/ demultiplexing. The eNodeB [104] is also configured to manage the System information Broadcast (SIB) in each NB-IoT cell on the downlink radio interface to provide basic information to at least one NB-IoT device [102] as a prerequisite to access the network. The eNodeB [104] is also configured to transfer dedicated non-access stratum (NAS) information, and to transfer radio access capability information of the at least one NB-IoT device [102] to the core network. In operation, the at least one NB-IoT device [102] registers with the eNodeB and accordingly, the subscriber’s communication, e.g., voice traffic, data traffic, can be routed to the subscriber through the eNodeB [104] utilizing the licensed radio spectrum. The eNodeB can employ a backhaul network, e.g., broadband wired or wireless network backbone, to route packet communication, e.g., voice traffic, data traffic, data, to the core network.
Referring to FIG.4 illustrates an exemplary block diagram of an exemplary eNodeB [400] of the communication network, in accordance with exemplary embodiments of the present invention. The eNodeB [400] comprises an antenna [402] a network interface module [409], a base band module [406], a control module [407], a control module [407], a memory unit [412], a processor [405] and a set of hardware engines/ peripherals [410], all the components connected to each other and working in conjunction to achieve the objectives of the present invention. The network
interface module [409] is configured to manage the connection of the eNodeB [400] with the at least one NB-IoT device [102] and the other network components. The base band module [406] is configured to process the baseband for the eNodeB [400]. The RF module [408] along with the antenna [402] is configured to transmit and receive radio signals at the eNodeB [400], and to receive the clock reference. The RF module [408] is configured to provides wireless access to the at least one NB-IoT device [102]. The plurality of hardware peripherals [410] comprises of transformers, encoders and decoders, etc. for implementing the functionality of the above-mentioned components. The processor [405] is configured to run a protocol stack.
The server [112, 200] is configured to detect an active time and a sleep time for the at least one NB-IoT device [102] and to determine at least one power-saving mode for the at least one NB-IoT device [102] based on at least one of the active time and the sleep time. In an instance of the present invention, the at least one power saving mode is one of a Power Saving Mode (PSM) and Extended idle-mode Discontinuous Reception (eDRX). The server [112] is also configured to host array of services for the at least one NB-IoT device [102].
Referring to FIG.2 illustrates an exemplary block diagram representation of a server [200] of the communication network, in accordance with exemplary embodiments of the present invention. The server [112] further comprises of a data collection unit [202], a decision-making unit [204], a manual setting module [208] and a database [206], all components are connected to each other and work in conjunction to achieve the objectives of the present application. In an instance of the present invention, in the server [200] architecture, the data collection unit [202], the decision-making unit [204], the manual setting module [208] and the database [206] are implemented by the service owner to implement at least one power-saving modes, and accordingly, configured by at least one of an original device manufacturer and an original equipment manufacturer.
The data collection unit [202] is configured to collect a first data from the at least one NB-IoT device [102], wherein the first data comprises an activity information of the at least one NB-IoT device [102]. The data collection unit [202] is further configured to collect the user activity data from at least one NB-IoT device [102] for
at least a predefined number of days. For instance, in operation, the data collection unit [202] tracks at least one activity on the at least one NB-IoT device [102] and transmits the collected data to the decision-making unit [204]. For example, in a bicycle lock at least one NB-IoT device [102], the data collection unit [202] collects daily activity of the usage of the cycle and shares the data with the decision-making unit [204] to determine at least one power-saving mode for the bi-cycle lock at least one NB-IoT device [102].
Referring to FIG.9 illustrates an exemplary signal flow diagram depicting the working of the data collection unit [202], in accordance with exemplary embodiments of the present invention. The operation starts at step [902] when at least one NB-IoT device [102] is operated by a user. At step [904], the data collection unit [202] continuously monitors usage time and activity of the at least one NB-IoT device [102]. At step [906], the data collection unit [202] operates in the background to determine an active and a sleep time of at least one NB-IoT device [102] based on the monitored activity of the at least one NB-IoT device [102]. At step [908], the data collection unit [202] determines whether the data is monitored for a pre-defined number of days. In an instance of the present invention, the pre-defined number of days is specified by a service owner for which active/sleep time is to be observed. At step [910], in an event the data collection unit [202] determines that data collection is completed, the collected data is sent to decision making unit [204] for selection of at least one power-saving mode for the at least one NB-IoT device [102].
The decision-making unit [204] is configured to identify at least one sleep time of the at least one NB-IoT device [102] based on the first data. The decision-making unit [204] is further configured to select at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102], and to update the selection of the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102] at a home subscriber server [106]. In another instance of the present invention, the decision-making unit [204] is configured to identify at least one active time of the at least one NB-IoT device [102] based on the first data. The decision-making unit [204] selects at least one power-saving mode for each of the at least one active time of the at least one NB-IoT device [102], and updates the selection of the at least one power-saving mode for each of
the at least one active time of the at least one NB-IoT device [102] at a home subscriber server [106]. The at least one power saving mode comprises a Power Saving Mode (PSM) and an Extended idle-mode Discontinuous Reception (eDRX). Referring to FIG.3 illustrates exemplary at least one power-saving modes for at least one NB-IoT device [102], in accordance with exemplary embodiments of the present invention. Referring to FIG.3A illustrates an exemplary Power Saving Mode (PSM) for the at least one NB-IoT device [102] an NB-IoT user device, in accordance with exemplary embodiments of the present invention. This capability is focused on reducing the power consumption of an at least one NB-IoT device [102] and enables the at least one NB-IoT device [102] to enter a deep sleep mode. The PSM is intended for the at least one NB-IoT device [102] designed for infrequent data transmission and that can accept a corresponding latency in the mobile terminating communication.
With the PSM approach, the at least one NB-IoT device [102] itself decides how often and for how long it needs to be active in order to transmit and receive data. In operation, during the PSM, the at least one NB-IoT device [102] remains registered with the network. Accordingly, upon the at least one NB-IoT device [102] waking from the sleep, the at least one NB-IoT device [102] is not needed to re-attach or re¬establish the packet data network (PDN) connections. Thus, while the at least one NB-IoT device [102] is in PSM mode, the at least one NB-IoT device [102] is not reachable for mobile terminating services, however, the network is aware of the unavailability of the at least one NB-IoT device [102] and avoids paging the at least one NB-IoT device [102] in vain.
The at least one NB-IoT device [102] is available for mobile terminating services when the at least one NB-IoT device [102] is in connected mode and for the whole of the time period the at least one NB-IoT device [102] is active time after the connected mode is established. The at least one NB-IoT device [102] requests the PSM by including a timer (T1) with the desired value in the attach, tracking area update (TAU) or routing area update. During the timer (T1), the at least one NB-IoT device [102] listens to the paging channel after transitioning from connected to idle mode. When the timer expires, the at least one NB-IoT device [102] enters PSM. The at least one NB-IoT device [102] can also include a second timer(T2), which is an
extension to the timer (T1) in order to remain in PSM for longer than the timer (T1) broadcasted by the network. The network accepts the PSM by providing the actual value of the timers to be used in the attach/TAU/RAU accept procedure. In an instance of the present invention, the maximum time of the timers is about 413 days.
Referring to FIG.3B illustrates an exemplary Extended idle-mode Discontinuous Reception (eDRX) mode for an NB-IoT user device, in accordance with exemplary embodiments of the present invention. The extended idle-mode discontinuous reception (eDRX) is another mechanism to reduce the power consumption of the at least one NB-IoT device [102] by extending the sleeping cycle in idle mode. The eDRX mode allows the at least one NB-IoT device [102] to turn part of its circuitry off during the eDRX period to save power. During the eDRX mode, the at least one NB-IoT device [102] is not listening for paging or downlink control channels, so the network does not contact the device.
The main difference with PSM is that this capability is useful for mobile terminating data, with a delayed reachability compared to current DRX. To achieve the same degree of mobile terminating services reachability with PSM, the at least one NB-IoT device [102] exits the PSM and issues periodic tracking area updating (TAU) or routing area updating (RAU) procedure with the same frequency as the extended idle mode DRX cycle, thus causing additional signalling for the network and power consumption in the at least one NB-IoT device [102]. The at least one NB-IoT device [102] can request the use of extended idle-mode DRX cycle (eDRX) during an attach, tracking area updating (TAU) or routing area updating (RAU) procedure by including the eDRX parameters.
Referring to FIG.10 illustrates an exemplary signal flow diagram depicting the working of a decision-making unit [204], in accordance with exemplary embodiments of the present invention. The decision-making unit [204] starts operating at step [1002]. At step [1004], the decision-making unit [204] receives first data collected by the data collection unit [202]. At step [1006], the decision-making unit [204] extracts active time and sleep time-based on first input received from the data collection unit [202]. Further, at step [1008], the decision-making unit [204] determines at least one power-saving mode for the active time and the sleep time of
the at least one NB-IoT device [102]. For instance, the decision-making unit [204] derives whether PSM or eDRX is required based on input from the at least one NB-IoT device [102].
In an instance of the present invention, at step [1010] and [1012] the decision-making unit [204] compares the sleep time of the at least one NB-IoT device [102] with a threshold number of hours (X) for the PSM or the eDRX selection respectively. For example, the decision-making unit [204] does not select the PSM for low sleep times, say 15 minutes, as this would drain device battery faster when the at least one NB-IoT device [102] is turned on and off frequently. Thus, the decision-making unit [204] selects a relevant eDRX or PSM sleep time by comparing permitted sleep times and the sleep times received from the data collection unit [202]. Upon determining the at least one power-saving mode for the at least one NB-IoT device [102], the decision-making unit [204] transmits the sleep cycle along with start and end time to the home subscriber server [106] at step [1014]. The home subscriber server [106] updates the data in subscriber profile and upon next attach or tracking area update from the device, new parameters for the selected at least one power-saving modes are sent to the at least one NB-IoT device [102].
The manual setting module [208] is configured to log at least one of the active time and the sleep time of the at least one NB-IoT device [102] identified by the decision-making unit [204]. In operation, once the at least one NB-IoT device [102] downloads a configuration file, the manual setting module [208] starts logging the active time and the sleep time of the at least one NB-IoT device [102] based on a user’s input to switch the at least one NB-IoT device [102] ON/ OFF. The manual setting module [208] is also configured to correlate the log for the at least one NB-IoT device [102] with a unique identifier of the at least one NB-IoT device [102] (for example, an IMEI number). The database [206] is configured to store the selected at least one power-saving mode for the at least one NB-IoT device [102], and to store the log of the manual setting module [208]. The database [206] is also configured to transmit at least one of the log and the selected at least one power-saving mode for the at least one NB-IoT device [102] to the service capability exposure function [110].
The home subscriber server [106, 500] is configured to receive the selection of the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102] from the decision-making unit [204]. In another instance of the present invention, the home subscriber server [106] is configured to receive the selection of the at least one power-saving mode for each of the at least one active time of the at least one NB-IoT device [102] from the decision-making unit [204]. The home subscriber server [106] is further configured to maintain a database comprising user-related and subscriber-related information. The home subscriber server [106] is also configured to facilitate user authentication and access authorization.
Referring to FIG.5 illustrates an exemplary block diagram of a home subscriber server [500] of the communication network, in accordance with exemplary embodiments of the present invention. The home subscriber server [500] comprises a processor [502], a memory [504], a power module [506], a bus [508] and a subscriber profile manager [512], an authentication center [514] and a power information database [516]. The memory [604] is configured to store computer-executable commands and instructions. The processor [502] are configured to execute commands/ instructions provided to the home subscriber server [500] to implement the functionalities of the home subscriber server [500]. The power module [506] is configured to manage the power requirement and supply at the home subscriber server [500]. The subscriber profile manager [512] with all subscription-related details of each configured subscriber and includes component for processing eDRX/PSM information along with timing received from server or configuration portal. The authentication center [514] is configured to authenticate each subscriber trying to access network, with the help of information pre-configured in its memory or database and also help in ciphering or integrity protection. The power information database [516] is configured to store pre-defined eDRX/ PSM values.
The mobility management unit [108] is configured to receive at least one of an attach request and a tracking area update request from the at least one NB-IoT device [102]. The mobility management unit [108] retrieves the selection of the at least one power-saving mode for each of the at least one sleep time of the at least
one NB-IoT device [102] from the home subscriber server [106]. The mobility management unit [108] transmits the selection of the at least one power-saving mode for each of the at least one sleep time to the at least one NB-IoT device [102] in response to at least one of the attach request and the tracking area update request. The mobility management unit [108] acts as a control node to process signal exchange between the at least one NB-IoT device [102] and the core network. The protocols running between the at least one NB-IoT device [102] and the core network, for examples, the Non-Access Stratum (NAS) protocols are processed by the mobility management unit [108]. The mobility management unit [108] is also configured for the establishment, maintenance and release of the bearers and is handled by the session management layer in the NAS protocol, and for the establishment of the connection and security between the network and at least one NB-IoT device [102] and is handled by the connection or mobility management layer in the NAS protocol layer.
The service capability exposure function [110] acts as an interface for small data transfers and control messaging between Enterprises and the operators’ core network. The service capability exposure function [110] provides Application Programming Interface (APIs) to the enterprises for the small data transfers and control messages and uses the network elements in the operators’ core network for performing its functions.
Referring to FIG.7 illustrates an exemplary method flow diagram depicting a method [700] for selection of at least one power-saving mode for at least one NB-IoT device [102] connected to a network, in accordance with exemplary embodiments of the present invention. The method begins at step [702]. The method at step [704] comprises a data collection unit [202] collecting a first data from the at least one NB-IoT device [102], wherein the first data comprises an activity information of the at least one NB-IoT device [102]. The data collection unit [202] is further configured to collect the user activity data from at least one NB-IoT device [102] for at least a predefined number of days. For instance, in operation, the data collection unit [202] tracks at least one activity on the at least one NB-IoT device [102] and transmits the collected data to the decision-making unit [204]. For example, in a bicycle lock at least one NB-IoT device [102], the data collection unit [202] collects daily activity of
the usage of the cycle and share the data with the decision-making unit [204] to determine at least one power-saving mode for the bi-cycle lock at least one NB-IoT device [102].
At step [706], the decision-making unit [204] identifies at least one sleep time of the at least one NB-IoT device [102] based on the first data. In operation, the decision-making unit [204] extracts active time and sleep time-based on first input received from the data collection unit [202]. Next at step [704], the decision-making unit [204] selects at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102]. For instance, the decision-making unit [204] derives whether PSM or eDRX is required based on input from the at least one NB-IoT device [102]. The decision-making unit [204] is configured to select the PSM based on a comparison of the at least one sleep time of the at least one NB-IoT device [102] with a threshold sleep time. In an instance of the present invention, the decision-making unit [204] compares the sleep time of the at least one NB-IoT device [102] with a threshold number of hours (X) for the PSM or the eDRX selection respectively. For example, the decision-making unit [204] does not select the PSM for low sleep times, say 15 minutes, as this would drain device battery faster when the at least one NB-IoT device [102] is turned on and off frequently. Thus, the decision-making unit [204] selects a relevant eDRX or PSM sleep time by comparing permitted sleep times and the sleep times received from the data collection unit [202].
Lastly, at step [708], the decision-making unit [204] updates the selection of the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102] at a home subscriber server [106]. In operation, upon determining the at least one power-saving mode for the at least one NB-IoT device [102], the decision-making unit [204] transmits the selected at least one power-saving mode, a sleep cycle further comprising a start time and an end time to the home subscriber server [106] at step [1014]. The home subscriber server [106] updates the data in subscriber profile and upon next attach or tracking area update from the device, new parameters for the selected at least one power-saving modes are sent to the at least one NB-IoT device [102]. The method [700] completes at step [710].
The method [700] of the present invention further encompasses the decision-making unit [204] identifying at least one active time of the at least one NB-IoT device [102] based on the first data. The decision-making unit [204], thus, selects the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102] based on the at least one active time. In operation, the decision-making unit [204] extracts active time based on first input received from the data collection unit [202]. For instance, the decision-making unit [204] derives whether PSM or eDRX is required based on input from the at least one NB-IoT device [102] and the active time of the at least one NB-IoT device [102]. In an instance of the present invention, the decision-making unit [204] determines a start time and a stop time for the at least one power saving mode based on at least one of the at least one sleep time and at least one active time.
The method [700] of the present invention further encompasses that the at least one NB-IoT device [102] transmits an attach request to a mobility management unit [108] of the network. The mobility management unit [108] retrieves the selection of the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102] from the home subscriber server [106]. The mobility management unit [108] transmits the selection of the at least one power-saving mode for each of the at least one sleep time to the at least one NB-IoT device [102] in response to the attach request. In another instance of the present invention, the at least one NB-IoT device [102] transmits a tracking area update request to a mobility management unit [108] of the network. The mobility management unit [108] retrieves the selection of the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102] from the home subscriber server [106]. The mobility management unit [108] transmits the selection of the at least one power-saving mode for each of the at least one sleep time to the at least one NB-IoT device [102] in response to the tracking area update. The mobility management unit [108] acts as a control node to process signal exchange between the at least one NB-IoT device [102] and the core network.
Referring to FIG.8 illustrates an exemplary signal exchange diagram depicting a method for selection of at least one power-saving mode for at least one NB-IoT device [102] connected to a network, in accordance with exemplary embodiments of
the present invention. At step [802], the at least one NB-IoT device [102] sends an attach request to the mobility management unit [108] to establish a connection with the network. The attach request comprises of information regarding Power Saving Mode (PSM) and Extended idle-mode Discontinuous Reception (eDRX), including but not limited to, timers, cycle length, etc. At step [804], the mobility management unit [108] requests the profile of the at least one NB-IoT device [102] from the home subscriber server [106]. At step [806], the mobility management unit [108] downloads the profile of the at least one NB-IoT device [102] from the home subscriber server [106] to check for eDRX and PSM values in the profile. At step [810], in an event, eDRX and PSM values are not set in the user profile, then MME will allow the at least one NB-IoT device [102] requested eDRX and PSM values and acknowledge by sending an “Attach Accept” signal. Further, at step [810], in an event, eDRX and PSM values set in the user profile, mobility management unit [108] overwrites the eDRX and PSM values at the at least one NB-IoT device [102] via the “Attach Accept” signal.
At step [812], the server [112] determines the eDRX and PSM values based on application requirement and sends the eDRX and PSM values to service capability exposure function [110] which further sends the values to the home subscriber server [106], using the method of the present application. At step [816], the at least one NB-IoT device [102] sends, to the mobility management unit [108], a “Tracking area request” due to periodic timer expiry, the tracking area change or recover after PSM cycle. At step [818-820] the mobility management unit [108] downloads the requested user profile from the home subscriber server [106] and checks for eDRX and PSM values in profile. At step [822], in an event, eDRX and PSM values are not set in the user profile, the mobility management unit [108] will allow the at least one NB-IoT device [102] requested eDRX and PSM values and acknowledge by sending an “Tracking Area Accept” signal. At step [822], in an event, eDRX and PSM values set in the user profile, the mobility management unit [108] overwrites the eDRX and PSM values at the at least one NB-IoT device [102] via the “Tracking Area Accept” signal. Accordingly, the at least one NB-IoT device [102] implements the eDRX and PSM values. The at least one NB-IoT device [102] will work according to new eDRX and PSM values.
Thus, the present invention provides a novel solution for the technical problem of selecting a power-saving mode for an NB-IoT device. Particularly, the solution of the present invention provides technical effect of optimally defining rules and actions for power saving based on a usage information of the NB-IoT device, and automatically triggering power saving actions on the NB-IoT device based on the usage events. Since, the selection of power-saving mode encompassed by the present application is independent of the RRC, the solution of the present invention is also helpful in instances of partially unpredictable terminated device access where power-saving modes could not be selected due to closely tying up of PSM/eDRX with RRC idle mode. While the solution of the present application is directed to NB-IoT technology, it can also be implemented in the Long-Term Evolution Machine Type Communications Category M1 (LTE MTC Cat M1, also referred to as LTE-M) and 5G-Evolved Machine Type Communications (eMTC) and any other such communication known to the person skilled in the art.
While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the invention. These and other changes in the preferred embodiments of the invention will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter to be implemented merely as illustrative of the invention and not as a limitation.
We Claim
1. A method for selection of a power-saving mode for at least one NB-IoT
device [102] connected to a network, the method comprising:
- collecting, by a data collection unit [202], a first data from the at least one NB-IoT device [102], wherein the first data comprises an activity information of the at least one NB-IoT device [102];
- identifying, by a decision-making unit [204], at least one sleep time of the at least one NB-IoT device [102] based on the first data;
- selecting, by the decision-making unit [204], at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102]; and
- updating, by the decision-making unit [204], the selection of the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102] at a home subscriber server [106].
2. The method as claimed in claim 1, further comprising:
- identifying, by a decision-making unit [204], at least one active time of the at
least one NB-IoT device [102] based on the first data; and selecting, by a
decision-making unit [204], the at least one power-saving mode for each of
the at least one sleep time of the at least one NB-IoT device [102] based on
the at least one active time.
3. The method as claimed in claim 1, further comprising:
- transmitting, by at least one NB-IoT device [102], an attach request to a mobility management unit [108] of the network;
- retrieving, by the mobility management unit [108], the selection of the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102] from the home subscriber server [106]; and
- transmitting, by the mobility management unit [108], the selection of the at least one power-saving mode for each of the at least one sleep time to the at least one NB-IoT device [102] in response to the attach request.
4. The method as claimed in claim 1, further comprising:
- transmitting, by at least one NB-IoT device [102], a tracking area update request to a mobility management unit [108] of the network;
- retrieving, by the mobility management unit [108], the selection of the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102] from the home subscriber server [106]; and
- transmitting, by the mobility management unit [108], the selection of the at least one power-saving mode for each of the at least one sleep time to the at least one NB-IoT device [102] in response to the tracking area update request.
5. The method as claimed in claim 1, wherein the data collection unit [202] collects the user activity data from at least one NB-IoT device [102] for at least a predefined number of days.
6. The method as claimed in claim 1, wherein the decision-making unit [204] selects the at least one power-saving mode for for each of the at least one sleep time of the at least one NB-IoT device [102] based on a comparison of the at least one sleep time with a threshold sleep time.
7. A system for selection of a power-saving mode for at least one NB-IoT device [102] connected to a network, the system comprising:
- a data collection unit [202] configured to collect a first data from the at least one NB-IoT device [102], wherein the first data comprises an activity information of the at least one NB-IoT device [102];
- a decision-making unit [204] connected to the data collection unit [202], said decision-making unit [204] configured to:
- identify at least one sleep time of the at least one NB-IoT device [102] based on the first data,
- select a at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102], and
- update the selection of the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102] at a home subscriber server [106].
8. The system as claimed in claim 7, wherein the decision-making unit [204] is
further configured to:
- identify at least one active time of the at least one NB-IoT device [102] based
on the first data, and
select the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102] based on the at least one active time.
9. The system as claimed in claim 7, further comprising a mobility management
unit [108] configured to:
- receive at least one of an attach request and a tracking area update request from the at least one NB-IoT device [102],
- retrieve the selection of the at least one power-saving mode for each of the at least one sleep time of the at least one NB-IoT device [102] from the home subscriber server [106], and
- transmit the selection of the at least one power-saving mode for each of the at least one sleep time to the at least one NB-IoT device [102] in response to at least one of the attach request and the tracking area update request.
10. The system as claimed in claim 7, wherein the data collection unit [202] is further configured to collect the user activity data from at least one NB-IoT device [102] for at least a predefined number of days.
| # | Name | Date |
|---|---|---|
| 1 | 201921025006-FORM-8 [26-06-2024(online)].pdf | 2024-06-26 |
| 1 | 201921025006-STATEMENT OF UNDERTAKING (FORM 3) [24-06-2019(online)].pdf | 2019-06-24 |
| 2 | 201921025006-PROVISIONAL SPECIFICATION [24-06-2019(online)].pdf | 2019-06-24 |
| 2 | 201921025006-Written submissions and relevant documents [16-04-2024(online)].pdf | 2024-04-16 |
| 3 | 201921025006-FORM-26 [28-03-2024(online)].pdf | 2024-03-28 |
| 3 | 201921025006-FORM 1 [24-06-2019(online)].pdf | 2019-06-24 |
| 4 | 201921025006-FIGURE OF ABSTRACT [24-06-2019(online)].pdf | 2019-06-24 |
| 4 | 201921025006-Correspondence to notify the Controller [27-03-2024(online)].pdf | 2024-03-27 |
| 5 | 201921025006-US(14)-HearingNotice-(HearingDate-04-04-2024).pdf | 2023-12-29 |
| 5 | 201921025006-Proof of Right (MANDATORY) [02-08-2019(online)].pdf | 2019-08-02 |
| 6 | 201921025006-ORIGINAL UR 6(1A) FORM 26-121022.pdf | 2022-10-26 |
| 6 | 201921025006-FORM-26 [02-08-2019(online)].pdf | 2019-08-02 |
| 7 | 201921025006-Response to office action [05-04-2022(online)].pdf | 2022-04-05 |
| 7 | 201921025006-ORIGINAL UR 6(1A) FORM 1 & FORM 26-060819.pdf | 2019-11-26 |
| 8 | 201921025006-FORM 18 [24-06-2020(online)].pdf | 2020-06-24 |
| 8 | 201921025006-8(i)-Substitution-Change Of Applicant - Form 6 [26-02-2022(online)].pdf | 2022-02-26 |
| 9 | 201921025006-ASSIGNMENT DOCUMENTS [26-02-2022(online)].pdf | 2022-02-26 |
| 9 | 201921025006-ENDORSEMENT BY INVENTORS [24-06-2020(online)].pdf | 2020-06-24 |
| 10 | 201921025006-DRAWING [24-06-2020(online)].pdf | 2020-06-24 |
| 10 | 201921025006-PA [26-02-2022(online)].pdf | 2022-02-26 |
| 11 | 201921025006-COMPLETE SPECIFICATION [24-06-2020(online)].pdf | 2020-06-24 |
| 11 | 201921025006-FER_SER_REPLY [22-02-2022(online)].pdf | 2022-02-22 |
| 12 | 201921025006-FER.pdf | 2021-10-19 |
| 12 | Abstract1.jpg | 2021-10-19 |
| 13 | 201921025006-FER.pdf | 2021-10-19 |
| 13 | Abstract1.jpg | 2021-10-19 |
| 14 | 201921025006-COMPLETE SPECIFICATION [24-06-2020(online)].pdf | 2020-06-24 |
| 14 | 201921025006-FER_SER_REPLY [22-02-2022(online)].pdf | 2022-02-22 |
| 15 | 201921025006-DRAWING [24-06-2020(online)].pdf | 2020-06-24 |
| 15 | 201921025006-PA [26-02-2022(online)].pdf | 2022-02-26 |
| 16 | 201921025006-ASSIGNMENT DOCUMENTS [26-02-2022(online)].pdf | 2022-02-26 |
| 16 | 201921025006-ENDORSEMENT BY INVENTORS [24-06-2020(online)].pdf | 2020-06-24 |
| 17 | 201921025006-FORM 18 [24-06-2020(online)].pdf | 2020-06-24 |
| 17 | 201921025006-8(i)-Substitution-Change Of Applicant - Form 6 [26-02-2022(online)].pdf | 2022-02-26 |
| 18 | 201921025006-Response to office action [05-04-2022(online)].pdf | 2022-04-05 |
| 18 | 201921025006-ORIGINAL UR 6(1A) FORM 1 & FORM 26-060819.pdf | 2019-11-26 |
| 19 | 201921025006-ORIGINAL UR 6(1A) FORM 26-121022.pdf | 2022-10-26 |
| 19 | 201921025006-FORM-26 [02-08-2019(online)].pdf | 2019-08-02 |
| 20 | 201921025006-US(14)-HearingNotice-(HearingDate-04-04-2024).pdf | 2023-12-29 |
| 20 | 201921025006-Proof of Right (MANDATORY) [02-08-2019(online)].pdf | 2019-08-02 |
| 21 | 201921025006-FIGURE OF ABSTRACT [24-06-2019(online)].pdf | 2019-06-24 |
| 21 | 201921025006-Correspondence to notify the Controller [27-03-2024(online)].pdf | 2024-03-27 |
| 22 | 201921025006-FORM-26 [28-03-2024(online)].pdf | 2024-03-28 |
| 22 | 201921025006-FORM 1 [24-06-2019(online)].pdf | 2019-06-24 |
| 23 | 201921025006-Written submissions and relevant documents [16-04-2024(online)].pdf | 2024-04-16 |
| 23 | 201921025006-PROVISIONAL SPECIFICATION [24-06-2019(online)].pdf | 2019-06-24 |
| 24 | 201921025006-STATEMENT OF UNDERTAKING (FORM 3) [24-06-2019(online)].pdf | 2019-06-24 |
| 24 | 201921025006-FORM-8 [26-06-2024(online)].pdf | 2024-06-26 |
| 1 | 201921025006E_23-08-2021.pdf |