Discontinuous transmission and reception for non-terrestrial network (NTN) beams

Abstract

This disclosure provides systems, methods, and apparatuses in which a non-terrestrial network (NTN) node 101 (e.g., a satellite 104 with onboard base station 106 or NTN ground BS 106') can provide one or more beam discontinuous transmission (DTX) or discontinuous reception (DRX) configurations (beam DTX / DRX configurations 140) to a user equipment (UE 102). The one or more beam DTX / DRX configurations including at least first beam DTX / DRX configuration specific to at least a first beam of the NTN node. The first beam DTX / DRX configuration can indicate active / non-active periods of a first beam on which the UE has an active radio resource control (RRC) connection or on which the UE is camping (in RRC idle / inactive state). The satellite can provide beam DTX / DRX configuration(s) for multiple beams. The satellite can communicate beam DTX / DRX configurations using RRC signaling, system information, downlink control information (DCI), or other control signaling.

Description

DISCONTINUOUS TRANSMISSION AND RECEPTION FOR NON-TERRESTRIAL NETWORK (NTN) BEAMSTECHNICAL FIELD

[0001] This disclosure relates generally to wireless communication and some aspects relate to a non-terrestrial network (NTN) node implementing beam-specific discontinuous transmission (DTX) and / or discontinuous reception (DRX) operation.BACKGROUND

[0002] This background description is provided for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0003] A wireless communication system includes one or more network entities (such as a base station) enabling communication for a mobile communication device (referred to as a user equipment (UE)). Each base station operates one or more cells to provide coverage for the UE. Existing wireless communication systems and network selection techniques are based primarily on legacy terrestrial networks. However, the 3rdGeneration Partnership Project (3 GPP) organization has proposed to extend 5thGeneration (5G) communications to non-terrestrial networks (NTNs) with 5G new radio (NR) technologies, or with the Long- Term-Evolution (LTE) technologies tailored for the Narrowband Internet-of-Thing (NB-IoT) or the enhanced Machine Type Communication (eMTC) technologies. A non-terrestrial network (NTN) refers to a network, or segment of networks, using radio frequency (RF) resources on board an NTN node. Example NTN nodes include spacebome vehicles or airborne vehicles. Airborne vehicles can include unmanned aircraft systems (UAS), High- Altitude Platform Systems (HAPS), balloons, dirigibles, winged vehicles such as airplane or drones, among other examples. Spacebome vehicles can include a Geostationary Earth Orbit (GEO) satellite (sometimes also referred to as a geosynchronous orbit (GSO) satellite), a Low Earth Orbit (LEO) satellite, a Medium Earth Orbit (MEO) satellite, or a Highly Elliptical Orbit (HEO) satellite, among other examples. In some implementations, NTN nodes can form constellations. For simplicity, the discussion below refers to all such apparatuses as satellites or NTN nodes.

[0004] A satellite directs radio frequency (RF) transmission towards a specific direction, creating a “beam’’ of focused energy' for a beam footprint, thereby improving signal qualifyand increasing network performance for UEs within the beam footprint. The footprint of a beam typically has an elliptic shape depending on the on-board antenna configuration and the elevation angle. In some implementations, a satellite can generate several beams within a field of view from the satellite. By projecting multiple beams toward the ground, the satellite might expand the cell coverage available for UEs in the footprint of the various beams.BRIEF SUMMARY

[0005] The systems, methods, and apparatuses of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0006] One innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communication by a user equipment (UE). The method includes the UE receiving, from a non-terrestrial network (NTN) node, one or more beam discontinuous transmission (DTX) or discontinuous reception (DRX) configurations (beam DTX / DRX configurations). The one or more beam DTX / DRX configurations include at least first beam DTX / DRX configuration specific to at least a first beam of the NTN node. The method includes the UE communicating with the NTN node via the first beam in accordance with the first beam DTX / DRX configuration.

[0007] In some aspects, the method also includes the UE receiving, from the NTN node, a second beam DTX / DRX configuration associated with at least a second beam of the NTN node. The method includes the UE communicating with the NTN node via the first beam or the second beam in accordance with the first beam DTX / DRX configuration or the second beam DTX / DRX configuration, respectively.

[0008] Another innovative aspect of the subject matter described in this disclosure can be implemented as a method for wireless communication by an NTN node. The method includes the NTN node transmitting one or more beam DTX / DRX configurations including at least a first beam DTX / DRX configuration specific to at least a first beam of the NTN node. The method includes the NTN node communicating with a UE via the first beam in accordance with the first beam DTX / DRX configuration.

[0009] Another innovative aspect of the subject matter described in this disclosure can be implemented as an apparatus that includes a communication unit and a processing system configured to control the communication unit to implement any one of the above-referenced methods.

[0010] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Otherfeatures, aspects, and advantages will become apparent from the description, the drawings, and the claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Like reference numbers and designations in the various drawings indicate like elements. Note that the relative dimensions of the figures may not be drawn to scale. To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0012] FIG. 1A shows an example wireless communication system including a user equipment (UE) and a non-terrestrial network (NTN) in which an NTN node provides a beam discontinuous transmission (DTX) or discontinuous reception (DRX) configuration to the UE.

[0013] FIG. IB shows example patterns for beam DTX / DRX operation.

[0014] FIG. 2A shows an example wireless communication system implementing an NTN base station (BS) connecting to a satellite via an NTN gateway using a transparent payload implementation.

[0015] FIG. 2B shows an example wireless communication system implementing an NTN BS onboard a satellite using a regenerative payload implementation.

[0016] FIG. 3A shows an example beam DTX / DRX operation for an NTN node operating multiple beams.

[0017] FIG. 3B shows a UE potentially in coverage of multiple beams at various times based on overlapping beams.

[0018] FIG. 4A shows example states for beam DTX / DRX operation.

[0019] FIG. 4B shows some potential differences between legacy cell DTX / DRX operation and beam DTX / DRX operation.

[0020] FIG. 5A shows example parameters for a beam DTX / DRX configuration.

[0021] FIG. 5B shows an example technique for configuring and activating beam DTX / DRX configurations.

[0022] FIG. 6A shows an example message flow in which an NTN node provides one or more beam DTX / DRX configuration(s) to a UE.

[0023] FIG. 6B shows another example message flow in which an NTN node provides one or more beam DTX / DRX configuration(s) to a UE.

[0024] FIG. 7 shows an example message flow including a beam DTX / DRX configuration and a UE in connected state.

[0025] FIG. 8 shows an example message flow including a rough beam DTX / DRX configuration and full beam DTX / DRX configuration.

[0026] FIG. 9 shows an example message flow including a beam DTX / DRX configuration included in system information.

[0027] FIG. 10 shows an example message flow in which a UE monitors a beam based on timing for a next paging occasion (PO) and a beam DTX / DRX configuration.

[0028] FIG. 11 shows an example message flow in which a UE can shift timing for a PO based on a beam DTX / DRX configuration.

[0029] FIG. 12 shows a flow chart diagram with example operations of a UE in connected state.

[0030] FIG. 13 shows a flow chart diagram with example operations of a UE in which a TCI state configuration can indicate a beam DTX / DRX configuration.

[0031] FIG. 14 shows a flow chart diagram with example operations of a UE in which the beam DTX / DRX configuration is provided in system information and the UE applies the beam DTX / DRX configuration based on a TCI state activation.

[0032] FIG. 15 shows a flow chart diagram with example operations of a UE that receives control signaling for a beam change, where the control signaling optionally includes a delay timer indicating when to begin monitoring the new beam.

[0033] FIG. 16 shows a flow chart diagram with example operations of a UE that can determine which beam to monitor for a next PO based on a beam DTX / DRX configuration.

[0034] FIG. 17 shows a flow chart diagram with example operations of a UE that can shift timing of a next PO based on a beam DTX / DRX configuration.

[0035] FIG. 18 shows a flow chart diagram with example operations of an NTN node that transmits a beam DTX / DRX configuration.

[0036] FIG. 19 shows another flow chart diagram with example operations of an NTN node.

[0037] FIG. 20 shows a flow chart diagram with example operations of an NTN node that shifts timing of a PO based on a beam DTX / DRX configuration.

[0038] FIG. 21A shows an example control plane protocol stack for a regenerative NTN architecture in accordance with aspects of this disclosure.

[0039] FIG. 21B shows an example control plane protocol stack for a transparent NTN architecture in accordance with aspects of this disclosure.

[0040] FIG. 22 shows a block diagram of example distributed or disaggregated implementation of an example base station using a centralized unit (CU) and a distributed unit (DU).

[0041] FIG. 23 shows a block diagram of an example wireless communication system showing hardware features and communication interfaces.DETAILED DESCRIPTION

[0042] The following description is directed to certain implementations for the purpose of describing innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied in a multitude of different ways. Some of the examples in this disclosure are based on wireless communication according to the 3rdGeneration Partnership Project (3GPP) wireless standards, such as the 4th generation (4G) Long Term Evolution (LTE) and 5thgeneration (5G) New Radio (NR) standards. However, the described implementations can be implemented in any device, system, or network that is capable of transmitting and receiving radio frequency signals according to any of the wireless communication standards, including any of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 or 802.16 wireless standards, or other known signals that are used to communicate within a wireless, cellular, or internet of things (loT) network, such as a system utilizing 4G, 5G, 6th generation (6G), WiFi, or future radio technology.

[0043] A non-terrestrial network (NTN) node may operate multiple beams to enhance the downlink coverage (i.e., to increase the satellite footprint). For example, a satellite can project more than one beam within a footprint area on Earth. While the use of multiple beams can enhance coverage, a satellite might not continuously project some beams. For example, a satellite may avoid having all of its beams active at the same time. A satellite might implement power sharing among satellite beams or implement different satellite beam patterns / size (i.e., wide or narrow) across the satellite footprint. The satellite might periodically activate or deactivate various satellite beams based on one or more constraints, such as the nominal Equivalent Isotropic Radiated Power (EIRP) density per satellite beam, limited power, or limited feeder link bandwidth. A user equipment (UE) within a coverage area of the NTN can save power by monitoring only active beams for downlink signals and / or paging messages.

[0044] Discontinuous transmission (DTX) and discontinuous reception (DTX) is a technique that can enable power saving features. For example, cell DTX / DRX is a network energy savings (NES) feature that enables a base station to indicate ON / OFF periods (alsoreferred to as active / non-active periods) when the base station will operate a cell serving a UE. During OFF periods, the base station and the UE can conserve power by limiting radio frequency transmission / reception. Cell DTX / DRX typically applies to an entire cell and is configured for UEs using radio resource control (RRC) messaging. Thus, a cell DTX / DRX configuration typically is configured for UEs in an RRC connected state. Absent the features of this disclosure, current techniques for cell DTX / DRX configuration are not suitable for NTN-based access involving multiple beam operation because the NTN might periodically operate various different beams within a cell. A cell DTX / DRX configuration indicating the ON / OFF pattern of a cell may unnecessarily limit a UE's ability to access one or more beams (within the cell) as the UE moves into or out of the coverage of various beams. Furthermore, when a UE is in the RRC idle / inactive state (e.g., not in RRC connected state), the UE may not receive a legacy cell DTX / DRX configuration.

[0045] This disclosure provides systems, methods, and apparatuses in which an NTN node (e.g., a satellite) can provide one or more beam DTX / DRX configurations to a UE. A beam DTX / DRX configuration can indicate active / non-active periods of a first beam on which the UE has an active RRC connection or on which the UE is camping (in RRC idle / inactive state). In some implementations, the satellite provides beam DTX / DRX configuration(s) for more than one beam. For example, the satellite can provide beam DTX / DRX configurations for all of its beams. In some implementations, the satellite provides the beam DTX / DRX configuration for a first beam and a second beam, where the second beam is adjacent or overlapping with the first beam. This disclosure describes several techniques for the satellite to communicate beam DTX / DRX configurations, such as RRC signaling, downlink control information (DCI), or media access control (MAC) control element (CE) control signaling. In some aspects, the satellite can communicate beam DTX / DRX configuration(s) using system information that is broadcast. Using the techniques of this disclosure, a UE can obtain the beam DTX / DRX configuration for more than one beam.

[0046] Aspects of this disclosure enable the satellite to indicate active and non-active periods on a per-beam basis. An active period can also be referred to as an ON period. A non-active period can refer to a period when the satellite completely or partially disables beam communication. In some implementations, a non-active period refers to an OFF period in which the satellite does not communicate (e.g., transmit or receive according to configured beam DTX or beam DRX). In some implementations, during a non-active period, the satellite may transmit some common downlink signals (such as system information, synchronization signals, and / or reference signals). Such non-active period can be referred to as a COMMON period (or other term) to distinguish from an OFF period. In some aspects, a beam DTX / DRXconfiguration can indicate ON / OFF / COMMON periods. Alternatively, or additionally, the beam DTX / DRX configuration can indicate whether the satellite will continue to transmit common downlink signals during a configured OFF period.

