Energy planning profile for saving electricity in user equipment (UE) devices

Abstract

Procedure, comprehensive: by means of a user equipment device (UE) (106), Exchanging communications (1408) with a base station (102, 604) to determine one or more power planning profiles, wherein the communications include a proposal from the UE to the base station for a power planning profile that specifies a constraint of Ko and K2 values, wherein K0 defines a number of slots between a slot planned for a physical downstream control channel, PDCCH, and a slot planned for a physical shared downstream channel, PDSCH, and wherein K2 defines a number of slots between a slot planned for the PDCCH and a slot planned for a physical shared upstream channel, PUSCH; Receiving a slot configuration plan based on the energy planning profile proposed by the UE; and Performing communication (1410) with the base station based on the energy planning profile proposed by the UE.

Description

AREA

[0001] The present application relates to wireless devices and in particular to devices, systems and methods for a wireless device for communicating a planning profile, such as an energy planning profile, for saving electricity in a network. DESCRIPTION OF RELATED TECHNOLOGY

[0002] The use of wireless communication systems is increasing rapidly. In recent years, wireless devices such as smartphones and tablet computers have become increasingly complex. In addition to telephony, many mobile devices now provide access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of running complex applications that utilize these functions.

[0003] For the majority of wireless network operators worldwide, Long Term Evolution (LTE) has become the technology of choice for providing their customers with mobile broadband data and high-speed internet access. LTE defines a set of physical downlink (DL) channels, categorized as transport or control channels, to carry information blocks received from the medium access control (MAC) layer or higher layers. LTE also defines a number of uplink (UL) channels in the physical layer.

[0004] For example, LTE defines a Physical Downlink Shared Channel (PDSCH) as a DL transport channel. The PDSCH is the primary data transmission channel, allocated to users on a dynamic and opportunistic basis. The PDSCH carries data in transport blocks (TB) corresponding to a MAC protocol data unit (PDU), which are forwarded from the MAC layer to the physical (PHY) layer once per transmission time interval (TTI). The PDSCH is also used to transmit broadcast information such as system information blocks (SIBs) and paging messages.

[0005] As another example, LTE defines a Physical Downlink Control Channel (PDCCH) as a DL control channel that carries the resource allocation for UEs contained in a Downlink Control Information (DCD) message. Multiple PDCCHs can be transmitted in the same subframe using Control Channel Elements (CCEs), each of which is a set of nine sets of four resource elements known as Resource Element Groups (REGs). The PDCCH uses quadrature phase shift keying (QPSK) modulation, with each REG corresponding to four QPSK symbols. Furthermore, depending on channel conditions, 1, 2, 4, or 8 CCEs can be used for a UE to ensure sufficient reliability.

[0006] Additionally, LTE defines a Physical Uplink Shared Channel (PUSCH) as an uplink channel shared by all user equipment (UE) in a cell to transmit user data to the network. Scheduling for all UEs is controlled by the LTE base station (enhanced Node B or eNB). The eNB uses the uplink scheduling authorization (DCI format 0) to inform the UE about the allocation of resource blocks (RB) and the modulation and encoding scheme to use. PUSCH typically supports QPSK and quadrature amplitude modulation (QAM). In addition to the user data, the PUSCH also carries all control information necessary to decode the information, such as transport format indicators and multiple-input multiple-output (MIMO) parameters.Control data is multiplexed with information data before the digital Fourier transform (DFT) propagates.

[0007] A proposed new telecommunications standard, exceeding current IMT (International Mobile Telecommunications Advanced) standards, is called fifth-generation mobile networks or fifth-generation wireless systems, or 5G for short (also known as 5G NR for 5G New Radio, or simply NR). 5G NR proposes higher capacity for a higher density of mobile broadband users and also supports device-to-device, highly reliable, and massively multi-machine communication, as well as lower latency and reduced battery consumption than current LTE standards. Furthermore, the 5G NR standard can enable less restrictive UE planning compared to current LTE standards. Consequently, ongoing 5G NR developments are focused on leveraging the benefits of less restrictive UE planning to further utilize power-saving opportunities.

[0008] Document WO 2017 / 014912 A1 discloses a time-division multiplex duplex (TDD) subframe structure that supports both single and multiple interlaced operating modes. SUMMARY

[0009] The invention is defined in the independent claims. Advantageous embodiments are defined in the dependent claims. Embodiments relate to a method, a device, and a storage medium for planning a user equipment device (UE) based on an energy planning profile.

[0010] In some embodiments, a user equipment device may be configured to perform a method for restricting user equipment (UE) communication behavior. The method may involve an exchange of communication between the UE and a base station to determine one or more scheduling profiles, such as one or more power scheduling profiles. In some embodiments, the communication with the base station to determine the one or more power scheduling profiles may involve an exchange of one or more radio resource control (RRC) signal messages. In some embodiments, the one or more power scheduling profiles must not conflict with each other. In some embodiments, a power scheduling profile may specify one or more parameters associated with the UE communication behavior, such as...One or more restrictions on the UE communication behavior and / or slot planning of the UE communication. Additionally, the procedure may include the UE receiving a slot configuration plan from the base station. The slot configuration plan may be based on at least one energy planning profile from one or more energy planning profiles. Furthermore, the procedure may include the UE communicating with the base station based on the at least one energy planning profile.

[0011] In some embodiments, one or more power scheduling profiles may include a profile that prevents the base station from scheduling the transmission of an acknowledgment of data received on the PDCCH to a slot immediately preceding a slot scheduled for PDCCH monitoring. In some embodiments, one or more power scheduling profiles may include a profile that prevents the base station from scheduling the transmission on the PUSCH to a slot immediately preceding a slot scheduled for PDCCH monitoring. In some embodiments, one or more power scheduling profiles may include a profile that prevents the base station from scheduling the transmission of an acknowledgment (ACK) from a PDCCH and a receive on the PDSCH to a slot across slots immediately preceding a slot scheduled for PDCCH monitoring.

[0012] The techniques described herein can be implemented and / or used in a number of different types of devices, including, but not limited to, mobile phones, tablet computers, body-worn computing devices, portable media players and any other computing devices.

[0013] This summary is intended to provide a brief overview of some of the items described in this document. Accordingly, it should be noted that the features described above are merely examples and should not be considered in any way limiting the scope or spirit of the item described herein. Further features, aspects, and advantages of the item described herein will become apparent from the following detailed description, figures, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] A better understanding of the present subject matter can be achieved by considering the following detailed description of various embodiments in conjunction with the following drawings, in which: Fig. 1 An example system for wireless communication according to some embodiments is illustrated; Fig. 2 illustrates a base station (BS) connected to a user equipment device (UE device) according to some embodiments; Fig. 3. An example block diagram of a UE according to some embodiments is illustrated; Fig. 4 illustrates an example block diagram of a BS according to some embodiments; Fig. 5 illustrates an example block diagram of a mobile communication switching logic according to some embodiments; Fig. Figure 6A illustrates an example of connections between an EPC network, an LTE base station (eNB) and a 5G NR base station (gNB); Fig. 6B illustrates an example of a protocol stack for an eNB and a gNB; Fig. Figure 7A illustrates an example of a 5G network architecture that incorporates both 3GPP (e.g., Mobile) as well as non-3GPP (e.g., non-mobile) access to the 5G CN according to some embodiments; Fig. Figure 7B illustrates an example of a 5G network architecture that includes both dual-3GPP (e.g., LTE and 5G-NR) access and non-3GPP access to the 5G CN according to some embodiments; Fig. Figure 8 illustrates an example of a baseband processor architecture for a UE according to some embodiments. Fig. Figure 9A illustrates an example of a PDCCH monitoring interval; Fig. Figure 9B illustrates an example of the power consumption of a UE for multiple PDCCH monitoring slots; The Fig. 10A to 10C illustrate an example of the power consumption of a UE for multiple transmissions during a PDCCH monitoring; Fig. 10D illustrates an example of the power consumption of a UE for multiple transmissions during a PDCCH monitoring according to some embodiments; The Fig. 11A to 11C illustrate an example of the power consumption of a UE for multiple reception processes during a PDCCH monitoring; Fig. 11D illustrates an example of the power consumption of a UE for multiple reception processes during a PDCCH monitoring according to some embodiments; The Fig. 12A to 12C illustrate an example of the power consumption of a UE for a transmission followed by a reception process during a PDCCH monitoring; Fig. 12D illustrates an example of the power consumption of a UE for a transmission followed by a reception process during PDCCH monitoring according to some embodiments; The Fig. 13A to 13C illustrate an example of the power consumption of a UE for a receive operation followed by a transmit, during a PDCCH monitoring; Fig. 13D illustrates an example of the power consumption of a UE for a receive operation followed by a transmit during PDCCH monitoring according to some embodiments; Fig. 14 A block diagram of an example of a process for determining a planning profile for a UE according to some embodiments illustrates; Fig. 15 example profiles and corresponding UE behaviors according to some embodiments are illustrated; Fig. 16 example parameter sets for different profiles according to some embodiments are illustrated; Fig. 17 illustrates an example of delayed confirmation with subsequent PDCCH monitoring according to some embodiments; Fig. 18 illustrates an example of a delayed PUSCH with subsequent PDCCH monitoring according to some embodiments; Fig. 19 illustrates an example of delayed cross-slot planning with subsequent PDCCH monitoring according to some embodiments; Fig. 20 illustrates an example of independent slot planning with subsequent PDCCH monitoring according to some embodiments.

[0015] Although the features described herein may be subject to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and described in detail herein. It should be understood, however, that the drawings and the detailed description thereto are not intended to be limited to the specific disclosed form, but rather that the invention is intended to cover all modifications, equivalents, and alternatives that fall within the spirit and scope of the subject matter as defined by the attached claims. DETAILED DESCRIPTION Terms

