Method to request a downlink signal

Abstract

Various aspects of the present disclosure relate to a UE for requesting a downlink (DL) signal, a processor for wireless communication, a network entity, methods, and a computer-readable medium. The UE determines whether at least one trigger condition for a request for a DL signal is satisfied. Based on the determination that at least one trigger condition is satisfied, the UE transmits a request for a DL signal to a network entity. In this way, the UE can request a DL signal on demand, and network energy saving is achieved accordingly.

Description

Technology Field

[0001] The present disclosure relates to wireless communications, and more specifically to a user equipment (UE) for requesting a downlink (DL) signal, a network entity, a processor for wireless communication, methods, and a computer-readable medium. Background Technology

[0002] A wireless communication system may include one or more network communication devices, e.g., base stations, which may be known differently as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device, e.g., a base station, may support wireless communication with one or more user communication devices, which may be known differently as User Equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or similar) or frequency resources (e.g., subcarriers, carriers)). Additionally, a wireless communication system may support wireless communication across various radio access technologies, including 3rd generation (3G) radio access technology, 4th generation (4G) radio access technology, and 5th generation (5G) radio access technology, among other suitable radio access technologies other than 5G (e.g., 6th generation (6G)).

[0003] For network energy saving (NES), it is possible to simplify the network (NW) or configure UEs with fewer SSBs for measurements according to the Rel-19 NES work item description (WID). Then, it can be inferred that measurements can be configured with relatively long reporting cycles. Some methods are listed in the WID to support on-demand synchronization signal / PBCH block (SSB) secondary cell (SCell) operation for UEs in connection modes configured with Carrier Aggregation (CA) for both in-band and cross-band CA. However, additional issues regarding this matter need to be studied.

[0004] The present disclosure relates to a UE for requesting a downlink (DL) signal, a network entity, a processor for wireless communication, methods, and a computer-readable medium.

[0005] In a first embodiment, a UE is provided. The UE comprises a processor and a transceiver coupled to the processor, and the processor is configured to: determine whether at least one trigger condition for a request for a downlink (DL) signal is satisfied; and, based on the determination that at least one trigger condition is satisfied, to transmit a request for a DL signal to a network entity through the transceiver.

[0006] In a second embodiment, a network entity is provided, comprising a processor and a transceiver coupled to the processor, wherein the processor is configured to receive a request for a DL signal from a user device (UE) through the transceiver, and the request for a DL signal is transmitted based on at least one trigger condition being satisfied in the UE.

[0007] In a third embodiment, a processor for wireless communication is provided. The processor includes at least one memory and a controller coupled to at least one memory, and the controller is configured to cause the controller to: determine whether at least one trigger condition for a request for a downlink (DL) signal is satisfied; and, based on the determination that at least one trigger condition is satisfied, to transmit a request for a DL signal to a network entity.

[0008] In a fourth embodiment, a method is provided comprising the steps of: determining whether at least one trigger condition for a request for a downlink (DL) signal is satisfied, as performed by a user device (UE); and transmitting a request for a DL signal to a network entity based on the determination that at least one trigger condition is satisfied.

[0009] In a fifth embodiment, a method performed by a network entity comprises the step of receiving a request for a DL signal from a user device (UE), wherein the request for a DL signal is transmitted based on at least one trigger condition being satisfied in the UE.

[0010] In a sixth embodiment, a computer-readable medium is provided in which instructions are stored, and when the instructions are executed by a processor of the device, the device enables the device to perform a method according to a fourth embodiment or a fifth embodiment of the present disclosure.

[0011] In some implementations of methods, UE, and network entities, the UE may receive from the network entity a configuration of whether or not to allow a request for a DL signal to be triggered.

[0012] In some implementations of the methods, UE, and network entity, at least one trigger condition comprises: a first trigger condition that the UE has low beam quality; a second trigger condition that the timer has expired—the timer is restarted when a request for a DL signal is transmitted—; a third trigger condition that the number or frequency of arrivals of uplink (UL) or DL ​​traffic within a configured time window is equal to or greater than a first threshold; a fourth trigger condition that there is no buffered data on the logical channel; a fifth trigger condition that the volume of buffered data or residual buffered data on the logical channel for UL transmission is greater than a second threshold or less than a third threshold—the third threshold is less than a second threshold—; a sixth trigger condition that the residual packet delay budget (PDB) of the logical channel or each packet associated with the logical channel is greater than a fifth threshold or less than a sixth threshold—the sixth threshold is less than a fifth threshold—; and a seventh trigger condition that the UE performs bandwidth portion (BWP) switching to the BWP associated with the DL signal; or includes one or more of the eighth trigger conditions that the UE performs a BWP switching from a sleep BWP to a non-sleep BWP.

[0013] In some implementations of the methods, UE, and network entity, the UE may determine that a first trigger condition is satisfied if one of the following is satisfied: the quality of the best beam among the configured beams is less than a first configured threshold; the number of beams among the configured beams having a quality less than a second configured threshold is greater than a first configured number; or the number of beams among the configured beams having a quality higher than a third configured threshold is less than a second configured number.

[0014] In some implementations of methods, UEs, and network entities, a request for a DL signal may be used to: transmit or interrupt transmission of an on-demand synchronization signal / PBCH block (SSB) to a secondary cell (SCell); trigger the activation or deactivation of the SCell; or request either the activation or deactivation of the SCell.

[0015] In some implementations of methods, UEs, and network entities, the on-demand SSB may include a configured SSB; an unconfigured SSB; or one of a configured SSB and an unconfigured SSB.

[0016] In some implementations of methods, UEs, and network entities, which on-demand SSB a request is made to may be indicated by the sequence of requests or included in a Media Access Control Information Element (MAC CE) or Radio Resource Control (RRC) message.

[0017] In some implementations of methods, UEs, and network entities, a request for a DL signal may indicate at least one SCell where the DL signal is requested.

[0018] In some implementations of methods, UEs, and network entities, a request for a DL signal may indicate an identifier (ID) of at least one SCell.

