Apparatus, system, and method for scheduling power profile for ue power saving

Abstract

The present disclosure relates to apparatuses, systems, and methods for scheduling power profile for UE power saving. Apparatuses, systems, and methods are provided for a wireless device to perform a method comprising a user equipment device (UE) exchanging communications with a base station to determine one or more scheduling profiles, such as one or more scheduling power profiles, where a scheduling power profile can specify one or more parameters associated with UE communication behavior, such as one or more constraints on UE communication behavior and / or time slot scheduling of UE communications. Additionally, the method can include the UE receiving a time slot configuration schedule from the base station. The time slot configuration schedule can be based on at least one of the one or more scheduling power profiles. Moreover, the method can include the UE performing communications with the base station based on the at least one scheduling power profile.

Description

[0001] This application is a divisional application of Chinese patent application filed on March 12, 2019, with national application number 201910183822.0 and invention title "Scheduling Power Profile for UE Power Saving". Technical Field

[0002] This application relates to wireless devices, and more specifically, to devices, systems, and methods for transmitting scheduling profiles, such as scheduling power profiles, for power saving to a network.

[0003] Related technical descriptions

[0004] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices now offer access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and can operate complex applications that utilize these functions.

[0005] Long Term Evolution (LTE) has become the technology of choice for most wireless network operators worldwide, providing their user base with mobile broadband data and high-speed internet access. LTE defines multiple downlink (DL) physical channels, classified as transport or control channels, to carry blocks of information received from Media Access Control (MAC) and higher layers. LTE also defines the number of physical layer channels for the uplink (UL).

[0006] For example, LTE defines the Physical Downlink Shared Channel (PDSCH) as the DL transport channel. The PDSCH is the primary data bearer channel allocated to users on a dynamic and opportunistic basis. The PDSCH carries data in transport blocks (TBs) corresponding to MAC Protocol Data Units (PDUs), which are passed from the MAC layer to the physical (PHY) layer once every transmission time interval (TTI). The PDSCH is also used to transmit broadcast information such as System Information Blocks (SIBs) and paging messages.

[0007] For example, LTE defines the Physical Downlink Control Channel (PDCCH) as the DL Control Channel, which carries the UE's resource allocation contained in the Downlink Control Information (DCI) message. Multiple PDCCHs can be transmitted in the same subframe using Control Channel Elements (CCEs), each of which is nine groups of four resource elements called Resource Element Groups (REGs). The PDCCH uses Quadrature Phase Shift Keying (QPSK) modulation, where four QPSK symbols are mapped to each REG. Furthermore, depending on channel conditions, 1, 2, 4, or 8 CCEs can be used to ensure sufficient robustness.

[0008] Additionally, LTE defines the Physical Uplink Shared Channel (PUSCH) as a UL channel shared by all devices (User Equipment, UE) in the radio cell to transmit user data to the network. Scheduling of all UEs is under the control of the LTE base station (Enhanced Node B or eNB). The eNB uses uplink scheduling clearance (DCI format 0) to notify the UE of resource block (RB) allocations and the modulation and coding schemes to be used. The PUSCH typically supports QPSK and Quadrature Amplitude Modulation (QAM). In addition to user data, the PUSCH carries any control information required for decoding, 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) expansion.

[0009] The next telecommunications standard proposed to surpass the current International Mobile Telecommunications Advanced (IMT-Advanced) standard is called 5G mobile network or 5G radio system, or simply 5G (for 5G New Radio, it is also called 5G-NR, or simply NR). Compared to the current LTE standard, 5G-NR offers higher capacity for higher density mobile broadband users, while supporting ultra-reliable and massive machine-type communication between devices, as well as lower latency and lower battery consumption. Furthermore, the 5G-NR standard allows for less restrictive UE scheduling compared to the current LTE standard. Therefore, efforts are underway to continuously develop 5G-NR to take advantage of less restrictive UE scheduling in order to further capitalize on power saving opportunities. Summary of the Invention

[0010] The implementation plan involves devices, systems, and methods for scheduling user equipment (UE) based on scheduling power profiles.

[0011] In some embodiments, the user equipment may be configured to perform a method for constraining UE communication behavior. This method may include the UE exchanging communications with a base station to determine one or more scheduling profiles, such as one or more scheduling power profiles. In some embodiments, the communication with the base station to determine the one or more scheduling power profiles may include exchanging one or more Radio Resource Control (RRC) signaling messages. In some embodiments, the one or more scheduling power profiles may not conflict with each other. In some embodiments, the scheduling power profile may specify one or more parameters associated with UE communication behavior, such as one or more constraints on UE communication behavior and / or time slot scheduling of UE communication. Additionally, the method may include the UE receiving time slot configuration scheduling from the base station. The time slot configuration scheduling may be based on at least one of the one or more scheduling power profiles. Furthermore, the method may include the UE performing communication with the base station based on at least one scheduling power profile.

[0012] In some implementations, one or more scheduling power profiles may include a profile that constrains the base station to schedule the transmission of acknowledgments of data received on the PDCCH to a time slot immediately preceding the time slot scheduled for PDCCH monitoring. In some implementations, one or more scheduling power profiles may include a profile that constrains the base station to schedule transmissions on the PUSCH to a time slot immediately preceding the time slot scheduled for PDCCH monitoring. In some implementations, one or more scheduling power profiles may include a profile that constrains the base station to schedule the transmission of ACKs for the PDCCH and the reception of data on the PDSCH across time slots immediately preceding the time slot scheduled for PDCCH monitoring.

[0013] The technologies described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to any one of cellular phones, tablets, wearable computing devices, portable media players, and various other computing devices.

[0014] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or essence of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0015] A better understanding of the subject matter can be obtained by considering the following detailed description of the various embodiments in conjunction with the accompanying drawings, in which:

[0016] Figure 1 An example wireless communication system according to some implementation schemes is shown.

[0017] Figure 2 A base station (BS) communicating with a user equipment (UE) according to some implementation schemes is shown.

[0018] Figure 3 Example block diagrams of a UE according to some implementation schemes are shown.

[0019] Figure 4 Example block diagrams of a BS according to some implementation schemes are shown.

[0020] Figure 5 An example block diagram of a cellular communication circuit according to some implementation schemes is shown.

[0021] Figure 6AAn example of the connection between the EPC network, the LTE base station (eNB), and the 5G NR base station (gNB) is shown.

[0022] Figure 6B An example of the protocol stack used for eNB and gNB is shown.

[0023] Figure 7A An example of a 5G network architecture according to some implementation schemes is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access in 5G CN.

[0024] Figure 7B An example of a 5G network architecture according to some implementation schemes is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access as well as non-3GPP access in 5G CN.

[0025] Figure 8 An example of a baseband processor architecture for a UE according to some implementation schemes is shown.

[0026] Figure 9A An example of the PDCCH monitoring interval is shown.

[0027] Figure 9B An example of the power consumption of a UE for multiple PDCCH monitoring slots is shown.

[0028] Figures 10A to 10C An example of power consumption during multiple transmissions by the UE during PDCCH monitoring is shown.

[0029] Figure 10D An example of power consumption during multiple transmissions by a UE during PDCCH monitoring is shown according to some implementation schemes.

[0030] Figures 11A to 11C An example of power consumption during multiple receptions by the UE during PDCCH monitoring is shown.

[0031] Figure 11D An example of power consumption during multiple receptions by a UE during PDCCH monitoring is shown according to some implementation schemes.

[0032] Figures 12A to 12C An example of power consumption during PDCCH monitoring, where the UE transmits and then receives, is shown.

[0033] Figure 12D An example of power consumption during PDCCH monitoring of a UE transmitting and then receiving is shown according to some implementation schemes.

[0034] Figures 13A to 13CAn example of power consumption during PDCCH monitoring when the UE receives and then transmits is shown.

[0035] Figure 13D An example of power consumption during PDCCH monitoring for a UE to receive and then transmit is shown according to some implementation schemes.

[0036] Figure 14 A block diagram illustrating an example of a process for determining a UE's scheduling profile according to some implementation schemes is shown.

[0037] Figure 15 Example configuration files and corresponding UE behaviors are shown according to some implementation schemes.

[0038] Figure 16 Example sets of parameters for various configuration files according to some implementation schemes are shown.

[0039] Figure 17 An example of delayed confirmation with subsequent PDCCH monitoring is shown according to some implementation schemes.

[0040] Figure 18 An example of a delayed PUSCH with subsequent PDCCH monitoring is shown according to some implementation schemes.

[0041] Figure 19 An example of delay-cross-slot scheduling with subsequent PDCCH monitoring is shown according to some implementation schemes.

[0042] Figure 20 An example of self-contained slot scheduling with subsequent PDCCH monitoring is shown according to some implementation schemes.

[0043] While the features described herein may be subject to various modifications and alternatives, specific embodiments thereof are shown by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit the invention to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0044] the term

[0045] The following is a glossary of terms used in this disclosure:

[0046] Storage medium – any of various types of nontransitory memory devices or storage devices. The term "storage medium" is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; 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 media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Storage media may also include other types of nontransitory memory or combinations thereof. Furthermore, storage media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media that may reside in different locations on different computer systems connected via a network, for example. Storage media may store program instructions (e.g., manifested as a computer program) that can be executed by one or more processors.

[0047] Carrier medium - storage media as described above, and physical transmission media such as buses, networks and / or other physical transmission media for transmitting signals such as electrical signals, electromagnetic signals or digital signals.