[0016] The following is a glossary of terms used in this revelation: Storage medium – any of the various types of non-volatile memory devices or data storage devices. The term "storage medium" is intended to include installation media, e.g., a CD-ROM, floppy disks, or a tape device; computer system memory or random-access memory, such as DRAM, DDR-RAM, SRAM, EDO-RAM, Rambus-RAM, etc.; non-volatile memory, such as flash memory; magnetic storage media, e.g., a hard disk or optical storage; registers or other similar types of memory elements, etc. The storage medium may include other types of non-volatile memory as well as combinations thereof.Furthermore, the storage medium can be located in a first computer system where the programs are executed, or it can be located in a second, different computer system connected to the first computer system via a network, such as the internet. In the latter case, the second computer system can provide the first computer with program instructions for execution. The term "storage medium" can include two or more storage media that may be located in different places, for example, in different computer systems connected via a network. Program instructions (e.g., formatted as computer programs) can be stored in the storage medium and executed by one or more processors. Carrier medium - a storage medium as described above, as well as a physical transmission medium, such as a bus, a network and / or another physical transmission medium, that transmits signals, such as electrical, electromagnetic or digital signals. Programmable hardware element – ​​encompasses various hardware devices comprising multiple programmable functional blocks connected via a programmable interface. Examples include FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field Programmable Object Arrays), and CPLDs (Complex PLDs). The programmable functional blocks can range from fine-grained (combinatorial logic or lookup tables) to coarse-grained (arithmetic logic units or processor cores). A programmable hardware element can also be referred to as "reconfigurable logic." Computer system – any of several different types of computing or processing systems, including a personal computer system (PC), mainframe system, workstation, network appliance, internet appliance, personal digital assistant (PDA), television system, grid computing system, or any other device or combination of devices. In general, the term "computer system" can be broadly defined to include any device (or combination of devices) with at least one processor that executes instructions from a storage medium. User equipment (or "UE device") – any of various types of computer system devices that are mobile or portable and capable of wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhone™, Android™-based phones), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), laptops, body-worn devices (e.g., smartwatches, smartglasses), PDAs, portable internet devices, music players, data storage devices, or other handheld devices, etc. In general, the term "UE" or "UE device" can be broadly defined to encompass any electronic, computing, and / or telecommunications device (or combination of devices) that can be easily transported by a user and is capable of wireless communication. Base station - The term 'base station' encompasses the full breadth of its usual meaning and includes at least one wireless communication station installed in a fixed location and used as part of a wireless telephone system or radio system for communication. Processing element – ​​refers to various elements or combinations of elements capable of performing a function in a device, such as user equipment or mobile network equipment. Processing elements can include, for example: processors and associated memory, sections or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as an application-specific integrated circuit (ASIC), programmable hardware elements such as a field-programmable gate array (FPGA), and any of the many combinations of the foregoing. Channel – a medium used to transmit information from a sender to a receiver. It should be noted that the characteristics of the term "channel" can vary according to different wireless protocols, and the term "channel" as used here should therefore be understood as being used in a manner consistent with the standard of the type of device to which the term refers. With some standards, channel widths can be variable (e.g., depending on the capability of the device, band conditions, etc.). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. In contrast, WLAN channels can be 22 MHz wide, while Bluetooth channels can be 1 MHz wide. Other protocols and standards may have different channel definitions. Furthermore, some standards may define and use multiple types of channels, e.g.,different channels for uplink or downlink and / or different channels for different uses such as data, control information, etc. Band - The term 'band' encompasses the full breadth of its usual meaning and includes at least one section of a spectrum (e.g., a radio frequency spectrum) in which channels are used or reserved for the same purpose. Automatic – refers to an action or operation (e.g., software executed by the computer system) performed by a computer system or device (e.g., switching logic, programmable hardware elements, ASICs, etc.) without user input that directly specifies or executes the action or operation. Thus, the term "automatic" contrasts with an operation performed or specified manually by the user, where the user provides input to directly execute the operation. An automatic procedure may be initiated by user input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," with the user specifying each action to be carried out.For example, a user completing an electronic form by selecting each field and providing input that specifies information (e.g., by typing information, selecting checkboxes, choosing a radio button, etc.) is manually filling out the form, even though the computer system needs to update the form in response to the user's actions. The form can also be automatically filled out by the computer system, where the computer system (e.g., software running on the computer system) analyzes the form's fields and completes the form entirely without any user input specifying the answers to the fields. As mentioned above, the user can request automatic form filling but is not involved in the actual form completion process (e.g., the user does not manually specify answers for fields; instead, they are filled in automatically).The following description provides various examples of operations that are performed automatically in response to actions taken by the user. Approximately refers to a value that is almost correct or exact. For example, "approximately" may refer to a value that is within 1 to 10 percent of the exact (or desired) value. However, it should be noted that the actual threshold (or tolerance) may be application-dependent. For example, in some embodiments, "approximately" may mean within 0.1% of a specified or target value, while in other embodiments, the threshold may be, for example, 2%, 3%, 5%, and so on, as desired or required by the specific application. Simultaneous execution refers to parallel processing, where tasks, processes, or programs are executed in a manner that overlaps at least partially. For example, simultaneity can be implemented using "strong" or strict parallelism, where tasks are executed (at least partially) in parallel on their respective computing elements, or using "weak parallelism," where tasks are executed in an interlocking manner, such as through time-division multiplexing of execution strands.

[0017] Various components may be described as "configured to" perform one or more tasks. In such contexts, "configured to" is a broad term that generally means "possessing a structure that" performs the task or tasks during operation. Thus, the component may be configured to perform the task even if it is not currently performing that task (e.g., a set of electrical conductors may be configured to electrically connect one module to another, even if the two modules are not connected). In some contexts, "configured to" may be a broad term referring to a structure that generally means "possessing switching logic that" performs the task or tasks during operation.Therefore, the component can be configured to perform the task even if it is not currently powered on. Generally, the switching logic that forms the structure accordingly "configured to" can include hardware circuits.

[0018] Various components may, for convenience, be described in the description as performing a task or tasks. Such descriptions should be interpreted as including the phrase "configured to." The citation of a component that is configured to perform one or more tasks does not expressly imply reliance on an interpretation under 35 U.S.C. § 112(f) for that component. Figures 1 and 2 - Communication system

[0019] Fig. Figure 1 illustrates a simplified example system for wireless communication according to some embodiments. It should be noted that the system is based on Fig. 1 represents only one example of a possible system and that features of this revelation can be implemented in any of the different systems as desired.

[0020] As shown, the example wireless communication system includes a base station 102A, which communicates via a transmission medium with one or more user devices 106A, 106B, etc., up to 106N. Each of the user devices can be referred to here as "user equipment" (UE). Thus, the user devices 106 are referred to as UEs or UE devices.

[0021] The base station (BS) 102A can be a base transceiver station (BTS) or a cell site (a “mobile base station”) and can include hardware that enables wireless communication with the UEs 106A to 106N.

[0022] The communication area (or coverage area) of the base station can be referred to as a "cell." The 102A base station and the 106 units can be configured to communicate over the transmission medium using one of several types of radio access technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (for example, 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. It should be noted that when implemented in the context of LTE, the 102A base station can alternatively be referred to as an "eNodeB" or "eNB." It should be noted that if the base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as “gNodeB” or “gNB”.

[0023] As shown, the base station 102A can also be equipped to communicate with a network 100 (e.g., with a mobile service provider's core network, a telecommunications network such as a public switched telephone network (PSTN), and / or the internet, among various possibilities). Thus, the base station 102A can facilitate or enable communication between user devices and / or between user devices and the network 100. In particular, the mobile base station 102A can equip the UEs 106 with various telecommunications capabilities, such as voice, SMS, and / or data services.

[0024] The Base Station 102A and other similar Base Stations (such as Base Stations 102B...102N) operating according to the same or a different mobile communication standard can thus be provided as a network of cells capable of providing a continuous or almost continuous overlapping service for UEs 106A to N and similar devices over a wide geographical area using one or more mobile communication standards.

[0025] Although the base station 102A can function as a "control cell" for the UEs 106A to N, as described in Fig. As illustrated in Figure 1, each UE 106 can thus also be capable of receiving signals from (and possibly within a communication range of) one or more other cells (which may be provided by base stations 102B to N and / or other base stations), which may be referred to as "neighbor cells." Such cells may also be capable of facilitating or enabling communication between user devices and / or between user devices and the Network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells providing any of several other granularities of a service area size. For example, the base stations 102A to B, which are located in Fig. The examples shown in Figure 1 are macrocells, while the base station 102N can be a microcell. Other configurations are also possible.

[0026] In some embodiments, the Base Station 102A can be a next-generation base station, such as a 5G New Radio (5G NR) base station or a "gNB". In some embodiments, a gNB can be connected to an older evolved packet core (EPC) network and / or to an NR core (NRC) network. Additionally, a gNB cell can include one or more transition and reception points (TRPs). Furthermore, a UE capable of operating according to 5G NR can be connected to one or more TRPs within one or more gNBs.

[0027] Note that a UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using a wireless network (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (e.g., WCDMA or TD-SCDMA air interfaces assigned), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). The UE 106 can also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g. GPS or GLONASS), one or more mobile television broadcasting standards (e.g. ATSC-M / H or DVB-H), and / or any other wireless communication protocol, if desired.Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0028] Fig. Figure 2 illustrates user equipment 106 (e.g., one of the devices 106A to 106N) communicating with a base station 102 according to some embodiments. The user equipment 106 can be a device capable of wireless communication, such as a mobile phone, a handheld device, a computer, or a tablet, or virtually any type of wireless device.

[0029] The UE 106 can include a processor configured to execute program instructions stored in memory. The UE 106 can perform any of the procedure execution modes described herein by executing such stored instructions.

[0030] Alternatively or additionally, UE 106 may include a programmable hardware element, such as a field-programmable gate array (FPGA), configured to perform any of the procedure implementations described herein or any section of any of the procedure implementations described herein.