[0019] In some implementations of methods, UEs, and network entities, a request for a DL signal may additionally indicate a cell group to which at least one SCell belongs.

[0020] In some implementations of methods, UE, and network entities, a request for a DL signal may include a bitmap displaying at least one SCell from a set of cells configured for the UE.

[0021] In some implementations of methods, UEs, and network entities, SCell may be the default SCell configured for the UE.

[0022] In some implementations of methods, UE, and network entities, after transmitting a request, the UE receives an indication indicating a SCell to which a DL signal is transmitted; and based on the received indication, the UE can receive a DL signal.

[0023] In some implementations of methods, UEs, and network entities, SCell is a cell or a neighbor cell of a cell provided by the network entity.

[0024] In some implementations of methods, UEs, and network entities, the indication further indicates time-frequency resources for the DL signal and the transmission pattern of the DL signal.

[0025] In some implementations of methods, UEs, and network entities, the transmitted DL signal may include at least one of an SSB or a system information block (SIB).

[0026] In some implementations of methods, UEs, and network entities, a request for a DL signal may be transmitted via an uplink signal, a wake-up signal (WUS), or a random access channel (RACH).

[0027] In some implementations of methods, UE, and network entities, the network entity may transmit to the UE a configuration of whether or not to allow a request for a DL signal to be triggered.

[0028] In some implementations of methods, UEs, and network entities, the network entity may, after receiving a request, transmit an indication indicating a SCell to which a DL signal is transmitted. Brief explanation of the drawing

[0029] FIG. 1 illustrates an example of a wireless communication system in which some embodiments of the present disclosure may be implemented. FIG. 2 illustrates an example of a process flow for requesting a downlink signal according to some exemplary embodiments of the present disclosure. FIG. 3 illustrates an example of a device suitable for implementing some embodiments of the present disclosure. FIG. 4 illustrates an example of a processor suitable for implementing some embodiments of the present disclosure. FIG. 5 illustrates a flowchart of a method performed by user equipment according to embodiments of the present disclosure. FIG. 6 illustrates a flowchart of a method performed by a network entity according to embodiments of the present disclosure. Throughout the drawings, identical or similar reference numbers represent identical or similar elements. Specific details for implementing the invention

[0030] Now, the principles of the present disclosure will be described with reference to some embodiments. These embodiments are described merely for illustrative purposes and are intended to help those skilled in the art understand and implement the present disclosure and do not imply any limitation to the scope of the present disclosure. The disclosure described herein may be implemented in various ways other than those described below. In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as generally understood by those skilled in the art to which the present disclosure pertains.

[0031] References to “one embodiment,” “exemplary embodiment,” “embodiment,” “some embodiments,” and similar terms in this disclosure indicate that the described embodiment(s) may include a particular feature, structure, or characteristic, but not that all embodiments must include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment(s). Moreover, where a particular feature, structure, or characteristic is described in relation to an embodiment, it is suggested that implementing such feature, structure, or characteristic in relation to other embodiments is within the knowledge of a person skilled in the art, whether or not explicitly described.

[0032] Additionally, it should be understood that while terms such as "first," "second," or similar are used in this specification to describe various elements, these elements are not limited by these terms. These terms are used merely to distinguish one element from another. For example, without departing from the scope of the embodiments, the first element may also be referred to as the second element, and likewise, the second element may also be referred to as the first element. As used in this specification, the term "and / or" includes any and any combination of one or more of the listed terms. In some examples, values, procedures, or devices may be referred to as "best," "lowest," "highest," "minimum," "maximum," or similar. These descriptions are intended to indicate that a selection may be made among a number of functional alternatives used, and it should be understood that such a selection is not necessarily superior, smaller, higher, or otherwise more desirable than other selections.

[0033] The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include plural forms unless the context clearly indicates otherwise. Furthermore, as used herein, terms such as “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” specify the presence of the mentioned features, elements, components, and / or similar things, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “includes” and variations thereof should be interpreted as open terms meaning “includes but not limited thereto.” The term “based on” should be interpreted as “at least partially based on.” The terms “one embodiment” and “embodiment” should be interpreted as “at least one embodiment.” The term "other embodiment" shall be interpreted as "at least one other embodiment." The use of expressions such as "A and / or B" may mean "A alone," "B alone," or "both A and B." Other explicit or implicit definitions may be included below.

[0034] Aspects of the present disclosure are described in the context of a wireless communication system. FIG. 1 illustrates an example of a wireless communication system (100) in which some embodiments of the present disclosure may be implemented. The wireless communication system (100) may include one or more network entities (102) (also referred to as network equipment (NE)), one or more UEs (104), a core network (106), and a packet data network (108). The wireless communication system (100) may support various radio access technologies. In some implementations, the wireless communication system (100) may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system (100) may be a 5G network, such as an NR network. In other implementations, the wireless communication system (100) may be a combination of a 4G network and a 5G network, or other suitable radio access technology including IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system (100) may support radio access technologies beyond 5G. Additionally, the wireless communication system (100) may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0035] One or more network entities (102) may be distributed across a geographical area to form a wireless communication system (100). One or more of the network entities (102) described herein may be network nodes, base stations, network elements, radio access network (RAN) nodes, base transceiver stations, access points, NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms, may include or be referred to as such. Network entities (102) and UEs (104) may communicate through a communication link (110) which may be a wireless or wired connection. For example, network entities (102) and UEs (104) may perform wireless communication (e.g., receiving signaling, transmitting signaling) through a Uu interface. In a 3GPP non-terrestrial network (NTN), a network entity (102) in the form of a satellite can communicate directly with a UE (104) using an NR / LTE Uu interface. The satellite can be a transparent satellite or a regenerative satellite. In the case of an NTN with a transparent satellite, a base station on Earth can communicate with the UE via the satellite. In the case of an NTN with a regenerative satellite, the base station can be onboard and can communicate directly with the UE.