[0048] Programmable hardware elements encompass a variety of hardware devices that include multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can vary from fine-grained (combinatorial logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."

[0049] Computer system – any of various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, networked appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a storage medium.

[0050] A user device (UE) (or “UE equipment”) is any of a variety of computer system devices that are mobile or portable and perform wireless communications. Examples of UE equipment include mobile phones or smartphones (e.g., iPhones). TM Based on Android TMTelephones), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM ), laptops, wearable devices (e.g., smartwatches, smart glasses), PDAs, portable internet devices, music players, data storage devices, or other handheld devices, etc. Generally speaking, the term "UE" or "UE device" can be broadly defined to encompass any electronic device, computing device, and / or telecommunications device (or combination of devices) that is easily transmitted and capable of wireless communication by a user.

[0051] Base station - The term "base station" has the full range of its general meaning and includes at least a wireless communication station that is installed in a fixed location and is used for communication as part of a wireless telephone system or radio system.

[0052] Processing element – ​​refers to various elements or combinations of elements capable of performing the functions of a device such as a user device or cellular network device. Processing elements may include, for example: processors and associated memory, portions or circuitry of individual processor cores, entire processor cores, processor arrays, circuitry such as ASICs (Application-Specific Integrated Circuits), programmable hardware elements such as Field-Programmable Gate Arrays (FPGAs), and any combination thereof.

[0053] A channel is a medium used to transmit information from a transmitter to a receiver. It should be noted that because the characteristics of the term "channel" can vary depending on the wireless protocol, the term "channel" as used herein should be considered in a standard manner consistent with the type of device to which the term is referenced. In some standards, channel width can be variable (e.g., depending on device capabilities, frequency 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 include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0054] Frequency band – The term “frequency band” has the full range of its general meaning and includes at least a segment of spectrum (e.g., radio frequency spectrum) in which a channel is used or reserved for the same purpose.

[0055] Automatic – refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuitry, programmable hardware components, ASICs, etc.) without requiring direct user input to specify or perform the action or operation. Therefore, the term “automatic” contrasts with an operation performed or specified manually by a user, where the user provides input to directly perform the operation. An automatic process can be initiated by user-provided input, but the subsequent actions performed “automatically” are not specified by the user; that is, they are not performed “manually”, where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input specifying information (e.g., by typing information, selecting a checkbox, selecting a radio component, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0056] "Approximately" refers to a value that is close to the correct or precise value. For example, "approximately" can refer to a value within 1% to 10% of the precise (or expected) value. However, it should be noted that the actual threshold (or tolerance) can vary depending on the application. For example, in some implementations, "approximately" may mean within 0.1% of some specified or expected value, while in various other implementations, the threshold may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of the specific application.

[0057] Concurrency refers to the parallel execution or implementation of tasks, processes, or programs in a manner that at least partially overlaps. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0058] Various components can be described as being "configured" to perform one or more tasks. In this context, "configured" is a broad expression generally referring to a "structure" that "has" performing one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured" can be a broad expression generally referring to a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently switched on. Typically, the circuit forming the structure corresponding to "configured" can include hardware circuitry.

[0059] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 U.S.SC §112(f) for that component.

[0060] Figure 1 and Figure 2 -Communication System

[0061] Figure 1 A simplified example wireless communication system according to some implementation schemes is shown. It should be noted that... Figure 1 The system described is merely one example of a possible system, and the features of this disclosure can be implemented in any of a variety of systems as needed.

[0062] As shown in the figure, the example wireless communication system includes a base station 102A, which communicates with one or more user equipments 106A, 106B, etc., to user equipment 106N via a transmission medium. Each of the user equipments may be referred to herein as a "user device" (UE). Therefore, user equipment 106 is referred to as a UE or UE device.

[0063] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (cellular base station), and may include hardware for implementing wireless communication with UE 106A to UE 106N.

[0064] The communication area (or coverage area) of a base station may be referred to as a "cell". Base station 102A and UE 106 can be configured to communicate via a transmission medium using any of a variety of Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if base station 102A is implemented in an LTE environment, its alternative location may be referred to as 'eNodeB' or 'eNB'. Note that if base station 102A is implemented in a 5G NR environment, its alternative location may be referred to as 'gNodeB' or 'gNB'.

[0065] As shown in the figure, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A can facilitate communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various communication capabilities such as voice, SMS, and / or data services.

[0066] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping services to UE 106A-N and similar devices over a geographical area via one or more cellular communication standards.

[0067] Therefore, although base station 102A can act as such Figure 1 The diagram shows the "serving cell" of UEs 106A-N, but each UE 106 may also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B-N and / or any other base stations), which may be referred to as "neighboring cells". Such cells may also facilitate communication between user equipments and / or between user equipments and network 100. These cells may include "macro" cells, "micro" cells, "pecimen" cells, and / or any other cells of various other granularities providing a service area size. For example, in Figure 1 Base stations 102A-B shown can be macro cells, while base station 102N can be micro cells. Other configurations are also possible.

[0068] In some implementations, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a “gNB”. In some implementations, the gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, a gNB cell may include one or more transition and receive points (TRPs). Additionally, a UE capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0069] It should be noted that UE 106 may be able to communicate using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD, etc.), UE 106 may be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, UE 106 may also be configured, or alternatively, to communicate using one or more Global Navigation Satellite Systems (GNSS, such as 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. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0070] Figure 2 A user device 106 (e.g., one of devices 106A to 106N) communicating with base station 102 is shown according to some embodiments. UE 106 may be a device with cellular communication capabilities, such as a mobile phone, handheld device, computer, or tablet computer, or virtually any type of wireless device.

[0071] UE 106 may include a processor configured to execute program instructions stored in memory. UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or additionally, UE 106 may include programmable hardware elements, such as an FPGA (Field Programmable Gate Array) configured to perform any of the method embodiments described herein or any portion thereof.

[0072] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD) or LTE using a single shared radio component and / or GSM or LTE using a single shared radio component. The shared radio component may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Typically, the radio component may include any combination of baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of the receive chain and / or transmit chain among various wireless communication technologies such as those discussed above.

[0073] In some implementations, UE 106 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to use it for communication. As another possibility, UE 106 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 may include shared radio components for communication using either LTE or 5G NR (or LTE or 1xRTT, or LTE or GSM), and separate radio components for communication using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0074] Figure 3 -UE block diagram

[0075] Figure 3 A simplified block diagram of a communication device 106 according to some embodiments is shown. Note that... Figure 3The block diagram of the communication device is merely one example of a possible communication device. According to the implementation, among other devices, the communication device 106 can be a user equipment (UE), 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 computer, notebook computer, or portable computing device), a tablet computer, and / or a combination of devices. As shown, the communication device 106 may include a set of components 300 configured to perform core functions. For example, this set of components may be implemented as a system-on-a-chip (SOC), which may include portions for various purposes. Alternatively, the set of components 300 may be implemented as individual components or groups of components for various purposes. This set of components 300 may be (e.g., communicatively; directly or indirectly) coupled to various other circuitry of the communication device 106.

[0076] For example, communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as connector I / F 320 (e.g., for connection to a computer system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), a display 360 that may be integrated with or external to the communication device 106, and cellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc., and short- to medium-range wireless communication circuitry 329 (e.g., Bluetooth). TM (and WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0077] Cellular communication circuitry 330 may be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 335 and 336 as shown. Short-to-medium-range wireless communication circuitry 329 may also be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 337 and 338 as shown. Alternatively, short-to-medium-range wireless communication circuitry 329 may be coupled (e.g., communicatively grounded; directly or indirectly) to antennas 337 and 338, or as an alternative, to antennas 335 and 336. Short-to-medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may 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.

[0078] In some embodiments, as further described below, the cellular communication circuit 330 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). Furthermore, in some embodiments, the cellular communication circuit 330 may include a single transmit chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component may be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with additional radio components, such as a second radio component that may be dedicated to a second RAT (e.g., 5G NR) and can communicate with the dedicated receive chain and the shared transmit chain.

[0079] The communication device 106 may also include and / or be configured to be used with one or more user interface elements. The user interface elements may include various components such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of the touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of various other components capable of providing information to the user and / or receiving or interpreting user input.

[0080] The communication device 106 may also include one or more smart cards 345 with SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more general purpose integrated circuit cards) 345.

[0081] As shown in the figure, the SOC 300 may include one or more processors 302 and display circuitry 304. The processors execute program instructions for communication device 106, and the display circuitry performs graphics processing and provides display signals to display 360. The one or more processors 302 may also be coupled to a memory management unit (MMU) 340 (which may be configured to receive addresses from the one or more processors 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310)) and / or coupled to other circuitry or devices (such as display circuitry 304, short-to-medium range wireless communication circuitry 329, cellular communication circuitry 330, connector I / F 320, and / or display 360). MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, MMU 340 may be included as part of one or more processors 302.

[0082] As described above, communication device 106 can be configured to communicate using wireless and / or wired communication circuits. Communication device 106 can be configured to perform a method including exchanging communications with a base station to determine one or more scheduling power profiles. In some embodiments, communication with the base station to determine one or more scheduling power profiles may include exchanging one or more Radio Resource Control (RRC) signaling messages. In some embodiments, the one or more scheduling power profiles may not conflict with each other. In some embodiments, the scheduling power profile may specify one or more parameters associated with the communication behavior of communication device 106, such as one or more constraints on the communication behavior of communication device 106 and / or the time slot scheduling of communication by communication device 106. Additionally, the method may include communication device 106 receiving a time slot configuration schedule from the base station. The time slot configuration schedule may be based on at least one of the one or more scheduling power profiles. Furthermore, the method may include communication device 106 performing communication with the base station based on at least one scheduling power profile.