[0031] The UE 106 can include one or more antennas for communication using one or more wireless communication protocols or technologies. In some embodiments, the UE 106 can be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD) or LTE using a single shared radio device and / or GSM or LTE using the same single shared radio device. The shared radio device can couple to a single antenna or to multiple antennas (e.g., for MIMO) to perform wireless communications. Generally, a radio device can include any combination of a baseband processor, analog RF signal processing switching logic (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing switching logic (e.g., for digital modulation and other digital processing).Similarly, the radio device can implement one or more receive and transmit chains using the aforementioned hardware. For example, the UE 106 can share one or more parts of a receive and / or transmit chain for multiple wireless communication technologies, such as those discussed above.

[0032] In some embodiments, the UE 106 can include separate transmit and / or receive chains (e.g., including separate antennas and other digital radio components) for each wireless communication protocol with which it is configured to communicate. Alternatively, the UE 106 can include one or more radio devices shared by multiple wireless communication protocols and one or more radio devices used exclusively by a single wireless communication protocol. For example, the UE 106 could include one shared radio device for communicating using either LTE or 5G NR (or LTE or 1xRTT or LTE or GSM) and separate radio devices for communicating using Wi-Fi and Bluetooth, respectively. Other configurations are also possible. Figure 3 - Block diagram of a teaching unit

[0033] Fig. Figure 3 illustrates a simplified example block diagram of a communication device 106 according to some embodiments. It is noted that the block diagram of the communication device is Fig. Figure 3 represents only one specific example of a possible communication device. According to embodiments, the communication device 106 can be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, and / or a combination of devices, among other devices. As shown, the communication device 106 can include a set of components 300 configured to perform core functions. For example, this set of components can be implemented as a system-on-a-chip (SOC) that may include sections for different purposes. Alternatively, this set of components 300 can be implemented as separate components or groups of components for the different purposes.The set of components 300 can be coupled (e.g. communicatively; directly or indirectly) to various other circuits of the communication device 106.

[0034] For example, the communication device 106 can include various types of memory (e.g., including NAND flash 310), an input / output interface, such as a connector interface 320 (e.g., for connecting to a computer system; docking; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), the display 360, which can be integrated into the communication device 106 or external to it, and cellular communication switching logic 330, such as for 5G NR, LTE, GSM, etc., and switching logic for short- to medium-range wireless communication 329 (e.g., Bluetooth™ and WLAN switching logic). In some embodiments, the communication device 106 can include wired communication switching logic (not shown), such as a network interface card, e.g., for Ethernet.

[0035] The cellular communication switching logic 330 can be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 335 and 336, as shown. The short- to medium-range wireless communication switching logic 329 can also be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 337 and 338, as shown. Alternatively, the short- to medium-range wireless communication switching logic 329 can be coupled (e.g., communicatively; directly or indirectly) to antennas 335 and 336 in addition to or instead of coupling (e.g., communicatively; directly or indirectly) to antennas 337 and 338.The switching logic for short to medium range wireless communication 329 and / or the cellular communication switching logic 330 can include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration.

[0036] In some embodiments, as further described below, the cellular communication switching logic 330 can include dedicated receive chains (including and / or coupled with, for example, communicatively, directly or indirectly dedicated processors and / or radio devices) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). Additionally, in some embodiments, the cellular communication switching logic 330 can include a single transmit chain that can be switched between radio devices assigned to specific RATs. For example, a first radio device can be assigned to a first RAT, e.g., LTE, and communicate with a dedicated receive chain and a shared transmit chain with an additional radio device, e.g., a second radio device assigned to a second RAT, e.g.,5G NR, can be assigned and can communicate with a dedicated receive chain and the shared transmit chain.

[0037] The communication device 106 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include any of various elements, such as the 360° display (which may be a touchscreen display), a keyboard (which may be a separate keyboard or implemented as part of a touchscreen display), a mouse, a microphone and / or speakers, one or more cameras, one or more keys or buttons, and / or any of various other elements capable of providing information to a user and / or receiving or interpreting user input.

[0038] The communication device 106 may further include one or more smart cards 345 which include SIM functionality (Subscriber Identity Module functionality), such as one or more UICC cards (Universal Integrated Circuit Cards) 345.

[0039] As shown, the SOC 300 can include one or more processors 302, which can execute program instructions for the communication device 106, and a display switching logic 304, which can perform graphics processing and provide display signals for the display 360. The one or more processors 302 can also be coupled with a memory management unit (MMU) 340, which can be configured to receive addresses from the one or more processor(s) 302 and translate these addresses into memory locations (e.g., in a memory 306, a read-only memory (ROM) 350, a NAND flash memory 310), and / or coupled with other circuits or devices, such as the display switching logic 304, the short-range wireless communication switching logic 329, the cellular communication switching logic 330, a connector interface 320, and / or the display 360.The MMU 340 can be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 can be enclosed as a section of one or more 302 processors.

[0040] As stated above, the communication device 106 can be configured to communicate using wireless and / or wired communication switching logic. The communication device 106 can be configured to perform a procedure that includes exchanging communication with a base station to determine one or more power planning profiles. In some embodiments, the communication with the base station to determine the one or more power planning profiles can include an exchange of one or more radio resource control (RRC) signal messages. In some embodiments, the one or more power planning profiles must not conflict with each other. In some embodiments, a power planning profile can specify one or more parameters that are associated with the communication behavior of the communication device 106, e.g.,B. one or more restrictions on the communication behavior of the communication device 106 and / or the slot planning of the communication of the communication device 106. Additionally, the method may include the communication device 106 receiving a slot configuration plan from the base station. The slot configuration plan may be based on at least one power planning profile from one or more power planning profiles. Furthermore, the method may include the communication device 106 communicating with the base station based on the at least one power planning profile.

[0041] As described herein, the communication device 106 can include hardware and software components for implementing the aforementioned features for a communication device 106 for communicating an energy planning profile for power savings to a network. The processor 302 of the communication device 106 can be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a storage medium (e.g., a non-volatile, computer-readable storage medium). Alternatively (or additionally), the processor 302 can be configured as a programmable hardware element, such as an FPGA (field-programmable gate array) or an ASIC (application-specific integrated circuit).Alternatively (or additionally), the processor 302 of the communication device 106, in conjunction with one or more of the other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, can be configured to implement some or all of the features described herein.

[0042] Additionally, as described herein, the Processor 302 can include one or more processing elements. Thus, the Processor 302 can include one or more integrated circuits (ICs) configured to perform the functions of the Processor 302. Furthermore, each integrated circuit can include switching logic (e.g., a first switching logic, second switching logic, etc.) configured to perform the functions of the one or more Processors 302.

[0043] Furthermore, as described herein, the cellular communication switching logic 330 and the short-range wireless switching logic 329 can each include one or more processing elements. In other words, one or more processing elements can be included in the cellular communication switching logic 330, and similarly, one or more processing elements can be included in the short-range wireless switching logic 329. Thus, the cellular communication switching logic 330 can include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication switching logic 330.

[0044] Additionally, each integrated circuit can include switching logic (e.g., a first switching logic, second switching logic, etc.) configured to perform the functions of the cellular communication switching logic 330. Similarly, the short-range wireless communication switching logic 329 can include one or more ICs configured to perform the functions of the short-range wireless communication switching logic 329. Additionally, each integrated circuit can include switching logic (e.g., a first switching logic, second switching logic, etc.) configured to perform the functions of the short-range wireless communication switching logic 329. Figure 4 - Block diagram of a base station

[0045] Fig. Figure 4 illustrates an example block diagram of a base station 102 according to some embodiments. It is noted that the base station is Fig. Figure 4 is only one example of a possible base station. As shown, the base station 102 can include one or more processors 404 that can execute program instructions for the base station 102. The one or more processors 404 can also be coupled to a memory management unit (MMU) 440, which can be configured to receive addresses from the one or more processors 404 and translate these addresses into locations in a memory (e.g., in a memory 460 and a read-only memory (ROM) 450), or to other circuits or devices.

[0046] The base station 102 can include at least one network port 470. The network port 470 can be configured to establish a connection to a telephone network and to provide access to the telephone network to a plurality of devices, such as the UE devices 106, as described above in the Fig. 1 and Fig. 2 described.

[0047] Network port 470 (or an additional network port) can be additionally or alternatively configured to connect to a mobile network, such as a mobile network operator's core network. The core network can provide mobility-related services and / or other services to multiple devices, such as the UE devices 106. In some cases, network port 470 can connect to a telephone network via the core network, and / or the core network can provide a telephone network (e.g., between other UE devices served by the mobile network operator).

[0048] In some embodiments, the base station 102 can be a next-generation base station, such as a 5G New Radio (5G NR) base station or a "gNB". In such embodiments, the base station 102 can be connected to an older developed packet core (EPC) network and / or to a non-reactive core (NRC) network. Additionally, the base station 102 can be considered a 5G NR cell and can include one or more transition and receive points (TRPs). Furthermore, a user entity (UE) capable of operating according to 5G NR can be connected to one or more TRPs within one or more gNBs.

[0049] The base station 102 can include at least one antenna 434 and possibly several antennas. The at least one antenna 434 can be configured to operate as a wireless transceiver and can further be configured to communicate with the UE devices 106 via a radio device 430. The antenna 434 communicates with the radio device 430 via a communication chain 432. The communication chain 432 can be a receive chain, a transmit chain, or both. The radio device 430 can be configured to communicate using various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0050] The Base Station 102 can be configured to communicate wirelessly using multiple wireless communication standards. In some cases, the Base Station 102 may include multiple radio devices, enabling it to communicate using several wireless communication technologies. For example, the Base Station 102 may include an LTE radio device for LTE communication, as well as a 5G NR radio device for 5G NR communication. In such a case, the Base Station 102 can operate as both an LTE base station and a 5G NR base station.Alternatively, the base station 102 can include a multi-mode radio device capable of communicating according to any of several wireless communication technologies (for example, 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0051] As described in more detail below, the BS 102 may include hardware and software components for implementing or supporting the implementation of features described herein. The BS 102 processor 404 may be configured to implement or support some or all of the procedures described herein, for example, by executing program instructions stored on a memory medium (such as non-volatile, machine-readable memory). Alternatively, the BS 102 processor may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), an ASIC (Application Specific Integrated Circuit), or a combination thereof.Alternatively (or additionally), the BS 102 processor 404 can be configured, in conjunction with one or more of the other components 430, 432, 434, 440, 450, 460, 470, to implement or support the implementation of some or all of the features described herein.

[0052] Additionally, the one or more 404 processors, as described herein, can be composed of one or more processing elements. In other words, one or more processing elements can be included within the one or more 404 processors. Thus, the one or more 404 processors can include one or more integrated circuits (ICs) configured to perform the functions of the one or more 404 processors. Furthermore, each integrated circuit can include switching logic (e.g., first switching logic, second switching logic, etc.) configured to perform the functions of the one or more 404 processors.