[0036] A network entity (102) may provide a geographic coverage area (112), and the network entity (102) may support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs (104) within the geographic coverage area (112). For example, the network entity (102) and the UE (104) may support wireless communication of signals related to the services (e.g., voice, video, packet data, messaging, broadcasting, etc.) according to one or more radio access technologies. In some implementations, the network entity (102) may be mobile and may be, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas (112) associated with the same or different radio access technologies may overlap, but different geographic coverage areas (112) may be associated with different network entities (102). The information and signals described herein may be represented using any of several different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout this specification may be represented as voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0037] One or more UEs (104) may be distributed across the geographical area of ​​the wireless communication system (100). The UE (104) may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or any other suitable term. In some implementations, the UE (104) may be referred to as a unit, station, terminal, or client, among other examples. Additionally or alternatively, the UE (104) may be referred to as an Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, among other examples. In some implementations, the UE (104) may be fixed within the wireless communication system (100). In some other implementations, the UE (104) may be mobile within the wireless communication system (100). In some other implementations, the UE (104) may be a UAV UE and may communicate with one or more network entities (102) during flight.

[0038] One or more UEs (104) may be devices having different forms or different capabilities. Some examples of UEs (104) are illustrated in FIG. 1. As illustrated in FIG. 1, the UE (104) may communicate with various types of devices, such as network entities (102), other UEs (104), or network equipment (e.g., a core network (106), a packet data network (108), relay devices, integrated access and backhaul (IAB) nodes, or other network equipment). Additionally, or alternatively, the UE (104) may support communication with other network entities (102) or UEs (104) that can act as relays within the wireless communication system (100).

[0039] The UE (104) may also support direct wireless communication with other UEs (104) via a communication link (114). For example, the UE (104) may support direct wireless communication with other UEs (104) via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link (114) may be referred to as a sidelink. For example, the UE (104) may support direct wireless communication with other UEs (104) via a PC5 interface.

[0040] A network entity (102) may support communication with a core network (106), other network entities (102), or both. For example, a network entity (102) may interface with the core network (106) through one or more backhaul links (116) (e.g., through S1, N2, N2 or other network interfaces). Network entities (102) may communicate with each other through backhaul links (116) (e.g., through X2, Xn or other network interfaces). In some implementations, network entities (102) may communicate directly with each other (e.g., between network entities (102)). In some other implementations, network entities (102) may communicate with each other or indirectly (e.g., through the core network (106)). In some implementations, one or more network entities (102) may include subcomponents such as access network entities, which may be examples of access node controllers (ANCs). The ANC may communicate with one or more UEs (104) through one or more other access network transmitting entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0041] In some implementations, the network entity (102) may be configured as a disaggregated architecture, which may be configured to use protocol stacks that are physically or logically distributed between two or more network entities (102), such as an integrated access backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration overseen by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., Cloud RAN (C-RAN)). For example, the network entity (102) may include one or more of a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-RT RIC, a Non-RT RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0042] The RU may also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmission reception point (TRP). One or more components of network entities (102) within a segregated RAN architecture may be co-located, or one or more components of network entities (102) may be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities (102) of a segregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0043] The functional partitioning between the CU, DU, and RU can be flexible and support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed in the CU, DU, or RU. For example, functional partitioning of the protocol stack can be utilized between the CU and the DU, thereby allowing the CU to support one or more layers of the protocol stack and the DU to support one or more different layers of the protocol stack. In some implementations, the CU can host functions and signaling of higher protocol layers (e.g., Layer 3 (L3), Layer 2 (L2)) (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). A CU may be connected to one or more DUs or RUs, and one or more DUs or RUs may host the functionality and signaling of lower protocol layers, for example, Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer), and each may be at least partially controlled by the CU (160).

[0044] Additionally or alternatively, functional partitioning of the protocol stack may be utilized between the DU and the RU, thereby allowing the DU to support one or more layers of the protocol stack and the RU to support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., through one or more RUs). In some implementations, functional partitioning between the CU and the DU, or between the DU and the RU, may be performed within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer may be performed by the other of the CU, DU, or RU).

[0045] The CU can be functionally further divided into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul communication links or fronthaul communication links may be implemented according to interfaces (e.g., channels) between layers of the protocol stack supported by their respective network entities (102) communicating through such communication links.

[0046] The core network (106) may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network (106) may be an evolved packet core (EPC) or a 5G core (5GC), and may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)), and a user plane entity that routes packets or interconnects them to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, a control plane entity can manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.), for one or more UEs (104) served by one or more network entities (102) associated with a core network (106).

[0047] The core network (106) may communicate with the packet data network (108) through one or more backhaul links (116) (e.g., through S1, N2, N2 or other network interfaces). The packet data network (108) may include an application server (118). In some implementations, one or more UEs (104) may communicate with the application server (118). The UE (104) may establish a session with the core network (106) (e.g., a protocol data unit (PDU) session or similar) through a network entity (102). The core network (106) may route traffic (e.g., control information, data, and similar) between the UE (104) and the application server (118) using the established session (e.g., an established PDU session). A PDU session may be an example of a logical connection between a UE (104) and a core network (106) (e.g., one or more network functions of the core network (106)).

[0048] In a wireless communication system (100), network entities (102) and UEs (104) can perform various operations (e.g., wireless communications) using the resources of the wireless communication system (100) (e.g., time resources (e.g., symbols, slots, subframes, frames, or similar) or frequency resources (e.g., subcarriers, carriers)). In some implementations, network entities (102) and UEs (104) may support different resource structures. For example, network entities (102) and UEs (104) may support different frame structures. In some implementations, for example in 4G, network entities (102) and UEs (104) may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, network entities (102) and UEs (104) can support various frame structures (i.e., multiple frame structures). Network entities (102) and UEs (104) can support various frame structures based on one or more numerologies.