[0083] As described herein, communication device 106 may include hardware and software components for implementing the features described above to transmit a scheduled power profile for power saving to a network. For example, by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium), processor 302 of communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or additionally), processor 302 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or in addition), in conjunction with one or more of other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, processor 302 of communication device 106 may be configured to implement some or all of the features described herein.

[0084] Furthermore, as described herein, processor 302 may include one or more processing elements. Therefore, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 302.

[0085] Furthermore, as described herein, both the cellular communication circuit 330 and the short-to-medium-range wireless communication circuit 329 may include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 330, and similarly, one or more processing elements may be included in the short-to-medium-range wireless communication circuit 329. Therefore, the cellular communication circuit 330 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 330. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 330. Similarly, the short-to-medium-range wireless communication circuit 329 may include one or more ICs configured to perform the functions of the short-to-medium-range wireless communication circuit 329. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-to-medium-range wireless communication circuit 329.

[0086] Figure 4 - Block diagram of a base station

[0087] Figure 4 An example block diagram of a base station 102 according to some implementation schemes is shown. It should be noted that... Figure 4 The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include one or more processors 404 capable of executing program instructions specific to base station 102. One or more processors 404 may also be coupled to a memory management unit (MMU) 440 (which may be configured to receive addresses from one or more processors 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450)) or other circuitry or devices.

[0088] Base station 102 may include at least one network port 470. Network port 470 may be configured to be coupled to a telephone network and provide access rights as described above. Figure 1 and Figure 2 The telephone network described herein includes multiple devices such as UE device 106.

[0089] Network port 470 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as UE device 106. In some cases, network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by a cellular service provider).

[0090] In some implementations, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a “gNB”. In such implementations, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0091] Base station 102 may include at least one antenna 434 and possibly multiple antennas. At least one antenna 434 may be configured to function as a wireless transceiver and may be further configured to communicate with UE device 106 via radio component 430. Antenna 434 communicates with radio component 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. Radio component 430 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0092] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some cases, base station 102 may include multiple radio components that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include LTE radio components for performing communication according to LTE and 5G NR radio components for performing communication according to 5G NR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include multimode radio components capable of performing communication according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0093] As further described herein, BS 102 may include hardware and software components for implementing or supporting embodiments of the features described herein. The processor 404 of base station 102 may be configured to implement or support some or all of the methods described herein, for example, by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium). Alternatively, processor 404 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit) or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 430, 432, 434, 440, 450, 460, 470, the processor 404 of BS 102 may be configured to implement or support some or all of the features described herein.

[0094] Furthermore, as described herein, one or more processors 404 may comprise one or more processing elements. In other words, one or more processing elements may be included in one or more processors 404. Therefore, one or more processors 404 may include one or more integrated circuits (ICs) configured to perform the functions of one or more processors 404. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 404.

[0095] Additionally, as described herein, the radio component 430 may comprise one or more processing elements. In other words, one or more processing elements may be included in the radio component 430. Therefore, the radio component 430 may include one or more integrated circuits (ICs) configured to perform the functions of the radio component 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the radio component 430.

[0096] Figure 5 Block diagram of cellular communication circuit

[0097] Figure 5 A simplified block diagram of an example cellular communication circuit according to some implementation schemes is shown. Note that... Figure 5 The block diagram of the cellular communication circuit is merely one example of a possible cellular communication circuit. According to the implementation, the cellular communication circuit 330 may be included in a communication device such as the communication device 106 described above. As mentioned above, among other devices, the communication device 106 may be a user equipment (UE), 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 computer, notebook computer, or portable computing device), a tablet computer, and / or a combination of these devices.

[0098] Cellular communication circuit 330 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as ( Figure 3 Antennas 335a-b and 336 are shown in the diagram. In some embodiments, the cellular communication circuit 330 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as... Figure 5 As shown, the cellular communication circuit 330 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT, such as LTE or LTE-A, and the modem 520 may be configured for communication according to a second RAT, such as 5G NR.

[0099] As shown, modem 510 may include one or more processors 512 and memory 516 communicating with processors 512. Modem 510 may communicate with radio frequency (RF) front end 530. RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, RF front end 530 may include receiver circuitry (RX) 532 and transmitter circuitry (TX) 534. In some embodiments, receiver circuitry 532 may communicate with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0100] Similarly, modem 520 may include one or more processors 522 and memory 526 communicating with processor 522. Modem 520 may communicate with RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some embodiments, receiving circuitry 542 may communicate with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.

[0101] In some implementations, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 336. Therefore, when cellular communication circuitry 330 receives an instruction to transmit according to a first RAT (e.g., supported by modem 510), switch 570 may be switched to a first state allowing modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 330 receives an instruction to transmit according to a second RAT (e.g., supported by modem 520), switch 570 may be switched to a second state allowing modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).

[0102] In some embodiments, the cellular communication circuit 330 may be configured to perform a method including exchanging communications with a base station to determine one or more scheduling power profiles. In some embodiments, the communication with the base station to determine the one or more scheduling power profiles may include exchanging one or more Radio Resource Control (RRC) signaling messages. In some embodiments, the one or more scheduling power profiles may not conflict with each other. In some embodiments, the scheduling power profile may specify one or more parameters associated with UE communication behavior, such as one or more constraints on UE communication behavior and / or time slot scheduling of UE communication. Additionally, the method may include receiving time slot configuration scheduling from the base station. The time slot configuration scheduling may be based on at least one of the one or more scheduling power profiles. Furthermore, the method may include performing communication with the base station based on at least one scheduling power profile.

[0103] As described herein, modem 510 may include hardware and software components for implementing the features described above or for UL data used in time-division multiplexing NSA NR operation, as well as various other techniques described herein. For example, processor 512 may be configured to implement some or all of the features described herein by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or additionally), processor 512 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or additionally), processor 512 may be configured to implement some or all of the features described herein in conjunction with one or more of other components 530, 532, 534, 550, 570, 572, 335, and 336.

[0104] Furthermore, as described herein, processor 512 may include one or more processing elements. Therefore, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0105] As described herein, modem 520 may include hardware and software components designed to implement the aforementioned features for delivering power-saving scheduled power profiles to the network, as well as various other technologies described herein. For example, processor 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or additionally), processor 522 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or additionally), in conjunction with one or more of other components 540, 542, 544, 550, 570, 572, 335, and 336, processor 522 may be configured to implement some or all of the features described herein.

[0106] Additionally, as described herein, processor 522 may include one or more processing elements. Therefore, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.

[0107] 5G NR architecture with LTE

[0108] In some specific implementations, fifth-generation (5G) wireless communication will initially be deployed in parallel with current wireless communication standards (e.g., LTE). For example, dual connectivity between LTE and the new 5G radio (5G NR or NR) has been designated as part of the initial deployment of NR. Therefore, as... Figure 6A As shown in -B, the Evolved Packet Core (EPC) network 600 can continue to communicate with the current LTE base station (e.g., eNB 602). Furthermore, eNB 602 can communicate with the 5G NR base station (e.g., gNB 604) and can transfer data between the EPC network 600 and gNB 604. Therefore, the EPC network 600 can be used (or reused), and gNB 604 can serve as additional capacity for the UE, for example, to provide increased downlink throughput for the UE. 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.

[0109] Figure 6B The proposed protocol stack for eNB 602 and gNB 604 is shown. As illustrated, eNB 602 may include a Media Access Control (MAC) layer 632 that interfacing with Radio Link Control (RLC) layers 622a-b. RLC layer 622a may also interfacing with Packet Data Convergence Protocol (PDCP) layer 612a, and RLC layer 622b may interfacing with PDCP layer 612b. Similar to the dual connectivity specified in Advanced LTE Release 12, PDCP layer 612a may interfacing with EPC network 600 via Primary Cell Group (MCG) bearer, while PDCP layer 612b may interfacing with EPC network 600 via decoupling bearer.

[0110] Additionally, as shown in the figure, gNB 604 may include a MAC layer 634 that interfaces with RLC layers 624a-b. RLC layer 624a may interface with the PDCP layer 612b of eNB 602 via the X2 interface for information exchange and / or coordination (e.g., UE scheduling) between eNB 602 and gNB 604. Furthermore, RLC layer 624b may interface with PDCP layer 614. Similar to the dual connectivity specified in Advanced LTE Release 12, PDCP layer 614 may interface with EPC network 600 via a secondary cell group (SCG) bearer. Therefore, eNB 602 may be considered the primary node (MeNB), and gNB 604 may be considered the secondary node (SgNB). In some cases, it may be required that the UE maintain connectivity with both the MeNB and the SgNB. In such cases, the MeNB may be used to maintain Radio Resource Control (RRC) connectivity with the EPC, while the SgNB may be used for capacity (e.g., additional downlink and / or uplink throughput).

[0111] 5G Core Network Architecture - Interoperability with Wi-Fi

