Enhanced performance through wake-up optimization
By optimizing the device wake-up process in the wireless communication system, and by grouping and synchronizing the wake-up event, the problem of excessive battery power consumption caused by the asynchronousness of the device wake-up event is solved, and the battery life of the device is extended.
Patent Information
- Application Number
- CN201980080415.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-12-11
- Filing Date
- 2019-12-10
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2039-12-10
AI Technical Summary
The asynchronousness of device wake-up events in existing wireless communication systems leads to excessive battery power consumption, shortening the battery life of the device.
By optimizing the device wake-up process, allowing multiple applications or operations to perform, group or synchronize wake-up events in the same wake-up instance to reduce the number of device wake-ups and the average duration of each wake-up, coordinating device wake-up using wake-up time intervals and preferred intervals.
Reduces the power consumption of the device, extends the battery life, and improves the efficiency of battery resources.
Smart Images

Figure CN113170395B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to communication systems and, more particularly, to wireless communications including device wake-up. Background Art
[0002] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
[0003] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., utilizing the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR can be based on 4G Long Term Evolution (LTE) standards. 5G NR technology needs to be further improved. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention
[0004] A simplified overview of one or more aspects is presented below to provide a basic understanding of these aspects. This overview is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that is presented later.
[0005] Multiple applications may impose a burden on the battery power of a wireless device through individual wake-up events for each of the multiple applications, which cause the UE to operate in an active state for a longer period of time. The device wake-up may consume a large amount of power relative to the total power battery life of the device. The aspects presented herein provide a solution to the battery burden problem by improving the way in which the wireless device coordinates device wake-up for multiple applications or multiple operations. In some aspects, the device wake-up process can be optimized to allow multiple applications and / or operations to be grouped together and executed in the same wake-up instance, which can reduce power consumption to improve the battery life of the wireless device. As presented herein, grouping or synchronization of multiple events in the same device wake-up can reduce the number of required device wake-ups and the average duration of each wake-up.
[0006] In one aspect of the present disclosure, a method, computer readable medium, and apparatus for wireless communication at a user equipment (UE) are provided. The apparatus receives a wake-up time interval from each of a plurality of applications. The apparatus forms a first device wake-up time interval. In some aspects, the first device wake-up time interval may include overlapping wake-up time intervals of the plurality of applications. The apparatus schedules device wake-ups during at least the first device wake-up time interval.
[0007] To accomplish the foregoing and related ends, one or more aspects include the features hereinafter fully described and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are indicative of only a few of the various ways in which the principles of the various aspects may be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.
[0009] Figure 2A , 2B , 2C and 2D are diagrams illustrating examples of a first 5G / NR frame, a DL channel within a 5G / NR subframe, a second 5G / NR frame, and a UL channel within a 5G / NR subframe, respectively.
[0010] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.
[0011] Figure 4A and 4B Illustrated are example aspects of device wake-up in accordance with certain aspects of the present disclosure.
[0012] Figure 5 is a diagram illustrating synchronized device wake-up in accordance with certain aspects of the present disclosure.
[0013] Figure 6 is a diagram illustrating device wake-up in accordance with certain aspects of the present disclosure.
[0014] Figure 7 is a diagram illustrating an evaluation period in accordance with certain aspects of the present disclosure.
[0015] Figure 8 is a diagram illustrating synchronized device wake-up in accordance with certain aspects of the present disclosure.
[0016] Fig. 9 is a flow chart of a method of wireless communication.
[0017] Fig.10 is a conceptual data flow diagram illustrating the flow of data between different parts / components in an exemplary apparatus.
[0018] Fig.11 is a diagram illustrating an example of a hardware implementation of an apparatus employing a processing system. DETAILED DESCRIPTION
[0019] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it is apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid blurring these concepts.
[0020] Several aspects of telecommunication systems will now be presented with reference to various devices and methods. These devices and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0021] For example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functions described throughout the present disclosure. One or more processors in a processing system can execute software. Whether it is software, firmware, middleware, microcode, hardware description language, or other, software should be broadly interpreted as representing instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc.
[0022] Therefore, in one or more example embodiments, the functions described can be implemented in hardware, software, or any combination thereof. If implemented in software, the functions can be stored on a computer-readable medium, or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. The storage medium can be any available medium that can be accessed by a computer. As an example and not limitation, such a computer-readable medium can include a random access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), an optical disk storage, a magnetic disk storage, other magnetic storage devices, a combination of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
[0023] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and a 5G core (5GC) 190. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.
[0024] Base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with EPC 160 via a backhaul link 132 (e.g., an S1 interface). Base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with 5GC 190 via a backhaul link 184. Among other functions, base stations 102 may perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and device tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the 5GC 190) via a backhaul link 134 (e.g., an X2 interface). The backhaul link 134 may be wired or wireless.
[0025] Base station 102 can communicate wirelessly with UE 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' can have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network can also include a home evolved Node B (eNB) (HeNB), which can provide services to a restricted group called a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 can include an uplink (UL) (also called a reverse link) transmission from UE 104 to base station 102 and / or a downlink (DL) (also called a forward link) transmission from base station 102 to UE 104. The communication link 120 can use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be through one or more carriers. The base station 102 / UE 104 may use up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) of bandwidth per carrier allocated in a carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. The carriers may be adjacent to each other, or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL compared to UL). The component carrier may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell), and the secondary component carrier may be referred to as a secondary cell (SCell).
[0026] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.
[0027] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 in the 5 GHz unlicensed spectrum via a communication link 154. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether the channel is available.
[0028] The small cell 102' may operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may improve coverage and / or increase capacity of the access network.
[0029] Whether it is a small cell 102' or a large cell (e.g., a macro base station), the base station 102 can include an eNB, a gNode B (gNB), or other types of base stations. Some base stations such as gNB 180 can operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with UE 104. When gNB 180 operates at mmW or near mmW frequencies, gNB 180 can be referred to as a mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF ranges from 30 GHz to 300 GHz and has a wavelength between 1 mm and 10 mm. The radio waves in this band can be referred to as millimeter waves. Near mmW can extend down to 3 GHz frequencies with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also called centimeter waves. Communications using mmW / near mmW radio bands have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.
[0030] Base station 180 may transmit beamformed signals in one or more transmit directions 182' to UE 104. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182". UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 may be the same, or may be different. The transmit and receive directions of UE 104 may be the same, or may be different.
[0031] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and collecting eMBMS-related billing information.
[0032] 5GC 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. AMF 192 may communicate with unified data management (UDM) 196. AMF 192 is a control node that handles signaling between UE 104 and 5GC 190. Typically, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, intranet, IP multimedia subsystem (IMS), PS streaming services, and / or other IP services.
[0033] A base station may also be referred to as a gNB, a node B, an evolved node B (eNB), an access point, a basic transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other suitable term. Base station 102 provides an access point to EPC 160 or 5GC 190 for UE 104. Examples of UE 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a health care device, an implant, a sensor / actuator, a display, or any other similar functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
[0034] Reference again Figure 1 In some aspects, the UE 104 may include a wake-up component 198 configured to form a first device wake-up time interval. The first device wake-up time interval may include overlapping wake-up time intervals of multiple applications. In some aspects, the wake-up component 198 may receive a wake-up time interval from each of the multiple applications. The wake-up component 198 may then organize the wake-up time intervals of the multiple applications to form the first device wake-up time interval, such that applications with overlapping wake-up time intervals are grouped together. The wake-up component 198 may schedule device wake-ups during at least the first device wake-up time interval.
[0035] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G / NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G / NR subframe. Figure 2C Figure 250 illustrates an example of a second subframe within a 5G / NR frame structure. Figure 2D280 is a diagram illustrating an example of UL channels within a 5G / NR subframe. The 5G / NR frame structure may be FDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be TDD, where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , 2C In the example provided, it is assumed that the 5G / NR frame structure is TDD, subframe 4 is configured with slot format 28 (primarily DL), where D is DL, U is UL, and X is flexible between DL / UL, and subframe 3 is configured with slot format 34 (primarily UL). Although subframes 3 and 4 are shown with slot formats 34 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are DL and UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically through DL control information (DCI), or semi-statically / statically through radio resource control (RRC) signaling). Note that the description of "infrastructure (inffa)" also applies to the 5G / NR frame structure for TDD.
[0036] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes (1ms) of equal size. Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4, or 2 symbols. Depending on the time slot configuration, each time slot may contain 7 or 14 symbols. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. The symbol on the DL may be a cyclic prefix (CP) OFDM (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-constrained scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter set (numerology). For slot configuration 0, different parameter sets μ from 0 to 5 allow 1, 2, 4, 8, 16 and 32 slots per subframe, respectively. For slot configuration 1, different parameter sets from 0 to 2 allow 2, 4 and 8 slots per subframe, respectively. Therefore, for slot configuration 0 and parameter set μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to 2μ*15kKz, where μ is parameter set 0 to 5. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, and parameter set μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figures 2A-2D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=0 with 1 slot per subframe. The subcarrier spacing is 15 kHz and the symbol duration is approximately 66.7 μs.
[0037] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.
[0038] like Figure 2A As shown, some of the REs carry reference (pilot) signals (RS) of the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for a specific configuration where 100x is the port number). x , but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).
[0039] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs), each CCE including nine RE groups (REGs), each REG including four consecutive REs in an OFDM symbol. The primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of the frame. The UE 104 uses the PSS to determine the subframe / symbol timing and the physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of the frame. The UE uses the SSS to determine the physical layer cell identification group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE may determine the physical cell identifier (PCI). Based on the PCI, the UE may determine the location of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) may be logically grouped using the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides multiple RBs in the system bandwidth as well as a system frame number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information such as System Information Blocks (SIBs) that are not transmitted through the PBCH, and paging messages.
[0040] like Figure 2C As shown, some of the REs carry DM-RS for channel estimation at the base station (indicated as R for one particular configuration, but other DM-RS configurations are possible). The UE can send DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the first one or two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent, and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. Although not shown, the UE can send a sounding reference signal (SRS). The base station can use the SRS for channel quality estimation to enable frequency-dependent scheduling on the UL.
[0041] Figure 2D An example of various UL channels within a subframe of a frame is illustrated. The PUCCH may be positioned as indicated in a configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.
[0042] Figure 33 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0043] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transmission channel, forward error correction (FEC) encoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time domain and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine coding and modulation schemes, and for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.
[0044] At UE 350, each receiver 354RX receives a signal through its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. TX processor 368 and RX processor 356 implement layer 1 functions associated with various signal processing functions. RX processor 356 can perform spatial processing on the information to recover any spatial stream going to UE350. If multiple spatial streams go to UE350, they can be combined into a single OFDM symbol stream by RX processor 356. Then, RX processor 356 converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbol on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by base station 310. These soft decisions can be based on the channel estimate calculated by channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by the base station 310. The data and control signals are then provided to the controller / processor 359, which implements Layer 3 and Layer 2 functions.
[0045] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.
[0046] Similar to the functions described in conjunction with the DL transmission of the base station 310, the controller / processor 359 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression, and security (encryption, decryption, integrity protection, integrity checking); RLC layer functions associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority processing, and logical channel priority.
[0047] The TX processor 368 may select an appropriate coding and modulation scheme and facilitate spatial processing using channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.
[0048] At the base station 310, the UL transmission is processed in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
[0049] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.
[0050] For different applications in the modem of the wireless device, the wake-up event occurs separately. This may burden the battery power of the device, especially Class M1 (CAT M1) and narrowband Internet of Things (NB-IoT) devices. The asynchronous wake-up may cause additional device wake-ups and an average longer amount of time for the device to be active. Each application can provide its wake-up time setting to the power saving mode (PSM) coordinator. The PSM coordinator can be configured to schedule device wake-ups (e.g., exit PSM) based on the earliest application wake-up time setting. The device can wake up several times a day to collect data from various applications (e.g., temperature sensors, outdoor environment sensors, etc.). The device can then send a report with the collected data back to the server. Device wake-up may consume a large amount of power relative to the total power battery life of the device.
[0051] Device wake-ups in lightweight machine-to-machine (LwM2M) client-related events, operations and / or features (e.g., registration updates, information reporting, device management, and service activation) may also be scheduled separately for different events, operations and / or features in an asynchronous manner. Therefore, the device may experience additional device wake-ups and long durations for each wake-up, which may result in significant and unnecessary power consumption, especially for NB-IoT and / or CAT-M1 devices. Such devices may have limited power and may have limited battery capacity without connection to any external power source. In some cases, the battery life of current devices may be reduced by several years, in part due to the manner in which device wake-ups are performed. Therefore, power optimization of such devices is required to ensure efficient use of wireless resources and battery power and the longevity of the device. Optimizing the manner in which the device wakes up may result in a reduction in the number of wake-up events, which may extend the life of the battery. For example, if a device that experiences 4 device wake-ups in a day is able to reduce device wake-ups to 3 in a day, the reduction may result in an extended battery life and a longer life for the device.
[0052] In some aspects, the device wake-up process can be optimized to allow multiple applications and / or operations (e.g., IoT applications, LwM2M operations) to be grouped together and executed in the same wake-up instance, which can reduce power consumption to improve battery life, for example, in resource-constrained devices (e.g., NB-IoT and CAT M1 devices). As presented herein, the grouping or synchronization of multiple events in the same device wake-up can reduce the number of required device wake-ups and the average duration of each wake-up. In some aspects, synchronization can occur across multiple applications. These applications can run independently and can be unaware of the operations of other applications of the device. Each application can be configured to provide a wake-up time interval to a component configured to coordinate the wake-up of each application in a combined manner. For example, each application can provide a wake-up time interval to a PSM coordinator, which can be configured to schedule a single wake-up interval for multiple applications with overlapping wake-up intervals. In some aspects, at least one of the applications can be configured to provide a preferred wake-up time interval and / or an associated priority for further optimizing the wake-up time scheduling. In some aspects, a client (eg, a PSM-aware LwM2M device) may be configured to synchronize multiple events / operations occurring within a specified time interval or within a dynamically calculated time interval.
[0053] Figure 4A and 4BIt is a diagram illustrating various aspects of device wakeup according to certain aspects of the present disclosure. The diagrams 400, 401 illustrate wakeup optimization for multiple applications (e.g., IoT applications). Diagram 400 includes application 1 402, application 2 404, and application 3 406. Applications 402, 404, 406 operate independently of each other and may not know when other applications are running and / or when other applications are scheduled to run. Each application 402, 404, 406 can be configured to provide a corresponding proposed wakeup interval 408 to the PSM coordinator of the device, rather than providing a specific time value. The proposed wakeup interval 408 can be a time range during which an application may need to perform an operation (e.g., a communication operation). In some aspects, the application sends a communication to the server during the proposed wakeup interval 408. In some aspects, the application monitors the communication during the proposed wakeup interval 408 and / or sends the communication during the proposed wakeup interval 408. The transmission can be in response to the communication received when monitoring during the proposed wakeup interval, or it can be a scheduled transmission. Each application 402, 404, 406 may also be configured to provide a duration for the application to perform an operation. In some aspects, the duration may be provided within the proposed wake-up interval 408. In some aspects, the duration may be provided separately from the proposed wake-up interval 408. The application only needs to perform a wake-up during a portion of the proposed wake-up interval 408, and does not require the device to be awakened throughout the interval. The application performs a wake-up during a portion of the proposed wake-up interval 408 for the duration required to perform the operation. In order for the application to perform the operation, the device must wake up (e.g., exit PSM). In this way, the proposed wake-up interval 408 provides a time range in which the device needs to wake up to allow the application to perform the operation.
[0054] In some aspects, the wake-up time interval may include a start time and an end time. In some aspects, the wake-up time interval may include a start time and a duration. At least one advantage of utilizing a wake-up time interval is that a device wake-up may occur at any time within the range of the proposed wake-up time interval 408 for an application, such that more than one application (e.g., applications 402, 404, 406) may be able to perform its operations during the wake-up time intervals of different applications, as compared to a situation where specific wake-up times of different applications overlap in time. This allows multiple applications to synchronize their device wake-ups, which may reduce the number of wake-ups performed by the device.
[0055] Referring to FIG. 4 , application 1 402 has a wakeup interval 408 that starts first in time. The wakeup interval 408 of application 1 402 provides a time range in which the device must wake up to allow application 1 402 to perform its operations. Application 2 404 has a wakeup interval 408 that starts after the wakeup interval of application 1. The wakeup intervals of each application may be the same or different. In the aspect of FIG. 4 , the wakeup intervals of application 1 402 and application 2 404 start at different times, but may end at the same time or approximately the same time. Application 3 406 has a wakeup interval 408 that starts after the wakeup intervals of application 1 402 and application 2 404, and has an end time that extends beyond the end of the wakeup intervals of application 1 402 and application 2 406. The overlap region 414 is the time when the wakeup intervals of applications 402, 404, 406 overlap, so that all three applications 402, 404, 406 can perform their operations within the overlap region 414. In this way, the device can wake up during the overlapping region 414 to allow the applications 402, 404, 406 to perform their operations. The overlapping region 414 provides a time when the applications 402, 404, 406 can perform their operations within a single device wakeup. In some aspects, when determining the actual scheduled wakeup 412, the duration that each application needs to perform the corresponding operation within the corresponding wakeup interval 408 can be considered. For example, the total duration of executing the operations of each application should fall within the overlapping region 414 so that all operations can be performed within the overlapping region 414. Considering the corresponding duration can ensure that the actual scheduled wakeup 412 occurs within the overlapping region 414, while providing sufficient time for all operations to be performed before the overlapping region 414 ends. The overlapping region 414 reduces the number of times the device wakes up, which improves battery life and performance.
[0056] Figure 4B A diagram 401 is illustrated in which applications 402, 404, 406 may further provide preferred intervals 410 within a wakeup interval 408, the preferred interval 410 identifying a time range at which the application prefers to perform its operation. In other words, the preferred interval 410 identifies a time at which the application prefers a device wakeup to occur in order to perform its operation. The preferred interval 410 is a shorter time range within the time range of the wakeup interval 408. Although the device may prefer the indicated preferred interval, the device wakeup may still occur within an interval 408 outside of the preferred interval 410. In the event that multiple preferred intervals 410 of multiple applications overlap, the PSM may determine that the device wakeup will occur within the preferred interval 410.
[0057] Reference again Figure 4B, application 1 402 has a preferred interval 410 that is first in time. The preferred interval 410 for any of the applications can occur at any time within the corresponding wake-up interval 408, and need not occur at a specific time. Application 2 404 has a preferred interval 410 that begins after the preferred interval of application 1 ends. Application 3 has a preferred interval 410 that partially overlaps with the preferred interval 410 of application 2. The overlapping portion of the preferred intervals of application 2 and application 3 forms a preferred region 416. The preferred region 416 is a time when multiple applications (e.g., application 2 404 and application 3 406) have overlapping preferred intervals 410, so that the three applications 402, 404, 406 can perform their operations within the preferred region 416. In this way, the device can wake up during the preferred region 416 to allow the applications 402, 404, 406 to perform their operations. The preferred region 416 provides a time when the applications 402, 404, 406 can perform their operations within a single device wake-up. As shown in FIG. 4 , preferred region 416 is smaller than overlap region 414 and thus further optimizes the device wake-up process by reducing the total time that the device is active. Although preferred interval 410 of application 1 is outside preferred region 416, the preferred region is within wake-up interval 408 of application 1, which allows application 1 to perform its operations during preferred region 416. In this case, not all preferred intervals 410 overlap, but because at least two preferred intervals overlap, preferred region 416 can be defined by the overlapping portions of the preferred intervals. In some aspects, the preferred intervals 410 of the applications may not overlap, and in this case, device wake-up can be based on overlap region 414.
[0058] In one example, the PSM may schedule wakeups to occur within a maximum number of overlapping preferred intervals. In another example, the PSM may schedule wakeups to occur within at least one preferred interval based on the preferred intervals or the priority of the corresponding application. In yet another example, the PSM may schedule wakeups to occur regardless of the preferred intervals and / or priority levels, such that the schedule minimizes the total number of wakeups.
[0059] Information related to the wake-up interval 408 and the preferred interval 410 can be provided by the application to the PSM coordinator. The PSM coordinator collects the wake-up intervals 408 and the preferred intervals 410 from each application and is configured to sort these intervals. The earliest wake-up interval is the wake-up interval with the earliest start time among the collected wake-up intervals. The PSM coordinator can be configured to group the wake-up time intervals of the application and arrange them in chronological order. The PSM coordinator can then identify the first device wake-up time interval including the overlapping wake-up time intervals of the application, as shown in Figure 4. In some aspects, the PSM coordinator can be configured to identify whether the earliest wake-up interval 408 overlaps with any of the other wake-up intervals. In this case, the PSM coordinator can identify such an overlap as an overlap area 414, so that the PSM can schedule device wake-ups within the overlap area 414 so that the overlapping applications perform their respective operations. The PSM coordinator can also be configured to identify the preferred wake-up time interval (e.g., preferred interval 410) within each wake-up interval 408. In some aspects, the PSM coordinator can identify the overlapping sub-intervals (e.g., preferred area 416) including at least two preferred wake-up time intervals. In this case, the PSM coordinator can then schedule the device wakeup during the subinterval (e.g., preferred region 416). The subinterval (e.g., preferred region 416) can include an overlap of a maximum number of preferred wakeup time intervals from each of the multiple applications. At least one advantage is that the device wakeup can be scheduled during the subinterval (e.g., preferred region 416) to synchronize multiple operations within the subinterval. This allows the applications to perform their respective operations within the subinterval (e.g., preferred region 416) and reduce the overall wakeup time of the device.
[0060] In some aspects, the PSM coordinator may be configured to identify a preferred wake-up time interval (e.g., preferred interval 410) and an associated priority value within each wake-up time interval from each of the applications. Each preferred wake-up time interval may include a time range that the corresponding application indicates as preferably performing an operation. In some aspects, each preferred wake-up time interval may be less than or equal to the corresponding wake-up time interval. Each preferred wake-up time interval may have a priority based on an associated priority value. Each of the applications may be configured to provide a proposed priority associated with its preferred interval 410. Once the PSM coordinator has sorted the wake-up intervals and arranged them in a sequential order, and has identified the device wake-up intervals (e.g., overlapping regions 414), the PSM coordinator may be configured to subsequently identify all preferred intervals 410 and associated priorities. The PSM coordinator may then schedule device wake-ups during the highest priority preferred wake-up time interval (e.g., preferred interval 410). For example, as shown in FIG. 4, a preferred region 416 is identified in association with the overlap of the preferred intervals 410 of application 2 404 and application 3 406. Although not explicitly defined in FIG. 4 , either Application 2 or Application 3 may have a preferred wake-up time interval of the highest priority.
[0061] The PSM coordinator may be configured to effectively schedule device wake-ups based on information received from the application. In some aspects, one or more applications may be configured to provide multiple wake-up intervals to the PSM coordinator. Multiple wake-up time intervals may correspond to the periodicity of events associated with one or more of the applications. An event may include an operation that the application needs to be performed by the UE, such as (multiple) operations including performing measurements, evaluating measurements, performing registrations, performing registration updates, providing information reports, etc. Therefore, the event requires the UE to wake up in order to perform the operation. Therefore, the PSM coordinator may have a complete view of future scheduling opportunities and be able to synchronize future device wake-ups more effectively. In some aspects, the PSM coordinator may be configured to share the latest device wake-up schedule (including associated periodicity (if any)) with the application as an asynchronous notification. These applications may then be configured to adjust and / or update their respective wake-up intervals based on the entire device wake-up schedule. In some aspects, the application may also query the latest device schedule before proposing its own wake-up interval to the PSM coordinator. Then, the application may be able to further adjust and / or update its respective wake-up interval based on the latest device schedule. In some aspects, the application may also submit a request for a preferred wake-up period, an anchor time, or an anchor time range. An anchor time may be a specific time at which a device wakes up to perform an operation. For example, an application may have an anchor time of two hours, causing the device to wake up every two hours to perform its operation. In some examples, an application may have an anchor time range (e.g., every 2-3 hours), causing the device to wake up every 2-3 hours to perform its operation. In response to a request from an application, the PSM coordinator may be configured to provide a preferred wake-up period, a preferred anchor time within the provided range, and based on the PSM coordinator's knowledge of the current schedule.
[0062] In some aspects, such as Figure 5 As shown, if the first wake-up interval 506 does not overlap with any of the remaining wake-up intervals (e.g., the wake-up interval 506 of application 2 504), the PSM coordinator can be configured to schedule the first device wake-up 508 of application 1 502 near the end of the first wake-up time interval 510. The PSM coordinator can also be configured to schedule the second device wake-up 508 of application 2 504 at a time closer to the beginning of the second wake-up time interval 512. Over time, the first device wake-up and the second device wake-up can be scheduled to align with each other so that the first device wake-up 508 and the second device wake-up 508 can overlap at area 514 in future wake-up time intervals. Figure 5In the aspect of FIG. 5 , application 1 502 may have a wake-up interval separation 510 of 10 hours, and application 2 504 may also have a wake-up interval separation 510 of 10 hours. In this case, the first wake-up intervals of the applications do not overlap, and in response, the PSM coordinator may schedule the device wake-up of application 1 closer to the end of its wake-up interval while also scheduling the device wake-up of application 2 closer to the start time of its wake-up interval. After the first 10-hour separation period of application 1 and application 2 has elapsed, the wake-up intervals 506 of application 1 and application 2 still do not overlap, but occur closer together than before. However, after the second 10-hour separation period of application 1 and application 2 has elapsed, the corresponding wake-up intervals 506 now overlap and form a region 514, so that application 1 and application 2 can perform their operations during the same device wake-up time.
[0063] Figure 6 600 is a diagram illustrating device wakeup according to certain aspects of the present disclosure. Unlike wakeup events triggered by applications at the device, an LwM2M client device may require device wakeup for events, operations, and / or features, such as, but not limited to, registration updates, information reporting, device management, and / or service initiation. Diagram 600 illustrates how aspects presented herein may optimize (e.g., synchronize) the wakeup of an LwM2M device. While some LwM2M devices may not have parameters or configurations that direct when the device should wake up (e.g., exit PSM) to evaluate measurement values during a measurement evaluation period between a minimum period (pmin) and a maximum period (pmax), other LwM2M devices may use two properties, such as a minimum evaluation period (epmin) that indicates the minimum time that the LwM2M client must wait between two evaluations of a reporting criterion, and a maximum evaluation period (epmax) that indicates the maximum time that the LwM2M client can wait between two evaluations of a reporting criterion. A device may enter PSM during epmin, and after expiration of epmax, the device must exit PSM and perform measurement evaluation.
[0064] Figure 7 is a diagram 700 illustrating an evaluation period according to certain aspects of the present disclosure. Figure 7, the information reporting interface (e.g., which performs observation and notification operations) can limit the measurement evaluation to occur before the pmin expiration 712, where pmin 704 is the minimum time interval between two reports to the server, and the previous report 710 is the most recent report sent to the server. At the pmin expiration 712, the measurement evaluation can be performed. After the pmin expiration, the measurement evaluation can be performed periodically during the measurement evaluation period 702, and a report can be issued if the measured value meets certain criteria. At the pmax expiration 714, the device wakes up and the report 720 is issued immediately. Pmax 706 is the maximum time interval between two reports to the server. Between pmin 704 and pmax 706 are epmin expiration 716 and epmax expiration 718, and these define how often the measurement evaluation should be performed between the pmin expiration 712 and the pmax expiration 714. Measurement evaluations may be performed at precise times (e.g., at epmin expiration 716 and epmax expiration 718), and the device may need to be woken up at each measurement evaluation, which may result in multiple device wakeups and reduce battery life. However, in order to optimize device wakeup, an incremental interval (Δ) may be introduced so that operations (e.g., measurement evaluations) may be performed over a time range rather than at a precise time (e.g., pmin expiration 712). The time range may be a precise time plus an incremental interval. For example, instead of measuring at the precise time of pmin expiration 712, measurements may occur within pmin expiration 712 and pmin expiration 712 plus an incremental interval. In some aspects, the incremental interval may be configured as a fixed value, or may be dynamically determined to synchronize multiple applications / activities / operations in a single wakeup. As discussed above, the device may stay in PSM until pmin expires, and after pmin expires (e.g., at time T1), the device may be configured to wake up in an interval of (T1, T1+Δ). For pmax, the LwM2M client must send a report before pmax expires (eg, at time T2), or within an interval of (T2-Δ, T2) if not completed yet. As used herein, the terms application, activity, and operation are interchangeable.
[0065] In some aspects, the incremental interval may be a function of epmax, epmin, pmin, pmax, or device configuration. In some aspects where epmin and epmax are defined, the incremental interval may be equal to the difference between epmax and epmin (e.g., epmax-epmin). In some aspects where epmax and epmin are not defined, the incremental interval may be based on multiple different attributes, for example, as a portion of pmin, a portion of pmax, pmin, a pre-configured default value, or a configuration value for a measurement type. The incremental interval may be applied to all device wakeups including pmin, pmax, and measurement evaluations. In some aspects, the incremental interval may be a function of the lifetime of the registration. For example, some implementations of lifetime extension require that registration updates be issued during the last 10% of the registration lifetime (e.g., between 90% and 100% of the registration lifetime). In some aspects, the incremental interval may have a lower importance for some events that are unlikely to coincide with other events (such as, but not limited to, bootstrap and registration). Therefore, the incremental interval may not be used for certain events, such as bootstrap and registration.
[0066] Back to reference Figure 6, diagram 600 shows multiple measurement evaluations (602, 604, 606, 608) that may need to be performed by, for example, an LwM2M device. epmax 610 and epmin 612 are defined based on a previous measurement evaluation 614 of operation 1602. epmin expiration 616 of operation 1602 is shown at the end of the range of epmin 612. epmax expiration 618 of operation 1602 is shown at the end of the range of epmax 610. Incremental intervals 620 of operation 1602 can be configured to provide intervals so that operation 1 can perform measurement evaluations within the incremental intervals 620, so that the measurement evaluations of operation 1 can occur simultaneously with the measurement evaluations of operations 2-4 604, 606, 608 to synchronize device wake-ups for operations 1-4. Each operation 602, 604, 606, 608 can correspond to an LwM2M application. Each operation 602, 604, 606, 608 has a corresponding incremental interval 620, and the LwM2M client can be configured to identify where the incremental intervals 620 can overlap to form an overlap area 624. The LwM2M client can be configured to sort the operations based on the previous measurement evaluation 614 and determine the wake-up time interval for each of the multiple operations. In some aspects, each wake-up time interval includes a start time and an incremental interval based on one or more of an application type, a configured time interval, or an operation interval configured by a server. The LwM2M client can then form an overlap area 624 where the corresponding incremental intervals 620 of each operation overlap, and can schedule device wakeups 622 within the overlap area 624. This optimizes the device wakeups 622 so that only one device wakeup is required to allow the operations 602, 604, 606, 608 to be performed.
[0067] Figure 8800 is a diagram illustrating synchronized device wakeup for different operations according to certain aspects of the present disclosure. Diagram 800 is directed to optimization of device wakeup for different LwM2M operations. For example, diagram 800 includes a measurement evaluation operation 802, a second operation / event / function that requires wakeup 804, a third operation / event / function that requires wakeup 806, and a registration update 808. Each of these operations requires the device to wake up to allow the operation to perform a function. In order to synchronize different LwM2M operations / events / functions (e.g., boot, registration, and information reporting), a wakeup interval time (e.g., a start time and an incremental interval (Δ)) may be determined for each operation / event / function. In some aspects, the incremental interval (Δ) of each operation / event / function may be configured (e.g., a fixed value) or may be dynamically determined. In some aspects, the wakeup interval start time and the wakeup type may be determined based on the type of operation / event / function. For example, a wakeup interval time (e.g., a start time and an increment interval (Δ)) associated with an LwM2M registration update operation for lifetime extension may be determined using a configured percentage of the registration lifetime (e.g., issuing a registration update during the last 5% of the registration lifetime). A wakeup interval time associated with an LwM2M boot retry attempt may be determined using a configured retry time value. For example, if a boot attempt fails, the device may attempt additional retries with an increasing delay between each subsequent attempt (e.g., 2 minutes, 4 minutes, 8 minutes, 16 minutes).
[0068] epmax 810 and epmin 812 are defined based on a previous measurement evaluation 814. The device wakeup that occurs for the measurement evaluation 802 occurs after the expiration of pmin and before the expiration of pmax. Another event that requires the device to wake up occurs at the expiration of pmax 804, where a report must be sent to the server before the expiration of the pmax. In some aspects, the wakeup time interval associated with the maximum evaluation period can be based on the difference between epmax and epmin (if both epmax and epmin are defined), or at least one of a configured percentage of pmax. Another event that also requires the device to wake up occurs at the expiration of pmin 806 after pmin for measurement evaluation. In some aspects, the wakeup time interval associated with the minimum period can be based on at least one of the maximum evaluation period, the minimum evaluation period, or a predefined evaluation period. In some aspects, the wake-up interval associated with the measurement evaluation can be based on at least one of: the difference between epmax and epmin (if both epmax and epmin are defined); a configured percentage of pmin (if pmin is defined); a configured percentage of pmax (if pmax is defined); or a configured default value. Another event that requires the device to wake up is a registration update 808, where a registration update is sent to the server to extend its lifetime. Figure 8 As shown, instead of performing operations at specific times, the introduction of incremental intervals 820 allows operations to be performed within a time range, so that any overlapping incremental intervals 820 can be identified, grouped together, and used to schedule a single device wakeup 822. Overlapping areas 824 can be identified in time intervals, and devices can wake up in this time interval and allow measurement evaluation 802 to be performed, allow pmax expiration 804 to send reports to the server, allow pmin expiration 806 to perform measurement evaluation, and allow registration updates 808 to send registration updates to the server to extend its life. Any combination of these events (802, 804, 806, 808) can be scheduled to be performed during one device wakeup interval without requiring four different device wakeups. This optimizes LwM2M operations to a reduced amount of device wakeups, which further extends battery life and reduces the duration that devices are activated.
[0069] Fig. 9 900 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104, 350, apparatus 1002 / 1002'). Optional aspects are shown in dashed lines. Various aspects of the method may help the UE optimize device wake-up time to allow multiple operations to be performed efficiently.
[0070] At 902, the UE may receive a wake-up time interval from multiple applications, such as in conjunction with Figure 4A , 4B, 6 and 8. The wake-up time interval may include a range during which the device may need to wake up to allow the corresponding application to perform operations. For example, the LwM2M client may need to coordinate device wake-up for different events / operations / features, such as measurement evaluation 802 occurring after pmin expiration and before pmax expiration, registration update 808 for sending a registration update to a server, and / or pmax expiration 804 for which a report must be sent to a server before pmax expiration. In some aspects, the wake-up time interval may include a start time and an end time. In some aspects, the wake-up time interval may include a start time and a duration. In yet other aspects, multiple wake-up time intervals may be received from at least one of multiple applications using the periodicity of events associated with each of the multiple wake-up time intervals. An event may include an operation that an application requires to be performed by the UE, such as (multiple) operations including any one of performing measurements, evaluating measurements, performing registrations, performing registration updates, providing information reports, etc. Therefore, the event requires the UE to wake up in order to perform the operation.
[0071] Each wake-up time interval received at 902 may correspond to a preferred wake-up time interval (e.g., 414, 514, 624, 824) of a corresponding application in a plurality of applications. In some aspects, the UE may identify a subinterval (e.g., 416) that includes an overlap of a maximum number of preferred wake-up time intervals from each of the plurality of applications, e.g., an overlap of at least two preferred wake-up time intervals. In some aspects, the preferred wake-up time interval for each respective wake-up time interval may include a time range in which the respective application prefers to perform an operation. Each preferred wake-up time interval may be less than the corresponding wake-up time interval. In some aspects, the subinterval may maximize the number of preferred intervals included in the overlap.
[0072] At 906, the UE may determine a wake-up time interval for each of the plurality of operations. In some aspects, each wake-up time interval includes a start time and an increment interval based on one or more of an application type, a configured time interval, or an operation interval configured by a server, such as in conjunction with Figure 6 The increment interval is 620 and Figure 8 820 in . In some aspects, the incremental interval can be a fixed value, or can be dynamically determined to synchronize multiple operations within the incremental interval. In some aspects, when the maximum evaluation period (epmax) and the minimum evaluation period (epmin) are known, the incremental interval can be the difference between the maximum evaluation period (epmax) and the minimum evaluation period (epmin).
[0073] At 908, the UE may form a first wake-up time interval (eg, 416). In some aspects, the first wake-up time interval may include overlapping wake-up time intervals for multiple applications.
[0074] At 910, the UE may schedule device wakeups during a first wakeup interval (e.g., 412 in conjunction with 414). At 912, the UE may schedule device wakeups during subintervals (e.g., 412 in conjunction with 416). In some aspects, the preferred wakeup time intervals may have associated priority values. Device wakeups may be scheduled during the highest priority preferred wakeup time interval having the highest priority value associated with the preferred wakeup time intervals. In some aspects, if the first wakeup time interval does not overlap with the second wakeup time interval, the UE may schedule the first device wakeup near the end of the first wakeup time interval at 914 (e.g., 412 in conjunction with 416). Figure 5 ), and at 916, the UE may schedule the second device to wake up at the beginning of the second wake-up time interval (also as shown in Figure 5 ). The first device wake-up and the second device wake-up can be scheduled to align the future device wake-ups in the future wake-up time interval. In some aspects, the device wake-up schedule can be provided to each of a plurality of applications, wherein at least one of the plurality of applications is configured to adjust its wake-up time interval based on the device wake-up schedule. In some aspects, a request can be received from at least one of the plurality of applications, wherein the device wake-up schedule is provided in response to the request from at least one of the plurality of applications. In some aspects, a request for wake-up information can be received from at least one of the plurality of applications, wherein the wake-up information includes at least one of a preferred wake-up period, an anchor time, or an anchor time range. The wake-up information can be provided to at least one of the plurality of applications in response to the request.
[0075] Fig.101 is a conceptual data flow diagram 1000 illustrating the data flow between different parts / components in an exemplary apparatus 1002. The apparatus may be a UE (e.g., 104, 350, apparatus 1102 / 1102') in wireless communication with a base station 1050 (e.g., base station 102, 180, 310). The apparatus includes a receiving component 1004 that receives downlink communications from the base station 1050. The apparatus may include a wake-up time interval component 1006 that receives a wake-up time interval and / or receives an indication of a client-related event / operational feature that requires wake-up from each of a plurality of applications 1021, 1022, 1023. The apparatus may also include: a preferred component 1008, wherein each wake-up time interval corresponds to a preferred wake-up time interval (e.g., 414, 514, 624, 824) within each wake-up time interval; a determining component 1010, which is configured to determine a wake-up time interval including a start time and an increment interval for each of a plurality of operations based on one or more of an application type, a configured time interval, or an operation interval configured by a server; a forming component 1012 that forms a first wake-up time interval; a scheduling component 1014 that schedules device wake-ups during the first wake-up interval; a sub-interval scheduling component 1016 that schedules device wake-ups during a sub-interval; and a sending component 1018 that sends an uplink communication to a base station 1050. In some aspects, the first device wake-up time interval formed by the forming component 1014 may include overlapping wake-up intervals for a plurality of applications or a plurality of operations. In one example, if the second wake-up time interval does not overlap with the third wake-up time (or with any of the remaining wake-up time intervals), the scheduling component 1014 may schedule the second device to wake up near the end of the second wake-up time interval and schedule the third device near the beginning of the third wake-up time interval.
[0076] The apparatus may include executing Fig. 9 Each of the blocks in the algorithm in the above flowchart is an additional component. In this way, it can be performed by the component Fig. 9 Each block in the above flowchart of the present invention may include one or more of these components. These components may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination of these.
[0077] Fig.111 is a diagram 1100 illustrating an example of a hardware implementation of an apparatus 1002' employing a processing system 1114. The processing system 1114 may be implemented with a bus structure, generally represented by a bus 1124. The bus 1124 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1114. The bus 1124 links together various circuits including one or more processors and / or hardware components represented by the processor 1104, components 1004, 1006, 1008, 1010, 1012, 1014, 1016, and 1018, and the computer readable medium / memory 1106. The bus 1124 may also link various other circuits known in the art, such as timing sources, peripherals, voltage regulators, and power management circuits, and therefore will not be described further.
[0078] The processing system 1114 may be coupled to the transceiver 1110. The transceiver 1110 is coupled to one or more antennas 1120. The transceiver 1110 provides components for communicating with various other devices over a transmission medium. The transceiver 1110 receives signals from the one or more antennas 1120, extracts information from the received signals, and provides the extracted information to the processing system 1114 (specifically, to the receiving component 1004). In addition, the transceiver 1110 receives information from the processing system 1114 (specifically, from the transmitting component 1018), and based on the received information, generates a signal to be applied to the one or more antennas 1120. The processing system 1114 includes a processor 1104 coupled to a computer-readable medium / memory 1106. The processor 1104 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1106. When executed by the processor 1104, the software causes the processing system 1114 to perform the various functions described above for any particular device. The computer-readable medium / memory 1106 may also be used to store data that is manipulated by the processor 1104 when executing software. The processing system 1114 also includes at least one of the components 1004, 1006, 1008, 1010, 1012, 1014, 1016, and 1018. The component may be a software component running in the processor 1104, a software component resident / stored in the computer-readable medium / memory 1106, one or more hardware components coupled to the processor 1104, or some combination thereof. The processing system 1114 may be a component of the UE 350 and may include the memory 360, and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359.
[0079] In one configuration, an apparatus 1002 / 1002′ for wireless communication includes components for receiving wake-up time intervals from each of a plurality of applications (e.g., at least a wake-up time interval component 1006), components for forming a first wake-up time interval (the first device wake-up time interval including overlapping wake-up time intervals of the plurality of applications) (e.g., at least a grouping component 1014), components for scheduling device wake-ups during at least the first wake-up time interval (e.g., at least a scheduling component 1016), components for identifying a preferred wake-up time interval within each wake-up time interval from each of the plurality of applications (e.g., at least an identification component 1008), components for identifying a subinterval that includes an overlap of a maximum number of preferred wake-up time intervals from each of the plurality of applications, components for scheduling device wake-ups within the subinterval (e.g., at least a subinterval scheduling component 1016) (the subinterval including overlaps of the preferred wake-up time intervals from each of the plurality of applications The method further comprises a component for scheduling a first device wakeup near the end of the first wakeup time interval (e.g., at least a scheduling component 1014) for scheduling a second device wakeup at the beginning of the second wakeup time interval (e.g., at least a scheduling component 1014), a component for providing a device wakeup schedule to each of the plurality of applications (wherein at least one of the plurality of applications is configured to adjust its wakeup time interval based on the device wakeup schedule) (e.g., at least a wakeup time interval component 1006), and a component for determining a wakeup time interval including a start time and an increment interval for each of the plurality of operations based on one or more of an application type, a configured time interval, or an operation interval configured by a server (e.g., at least a determining component 1010). The aforementioned components may be one or more of the aforementioned components of the apparatus 1002 and / or the processing system 1114 of the apparatus 1002', which are configured to perform the functions described by the aforementioned components. As described above, the processing system 1114 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Likewise, in one configuration, the above components may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions described by the above components.
[0080] Optimizing the way in which the device wakes up can result in a reduction in the number of daily wakeups, which can extend the life of the battery. In some cases, these devices may experience 4 device wakeups in a day, and reducing the device wakeups to 3 times a day may result in an extension of the life of the battery and the device. Grouping or synchronization of multiple events in the same device wakeup can reduce the number of required device wakeups and the average duration of each wakeup. In some aspects, synchronization can occur across multiple applications. These applications typically run independently and may not be aware of the operations of other applications. Each application is configured to provide a wakeup time interval, and the PSM coordinator can be configured to schedule a single wakeup interval for multiple applications with overlapping wakeup intervals. The advantage of synchronizing multiple events to at least one of a single device wakeup is that battery life can be improved due to the reduction in device wakeups and the power savings associated with reducing the number of device wakeups.
[0081] It should be understood that the specific order or hierarchy of each frame in the disclosed process / flow chart is an illustration of an exemplary scheme. Based on design preferences, it should be understood that the specific order or hierarchy of each frame in the process / flow chart can be rearranged. In addition, some frames can be combined or omitted. The attached method claims present the elements of each frame in a sample order and are not meant to be limited to the specific order or hierarchy presented.
[0082] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. For those skilled in the art, various modifications to these aspects will be apparent, and the general principles defined herein can be applied to other aspects. Therefore, the present claim is not intended to be limited to the various aspects shown herein, but to conform to the full scope consistent with the language claim, wherein, unless otherwise specified, the singular reference element is not intended to represent "one and only one", but to represent "one or more". The word "exemplary" is used herein to represent "used as an example, instance, or explanation". Any aspect described as "exemplary" herein does not have to be interpreted as being superior to or advantageous to other aspects. Unless otherwise clearly stated, the term "some" refers to one or more. Such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, phrases such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be included by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly recited in the claims. The words "module," "mechanism," "element," "device," and the like may not replace the word "component." Thus, unless a claim element is explicitly recited using the phrase "component for...", any claim element should not be interpreted as a component plus function.
Claims
1. A method for wireless communication at a user equipment (UE), comprising: receiving a wake-up time interval for each of each of the one or more operations in the plurality of applications, wherein each wake-up time interval comprises a preferred wake-up time interval; forming a first wake-up time interval, the first wake-up time interval comprising overlapping wake-up time intervals of the plurality of applications or the plurality of operations; scheduling device wake-up during at least a subinterval of the first wake-up time interval, the subinterval comprising an overlap of at least two preferred wake-up time intervals; and performing said device wake-up during said subinterval, When the corresponding preferred wake-up time intervals of some of the multiple applications are not included in the sub-interval, the some of the applications are also allowed to perform their operations during the sub-interval.
2. The method according to claim 1, wherein: The wake-up time interval from each of the plurality of applications includes a time range for the respective application to perform communication operations.
3. The method according to claim 2, wherein: The wake-up time interval from each of the plurality of applications includes a start time and one of an end time or a duration.
4. The method according to claim 1, wherein: An application among the plurality of applications indicates a plurality of wake-up time intervals corresponding to periodicity of an event associated with the application.
5. The method according to claim 1, The at least two preferred wake-up time intervals include a maximum number of preferred wake-up time intervals from each of the plurality of applications.
6. The method according to claim 1, wherein each preferred wake-up time interval comprises a time range indicated by each application as preferably performing an operation, and each preferred wake-up time interval is less than or equal to the corresponding wake-up time interval.
7. The method according to claim 1, wherein: Each preferred wake-up time interval has a priority based on an associated priority value, and wherein the device is scheduled to wake up during the highest priority preferred wake-up time interval.
8. The method according to claim 1, wherein: The first wake-up time interval does not overlap with the second wake-up time interval, and the first wake-up time interval is separated from the second wake-up time interval by a configured duration, and the method further includes: scheduling the device to wake up near the end of the first wake-up time interval; and The second device is scheduled to wake up at the beginning of the second wake-up time interval. 9 . The method of claim 8 , wherein the device wakeup and the second device wakeup are scheduled to align the device wakeup and the second device wakeup in a future wakeup time interval.
10. The method according to claim 1, further comprising: A device wake-up schedule is provided to each of the plurality of applications, wherein at least one of the plurality of applications is configured to adjust a wake-up time interval of the at least one of the plurality of applications based on the device wake-up schedule.
11. The method according to claim 1, further comprising: receiving a request for wake-up information from at least one of the plurality of applications, wherein the wake-up information includes at least one of a preferred wake-up period, an anchor time, or an anchor time range; as well as The wake-up information is provided to the at least one of the plurality of applications in response to the request.
12. The method according to claim 1, further comprising: A wake-up time interval is determined for each of the plurality of operations, each wake-up time interval including a start time and an increment interval based on one or more of an application type, a configured time interval, or an operation interval configured by a server.
13. The method according to claim 12, wherein: Each of the plurality of operations corresponds to a lightweight machine-to-machine (LwM2M) application.
14. The method of claim 13, wherein the wake-up time interval is associated with a minimum period, wherein the minimum period is based on at least one of a maximum evaluation period, a minimum evaluation period, or a predefined evaluation period.
15. An apparatus for wireless communication, comprising: at least one processor coupled to the memory, the at least one processor configured to: receiving a wake-up time interval for each of each of the one or more operations in the plurality of applications, wherein each wake-up time interval comprises a preferred wake-up time interval; forming a first wake-up time interval, the first wake-up time interval comprising overlapping wake-up time intervals of the plurality of applications or the plurality of operations; scheduling device wake-up during at least a subinterval of the first wake-up time interval, the subinterval comprising an overlap of at least two preferred wake-up time intervals; and performing said device wake-up during said subinterval, When the corresponding preferred wake-up time intervals of some of the multiple applications are not included in the sub-interval, the some of the applications are also allowed to perform their operations during the sub-interval.
16. The apparatus of claim 15, wherein the at least two preferred wake-up time intervals comprise a maximum number of preferred wake-up time intervals from each of the plurality of applications.
17. The device according to claim 15, wherein: The first wake-up time interval does not overlap with the second wake-up time interval, and the at least one processor is further configured to: scheduling the device to wake up near the end of the first wake-up time interval; and The second device is scheduled to wake up at the beginning of the second wake-up time interval.
18. The apparatus of claim 15, wherein the at least one processor is further configured to: A wake-up time interval is determined for each of the plurality of operations, each wake-up time interval including a start time and an increment interval based on one or more of an application type, a configured time interval, or an operation interval configured by a server.
19. An apparatus for wireless communication, comprising: means for receiving a wake-up time interval for each of each of the one or more operations in the plurality of applications, wherein each wake-up time interval comprises a preferred wake-up time interval; means for forming a first wake-up time interval, the first wake-up time interval comprising overlapping wake-up time intervals of the plurality of applications or the plurality of operations; means for scheduling a device wakeup during a subinterval of at least said first wakeup time interval, said subinterval comprising an overlap of at least two preferred wakeup time intervals; as well as means for performing wake-up of said device during said subinterval, When the corresponding preferred wake-up time intervals of some of the multiple applications are not included in the sub-interval, the some of the applications are also allowed to perform their operations during the sub-interval.
20. The apparatus of claim 19, wherein the at least two preferred wake-up time intervals comprise a maximum number of preferred wake-up time intervals from each of the plurality of applications.
21. The device according to claim 19, wherein The first wake-up time interval does not overlap with the second wake-up time interval, and the apparatus further comprises: means for scheduling the device to wake up near the end of the first wake-up time interval; and Means for scheduling a second device to wake up at a beginning of the second wake time interval.
22. The apparatus of claim 19, further comprising: Means for determining a wake-up time interval for each of the plurality of operations, each wake-up time interval comprising a start time and an increment interval based on one or more of an application type, a configured time interval, or an operation interval configured by a server.
23. A computer readable medium storing computer executable code, the computer executable code comprising code for: receiving a wake-up time interval for each of each of the one or more operations in the plurality of applications, wherein each wake-up time interval comprises a preferred wake-up time interval; forming a first wake-up time interval, the first wake-up time interval comprising overlapping wake-up time intervals of the plurality of applications or the plurality of operations; scheduling device wake-up during at least a subinterval of the first wake-up time interval, the subinterval comprising an overlap of at least two preferred wake-up time intervals; and performing said device wake-up during said subinterval, in, When corresponding preferred wake-up time intervals of a portion of the plurality of applications are not included in the sub-interval, the portion of applications are also allowed to perform their operations during the sub-interval.