[0049] One or more numerologies may be supported in a wireless communication system (100), and the numerologies may include subcarrier spacing and cyclic prefixes. A first numerology (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may use one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a general cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a general cyclic prefix. A fifth numerology (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a general cyclic prefix.

[0050] The time intervals of a resource (e.g., a communication resource) can be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, 10 milliseconds (ms). In some implementations, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a duration, for example, 1 ms. In some implementations, each frame may have the same duration. In some implementations, each subframe within a frame may have the same duration.

[0051] Additionally or alternatively, the time intervals of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may contain a number (e.g., a large number) of slots. The number of slots within each subframe may also depend on one or more numerologies supported by the wireless communication system (100). For example, the first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with their respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may each use a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and sixteen slots per subframe. Each slot may contain a number (e.g., a large number) of symbols (e.g., OFDM symbols). In some implementations, the number of slots per subframe (e.g., quantity) may depend on the numerology. For a standard cyclic prefix, a slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to 60 kHz subcarrier spacing), a slot may contain 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for the standard cyclic prefix and the extended cyclic prefix may depend on the numerology. It should be understood that a reference to a first numerology (e.g., μ=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0052] In a wireless communication system (100), the electromagnetic (EM) spectrum may be divided into various classes, frequency bands, frequency channels, etc. based on frequency or wavelength. For example, the wireless communication system (100) may support one or more operating frequency bands such as frequency range designations FR1 (410 MHz-7.125 GHz), FR2 (24.25 GHz-52.6 GHz), FR3 (7.125 GHz-24.25 GHz), FR4 (52.6 GHz-114.25 GHz), FR4a or FR4-1 (52.6 GHz-71 GHz), and FR5 (114.25 GHz-300 GHz). In some implementations, network entities (102) and UEs (104) may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by network entities (102) and UEs (104) among other equipment or devices for cellular communication traffic (e.g., control information, data). In some implementations, FR2 may be used by network entities (102) and UEs (104) among other equipment or devices for short-range, high data rate capabilities.

[0053] FR1 may be associated with one or more numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology including 15 kHz subcarrier spacing (e.g., μ=0); a second numerology including 30 kHz subcarrier spacing (e.g., μ=1); and a third numerology including 60 kHz subcarrier spacing (e.g., μ=2). FR2 may be associated with one or more numerologies (e.g., at least two numerologies). For example, FR2 may be associated with a third numerology including 60 kHz subcarrier spacing (e.g., μ=2); and a fourth numerology including 120 kHz subcarrier spacing (e.g., μ=3).

[0054] FIG. 2 illustrates an example of a process flow for requesting a downlink (DL) signal according to some exemplary embodiments of the present disclosure. The process flow (200) may involve a UE (201) and a network entity (e.g., a base station) (202). The process flow (200) may be applied to a wireless communication system (100) with reference to FIG. 1, for example, the UE (201) may be any of the UEs (104), and the network entity (202) may be any of the network entities (102). It will be well known that the process flow (200) may be applied to other communication scenarios.

[0055] At 210, the network entity (202) may optionally transmit to the UE (201) a configuration (215) that allows or does not allow triggering requests for DL ​​signals. Accordingly, at 220, the UE (201) receives the configuration (215). By doing this, the NW may configure the UE (201) to enable or disable trigger requests for enabling or disabling secondary cells (SCell), or the NW may configure the UE (201) to enable or disable SCell. For example, the configuration (215) may set up or disable requests for on-demand SSBs; or onDemandSSB-Request If the field exists, the UE (201) is allowed to request transmissions from SSB(s), e.g., SCell, on demand while in RRC_CONNECTED.

[0056] In 230, the UE (201) determines whether at least one trigger condition of the request for a DL signal is satisfied. The trigger conditions may include one or more of a beam quality-based trigger condition, a timer-based trigger condition, a traffic-based trigger condition, a data volume-based trigger condition, a residual packet delay budget (PDB)-based trigger condition, a bandwidth portion (BWP) switching-based trigger condition, or any combination thereof.

[0057] At 240, the UE (201) transmits a request (245) for a DL signal to the network entity (202) based on the determination that at least one trigger condition is satisfied. Accordingly, at 250, the network entity (202) receives the request (245) for a DL signal from the UE (201).

[0058] In some embodiments, the UE (201) may transmit a request (245) for a DL signal via an uplink signal, a wake-up signal (WUS), or a random access channel (RACH). The request (245) for a DL signal may be used to request the transmission of an on-demand synchronization signal / PBCH block (SSB) for one or more SCells, or to stop the transmission. Additionally or alternatively, the request (245) may be used to request the activation or deactivation of the SCell(s). Additionally or alternatively, the request (245) may be used to request the activation or deactivation of the SCell(s).

[0059] In some embodiments, the requested on-demand SSB may include the currently configured SSB(s), other unconfigured SSB(s), or both the configured SSB(s) and unconfigured SSB(s). In some embodiments, which on-demand SSB is the request for may be indicated by the sequence of requests or included in a Media Access Control Information Element (MAC CE) or Radio Resource Control (RRC) message. The request for an on-demand SSB may be used to enable SCell(s), to request a normal SSB (containing more beams), or to request more SSB transmissions (more frequent transmissions).

[0060] In this way, the UE (201) can request a DL signal on demand, and thus the DL signal can be transmitted or stopped depending on the UE's request. In this way, network energy saving is achieved.

[0061] Trigger condition(s) may include beam quality-based trigger conditions. Depending on the beam quality-based trigger condition, if the UE (201) determines that it has low beam quality, it may request a DL signal from the NW. Some criteria may be calculated to determine whether the UE (201) is in a low beam quality state.

[0062] In some embodiments, if the quality of the best beam among the configured beam(s) (one specific beam or multiple beams), e.g., the reference signal received power (RSRP) of the SSB, is lower than a configured threshold, the UE may determine that it has low beam quality. Additionally or alternatively, the UE may be configured in multiples, and if the number of bad beams among the configured beams (e.g., the quality of the SSB is lower than a configured threshold) is greater than the configured number, the UE may determine that it has low beam quality, and a request for an on-demand SSB may be triggered. Additionally or alternatively, another number k may be configured for the UE; and if only m (less than k) good beam(s)—e.g., the RSRP of the SSB is higher than the configured threshold measured by the UE—exist, the UE may determine that it has low beam quality, and a request for an on-demand SSB may be triggered.

[0063] Additionally, requests may be made for a currently configured SSB, for another SSB, or for more SSBs including both configured and unconfigured ones. Requests may also be transmission periods for on-demand SSBs. In some embodiments, which SSB a request is for may be indicated by the sequence of requests or included in a Media Access Control Information Element (MAC CE) or Radio Resource Control (RRC) message.

[0064] Regarding timer-based trigger conditions, timer / time windows / durations may be configured for the UE. A request for an on-demand SSB may be triggered when the timer expires, transmitted, or indicated to a lower layer. Alternatively, a request for an on-demand SSB may be triggered when the timer expires and when other trigger condition(s) in this disclosure are satisfied, transmitted, or indicated to a lower layer.

[0065] In some embodiments, the timer may be used as a prohibit timer to avoid frequent requests; when the timer is active, the UE is not allowed to trigger a request. Additionally or alternatively, the timer may be used as a trigger timer to avoid no requests for a long period, for example, when the time expires, the UE triggers a request for a DL signal. More than one timer including a prohibit timer and a trigger timer is also possible.

[0066] The UE can start or restart the timer when a request for the on-demand SSB is triggered, transmitted, or indicated to a lower layer. For example, if the timer is managed or configured by the MAC layer and the request is transmitted by the PHY layer, the MAC layer and the request triggered by the MAC layer may indicate to a lower layer, e.g., the PHY layer, to transmit the request. As another example, if the timer is managed or configured by the PHY layer and the request is transmitted by the PHY layer, the request is directly triggered and / or transmitted by the PHY layer.

[0067] The trigger condition may additionally be based on the arrival of traffic at the UE. In some embodiments, a request for an on-demand SSB may be triggered, transmitted, or indicated to a lower layer when the number or frequency of arrival of UL / DL (e.g., paging to the UE is received) traffic is equal to or greater than a threshold configured within a configured timer or time window or duration.

[0068] Regarding traffic-based trigger conditions, one or more specific traffic(s) logical channel(s) may be configured for the UE. When there is no longer any buffered data for specific traffic(s) or logical channel(s), this means that there is little demand for UL transmission, and the UE may request that the SCell(s) stop transmitting SSB, or the UE may stop receiving SSB; alternatively, the UE may request that the SCell(s) be disabled, or the UE autonomously disables the SCell(s).

[0069] Regarding data volume-based trigger conditions, one or more thresholds for data volume may be configured for the UE. The threshold(s) may be configured for the buffered data volume or the buffered residual data volume. If the buffered data volume or the buffered residual data volume is greater than the threshold, this means that there is a high demand for UL transmission, and a request for an on-demand SSB may be triggered, or the activation of the SCell(s) may be triggered, or the SCell(s) are activated.

[0070] Regarding residual PDB-based trigger conditions, one or more threshold(s) for residual PDBs may be configured on the logical channel(s). If the residual PDB of the logical channel or each packet associated with the logical channel is smaller than the threshold, this means that there is time pressure for UL transmission and more resources are required for transmission, and a request for an on-demand SSB may be triggered, a request for activation of SCell(s) may be triggered, or SCell(s) may be activated.

[0071] In response to this, if the remaining PDB of the logical channel or each packet associated with the logical channel is greater than a threshold or another threshold, this means there is no time pressure for UL transmission, and the UE may request to stop the SSB transmission of the SCell(s), or the UE may stop receiving the SSB(s); alternatively, the UE may request to disable the SCell(s), or the UE may autonomously disable the SCell(s).

[0072] Considering potential BWP switching and SSB configurations, it is possible for a UE to perform a BWP switch to transmit different traffic, for example, from a BWP associated with an SSB to a BWP not associated with an SSB. Regarding BWP-based trigger conditions, if the UE performs a BWP switch to a BWP associated with an SSB, a request for the on-demand SSB is triggered. Additionally, or alternatively, if the UE performs a BWP switch from a dormant BWP to a BWP that is not dormant, a request for the on-demand SSB is triggered.

[0073] In some embodiments, if the UE performs a BWP switching to a BWP associated with the SSB and one or more of the other trigger condition(s) described above are satisfied, a request for an on-demand SSB is triggered. Additionally or alternatively, if the UE performs a BWP switching to a BWP associated with the SSB and the UE identifies its location changes, a request for an on-demand SSB is triggered.

[0074] The UE may indicate which SCell(s) the request is for, which may be SCell(s) of a main cell group (MCG) or a secondary cell group (SCG). In some embodiments, a request for a DL signal indicates at least one SCell for which the DL signal is requested. For example, a request for a DL signal may indicate an identifier (ID) of at least one SCell. The ID may be an index or PHY ID of the SCell(s).

[0075] If the index of SCell(s) is repeated across cell groups (CGs), it may be necessary to identify which CG(s) the SCell(s) belong to. To this end, the request for the DL signal may additionally indicate the cell group to which at least one SCell belongs using an additional indicator. In some embodiments, a binary value may be used to indicate that the CG is an MCG or an SCG, for example, 0 means MCG and 1 means SCG. Additionally, if there is only one on-demand SSB SCell configured for the UE per CG (e.g., one SCell for the MCG and / or one SCell for the SCG), the UE may indicate this with 1 bit.

[0076] In some embodiments, ID(s) may be included via a RACH or message used to request an on-demand SSB. For example, a request for a flexible-length on-demand SSB MAC CE may be identified by a MAC subheader having an LCID. A SCell ID / index may be included in the MAC CE to indicate which SCell(s) the request is for.

[0077] Additionally or alternatively, a request for a DL signal may include a bitmap indicating the SCell(s) for which the DL signal is requested from the set of cells configured for the UE. For example, a request for a one-octet on-demand SSB MAC CE may be identified by a MAC subheader containing a Logical Cell ID (LCID). It has a fixed size and consists of a single octet containing seven C-fields and one R-field. The C-field (Ci) may be used to indicate which SCell(s) the request is for. As another example, a request for a four-octet on-demand SSB MAC CE may be identified by a MAC subheader containing an LCID. This has a fixed size and consists of four octets containing thirty-one C-fields and one R-field. The C-field (Ci) may be used to indicate which SCell(s) the request is for.

[0078] In some embodiments, a default or specific cell may be configured for the UE, which is a SCell. A request for an on-demand SSB means that the UE requests an SSB transmission from the default cell. The UE does not need to specify the SCell(s) in the request.

[0079] After a request for a DL signal is transmitted, the UE may monitor or receive potential DL transmissions from the NW, for example, the UE immediately monitors an SSB transmission. In some embodiments, the UE may additionally receive a indication from the NW after transmitting the request and monitor or receive potential DL transmissions based on the indication. The transmitted DL signal from the NW may include at least one of an SSB or a System Information Block (SIB).

[0080] The indication may indicate one or more SCells to which the DL signal is transmitted. The SCell(s) may be a cell provided by the base station receiving the request, or a neighboring cell of that cell. Additionally, the indication may include time-frequency resources for the DL signal and a transmission pattern of the DL signal. The resources may be represented by at least one of a start point or start time, a period and / or offset of the DL signal, a transmission opportunity of the DL signal, and others.

[0081] DL transmission-related indications may be configured or transmitted, for example, from a predefined, pre-configured, or common channel, search space, or resource, or by system information from a SCell or a neighboring cell of a SCell, for example, other SCell(s) or PCell. The indications may be transmitted via a dedicated signaling / information element (IE), or the configuration is predefined.

[0082] FIG. 3 illustrates an example of a device suitable for implementing some embodiments of the present disclosure. The device (300) may be an example of a UE (104) or network entity (102) described herein. The device (300) may support wireless communication with one or more network entities (102), UEs (104), or any combination thereof. The device (300) may include components for bidirectional communication, such as a processor (302), memory (304), a transceiver (306), and optionally, an I / O controller (308), for transmitting and receiving communications. These components may communicate electronically through one or more interfaces (e.g., a bus) or be coupled in other ways (e.g., kinetically, phonologically, functionally, electronically, electrically).

[0083] A processor (302), memory (304), transceiver (306), or various combinations thereof or various components thereof may be examples of means for carrying out various aspects of the disclosure described herein. For example, a processor (302), memory (304), transceiver (306), or various combinations thereof or components thereof may support a method for carrying out one or more of the operations described herein.

[0084] In some implementations, the processor (302), memory (304), transceiver (306), or various combinations or components thereof may be implemented in hardware (e.g., within a communication management circuit). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination configured as a means to perform the functions described in this disclosure or otherwise supporting it. In some implementations, the processor (302) and the memory (304) coupled to the processor (302) may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in the memory (304) by the processor (302).

[0085] For example, the processor (302) may support wireless communication in the device (300) according to the examples disclosed herein. The device (300) may be an example of a UE (104). In this case, the processor (302) may be configured to be operable to support means for determining whether at least one trigger condition for a request for a downlink (DL) signal is satisfied; and means for transmitting a request for a DL signal to a network entity based on determining that at least one trigger condition is satisfied.

[0086] The device (300) may be a network entity (102), for example, an example of a network entity. In this case, the processor (302) may be configured to be operable to support means for receiving a request for a DL signal from a user device (UE) via a transceiver, and the request for a DL signal is transmitted based on at least one trigger condition being satisfied in the UE.

[0087] The processor (302) may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor (302) may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor (302). The processor (302) may be configured to execute computer-readable instructions stored in memory (e.g., memory (304)) to enable the device (300) to perform various functions of the present disclosure.

[0088] Memory (304) may include random access memory (RAM) and read-only memory (ROM). Memory (304) may store computer-readable, computer-executable code containing instructions that enable the device (300) to perform the various functions described herein when executed by the processor (302). The code may be stored in a non-transient computer-readable medium, such as system memory or other types of memory. In some implementations, the code may not be directly executable by the processor (302), but may enable the computer to perform the functions described herein (e.g., during compilation and execution). In some implementations, memory (304) may include a basic I / O system (BIOS) capable of controlling basic hardware or software operations, such as interactions with devices, among other things, peripheral components or others.

[0089] The I / O controller (308) can manage input and output signals for the device (300). The I / O controller (308) can also manage peripherals that are not integrated into the device (300). In some implementations, the I / O controller (308) may represent a physical connection or port to an external peripheral. In some implementations, the I / O controller (308) may use an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or other known operating systems. In some implementations, the I / O controller (308) may be implemented as part of a processor such as the processor (302). In some implementations, a user may interact with the device (300) through the I / O controller (308) or through a hardware component controlled by the I / O controller (308).

[0090] In some implementations, the device (300) may include a single antenna (310). However, in some other implementations, the device (300) may have more than one antenna (310) (i.e., multiple antennas) comprising multiple antenna panels or antenna arrays, which can transmit or receive multiple wireless transmissions simultaneously. The transceiver (306) may communicate bidirectionally through one or more antennas (310), wired links, or wireless links as described herein. For example, the transceiver (306) may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver (306) may also include a modem for modulating packets, providing the modulated packets to one or more antennas (310) for transmission, and demodulating packets received from one or more antennas (310). The transceiver (306) may include one or more transmission chains, one or more reception chains, or a combination thereof.

[0091] A transmission chain may be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator to modulate data onto a carrier signal to prepare the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas (310) for transmitting the amplified signal into air or a wireless medium.

[0092] A receiving chain may be configured to receive signals (e.g., control information, data, packets) through a wireless medium. For example, a receiving chain may include one or more antennas (310) for receiving signals through air or a wireless medium. A receiving chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. A receiving chain may include at least one demodulator configured to demodulate the received signal and acquire the transmitted data by reversing the modulation technique applied during the transmission of the signal. A receiving chain may include at least one decoder for receiving the transmitted data by decoding and processing the demodulated signal.

[0093] FIG. 4 illustrates an example of a processor (400) suitable for implementing some embodiments of the present disclosure. The processor (400) may be an example of a processor configured to perform various operations according to the examples described herein. The processor (400) may include a controller (402) configured to perform various operations according to the examples described herein. The processor (400) may optionally include at least one memory (404). Additionally or alternatively, the processor (400) may optionally include one or more arithmetic logic units (ALUs) (406). One or more of these components may communicate electronically through one or more interfaces (e.g., buses) or be coupled (e.g., kinetically, phonologically, functionally, electronically, electrically).

[0094] The processor (400) may be a processor chipset and may include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, acquiring, searching, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or contained in the processor chipset (e.g., processor (400)), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), etc.).