[0112] In some implementations, access to the 5G core network (CN) can be made via (or through) cellular connections / interfaces (e.g., via 3GPP communication architectures / protocols) and non-cellular connections / interfaces (e.g., non-3GPP access architectures / protocols such as Wi-Fi connections). Figure 7AAn example of a 5G network architecture according to some implementation schemes is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access in a 5G CN. As shown, a user equipment (e.g., UE 106) can access the 5G CN via both a radio access network (RAN, e.g., gNB or base station 604) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to a non-3GPP Interoperability Function (N3IWF) 702 network entity. N3IWF may include a connection to the core access and mobility management function (AMF) 704 of the 5G CN. AMF 704 may include an instance of 5G mobility management (5G MM) functions associated with UE 106. Additionally, the RAN (e.g., gNB 604) may also have a connection to AMF 704. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register access simultaneously via gNB 604 and AP 112. As shown, AMF704 may include one or more functional entities associated with 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 entities may also be supported by the 5G CN's Session Management Functions (SMF) 706a and SMF 706b. AMF 706 may connect to (or communicate with) SMF 706a. Furthermore, gNB 604 may communicate with (or connect to) User Plane Function (UPF) 708a, which may also communicate with SMF 706a. Similarly, N3IWF 702 may communicate with UPF 708b, which may also communicate with SMF 706b. Both UPFs can communicate with data networks (e.g., DN 710a and 710b) and / or the Internet 700 and IMS core network 710.

[0113] Figure 7BAn example of a 5G network architecture according to some implementation schemes is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access and non-3GPP access in a 5G CN. As shown, a user equipment (e.g., UE 106) can access the 5G CN through both a radio access network (RAN, such as gNB or base station 604 or eNB or base station 602) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to the N3IWF 702 network entity. The N3IWF may include a connection to the AMF 704 of the 5G CN. AMF 704 may include an instance of 5G MM functionality associated with UE 106. Additionally, the RAN (e.g., gNB 604) may also have a connection to AMF 704. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register access simultaneously via gNB 604 and AP 112. Additionally, the 5G CN can support dual registration of the UE on both a legacy network (e.g., LTE via base station 602) and a 5G network (e.g., via base station 604). As shown, base station 602 may have connections to both Mobility Management Entity (MME) 742 and Service Gateway (SGW) 744. MME 742 may have connections to both SGW 744 and AMF 704. Furthermore, SGW 744 may have connections to both SMF 706a and UPF 708a. As shown, AMF 704 may include one or more functional entities associated with the 5G CN (e.g., NSSF 720, SMSF 722, AF 724, UDM 726, PCF 728, and / or AUSF 730). Note that UDM 726 may also include Home Subscriber Server (HSS) functionality, and PCF may also include Policy and Charging Rules (PCRF) functionality. It should also be noted that these functional entities can also be supported by the 5G CN's SMF 706a and SMF 706b. The AMF 706 can connect to (or communicate with) the SMF 706a. Furthermore, the gNB 604 can communicate with (or connect to) the UPF 708a, which in turn can communicate with the SMF 706a. Similarly, the N3IWF702 can communicate with the UPF 708b, which in turn can communicate with the SMF 706b. Both UPFs can communicate with data networks (e.g., DN710a and 710b) and / or the Internet 700 and IMS core network 710.

[0114] It should be noted that, in various implementations, one or more of the aforementioned network entities may be configured to perform a method of scheduling the UE based on a scheduling power profile, which may specify one or more parameters associated with the UE's communication behavior, such as one or more constraints on the UE's communication behavior and / or the time slot scheduling of UE communication, as further described herein.

[0115] Figure 8 An example of a baseband processor architecture for a UE (e.g., UE 106) according to some implementation schemes is shown. As described above, Figure 8 The baseband processor architecture 800 described herein can be implemented on one or more radio components (e.g., radio components 329 and / or 330) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access stratum 810 may include a 5G NAS 820 and a traditional NAS 850. The traditional NAS 850 may include a communication connection with a traditional access stratum (AS) 870. The 5G NAS 820 may include communication connections with a 5G AS 840 and a non-3GPP AS 830, as well as a Wi-Fi AS 832. The 5G NAS 820 may include functional entities associated with both access strata. Therefore, the 5G NAS 820 may include multiple 5G MM entities 826 and 828 and 5G session management (SM) entities 822 and 824. The traditional AS 850 may include functional entities such as Short Message Service (SMS) entity 852, Evolved Packet System (EPS) Session Management (ESM) entity 854, Session Management (SM) entity 856, EPS Mobility Management (EMM) entity 858, and Mobility Management (MM) / GPRS Mobility Management (GMM) entity 860. Furthermore, the traditional AS 870 may include functional entities such as LTE AS 872, UMTS AS 874, and / or GSM / GPRS 876.

[0116] Therefore, the baseband processor architecture 800 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access) networks. It's important to note that, as shown in the figure, the 5G MM can maintain separate connection management and registration management state machines for each connection. Furthermore, a device (e.g., UE 106) can register to a single PLMN (e.g., a 5G CN) using both 5G cellular and non-cellular access. Additionally, a device can be in a connected state in one access and an idle state in another, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.

[0117] It should be noted that, in various implementations, one or more of the above-described elements may be configured to perform a method of scheduling the UE based on a scheduling power profile, which may specify one or more parameters associated with the UE's communication behavior, such as one or more constraints on the UE's communication behavior and / or the time slot scheduling of UE communication, as further described herein.

[0118] UE scheduling power profile

[0119] In the current implementation of the 5G New Radio (5G NR) standard, the UE can be configured to periodically monitor the Physical Downlink Control Channel (PDCCH), for example... Figure 9A As shown in the figure, the UE can monitor the PDCCH every five time slots 902, and if the UE has no pending data, it can enter a low-power mode to reduce power consumption when not monitoring the PDCCH in time slot 904. In some implementations, a search space configuration can be enabled to allow the UE to periodically monitor the PDCCH. The UE's power consumption during periodic PDCCH monitoring is determined by... Figure 9B As shown in the figure, when no PDCCH is monitored, the UE can have extremely low power consumption; however, power consumption can increase linearly before the monitoring period (e.g., power ramp 910), maintain maximum power consumption for a period of time before, during, and after the monitoring period (e.g., maximum power level 912), and then decrease linearly after the monitoring period ends (e.g., power ramp 914). For example, when the UE is in time slot N (e.g., Figure 9A When receiving data in time slot N, the UE will wake up before time slot N to prepare for data reception. During wake-up, the UE may consume power (e.g., power ramp 910) to prepare (or reinitialize / start) its clock, set its voltage configuration, warm up the UE's radio frequency integrated circuit (RFIC), lock the phase-locked loop (PLL), etc. After receiving data in time slot N, the UE's modem may perform decoding and a series of actions for signal decoding, and shut down UE components to reduce power consumption. For example, the UE modem may shut down the RFIC, perform automatic gain control (AGC), update the time tracking loop (TTL) and / or frequency tracking loop (FTL), perform channel estimation, and / or perform data decoding. Again, when the UE receives data in time slot N (e.g., ... Figure 9AWhen transmitting data in time slot 906, the UE will wake up before time slot N to prepare for data transmission. During wake-up, similar to when the UE is preparing to receive data, the UE may consume power (e.g., power ramp 910) to prepare (or reinitialize / start) its clock, warm up the UE's RFIC, lock the phase-locked loop (PLL), encode data, etc. After time slot N, the UE may consume power (e.g., power ramp 914) to turn off the RFIC. Therefore, turning components on and off to receive and / or transmit data consumes power (specifically, the RFIC ramp rise and ramp fall).

[0120] The embodiments described herein disclose systems and methods for reducing power consumption during wake-up and shutdown periods associated with periodic monitoring of the PDCCH. For example, in some embodiments, the UE may notify the base station (e.g., gNB) of scheduling constraints via a scheduling profile such as a scheduling power profile. Figure 10D , Figure 11D , Figure 12D and Figure 13D Power savings are illustrated for various transmission and / or reception scenarios. In some implementations, the UE may transmit acknowledgments, transmit data on the PUSCH, and / or transmit various other data and / or control information. In some implementations, the UE may receive data on the PDCCH and / or PDSCH.