[0047] This disclosure contemplates several options for efficiently communicating beam DTX / DRX configuration information. For example, a beam DTX / DRX configuration can be similar to a cell DTX / DRX configuration with the addition of beam-specific information, such as beam matching information. Beam matching information (which can also be referred to as beam identification information or other similar terms) can be any information that identifies a particular beam. Examples of beam matching information include but are not limited to a TCI state, a beam identifier (ID), or a beam index, among other examples. In some implementations, beam matching information can be an SSB index or CSI-RS index that is associated with a particular beam, such as where system information configures multiple SSB / CSI-RS resources for respective beams. In some implementations, a satellite can include the beam matching information in a beam DTX / DRX configuration, in system information, or both. Alternatively, or additionally, the satellite can include the beam matching information in dedicated control signaling (such as RRC, DCI, or MAC CE).

[0048] In some implementations, a satellite can transmit control signaling to activate (e.g., on a per beam basis) one or more pre-configured beam DTX / DRX configurations. For example, the pre-configured beam DTX / DRX configurations can be identified by a configuration ID or index. The control signaling can indicate the configuration ID or index and beam matching information. In some implementations, the pre-configured beam DTX / DRX configurations are defined in system information in such a way that they can be reused or modified on a per-beam basis. In some implementations, a technical specification can specify the pre-configured beam DTX / DRX configurations, thereby reducing system overhead. In some implementations, a satellite can transmit aggregate beam DTX / DRX configuration information for multiple beams. To reduce overhead, the satellite may transmit a common portion with common beam DTX / DRX configuration information (such as periodicity or duration) and beam-specific portion(s) with beam-specific beam DTX / DRX configuration information (such as an offset or start time).

[0049] In some implementations, a satellite can transmit a first beam DTX / DRX configuration with fewer parameters, such as a minimum configuration needed for the UE to determine the beginning of a next active period of a beam. The first beam DTX / DRX configuration can be referred to as a “rough” beam DTX / DRX configuration. The adjective “rough” can be replaced with alternative adjectives, such as coarse, basic, limited, partial, low resolution, or other similar terms. A rough beam DTX / DRX configuration includes lessdata and overhead compared to a full beam DTX / DRX configuration. The satellite can also transmit a second beam DTX / DRX configuration with more parameters. The second beam DTX / DRX configuration can be referred to as a full beam DTX / DRX configuration. The adjective “full’' can be replaced with alternative adjectives, such as detailed, granular, complete, extended, high resolution, or other similar terms. In some implementations, the satellite transmits a full beam DTX / DRX configuration for one beam (such as a serving beam) and rough beam DTX / DRX configurations for other beams (such as adjacent or overlapping beams).

[0050] In some aspects, a UE can use the beam DTX / DRX configurations of various beams to determine which beam and / or timing to receive paging messages from the satellite. For example, the UE might switch from monitoring a first beam to monitoring a second beam when a paging occasion occurs during an active period of the second beam and a non-active period of the first beam. In some implementations, the UE and the satellite can shift (e.g., adjust, modify, or extend) a paging occasion when the paging occasion occurs during a nonactive period of a beam.

[0051] Particular implementations of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. A UE camping on a particular beam benefits by knowing the active / non-active periods of that beam and potentially also beam active / non-active periods of other adjacent or overlapping beams. The UE can conserve power by refraining from monitoring for paging messages or downlink signals during non-active periods of the beam. Alternatively, or additionally, the UE can determine which beam and paging occasion to monitor based on active periods of various beams. The potential technical advantages include power saving for the NTN node and UE, coordination of paging occasions when the NTN node operates different beams, broader coverage options, among other advantages.

[0052] The examples of this disclosure are based on NTN technology. An NTN node is described as a satellite. In various implementations, the NTN node can be any type of airborne or spaceborne device that operates multiple beams for communicating with another device. As future developments enable other types of devices (such as loT devices, wearables, robots, etc.) to communicate with another device using more than one beam, the concepts of this disclosure can extend to such devices.

[0053] FIG. 1A shows an example wireless communication system 100A including a UE 102 and a non-terrestrial network in which an NTN node 101 provides a beam DTX / DRX configuration to the UE 102. An NTN extends or augments the service capability of a wirelesscommunication system. An NTN refers to a network, or segment of networks, using radio frequency (RF) resources on board an NTN node 101 (such as a spaceborne vehicle or an airborne vehicle). An NTN node 101 can belong to one of several t pes based on altitude, orbit, and beam footprint size. FIG. 1 A shows an NTN node 101 as a satellite 104. A satellite 104 can support a transparent or a regenerative (with on board processing) pay load architecture, as further described with reference to FIG. 2A and FIG. 2B). The satellite 104 ty pically generates several beams for a given service area bounded by the satellite’s field of view. For a transparent payload implementation (as shown in FIG. 2A), a satellite 104 can apply RF filtering and frequency conversion and amplification, and not change the waveform signal. For a regenerative payload implementation (such as shown in FIG. 2B), a satellite 104 can apply RF filtering, frequency conversion and amplification, demodulation and decoding, routing, and coding / modulation.

[0054] An NTN gateway 108 (sometimes also referred to as a “sat-gateway” or “GW”) communicatively couples the satellite 104 to ground components of the example wireless communication system 100A (such as a ground NTN BS 106', a core network (CN) 110, or other data network resources). In some deployments, the NTN node 101 (e.g., satellite 104) can perform some or all functions of a base station (shown as BS 106). The BS 106 can be included on-board the satellite 104 or can be partially or wholly located on the ground (shown as ground NTN BS 106'). In this disclosure, the term BS 106 can refer to either or both of the BS 106' on the ground (when present) or the BS 106 (when onboard the satellite 104). The satellite 104, the NTN gateway 108. and the BS 106 / 106' form part of a RAN (sometimes referred to as an NTN RAN). In some implementations, the radio access technology for the NTN RAN is based on 5G NR. Alternatively, the radio access technology' for the NTN RAN can use an Evolved Universal Terrestrial Radio Access (E-UTRA) air interface for 4G LTE, or another radio access technology such as NB-IoT, among other examples. Any number of RANs can be communicatively coupled to the CN 110. The CN 110 can be implemented as an evolved packet core (EPC), a fifth generation (5G) core (5GC), or a sixth generation (6G) core.

[0055] In this disclosure, the NTN node 101 can refer to the satellite 104. the BS 106 / 106', or collectively to the satellite 104 and the BS 106 / 106', such that the phrases or reference numbers can be interchangeable. When the UE 102 is within a coverage area of the satellite 104, the UE 102 can establish a radio connection to the satellite 104 via an NTN cell 120. The NTN cell 120 refers to a coverage area in which the satellite 104 operates as part of a radio network. The radio network can be associated with a footprint on the surface of the Earth or could be deployed in air, space, a spaceship, or other planetary objects. The radioconnection between the UE 102 and the satellite 104 can also be referred to as service link 103. When the UE 102 and the BS 106 have established the service link 103, the UE 102 is said to be in an RRC connected (RRC_CONNECTED) state. After the UE is in the RRC_CONNECTED state, the UE 102 might send a network registration request or other uplink NAS messages to the CN 110 via the NTN node 101 (e.g., the satellite 104 and the BS 106). The satellite 104 communicates the network registration request or other NAS messages to the CN 110 via a feeder link 107 that communicatively couples the satellite 104 to the NTN gateway 108. The CN 110 determines whether to accept or reject the network registration based on user subscription information. Depending on where the UE 102 is located or what RAN is being accessed, the CN 110 might accept or reject the network registration request. The CN 110 provides the network registration accept / reject or other downlink NAS messages to the satellite 104 via the NTN gatew ay 108 and feeder link 107. After registering to the CN 110, the UE 102 can release or suspend the radio connection (e.g., service link 103). An RRC idle (RRC IDLE) state refers to a state where the radio connection is released or not yet established. An RRC inactive (RRC INACTIVE) state refers to a state where the radio connection is suspended. For simplicity7, the term “idle state” is used below to refer to the RRC IDLE state and / or RRC INACTIVE state. The term “connected state” refers to the RRC CONNECTED state.

[0056] The NTN node 101 (sometimes also referred to as a network entity) typically transmits downlink reference signals, e.g., synchronization signal blocks (SSBs) or channel state information reference signals (CSI-RSs), for the UE 102 to utilize to maintain downlink and uplink communication with the NTN node 101. To reduce power consumption, the NTN Node 101 may not transmit some of the SSBs and / or CSI-RSs in the active bandwidth part (BWP) of a serving cell. For example, the NTN Node 101 might implement network energy7saving (NES) techniques in which the NTN Node 101 eliminates or reduces some uplink and downlink transmissions. Cell DTX / DRX is an NES feature for a network entity to inform UEs of the active / non-active pattern of signals for a cell. However, because the legacy cell DTX / DRX configuration is a cell-wide configuration, the cell DTX / DRX configuration cannot provide beam-specific information to indicate active / non-active patterns on a perbeam basis. Furthermore, because legacy cell DTX / DRX configuration is only provided to a UE via dedicated RRC signaling (in RRC connected state), the legacy cell DTX / DRX configuration cannot provide the information to a UE in the RRC IDLE / IN ACTIVE state. Moreover, due to the UE 102 mobility7, the UE 102 may move from one beam to another beam even in the RRC connected state. Legacy techniques for cell DTX / DRX are inadequate or would be difficult to frequently update to support UE mobility among various beams of anNTN node 101. Absent the techniques of this disclosure, a legacy cell DTX / DRX configuration would disrupt the behavior of the UE 102 camping on an NTN node 101 using multiple beam operation. Among other examples, the undesirable behavior could cause more UE power consumption and / or more errors in receiving the DL data.

[0057] In FIG. 1A, the NTN node 101 operates multiple beams (shown as a first beam 124 and a second beam 125). To manage power output and / or conserve energy, the NTN node 101 can operate the beams using discontinuous transmission / reception (referred to as beam DTX / DRX operation). As further described with reference to FIG. IB. each beam can have a different pattern for active / non-active periods. A UE 102 can be located in an area which has partially overlapping or adjacent coverage from both the first beam 124 and the second beam 125. The NTN node 101 can provide 140 one or more beam DTX / DRX configuration(s) to the UE. For example, a first beam DTX / DRX configuration can indicate the active / non- active periods for a first beam 124. A second beam DTX / DRX configuration can indicate the active / non-active periods for a second beam 125. The UE 102 can use the beam DTX / DRX configurations to determine when to monitor a particular beam for downlink signals or when to communicate uplink transmissions to the NTN node 101. For example, the UE 102 can monitor a first physical downlink control channel (PDCCH) of the first beam 124 during an active period of first beam 124.

[0058] FIG. IB shows a diagram 100B of example patterns for beam DTX / DRX operation. The patterns in FIG. IB are provided as an example, and other deployments can have different patterns. In the example of FIG. 1 B, during a first period Ti, a first beam (such as first beam 124 from FIG. 1A) is in the active state (such as an “ON” state). Thus, with respect to the first beam, the first period Ti can be referred to as an ON period. Meanwhile, a second beam (such as second beam 125 from FIG. 1A) can be in a non-active state (such as an “OFF” state). Thus, with respect to the second beam, the first period Ti can be referred to as an OFF period. FIG. IB shows example patterns of a first beam with subframes 1-5 in an ON period and a second beam with subframes 1-5 in an OFF period during the first period Ti. During a second period 75, subframes 6-10 are in the OFF period for the first beam and are in the ON period for the second beam. Although the example of FIG. IB shows the first beam and the second beam having opposite states, other beam DTX / DRX configurations are possible. Each beam can have a different beam DTX / DRX operation based on power limitations, traffic requirements, feeder link capacity, etc. Referring again briefly to FIG. 1A, the beam DTX / DRX configurations 140 can indicate the ON periods and OFF periods of the first beam 124 and the second beam 125.

[0059] The example in FIG. IB shows the beams having alternating ON periods and OFF periods. An OFF period is an example of a non-active state. As further described with reference to FIG. 4A, another example of a non-active state can include a COMMON period. During the COMMON period, an NTN node can transmit some common downlink signals (such as system information, synchronization signals, and / or reference signals). In some aspects, a beam DTX / DRX configuration can indicate ON / OFF / COMMON periods. Alternatively, or additionally, the beam DTX / DRX configuration can indicate whether the NTN node will continue to transmit common downlink signals during a configured OFF period.