[0095] A controller (402) may be configured to manage and coordinate various operations of the processor (400) (e.g., signaling, receiving, acquiring, searching, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) so that the processor (400) may support various operations according to the examples described herein. For example, the controller (402) may operate as a control unit of the processor (400) and generate control signals that manage the operations of various components of the processor (400). These control signals include the activation or deactivation of function units, the selection of data paths, the initiation of memory access, and the timing adjustment of operations.

[0096] The controller (402) may be configured to fetch instructions from memory (404) (e.g., acquire, retrieve, receive) and determine subsequent instruction(s) to be executed, thereby enabling the processor (400) to support various operations according to the examples described herein. The controller (402) may be configured to track the memory addresses of instructions associated with memory (404). The controller (402) may be configured to decode instructions to determine the operations to be performed and the accompanying operands. For example, the controller (402) may be configured to interpret instructions and determine control signals to be output to other components of the processor (400) to enable the processor (400) to support various operations according to the examples described herein. Additionally or alternatively, the controller (402) may be configured to manage data flow within the processor (400). The controller (402) may be configured to control data transfer between the registers, arithmetic logic units (ALU), and other functional units of the processor (400).

[0097] Memory (404) may include one or more caches (e.g., memory local to or contained in the processor (400)) or other memory, e.g., RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory (404) may be located within or on the processor chipset (e.g., local to the processor (400)). In some other implementations, memory (404) may be located outside the processor chipset (e.g., remote from the processor (400)).