[0121] Figure 10D The diagram illustrates the relationship between [various implementation schemes] and [other schemes]. Figures 10A to 10C The current implementation shown represents a power saving compared to performing two transmissions. Specifically, Figures 10A to 10C The power consumed in the first transmission is shown. Figure 10A ), the power consumed in the second transmission ( Figure 10B ) and the total power consumed in the two transmissions ( Figure 10C As shown in the figure, for each transmission, the UE consumes power to prepare for the transmission, performs the transmission, and then powers off after the transmission. However, according to some implementation schemes and as... Figure 10D As shown, when the UE can schedule transmissions back-to-back, the UE can avoid power outages after the first transmission and avoid power-on for the second transmission, thus saving additional power compared to the current implementation.

[0122] Figure 11D The diagram illustrates the relationship between [various implementation schemes] and [other schemes]. Figures 11A to 11C The current implementation shown represents a power saving compared to performing two receptions. Specifically, Figures 11A to 11C The power consumed during the first reception is shown. Figure 11A ), the power consumed in the second reception ( Figure 11B ) and the total power consumed by the two receptions ( Figure 11CAs shown in the figure, for each reception, the UE consumes power to prepare for reception, performs reception, and then powers off after reception. However, according to some implementation schemes and as... Figure 11D As shown, when the UE can schedule reception back-to-back, the UE can avoid power outages after the first reception and avoid power-on for the second reception, thus saving additional power compared to the current implementation.

[0123] Figure 12D The diagram illustrates the relationship between [various implementation schemes] and [other schemes]. Figures 12A to 12C The current implementation shown offers power savings compared to transmitting and then receiving. Specifically, Figures 12A to 12C The power consumed by the transmission is shown. Figure 12A ), power consumed by receiving ( Figure 12B ) and the total power consumed in transmission and reception ( Figure 12C As shown in the figure, for transmission and reception, the UE consumes power to prepare for transmission / reception, performs transmission / reception, and then powers off after transmission / reception. However, according to some implementation schemes and as... Figure 12D As shown, when the UE can schedule transmission and reception back-to-back, the UE can avoid power outages after transmission and avoid re-powering on for reception, thus saving additional power compared to the current implementation.

[0124] Figure 13D The diagram illustrates the relationship between [various implementation schemes] and [other schemes]. Figures 13A to 13C The current implementation shown offers power savings compared to receiving and then transmitting. Specifically, Figures 13A to 13C The power consumed by the receiver is shown. Figure 13A ), power consumed during transmission ( Figure 13B ) and the total power consumed in receiving and transmitting ( Figure 13C As shown in the figure, for transmission and reception, the UE consumes power to prepare for transmission / reception, performs transmission / reception, and then powers off after transmission / reception. However, according to some implementation schemes and as... Figure 13D As shown, when the UE can schedule reception and transmission back-to-back, the UE can avoid power outages after reception and avoid power-on for transmission, thus saving additional power compared to the current implementation.

[0125] Figure 14 A block diagram illustrating an example of a process for determining a UE's scheduling profile, according to some implementation schemes, is shown. Among other things, Figure 14The process shown can be used in conjunction with any of the systems or devices shown in the accompanying figures. In various embodiments, some of the process elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional process elements may also be executed as needed. As shown, the process can operate as follows.

[0126] At 1402, a UE such as UE 106 may propose one or more scheduling profiles, such as one or more scheduling power profiles, to a base station such as base station 102 (which may be configured as a gNB, such as gNB 604). It should be noted that if a UE proposes more than one scheduling power profile, the scheduling power profiles may not conflict with each other. In some embodiments, the proposal may be transmitted via a Radio Resource Control (RRC) signaling message. In some embodiments, the scheduling power profile may include one or more (or a set of) parameters and / or constraints for system configuration. These parameters (or constraints) may restrict network scheduling to a specific configuration. In some embodiments, the scheduling power profile may include a set of other scheduling power profiles. In some embodiments, such as Figure 15 As shown, the scheduling power profile can specify specific UE behaviors or sets of behaviors. For example, such as Figure 15 As shown, configuration file P1 can specify a configuration file for delayed acknowledgments (ACKs) with PDCCH monitoring. Similarly, configuration file P2 can specify a configuration file for delayed PUSCH scheduling with PDCCH monitoring. Furthermore, configuration file P3 can specify a configuration file for cross-slot scheduling with PDCCH monitoring; configuration file P4 can specify a configuration file for the large bandwidth portion (BWP) of big data packet scheduling; configuration file P5 can specify a configuration file for self-contained slot scheduling; configuration file P10 can specify a configuration file for power saving, such as a set of configuration files including any, some, or all of configuration files P1, P2, and / or P3; configuration file P11 can specify a configuration file for high throughput, such as a set of configuration files including any, some, or all of configuration files P1 and / or P4; configuration file P14 can specify a configuration file for low latency, such as a set of configuration files including at least configuration file P5; configuration file P15 can specify a configuration file for high system capacity; configuration file P14 can specify a configuration file for small data traffic, such as voice data and / or SMS data; configuration file P20 can specify a configuration file for PDCCH monitoring periods.

[0127] In some implementations, the scheduling power profile may include one or more parameters to specify the profile. For example, parameters may include a set of values ​​for search space monitoring periodicity. Alternatively, parameters may include a set of configurable values ​​and / or constraints for K0, where K0 is defined as the number of time slots (e.g., from 0 to n) between time slots scheduled for PDCCH and time slots scheduled for PDSCH. Another example is that parameters may include a set of configurable values ​​and / or constraints for K1, where K1 is defined as the number of time slots (e.g., from 0 to n) between time slots scheduled for PDSCH and time slots scheduled for acknowledgment. Yet another example is that parameters may include a set of configurable values ​​and / or constraints for K2, where K2 is defined as the number of time slots (e.g., from 0 to n) between time slots scheduled for PDCCH and time slots scheduled for PUSCH. Additionally, parameters may include minimum and / or maximum bandwidth values ​​and / or constraints in the BWP, a set of supported multiple-input multiple-output (MIMO) layers, search space index, control resource set (CORESET) index, BWP index, secondary cell (Scell) index, maximum number of Scells, DRX configuration, etc. It should be noted that in some implementations, different configuration files may include different parameters and / or constraints. In other words, a first configuration file may include the above parameters and a first combination of other parameters, and a second configuration file may include a second combination of the above parameters.

[0128] Figure 16 Example parameter sets for various configuration files according to some implementation schemes are shown. As shown, configuration file P1 may include various parameters for supporting delayed ACKs with subsequent PDCCH monitoring, such as a first parameter p, where p specifies the search space monitoring periodicity, and a second parameter defining the relationship between K0, K1, and p. Additionally, configuration file P2 may include various parameters for supporting delayed PUSCHs with subsequent PDCCH monitoring, such as a first parameter p, where p specifies the search space monitoring periodicity, and a second parameter defining the relationship between K2 and p. Furthermore, configuration file P3 may include various parameters for supporting delayed cross-slot scheduling with subsequent PDCCH monitoring, such as a first parameter p, where p specifies the search space monitoring periodicity, a second parameter defining the relationship between K0 and p, and a third parameter specifying the value of K1. Additionally, configuration file P4 may include various parameters for supporting low traffic rates, such as supported BWPs, supported search space indices, supported MIMO layers, supported K0, K1, and K2 values, supported Scell ​​indices, supported number of S cells, etc.

[0129] return Figure 14At 1404, the base station may determine whether to accept a scheduling proposal (e.g., one or more scheduling power profiles proposed by the UE at 1402). This determination may be based at least in part on network scheduling constraints, such as whether the base station has pending data from the UE, whether the base station has previously accepted a scheduling proposal that conflicts with the UE's proposal, channel conditions, etc. (from the UE and / or from other UEs served by the base station). If the base station accepts the scheduling proposal, the process may continue at 1410. Alternatively, if the base station does not accept the scheduling proposal, the process may continue at 1406.

[0130] At 1406, if the base station determines that it does not accept the scheduling proposal, it may transmit a counterproposal to the UE. In response, at 1408, the base station and the UE may negotiate (e.g., by exchanging one or more additional proposals) to determine a scheduling power profile (or multiple scheduling power profiles) for UE communication. It should be noted that the UE and the base station may agree on more than one scheduling power profile, as long as the multiple profiles do not conflict with each other. In other words, in some implementations, the base station (network) may configure multiple profiles for the UE. In some implementations, one or more scheduling power profiles may be valid, wherein the valid profile may be the profile currently being used between the base station and the UE.

[0131] At 1410, the UE and the base station can communicate based on at least one of an agreed-upon scheduling power profile (e.g., an effective profile). For example, if the first profile specifies UE behavior during transmission acknowledgment (ACK) while performing PDCCH monitoring, the base station can schedule ACKs in time slots continuous with PDCCH monitoring based on the search space monitoring periodicity included in the first profile, as referenced below. Figure 17 Furthermore, similarly, if the second profile specifies UE behavior when transmitting on PUSCH while performing PDCCH monitoring, the base station can schedule PUSCH transmissions in time slots continuous with PDCCH monitoring based on the search space monitoring periodicity included in the second profile, for example, as referenced below. Figure 18 Furthermore, if the third profile specifies UE behavior for cross-slot scheduling while performing PDCCH monitoring, the base station can schedule UE transmission and reception based on parameters included in the third profile, as shown in the following reference. Figure 19 Furthermore, if the fourth profile specifies a self-contained time slot, the base station can schedule UE transmission and reception based on parameters included in the fourth profile, as shown in the following reference. Figure 20 Further details are provided.

[0132] Figure 17An example of delayed acknowledgment with subsequent PDCCH monitoring is shown according to some implementation schemes. For example, if we assume that a UE such as UE 106 transmits an acknowledgment (ACK) in the uplink (UL) and monitors the PDCCH at similar timing, the network (e.g., base station 102, gNB 604) can schedule (e.g., partly based on an agreed scheduling power profile) ACK transmission 1708 exactly before the scheduled PDCCH monitoring 1702 occurs, such that UE transmission and UE reception can occur in consecutive (e.g., back-to-back) time slots. This scheduling scheme allows the UE to save power by avoiding ramp-down (e.g., after ACK transmission) and ramp-up (e.g., before scheduled PDCCH monitoring 1702). Figure 17 As shown, the UE can be configured to monitor the PDCCH every 5 time slots. Therefore, if the UE receives the PDSCH in time slot n (e.g., schedules the PDSCH to the UE at 1706), the UE will typically transmit the corresponding ACK in time slot n+1. However, in some implementations, the scheduling power profile can delay the corresponding ACK to time slot n+4, as shown, thereby allowing the UE to save power by avoiding RFIC ramp-down and RFIC ramp-up. It should be noted that the UE may not monitor the PDCCH at time slot 1704. It should also be noted that the scheduling power profile can be determined at least in part based on communication configuration conditions and / or UE constraints. Therefore, according to… Figure 17 For example, communication configuration conditions may include a UE configured to have at least a PDCCH monitoring period p, where p defines the number of time slots between PDCCH monitoring sessions and p is greater than 1. UE constraints can be back-to-back (or consecutive) or very close (e.g., one time slot interval) ACK and PDCCH monitoring. In other words, when a UE is configured to monitor PDCCH in time slot n, ACKs for PDCCH can be scheduled one time slot before PDCCH monitoring (e.g., time slot n-1) so that transmission (ACK) and reception (PDCCH monitoring) can occur without RFIC ramp-down and RFIC ramp-up in between. Therefore, if such a scheduling power profile is enabled (e.g., the RRC parameter PS_ACK_Schedule is set to "true" or "1"), the network can make scheduling decisions (e.g., ACK transmission timing) to satisfy UE constraints.

[0133] Figure 18An example of a delayed PUSCH with subsequent PDCCH monitoring is shown according to some implementation schemes. For example, if we assume that a UE such as UE 106 transmits a PUSCH while performing PDCCH monitoring, the network (e.g., base station 102, gNB 604) can schedule (e.g., partly based on an agreed scheduling power profile) the PUSCH 1808 to be transmitted in a time slot immediately preceding the scheduled PDCCH monitoring time slot 1802, allowing the UE to transmit and receive in consecutive (back-to-back) time slots. This scheduling scheme allows the UE to save power by avoiding ramp-down (e.g., after transmission on the PUSCH) and ramp-up (e.g., before scheduled PDCCH monitoring). Figure 18 As shown, the UE can be configured to monitor the PDCCH every 5 time slots. Therefore, if the UE is scheduled to transmit the PUSCH in time slot n+4 and monitor the PDCCH in the next time slot (e.g., in time slot n+5), the UE can save power by avoiding RFIC ramp-down and RFIC ramp-up. It should be noted that the UE may not monitor the PDCCH in time slot 1804. It should also be noted that the scheduling power profile can be determined at least in part based on communication configuration conditions and / or UE constraints. Therefore, according to... Figure 18 For example, communication configuration conditions may include a UE configured to have at least a PDCCH monitoring period p, where p defines the number of time slots between PDCCH monitoring sessions and p is greater than 1. UE constraints may be back-to-back (or consecutive) PUSCH transmissions and PDCCH monitoring. In other words, when a UE is configured to monitor the PDCCH in time slot n, a PUSCH transmission may be scheduled one time slot prior to the PDCCH monitoring (e.g., time slot n-1) such that transmission (PUSCH) and reception (PDCCH monitoring) can occur without RFIC ramp-down and RFIC ramp-up in between. Therefore, if such a scheduling power profile is enabled (e.g., the RRC parameter PS_PUSCH_Schedule is set to "true" or "1"), the network can make scheduling decisions (e.g., PUSCH transmission timing) to satisfy UE constraints.

[0134] Figure 19An example of delayed cross-slot scheduling with subsequent PDCCH monitoring is shown according to some implementation schemes. For example, if we assume that a UE such as UE 106 is receiving on PDSCH while performing PDCCH monitoring 1902, the network (e.g., base station 102, gNB 604) can schedule (e.g., in part based on an agreed scheduling power profile) PDSCH reception 1906 and ACK transmission 1908 in the slot immediately preceding the scheduled PDCCH monitoring slot 1902, allowing the UE to transmit and receive in consecutive (back-to-back) slots. This scheduling scheme allows the UE to save power by avoiding sloping downscaling (e.g., after transmission on PUSCH) and sloping upscaling (e.g., before scheduled PDCCH monitoring). Note that the UE may not monitor the PDCCH at slot 1904. It should also be noted that when the UE only receives on the PDCCH, it can use narrowband (NB). However, if the UE also receives on the PDSCH, it can open its radio bandwidth to a wider bandwidth (WB) to receive data on the PDSCH. Therefore, to take advantage of bandwidth adaptability with transmit-receive alignment, PDSCH and ACK can be scheduled in the time slot immediately preceding the scheduled PDCCH monitoring. Figure 19 As shown, the UE can be configured to monitor the PDCCH every 3 time slots. Therefore, if the UE is scheduled to receive on the PDSCH in time slot n+2 and the ACK for PDCCH monitoring is delayed to time slot n+2, the UE can monitor the PDCCH in the next time slot (e.g., in time slot n+3), thereby allowing the UE to save power by avoiding RFIC ramp-down and RFIC ramp-up while utilizing bandwidth adaptability. It should be noted that the scheduling power profile can be determined at least in part based on communication configuration conditions and / or UE constraints. Therefore, according to... Figure 19For example, communication configuration conditions may include the UE being configured to have at least a PDCCH monitoring period p, where p defines the number of time slots between PDCCH monitoring sessions and p is greater than 1, and cross-time slot scheduling is enabled. UE constraints may be K0>0 (which allows the UE to monitor PDCCH with a narrow BWP and receive PDSCH with a wide BWP) and K1=0 (which ensures that PDSCH reception and ACK transmission occur in common (same) time slots), where K0 defines the number of time slots between the time slots scheduled for PDCCH and the time slots scheduled for PDSCH (e.g., from 0 to n), and K1 defines the number of time slots between the time slots scheduled for PDSCH and the time slots scheduled for acknowledgment (e.g., from 0 to n). In other words, when a UE is configured to monitor the PDCCH in slot n, PDSCH reception and ACK transmission can be scheduled one slot prior to PDCCH monitoring (e.g., slot n-1), allowing reception (PDSCH) / transmission (ACK) and reception (PDCCH monitoring) to occur without RFIC ramp-down and ramp-up in between. Therefore, if such a scheduling power profile is enabled (e.g., the RRC parameter PS_K1_equal_0 is set to "true" or "1"), the network can make scheduling decisions (e.g., ACK transmission timing and PDSCH reception) to satisfy UE constraints.

[0135] Figure 20 An example of self-contained time slot scheduling with subsequent PDCCH monitoring is shown according to some implementation schemes. For example, if it is assumed that a UE such as UE 106 is receiving on PDSCH while performing PDCCH monitoring 2002, the network (e.g., base station 102, gNB 604) can schedule (e.g., in part based on an agreed scheduling power profile PDSCH reception 2006 and ACK transmission 2008) within a time slot with scheduled PDCCH monitoring 2002, allowing the UE to transmit and receive in a single time slot. This scheduling scheme allows the UE to save power by avoiding ramp-down (e.g., after receiving on PDCCH and after receiving PDSCH) and ramp-up (e.g., before receiving the scheduled PDSCH and before sending ACK). Figure 20 As shown, the UE can be configured to monitor the PDCCH every 3 time slots. Therefore, if the UE is scheduled to receive on the PDSCH in time slot n, the PDSCH ACK is also scheduled in time slot n. This scheme allows the UE to save power by avoiding RFIC ramp-down and RFIC ramp-up. Note that the UE may not monitor the PDCCH in time slot 2004. It should also be noted that the scheduling power profile can be determined at least in part based on communication configuration conditions and / or UE constraints. Therefore, according to... Figure 20For example, communication configuration conditions may include the UE being configured with at least a PDCCH monitoring period p, where p defines the number of time slots between PDCCH monitoring sessions and p is greater than 1, and same time slot scheduling is enabled. UE constraints may be K0 = 0 (which allows the UE to monitor a PDCCH with a narrow BWP and receive a PDSCH with a wide BWP) and K1 = 0 (which ensures that PDSCH reception and ACK transmission occur in a common (same) time slot), where K0 defines the number of time slots between the time slots scheduled for PDCCH and the time slots scheduled for PDSCH (e.g., from 0 to n), and K1 defines the number of time slots between the time slots scheduled for PDSCH and the time slots scheduled for acknowledgment (e.g., from 0 to n). In other words, when a UE is configured to monitor the PDCCH in slot n, PDSCH reception and ACK transmission can be scheduled within a single slot (e.g., slot n) with PDCCH monitoring, allowing reception (PDSCH) / transmission (ACK) and reception (PDCCH monitoring) to occur without RFIC ramp-down and RFIC ramp-up in between. Therefore, if such a scheduling power profile is enabled (e.g., the RRC parameter K0_K1_equal_0 is set to "true" or "1"), the network can make scheduling decisions (e.g., ACK transmission timing and PDSCH reception) to satisfy UE constraints.

[0136] As described above, in some embodiments, one or more profiles can be effectively used (e.g., configured for) data transmission between a UE (such as UE 106) and a base station (network) (such as base station 102, gNB 604). In some embodiments, the profile can be dynamically changed (or switched), for example, in response to an increase and / or decrease in traffic arrival rate, a change in traffic latency requirements, a change in power consumption requirements, etc. In some embodiments, dynamic changes can be triggered via explicit signaling between the network and the UE. For example, the network can send an explicit signal to the UE to change the valid profile to be used for data transmission. Alternatively, the UE can send an explicit signal to the network to request a change to the valid profile to be used for data transmission. In some embodiments, dynamic changes can be triggered based on a timer (additionally and / or alternatively). For example, the valid profile to be used for data transmission can be changed based on timer operation.

[0137] In some implementations, the network (e.g., gNB 604, base station 102) may indicate a profile to a UE such as UE 106 via signaling using downlink control information (DCI), media access control (MAC) control element (CE), and / or radio resource control (RRC) signaling. For example, the network may transmit a signal (e.g., including indications in DCI, MAC CE, and / or RRC signaling) that instructs the UE to use a high-throughput profile when there is a large amount of data to be delivered to the UE. As another example, the network may transmit a signal (e.g., including indications in DCI, MAC CE, and / or RRC signaling) that instructs the UE to use a power-saving profile when the traffic arrival rate drops below a threshold. Yet another example is that the network may transmit Layer 1 (L1) signals to instruct the UE to use a low-latency profile when supported traffic requires low latency.

[0138] In some implementations, the UE may send a profile change request signal to the network. For example, when the UE knows that downlink file transfer has been completed and may want to switch to a power-saving profile. In other words, in response to the completion of downlink file transfer, the UE may request a profile change to the power-saving profile.

[0139] In some implementations, profile changes may be based at least in part on timer operations. For example, a default profile may be configured. Additionally, timers may be defined (e.g., ProfileActiveTimer timers). Timers may be started, restarted, and / or reset when the network activates a new set of profiles. Alternatively, timers may be reset based on conditions. For example, in some implementations, conditions may include a data arrival rate exceeding a threshold, the number of PDSCH slots scheduled for a specified number of slots exceeding a threshold, and so on. In some implementations, when a timer expires, the currently active profile may be deactivated (disabled), and the default profile may be activated (enabled). In some implementations, the default profile may be updated periodically via the network, for example.

[0140] Other implementation plans

[0141] In some implementations, one approach may include user equipment such as UE 106:

[0142] Exchange communications with the base station to determine one or more scheduling profiles, such as one or more scheduling power profiles, wherein the scheduling power profile specifies one or more parameters and / or one or more constraints on the UE's communication behavior;

[0143] Scheduled time slots are received based on at least one of one or more scheduling power profiles; and

[0144] Communication with the base station is performed based on at least one scheduling power profile.

[0145] In some implementations, communication with a base station to determine one or more scheduling power profiles may include (including) Radio Resource Control (RRC) signaling message exchange.

[0146] In some implementations, one or more scheduling power profiles may not conflict with each other.

[0147] In some implementations, one or more scheduling power profiles may include one or more of the following:

[0148] Configuration file for delayed acknowledgments (ACKs) with physical downlink control channel (PDCCH) monitoring;

[0149] Configuration file for scheduling delayed Physical Uplink Shared Channel (PUSCH) with PDCCH monitoring;

[0150] Configuration file for cross-slot scheduling with PDCCH monitoring;

[0151] Configuration file for the high bandwidth portion (BWP) of big data packet scheduling;

[0152] Configuration file used for self-contained time slot scheduling;

[0153] Configuration file for power saving;

[0154] Configuration files for high throughput;

[0155] Configuration files for low latency;

[0156] Configuration files for high system capacity;

[0157] Configuration files for small data traffic; and / or

[0158] Configuration file used for PDCCH monitoring periods.

[0159] In some implementations, one or more parameters and / or constraints may include one or more of the following:

[0160] The first parameter defines a set of values ​​used for periodicity monitoring of the search space.

[0161] The second parameter is defined as the number of time slots between the receive scheduling time slots on the PDCCH and the receive scheduling time slots on the Physical Downlink Shared Channel (PDSCH).

[0162] The third parameter is defined as the number of time slots between the receive scheduling time slots and the time slots for acknowledgment scheduling on the PDSCH.

[0163] The fourth parameter is defined as the number of time slots between the receive scheduling time slots on the PDCCH and the transmit scheduling time slots on the PUSCH.

[0164] The fifth parameter defines the minimum and / or maximum bandwidth values ​​and / or constraints in the BWP; and / or

[0165] The sixth parameter limits the number of multiple-input multiple-output (MIMO) layers that can be supported.

[0166] In some implementations, one or more scheduling power profiles may include a first profile that constrains the base station to schedule the transmission of acknowledgments of data received on the PDCCH to a first time slot immediately preceding a second time slot scheduled for PDCCH monitoring. In some implementations, the first profile may be indicated via the PS_ACK_Schedule RRC parameter.

[0167] In some implementations, one or more scheduling power profiles may include a second profile that constrains the base station to schedule transmissions on the PUSCH to a third time slot immediately preceding the fourth time slot scheduled for PDCCH monitoring. In some implementations, the second profile may be indicated via the PS_PUSCH_Schedule RRC parameter.

[0168] In some implementations, one or more scheduling power profiles may include a third profile that constrains the base station to schedule the transmission of PDCCH ACKs and reception on the Physical Downlink Shared Channel (PDSCH) across time slots to a fifth time slot immediately preceding the sixth time slot scheduled for PDCCH monitoring. In some implementations, the third profile is indicated via the PS_K1_equal_0RRC parameter.

[0169] In some implementations, one approach may include base stations such as gNB 604 and / or base station 102:

[0170] Exchange communications with user equipment (UE) to determine one or more scheduling profiles, such as one or more scheduling power profiles, wherein the scheduling power profile specifies one or more parameters and / or one or more constraints on UE communication behavior;

[0171] Time slot configuration scheduling is transmitted to the UE based on at least one of one or more scheduling power profiles; and

[0172] Communication with the UE is performed based on at least one scheduling power profile.

[0173] In some implementations, communicating with the UE to determine one or more scheduling power profiles may include (or contain) Radio Resource Control (RRC) signaling message exchange.

[0174] In some implementations, one or more scheduling power profiles may not conflict with each other.

[0175] In some implementations, one or more scheduling power profiles may include one or more of the following:

[0176] Configuration file for delayed acknowledgments (ACKs) with physical downlink control channel (PDCCH) monitoring;

[0177] Configuration file for scheduling delayed Physical Uplink Shared Channel (PUSCH) with PDCCH monitoring;

[0178] Configuration file for cross-slot scheduling with PDCCH monitoring;

[0179] Configuration file for the high bandwidth portion (BWP) of big data packet scheduling;

[0180] Configuration file used for self-contained time slot scheduling;

[0181] Configuration file for power saving;

[0182] Configuration files for high throughput;

[0183] Configuration files for low latency;

[0184] Configuration files for high system capacity;

[0185] Configuration files for small data traffic; and / or

[0186] Configuration file used for PDCCH monitoring periods.

[0187] In some implementations, one or more parameters and / or constraints may include one or more of the following:

[0188] The first parameter defines a set of values ​​used for periodicity monitoring of the search space.

[0189] The second parameter is defined as the number of time slots between the receive scheduling time slots on the PDCCH and the receive scheduling time slots on the Physical Downlink Shared Channel (PDSCH).

[0190] The third parameter is defined as the number of time slots between the receive scheduling time slots and the time slots for acknowledgment scheduling on the PDSCH.

[0191] The fourth parameter is defined as the number of time slots between the receive scheduling time slots on the PDCCH and the transmit scheduling time slots on the PUSCH.

[0192] The fifth parameter defines the minimum and / or maximum bandwidth values ​​and / or constraints in the BWP; and / or

[0193] The sixth parameter limits the number of multiple-input multiple-output (MIMO) layers that can be supported.

[0194] In some implementations, one or more scheduling power profiles may include a first profile that constrains the base station to schedule the transmission of acknowledged data received on the PDCCH to a first time slot immediately preceding a second time slot scheduled for PDCCH monitoring.

[0195] In some implementations, the first configuration file may be indicated via the PS_ACK_Schedule RRC parameter.

[0196] In some implementations, one or more scheduling power profiles may include a second profile that constrains the base station to schedule transmissions on the PUSCH to a third time slot immediately preceding the fourth time slot scheduled for PDCCH monitoring. In some implementations, the second profile may be indicated via the PS_PUSCH_Schedule RRC parameter.

[0197] In some implementations, one or more scheduling power profiles may include a third profile that constrains the base station to schedule the transmission of PDCCH ACKs and reception on the Physical Downlink Shared Channel (PDSCH) across time slots to a fifth time slot immediately preceding the sixth time slot scheduled for PDCCH monitoring. In some implementations, the third profile may be indicated via the PS_K1_equal_0RRC parameter.

[0198] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0199] Embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0200] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system performs a method, such as any method embodiment of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.

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