[0060] FIG. 2A is a block diagram of an example wireless communication system 200A implementing a BS 106' (on the ground) connecting to a satellite 104 via an NTN gateway 108 using a transparent payload implementation. The example wireless communication system 200A uses one type of NTN deployment referred to as transparent payload architecture, which involves an NTN gateway 108 and a “transparent” satellite 104 for extending the range of a Uu interface. The Uu interface refers to the link between the UE 102 and a base station. In some implementations, the satellite 104 implements a frequency conversion and an RF amplifier in both the uplink and downlink directions. With that being said, the satellite 104 function is similar to that of an analogue RF repeater. As a result, the satellite 104 repeats the Uu radio interface from a feeder link 107 (between the NTN gateway 108 and the satellite 104) to the service link 103 (between the satellite 104 and the UE 102) in the downlink direction and vice versa in the uplink direction. The Satellite Radio Interface (SRI) on the feeder link is the Uu interface, and the NTN gateway 108 supports functions to forward the signal of the Uu interface. The NTN gateway 108 can be placed at the same site as the BS 106' location, or can be connected to the BS 106' at a distance via a wired link. It is also possible to connect more than one NTN gateway 108 to a BS 106'. Different transparent satellites may be connected to the same base station on the ground, via the same NTN gateway, or via different NTN gateways. FIG. 2A also shows a data network 210 that is accessible via the CN 110.

[0061] FIG. 2B shows a block diagram of an example wireless communication system 200B implementing an NTN BS 106 onboard a satellite 104 using a regenerative payload implementation. The BS 106 can perform some or all of the functions of a base station, including those described with reference to BS 106 or BS 106' in this disclosure. The service link (labeled Uu interface) is shown between the UE 102 and the BS 106. In the example of FIG. 3B, the feeder link from the BS 106 to the NTN gateway 108 can be referred to as the SRI. In this example, the SRI is a transport link between the NTN gateway 108 and thesatellite 104 that carries traffic for the Ng (or SI) interface. The NTN gateway 108 at one end of the SRI serves as an intermediate node forwarding the Sl / Ng traffic to and from the CN 110. The Ng interface from the BS 106 includes a portion over the SRI (shown as Ng over SRI) and a portion on the ground. Different regenerative satellites can connect to the same CN 110 on the ground, via the same NTN gateway 108, or via different NTN gateways.

[0062] In some implementations, a first portion of the base station functionality7(shown as BS 106) can be implemented on the satellite 104 while a second portion of the base station functionality (shown as BS 106') can be implemented at a ground entity. For example, in a disaggregated network, BS 106 can be divided into two components: the Distributed Unit (DU) and Centralized Unit (CU). In an example, the BS 106 can operate as a DU that handles baseband processing, including RF signal processing and modulation / demodulation. The BS 106' can be an example CU that manages higher-layer tasks like resource management, scheduling, and network optimization.

[0063] In terms of the satellite moving pattern, there are three ty pes of service links that are supported in NTN:• Earth-fixed: provisioned by beam(s) continuously covering the same geographical areas all the time (e.g., the case of Geostationary Earth Orbit or Geosynchronous Orbit (GEO / GSO) satellites)• Quasi-Earth-fixed: provisioned by beam(s) covering one geographic area for a limited period and a different geographic area during another period (e g., the case of Low Earth Orbit or Medium Earth Orbit (LEO / MEO) satellites capable of using steerable beams), or• Earth-moving: provisioned by beam(s) whose coverage area slides over the Earth surface (e.g., the case of LEO / MEO satellites using fixed or non-steerable beams).

[0064] With LEO / MEO satellites, the satellite 104 can provide either quasi-Earth-fixed cell coverage or Earth-moving cell coverage. With GEO satellites, the satellite 104 can provide Earth fixed cell coverage.

[0065] FIG. 3A shows an example beam DTX / DRX operation for an NTN node 101 operating multiple beams. In FIG. 3A, the NTN node 101 operates four beams to increase the coverage of the NTN cell 120. The beams are labeled "‘beam 1,” "‘beam 2.” "‘beam 3,’?and ‘‘beam 4” for reference purposes. Beam 1 can be an example of the first beam 124 described with reference to FIG. 1A and FIG. IB. Beam 2 can be an example of the second beam 125 described with reference to FIG. 1A and FIG. IB.

[0066] In an example scenario (as a premise for FIG. 3 A), the NTN node 101 has limited power or limited feeder link bandwidth. Based on such limitations, the NTN node 101 canonly activate at most two downlink beams at the same time. During a first time period Ti shown at example 300, the NTN node 101 activates beam 1 and beam 4. For example, the first time period Ti can be a time that includes sfl and sf5 shown with reference to FIG. IB). During a second time period T2 shown at example 301, the NTN node 101 activates a beam 2 and beam 3. For example, the second time period T2 can be a time that includes sf6 and sflO shown with reference to FIG. IB).

[0067] The example beam DTX / DRX operation in FIG. 3A can explain a potential technical advantage of the described beam DTX / DRX configurations. UEs (not shown) located at the coverage areas of beam 2 and beam 3 may not be able to operate normally (e.g., receives downlink traffic, monitor the PDCCH, etc.) during the first time period Ti, since those are non-active (or active below the nominal EIRP) during that time period. Those UEs will resume their normal operations (such as the operations in RRC connected state or monitoring for paging messages) during the second time period T2 where beam 2 and beam 3 once again become active. To make UEs aware of when to pause / resume the communication or monitoring, the NTN node 101 can inform the UEs of the active / non-active pattern of each beam. A beam DTX / DRX configuration can inform the UEs of the active / non-active patterns on a per-beam (or per-beam-group) basis. The beam DTX / DRX configurations enable UEs to act accordingly based on which beam a UE is monitoring or connected. The beam DTX / DRX configurations can provide potential technical advantages such as enabling efficient communication during active periods and preventing UEs from wasting their pow er during the beam non-active periods.

[0068] In FIG. 3A, the various beams are shown as covering different footprints. In some deployments, the various beams can cover adjacent footprints. In some deployments, the footprint of the various beans can be partially or fully overlapping. Thus, it is possible for a UE to be within the coverage area of more than one beam. Since each beam can have a different active / non-active pattern, in some implementations, the NTN node 101 provides beam DTX / DRX configurations to the UE to inform the UE about the active / non-active patterns on a per-beam basis.

[0069] FIG. 3B shows a UE potentially in coverage of multiple beams at various times based on overlapping beams. In the first example 302, coverage of the first beam 124 and the second beam 125 partially overlap. For example, the first beam 124 can have a first orientation and the second beam 125 can have a second orientation. In some implementations, an NTN node can operate multiple beams in the first orientation (such as rows) and multiple beams in the second orientation (such as columns). The designation of rows / columns are for ease of reference and could describe beams having elliptical footprints with a major axis invarious orientations based on elevation angle, altitude, azimuth, etc. The UE 102 can be located in the coverage area of the first beam 124 and the second beam 125. Depending on direction of travel (for the NTN node or the UE), one beam may be better suited for serving the UE 102 compared to the other beams. An NTN node may decide to move the UE 102 from one beam to the other based on channel state information, predicted beam failure, the NTN node moving trajectory, the UE position, or service requirements, among other example criteria. Advantageously, the NTN node can inform the UE 102 regarding the beam DTX / DRX configurations of the various beams (such as the 124 and the second beam 125) that might serve the UE 102 at various active periods.

[0070] In a second example 303, FIG. 3B shows a scenario where coverage areas of various beams are different sizes and may have partially or completely overlapping footprint. For example, a first beam 124 may completely overlap the coverage from a second beam 125. The active / non-active periods of the first beam 124 and the various other beams (including the second beam 125) can vary. For example, the NTN node may configure periodic active periods for the first beam 124 to enable synchronization and paging for idle / inactive UEs. The NTN node may configure longer or shorter active periods for the other beams based on the quantity of UEs and / or traffic flows in other beams where longer active periods are configured for beams having more UEs or higher traffic and shorter active periods are configured for beams having fewer UEs or less traffic.