[0098] Memory (404) may store computer-readable, computer-executable code containing instructions that, when executed by the processor (400), cause the processor (400) to perform the various functions described herein. The code may be stored in a non-transient computer-readable medium, such as system memory or other types of memory. A controller (402) and / or a processor (400) may be configured to execute computer-readable instructions stored in memory (404) to cause the processor (400) to perform the various functions. For example, the processor (400) and / or the controller (402) may be coupled to or with memory (404), and the processor (400), the controller (402), and the memory (404) may be configured to perform the various functions described herein. In some examples, the processor (400) may include multiple processors, and the memory (404) may include multiple memories. One or more of the multiple processors may be combined with one or more of the multiple memories, and they may be configured to perform the various functions of this specification individually or collectively.

[0099] One or more ALUs (406) may be configured to support various operations according to the examples described herein. In some implementations, one or more ALUs (406) may be located in or on a processor chipset (e.g., processor (400)). In some other implementations, one or more ALUs (406) may be located outside the processor chipset (e.g., processor (400)). One or more ALUs (406) may perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs (406) may receive input operands and an operation code that determines the operation to be executed. One or more ALUs (406) may be composed of various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALUs (406) may support logical operations such as AND, OR, exclusive OR (XOR), negative OR (NOR), and negative AND (NAND), thereby enabling one or more ALUs (406) to handle conditional operations, comparisons, and bitwise operations.