[0202] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. The present invention is intended that the following claims be interpreted to encompass all such variations and modifications.

Claims

1. A base station, comprising: At least one antenna; At least one radio component coupled to the antenna; and At least one processor coupled to the at least one radio component, wherein the at least one processor is configured to cause the base station to: The system exchanges communications with a user equipment (UE) to determine a scheduling power profile, wherein the communications include sending a proposal from the UE to the base station for the scheduling power profile and the scheduling power profile specifies constraints on the values ​​of K0 and K2, wherein K0 is defined as the number of time slots between the time slots scheduled for the physical downlink control channel (PDCCH) and the time slots scheduled for the physical downlink shared channel (PDSCH), and wherein K2 is defined as the number of time slots between the time slots scheduled for the PDCCH and the time slots scheduled for the physical uplink shared channel (PUSCH); The time slot configuration scheduling is transmitted to the UE based on the scheduling power profile proposed by the UE. as well as Communication with the UE is performed based on the scheduling power profile proposed by the UE.

2. The base station according to claim 1, The communication with the UE for determining the scheduling power profile includes the exchange of Radio Resource Control (RRC) signal messages.

3. The base station according to claim 1, The proposed scheduling power profile includes one or more parameters, and said one or more parameters include one or more of the following: The first parameter defines a set of values ​​used for periodicity monitoring of the search space. The second parameter is defined as the number of time slots between the receive scheduling time slots on the Physical Downlink Control Channel (PDCCH) and the receive scheduling time slots on the Physical Downlink Shared Channel (PDSCH). The third parameter is defined as the number of time slots between the receive scheduling time slots and the time slots for acknowledgment scheduling on the PDSCH. The fourth parameter is defined as the number of time slots between the receive scheduling time slots on the PDCCH and the transmission scheduling time slots on the Physical Uplink Shared Channel (PUSCH). The fifth parameter defines the minimum and / or maximum bandwidth value and / or constraints within the Large Bandwidth Portion (BWP); or The sixth parameter defines the number of supported multiple-input multiple-output (MIMO) layers.