[0053] Furthermore, the radio device 430, as described herein, can be composed of one or more processing elements. In other words, one or more processing elements can be included in the radio device 430. Thus, the radio device 430 can include one or more integrated circuits (ICs) configured to perform the functions of the radio device 430. Additionally, each integrated circuit can include switching logic (e.g., a first switching logic, second switching logic, etc.) configured to perform the functions of the radio device 430. Figure 5: Block diagram of a mobile communication switching logic

[0054] Fig. Figure 5 illustrates a simplified example block diagram of a mobile communication switching logic according to some embodiments. It is noted that the block diagram of the mobile communication switching logic of Fig. Figure 5 represents only one specific example of a possible cellular communication switching logic. According to embodiments, the cellular communication switching logic 330 can be enclosed in a communication device, such as the communication device 106 described above. As stated above, the communication device 106 can be a user equipment device (UE device), a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, and / or a combination of devices, among other devices.

[0055] The mobile communication switching logic 330 can be connected (e.g. communicatively; directly or indirectly) to one or more antennas, such as the antennas 335a to b and 336, as shown (in Fig. 3) be coupled. In some embodiments, the mobile communication switching logic 330 may include dedicated receive chains (including and / or coupled with, e.g., communicatively; directly or indirectly dedicated processors and / or radio devices) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as in Fig. Figure 5 shows that the mobile communications switching logic 330 includes a modem 510 and a modem 520. The modem 510 can be configured for communication according to a first RAT, such as LTE or LTE-A, and the modem 520 can be configured for communication according to a second RAT, such as 5G NR.

[0056] As shown, the modem 510 can include one or more processors 512 and a memory 516 in communication with the processors 512. The modem 510 can communicate with a radio frequency (RF) front end 530. The RF front end 530 can include switching logic for transmitting and receiving radio signals. For example, the RF front end 530 can include receive switching logic (RX) 532 and transmit switching logic (TX) 534. In some embodiments, the receive switching logic 532 can communicate with the downlink (DL) front end 550, which can include switching logic for receiving radio signals via the antenna 335a.

[0057] Similarly, the modem 520 can include one or more processors 522 and a memory 526 in communication with the processors 522. The modem 520 can communicate with an RF frontend 540. The RF frontend 540 can include switching logic for transmitting and receiving radio signals. For example, the RF frontend 540 can include receive switching logic 542 and transmit switching logic 544. In some embodiments, the receive switching logic 542 can communicate with the DL frontend 560, which can include switching logic for receiving radio signals via the antenna 335b.