[0100] The processor (400) may support wireless communication according to examples as disclosed in this specification. The processor (400) may be implemented in a UE (104). In this case, the processor (400) may be configured to be operable to support means for determining whether at least one trigger condition of a request for a downlink (DL) signal is satisfied; and means for transmitting a request for a DL signal to a network entity based on determining that at least one trigger condition is satisfied.

[0101] The processor (400) may be implemented in a network entity (102), for example, a base station. In this case, the processor (400) may be configured to be operable to support means for receiving a request for a DL signal from a user device (UE), and the request for a DL signal is transmitted based on at least one trigger condition being satisfied in the UE.

[0102] FIG. 5 illustrates a flowchart of a method (500) performed by a UE according to embodiments of the present disclosure. Operations of the method (500) may be implemented by a device or its components as described herein. For example, operations of the method (500) may be performed by a UE (104) as described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use special-purpose hardware to perform embodiments of the described functions.

[0103] In 510, the method may include a step of determining whether at least one trigger condition of a request for a downlink (DL) signal is satisfied. The operations of 510 may be performed according to the examples described herein. In some implementations, aspects of the operations of 510 may be performed by a UE (104) as described with reference to FIG. 1.

[0104] In 520, the method may include the step of transmitting a request for a DL signal to a network entity based on determining that at least one trigger condition is satisfied. The operations of 520 may be performed according to the examples described herein. In some implementations, aspects of the operations of 520 may be performed by a UE (104) as described with reference to FIG. 1.

[0105] FIG. 6 illustrates a flowchart of a method (600) performed by a network entity according to embodiments of the present disclosure. The operations of the method (600) may be implemented by a device or its components as described herein. For example, the operations of the method (600) may be performed by a network entity (102) as described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may perform embodiments of the described functions using special-purpose hardware.

[0106] In 610, the method may include the step of receiving a request for a DL signal from a user device (UE), and the request for a DL signal is transmitted based on at least one trigger condition being satisfied in the UE. The operations of 610 may be performed according to the examples described herein. In some implementations, aspects of the operations of 610 may be performed by a network entity (102) as described with reference to FIG. 1.

[0107] It should be noted that the methods described herein describe possible implementations, and that operations and steps may be rearranged or modified in other ways, and other implementations are possible. Furthermore, aspects from two or more of the methods may be combined.