4. The base station according to claim 1, The aforementioned scheduling power profile does not conflict with one or more other scheduling power profiles.

5. The base station according to claim 4, The one or more other scheduling power profiles mentioned above include one or more of the following: Configuration file for delayed acknowledgments (ACKs) with physical downlink control channel (PDCCH) monitoring; Configuration file for scheduling delayed Physical Uplink Shared Channel (PUSCH) with PDCCH monitoring; Configuration file for cross-slot scheduling with PDCCH monitoring; Configuration file for the high bandwidth portion (BWP) of big data packet scheduling; Configuration file used for self-contained time slot scheduling; Configuration file for power saving; Configuration files for high throughput; Configuration files for low latency; Configuration files for high system capacity; Configuration files for small data traffic; or Configuration file used for PDCCH monitoring periods.

6. The base station according to claim 4, The one or more additional scheduling power profiles mentioned above include a configuration file that constrains the base station to schedule the transmission of acknowledgments of data received on the Physical Downlink Control Channel (PDCCH) to a first time slot immediately preceding the second time slot scheduled for PDCCH monitoring. And the configuration file mentioned therein is indicated via radio resource control parameters.

7. The base station according to claim 4, The one or more additional scheduling power profiles include a profile that constrains the base station to schedule transmissions on the Physical Uplink Shared Channel (PUSCH) to a third time slot immediately preceding the fourth time slot scheduled for monitoring the Physical Downlink Control Channel (PDCCH), and the profile is indicated via Radio Resource Control (RRC) parameters.