[0058] In some embodiments, a switch 570 can couple the transmit switching logic 534 with an uplink (UL) front end 572. Additionally, the switch 570 can couple the transmit switching logic 544 with the UL front end 572. The UL front end 572 can include switching logic for transmitting radio signals via the antenna 336. Thus, when the cellular communication switching logic 330 receives instructions to transmit according to the first RAT (e.g., as supported via the modem 510), the switch 570 can be switched to a first state that allows the modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain that includes the transmit switching logic 534 and the UL front end 572). Similarly, if the mobile communications switching logic 330 receives instructions to send according to the second RAT (e.g.,(as supported via modem 520), the switch 570 can be switched to a second state which allows the modem 520 to send signals according to the second RAT (e.g. via a transmit chain that includes the transmit switching logic 544 and the UL front end 572).

[0059] In some embodiments, the cellular communication switching logic 330 can be configured to perform a procedure that includes exchanging communications with a base station to determine one or more power planning profiles. In some embodiments, the communication with the base station to determine the one or more power planning profiles can include exchanging one or more radio resource control (RRC) signal messages. In some embodiments, the one or more power planning profiles must not conflict with each other. In some embodiments, a power planning profile can specify one or more parameters associated with the UE communication behavior, such as one or more restrictions on the UE communication behavior and / or the slot scheduling of the UE communication.Additionally, the procedure can include receiving a slot configuration plan from the base station. The slot configuration plan can be based on at least one energy planning profile from one or more energy planning profiles. Furthermore, the procedure can include communicating with the base station based on the at least one energy planning profile.

[0060] As described herein, the Modem 510 can include hardware and software components for implementing the features described above or for time-division multiplexing UL data for NSA-NR operations, as well as the various other techniques described herein. The Processors 512 can be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a storage medium (such as a non-volatile, computer-readable storage medium). Alternatively (or additionally), the Processor 512 can be configured as a programmable hardware element, such as an FPGA (field-programmable gate array) or an ASIC (application-specific integrated circuit).Alternatively (or additionally), the 512 processor can be configured in conjunction with one or more of the other components 530, 532, 534, 550, 570, 572, 335 and 336 to implement some or all of the features described herein.

[0061] Additionally, as described herein, the 512 processors can include one or more processing elements. Thus, the 512 processors can include one or more integrated circuits (ICs) configured to perform the functions of the 512 processors. Furthermore, each integrated circuit can include switching logic (e.g., first switching logic, second switching logic, etc.) configured to perform the functions of the 512 processors.

[0062] As described herein, the Modem 520 can include hardware and software components for implementing the aforementioned features for communicating a power-saving energy planning profile to a network, as well as the various other techniques described herein. The Processors 522 can be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a memory medium (such as a non-volatile, computer-readable storage medium). Alternatively (or additionally), the Processor 522 can be designed as a programmable hardware element, such as an FPGA (field-programmable gate array) or an ASIC (application-specific integrated circuit).Alternatively (or additionally), the 522 processor can be configured in conjunction with one or more of the other components 540, 542, 544, 550, 570, 572, 335 and 336 to implement some or all of the features described herein.

[0063] Additionally, as described herein, the 522 processors can include one or more processing elements. Thus, the 522 processors can include one or more integrated circuits (ICs) configured to perform the functions of the 522 processors. Furthermore, each integrated circuit can include switching logic (e.g., a first switching logic, second switching logic, etc.) configured to perform the functions of the 522 processor. 5G NR architecture with LTE

[0064] In some implementations, fifth-generation wireless communication (5G) is initially deployed concurrently with current wireless communication standards (e.g., LTE). For example, dual connectivity between LTE and 5G New Radio (5G NR or NR) was defined as part of the initial NR deployment. Thus, as in the Fig. Figures 6A to B illustrate how an Developed Packet Core (EPC) network 600 can continue to communicate with existing LTE base stations (e.g., an eNB 602). Additionally, the eNB 602 can communicate with a 5G NR base station (e.g., gNB 604) and transfer data between the EPC network 600 and the gNB 604. Thus, the EPC network 600 can be used (or reused), and the gNB 604 can serve as additional capacity for User Entities (UEs), for example, to provide increased downlink throughput. In other words, LTE can be used for control plane signaling, and NR can be used for user plane signaling. Therefore, LTE can be used to establish connections to the network, and NR can be used for data services.

[0065] Fig. Figure 6B illustrates a proposed protocol stack for the eNB 602 and the gNB 604. As shown, the eNB 602 can include a medium access control (MAC) layer 632, which interacts with radio link control (RLC) layers 622a to b. RLC layer 622a can also interact with a packet data convergence protocol (PDCP) layer 612a, and RLC layer 622b can interact with a PDCP layer 612b. Similar to dual connectivity according to LTE-Advanced Release 12, PDCP layer 612a can interact with the EPC network 600 via a "Master Cell Group" (MCG) carrier, while PDCP layer 612b can interact with the EPC network 600 via a split carrier.

[0066] Additionally, as shown, the gNB 604 can include a MAC layer 634 that interacts with RLC layers 624a to b. RLC layer 624a can interact with the PDCP layer 612b of the eNB 602 via an X2 interface for information exchange and / or coordination (e.g., planning a UE) between the eNB 602 and the gNB 604. Furthermore, RLC layer 624b can interact with PDCP layer 614. Similar to the dual connectivity defined in LTE Advanced Release 12, PDCP layer 614 can interact with the EPC network 600 via a secondary cell group (SCG) carrier. Thus, the eNB 602 can be considered a master node (MeNB), while the gNB 604 can be considered a secondary node (SgNB). In some scenarios, it may be necessary for a UE to maintain a connection to both a MeNB and a SgNB.In such scenarios, the MeNB can be used to maintain a radio resource control (RRC) link to an EPC, while the SgNB can be used for capacity (e.g., additional downlink and / or uplink throughput). 5G core network architecture - collaboration with Wi-Fi

[0067] In some embodiments, the 5G core network (CN) can be accessed via (or through) a cellular connection / interface (e.g., via a 3GPP communication architecture / protocol) and a non-cellular connection / interface (e.g., a non-3GPP access architecture / protocol such as a Wi-Fi connection). Fig. Figure 7A illustrates an example of a 5G network architecture that includes both 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN according to some embodiments. As shown, a user equipment device (such as the UE 106) can access the 5G CN via both a radio access network (RAN, such as a gNB or the base station 604) and an access point, such as the AP 112. The AP 112 can include a connection to the Internet 700 as well as a connection to a network unit with a non-3GPP interworking function (N3IWF) 702. The N3IWF can include a connection to a core access and mobility management function (AMF) 704 of the 5G CN. The AMF 704 can include an instance of a 5G Mobility Management (5G MM) function that is assigned to the UE 106. Additionally, the RAN (e.g.,The gNB 604) can also have a connection to the AMF 704. Thus, the 5G-CN can support unified authentication over both connections and simultaneously allow simultaneous registration for access to the UE 106 via both the gNB 604 and the AP 112. As shown, the AMF 704 can include one or more functional units assigned to the 5G-CN (e.g., Network Slice Selection Function (NSSF) 720, Short Message Service Function (SMSF) 722, Application Function (AF) 724, Unified Data Management (UDM) 726, Policy Control Function (PCF) 728, and / or Authentication Server Function (AUSF) 730).It should be noted that these functional units can also be supported by a Session Management Function (SMF) 706a and an SMF 706b of the 5G-CN. The AMF 706 can be connected to (or communicate with) the SMF 706a. Furthermore, the gNB 604 can communicate with (or be connected to) a User Plane Function (UPF) 708a, which can also communicate with the SMF 706a. Similarly, the N3IWF 702 can communicate with a UPF 708b, which can also communicate with the SMF 706b. Both UPFs can communicate with the data network (e.g., a DN 710a and 710b) and / or the Internet 700 and an IMS core network 710.

[0068] Fig. Figure 7B illustrates an example of a 5G network architecture that includes both dual-3GPP (e.g., LTE and 5G-NR) access and non-3GPP access to the 5G CN according to some embodiments. As shown, a user equipment device (such as UE 106) can access the 5G CN via a radio access network (RAN, such as gNB or Base Station 604 or eNB or Base Station 602) or via an access point, such as AP 112. AP 112 can include a connection to the Internet 700 as well as a connection to the network unit with N3IWF 702. N3IWF can include a connection to the 5G CN's AMF 704. AMF 704 can include an instance of the 5G MM function associated with UE 106. Additionally, the RAN (e.g., the gNB 604) can also have a connection to the AMF 704.Thus, the 5G-CN can support unified authentication across both connections and enable simultaneous registration for UE 106 access via both the gNB 604 and the AP 112. Additionally, the 5G-CN can support dual registration of the UE in both a legacy network (e.g., LTE via the base station 602) and a 5G network (e.g., via the base station 604). As shown, the base station 602 can have connections to a Mobility Management Unit (MME) 742 and a Serving Gateway (SGW) 744. The MME 742 can have connections to both the SGW 744 and the AMF 704. Furthermore, the SGW 744 can have connections to both the SMF 706a and the UPF 708a. As shown, the AMF 704 can include one or more functional units assigned to the 5G-CN (e.g. NSSF 720, SMSF 722, AF 724, UDM 726, PCF 728 and / or AUSF 730).It should be noted that the UDM 726 can also include a Home Subscriber Server (HSS) function, and the PCF can also include a Policy and Charging Rules (PCRF) function. It should also be noted that these functional units can be supported by the 5G-CN's SMF 706a and SMF 706b. The AMF 706 can be connected to (or communicate with) the SMF 706a. Furthermore, the gNB 604 can communicate with (or be connected to) a UPF 708a, which can also communicate with the SMF 706a. Similarly, the N3IWF 702 can communicate with a UPF 708b, which can also communicate with the SMF 706b. Both UPFs can communicate with the data network (e.g., the DN 710a and 710b) and / or the Internet 700 and the IMS core network 710.

[0069] It should be noted that in various embodiments, one or more of the network units described above may be configured to perform procedures for planning a UE based on an energy planning profile that may specify one or more parameters associated with the UE communication behavior, e.g., one or more restrictions on the UE communication behavior and / or slot planning of the UE communication, as further described herein.

[0070] Fig. Figure 8 illustrates an example of a baseband processor architecture for a UE (such as the UE 106), according to some embodiments. The in Fig. The 800 baseband processor architecture described in Section 8 can be implemented on one or more radio devices (e.g., the 329 and / or 330 radio devices described above) or modems (e.g., the 510 and / or 520 modems) as described above. As shown, the Non-Access Stratum (NAS) 810 can include a 5G NAS 820 and a legacy NAS 850. The legacy NAS 850 can include a communication link with a legacy Access Stratum (AS) 870. The 5G NAS 820 can include communication links with both a 5G AS 840 and a non-3GPP AS 830 and a Wi-Fi AS 832. The 5G NAS 820 can include functional units associated with both access stratums. Thus, the 5G NAS 820 can include multiple 5G MM units 826 and 828 and 5G Session Management (SM) units 822 and 824.The older NAS 850 can include functional units such as the Short Message Service (SMS) entity 852, the Developed Packet System Session Management (ESM) entity 854, the Session Management (SM) entity 856, the EPS Mobility Management (EMM) entity 858, and the Mobility Management (MM) / GPRS Mobility Management (GMM) entity 860.

[0071] Additionally, the older AS 870 can include functional units such as an LTE-AS 872, UMTS-AS 874 and / or GSM / GPRS-AS 876.

[0072] Thus, the 800 baseband processor architecture enables a shared 5G NAS for both 5G cellular and non-cellular access (e.g., non-3GPP access). It is important to note that, as shown, the 5G MM can maintain individual connection management and registration management state machines for each connection. Additionally, a device (e.g., the UE 106) can register with a single PLMN (e.g., 5G-CN) using both 5G cellular and non-cellular access. Furthermore, it is possible for the device to be in a connected state during one access and in a sleep state during another, and vice versa. Finally, there can be common 5G MM procedures for both accesses (e.g., registration, deregistration, identification, authentication, and so on).

[0073] It should be noted that in various embodiments, one or more of the elements described above may be configured to perform procedures for planning a UE based on an energy planning profile, which may specify one or more parameters associated with the UE communication behavior, e.g., one or more restrictions on the UE communication behavior and / or slot planning of the UE communication, as further described herein. EU energy planning profile

[0074] In current implementations of the 5G New Radio (5G NR) standard, a UE can be configured to periodically monitor the Physical Downlink Control Channel (PDCCH), e.g., as described by Fig. Figure 9A illustrates this. As shown, the UE can monitor the PDCCH at every fifth slot 902, and if the UE has no pending data, it can enter a low-power mode to reduce power consumption when the PDCCH in slots 904 is not being monitored. In some implementations, a search space configuration can be enabled to allow the UE to periodically monitor the PDCCH. The power consumption of the UE during periodic monitoring of the PDCCH is determined by Fig. Figure 9B illustrates this. As shown, if the UE is not monitoring the PDCCH, it can have very low power consumption; however, the power consumption can increase before the monitoring period (e.g., power ramp 910), remain at maximum power consumption for a period before, during, and after the monitoring period (e.g., maximum power level 912), and then decrease after the monitoring period is complete (e.g., power ramp 914). For example, if the UE is receiving data in slot N (e.g., slot 906 of Fig. 9A), the UE powers up before slot N to prepare for data reception. During power-up, the UE may consume power (e.g., power ramp 910) to prepare (or reinitialize / restart) its clock, set its voltage configuration, warm up its radio frequency integrated circuit (RFIC), lock its phase lock loop (PLL), and so on. After receiving the data in slot N, a modem in the UE may perform decoding and a series of actions to decode the signal and turn off components of the UE to reduce power consumption. For example, the UE modem may turn off the RFIC, perform automatic gain control (AGC), time tracking loops (TTL) and / or frequency tracking loops (FTL), channel estimation, and / or data decoding.As another example, the UE starts up in advance (before) slot N to prepare the data transmission when the UE receives data in a slot N (e.g. slot 906 from . Fig. 9A). During startup, similar to when the UE is preparing to receive data, the UE can consume power (e.g., power ramp 910) to prepare (or reinitialize / restart) its clock, warm up the UE's RFIC, lock the phase-lock loop (PLL), encode the data, and so on. After slot N, the UE can consume power (e.g., power ramp 914) by turning off the RFIC. Thus, turning components on and off for receiving and / or sending data consumes power (especially starting up or shutting down the RFIC).

[0075] The embodiments described herein disclose systems and methods for reducing power consumption during startup and shutdown, which are associated with periodic monitoring of the PDCCH. In some embodiments, the UE can, for example, inform a base station (e.g., a gNB) about a planning constraint by means of a planning profile, such as an energy planning profile. Fig. 10D, Fig. 11D, Fig. 12D and Fig. Figure 13D illustrates, for example, the power savings for various transmit and / or receive scenarios. In some embodiments, the UE can send an acknowledgment, data on the PUSCH, and / or other various data and / or control information. In some embodiments, the UE can receive data on the PDCCH and / or on the PDSCH.

[0076] Fig. Figure 10D illustrates the power savings over two transmissions compared to current implementations, as shown in the Fig. 10A to 10C, according to some embodiments, are illustrated. In particular, the Fig. 10A to 10C the current consumed for a first transmission ( Fig. 10A), the current consumed for a second transmission ( Fig. 10B) and the total power consumption between the two transmissions ( Fig. 10C). As shown, the UE consumes power for each transmission to prepare for the transmission, to carry out the transmission, and then to shut down after the transmission. According to some embodiments and as in Fig. Figure 10D illustrates that if the UE can schedule the transmissions sequentially, the UE can avoid the power consumed when shutting down after the first transmission and restarting for the second transmission, thus saving additional power compared to current implementations.

[0077] Fig. Figure 11D illustrates the power savings between two reception processes compared to current implementations, as shown in the Fig. Figures 11A to 11C, according to some embodiments, illustrate. In particular, the Fig. 11A to 11C the current consumed for a first reception process ( Fig. 11A), the current consumed for a second reception process ( Fig. 11B) and the total power consumption between the two reception processes ( Fig. 11C). As shown, the UE consumes power for each reception operation to prepare for the reception operation, to carry out the reception operation, and then to shut down after the reception operation. If, according to some embodiments and as described by Fig. Figure 11D illustrates that if the UE can schedule the reception processes sequentially, the UE can avoid the power consumed when shutting down after the first reception process and when restarting for the second reception process, thus saving additional power compared to current implementations.

[0078] Fig. Figure 12D illustrates the power savings between a transmission followed by a reception process compared to current implementations, as shown in the Fig. Figures 12A to 12C, according to some embodiments, illustrate. In particular, the Fig. 12A to 12C for a transmission ( Fig. 12A) consumed current, the current consumed for a receiving process ( Fig. 12B) and the total power consumption between the transmission and reception process ( Fig. 12C). As shown, the UE consumes power for both the transmission and reception processes, to prepare for the transmission / reception process, to carry out the transmission / reception process, and then to shut down after the transmission / reception process. If, according to some embodiments and as in Fig. Figure 12D illustrates that while the UE can schedule the transmission and reception processes sequentially, it can avoid the power consumed during shutdown after transmission and restart for reception, thus saving additional power compared to current implementations.

[0079] Fig. Figure 13D illustrates the power savings between a receive operation followed by a transmit compared to current implementations, as shown in the Fig. Figures 13A to 13C, according to some embodiments, illustrate. In particular, the Fig. 13A to 13C the current consumed for a reception process ( Fig. 13A), the electricity consumed for a transmission ( Fig. 13B) and the total power consumption between the receiving process and the transmission ( Fig. 13C). As shown, the UE consumes power for both the transmission and reception processes, to prepare for the transmission / reception process, to carry out the transmission / reception process, and then to shut down after the transmission / reception process. If, according to some embodiments and as in Fig. Figure 13D illustrates that if the UE can schedule the receiving and transmitting processes sequentially, the UE can avoid the power consumed during shutdown after the receiving process and during restart for transmission, thus saving additional power compared to current implementations.

[0080] Fig. Figure 14 illustrates a block diagram of an example process for determining a planning profile for a UE according to some embodiments. The in Fig. The process shown in Figure 14 can be used in conjunction with any of the systems or devices shown in the preceding figures, in addition to other devices. In various embodiments, some of the process elements shown can be performed simultaneously, in a different order than shown, or omitted. Furthermore, additional process elements can be performed as desired. As shown, this process can operate as follows.

[0081] In the 1402, a User Environment (UE), such as UE 106, can propose one or more scheduling profiles, such as one or more power scheduling profiles, to a base station, such as base station 102 (which may be configured as a gNB, such as gNB 604). It is important to note that if the UE proposes more than one power scheduling profile, the power scheduling profiles must not conflict with each other. In some embodiments, the proposal may be transmitted via a Radio Resource Control (RRC) signaling message. In some embodiments, a power scheduling profile may include one or more (or a set of) parameters and / or constraints for the system configuration. The parameters (or constraints) may limit network scheduling to a specific configuration. In some embodiments, a power scheduling profile may include a set of other power scheduling profiles.In some embodiments, such as in . Fig. As illustrated in section 15, an energy planning profile can define a specific UE behavior or sets of behaviors. For example, as shown in Fig. Figure 15 shows how profile P1 can define a delayed acknowledgment (ACK) profile with PDCCH monitoring. As another example, profile P2 can define a delayed push scheduling profile with PDCCH monitoring. As another example, profile P3 can define a cross-slot scheduling profile with PDCCH monitoring; profile P4 can define a Large Bandwidth Part (BWP) profile for scheduling large data packets; profile P5 can define a standalone slot scheduling profile; profile P10 can define a power-saving profile, e.g., a set of profiles including any, some, or all of profiles P1, P2, and / or P3; profile P11 can define a high-throughput profile, e.g., a set of profiles including any, some, or all of profiles P1 and / or P4; profile P14 can define a low-latency profile, e.g.,a set of profiles that includes at least profile P5; a profile P15 can define a profile for high system capacity; a profile P14 can define a profile for small data traffic, e.g. voice data and / or SMS data; a profile P20 can define a profile for a PDCCH monitoring period.

[0082] In some embodiments, an energy planning profile may include one or more parameters for defining the profile. For example, the parameters may include a set of values ​​for search space monitoring periodicity. As another example, the parameters may include a set of configurable values ​​and / or constraints for K0, where K0 defines a number of slots (e.g., from 0 to n) between a slot planned for PDCCH and a slot planned for PDSCH. As yet another example, the parameters may include a set of configurable values ​​and / or constraints for K1, where K1 defines a number of slots (e.g., from 0 to n) between a slot planned for PDSCH and a slot planned for confirmation. As yet another example, the parameters may include a set of configurable values ​​and / or constraints for K2, where K2 defines a number of slots (e.g.,from 0 to n) defines the slot allocated for PDCCH and the slot allocated for PUSCH. Additionally, the parameters can include minimum and / or maximum bandwidth values ​​and / or limitations in BWPs, a number of supported multiple-input multiple-output (MIMO) layers, search space indices, CORESET (Control Resource Set) indices, BWP indices, secondary cell (scell) indices, maximum number of scells, DRX configurations, and so on. It should be noted that in some embodiments, different profiles may include different parameters and / or limitations. In other words, a first profile may include a first combination of the parameters discussed above, among other parameters, and a second profile may include a second combination of the parameters discussed above.

[0083] Fig. Figure 16 illustrates example parameter sets for different profiles according to some embodiments. As shown, a profile P1 can include various parameters to support delayed ACK with subsequent PDCCH monitoring, such as a first parameter p, where p specifies a search space monitoring periodicity, and a second parameter that defines a relationship between Ko, K1, and p. Additionally, a profile P2 can include various parameters to support delayed PUSCH with subsequent PDCCH monitoring, such as a first parameter p, where p specifies a search space monitoring periodicity, and a second parameter that defines a relationship between K2 and p.Furthermore, a P3 profile can include various parameters to support delayed cross-slot planning with subsequent PDCCH monitoring, such as a first parameter p, where p defines a search space monitoring periodicity, a second parameter that defines a relationship between K0 and p, and a third parameter that defines a value for K1. Additionally, a P4 profile can include various parameters to support low traffic rates, such as supported BWPs, supported search space indices, supported MIMO layers, supported values ​​of Ko, K1 and K2, supported Scell ​​indices, supported number of S-cells, and so on.

[0084] Returning to Fig. At step 1404, the base station can determine whether to accept the planning proposal (e.g., the one or more energy planning profiles proposed by the UE at step 1402). This determination can be based, at least in part, on network planning constraints, such as whether the base station has outstanding data for the UE, whether the base station has previously accepted planning proposals (from the UE and / or other UEs served by the base station) that conflict with the UE's proposal, channel conditions, and so on. If the base station accepts the planning proposal, the process can proceed at step 1410. Alternatively, if the base station does not accept the planning proposal, the process can proceed at step 1406.

[0085] If the base station determines at 1406 not to accept the scheduling proposal, it can submit a counter-proposal to the UE. In response, the base station and the UE can negotiate at 1408 (e.g., by exchanging one or more additional proposals) to determine one (or more) power scheduling profiles for UE communication. It should be noted that the UE and the base station can agree on more than one power scheduling profile, as long as the multiple profiles do not conflict with each other. In other words, in some embodiments, the base station (network) can configure the UE with multiple profiles. In some embodiments, one or more power scheduling profiles can be active, with an active profile being one currently in use between the base station and the UE.

[0086] At 1410, the UE and the base station can communicate based on at least one of the agreed-upon energy planning profiles (e.g., active profiles). For example, if a first profile specifies the UE's behavior when transmitting an acknowledgment (ACK) during PDCCH monitoring, the base station can schedule the ACK in a slot following the PDCCH monitoring based on a search area monitoring periodicity included in the first profile, e.g., as described below with reference to Fig. 17 is further described. Similarly, if a second profile defines the UE behavior during transmission on the PUSCH while performing PDCCH monitoring, the base station can schedule the PUSCH transmission in a slot following the PDCCH monitoring based on a search area monitoring periodicity included in the second profile, e.g., as described below with reference to Fig. 18 further described. Furthermore, if a third profile defines the UE behavior for cross-slot scheduling during PDCCH monitoring, the base station can schedule UE transmissions and receptions based on parameters included in a third profile, e.g., as described below with respect to Fig. 19 is further described. Furthermore, if a fourth profile defines a separate slot, the base station can schedule UE transmissions and receptions based on parameters included in a fourth profile, e.g., as described below with regard to Fig. 20 is described further.

[0087] Fig. Figure 17 illustrates an example of delayed acknowledgment with subsequent PDCCH monitoring according to some embodiments. For example, if a UE, such as UE 106, is to send an acknowledgment (ACK) in the uplink (UL) and monitor the PDCCH in a similar timeframe, then the network (e.g., the base station 102, the gNB 604) can schedule the ACK transmission 1708 shortly before the scheduled PDCCH monitoring 1702 occurs (e.g., partly based on an agreed-upon power scheduling profile) such that UE transmission and UE reception can occur in consecutive (e.g., sequential) time slots. Such a scheduling scheme can enable the UE to save power by avoiding a shutdown (e.g., after sending the ACK) and a startup (e.g., before the scheduled PDCCH monitoring 1702). As shown in Figure 17, the UE can be used to save power by avoiding a shutdown (e.g., after sending the ACK) and a startup (e.g., before the scheduled PDCCH monitoring 1702). Fig. As shown in Figure 17, the UE can be configured to monitor the PDCCH every 5 time slots, so that when the UE receives the PDSCH in slot n (e.g., scheduling the PDSCH to the UE at 1706), the UE would typically send a corresponding ACK in slot n+1. However, in some embodiments, a power scheduling profile can delay the corresponding ACK until slot n+4, as shown, allowing the UE to conserve power by preventing an RFIC shutdown and startup. Note that the UE must not monitor the PDCCH at slot 1704. It should also be noted that the power scheduling profile can be determined, at least in part, based on a communication configuration condition and / or a UE constraint. Thus, according to the example in Figure 17, the UE can be configured to monitor the PDCCH at slot 1704. Fig. 17. The communication configuration condition includes that the UE is configured with at least one PDCCH monitoring period of p, where p defines a number of timeslots between PDCCH monitoring and p is greater than 1. The UE constraint can be sequential (or contiguous) or very close (e.g., one-slot gap) ACK and PDCCH monitoring. In other words, if the UE is configured to monitor the PDCCH in slot n, an ACK for a PDSCH can be scheduled one timeslot before the PDCCH monitoring, e.g., timeslot n - 1, so that the transmission (ACK) and reception (PDCCH monitoring) can occur without an RFIC shutdown and start-up in between. Therefore, if such an energy planning profile is activated (e.g., an RRC parameter PS_ACK_Schedule is set to "true" or "1"), the network can make planning decisions (such as...(the ACK transmission timing) to meet the EU restriction.

[0088] Fig. Figure 18 illustrates an example of a delayed PUSCH with subsequent PDCCH monitoring according to some embodiments. For example, if a UE, such as UE 106, is to send the PUSCH during PDCCH monitoring, the network (e.g., base station 102, gNB 604) can schedule the sending of PUSCH 1808 in a timeslot immediately preceding a scheduled PDCCH monitoring timeslot 1802 (e.g., partly based on an agreed energy scheduling profile), so that the UE can send and receive in successive (consecutive) timeslots. Such a scheduling scheme can enable the UE to save power by preventing a shutdown (e.g., after sending on the PUSCH) and a startup (e.g., before the scheduled PDCCH monitoring). As shown in Fig. As shown in Figure 18, the UE can be configured to monitor the PDCCH every 5 time slots. That is, if the UE is scheduled to send the PUSCH in slot n+4 and monitor the PDCCH in the next slot (e.g., slot n+5), then the UE can save power by preventing an RFIC shutdown and startup. Note that the UE must not monitor the PDCCH on slots 1804. It should also be noted that the power scheduling profile can be determined, at least in part, based on a communication configuration condition and / or a UE constraint. Thus, according to the example in Figure 18, the following can be achieved: Fig. 18. The communication configuration condition includes that the UE is configured with at least one PDCCH monitoring period of p, where p defines a number of timeslots between PDCCH monitoring and p is greater than 1. The UE constraint can be a sequential (or successive) PUSCH transmission and PDCCH monitoring. In other words, if the UE is configured to monitor the PDCCH in slot n, a PUSCH transmission can be scheduled one timeslot before the PDCCH monitoring, e.g., timeslot n - 1, so that the transmission (PUSCH) and receive operation (PDCCH monitoring) can occur without an RFIC shutdown and RFIC startup in between. Therefore, if such an energy planning profile is activated (e.g., an RRC parameter PS_PUSCH_Schedule is set to "true" or "1"), the network can make planning decisions (such as the PUSCH transmission timing) to meet the UE constraint.

[0089] Fig. Figure 19 illustrates an example of delayed cross-slot scheduling with subsequent PDCCH monitoring according to some embodiments. For example, if a UE, such as UE 106, is scheduled to receive on the PDSCH while performing PDCCH monitoring 1902, the network (e.g., base station 102, gNB 604) can schedule the PDSCH receive operation 1906 and an ACK transmission 1908 in a timeslot immediately preceding a scheduled PDCCH monitoring timeslot 1902 (e.g., partly based on an agreed-upon power scheduling profile), so that the UE can transmit and receive in consecutive timeslots. Such a scheduling scheme can enable the UE to conserve power by preventing a shutdown (e.g., after transmitting on the PUSCH) and a startup (e.g., before the scheduled PDCCH monitoring). It should be noted that the UE is not permitted to monitor the PDCCH at slots 1904.It should also be noted that if the UE only receives on the PDCCH, it can use a narrow band (NB). However, if the UE also receives on the PDSCH, it can open its radio frequency bandwidth to a wider bandwidth (WB) to receive data on the PDSCH. To take advantage of bandwidth matching with transmit / receive alignment, the PDSCH and ACK can therefore be scheduled in a timeslot immediately before the planned PDCCH monitoring. As in... Fig. As shown in Figure 19, the UE can be configured to monitor the PDCCH every 3 time slots. That is, if the UE is scheduled to receive on the PDSCH in slot n+2 and an ACK from the PDCCH monitoring on slot n+2 is delayed, then the UE can monitor the PDCCH in the next slot (e.g., slot n+3). This allows the UE to save power by preventing an RFIC shutdown and startup while simultaneously taking advantage of bandwidth matching. It should be noted that the power scheduling profile can be determined, at least in part, based on a communication configuration condition and / or a UE constraint. Thus, according to the example in Figure 19, the following can be determined: Fig. 19. The communication configuration condition includes that the UE is configured with at least one PDCCH monitoring period of p, where p defines a number of time slots between PDCCH monitoring sessions and p is greater than 1, allowing cross-slot scheduling. The UE constraint can be K0 greater than 0 (which allows the UE to monitor the PDCCH with a narrow BWP and receive the PDSCH with a wide BWP) and K1 = 0 (which ensures that PDSCH receive and ACK transmission occur in a common (same) time slot), where K0 defines a number of slots (e.g., from 0 to n) between a slot scheduled for PDCCH and a slot scheduled for PDSCH, and K1 defines a number of slots (e.g., from 0 to n) between a slot scheduled for PDSCH and a slot scheduled for acknowledgment.In other words, if the UE is configured to monitor the PDCCH in slot n, a PDSCH receive operation and an ACK transmission can be scheduled one timeslot before the PDCCH monitoring, e.g., timeslot n - 1, so that the receive (PDSCH) / transmit (ACK) operation and the receive operation (PDCCH monitoring) can occur without an RFIC shutdown and RFIC startup in between. Thus, when such a power scheduling profile is enabled (e.g., an RRC parameter PS_K1_equal_o is set to "true" or "1"), the network can make scheduling decisions (such as ACK transmission timing and PDSCH receive operation) to satisfy the UE constraint.

[0090] Fig. Figure 20 illustrates an example of standalone slot scheduling with subsequent PDCCH monitoring according to some embodiments. For example, if a UE, such as UE 106, is to receive on the PDSCH while performing PDCCH monitoring 2002, then the network (e.g., base station 102, gNB 604) can schedule the PDSCH receive operation 2006 and an ACK transmission 2008 in a timeslot with a scheduled PDCCH monitoring timeslot 2002 (e.g., partly based on an agreed energy scheduling profile), so that the UE can transmit and receive in a single timeslot. Such a scheduling scheme can allow the UE to save power by preventing a shutdown (e.g., after receiving the PDCCH and after receiving the PDSCH) and a startup (e.g., before receiving the scheduled PDSCH and before sending the ACK). As in Fig. As shown in Figure 20, the UE can be configured to monitor the PDCCH every 3 time slots. That is, if the UE is scheduled to receive on the PDSCH in slot n, then an ACK from the PDSCH in slot n is also scheduled. Such a scheme can allow the UE to save power by preventing an RFIC shutdown and startup. Note that the UE must not monitor the PDCCH on slots 2004. It should also be noted that the power planning profile can be determined, at least partially, based on a communication configuration condition and / or a UE constraint. Thus, according to the example of Fig.20. The communication configuration condition includes that the UE is configured with at least one PDCCH monitoring period of p, where p defines a number of time slots between PDCCH monitoring and p is greater than 1, allowing the same slot scheduling to be enabled. The UE constraint can be K0 = 0 (which allows the UE to monitor the PDCCH with a narrow BWP and receive the PDSCH with a wide BWP) and K1 = 0 (which ensures that the PDSCH receive operation and ACK transmission occur in a common (same) time slot), where K0 defines a number of slots (e.g., from 0 to n) between a slot scheduled for the PDCCH and a slot scheduled for the PDSCH, and K1 defines a number of slots (e.g., from 0 to n) between a slot scheduled for the PDSCH and a slot scheduled for an acknowledgment.In other words, if the UE is configured to monitor the PDCCH in slot n, a PDSCH receive operation and an ACK transmission can be scheduled in a single timeslot with PDCCH monitoring, e.g., timeslot n, so that the receive (PDSCH) / transmit (ACK) operation and the receive operation (PDCCH monitoring) can occur without an RFIC shutdown and start-up in between. Thus, when such a power scheduling profile is enabled (e.g., an RRC parameter K0_K1_equal_0 is set to "true" or "1"), the network can make scheduling decisions (such as ACK transmission timing and PDSCH receive operation) to comply with the UE constraint.

[0091] As explained above, in some embodiments, one or more profiles for data transfer between a UE, such as the UE 106, and a base station (network), such as the base station 102, the gNB 604, can be active (e.g., configured for use). In some embodiments, profiles can be dynamically changed (or switched), for example, in response to increases and / or decreases in the traffic arrival rate, changes in traffic delay requirements, changes in power consumption requirements, and so on. In some embodiments, the dynamic change can be triggered by explicit signaling between the network and the UE. For example, the network can send an explicit signal to the UE to change an active profile to be used for data transfer.As another example, the UE can send an explicit signal to the network to request a change to an active profile to be used for a data transfer. In some implementations, the dynamic change can be triggered (additionally and / or alternatively) based on a timer. For example, an active profile to be used for a data transfer can change due to a timer operation.

[0092] In some embodiments, the network (e.g., the gNB 604, the base station 102) can specify a profile to be used by a user entity (UE), such as the UE 106, by signaling using downlink control information (DCI), a medium access control (MAC) control element (CE), and / or radio resource control (RRC) signaling. For example, the network can send (transmit) a signal (e.g., an indicator included in the DCI, MAC CE, and / or RRC signaling) that can indicate to the UE that it is using a high-throughput profile when a large amount of data is to be delivered to the UE. As another example, the network can send a signal (e.g.,The network can send (transmit) a signal (included in DCI, MAC-CE, and / or RRC signaling) that indicates to the UE to use a power-saving profile when the traffic arrival rate drops below a threshold. As another example, the network can send (transmit) a Layer 1 (L1) signal to indicate to the UE that it is using a low-latency profile when supported traffic requires low latency.

[0093] In some implementations, the UE can send (transmit) a profile change request signal to the network. For example, if a UE knows that a downlink file transfer has completed and might want to switch to a power-saving profile, then the UE can request a profile change to a power-saving profile in response to the completion of a downlink file transfer.

[0094] In some embodiments, a profile change can be based, at least partially, on a timer operation. For example, a default profile can be configured. Additionally, a timer (e.g., a ProfileActiveTimer) can be defined. The timer can be started, restarted, and / or reset when the network activates a new set of profiles. Additionally, the timer can be reset based on a condition. For example, in some embodiments, the condition can include a data arrival rate exceeding a threshold, a number of PDSCH slots scheduled for a certain number of slots exceeding a threshold, and so on. In some embodiments, after the timer expires, a currently active profile can be deactivated (turned off) and a default profile can be activated (activated).In some implementations, the default profile can be updated regularly, e.g. via the network. Other embodiments

[0095] In some embodiments, a method for a user equipment device, such as UE 106, may include: Communication exchange with a base station to determine one or more planning profiles, such as one or more energy planning profiles, wherein an energy planning profile defines one or more parameters and / or restrictions of the UE communication behavior; Receiving a slot configuration plan based on at least one power planning profile of one or more power planning profiles; and performing communication with the base station based on the at least one power planning profile.

[0096] In some embodiments, communication with the base station to determine one or more energy planning profiles may include the exchange of radio resource control (RRC) signal messages.

[0097] In some embodiments, one or more energy planning profiles must not conflict with each other.

[0098] In some embodiments, one or more energy planning profiles may include (comprise) one or more of: a delayed acknowledgment (ACK) profile with physical downlink control channel (PDCCH) monitoring; a profile for delayed scheduling of the physical uplink shared channel (PUSCH) with PDCCH monitoring; a profile for cross-slot planning with PDCCH monitoring; a profile for the large bandwidth share (BWP) for planning large data packets; a profile for independent slot planning; a profile for saving electricity; a profile for high throughput; a low latency profile; a profile for high system capacity; a small data traffic profile; and / or a profile for the PDCCH monitoring period.

[0099] In some embodiments, one or more parameters and / or restrictions may include one or more of: a first parameter that defines a set of values ​​for the search space monitoring periodicity; a second parameter that defines a number of slots between a slot planned for the receive operation on the PDCCH and a slot planned for the receive operation on the physical downlink shared channel (PDSCH); a third parameter that defines a number of slots between a slot planned for the receive operation on the PDSCH and a slot planned for an acknowledgment; a fourth parameter that defines a number of slots between a slot planned for the receive process on the PDCCH and a slot planned for transmission on the PUSCH; a fifth parameter that defines minimum and / or maximum bandwidth values ​​and / or limitations in BWPs; and / or a sixth parameter that defines a set of supported MIMO (Multiple-Input-Multi-Output) layers.

[0100] In some embodiments, one or more energy scheduling profiles may include a first profile that prevents the base station from scheduling the transmission of an acknowledgment of data received on the PDCCH to a first slot immediately preceding a second slot scheduled for PDCCH monitoring. In some embodiments, the first profile may be specified via a PS_ACK_Schedule RRC parameter.

[0101] In some embodiments, one or more energy scheduling profiles can include a second profile that prevents the base station from scheduling the transmission on the PUSCH to a third slot immediately preceding a fourth slot scheduled for PDCCH monitoring. In some embodiments, the second profile can be specified via a PS_PUSCH_Schedule RRC parameter.

[0102] In some embodiments, one or more energy scheduling profiles may include a third profile that prevents the base station from scheduling the transmission of an ACK from a PDCCH and a receive operation across slots on the Physical Downlink Shared Channel (PDSCH) to a fifth slot immediately preceding a sixth slot scheduled for PDCCH monitoring. In some embodiments, the third profile is specified via a PS_K1_equal_0 RRC parameter.

[0103] In some embodiments, a method for a base station, such as the gNB 604 and / or the base station 102, may include: Communication exchange with a user equipment device (UE) to determine one or more planning profiles, such as one or more energy planning profiles, wherein an energy planning profile defines one or more parameters and / or constraints of the UE communication behavior; Sending, to the UE, a slot configuration plan based on at least one energy planning profile of one or more energy planning profiles; and carrying out communication with the UE based on the at least one energy planning profile.

[0104] In some embodiments, communication with the UE to determine one or more energy planning profiles may include the exchange of the radio resource control (RRC) signal message.

[0105] In some embodiments, one or more energy planning profiles must not conflict with each other.

[0106] In some embodiments, one or more energy planning profiles may include (comprise) one or more of: a delayed acknowledgment (ACK) profile with physical downlink control channel (PDCCH) monitoring; a profile for delayed scheduling of the physical uplink shared channel (PUSCH) with PDCCH monitoring; a profile for cross-slot planning with PDCCH monitoring; a profile for the large bandwidth share (BWP) for planning large data packets; a profile for independent slot planning; a profile for saving electricity; a profile for high throughput; a low latency profile; a profile for high system capacity; a small data traffic profile; and / or a profile for the PDCCH monitoring period.

[0107] In some embodiments, one or more parameters and / or restrictions may include (comprise) one or more of: a first parameter that defines a set of values ​​for the search space monitoring periodicity; a second parameter that defines a number of slots between a slot planned for the receive operation on the PDCCH and a slot planned for the receive operation on the physical downlink shared channel (PDSCH); a third parameter that defines a number of slots between a slot planned for the receive operation on the PDSCH and a slot planned for an acknowledgment; a fourth parameter that defines a number of slots between a slot planned for the receive process on the PDCCH and a slot planned for transmission on the PUSCH; a fifth parameter that defines minimum and / or maximum bandwidth values ​​and / or limitations in BWPs; and / or a sixth parameter that defines a set of supported MIMO (Multiple-Input-Multi-Output) layers.

[0108] In some embodiments, one or more energy planning profiles may include a first profile that prevents the base station from scheduling the transmission of an acknowledgment of the data received on the PDCCH to a first slot immediately preceding a second slot scheduled for PDCCH monitoring.

[0109] In some implementations, the first profile can be specified via a PS_ACK_Schedule RRC parameter.

[0110] In some embodiments, one or more energy scheduling profiles can include a second profile that prevents the base station from scheduling the transmission on the PUSCH to a third slot immediately preceding a fourth slot scheduled for PDCCH monitoring. In some embodiments, the second profile can be specified via a PS_PUSCH_Schedule RRC parameter.

[0111] In some embodiments, one or more power scheduling profiles may include a third profile that prevents the base station from scheduling the transmission of an ACK from a PDCCH and a receive operation across slots on the Physical Downlink Shared Channel (PDSCH) to a fifth slot immediately preceding a sixth slot scheduled for PDCCH monitoring. In some embodiments, the third profile may be specified via a PS_K1_equal_o-RRC parameter.

[0112] It is understood that the use of personally identifiable information should follow data protection regulations and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining user privacy. In particular, personally identifiable information should be managed and handled in a manner that minimizes the risks of unintentional or unauthorized access or use, and the nature of any authorized use should be clearly indicated to users.

[0113] Embodiments of the present disclosure can be implemented in a variety of forms. For example, some embodiments can be implemented as a computer-implemented method, a computer-readable storage medium, or a computer system. Other embodiments can be implemented using one or more user-adapted hardware devices, such as ASICs. Still other embodiments can be implemented using one or more programmable hardware elements, such as FPGAs.

[0114] In some embodiments, a non-volatile, computer-readable storage medium may be configured to store program instructions and / or data, wherein the program instructions, when executed by a computer system, cause the computer system to perform a procedure, e.g., any one of the procedure execution forms described herein, or any combination of the procedure execution forms described herein, or any subset of any one of the procedure execution forms described herein, or any combination of such subsets.

[0115] In some embodiments, a device (e.g., a UE 106) can be configured to include a processor (or a set of processors) and a storage medium, wherein program instructions are stored on the storage medium, the processor being configured to read and execute the program instructions from the storage medium, and the program instructions being executable to implement any of the various method implementations described herein (or any combination of the method implementations described herein, or any subset of any of the method implementations described herein, or any combination of such subsets). The device can be implemented in one of many forms.

[0116] Although the embodiments have been described above in considerable detail, numerous variations and modifications are apparent to the person skilled in the art after a full understanding of the foregoing disclosure. It is intended that the following claims be interpreted to include all such variations and modifications.

Claims

[1] Procedure, encompassing: by means of a user equipment device (UE) (106), Exchanging communications (1408) with a base station (102, 604) to determine one or more power planning profiles, wherein the communications include a proposal from the UE to the base station for a power planning profile that specifies a constraint of Ko and K2 values, wherein K0 defines a number of slots between a slot planned for a physical downstream control channel, PDCCH, and a slot planned for a physical shared downstream channel, PDSCH, and wherein K2 defines a number of slots between a slot planned for the PDCCH and a slot planned for a physical shared upstream channel, PUSCH; Receiving a slot configuration plan based on the energy planning profile proposed by the UE; and Performing communication (1410) with the base station based on the energy planning profile proposed by the UE. [2] Method according to claim 1, wherein the communication with the base station for determining one or more energy planning profiles includes an exchange of the Radio Resource Control (RRC) signal message. [3] Method according to any of the preceding claims, wherein the one or more energy planning profiles do not conflict with each other. [4] Method according to any of the preceding claims, wherein the one or more energy planning profiles include one or more of: a delayed acknowledgment profile, ACK, with monitoring of the Physical Downlink Control Channel (PDCCH); a profile for a delayed physical uplink shared channel (PUSCH) that is scheduled with PDCCH monitoring; a profile for cross-slot planning with PDCCH monitoring; a profile for a large bandwidth part (BWP) for planning large data packets; a profile for independent slot planning; a profile for saving electricity; a profile for high throughput; a low latency profile; a profile for high system capacity; a small data traffic profile; or a profile for a PDCCH monitoring period. [5] Method according to any one of the preceding claims, further comprising: where one or more parameters include one or more of: a first parameter that defines a set of values ​​for a search space monitoring periodicity; a second parameter that defines a number of slots between a slot planned for the receive operation on the PDCCH and a slot planned for the receive operation on the physical downlink shared channel (PDSCH); a third parameter that defines a number of slots between a slot planned for the receive operation on the PDSCH and a slot planned for an acknowledgment; a fourth parameter that defines a number of slots between a slot planned for the receive process on the PDCCH and a slot planned for the transmit on the PUSCH; a fifth parameter that defines minimum and / or maximum bandwidth values ​​and / or limitations in BWPs; or a sixth parameter that defines a set of supported multiple-input multiple-output (MIMO) layers. [6] Method according to any of the preceding claims, wherein the one or more energy planning profiles comprise a first profile that prevents the base station from scheduling the transmission of an acknowledgment of the data received on the PDCCH to a first slot immediately preceding a second slot scheduled for PDCCH monitoring. [7] Method according to claim 6, wherein the first profile is specified via a PS_ACK_Schedule-RRC parameter. [8] Method according to any of the preceding claims, wherein the one or more energy planning profiles comprise a second profile that prevents the base station from planning the transmission on the PUSCH to a third slot immediately preceding a fourth slot planned for PDCCH monitoring. [9] Method according to claim 8, wherein the second profile is specified via a PS_PUSCH_Schedule-RRC parameter. [10] Method according to one of the preceding claims, wherein the one or more energy planning profiles comprise a third profile that prevents the base station from scheduling the transmission of an ACK of a PDCCH and a receive operation on the physical downlink shared channel (PDSCH) to a fifth slot immediately preceding a sixth slot scheduled for PDCCH monitoring. [11] Method according to claim 10, wherein the third profile is specified via a PS_K1_equal_o-RRC parameter. [12] Method according to any one of the preceding claims, further comprising: the EU, which proposes one or more energy planning profiles to the base station (1402); and receives a counter-proposal from the base station (1406). [13] Method according to any one of the preceding claims, further comprising: the EU, which receives a signal from the base station indicating a change from at least one energy planning profile to another energy planning profile. [14] Method according to any one of the preceding claims, further comprising: the EU, which sends a signal to the base station indicating a request to switch from at least one energy planning profile to another energy planning profile. [15] Device comprising: at least one antenna; at least one radio device coupled to at least one antenna; and a processing element coupled with at least one radio device; wherein the processing element is configured to cause the device to implement a method according to any one of claims 1 to 14. [16] Storage medium comprising program instructions which, when executed, cause a device to implement a method according to any one of claims 1 to 14.

Images