[0108] The various exemplary blocks and components described in connection with the disclosure of this specification may be implemented or performed by a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described in this specification. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented by a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0109] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored as one or more instructions or code forms on a computer-readable medium or transmitted therethrough. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of the software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be located in various physical locations, including distributed so that parts of the functions are implemented in different physical locations.

[0110] Computer-readable media include both non-transient computer storage media and communication media, which include any medium that facilitates the transfer of computer programs from one place to another. Non-transient storage media may be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, non-transient computer-readable media may include RAM, ROM, electrically erasable and programmable ROM (EEPROM), flash memory, compact disc (CD)-ROM or other optical disc storage, magnetic disc storage or other magnetic storage devices, or any other non-transient medium that can be used to carry or store desired means of program code in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0111] As used herein, including in the claims, the article "a" preceding an element is not restricted and is understood to mean "at least one" of the elements or "one or more" of the elements. The terms article ("a"), "at least one," "one or more," and "at least one of one or more" may be interchangeable. When used in this specification, including in claims, the word “or” used in a list of items (e.g., a list of items accompanied by phrases such as “at least one of,” or “one or more of,” or “one or both of) indicates a comprehensive list; thus, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A, B, and C). Furthermore, when used in this specification, the phrase “based on” should not be interpreted as a reference to a closed set of conditions. For example, an exemplary step described as “based on condition A” may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, when used in this specification, the phrase “based on” should be interpreted in the same way as the phrase “at least partially based.” Furthermore, when used in this specification, including in claims, the “set” may include one or more elements.

[0112] This description is provided to enable a person skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to a person skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Accordingly, the present disclosure is not limited to the examples and designs described herein, but should be given the broadest scope conforming to the principles and novel features disclosed herein.

Claims

Claim 1 As user equipment (UE), the processor; and a transceiver coupled to the processor, wherein the processor: Determine whether at least one trigger condition for a request for a downlink (DL) signal is satisfied; A UE configured to transmit a request for the DL signal to a network entity via the transceiver based on a determination that at least one of the above trigger conditions is satisfied. Claim 2 In paragraph 1, the processor further comprises: a UE configured to receive from the network entity a configuration of allowing or not allowing a request for the DL signal to be triggered. Claim 3 In claim 1, the at least one trigger condition comprises: a first trigger condition that the UE has low beam quality; a second trigger condition that the timer has expired—the timer is restarted when a request for the DL signal is transmitted—; a third trigger condition that the number or frequency of arrivals of uplink (UL) or DL ​​traffic within a configured time window is equal to or greater than a first threshold; a fourth trigger condition that there is no buffered data in the logical channel; a fifth trigger condition that the volume of buffered data or residual buffered data in the logical channel for UL transmission is greater than a second threshold or less than a third threshold—the third threshold is less than the second threshold—; a sixth trigger condition that the residual packet delay budget (PDB) of the logical channel or each packet associated with the logical channel is greater than a fifth threshold or less than a sixth threshold—the sixth threshold is less than the fifth threshold—; and a seventh trigger condition that the UE performs BWP switching to bandwidth portions (BWP) associated with the DL signal. A UE comprising one or more of the eighth trigger conditions that the above UE performs BWP switching from a dormant BWP to a non-dormant BWP. Claim 4 In paragraph 3, the above processor additionally: The quality of the best beam among the configured beams is smaller than the first configured threshold value; Among the configured beams, the number of beams having a quality smaller than a second configured threshold is greater than the first configured number; or A UE configured to determine that the first trigger condition is satisfied when one of the conditions is met where the number of beams having a quality higher than a third configured threshold among the configured beams is smaller than the second configured number. Claim 5 In claim 1, the request for the DL signal is: transmission or interruption of transmission of an on-demand synchronization signal / PBCH block (SSB) to a secondary cell (SCell); triggering the activation or deactivation of the SCell; or a UE used to request one of the activation or deactivation of the SCell. Claim 6 In paragraph 5, the on-demand SSB comprises: a configured SSB; an unconfigured SSB; or one of a configured SSB and an unconfigured SSB, UE. Claim 7 In paragraph 6, the UE, for which on-demand SSB the request is for, is indicated by the sequence of the request or included in the Media Access Control Information Element (MAC CE) or Radio Resource Control (RRC) message. Claim 8 In claim 1, the request for the DL signal is a UE indicating at least one SCell where the DL signal is requested. Claim 9 In paragraph 8, the request for the DL signal is a UE indicating the identifier (ID) of at least one SCell. Claim 10 In paragraph 8, the request for the DL signal further indicates the cell group to which the at least one SCell belongs, UE. Claim 11 In paragraph 8, the request for the DL signal comprises a bitmap representing at least one SCell from a set of cells configured for the UE, wherein the UE. Claim 12 In paragraph 5, the above SCell is a default SCell configured for the above UE. Claim 13 In claim 1, the processor further comprises: receiving a mark indicating a SCell to which the DL signal is transmitted after transmitting the request; and a UE configured to receive the DL signal based on the received mark. Claim 14 In paragraph 13, the SCell is a UE that is a cell provided by the network entity or a neighbor cell of the cell. Claim 15 In paragraph 13, the above indication further indicates time-frequency resources for the DL signal and a transmission pattern of the DL signal, UE. Claim 16 In paragraph 13, the transmitted DL signal comprises at least one of an SSB or a System Information Block (SIB), a UE. Claim 17 In paragraph 1, the request for the DL signal is transmitted via an uplink signal, a wake-up signal (WUS), or a random access channel (RACH), in a UE. Claim 18 A network entity comprising: a processor; and a transceiver coupled to said processor, wherein the processor: The above transceiver is configured to receive a request for a DL signal from a user device (UE), and A network entity that transmits a request for the above DL signal based on at least one trigger condition being satisfied in the UE. Claim 19 In paragraph 18, the processor further comprises: a network entity configured to transmit to the UE a configuration of allowing or not allowing a request for the DL signal. Claim 20 In paragraph 18, the processor further comprises: a network entity configured to transmit, after receiving the request, an indication indicating the SCell to which the DL signal is transmitted.

Images