8. The base station according to claim 4, The one or more additional scheduling power profiles include a profile that constrains the base station to schedule the transmission of acknowledgments for the physical downlink control channel and the reception on the physical downlink shared channel across time slots to a fifth time slot immediately preceding the sixth time slot scheduled for monitoring the physical downlink control channel, and the profile is indicated via radio resource control (RRC) parameters.

9. A device for wireless communication, comprising: Memory; and At least one processor communicating with the memory; The at least one processor is configured to: The system exchanges Radio Resource Control (RRC) messages with the User Equipment (UE) to determine one or more scheduling profiles, wherein the RRC message includes a proposed scheduling power profile sent to the device, and the scheduling power profile specifies constraints on the values ​​of K0 and K2, wherein K0 is defined as the number of time slots between the time slots scheduled for the Physical Downlink Control Channel (PDCCH) and the time slots scheduled for the Physical Downlink Shared Channel (PDSCH), and wherein K2 is defined as the number of time slots between the time slots scheduled for the PDCCH and the time slots scheduled for the Physical Uplink Shared Channel (PUSCH); Based on the proposed scheduling configuration file, instructions are generated to transmit time slot configuration scheduling to the UE; and Communication with the UE is performed based on the proposed scheduling profile.

10. The device according to claim 9, The proposed scheduling power profile includes one or more parameters, and said one or more parameters include one or more of the following: The first parameter defines a set of values ​​used for periodicity monitoring of the search space. The second parameter is defined as the number of time slots between the receive scheduling time slots on the Physical Downlink Control Channel (PDCCH) and the receive scheduling time slots on the Physical Downlink Shared Channel (PDSCH). The third parameter is defined as the number of time slots between the receive scheduling time slots and the time slots for acknowledgment scheduling on the PDSCH. The fourth parameter is defined as the number of time slots between the receive scheduling time slots on the PDCCH and the transmission scheduling time slots on the Physical Uplink Shared Channel (PUSCH). The fifth parameter defines the minimum and / or maximum bandwidth value and / or constraints within the Large Bandwidth Portion (BWP); or The sixth parameter defines the number of supported multiple-input multiple-output (MIMO) layers.

11. The device according to claim 9, The aforementioned scheduling power profile does not conflict with one or more other scheduling power profiles.

12. The device according to claim 11, The one or more other scheduling profiles mentioned above include three or more of the following: Configuration file for delayed acknowledgments (ACKs) with physical downlink control channel (PDCCH) monitoring; Configuration file for scheduling delayed Physical Uplink Shared Channel (PUSCH) with PDCCH monitoring; Configuration file for cross-slot scheduling with PDCCH monitoring; Configuration file for the high bandwidth portion (BWP) of big data packet scheduling; Configuration file used for self-contained time slot scheduling; Configuration file for power saving; Configuration files for high throughput; Configuration files for low latency; Configuration files for high system capacity; Configuration files for small data traffic; or Configuration file used for PDCCH monitoring periods.

13. The device according to claim 11, The one or more other scheduling configuration files mentioned above include: The first configuration file constrains the device to schedule the transmission of acknowledgments of data received on the Physical Downlink Control Channel (PDCCH) to a first time slot immediately preceding the second time slot scheduled for PDCCH monitoring; and The second configuration file constrains the device to schedule transmissions on the Physical Uplink Shared Channel (PUSCH) to the third time slot immediately preceding the fourth time slot scheduled for monitoring the PDCCH.

14. The device according to claim 11, The one or more other scheduling profiles include a first profile that constrains the device to schedule the transmission of acknowledgments for the physical downlink control channel and the reception on the physical downlink shared channel across time slots to a fifth time slot immediately preceding the sixth time slot scheduled for physical downlink control channel monitoring, and wherein the first profile is indicated via RRC parameters.

15. A method for wireless communication, comprising: From base station: Receive a proposed scheduling power profile from the user equipment (UE), wherein the scheduling power profile specifies constraints on the values ​​of K0 and K2, wherein K0 is limited to the number of time slots scheduled for the physical downlink control channel (PDCCH) and the number of time slots scheduled for the physical downlink shared channel (PDSCH), and wherein K2 is limited to the number of time slots scheduled for the PDCCH and the number of time slots scheduled for the physical uplink shared channel (PUSCH); Based on the proposed scheduling power profile, the time slot configuration scheduling is transmitted to the UE; and Communication with the UE is performed based on the proposed scheduling power profile.

16. The method according to claim 15, The proposal for the scheduling power profile is transmitted via Radio Resource Control (RRC) signal messages.

17. The method according to claim 15, The proposed scheduling power profile includes one or more parameters, and said one or more parameters include one or more of the following: The first parameter defines a set of values ​​used for periodicity monitoring of the search space. The second parameter is defined as the number of time slots between the receive scheduling time slots on the Physical Downlink Control Channel (PDCCH) and the receive scheduling time slots on the Physical Downlink Shared Channel (PDSCH). The third parameter is defined as the number of time slots between the receive scheduling time slots and the time slots for acknowledgment scheduling on the PDSCH. The fourth parameter is defined as the number of time slots between the receive scheduling time slots on the physical downlink control channel (PDCCH) and the transmission scheduling time slots on the physical uplink shared channel (PUSCH). The fifth parameter defines the minimum and / or maximum bandwidth value and / or constraints within the Large Bandwidth Portion (BWP); or The sixth parameter defines the number of supported multiple-input multiple-output (MIMO) layers.

18. The method according to claim 15, The proposed scheduling power profile does not conflict with one or more other scheduling power profiles, and said one or more other scheduling power profiles include one or more of the following: Configuration file for delayed acknowledgments (ACKs) with physical downlink control channel (PDCCH) monitoring; Configuration file for scheduling delayed Physical Uplink Shared Channel (PUSCH) with PDCCH monitoring; Configuration file for cross-slot scheduling with PDCCH monitoring; Configuration file for the high bandwidth portion (BWP) of big data packet scheduling; Configuration file used for self-contained time slot scheduling; Configuration file for power saving; Configuration files for high throughput; Configuration files for low latency; Configuration files for high system capacity; Configuration files for small data traffic; or Configuration file used for PDCCH monitoring periods.

19. The method according to claim 18, The one or more other scheduling power profiles mentioned above include at least one of the following: A first configuration file, which constrains the base station to schedule the transmission of acknowledgments of data received on the Physical Downlink Control Channel (PDCCH) to a first time slot immediately preceding a second time slot scheduled for PDCCH monitoring; and The second configuration file constrains the base station to schedule transmissions on the Physical Uplink Shared Channel (PUSCH) to the third time slot immediately preceding the fourth time slot scheduled for PDCCH monitoring.

20. The method according to claim 18, The one or more of the other scheduling power profiles include a first profile that constrains the base station to schedule the transmission of acknowledgments for the physical downlink control channel and the reception on the physical downlink shared channel across time slots to a fifth time slot immediately preceding the sixth time slot scheduled for monitoring the physical downlink control channel, and wherein the first profile is indicated via radio resource control parameters.

Images