[0071] FIG. 4A shows example states for beam DTX / DRX operation. The diagram 400 shows three example beam states: an ON state 492, a COMMON state 493, and an OFF state 494. The ON state 492 is an example active state. The COMMON state 493 and the OFF state 494 can be referred to as non-active states (sometimes also referred to as ‘‘inactive'’ states).

[0072] When the NTN node has a particular beam in the ON state 492, the NTN node can transmit control signal and data to a UE via that beam. For a beam in the OFF state 494, the NTN node refrains from transmitting or receiving signals via that beam, such that there is no beam transmission during the non-active period of an OFF state. In some implementations, a beam DTX / DRX configuration can indicate active / non-active periods to refer to the ON / OFF states, respectively.

[0073] In some aspects, an NTN node might continue to transmit limited signaling, such as common signaling for paging and / or system information without user data. Common downlink signals consume less power. Thus, it is possible for an NTN node to satisfy pow er budget constraints or energy savings while still transmitting the common signaling. Thus,this disclosure contemplates a non-active state, referred to as COMMON state 493. that achieves advantages of a non-active period for beam DTX / DRX operation while still providing limited signaling. The COMMON state 493 is referred to as “COMMON” to reflect that the limited downlink signals are broadcast or group-common signals. The COMMON state 493 can be referred to by other terms, such as limited state, power saving (PS) state, partial-active state, or other terms. In some implementations, the COMMON state 493 is a variant of the OFF state 494 where the NTN node continues to transmit limited signaling during the OFF state 494.

[0074] In some implementations, a beam DTX / DRX configuration can indicate a pattern for the ON / OFF / COMMON states, where the periods for the OFF state and the COMMON state are distinctly configured in the beam DTX / DRX configuration. Alternatively, or additionally, the beam DTX / DRX configuration can indicate whether the OFF state includes transmission of limited signaling, such that part or all of the non-active periods of the OFF state operate similar to the described COMMON state 493.

[0075] FIG. 4B shows some potential differences between legacy cell DTX / DRX operation and beam DTX / DRX operation. As shown in block 420, legacy cell DTX / DRX operation applies to an entire cell and is used with connected state UEs for network energy savings. In cell DTX / DRX operation, a serving cell may be configured by RRC with a periodic cell DTX pattern (i.e., active and non-active periods). The cell DTX operation affects UE's monitoring activity of PDCCH and configured downlink assignments in RRC CONNECTED. A serving cell may be configured by RRC with a periodic cell DRX pattern (i.e., active and non-active periods). The cell DRX operation controls scheduling request and configured uplink grant transmission activity in RRC CONNECTED. For all activated serving cells with cell DRX configured and activated, a MAC entity of a UE may transmit configured uplink grant transmissions and scheduling request messages using the cell DRX operation.

[0076] As shown in block 440, a potential technical advantage of beam DTX / DRX configuration is that a beam DTX / DRX configuration enables beam-specific (per beam) DTX / DRX parameters. Thus, the beam DTX / DRX configuration can be more granular than legacy cell DTX / DRX configuration. Furthermore, in some aspects, an NTN node can provide the beam DTX / DRX configuration(s) to UEs that have a variety of RRC states, including as the RRC idle, inactive or connected states.

[0077] FIG. 5A shows example parameters for a beam DTX / DRX configuration 540. The beam DTX / DRX configuration 540 can include a configuration index value 549. In some implementations, the configuration index value 549 corresponds to an index from a set of pre-configured beam DTX / DRX configurations (such as specified in system information or in a technical specification). Alternatively, the configuration index value 549 can be any value that refers to a first unique instance of a beam DTX / DRX configuration 540 to distinguish it from a second unique instance of the beam DTX / DRX configuration 540. An NTN node can indicate the configuration index value 549 in a control signaling message (such as an RRC message) to indicate the unique instance of the beam DTX / DRX configuration 540 that applies to a particular beam.

[0078] In some implementations, the beam DTX / DRX configuration 540 is for DTX only, DRX only, or both DTX and DRX. The beam DTX / DRX configuration 540 can include a configuration type 541 A to indicate whether the beam DTX / DRX configuration 540 applies to beam DTX, beam DRX, or both. Additional example parameters include indications of a periodicity for the active period, such as on duration 54 IB, a start offset 541C, a slot offset 541D, a cycle 541E, and an initial activation status 541F, among other examples. The on duration 541B can indicate the active duration at the beginning of a beam DTX / DRX cycle. The start offset 541 C can indicate the subframe where the beam DTX / DRX cycle starts. The slot offset 541D can indicate the delay before starting the on duration timer. The cycle 541E can indicate the beam DTX / DRX cycle period. The initial activation status 54 IF can indicate the initial activation status of beam DTX / DRX operation.

[0079] In some implementations, the beam DTX / DRX configuration 540 indicates a beam pattern reflecting the time-varying beam status in one of the three states (e.g., {ON, COMMON, OFF} as described with reference to FIG. 4A), where the ‘ON’ state means the beam is operating normally and can be accessed by any legacy UE, the ‘OFF’ state means the beam is completely turned off and hence is not visible to any UE, and the ‘COMMON’ state means the beam transmits only the common signal(s) used for initial access, cell search, paging, and / or random access purposes. A beam transmitting only the common signals is visible to the legacy UE and can be used to transmit the paging message as well as the system information but cannot be used to transmit other dedicated control messages and user data. In some implementations, the on duration 541B timer field and / or a COMMON duration timer field indicate one of the following ON / COMMON duration values in milliseconds {1, 2, 3, 4, 5, 6, 8, 10, 20, 30, 40, 50, 60, 80, 100, 200, 300, 400, 500, 600, 800, 1000, 1200, 1600}. The beam DTX / DRX configuration 540 can include a CycleStartOffset field (e.g., start offset 541 C) indicating one of the following DTX / DRX cycle values in milliseconds {10, 20, 32, 40, 60, 64, 70. 80. 128, 160, 256, 320. 512, 640, 1024, 1280, 2048, 2560. 5120, 10240}, an offset value (e.g., start offset 541C) smaller than the DTX / DRX cycle value (e.g..cycle 541E), and a slot offset field (e.g., slot offset 541D) indicating a slot offset value ranging from 0 to 31.

[0080] In some implementations, the beam DTX / DRX configuration 540 includes a field 545 indicating a time for next ON cycle. For example, the beam DTX / DRX configuration 540 can be a rough beam DTX / DRX configuration that provides minimal information to inform the UE of the next ON duration for a beam where the UE can obtain a full beam DTX / DRX configuration. In some implementations, the field 545 can include an action delay value indicating time or time period (such as a quantity of symbols, milliseconds, seconds, etc.) when the beam DTX / DRX configuration becomes active or when the next ON period starts. In some implementations, the beam DTX / DRX configuration 540 includes an indication 572 to enable a UE to shift a paging occasion when the paging occasion occurs during an OFF period. If enabled, the UE can shift a start time for the paging occasion to a next ON period (or next COMMON period). In some implementations, the beam DTX / DRX configuration 540 includes an indication 594 indicating that the NTN node will transmit common signaling during a configured OFF period (such that the OFF period is similar to the COMMON state 493 described with reference to FIG. 4A). In some implementations, the indication 594 has a value indicating that the NTN node will NOT transmit common signaling during a configured OFF period.

[0081] In some implementations, the beam DTX / DRX configuration 540 includes beam matching information 547. The beam matching information 547 can refer to any information that matches system information 522 or an RRC message and that can identify to which beam or beam group the beam DTX / DRX configuration 540 applies. Examples of beam matching information 547 include a TCI state 546A, a beam ID or index 546B, or an ID or index of related SSB or CSI-RS 546C, among other examples.

[0082] FIG. 5B shows an example technique for configuring and activating beam DTX / DRX configurations. In some implementations, an NTN node can pre-configure a list of candidate beam DTX / DRX configurations (544A, ..., 544D). For example, the NTN node can configure the candidate beam DTX / DRX configurations using RRC signaling (e.g., RRCReconfiguration) or system information. Alternatively, the pre-configured candidate beam DTX / DRX configurations can be specified in a technical specification. Each configuration may include a subset or all of the parameters described with reference to FIG. 5A. In some implementations, a configuration message can include first portion that includes common parameters that applies to multiple beam DTX / DRX configurations and one or more second portions that includes beam-specific parameters for one or more candidate beam DTX / DRX configurations.

[0083] The NTN node can activate a particular one of the candidate beam DTX / DRX configurations (544A, ..., 544D) using control signaling 548. In some implementations, the control signaling 548 can be referred to as a beam DTX / DRX activation indication. For example, the beam DTX / DRX activation indication can refer to one of the candidate beam DTX / DRX configurations (544A, ..., 544D) using a configuration index value 549. The control signaling 548 (e.g., beam DTX / DRX activation indication) can also include beam matching information 547. Thus, the control signaling 548 can reduce signaling overhead by linking a reusable beam DTX / DRX configuration to a particular beam and can dynamically enable or disable beam DTX / DRX operation on a per-beam basis. In some implementations, the control signaling 548 is a DCI field on a PDCCH. Alternatively, or additionally, the NTN node can transmit the control signaling 548 in a MAC CE message or a system information block (SIB) broadcast message. In other implementations, the control signaling 548 is a dedicated RRC message such as the RRC message providing the TCI state configuration or providing the CSI-RS configuration.

[0084] Next, several example scenarios in which a UE and / or a RAN perform the techniques of this disclosure for configuring a UE with the beam-specific active / non- active patterns (e.g., the beam DTX / DRX configurations) of the serving and neighboring beams are discussed with reference to FIGS. 6-11. Generally speaking, similar events in Figs. A-11 are labeled with reference numbers that have the same lower-order digits. For brevity, similar events are not discussed in detail in each instance, but the discussion of a certain event with reference to one of the figures also applies to similar events in other figures.

[0085] FIG. 6A shows an example message flow 600 in which an NTN node 101 provides one or more beam DTX / DRX configuration(s) to a UE 102. The NTN node 101 transmits one or more beam DTX / DRX configurations 640 to the UE 102 via the first beam 124 while the first beam 124 is in an ON state or a COMMON state 695. The beam DTX / DRX configurations 640 can include one or more instances of the beam DTX / DRX configuration 540 described with refence to FIG. 5 A. The NTN node 101 can communicate the beam DTX / DRX configurations 640 via RRC messaging (such as for a UE 102 that is in RRC connected state). Alternatively, or additionally, the NTN node 101 can communicate the beam DTX / DRX configurations 640 via system information (such as for a UE 102 that is in RRC idle / inactive state). System information can refer to a system information block (SIB) broadcast message, such as a SIB type 1 (SIB1), SIB type 19 (SIB19), or a new SIB type. The UE 102 can communicate with the NTN node 101 via the first beam 124 based on the beam DTX / DRX configuration 640 for the first beam 124. For example, the UE 102 can determine the active and non-active periods of the first beam 124 based on the beamDTX / DRX configuration 640. The UE 102 refrains from transmitting uplink signals to the NTN node 101 via the first beam 124 during non-active periods of the first beam 124. The UE 102 can monitor for, and receive, downlink signals from the NTN node 101 during the active periods of the first beam 124.

[0086] In some implementations, the beam DTX / DRX configurations 640 includes the beam DTX / DRX configuration for the second beam 125. In some implementations, the UE 102 receives beam DTX / DRX configurations 640' from the second beam 125, such as if the second beam 125 is in an ON state or COMMON state 695'. In other implementations, the UE 102 receives beam DTX / DRX configurations 640' from the first beam 124 as part of the same information block or message 640, or as a separate information block or message.

[0087] In the example of FIG. 6A. at block 670, the UE 102 switches from the first beam124 to the second beam 125. There may be various reasons the UE 102 switches to the second beam 125. For example, the UE 102 may receive a beam activation indication 660 from the NTN node 101 instructing the UE 102 to switch to the second beam 125. For example, the beam activation indication 660 can be a DCI or MAC CE causing the UE 102 to activate a TCI state for the second beam 125. Alternatively, the UE 102 may switch to the second beam125 based on a beam failure prediction, channel state, or beam (re)selection. In scenarios where the NTN node 101 transmits a beam activation indication 660 to cause the UE 102 to switch to the second beam 125, the NTN node 101 can optionally include a beam DTX / DRX activation indication or beam DTX / DRX configuration of the second beam if not already provided (such as in the beam DTX / DRX configurations 640, 640').

[0088] Based on the beam DTX / DRX configuration of the second beam 125, in some implementations, the UE 102 does not monitor the PDCCH transmission from the second beam 125 immediately after changing to the second beam 125. Instead, the UE 102 monitors 680 the PDCCH transmission from the second beam 125 after the next ON period 698 (or COMMON period) of the second beam 125 has started.

[0089] For ease of illustration, FIG. 6B through FIG. 11 show the first beam 124 and the second beam 125 alternating between ON periods and OFF periods. For example, the first beam 124 has an ON period 692 followed by an OFF period 694. The second beam 125 has an OFF period 696 followed by an ON period 698. In some implementations, the various ON / OFF periods can include a beam operating in a COMMON state. For the implementations and figures that describe common signaling (such as system information), the features can apply to an ON period (as shown in the Fig.) or a COMMON state. Some of the following descriptions refer to a serving beam and non-serving beam. A serving beam refers to a beamon which the LIE is camped. The UE can have an RRC connection on a serving beam. Alternatively, the UE can camp on a serving beam while in the RRC idle / inactive state.

[0090] FIG. 6B shows another example message flow 601 in which an NTN node 101 provides one or more beam DTX / DRX configuration(s) to a UE 102. As with FIG. 6A, the UE 102 can receive beam DTX / DRX configurations 640 from the NTN node 101 via the first beam 124 while the first beam 124 is in an ON period 692 (or COMMON period). The first beam 124 can be associated with an SSB or a CSI-RS. As described in this disclosure, the beam DTX / DRX configuration 640 for the first beam 124 can include only the beam DTX configuration for the first beam 124 or can include beam DTX and DRX configurations 640' for the first beam 124 and other beams (e.g., second beam 125). In some implementations, the beam DTX / DRX configuration is a beam pattern regarding the time-varying beam status in one of the two states {ON, OFF}, where the ‘ON’ state means the beam is operating normally and can be accessed / used by any legacy UE while the ’OFF’ state means the beam is completely turned off and hence is not visible to any UE. In some implementations, the ‘OFF’ state means the beam transmits only the common signal(s) used for the initial access, for the cell search, for the paging, and / or for the random access purposes. In some implementations, the beam DTX / DRX configuration includes an indication specifying whether the ’OFF’ state means the beam transmits only the common signal(s) (such as those used for initial access, cell search, paging, and / or random access purposes) or the beam is completely turned off.

[0091] The UE 102 may also receive beam information about other beams overlapping, adjacent, or close to the first beam 124, including the second beam 125. In some implementations, the other beams overlapping, adjacent, or close to the first beam 124 have the same Physical Cell Identity (PCI) as the first beam 124. In some implementations, the NTN node 101 provides information about the serving / non-serving beams as TCI state configurations. In some implementations, the NTN node 101 provides CSI-RS resource configurations of serving / non-serving CSI-RSs for the serving / non-serving beams. The UE 102 may be configured (via a CSI report configuration 651) to report CSI and hence may transmit a CSI report 652 to the NTN node 101. Based on the CSI report or other information, the NTN node 101 may determine to change the serving beam from the first beam 124 to the second beam 125 for better serving the UE 102, and hence transmits beam activation indication 660 to the UE 102. In some implementations, the beam activation indication 660 can be control signaling, such as a DCI or a MAC CE, for activating the TCI state associated with the second beam 125. In some implementations, the control signaling can indicate (via the logical channel ID (LCID) of the MAC CE, or via a one-bit indication included in theMAC CE) a configuration index value of a pre-configured beam DTX / DRX configuration to activate for the second beam 125. Alternatively, the beam activation indication 660 can include a rough beam DTX / DRX configuration or parameters. Events 651, 652, and 660 may apply to instances where the UE 102 is in an RRC connected stated and might be omitted when the UE 102 is an RRC idle / inactive state.

[0092] At block 670, the UE 102 may change the serving beam to the second beam 125 (i.e., decodes the PDCCH demodulation reference signal (DMRS) based on the same channel property assumption made for second beam 125) and applies the beam DTX / DRX configuration associated with the second beam 125. Based on the beam DTX / DRX configuration of the second beam 125, the UE 102 does not monitor the PDCCH transmission from the second beam 125 immediately after changing the serving beam to the second beam 125, but monitors 680 the PDCCH transmission from the second beam 125 only after the next ON period 698 has started.

[0093] FIG. 7 shows an example message flow 700 including a beam DTX / DRX configuration and a UE in an RRC connected state 730. The UE 102 initially connects to the NTN node 101 via the first beam 124. The first beam 124 can be configured with an SSB or a CSI-RS. While remaining in the connected state 730, the UE 102 receives, via the first beam124, a first beam DTX / DRX configuration 740 for the first beam 124. In some implementations, the first beam DTX / DRX configuration 740 contains only the beam DTX configuration without having the beam DRX configuration. In some implementations, the first beam DTX / DRX configuration 740 indicates a beam pattern regarding the time-varying beam status in one of the two states {ON, OFF}, where the ‘ON’ state means the beam is operating normally and can be accessed / used by any legacy UE while the ‘OFF’ state means the beam is completely turned off and hence is not visible to any UE. In some implementations, the 'OFF’ state means the beam transmits only the common signal(s) used for the initial access, for the cell search, for the paging, and / or for the random access purposes. In some implementations, the first beam DTX / DRX configuration 740 includes an indication specifying whether the ‘OFF’ state means the beam transmits only the common signal(s) (such as those used for initial access, cell search, paging, and / or random access purposes) or the beam is completely turned off.

[0094] In some implementations, the UE 102 also receives, via the first beam 124, one or more beam DTX / DRX configurations for other beams overlapping, adjacent, or close to the first beam 124, including a second beam DTX / DRX configuration 742 for the second beam125. In some implementations, the other beams overlapping, adjacent, or close to the first beam 124 have the same PCI as the first beam 124. In some implementations, the beamDTX / DRX configurations for the serving / non-serving beams are provided together with the TCI state configurations of these serving / non-serving beams. In some implementations, the beam DTX / DRX configurations for the serving / non-serving CSI-RSs are provided together with the CSI-RS resource configurations of these serving / non-serving CSI-RSs. In some implementations, the beam DTX / DRX configurations are provided together and sequentially numbered (i.e., indexed) in a dedicated RRC message / IE or in the system information, and each TCI state configuration or CSI-RS resource configuration refers to one of the index numbers to make an association between the beam DTX / DRX configuration and the beam. In some implementations, the UE 102 may only activate / apply the beam DTX / DRX configurations for the serving / non-serving beams after receiving a beam DTX / DRX activation indication 748 (such as DCI or MAC CE) for activating all or a specific beam DTX / DRX configuration(s). The DCI can be a dedicated DCI (dedicated to the UE 102) or a group-based DCI (common to a group of UEs).

[0095] As described with reference to FIG. 6B, the UE 102 may transmit a CSI report 652 to the NTN node 101. Based on the CSI report or other information, the NTN node 101 may determine to change the serving beam from the first beam 124 to the second beam 125 for better serving the UE 102 and hence transmits control signaling 760 to the UE 102. The control signaling 760 can be a MAC CE for activating the TCI state associated with second beam 125. The control signaling 760 can be similar to the MAC CE described for the control signaling carrying a beam activation indication 660 as described with reference to FIG. 6B. As with FIG. 6A and FIG. 6B. the UE 102 can switch (block 670) to the second beam 125 and start monitoring (block 680) the second beam 125 after the start of the next ON period 698 of the second beam 125. During the ON period 698, the UE 102 can receive updated beam DTX / DRX configurations 784 for other beams adjacent or overlapping the second beam 125.

[0096] FIG. 8 shows an example message flow 800 including a rough beam DTX / DRX configuration and full beam DTX / DRX configuration. Events 730, 640, 652, 670, 680 are the same as described with reference to FIG. 7. The message flow 800 is generally similar to the message flow 700, with the differences discussed below.

[0097] In FIG. 8, the beam DTX / DRX configuration 640 might include the first beam DTX / DRX configuration for the first beam 124 without including beam DTX / DRX configurations for other beams. In the control signaling 860 (such as a MAC CE) for activating the TCI state associated with the second beam 125, the NTN node 101 includes the beam DTX / DRX configuration for the beam being activated (i.e., second beam DTX / DRX configuration for the second beam 125). In some implementations, the second beamDTX / DRX configuration indicates the active / non-active pattern of the second beam 125. Alternatively, the second beam DTX / DRX configuration (in the control signaling 860) is a rough beam DTX / DRX configuration. For example, the control signaling 860 can include a beam DTX parameter that indicates a time instance (or a duration) until which (or during which) the UE 102 does not need to monitor the PDCCH of the second beam 125.

[0098] After receiving the control signaling 860 activating the TCI state associated with second beam 125, the UE 102 may switch (block 670) to the second beam 125. The UE 102 can apply the beam DTX / DRX configuration (from the control signaling 860), such as the time instance / timer indication. Based on the beam DTX / DRX configuration of the second beam 125, the UE 102 delays the monitoring on the PDCCH and starts monitoring (block 680) the PDCCH from the second beam 125 until at or after the beginning of the ON period 698. During the ON period 698, the UE 102 may further receive the full beam DTX / DRX configuration 886 for the second beam 125 via a dedicated RRC message or via the system information. A potential technical advantage of using a rough beam DTX / DRX configuration is reduced signaling overhead, such as when each beam includes full beam DTX / DRX configuration for itself and only limited information about the other beams.

[0099] FIG. 9 shows an example message flow 900 including a beam DTX / DRX configuration included in system information. The message flow 900 is generally similar to the message flow 600, with the differences discussed below; In FIG. 9, NTN node 101 transmits beam DTX / DRX configurations 940 for each beam via system information. Each beam DTX / DRX configuration provided in the system information is either associated with at least an SSB index or at least a CSI-RS resource identity. The system information used to carry the beam-specific beam DTX / DRX configurations can be SIB1. SIB 19, or a new- SIBx with the value x greater than 25. In some implementations, a beam DTX / DRX configuration provided in the system information is associated with more than one SSBs or more than one CSI-RSs, if the beam DTX / DRX configuration is applicable to more than one SSBs / CSI-RSs. In some implementations, the system information can configure a set of candidate beam DTX / DRX configurations that can be activated on a per-beam or per-beam-group basis using a beam DTX / DRX activation indication 948. For example, the beam DTX / DRX activation indication 948 can be in a DCI (such as a group-common DCI). As show n in FIG. 9, the UE 102 can receive system information with one or more beam DTX / DRX configurations 984 after camping on the second beam 125. A potential technical advantage of FIG. 9 is that a UE 102 can receive system information from its currently camped beam to obtain beam DTX / DRX configurations for adjacent or overlapping beams. Furthermore, the UE 102 can receive the system information during RRC idle / inactive state.

[0100] FIG. 10 shows an example message flow 1000 in which a UE 102 monitors a beam based on timing for a next paging occasion (PO) and a beam DTX / DRX configuration. The example of FIG. 10 can be used, for example, when the UE 102 is in an RRC idle / inactive state 1035 and periodically monitors downlink control signals during configured POs to receive paging messages from the NTN node 101. When the NTN node 101 has downlink information for the UE 102, the NTN node 101 transmits a paging DCI scheduling a paging message during the configured PO. FIG. 10 shows an example scenario where a configured PO occurs during an OFF period of a beam on which the UE 102 is camping.

[0101] In FIG. 10, the UE 102 initially is configured to an NTN cell offered by the first beam 124 (which is an SSB beam). In the RRC idle state 1035, the UE 102 receives system information including the beam DTX / DRX configurations 940 of the serving beam (e.g., the first beam 124) and other beams (e.g., the second beam 125). In some implementations, the UE 102 receives a beam DTX / DRX activation indication 948 (such as a group-common DCI) that activates a beam DTX configuration for the first beam 124.

[0102] The UE 102 can determine its POs based on the Paging Channel (PCCH) configuration (i.e., PCCH-Conflg, which is provided in SIB1 system information) and also the UE identity (e.g., 5G-S-TMSI). Typically, the UE 102 will attempt to monitor for the paging message matching the UE identity in the calculated PO. At block 1073, based on beam DTX configurations 940, the UE 102 determines that a next PO occurs during a nonactive period of a first beam 124 and that the next PO occurs during an active period of the second beam 125. For example, the UE 102 determines that the PO paging occasion 1078 will occur within the OFF period 694 of the first beam 124. At block 1074, the UE 102 determines to switch to the second beam 125 since the PO 1078 occurs within an ON period (i.e., the ON period 698) of the second beam 125. Before the paging occasion 1078, the UE 102 switches to the second beam 125. During the paging occasion 1078, the UE 102 monitors the paging channel of the second beam 125 to receive a paging message 1079. The NTN node 101 can replicate paging messages among multiple beams so the UE 102 can receive the paging messages regardless of which beam the UE 102 is currently monitoring.

[0103] FIG. 11 shows an example message flow 1100 in which a UE 102 can shift timing for a PO based on a beam DTX / DRX configuration. In the RRC idle state 1035, the UE 102 receives the beam DTX / DRX configuration 940 of the serving beam (e.g., the first beam 124) and other beams. As described with reference to FIG. 10. the UE 102 can determine that a paging occasion 1078 occurs during an OFF period 694 of the first beam 124. At block 1176, the UE 102 determines to shift the PO 1078 based on the beam DTX / DRX configurations 940. In some implementations, UE 102 may receive an indication in system information1172 indicating whether and / or how the UE 102 is allowed to shift a PO. For example, the indication can inform the UE 102 to shift the PO to the next ON period (or COMMON period) of its current serving beam. Alternatively, or additionally, the indication can inform the UE 102 to shift the PO to a next ON / COMMON period of any available beam. Alternatively, or additionally, the indication in system information 1172 (or in a beam DTX / DRX configuration 940) can indicate whether PO shifting is enabled at the NTN node 101. Based on the indicator (if present) and the beam DTX / DRX configuration 940, at block 1176, the UE 102 determines to shift the PO 1078 to a later time (shown as shifted paging occasion 1178). In the example of FIG. 11, the shifted paging occasion 1178 aligns with the beginning of the next ON period 692 of the first beam 124. In some implementations, the system information 1172 can indicate other techniques or timing for shifting the PO, for instance, the shifted paging occasion 1178 is the first PO (may belong to other UEs) occurring after the ON period 692 of the first beam 124. While FIG. 11 shows the shifted paging occasion 1178 occurring during the ON period 692 of the first beam 124, in other implementations, the shifted paging occasion 1 178 is shifted to occur in anext available ON period of any available beam.

[0104] The descriptions of FIG. 12 to FIG. 20 provide several example operations for implementing the techniques of this disclosure. The example operations enable an NTN node to configure a UE with the beam-specific active / non-active patterns (e.g., the beam DTX / DRX configurations). Generally speaking, similar events in Figs. 12-20 are labeled with reference numbers that have the same lower-order digits. For brevity, similar events are not discussed in detail in each instance, but the discussion of a certain event with reference to one of the figures also applies to similar events in other figures. Some operations of FIG. 12 to FIG. 20 are described for a UE in the connected state and using RRC messages. However, the concepts can also be adapted to a UE in RRC idle / inactive state and using common signaling. Furthermore, the descriptions of FIG. 12 to FIG. 20 refer to a base station (BS) in communication with the UE. The BS can be, for example, the BS 106 or the BS 106' described herein. Furthermore, it should be apparent that in an NTN, any messages to or from a BS are received or transmitted by an NTN node. Thus, reference to BS in FIG. 12 to FIG. 20 can be replaced by NTN node, network entity, satellite, or similar terms.

[0105] FIG. 12 shows a flow chart diagram with example operations 1200 of a UE (e.g., the UE 102 in this disclosure). Initially, the UE operates 1240 in the connected state and receives, from the BS, the beam DTX / DRX configuration associated with the first beam serving the UE. The beam DTX / DRX configuration can include any of the features or parameters described with reference to the beam DTX / DRX configurations 140, 440, 540, 640, 740, 940.In some implementations, the beam DTX / DRX configuration is received in an RRC message. In some implementations, the beam DTX / DRX configuration is a beam pattern regarding the time-varying beam status in one of the two states {ON, OFF}, where the ‘ON’ state means the beam is operating normally and can be accessed / used by any legacy UE while the ‘OFF’ state means the beam transmits only the common signal(s) used for initial access, cell search, paging, and / or random access purposes. In some implementations, the beam DTX / DRX configuration includes an indication specifying whether the ‘OFF’ state means the beam transmits only the common signal(s) (used for the initial access, cell search, paging, and / or random access purposes) or the beam is completely turned off. In some implementations, the beam DTX / DRX configuration is a beam pattern reflecting the time-varying beam status in one of the three states {ON, COMMON, OFF}, where the ‘ON’ state means the beam is operating normally and can be accessed by any legacy UE, the ‘OFF’ state means the beam is completely turned off and hence is not visible to any UE, and the ‘COMMON’ state means the beam transmits only the common signal(s) used for the initial access, cell search, paging, and / or random access purposes. After receiving the beam DTX / DRX configuration for the first beam, the UE may further receive 1248 a DCI activating the beam DTX / DRX configuration for the first beam or activating the beam DTX / DRX configurations for all beams.

[0106] Based on the beam DTX / DRX configuration of the first beam, the UE skips monitoring 1258 the PDCCH of the first beam and ignores the configured uplink resources during the non-active period (i. e. , the OFF period). If the non-active period is a COMMON period the UE may monitor the first beam's PDCCH for common signaling. The UE receives 1242 from the BS an RRC message including the beam DTX / DRX configurations associated with a second beam. In some implementations, the beam DTX / DRX configuration contains only the beam DTX configuration without having the beam DRX configuration.

[0107] The UE receives 1260, from the BS, an RRC message or a MAC CE activating the TCI state of the second beam for the PDCCH monitoring. Note that prior to block 1260, the UE may have already received the TCI state configuration for the second beam from the BS. In some implementations, the RRC message or the MAC CE at block 1260 also indicates the activation of the beam DTX / DRX configuration for the second beam. Based on the RRC message or the MAC CE at block 1260, the UE switches 1270 from the first beam to the second beam for the PDCCH monitoring. The UE also implements, in its communication unit, active / non-active periods of the beam DTX / DRX configuration associated with the second beam. The UE monitors 1280 the PDCCH of the second beam starting from the first ON period after switching to the second beam.

[0108] FIG. 13 shows a flow chart diagram with example operations 1300 of a UE in which a TCI state configuration can indicate a beam DTX / DRX configuration. The operations 1300 enable a UE to switch from a first beam to a second beam and implement the active / non- active (i. e. , ON / OFF) pattern of the second beam based on the beam DTX / DRX configuration included or associated with the TCI state configuration of the second beam. The flow diagram in FIG. 13 is similar to that in FIG. 12, except in FIG. 13, the UE obtains 1355 the beam DTX / DRX configuration of the second beam from the TCI state configuration associated with the second beam. In some implementations, the beam DTX / DRX configuration of the second beam is directly included in the TCI state configuration associated with the second beam. In another implementation, all the beam DTX / DRX configurations are sequentially numbered (i.e., indexed) and provided together in a separate RRC message / IE, and the TCI state configuration associated with the second beam includes an index number referring to the beam DTX / DRX configuration used by the second beam.

[0109] FIG. 14 shows a flow chart diagram with example operations 1400 of a UE in which the beam DTX / DRX configuration is provided in system information. The flow diagram in FIG. 14 is similar to that in FIG. 12, except in FIG. 14, the UE obtains 1440 the beam DTX / DRX configurations of the first beam and the second beam from the system information, instead of obtaining these configurations from dedicated RRC messages. The UE receives 1455, from the BS, an RRC message including the TCI state configuration of the second beam. In some implementations, the TCI state configuration can refer to, or include, a beam DTX / DRX configuration. The UE receives 1260 an RRC message or MAC CE activating the TCI state of the second beam. Thereafter, the UE can switch (block 1270) to the second beam and monitor (block 1280) the PDCCH of the second beam based on the beam DTX / DRX configuration, as described with reference to FIG. 12.

[0110] FIG. 15 shows a flow chart diagram with example operations 1500 of a UE that receives control signaling for a beam change, where the control signaling optionally includes a delay timer indicating when to begin monitoring the new beam. The UE operates 1240 in the connected state, and receives from the BS, an RRC message including the beam DTX / DRX configuration associated with the first beam serving the UE. Based on the beam DTX / DRX configuration of the first beam, the UE may skip 1258 monitoring the PDCCH of the first beam and ignore the configured uplink resources during the non-active period (i.e., the OFF period). During the active period (i.e., the ON period), the UE may also receive 1455, from the BS, an RRC message including the TCI state configuration associated with the second beam. The UE may receive 1560, from the BS, a MAC CE activating the TCI state associated with the second beam for the PDCCH monitoring. The flow proceeds to thedecision block 1561, where the HE determines whether the MAC CE activating the TCI state includes an action delay value indicating time or time period. For example, the time can be a fixed or relative time. The time period can be a quantity of symbols, subframes, slots. In some implementations, the time period can be based on a time interval, such as transmission time intervals (TTIs). milliseconds, or seconds. The action delay value can indicate a delay before the beam DTX / DRX configuration is active.[OHl] If the determination at block 1561 is negative (i.e., the MAC CE activating the TCI state does not indicate a time or time period), the flow proceeds to the block 1571, where the UE may switch from the first beam to the second for the PDCCH monitoring and start monitoring the PDCCH. The UE may further receive 1584, from the BS, an RRC message including the beam DTX / DRX configuration associated with the second beam. On the other hand, if the determination at block 1561 is positive (i.e., the MAC CE activating the TCI state does indicate a time or time period), the flow proceeds to the block 1570, where the UE may switch from the first beam to the second beam and refrain from immediately monitoring the PDCCH. Instead, the UE monitors 1580 the PDCCH of the second beam, starting from the time or after the time period indicated in the MAC CE or upon the expiry of a timer indicated in the MAC CE. By monitoring the PDCCH of the second beam, the UE may receive 1584, from the BS, an RRC message including the beam DTX / DRX configuration associated with the second beam.

[0112] FIG. 16 shows a flow chart diagram with example operations 1600 of a UE that can determine which beam to monitor for a next PO based on a beam DTX / DRX configuration. In some implementations, a UE in the idle state can implement the operations 1600 to switch from one beam to another beam for paging monitoring, based the beam DTX / DRX configurations of the beams. Initially, the UE operates 1640 in the idle state and receives from the BS, a system information including the beam DTX / DRX configurations for more than one beam, including the serving beam (i.e., the beam the UE is currently camping on). Optionally, the UE may also receive 1248, from the BS, a group-based DCI activating a specific or all beam DTX / DRX configuration(s).

[0113] The UE operating in the idle state may also determine 1672 the next paging occasion for paging monitoring, based on the PCCH configuration and the UE identity7. The UE may determine 1673A whether the next PO falls within a non-active period (i.e., the OFF period) of the serving beam. If the determination at block 1673 A is negative (i.e.. the next PO overlaps with or falls within an active period of the serving beam), the flow proceeds to the block 1678, where the UE stays in the serving beam and monitors for the paging in the next PO

[0114] On the other hand, if the determination at block 1673A is positive (i. e. , the next PO falls within an OFF period), the flow proceeds to another decision block 1673B, where the UE may determine if next PO overlaps with any of the active periods (i.e., the ON periods or the COMMON periods) of the beams that are reachable for the UE. If the determination of the decision block 1673B is positive, the UE may switch 1674 to the best beam (where best may be quantified in terms of reference signal received power (RSRP) or reference signal received quality (RSRQ)) whose active period overlaps with the next PO and then monitors for the paging in the next PO on the best beam. On the other hand, if the determination at block 1673B is negative, the flow proceeds to the block 1679, where the UE remains in the serving beam.

[0115] FIG. 17 shows a flow chart diagram with example operations 1700 of a UE that can shift timing of a next PO based on a beam DTX / DRX configuration. In some implementations, the operations 1700 enable a UE in the idle state to shift a PO based the beam DTX / DRX configuration of the serving beam and a PO shifting indication provided in the system information. The UE may operate 1640 in the idle state, and receive from the BS, a system information including the beam DTX / DRX configurations for more than one beam including the serving beam (i.e., the beam the UE is currently camping on). The UE may also receive 1248, from the BS, a group-based DCI activating either a specific or all beam DTX / DRX configuration(s). The UE may also receive 1772, from the BS, a system information including a flag or an IE indicating that the network supports shifting a PO. The UE may also determine 1672 the next paging occasion for paging monitoring, based on the PCCH configuration and the UE identity'.

[0116] The UE may determine 1673A whether the next PO falls within a non-active period (i.e., the OFF period) of the serving beam. If the determination at block 1673A is negative (i.e., the next PO overlaps with or falls within an active period of the serving beam), the flow proceeds to the block 1678, where the UE remains in the serving beam and monitors for the paging in the next PO. On the other hand, if the determination at block 1673A is positive (i.e., the next PO completely falls within an OFF period of the serving beam), the flow proceeds to the block 1778. where the UE may disregard the next PO and monitor for the paging in the first PO overlapping with the earliest active period (i.e., the earliest ON period or COMMON period) after the next PO, where the first PO overlapping with the earliest active period may not be the PO belonging to the UE according to the PO calculation based on the PCCH configuration and the UE identity.

[0117] The descriptions of FIG. 18 to FIG. 20 provide several example operations of an NTN node implementing aspects of this disclosure. An NTN node (e.g., a BS 106, BS 106',satellite 104, or any combination) can implement the operations of FIG. 18 to FIG. 20 to implement network-side aspects of beam DTX / DRX configuration(s) for multiple beam operation.

[0118] FIG. 18 shows a flow chart diagram with example operations 1800 of an NTN node that transmits a beam DTX / DRX configuration. The operations 1800 can be implemented by a BS (e.g., BS 106 or BS 106' in this disclosure) of an NTN node (e.g., NTN node 101). Initially, the BS transmits 1840, to a UE, via a dedicated RRC message or a system information, a beam DTX / DRX configuration of the beam serving the UE. Later or at the same time, the BS transmits 1842, to the UE, via a dedicated RRC message or a system information, the beam DTX / DRX configurations of one or more beams overlapping, adjacent, or close to the beam serving the UE. In some implementations, the beams overlapping, adjacent, or close to the beam serving the UE may have the same PCI as the beam serving the UE. In some implementations, the beam DTX / DRX configurations for the serving / non- serving beams are provided together with the TCI state configurations of these serving / non- serving beams. In some implementations, the beam DTX / DRX configurations for the serving / non-serving CSI-RSs are provided together with the CSI-RS resource configurations of these serving / non-serving CSI-RSs. In some implementations, all the beam DTX / DRX configurations are provided together and sequentially numbered (i.e., indexed) in a dedicated RRC message / IE or in the system information, and each TCI state configuration or CSI-RS resource configuration refers to one of the index numbers to make an association between the beam DTX / DRX configuration and the beam.

[0119] The BS may also transmit 1848, to the UE, a DCI either for activating the beam DTX / DRX configuration for the serving beam or activating the beam DTX / DRX configurations for all the serving / non-serving beams, where the DCI may be a dedicated DCI (dedicated to the UE) or a group-based DCI (common to a group of UEs). After that, the BS determines 1859 to switch the serving beam of the UE to another beam (e.g., overlapping or adjacent to the serving beam). The BS transmits 1860 to the UE, a MAC CE used to activate the TCI state associated with the new serving beam for the PDCCH monitoring, where the MAC CE may indicate the activation of the beam DTX / DRX configuration for the new serving beam.

[0120] FIG. 19 shows another flow chart diagram with example operations 1900 of an NTN node (e.g.. BS 106 or BS 106' in this disclosure). A BS can implement the example operations 1900 to inform a UE of the beam DTX / DRX configuration of a new serving beam upon changing the serving beam for the UE. The BS transmits 1840, to a UE, via a dedicated RRC message or a system information, a beam DTX / DRX configuration of the beam serving theUE. The BS may also transmit, to the UE, at block 1948. a DC1 for activating the beam DTX / DRX configuration for the serving beam, where the DCI can be a dedicated DCI (dedicated to the UE) or a group-based DCI (common to a group of UEs). The BS determines 1859 to switch the serving beam of the UE to another beam (e.g., overlapping or adjacent to the serving beam). The BS transmits 1960 to the UE. a MAC CE used to activate the TCI state associated with the new serving beam for the PDCCH monitoring. The MAC CE may further include a beam DTX / DRX configuration for the new serving beam. In some implementations, the beam DTX / DRX configuration includes one or more parameters described with reference to FIG. 5A. In some implementations, the beam DTX / DRX configuration is a rough beam DTX / DRX configuration that includes a time or time period informing the UE wait to monitor the PDCCH until the specified time or a duration of the time period.

[0121] FIG. 20 shows a flow chart diagram with example operations 2000 of an NTN node that shifts timing of a PO based on a beam DTX / DRX configuration. The NTN node (e.g., BS) can shift a paging occasion to occur during the active period of an adjacent or overlapping beam. The BS transmits 1840, to a UE, via a dedicated RRC message or a system information, a beam DTX / DRX configuration of the beam serving the UE. At block 2072, the BS transmit, to the UE, a system information including a flag or an IE indicating that the network supports shifting POs. The BS receives 2073A, from the core network, a paging message used to page a UE. The BS calculates 2073B the next PO for the UE based on the PCCH configuration and the UE identity. The BS shifts 2074, for the UE being paged, the next PO on a first beam to the first PO overlapping with the earliest ON period if the next PO on the first beam does not overlap with an ON period of the first beam. Note that the BS may need to perform the shifting 2074 once per beam. The BS transmits 2078, to the UE, on each beam, the paging message including the UE's identity in the PO overlapping with the ON period of the beam, where the PO may be UE’s next PO or the PO being shifted (and hence not belonging to the UE).

[0122] FIG. 21A shows an example control plane protocol stack 2100A for a regenerative NTN architecture in accordance with aspects of this disclosure. The diagram of the NTN control plane protocol stack 2100 A shows the NR-Uu interface (e.g., via a service link) between the satellite 104 (e.g., the BS 106) and the UE 102. The NR-Uu includes a radio resource control (RRC) protocol in addition to the PDCP, RLC, MAC, and PHY layers. The Ng-C interface is between the BS 106 and the CN 110. The example CN 110 in FIG. 21 A can illustrate the operation of an access and mobility function (AMF) of the 5GC. In 3GPP standards (e.g., the 3GPP technical specification (TS) 24.501 version 18.4.0), refer to an N1interface. The diagram of the NTN control plane protocol stack 2100 A shows the N1 interface between the NAS layer of the UE 102 and the NAS layer of the CN 110. The N1 interface links the UE 102 and the AMF of the CN 110 via an access network. In FIG. 21 A, the access network includes the NTN (such as the satellite 104, BS 106) coupled by the NTN gateway 108.

[0123] The example illustrated in FIG. 21 A shows the BS 106 as a gNB. However, FIG. 21A could be modified to describe a scenario in which the BS 106 is an eNB. The CN 110 can illustrate the operation of a mobility management entity (MME) of an EPC. For example, if the radio access technology for the NTN RAN is E-UTRA or NB-IoT, the Ng-U interface can be referred to as an SI -MME interface. The Nr-Uu can be referred to as an LTE-Uu interface.

[0124] FIG. 21B shows an example control plane protocol stack 2100B for a transparent NTN architecture in accordance with aspects of this disclosure. As with FIG. 21 AA, the NTN control plane protocol stack 2100B illustrated in FIG. 2 IB is also similar to that of a TN, with the addition of the satellite 104 and the NTN gateway 108 being placed in the NR-Uu interface.

[0125] FIG. 22 is a block diagram of example distributed or disaggregated implementation of an example base station 2206 (such as BS 106) using a centralized unit (CU) and a distributed unit (DU). In this implementation, the BS 2206 includes a CU 2215 and one or more distributed units (DUs) 2216. In some implementations a terrestrial base station portion BS 106’ houses the CU 2215 while a satellite base station portion BS 106 houses the DU 2216. See FIGs. 1A and 2B. In other implementations terrestrial base station BS 106’ houses both the CU and DU (see FIG. 2A), and in yet other implementations the satellite base station BS 106 houses both the CU and DU. The CU 2215 includes processing hardware, such as one or more general-purpose processors (e.g., CPUs) and a computer- readable memory storing machine-readable instructions executable on the general-purpose processor(s), and / or special-purpose processing units. For example, the CU 2215 can include a PDCP controller, an RRC controller and / or an RRC inactive controller. In some implementations, the CU 2215 can include a radio link control (RLC) controller configured to manage or control one or more RLC operations or procedures. In further implementations, the CU 2215 does not include an RLC controller.

[0126] Each of the DUs 2216 also includes processing hardware that can include one or more general-purpose processors (e g., CPUs) and computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors,and / or special-purpose processing units. For example, the processing hardware can include a MAC controller configured to manage or control one or more MAC operations or procedures (e.g., a random access procedure), and / or an RLC controller configured to manage or control one or more RLC operations or procedures. The process hardware can also include a physical layer controller configured to manage or control one or more physical layer operations or procedures.

[0127] In some embodiments, a RAN supports Integrated Access and Backhaul (IAB) functionality. In some implementations, the DU 2216 operates as an lAB-node, and the CU2215 operates as an lAB-donor. In some embodiments, the RAN supports NTN functionality.

[0128] In some implementations, the CU 2215 can include a logical node CU control plane (CU-CP 2215A) that hosts the control plane part of the PDCP protocol of the CU 2215. The CU 2215 can also include logical node(s) referred to as a CU user plane (CU-UP 2215B) that hosts the user plane part of the PDCP protocol and / or Service Data Adaptation Protocol (SDAP) protocol of the CU 2215. The CU-CP 2215A can transmit control information (e.g., RRC messages, Fl application protocol messages), and the CU-UP 2215B can transmit the data packets (e.g., SDAP PDUs or Internet Protocol packets).

[0129] The CU-CP 2215A can be connected to multiple CU-UP 2215B through the El interface. The CU-CP 2215A selects the appropriate CU-UP 2215B for the requested services for the UE 102. In some implementations, a single CU-UP 2215B can connect to multiple CU-CP 2215A through the El interface. The CU-CP 2215A can connect to one or more DU(s)2216 through an Fl-C interface. The CU-UP 2215B can connect to one or more DU(s) 2216 through the Fl-U interface under the control of the same CU-CP 2215A. In some implementations, one DU 2216 can connect to multiple CU-UP 2215B under the control of the same CU-CP 2215A. In such implementations, the connectivity between a CU-UP 2215B and a DU 2216 is established by the CU-CP 2215A using Bearer Context Management functions.

[0130] The CU-CP(s) 2215A generates the carrier frequency configurations (such as frequency and timing information) in the system information messages (such as SIB2 or SIB4) and provides the system information messages to the DU(s) 2216. The DU(s) 2216 passes these SIBs to lower layers (such as a physical layer (PHY), baseband unit (BBU) or radio head unit (RRH)) for a broadcast transmission. Similarly, the CU-CP(s) 2215A generates the NTN neighbor cell configuration (in SIB19) and, in some instances, the configuration of NTN-specific triggering conditions and provides that information to the DU(s) 2216 for transmission.

[0131] FIG. 23 shows a block diagram of an example wireless communication system 2300 showing hardware features and communication interfaces. The depicted hardware configurations may omit certain components well-understood to be frequently implemented in such electronic devices, such as displays, peripherals, power supplies, and the like. The wireless communication system 2300 includes the same elements as described with reference to FIG. 1A, including the UE 102, the BS 106, the satellite 104, and the CN 110. In some implementations, the UE 102 can support at least a 5G NR (or simply, “NR”) or E-UTRA air interface to communicate with the BS 106. The BS 106 connects to the CN 110 via an interface (e.g.. SI or NG interface). The BS 106 can connect to other base stations (including the BS 106' or the BS 2308) via an interface (e.g., X2 or Xn interface) for interconnecting NG RAN nodes. In Fig. 23, the BS 2308 operates a terrestrial network (TN) cell 2309.

[0132] The BS 106 is equipped with processing hardware 2306 that can include a receiver 2316B configured to receive data in the uplink direction. The processing hardware 2306 can also include a transmitter 2316A configured to transmit data in the downlink direction. The processing hardware can include one or more general-purpose processor(s) 2316C (e.g., CPUs) and a non-transitory computer-readable memory (CRM) 2316D storing instructions that the one or more general-purpose processors execute. Additionally, or alternatively, the processing hardware 2306 can include special -purpose processing units. The processor 2316C may include, for example, one or more central processing units, graphics processing units (GPUs), or other application-specific integrated circuits (ASICs), and the like. CRM 2316D may include any suitable memory or storage device such as random-access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NVRAM), read-only memory (ROM), or Flash memory usable to store device data of the BS 106. The satellite 104 can include processing hardware 2304, such as a transmitter 2314A, a receiver 2314B, a processor 2314C, and CRM 2314D (similar to components 2306, 2316A, 2316B, 2316C and 2316D of the BS 106). In some implementations, the components 2314A. 2314B, 2314C and 2314D are shared or commonly implemented with the components 2316A, 2316B, 2316C and 2316D. The BS 2308 can include generally similar components (not shown) as the processing hardware 2306.

[0133] The UE 102 is equipped with processing hardware 2302 that can include one or more general-purpose processors such as CPUs and non-transitory computer-readable memory 2312D storing machine-readable instructions executable on the one or more general-purpose processors, and / or special-purpose processing units. The processing hardware 2302 can also include a transmitter 2312A configured to transmit data in the downlink direction. The processing hardware further can include a receiver 2312B configured to receive data in theuplink direction. The processing hardware 2302. in an example implementation, includes a processor 2312C to process data that the UE 102 will transmit in the uplink direction or process data received by UE 102 in the downlink direction. The processor(s) 2312C may include, for example, one or more central processing units, GPUs, or other ASICs, and the like. To illustrate, the processor(s) 2312C may include an application processor (AP) utilized by the UE 102 to execute an operating system and various user-level software applications, as well as one or more processors utilized by modems or a baseband processor. The CRM 2312D may include any suitable memory or storage device such as RAM, SRAM, DRAM, NVRAM, ROM, Flash memory, SSD or other mass-storage devices, and the like useable to store one or more sets of executable software instructions and associated data that manipulate the one or more processor(s) 2312C and other components of the processing hardware 2302 to perform the various functions described herein and attributed to the UE 102. The sets of executable software instructions include, for example, an operating system (OS) and various drivers (not shown), and various software applications (not shown), which are executable by processor(s) 2312C to enable user-plane communication, control-plane signaling, and user interaction with the UE 102.

[0134] The CN 110 can be an Evolved Packet Core (EPC) and / or a 5G core (5GC). Among other components, the EPC can include a Serving Gateway (SGW), a Mobility Management Entity (MME), a Home Subscriber Server (HSS), and a Packet Data Network Gateway (PGW). The SGW in general is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., and the MME is configured to manage authentication, registration, paging, and other related functions. The PGW provides connectivity from the UE to one or more external packet data networks, e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network. The 5GC includes a User Plane Function (UPF), a Unified Data Management (UDM), an Access and Mobility Management Function (AMF), and / or Session Management Function (SMF). Generally speaking, the UPF is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., the AMF is configured to manage authentication, registration, paging, and other related functions, and the SMF is configured to manage PDU sessions. The HSS and the UDM store and maintain subscription information regarding the UE 102. The CN 110 can be implemented by one or more processing elements (shown as processing hardware 2310). The processing hardware 2310 can include a transmitter 2311 A, a receiver 231 IB, a processor 2311C, and a CRM 231 ID, similar to corresponding components described with reference to processing hardware 2302, 2304. and 2306.

[0135] The transmitters 2312A, 2314A, 2316A, and 2311A and receivers 2312B. 2314B, 2316B, and 231 IB are examples of a communication unit. The processors 2312C, 2314C, 2316C, and 2311C can also be referred to as a processing system. Other examples of a communication unit and a processing system are possible, including some examples that are commonly used in awireless communication system. The BS 106, UE 102, satellite 104. and CN 110 can include other components not illustrated in FIG. 23. Similarly, the UE 102 can include a system information interpretation unit capable of interpreting any of the example system information described in this disclosure. The UE 102 can also include an RRC management unit that can operate an RRC IN ACTIVE or RRC SUSPENDED based on information from the BS 106 to transition to an RRC suspended state. The system information interpretation unit and / or the RRC management unit can be implemented by a processing system and communication unit of the UE 102.

[0136] FIG. 1 A through FIG. 23 and the operations described herein are examples meant to aid in understanding example implementations and should not be used to limit the potential implementations or limit the scope of the claims, some implementations may perform additional operations, fewer operations, operations in parallel or in a different order, and some operations differently.

[0137] Aspects of the subject matter described in this disclosure can be implemented as a computer-readable medium having stored therein instructions which, when executed by a processor, causes the processor to perform any one of the above-mentioned functionalities. Aspects of the subject matter described in this disclosure can be implemented as a system having means for implementing any one of the above-mentioned functionalities. Aspects of the subject matter described in this disclosure can be implemented as an apparatus having one or more processors configured to perform one or more operations from any one of the above- mentioned functionalities.

[0138] The following additional considerations may apply to the foregoing and the following discussions. Generally speaking, description for one of the above figures can apply to another of the above figures. Any event or block described above can be optional. For example, an event or block with dashed lines can be optional. In some implementations, “message’' is used and can be replaced by “information element (IE),” and vice versa. In some implementations, “IE” is used and can be replaced by “field,” and vice versa. In some implementations, “configuration” can be replaced by “configurations” or “configuration parameters,” and vice versa. In some implementations, “some” means “one or more.” In some implementations, “at least one” means “one or more.” The “eNB” can be replaced by “base station,” “gNB,” “6G base station,” “evolved gNB,” or 6G gNB. “MME” can bereplaced by AMF or evolved AMF or 6G AMF. “Core network (CN)” can be replaced by EPC, 5GC or 6GC.

[0139] Some examples of this disclosure refer to RRC messages for illustrative purposes. In the various figures and descriptions, some RRC messages can be replaced by other examples. For example, “RRC Connection Request message” can be replaced by “RRC Setup Request message.” “RRC Connection Setup message” can be replaced by “RRC Setup message.” “RRC Connection Setup Complete message” can be replaced by “RRC Setup Complete message.” “RRC Connection Reconfiguration message” can be replaced by “RRC Reconfiguration message.” “RRC Connection Reestablishment Request message” can be replaced by “RRC Reestablishment Request message.” “RRC Connection Reestablishment message” can be replaced by “RRC Reestablishment message.” “RRC Connection Reestablishment Complete message” can be replaced by “RRC Reestablishment Complete message.” “RRC Connection Resume Request message” can be replaced by “RRC Resume Request message.” “RRC Connection Resume message” can be replaced by “RRC Resume message.” “RRC Connection Resume Complete message” can be replaced by “RRC Resume Complete message.” “NAS Attach Request message” or “TAU Request message” can be replaced by “Registration Request message.” “NAS Attach Accept message” or “TAU Accept message” can be replaced by “Registration Accept message.”

[0140] Unless defined otherwise, technical and scientific terms used herein have the same meaning as is commonly understood by one of ordinary skill in the art to which this specification belongs. The terms “first,” “second,” and the like, as used herein do not denote any order, quantity, or importance, but rather are used to distinguish one element from another. The use of terms “including,” “comprising” or “having” and variations thereof herein are meant to encompass the items listed thereafter and equivalents thereof as well as additional items. The terms “connected” and “coupled” are not restricted to physical or mechanical connections or couplings and can include electrical connections or couplings, whether direct or indirect. Furthermore, terms “circuit” and “circuitry ” and “control unit” may include either a single component or a plurality of components, which are either active and / or passive and are connected or otherwise coupled together to provide the described function. In addition, the term operationally coupled as used herein includes wired coupling, wireless coupling, electrical coupling, magnetic coupling, radio communication, software based communication, or combinations thereof.

[0141] Some or all of the foregoing or the following implementations can be jointly combined or formed to be a new or another one implementation. The foregoing or the following techniques can be used to solve at least (but not limited to) the issue(s) orscenario(s) mentioned in this disclosure. Any two or more than two of the foregoing or the following paragraphs, (sub)-bullets, points, actions, or claims described in each method / technique / implementation may be combined logically, reasonably, and properly to form a specific method. Any sentence, paragraph, (sub)-bullet, point, action, or claim described in each of the foregoing or the following technique(s) / implementation(s) / concept(s) may be implemented independently and separately to form a specific method. Dependency, such as “based on,” “more specifically,” “where” or etc., in technique(s) / implementation(s) / concept(s) mentioned in this disclosure is just one possible implementation which would not restrict the specific method.

[0142] As used herein, the terms “user device”, “user equipment” (for example, UE 102), “wireless communication device”, “mobile communication device”, “communication device”, or “mobile device” refer to any one or all of cellular telephones, smartphones, portable computing devices, personal or mobile multi-media players, laptop computers, tablet computers, smartbooks, Intemet-of- Things (loT) devices, palm-top computers, wireless electronic mail receivers, multimedia Internet enabled cellular telephones, wireless gaming controllers, display sub-systems, driver assistance systems, vehicle controllers, vehicle system controllers, vehicle communication system, infotainment systems, vehicle telematics systems or subsystems, vehicle display systems or subsystems, vehicle data controllers, point- of-sale (POS) terminals, health monitoring devices, drones, cameras, media-streaming dongles or another personal media devices, wearable devices such as smartwatches, wireless hotspots, femtocells, broadband routers or other types of routers, and similar electronic devices which include a programmable processor and memory and circuitry configured to perform operations as described herein. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an internet-of-things (loT) device or a mobile-internet device (MID). Depending on the type, the user device can include one or more general-purpose processors, a computer- readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0143] Certain techniques are described in this disclosure as including logic or a number of components or modules. Modules can be software modules (e.g, code, or machine-readable instructions stored on non-transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module can comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit(ASIC), a digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry’ (e.g., configured by software) may be driven by cost and time considerations.

[0144] When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. The software can be executed by one or more general-purpose processors or one or more special-purpose processors.

[0145] As used herein, the terms "‘component” and “module” are intended to be broadly construed as hardware, firmware, or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, or a combination of hardware and software. As used herein, the phrase “based on” is intended to be broadly construed to mean “based at least in part on.”

[0146] As used herein, a phrase referring to a list of items separated by “or” refers to any combination of those items, including single members. For example, “a, b, or c” is intended to cover the possibilities of: a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a and b and c.

[0147] In this disclosure, an expression of “X / Y” may include meaning of any of the following: “X or Y” or “X and Y” or “X and / or Y." An expression of “(A) B” or “B (A)” may include concept of “only B.” An expression of “(A) B” or “B (A)” may include the concept of “A+B” or “B+A.”

[0148] In this disclosure, the term "can" indicates a capability, or alternatively indicates a possible implementation option. The term "may" indicates a permission or a possible implementation option.

[0149] Some aspects are described herein in connection with thresholds. As used herein, satisfying a threshold may refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, or the like.

[0150] The various illustrative components, logic, logical blocks, modules, circuits, operations and algorithm processes described in connection with the implementations disclosed herein may be implemented as electronic hardware, firmware, software, or combinations of hardware, firmware or software, including the structures disclosed in thisspecification and the structural equivalents thereof. The interchangeability of hardware, firmware and software has been described generally, in terms of functionality, and illustrated in the various illustrative components, blocks, modules, circuits and processes described above. Whether such functionality is implemented in hardware, firmware or software depends upon the particular application and design constraints imposed on the overall system.

[0151] As described above, some aspects of the subject matter described in this specification can be implemented as software. For example, various functions of components disclosed herein, or various blocks or steps of a method, operation, process or algorithm disclosed herein can be implemented as one or more modules of one or more computer programs. Such computer programs can include non-transitory processor-executable or computer-executable instructions encoded on one or more tangible processor-readable or computer-readable storage media for execution by, or to control the operation of, a data processing apparatus including the components of the devices described herein. By way of example, and not limitation, such storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store program code in the form of instructions or data structures. Combinations of the above should also be included within the scope of storage media.

[0152] Various modifications to the implementations described in this disclosure may be readily apparent to persons having ordinary skill in the art, and the generic principles defined herein may be applied to other implementations without departing from the scope of this disclosure. Thus, the claims are not intended to be limited to the implementations shown herein but are to be accorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.

[0153] Additionally, various features that are described in this specification in the context of separate implementations also can be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also can be implemented in multiple implementations separately or in any suitable subcombination. As such, although features may be described above as acting in particular combinations, and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

[0154] The drawings may schematically depict one or more example processes in the form of a flowchart or flow diagram. However, other operations that are not depicted can beincorporated in the example processes that are schematically illustrated. For example, one or more additional operations can be performed before, after, simultaneously, or between any of the illustrated operations. In some circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other implementations are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results.

[0155] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects. While the aspects of the disclosure have been described in terms of various examples, any combination of aspects from any of the examples is also within the scope of the disclosure. The examples in this disclosure are provided for pedagogical purposes.

Claims

CLAIMSWhat is claimed is:

1. A method for wireless communication by a user equipment (UE) (102), the method comprising: receiving, from a non-terrestrial network (NTN) node (101, 104, 106), one or more beam discontinuous transmission (DTX) or discontinuous reception (DRX) configurations (beam DTX / DRX configurations), the one or more beam DTX / DRX configurations including at least a first beam DTX / DRX configuration specific to at least a first beam of the NTN node and beam matching information to identify the first beam; and communicating with the NTN node via the first beam in accordance with the first beam DTX / DRX configuration.

2. The method of claim 1, wherein the receiving the one or more beam DTX / DRX configurations includes: receiving, from the NTN node, a second beam DTX / DRX configuration associated with at least a second beam of the NTN node; and communicating with the NTN node via the first beam or the second beam in accordance with the first beam DTX / DRX configuration or the second beam DTX / DRX configuration, respectively.

3. The method of claim 1 or 2, wherein the receiving the one or more beam DTX / DRX configurations includes at least one of: receiving the one or more beam DTX / DRX configurations via a medium access control (MAC) control element (MAC CE), receiving the one or more beam DTX / DRX configurations via radio resource control (RRC) signaling, receiving the one or more beam DTX / DRX configurations via downlink control information (DCI) on a physical downlink control channel (PDCCH); receiving the one or more beam DTX / DRX configurations via system information; or any combination thereof.

4. The method of any one of claims 1 to 3, wherein the one or more beam DTX / DRX configurations include at least one of: duration of an active period of a particular beam; or a beam DTX / DRX cycle indicating a periodicity for the active period.

5. The method of any one of claims 1 to 4, wherein the one or more beam DTX / DRX configurations include an action delay value indicating time or time period before the one or more beam DTX / DRX configurations is active.

6. The method of any one of claims 1 to 5, wherein the one or more beam DTX / DRX configurations include at least one of: an indication that the NTN node will discontinue transmitting common downlink signals during an OFF period, the common downlink signals excluding UE-specific data or control signaling; or a configuration of a COMMON period during which the NTN node will transmit the common downlink signals.

7. The method of any one of claims 1 to 6, wherein the beam matching information includes at least one of: a beam identifier (ID); an index of a beam configuration (beam index); an index or resource ID of a synchronization signal block (SSB) resource configured for a beam associated with the particular beam DTX / DRX configuration; an index or resource ID of a channel state information reference signal (CSI-RS) resource configured for the beam associated with the particular beam DTX / DRX configuration; or a transmission configuration indicator (TCI) or TCI state index that corresponds to the beam associated with the particular beam DTX / DRX configuration.

8. The method of any one of claims 1 to 7, wherein the communicating with the NTN node via the first beam in accordance with the first beam DTX / DRX includes: monitoring or receiving a downlink control channel of the first beam during an active period indicated in the first beam DTX / DRX configuration; and refraining from communicating with the NTN node via the first beam during a nonactive period indicated in the first beam DTX / DRX configuration.

9. The method of any one of claims 1 to 8, wherein the receiving the one or more beam DTX / DRX configurations includes: receiving, via the first beam, a rough beam DTX / DRX configuration of a third beam of the NTN node; switching from the first beam to the third beam based, at least in part, on the rough beam DTX / DRX configuration; andreceiving via the third beam, a full beam DTX / DRX configuration of the second beam.

10. The method of any one of claims 1 to 9, further comprising: determining that a paging occasion (PO) occurs during a non-active period of the first beam based on the first beam DTX / DRX configuration; and determining that the PO occurs during an active period of the second beam based on the second beam DTX / DRX configuration; and switching from the first beam to the second beam before the PO.1 1. The method of any one of claims 1 to 10, further comprising: determining that a paging occasion (PO) occurs during a non-active period of the first beam based on the first beam DTX / DRX configuration; and shifting a start time of the PO to a next active period of the first beam or the second beam.

12. A method for wireless communication by a non-terrestrial network (NTN) node, the method comprising: transmitting one or more beam discontinuous transmission (DTX) or discontinuous reception (DRX) configurations (beam DTX / DRX configurations), the one or more beam DTX / DRX configurations including at least a first beam DTX / DRX configuration specific to at least a first beam of the NTN node, wherein the first beam DTX / DRX configuration includes beam matching information to identify the first beam; and communicating with a user equipment (UE) via the first beam in accordance with the first beam DTX / DRX configuration.

13. The method of claim 12, wherein the transmitting the one or more beam DTX / DRX configurations includes: transmitting a second beam DTX / DRX configuration associated with at least a second beam of the NTN node; and communicating with the UE via the first beam or the second beam in accordance with the first beam DTX / DRX configuration or the second beam DTX / DRX configuration, respectively.

14. The method of claim 12 or 13, wherein the transmitting the one or more beam DTX / DRX configurations includes at least one of: transmitting the one or more beam DTX / DRX configurations via a medium access control (MAC) control element (MAC CE),transmiting the one or more beam DTX / DRX configurations via radio resource control (RRC) signaling, transmitting the one or more beam DTX / DRX configurations via downlink control information (DCI) on a physical downlink control channel (PDCCH); transmitting the one or more beam DTX / DRX configurations via system information; or any combination thereof.

15. The method of any one of claims 12 to 14, wherein the one or more beam DTX / DRX configurations include beam matching information that enables the UE to determine which beam is associated with a particular beam DTX / DRX configuration, the beam matching information including at least one of: a beam identifier (ID); an index of a beam configuration (beam index); an index or resource ID of a synchronization signal block (SSB) resource configured for a beam associated with the particular beam DTX / DRX configuration; an index or resource ID of a channel state information reference signal (CSI-RS) resource configured for the beam associated with the particular beam DTX / DRX configuration; or a transmission configuration indicator (TCI) or TCI state index that corresponds to the beam associated with the particular beam DTX / DRX configuration.

16. The method of any one of claims 12 to 15, wherein the one or more beam DTX / DRX configurations include at least one of: duration of an active period of a particular beam; a beam DTX / DRX cycle indicating a periodicity’ for the active period; or an action delay value indicating time or time period before the one or more beam DTX / DRX configurations is active.

17. The method of any one of claims 12 to 16, further comprising, when a paging occasion (PO) for the UE overlaps a non-active period of the first beam and the NTN node has a paging message to transmit to the UE: transmitting the paging message during a shifted PO that occurs in a next active period of the first beam or the second beam.

18. An apparatus, comprising: a communication unit; anda processing system configured to control the communication unit to implement any one of the methods of any one of claims 1 to 17.

Images