WO2025148269A1

WO2025148269A1 - Systems and methods for supporting transmission or reception of signals according to the adaptive periodicity of common channel

Info

Publication number: WO2025148269A1
Application number: PCT/CN2024/106385
Authority: WO
Inventors: Ziyang Li; Nan Zhang; Fangyu CUI; Wei Cao
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2024-07-19
Filing date: 2024-07-19
Publication date: 2025-07-17
Anticipated expiration: 2027-01-19

Abstract

Presented are systems and methods for supporting transmission or reception of signals according to the adaptive periodicity of a common channel. A wireless communication device can determine a resource for transmission or reception of a signal. The wireless communication device can perform the transmission or reception of the signal, according to the resource.

Description

SYSTEMS AND METHODS FOR SUPPORTING TRANSMISSION OR RECEPTION OF SIGNALS ACCORDING TO THE ADAPTIVE PERIODICITY OF COMMON CHANNEL

TECHNICAL FIELD

The disclosure relates generally to wireless communications, including but not limited to systems and methods for supporting transmission or reception of signals according to the adaptive periodicity of a common channel.

BACKGROUND

Coverage is a key consideration in cellular network deployments. With the rise of interconnected devices, there is a growing focus on effective device communication. The current 3GPP standards, spanning from 3G to 5G and beyond, focus on the importance of seamless communication among various devices, from smart home devices to wearable devices. In industrial settings, the complexity of tasks often requires collaboration. This calls for several cooperative operational management systems, with the aim of creating workgroups and managing different types of devices to complete the required tasks.

SUMMARY

The example embodiments disclosed herein are directed to solving the issues relating to one or multiple of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings. In accordance with various embodiments, example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.

At least one aspect is directed to a system, method, apparatus, or computer-readable medium. A wireless communication device (e.g., UE) can determine a resource for transmission or reception of a signal. The wireless communication device can perform the transmission or reception of the signal, according to the resource. In certain implementations, the wireless communication device can receive a resource configuration (e.g., implicitly or explicitly provides active/inactive time information) from a wireless communication node (e.g., BS) . In certain implementations, the wireless communication device can receive the resource configuration via system information (e.g., SIB1, SIB19, MIB) signaling or radio resource control (RRC) signaling. In certain implementations, the resource configuration may include at least one of the following: information of at least one type of active or inactive time, or information of at least one synchronization signal (SS) (e.g., SSB) .

In certain implementations, at least one of: the SS may include at least one of the following: a synchronization signal block, a physical broadcast channel (PBCH) signal, a SS/PBCH block (SSB) , a primary SS, or a secondary SS (SSS) ; the information of the at least one SS may include at least one of the following: at least one SS index (e.g., SSB index) , at least one SS periodicity, at least one SS offset, at least one SS location, or at least one SS pattern; at least one of the SS periodicity, the SS offset, the SS location, or the SS pattern can be configured for a specific SS or SS index, or for a plurality (e.g., or a list/set) of SSes or SS indices; the plurality of SSes or SS indices may include at least one of the following: all SSes or SS indices, a number of consecutive SS indices, or a number of non-consecutive SS indices; or the information of at least one type of active or inactive time may include at least one parameter of active or inactive time.

In certain implementations, the information of at least one type of active or inactive time may include at least one of the following: an indication of whether beam hopping is enabled or disabled; an indication of whether a repeater node is used to serve a cell; an indication of whether one or more SSes are disabled or canceled; an index of a configuration of active or inactive time; an indication of one or more periodicities for active or inactive time; an indication of one or more offset values (e.g., frame level, sub-frame level, ms level, slot level, or symbol level) ; or an indication of one or more durations (e.g., frame level, sub-frame level, ms level, slot level, or symbol level) . In certain implementations, the at least one type of active or inactive time can be associated with the at least one SS. In some implementations, at least one of: one type of active or inactive time can be associated with one SS or SS index; one type of active or inactive time can be associated with a plurality of SSes or SS indices; or one type of active or inactive time can be associated with all of the at least one SS.

In certain implementations, the resource may include at least one of the following: a valid or invalid occasion for the signal; a valid or invalid random access channel (RACH) occasion (RO) ; a valid or invalid physical RACH (PRACH) repetition; an association between at least one index of the synchronization signal and at least one occasion for the signal; a mapping ratio N for mapping between an index of the synchronization signal and an occasion for the signal; a PRACH repetition number; a random access response (RAR) window length; or a valid or invalid physical uplink shared channel (PUSCH) occasion of a configured grant (CG) transmission.

In certain implementations, the occasion for the signal for validation can be from a candidate occasion list/set/group. The candidate occasion list may include at least one of the following: all occasions for the signal; occasions for the signal after the mapping between at least one index of one or more synchronization signals and at least one occasion for the signal; occasions for the signal that are associated or mapped with at least one index of one or more synchronization signals; occasions for the signal that are associated with at least one index of one or more synchronization signals with first periodicity; or occasions for the signal that are associated with at least one synchronization signal with a first index.

In certain implementations, the wireless communication device can determine for initial cell selection that half frames with synchronization signal (SS) /physical broadcast channel (PBCH) blocks occur with a periodicity of N frames, where N can be determined according to at least one of the following: a type or capability of the wireless communication device, whether the wireless communication device is served by a satellite, or whether the wireless communication device is served by a repeater node. In certain implementations, at least one of: when the type or capability is normal, N is a first value; when the type or capability includes support for non-terrestrial network (NTN) , N is a second value; when the wireless communication device is not served by a satellite or a repeater node, N is a first value; or when the wireless communication device is served by a satellite or a repeater node, N is a second value, where the first value and the second value are each a respective integer value.

In certain implementations, at least one of: the signal may include a random access signal or a physical random access channel (PRACH) transmission; the resource configuration can be configured to support a periodicity of a synchronization signal (SS periodicity) (e.g., SSB) associated with the signal; a random access configuration includes a frame index in which a random access channel (RACH) occasion is configured, where the frame index can be determined by at least one of the SS periodicity or a periodicity of the signal; a random access configuration may include n_f mod (x*n) = y, where n is a factor corresponding to the SS periodicity, x is associated with a periodicity of the signal, y is a defined integer value, and n_f is a frame index in which a random access channel (RACH) occasion is configured; or an index of the random access configuration (e.g., e.g., PRACH configuration can be associated with an index of the synchronization signal (e.g., SSB index) .

In certain implementations, at least one of: the signal may include a random access signal or a physical random access channel (PRACH) transmission; one or more occasions of the signal (e.g., PRACH occasions) can be validated by a synchronization signal associated with the signal; the wireless communication device can determine one or more valid or invalid occasions of the signal according to the resource configuration; or the wireless communication device can determine one or more valid or invalid repetitions of the signal according to the resource configuration.

In certain implementations, at least one of: the signal may include a random access signal or a physical random access channel (PRACH) transmission; one or more occasions of the signal can be validated by a synchronization signal associated with the signal; the wireless communication device can determine one or more valid or invalid occasions of the signal according to at least one location, time period, periodicity, or configuration of the synchronization signal; the wireless communication device can determine one or more valid or invalid repetitions of the signal according to at least one location, time period, periodicity, or configuration of the synchronization signal; at least one synchronization signal in a first time period may have a different periodicity as at least one synchronization signal in a second time period; or at least one synchronization signal with a first index may have a different periodicity as at least one synchronization signal with a second index.

In certain implementations, at least one of: the signal may include a random access signal or a physical random access channel (PRACH) transmission; one or more occasions of the signal can be validated by a synchronization signal associated with the signal; the wireless communication device can determine a sequence of the signal according to a sequence of the synchronization signal; the wireless communication device can determine one or more valid or invalid occasions of the signal according to a sequence of the synchronization signal; the wireless communication device can determine a mapping ratio N for mapping between an index of the synchronization signal and an occasion for the signal, where the mapping ratio can correspond to the index, a periodicity of the synchronization signal, or a list/set of synchronization signals, and where N can be defined as: a number of occasions associated with the index of the synchronization signal or a number of SSBs corresponding to all candidate SSBs within an association period; or the wireless communication device can determine a number of frequency division multiplexed occasions of the signal, where the number of frequency division multiplexed occasions multiplied by the mapping ratio can be restricted to be equal to or less than 1.

In certain implementations, the signal may include a random access response (RAR) . In some implementations, a window for reception of the signal may include at least one of the following: a window that starts after a start of an active time; a window that starts after a start of an active time associated with a selected synchronization signal; a window that ends before an end of the active time; a window that ends before an end of an active time associated with the selected synchronization signal; or a window with a length that is adjusted according to a duration of the active time. In certain implementations, the signal may include a configured grant (CG) transmission, where a physical uplink shared channel (PUSCH) occasion for the signal may include at least one of the following: a PUSCH occasion that is validated by a synchronization signal associated with the signal; a PUSCH occasion that is validated by a sequence of a synchronization signal associated with the signal; a PUSCH occasion that is valid if the PUSCH occasion does not overlap with an inactive time; a PUSCH occasion that is invalid if the PUSCH occasion overlaps with an inactive time; a PUSCH occasion that is valid if the PUSCH occasion is within the active time; or a PUSCH occasion that is invalid if the PUSCH occasion is not within the active time.

In certain implementations, the wireless communication node (e.g., BS) can determine a resource for transmission or reception of a signal. The wireless communication node can perform the reception or transmission of the signal, according to the resource.

The system of the technical solutions disclosed herein addresses the impact of larger/adaptive SSB (or other SS) periodicities on related signal/channel designs in wireless communication systems. The system of the technical solutions supports transmission and/or reception of signals (e.g., provides a new initial access design method) according to the adaptive periodicity of a common channel. The system of the technical solutions can achieve this through at least one of the following example configurations (e.g., features or solutions) :

● Example configuration 1: Explicitly introducing a new PRACH configuration to adapt to the periodicity of SSB (or other SS) .

● Example configuration 2: Implicitly associating PRACH (or other random access signaling) occasions with synchronization signals.

BRIEF DESCRIPTION OF THE DRAWINGS

Various example embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for purposes of illustration only and merely depict example embodiments of the present solution to facilitate the reader’s understanding of the present solution. Therefore, the drawings should not be considered limiting of the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.

FIG. 1 illustrates an example cellular communication network in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure;

FIG. 2 illustrates a block diagram of an example base station and a user equipment device, in accordance with some embodiments of the present disclosure;

FIG. 3 illustrates an example configuration of a non-terrestrial network, in accordance with some embodiments of the present disclosure;

FIG. 4 illustrates an example arrangement/configuration of a satellite footprint and a beam footprint, in accordance with some embodiments of the present disclosure;

FIG. 5 illustrates an example arrangement/configuration of an active/inactive time (e.g., active time and/or inactive time) configuration, in accordance with some embodiments of the present disclosure;

FIG. 6 illustrates another example arrangement/configuration of an active/inactive time configuration, in accordance with some embodiments of the present disclosure;

FIG. 7 illustrates another example arrangement/configuration of an active/inactive time configuration, in accordance with some embodiments of the present disclosure;

FIG. 8 illustrates another example arrangement/configuration of an active/inactive time configuration, in accordance with some embodiments of the present disclosure;

FIG. 9 illustrates an example arrangement/configuration of SSB periodicities, in accordance with some embodiments of the present disclosure;

FIG. 10 illustrates another example arrangement/configuration of SSB periodicities, in accordance with some embodiments of the present disclosure;

FIG. 11 illustrates an example arrangement/configuration of a number of FDMed ROs, mapping ratio (s) , and SSB index/indices, in accordance with some embodiments of the present disclosure;

FIG. 12 illustrates an example configuration of an RAR window design, mapping ratio, and SSB index, in accordance with some embodiments of the present disclosure; and

FIG. 13 illustrates a flow diagram of an example method for supporting transmission and/or reception of signals according to adaptive periodicity of a common channel, in accordance with an embodiment of the present disclosure.

DETAILED DESCRIPTION

1. Mobile Communication Technology and Environment

FIG. 1 illustrates an example wireless communication network, and/or system, 100 in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of things (NB-IoT) network, and is herein referred to as “network 100. ” Such an example network 100 includes a base station 102 (hereinafter “BS 102” ; also referred to as wireless communication node) and a user equipment device 104 (hereinafter “UE 104” ; also referred to as wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel) , and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 overlaying a geographical area 101. In Figure 1, the BS 102 and UE 104 are contained within a respective geographic boundary of cell 126. Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one base station operating at its allocated bandwidth to provide adequate radio coverage to its intended users.

For example, the BS 102 may operate at an allocated channel transmission bandwidth to provide adequate coverage to the UE 104. The BS 102 and the UE 104 may communicate via a downlink radio frame 118, and an uplink radio frame 124 respectively. Each radio frame 118/124 may be further divided into sub-frames 120/127 which may include data symbols 122/128. In the present disclosure, the BS 102 and UE 104 are described herein as non-limiting examples of “communication nodes, ” generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and/or wired communications, in accordance with various embodiments of the present solution.

FIG. 2 illustrates a block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM/OFDMA signals) in accordance with some embodiments of the present solution. The system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 of Figure 1, as described above.

System 200 generally includes a base station 202 (hereinafter “BS 202” ) and a user equipment device 204 (hereinafter “UE 204” ) . The BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with one another as necessary via a data communication bus 220. The UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with one another as necessary via a data communication bus 240. The BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmission of data as described herein.

As would be understood by persons of ordinary skill in the art, system 200 may further include any number of modules other than the modules shown in Figure 2. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure.

In accordance with some embodiments, the UE transceiver 230 may be referred to herein as an “uplink” transceiver 230 that includes a radio frequency (RF) transmitter and a RF receiver each comprising circuitry that is coupled to the antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion. Similarly, in accordance with some embodiments, the BS transceiver 210 may be referred to herein as a “downlink” transceiver 210 that includes a RF transmitter and a RF receiver each comprising circuity that is coupled to the antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in time duplex fashion. The operations of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operations of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 at the same time that the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is close time synchronization with a minimal guard time between changes in duplex direction.

The UE transceiver 230 and the base station transceiver 210 are configured to communicate via the wireless data communication link 250, and cooperate with a suitably configured RF antenna arrangement 212/232 that can support a particular wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.

In accordance with various embodiments, the BS 202 may be an evolved node B (eNB) , a serving eNB, a target eNB, a femto station, or a pico station, for example. In some embodiments, the UE 204 may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA) , tablet, laptop computer, wearable computing device, etc. The processor modules 214 and 236 may be implemented, or realized, with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this manner, a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, or the like. A processor may also be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or multiple microprocessors in conjunction with a digital signal processor core, or any other such configuration.

Furthermore, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in firmware, in a software module executed by processor modules 214 and 236, respectively, or in any practical combination thereof. The memory modules 216 and 234 may be realized as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, such that the processors modules 210 and 230 can read information from, and write information to, memory modules 216 and 234, respectively. The memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by the processor modules 210 and 230, respectively.

The network communication module 218 generally represents the hardware, software, firmware, processing logic, and/or other components of the base station 202 that enable bi-directional communication between base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, network communication module 218 may be configured to support internet or WiMAX traffic. In a typical deployment, without limitation, network communication module 218 provides an 802.3 Ethernet interface such that base station transceiver 210 can communicate with a conventional Ethernet based computer network. In this manner, the network communication module 218 may include a physical interface for connection to the computer network (e.g., Mobile Switching Center (MSC) ) . The terms “configured for, ” “configured to” and conjugations thereof, as used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., that is physically constructed, programmed, formatted and/or arranged to perform the specified operation or function.

The Open Systems Interconnection (OSI) Model (referred to herein as, “open system interconnection model” ) is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication device, wireless communication node) open to interconnection and communication with other systems. The model is broken into seven subcomponents, or layers, each of which represents a conceptual collection of services provided to the layers above and below it. The OSI Model also defines a logical network and effectively describes computer packet transfer by using different layer protocols. The OSI Model may also be referred to as the seven-layer OSI Model or the seven-layer model. In some embodiments, a first layer may be a physical layer. In some embodiments, a second layer may be a Medium Access Control (MAC) layer. In some embodiments, a third layer may be a Radio Link Control (RLC) layer. In some embodiments, a fourth layer may be a Packet Data Convergence Protocol (PDCP) layer. In some embodiments, a fifth layer may be a Radio Resource Control (RRC) layer. In some embodiments, a sixth layer may be a Non-Access Stratum (NAS) layer or an Internet Protocol (IP) layer, and the seventh layer being the other layer.

Various example embodiments of the present solution are described below with reference to the accompanying figures to enable a person of ordinary skill in the art to make and use the present solution. As would be apparent to those of ordinary skill in the art, after reading the present disclosure, various changes or modifications to the examples described herein can be made without departing from the scope of the present solution. Thus, the present solution is not limited to the example embodiments and applications described and illustrated herein. Additionally, the specific order or hierarchy of steps in the methods disclosed herein are merely example approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present solution. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present solution is not limited to the specific order or hierarchy presented unless expressly stated otherwise.

2. Systems and Methods for Supporting Transmission or Reception of Signals According to the Adaptive Periodicity of a Common Channel

In non-terrestrial networks (NTN) , a satellite can cover a huge area with limited simultaneous beams. In this regard, beam hopping can be used to facilitate coverage of a huge area by allowing each beam to serve a smaller area. In certain implementations, the coverage availability based on beam hopping patterns can adapt to the traffic load in different areas. Due to beam hopping, the user equipment (UE) may transmit or receive signals when the serving beam is active. The SS/PBCH block (SSB) (and more generally, synchronization signal) periodicity may be 20 ms for initial cell selection, but there may not be an active beam within each/every 20ms for this cell. In certain implementations, the SSB periodicity may be extended accordingly to a larger or more adaptive value, e.g., 640 ms. The larger/adaptive SSB periodicity may have an impact on other signal/channel designs/configurations. The technical solutions described herein can provide an initial access design with adaptive periodicity for the common channel. The present disclosure can be applied to 5G and/or 6G.

In certain implementations, the structure of transparent NTN is shown in FIG. 3. As shown, the link between UE and satellite is a service link. The link between BS and satellite is a feeder link that can be common for all UEs within the same cell. In NTN, beaming hopping can facilitate coverage of a huge area with limited simultaneous beams. The coverage availability, based on beam sweeping periodicity, can be adaptive to the traffic load in different areas. In certain implementations, as shown in FIG. 4, the entire/whole footprint of a satellite can be exceedingly large. For example, a typical low-earth orbit (LEO) satellite at a 600km orbital height can cover a circular area with a radius of approximately 1000km, given a minimum elevation angle of 30 degrees. However, the footprint of a single beam can be constrained/limited by the legacy physical random-access channel (PRACH) design for terrestrial networks. In certain implementations, the maximum radius of a beam can be limited to 100km due to the PRACH Cyclic Prefix (CP) length limitation. As a result, a satellite may require a large number of beams (potentially hundreds or even thousands) to cover its entire/whole footprint. In certain implementations, the effective isotropic radiated power (EIRP) density (measured in dBW/MHz) can be used for downlink (DL) coverage system-level evaluation, which may mean/indicate that the total transmission power is proportional to the system bandwidth. In certain implementations, the total transmission power can be limited by the payload hardware capability instead of the system bandwidth. Due to the limitation on the total transmission power of a satellite, a certain portion/part/subset of the beams can be activated simultaneously (at a certain time) to ensure a satisfactory link budget.

In certain implementations, within terrestrial networks (TN) , repeaters (e.g., NCR) or reconfigurable intelligent surface (RIS) with beam sweeping capability can be used to deal with coverage holes/gaps. The common signal from the base station (BS) can be forwarded by the repeater, or RIS, using beam hopping. In certain implementations, network energy saving (NES) can be considered by a BS using beam hopping to serve low traffic areas or off-peak hours.

In the present disclosure, “beam” can be a transmission configuration indicator (TCI) state, a spatial filter, an associated RS with a quasi-colocation (QCL) relationship, or a beam index for a communication node. The communication node can be a network node or a terminal.

In the present disclosure, “active time” can refer to the time period when a service (e.g., including uplink (UL) and/or downlink (DL) transmission access) is available to a certain UE/cell or beam (s) . In some implementations, the active time can refer to serving time, beam active time, activated time ON-duration, and the like. In certain implementations, a satellite may cover a huge area/footprint (e.g., larger than one cell) with beam hopping, and one cell or one UE may be served within the active time when the corresponding beam is available (e.g., switched on or hopped) to such an area, cell, or UE. In some implementations, for example, considering traffic conditions, the active time may be periodic, such as when the active time pattern is deterministic over a relatively long time period. In some implementations, the active time may be aperiodic, such as when the traffic is unexpected and no certain pattern can be maintained.

In the present disclosure, “inactive time” can refer to the time period when the service is not available to a certain UE/cell or beam (s) . In some implementations, the inactive time can refer to sleep time, beam inactive time, de-activated time, OFF-duration, and the like. In some implementations, for example, considering traffic conditions, the inactive time may be periodic, such as when the inactive time pattern is certain over a relatively long time period. In some implementations, the inactive time may be aperiodic, such as when the traffic is unexpected and no certain pattern can be maintained. In some implementations, within the inactive time, the UE may not be expected to transmit and/or receive. In some implementations, the transmission and/or reception may be canceled. In some implementations, the transmission and/or reception may be postponed.

In the present disclosure, synchronization signal can refer to at least one of the SSB, SS/PBCH blocks, PSS, SSS, or PBCH. The random-access signal can refer to the PRACH signal. The PRACH signal may also refer to the NB-IoT PRACH (NPRACH) signal.

In certain embodiments, the UE can obtain/determine the configuration information of at least one of one or more types of active/inactive time or one or more SSBs. In some/conventional systems) , all the UEs may assume the same SSB periodicity for initial cell search.

In the present disclosure described herein, different UEs may assume different periodicities of SSB bursts for initial cell selection. For example, for initial cell selection, a UE may assume that half frames with SS/PBCH blocks occur with a periodicity of N frames, where N is an integer. In some implementations, N can be determined by at least one of the following example approaches:

● UE type/capability, e.g., if the UE is normal UE, N =2, if the UE is NTN UE, N = 64;

● Whether the UE is served by satellite, e.g., if the UE is served by satellite, N = 64, otherwise, N = 2; or

● Whether the UE is served by NCR/RIS, e.g., if the UE is served by NCR/RIS, N = 64, otherwise, N = 2.

In certain implementations, the UE can receive/obtain configuration information via signaling (e.g., system information, SIB1, SIB19, MIB, RRC) from a gNB/BS related to at least one of the following: one or more types of active/inactive time, or one or more SSBs. In certain implementations, the configuration information of one or more SSBs may include at least one of the following: one or more SSB indexes; one or more periodicities; one or more offsets; one or more locations; or one or more patterns, e.g., SSB patterns, SSB to PRACH association pattern, among others.

In certain implementations, at least one of a periodicity, an offset, a location, or a pattern can be configured for all SSBs. For example, for the configuration of an SSB burst, all SSBs may have the same periodicity, offset, location, and/or pattern.

In certain implementations, at least one of a periodicity, an offset, a location, or a pattern can be configured for a particular list/set/plurality of SSBs or SSB indexes/indices. Each list of SSB indexes may include one or more consecutive or non-consecutive SSB indexes. One or more periodicities, offsets, locations, or patterns can be configured for one or more lists/pluralities of SSBs or SSB indices. A list of SSBs (or SSB indices) may have at least one of the first periodicities, the first offset, the first location, or the first pattern. For example, {SSB 1, 3, 5} can have at least one of the first periodicities, the first offset, the first location, or the first pattern. Another list of SSBs (or SSB indices) may have at least one of the second periodicity, the second offset, the second location, or the second pattern. For example, {SSB 2, 4, 6} can have at least one of the second periodicity, the second offset, the second location, or the second pattern. In some implementations, each periodicity can be configured with a list of SSB indexes/indices, such as {SSB index list x, periodicity} . In some implementations, each periodicity and offset can be configured with a list of SSB indexes, such as {SSB index list x, periodicity, offset} . In some implementations, each pattern can be configured with a list of SSB indexes, such as {SSB index list x, pattern} .

In certain implementations, at least one of a periodicity, an offset, a location, or a pattern can be configured per SSB. For example, each SSB can be associated with at least one of the following: a periodicity, an offset, a location, or a pattern. In some implementations, each SSB index can be configured together with a periodicity, such as {SSB index x, periodicity} . In some implementations, each SSB index can be configured together with a periodicity and an offset, such as {SSB index x, periodicity, offset} . In some implementations, each SSB index can be configured in conjunction with a pattern, such as {SSB index x, pattern} .

In certain implementations, the active/inactive time configuration can be indicated via at least one of the following parameters: a parameter to indicate whether beam hopping is enabled/disabled; a parameter to indicate whether an NCR/RIS is used to serve the cell; a parameter to indicate whether one or more SSB (s) is disabled/canceled; an index of active/inactive time configuration; one or more periodicity; one or more offset values (e.g., frame level, sub-frame level, ms level, slot offset, and/or symbol offset) ; or one or more duration (e.g., frame level, sub-frame level, ms level, slot level, and/or symbol level) .

Below are some examples of active/inactive time configurations. The time configuration of active time is taken as an example. In some implementations, the same technical solution can be applicable to inactive time.

Example 1: The active time configuration can be/include/specify/indicate a regular pattern. In each period, there can be one duration of active time. The active time configuration can be determined by a periodicity, an offset (which may also be a combination of a slot level offset and a symbol level offset) , and/or a duration. The meaning or relationship of these parameters is illustrated in FIG. 5.

Example 2: The active time configuration can be an irregular pattern. In each period, there can be more than one duration of active time. In some implementations, the more than one duration of active time can correspond to more than one type of active time. The active time configuration can be determined by a periodicity, a plurality of offsets (each offset may also be a combination of a slot level offset and a symbol level offset) , and a plurality of durations. The meaning or relationship of these parameters is illustrated in FIG. 6. As shown, the first offset can be defined as the time interval between the reference time and the start (slot or symbol) of the first duration of active time in the period. The second offset can be defined as the time interval between the reference time and the start (slot or symbol) of the second duration of active time in the period.

Example 3: The active time configuration can be an irregular pattern. In each period, there can be more than one duration of active time. In some implementations, the more than one duration of active time can correspond to more than one type of active time. The active time configuration can be determined by a periodicity, a plurality of offsets (each offset may also be a combination of a slot level offset and a symbol level offset) , and a plurality of durations. The meaning or relationship of these parameters is illustrated in FIG. 7. The first offset can be defined as the time interval between the reference time and the start (slot or symbol) of the first duration of active time in the period. The second offset can be defined as the time interval between the end of the first duration of active time and the start (slot or symbol) of the second duration of active time in the period.

Example 4: The active time configuration may include one or more sets of patterns. Each set may include at least one of the following: a periodicity, one or more offsets, or one or more durations. In some implementations, each set can correspond to one type of active time. Each set of active time configurations can be determined by the parameters, as illustrated in Examples 1～3.

In certain implementations, one or more types of active/inactive time can be associated with SSB (or other SS) indexes. In some implementations, one type of active time/inactive time can be associated with one SSB index for instance. For example, Type 1 active time can be associated with SSB index 1, and Type 2 active time can be associated with SSB index 2. In some implementations, one type of active time/inactive time can be associated with one set of SSB indexes. For example, Type 1 active time can be associated with SSB indexes that are forwarded by NCR/RIS, and Type 2 active time can be associated with SSB indexes that are used to serve normal UEs. For example, different SSBs may have different periodicities, where Type 1 active time can be associated with SSB indexes with the first periodicity, and Type 2 active time can be associated with SSB indexes with the second periodicity. For example, Type 1 active time can be associated with SSB indexes indicated by one parameter, e.g., ssb-PositionsInBurst in SIB1, and Type 2 active time can be associated with SSB indexes indicated by another parameter, e.g., a new parameter in SIB1. In some implementations, there can be one type of active time/inactive time associated with all transmitted SSBs. In some implementations, one type of active/inactive time can correspond to both UL and DL. In some implementations, one type of active/inactive can correspond to an UL operation, and another type of active/inactive can correspond to a DL operation.

In certain embodiments, the design of random access signaling/PRACH may include extending or adapting the periodicity of synchronization signals. In some implementations/options, a new PRACH configuration can be explicitly introduced to adapt to the periodicity of SSB. In one implementation, a table is defined for the PRACH configuration. Each row of the table can represent a specific PRACH configuration in a cell, including the PRACH format, time domain location of RO, and the like. Some rows of the table are reproduced below:

Table 6.3.3.2-2: Random access configurations for FR1 and paired spectrum/supplementary uplink.

In certain implementations/options, in the formula n_fmod x=y, x can be replaced with x*n, where n can be a value associated with the SSB periodicity. In some implementations, n can be applied to the rows with x=16, where n can be 1, 2, or 4, corresponding to SSB periodicities of 160 ms, 320 ms, and 640 ms. In some implementations, n can be applied to any row, where x*n equals to SSB periodicity/10ms, e.g., when SSB periodicity is 160 ms, x*n equals to 16, and when SSB periodicity is 320 ms, x*n equals to 32. In some implementations, n_f can refer to the frame index at which a RACH occasion is configured.

In certain implementations/options, the PRACH configuration index can be associated with the SSB index. In some implementations, different SSBs can be associated with different PRACH configurations. For example, when SSB 1 is associated with PRACH configuration index 1, the PRACH occasions associated with SSB 1 can be located in the 4^th subframe, and when SSB 2 is associated with PRACH configuration index 2, the PRACH occasions associated with SSB 2 can be located in the 7^th subframe.

In certain implementations/options, the PRACH occasions can be implicitly associated with the synchronization signals. In some implementations, the existing PRACH configuration can be reused. The existing PRACH periodicity is up to 160 ms. In some implementations, if the SSB periodicity is extended to 640 ms or the periodicity of some SSBs is different from others, some of the PRACH occasions may not be valid for association with the SSBs. In some implementations, the RO index and/or preamble index are associated with the SSB index. In some implementations, when the SSB periodicity is extended, different SSBs have different periodicities, or more than one SSB is multiplexed in the same time and frequency domain resources, there can be further restrictions on the association between PRACH occasions and SSBs.

In certain implementations/options, the UE can determine valid or invalid PRACH occasions according to the active/inactive time configuration, as shown in FIG. 8. In this option, SSB periodicity can be unchanged, e.g., different SSBs may have the same periodicity. In some implementations, the PRACH occasion is not valid if the PRACH occasion is not within the active time. In some implementations, the PRACH occasion is not valid if the PRACH occasion overlaps with the inactive time. In some implementations, the PRACH occasion is not valid if the PRACH occasion is not within the active time corresponding to the associated SSB (s) . In some implementations, the PRACH occasion is not valid if the PRACH occasion overlaps with the inactive time corresponding to the associated SSB (s) .

In certain implementations/options, the UE can determine valid or invalid PRACH repetitions according to the active/inactive time configuration. In this option, the SSB periodicity can be unchanged, e.g., different SSBs may have the same periodicity. In some implementations, the PRACH repetition is not valid if the PRACH repetition is not within the active time. In some implementations, the PRACH repetition is not valid if the PRACH repetition overlaps with the inactive time. In some implementations, the PRACH repetition is not valid if the PRACH occasion is not within the active time corresponding to the associated SSB(s) . In some implementations, the PRACH repetition is not valid if the PRACH occasion overlaps with the inactive time corresponding to the associated SSB (s) .

In certain implementations/options, the UE can determine valid or invalid PRACH occasions according to the locations of synchronization signals. In certain implementations, one or more SSBs may have different periodicities over different time periods. The mapping and/or validation for PRACH are to be performed in each of these time periods with different SSB periodicities. In some implementations, some of the PRACH occasions can be invalid when the SSB periodicity is changed. In some implementations, the PRACH configuration can be pre-defined. In some implementations, where SSBs have different periodicities over different time periods, the PRACH periodicity can remain unchanged.

In certain implementations, a new validation rule can be applied when SSB periodicity changes, such that some PRACH occasions can be determined to be invalid according to the changed SSB periodicity and location. In some implementations, the new validation rule can ensure that UE selects a proper PRACH occasion to transmit PRACH using the beam that is active. For example, as shown in FIG. 9, during the first time interval [t1, t2] , e.g., during initial cell selection or before the UE connects to the network, the SSBs (e.g., in an SSB burst) may have the first periodicity P1. During the second time interval [t2, t3] , e.g., after the UE connects to the network, the second periodicity P2 can be indicated to the UE via UE specific or cell specific signaling. In some implementations, the mapping between SSBs and PRACH can be updated based on the new SSB periodicity, or the UE can re-validate (using the validation based on the new P2) and identify the RO (with the newly assumed P2) from the originally associated ROs (by assuming P1) . In some implementations, during the first time interval [t1, t2] , where beam hopping is not enabled/allowed, the SSBs (e.g., in an SSB burst) may have the first periodicity. During the second time interval [t2, t3] , where beam hopping is enabled at time t2, the SSBs (e.g., in another SSB burst) may have the second periodicity. In some implementations, during the first time interval [t1, t2] , where the NCR is off, the SSBs may have the first periodicity. During the second time interval [t2, t3] , where NCR is turned on at time t2, the SSBs may have the second periodicity.

In certain implementations/options, different SSBs may have different periodicities. The mapping and/or validation for PRACH are to be done for the SSBs with different SSB periodicities. In some implementations, at least one synchronization signal (SS) with a first index may have a different periodicity than at least one SS signal with a second index. In some implementations, some of the PRACH occasions associated with a specific SSB can be invalid. In some implementations, the PRACH configuration can be pre-defined. In some implementations, the same number of PRACH occasions or preambles can be associated with each SSB. In some implementations, where different SSBs have different periodicities, a new validation rule can be applied, such that some PRACH occasions may be invalid according to the SSB periodicity and location of the associated SSB. The new validation rule can ensure that UE selects a proper PRACH occasion to transmit PRACH using the beam that is active. For example, as shown in FIG. 10, the first SSB can be transmitted to normal UEs. The first SSB may have the first periodicity. The second SSB can be forwarded by NCR/RIS to UEs. The periodicity can be different after forwarding. In this regard, the second SSB may have the second periodicity. In some implementations, the first SSB can correspond to a beam that serves an area with higher traffic. The first SSB may have the first periodicity. The second SSB can correspond to a beam that serves an area with lower traffic. The second SSB may have the second periodicity. In some implementations, the first SSB can correspond to a beam that allows the functionality of beam hopping. The first SSB can have the first periodicity. The second SSB can correspond to a beam that disables the functionality of beam hopping. The second SSB may have the second periodicity.

In certain implementations/options, the UE can determine the PRACH occasion or sequence for PRACH transmission according to the sequence of synchronization signals. In this option, more than one SSB can be multiplexed in the same time and frequency domain resources. In some implementations, each SSB may have a unique sequence. In some implementations, the sequence can refer to at least one of the following: the OCC (orthogonal cover code) sequence, the NOMA (non-orthogonal multiple access) sequence, or the like. In some implementations, the OCC sequence can be at least based on the DFT sequence, the Walsh sequence, the ZC sequence, the Hadamard matrix, and the like. The elements of the sequences can be applied to at least one of PSS, SSS, PBCH, or the whole/entire SS/PBCH blocks (SSB) . In some implementations, the first SSB and the second SSB can be multiplexed in the same time and frequency domain resources with the first sequence and the second sequence, respectively. When the UE detects 2 SSBs, they may be associated with more than PRACH occasions or preambles. The UE can select one of them and determine the exact PRACH occasion for transmitting PRACH according to the sequence of the selected SSB. In some implementations, the first SSB and the second SSB can be multiplexed in the same time and frequency domain resources with the first sequence and the second sequence, respectively. When the UE detects 2 SSBs, they may be associated with the same PRACH occasion. The UE can select one of the SSBs and determine the sequence for PRACH transmission according to the sequence of the selected SSB.

In certain implementations/options, the mapping ratio for the mapping between the SSB index and PRACH occasion can be per SSB index, per periodicity, or per SSB list/set. In the existing standards, there can be a mapping relationship between SSB indexes and PRACH occasions. In certain implementations, a common mapping ratio N is defined as the number of SSB indexes associated with one PRACH occasion. In some implementations, N can be defined as the number of ROs associated with one SSB index. In some implementations, N can be defined as the number of the set of SSBs, which can refer to all potential candidate SSBs within the association period. In certain implementations, the mapping ratio can be defined as per the SSB index, e.g., different SSBs may have different mapping ratios. In some implementations, the mapping ratio can be defined as per periodicity, where each periodicity can correspond to one or more SSBs and a mapping ratio. In certain implementations, the mapping ratio can be defined as per the SSB list, where each list of SSBs may have a specific mapping ratio. Each list/set can include one or more consecutive or non-consecutive SSB indexes.

In some implementations, each SSB may have a specific mapping ratio. For example, the first SSB may have the first mapping ratio N1, and the second SSB may have the second mapping ratio N2. In some implementations, the SSBs may have different periodicities, e.g., {SSB 1, 3, 5} may have a first periodicity P1, and {SSB 2, 4, 6} may have a second periodicity P2. For SSBs with periodicity P1, the SSBs may have the first mapping ratio N1. For SSBs with periodicity P2, the SSBs may have the second mapping ratio P2. In some implementations, each list/set of SSBs may have a specific mapping ratio. For example, the first list of SSBs (e.g., {SSB 1, 3, 5} ) may have the first mapping ratio N1, and the second list of SSBs (e.g., {SSB 2, 4, 6}) may have the second mapping ratio N2.

In certain implementations/options, restrictions on the network configuration can include the number of FDMed ROs and/or mapping ratio. In some implementations, the network can configure several FDMed ROs. In some implementations, if FDMed ROs are associated with different SSBs, the network configuration may require that gNB have different reception beams to simultaneously receive the PRACH. In some implementations, the approach may not be applicable for NTN scenarios. In some implementations, as shown in FIG. 11, four cases are listed to illustrate the meaning of the number of FDMed ROs, mapping ratio (s) , and SSB index (es) . Each rectangle can refer to an RO, and “SSB x” within the rectangle can refer to the associated SSB index (es) . For cases 1 and 2, the BS reception beam can associate with one SSB at the same time. In some implementations, it may not be possible to associate more than 1 SSB in the time domain RO. In some implementations, the possible solution can be to restrict the number of FDM ROs *mapping ratio N <= 1.

In certain embodiments, the design on an RAR window can be extended or adapted to the periodicity of synchronization signals. In the existing standards, after the UE transmits the PRACH, the UE can detect the random-access response in the RAR window. In some implementations, the start of the RAR window and the length of the RAR window can be defined as follows:

The window starts at the first symbol of the earliest CORESET the UE is configured to receive PDCCH for Type1-PDCCH CSS set, as defined in clause 10.1, that is at least one symbol, after the last symbol of the last PRACH occasion corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for Type1-PDCCH CSS set as defined in clause 10.1. Iforas defined in [4, TS 38.211] , is not zero, the window starts after an additional T_TA+k_mac msec where T_TA is defined in [4, TS 38.211] and k_mac is provided by kmac or k_mac=0 if kmac is not provided. The length of the window in number of slots, based on the SCS for Type1-PDCCH CSS set, is provided by ra-ResponseWindow.

In certain implementations, where beam hopping is allowed, the UE may not be able to receive any signals outside of the beam’s active time, such that the start and length of the RAR window can be adapted according to the beam’s active time. In some implementations, the RAR window design can limit the window within the active time. In some implementations, the design of the RAR window may include at least one of the following: the window starts after the start of active time; the window starts after the start of active time associated with the selected SSB; the window ends before the end of active time; the window ends before the end of active time associated with the selected SSB; or the length of the window can be adjusted according to the duration of active time. For example, as shown in FIG. 12, the RAR window can start at t0 according to existing standards and end at t1, where t1-t0 is the configured RAR window length, e.g., indicated by ra-ResponseWindow or msgB-ResponseWindow. In some implementations, where the beam for transmitting RAR messages is active during the time interval [t0’ , t1’ ] , the RAR window may be adjusted to [t0’ , t1’ ] , where t1’ -t0’ is the duration of active time.

In certain embodiments, the design on the configured grant PUSCH transmission can be extended or adapted to the periodicity of synchronization signals. In the existing SSB to CG-SDT mapping, SSBs are mapped to valid PUSCH occasions. In some implementations, not all PUSCH occasions can be within the beam active time, such that the validation rule is to be revised according to the beam’s active time. In some implementations, after the mapping between the SSBs and valid PUSCH occasions, the PUSCH occasions require re-validation according to at least one of active/inactive time configurations or synchronization signal configurations.

In certain implementations, for CG based RACH less handover, the validation rule for PUSCH occasions can be as follows. In some implementations, not all PUSCH occasions can be within the beam’s active time, such that the validation rule is to be revised according to the beam’s active time. In some implementations, after the mapping between the SSBs and valid PUSCH occasions, the PUSCH occasions require re-validation according to at least one of active/inactive time configurations or synchronization signal configurations. In some approaches, a PUSCH occasion is valid if it does not overlap with a valid PRACH occasion.

In some implementations, the PUSCH occasion is validated by a synchronization signal associated with the CG based transmission, for example, this validation is performed after the mapping between the SSBs and valid PUSCH occasions. In some implementations, the PUSCH occasion is validated by a sequence of synchronization signals associated with the CG based transmission, for example, this validation is performed after the mapping between the SSBs and valid PUSCH occasions. In some implementations, the PUSCH occasion is valid if it does not overlap with inactive time. In some implementations, the PUSCH occasion is invalid if it overlaps with inactive time. In some implementations, the PUSCH occasion is valid if the PUSCH occasion is within the active time. In some implementations, the PUSCH occasion is invalid if the PUSCH occasion is not within the active time. The active/inactive time can be associated with at least one of the following: all SSBs, all SSBs configured for the CG transmission, an SSB index, or a list/set of SSB indexes, which can be consecutive or non-consecutive.

Referring now to FIG. 13, which illustrates a flow diagram of a method 1300 for supporting transmission or reception of signals according to the adaptive periodicity of a common channel. The method 1300 may be implemented using any of the components and devices detailed herein in conjunction with FIGS. 1–12. In an overview, the method 1300 may include a wireless communication device determining a resource for transmission or reception of a signal (STEP 1302) . The method 1300 may include the wireless communication device performing the transmission or reception of the signal, according to the resource (STEP 1304) .

In certain configurations, a wireless communication device (e.g., UE) can determine a resource for transmission or reception of a signal (STEP 1302) . The wireless communication device can perform the transmission or reception of the signal, according to the resource (STEP 1304) . In certain configurations, the wireless communication device can receive a resource configuration (e.g., implicitly or explicitly provides active/inactive time information) from a wireless communication node (e.g., BS) . In certain configurations, the wireless communication device can receive the resource configuration via system information (e.g., SIB1, SIB19, MIB) signaling or radio resource control (RRC) signaling. In certain configurations, the resource configuration may include at least one of the following: information of at least one type of active or inactive time, or information of at least one synchronization signal (SS) (e.g., SSB) .

In certain configurations, at least one of: the SS may include at least one of the following: a synchronization signal block, a physical broadcast channel (PBCH) signal, a SS/PBCH block (SSB) , a primary SS, or a secondary SS (SSS) ; the information of the at least one SS may include at least one of the following: at least one SS index (e.g., SSB index) , at least one SS periodicity, at least one SS offset, at least one SS location, or at least one SS pattern; at least one of the SS periodicity, the SS offset, the SS location, or the SS pattern can be configured for a specific SS or SS index, or for a plurality (e.g., or a list/set) of SSes or SS indices; the plurality of SSes or SS indices may include at least one of the following: all SSes or SS indices, a number of consecutive SS indices, or a number of non-consecutive SS indices; or the information of at least one type of active or inactive time may include at least one parameter of active or inactive time.

In certain configurations, the information of at least one type of active or inactive time may include at least one of the following: an indication of whether beam hopping is enabled or disabled; an indication of whether a repeater node is used to serve a cell; an indication of whether one or more SSes are disabled or canceled; an index of a configuration of active or inactive time; an indication of one or more periodicities for active or inactive time; an indication of one or more offset values (e.g., frame level, sub-frame level, ms level, slot level, or symbol level) ; or an indication of one or more durations (e.g., frame level, sub-frame level, ms level, slot level, or symbol level) . In certain configurations, the at least one type of active or inactive time can be associated with the at least one SS. In some implementations, at least one of: one type of active or inactive time can be associated with one SS or SS index; one type of active or inactive time can be associated with a plurality of SSes or SS indices; or one type of active or inactive time can be associated with all of the at least one SS.

In certain configurations, the resource may include at least one of the following: a valid or invalid occasion for the signal; a valid or invalid random access channel (RACH) occasion (RO) ; a valid or invalid physical RACH (PRACH) repetition; an association between at least one index of the synchronization signal and at least one occasion for the signal; a mapping ratio N for mapping between an index of the synchronization signal and an occasion for the signal; a PRACH repetition number; a random access response (RAR) window length; or a valid or invalid physical uplink shared channel (PUSCH) occasion of a configured grant (CG) transmission.

In certain configurations, the occasion for the signal for validation can be from a candidate occasion list/set. The candidate occasion list may include at least one of the following: all occasions for the signal; occasions for the signal after the mapping between at least one index of one or more synchronization signals and at least one occasion for the signal; occasions for the signal that are associated or mapped with at least one index of one or more synchronization signals; occasions for the signal that are associated with at least one index of one or more synchronization signals with first periodicity; or occasions for the signal that are associated with at least one synchronization signal with a first index.

In certain configurations, the wireless communication device can determine for initial cell selection that half frames with synchronization signal (SS) /physical broadcast channel (PBCH) blocks occur with a periodicity of N frames, where N can be determined according to at least one of the following: a type or capability of the wireless communication device, whether the wireless communication device is served by a satellite, or whether the wireless communication device is served by a repeater node. In certain configurations, at least one of: when the type or capability is normal, N is a first value; when the type or capability includes support for non-terrestrial network (NTN) , N is a second value; when the wireless communication device is not served by a satellite or a repeater node, N is a first value; or when the wireless communication device is served by a satellite or a repeater node, N is a second value, where the first value and the second value are each a respective integer value.

In certain configurations, at least one of: the signal may include a random access signal or a physical random access channel (PRACH) transmission; the resource configuration can be configured to support a periodicity of a synchronization signal (SS periodicity) (e.g., SSB) associated with the signal; a random access configuration includes a frame index in which a random access channel (RACH) occasion is configured, where the frame index can be determined by at least one of the SS periodicity or a periodicity of the signal; a random access configuration may include n_f mod (x*n) = y, where n is a factor corresponding to the SS periodicity, x is associated with a periodicity of the signal, y is a defined integer value, and n_f is a frame index in which a random access channel (RACH) occasion is configured; or an index of the random access configuration (e.g., e.g., PRACH configuration can be associated with an index of the synchronization signal (e.g., SSB index) .

In certain configurations, at least one of: the signal may include a random access signal or a physical random access channel (PRACH) transmission; one or more occasions of the signal (e.g., PRACH occasions) can be validated by a synchronization signal associated with the signal; the wireless communication device can determine one or more valid or invalid occasions of the signal according to the resource configuration; or the wireless communication device can determine one or more valid or invalid repetitions of the signal according to the resource configuration.

In certain configurations, at least one of: the signal may include a random access signal or a physical random access channel (PRACH) transmission; one or more occasions of the signal can be validated by a synchronization signal associated with the signal; the wireless communication device can determine one or more valid or invalid occasions of the signal according to at least one location, time period, periodicity, or configuration of the synchronization signal; the wireless communication device can determine one or more valid or invalid repetitions of the signal according to at least one location, time period, periodicity, or configuration of the synchronization signal; at least one synchronization signal in a first time period may have a different periodicity as at least one synchronization signal in a second time period; or at least one synchronization signal with a first index may have a different periodicity as at least one synchronization signal with a second index.

In certain configurations, at least one of: the signal may include a random access signal or a physical random access channel (PRACH) transmission; one or more occasions of the signal can be validated by a synchronization signal associated with the signal; the wireless communication device can determine a sequence of the signal according to a sequence of the synchronization signal; the wireless communication device can determine one or more valid or invalid occasions of the signal according to a sequence of the synchronization signal; the wireless communication device can determine a mapping ratio N for mapping between an index of the synchronization signal and an occasion for the signal, where the mapping ratio can correspond to the index, a periodicity of the synchronization signal, or a list/set of synchronization signals, and where N can be defined as: a number of occasions associated with the index of the synchronization signal or a number of SSBs corresponding to all candidate SSBs within an association period; or the wireless communication device can determine a number of frequency division multiplexed occasions of the signal, where the number of frequency division multiplexed occasions multiplied by the mapping ratio can be restricted to be equal to or less than 1.

In certain configurations, the signal may include a random access response (RAR) . In some implementations, a window for reception of the signal may include at least one of the following: a window that starts after a start of an active time; a window that starts after a start of an active time associated with a selected synchronization signal; a window that ends before an end of the active time; a window that ends before an end of an active time associated with the selected synchronization signal; or a window with a length that is adjusted according to a duration of the active time. In certain configurations, the signal may include a configured grant (CG) transmission, where a physical uplink shared channel (PUSCH) occasion for the signal may include at least one of the following: a PUSCH occasion that is validated by a synchronization signal associated with the signal; a PUSCH occasion that is validated by a sequence of a synchronization signal associated with the signal; a PUSCH occasion that is valid if the PUSCH occasion does not overlap with an inactive time; a PUSCH occasion that is invalid if the PUSCH occasion overlaps with an inactive time; a PUSCH occasion that is valid if the PUSCH occasion is within the active time; or a PUSCH occasion that is invalid if the PUSCH occasion is not within the active time.

In certain configurations, the wireless communication node (e.g., BS) can determine a resource for transmission or reception of a signal. The wireless communication node can perform the reception or transmission of the signal, according to the resource.

While various embodiments/implementations of the present solution have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Likewise, the various diagrams may depict an example architecture or configuration, which are provided to enable persons of ordinary skill in the art to understand example features and functions of the present solution. Such persons would understand, however, that the solution is not restricted to the illustrated example architectures or configurations but can be implemented using a variety of alternative architectures and configurations. Additionally, as would be understood by persons of ordinary skill in the art, one or multiple features of one embodiment/implementation can be combined with one or multiple features of another embodiment/implementation described herein. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.

It is also understood that any reference to an element herein using a designation such as “first, ” “second, ” and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.

Additionally, a person having ordinary skill in the art would understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols, which may be referenced in the above description, can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

A person of ordinary skill in the art would further appreciate that any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as “software” or a “software module) , or any combination of these techniques. To clearly illustrate this interchangeability of hardware, firmware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware or software, or a combination of these techniques, depends upon the particular application and design constraints imposed on the overall system. Skilled artisans can implement the described functionality in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure.

Furthermore, a person of ordinary skill in the art would understand that various illustrative logical blocks, modules, devices, components, and circuits described herein can be implemented within or performed by an integrated circuit (IC) that can include a general purpose processor, a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, or any combination thereof. The logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device. A general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or multiple microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein.

If implemented in software, the functions can be stored as one or multiple instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another. A storage media can be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

In this document, the term “module” as used herein, refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according to embodiments of the present solution.

Additionally, memory or other storage, as well as communication components, may be employed in embodiments of the present solution. It will be appreciated that, for clarity purposes, the above description has described embodiments of the present solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution. For example, functionality illustrated to be performed by separate processing logic elements, or controllers, may be performed by the same processing logic element, or controller. Hence, references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Thus, the disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims below.

Claims

A method comprising:

determining, by a wireless communication device, a resource for transmission or reception of a signal; and

performing, by the wireless communication device, the transmission or reception of the signal, according to the resource.
The method of claim 1, comprising:

receiving, by the wireless communication device from a wireless communication node, a resource configuration.
The method of claim 2, wherein the wireless communication device receives the resource configuration via system information signaling or radio resource control (RRC) signaling.
The method of claim 2, wherein the resource configuration comprises at least one of: information of at least one type of active or inactive time, or information of at least one synchronization signal (SS) .
The method of claim 4, wherein at least one of:

the SS comprises at least one of: a synchronization signal block, a physical broadcast channel (PBCH) signal, a SS/PBCH block (SSB) , a primary SS, or a secondary SS (SSS) ;

the information of the at least one SS comprises at least one of: at least one SS index, at least one SS periodicity, at least one SS offset, at least one SS location, or at least one SS pattern;

at least one of the SS periodicity, the SS offset, the SS location or the SS pattern is configured for a specific SS or SS index, or for a plurality of SSes or SS indices;

the plurality of SSes or SS indices comprises: all SSes or SS indices, a number of consecutive SS indices, or a number of non-consecutive SS indices; or

the information of at least one type of active or inactive time comprises at least one parameter of active or inactive time.
The method of claim 4, wherein the information of at least one type of active or inactive time comprises at least one of:

an indication of whether beam hopping is enabled or disabled;

an indication of whether a repeater node is used to serve a cell;

an indication of whether one or more SSes are disabled or canceled;

an index of a configuration of active or inactive time;

an indication of one or more periodicities for active or inactive time;

an indication of one or more offset values; or

an indication of one or more durations.
The method of claim 4, wherein the at least one type of active or inactive time is associated with the at least one SS, wherein at least one of:

one type of active or inactive time is associated with one SS or SS index;

one type of active or inactive time is associated with a plurality of SSes or SS indices; or

one type of active or inactive time is associated with all of the at least one SS.
The method of claim 1, wherein the resource comprises at least one of:

a valid or invalid occasion for the signal;

a valid or invalid random access channel (RACH) occasion (RO) ;

a valid or invalid physical RACH (PRACH) repetition;

an association between at least one index of the synchronization signal and at least one occasion for the signal;

a mapping ratio N for mapping between an index of the synchronization signal and an occasion for the signal;

a PRACH repetition number;

a random access response (RAR) window length; or

a valid or invalid physical uplink shared channel (PUSCH) occasion of a configured grant (CG) transmission.
The method of claim 8, wherein the occasion for the signal for validation is from a candidate occasion list, wherein the candidate occasion list comprises at least one of:

all occasions for the signal;

occasions for the signal remaining after the mapping between at least one index of one or more synchronization signals and at least one occasion for the signal;

occasions for the signal that are associated or mapped with at least one index of one or more synchronization signals;

occasions for the signal that are associated with at least one index of one or more synchronization signals with a first periodicity; or

occasions for the signal that are associated with at least one synchronization signal with a first index.
The method of claim 1, comprising:

determining, by the wireless communication device for initial cell selection that half frames with synchronization signal (SS) /physical broadcast channel (PBCH) blocks occur with a periodicity of N frames, wherein N is determined according to at least one of: a type or capability of the wireless communication device, whether the wireless communication device is served by a satellite, or whether the wireless communication device is served by a repeater node.
The method of claim 10, wherein at least one of:

when the type or capability is normal, N is a first value;

when the type or capability includes support for non-terrestrial network (NTN) , N is a second value;

when the wireless communication device is not served by a satellite or a repeater node, N is a first value; or

when the wireless communication device is served by a satellite or a repeater node, N is a second value,

wherein the first value and the second value are each a respective integer value.
The method of claim 1, wherein at least one of:

the signal comprises a random access signal or a physical random access channel (PRACH) transmission;

the resource configuration is configured to support a periodicity of a synchronization signal (SS periodicity) associated with the signal;

a random access configuration includes a frame index in which a random access channel (RACH) occasion is configured, wherein the frame index is determined by at least one of the SS periodicity or a periodicity of the signal;

a random access configuration includes n_f mod (x*n) = y, where n is a factor corresponding to the SS periodicity, x is associated with a periodicity of the signal, y is a defined integer value, and n_f is a frame index in which a random access channel (RACH) occasion is configured; or

an index of the random access configuration is associated with an index of the synchronization signal.
The method of claim 1, wherein at least one of:

the signal comprises a random access signal or a physical random access channel (PRACH) transmission;

one or more occasions of the signal are validated by a synchronization signal associated with the signal;

the wireless communication device determines one or more valid or invalid occasions of the signal according to the resource configuration; or

the wireless communication device determines one or more valid or invalid repetitions of the signal according to the resource configuration.
The method of claim 1, wherein at least one of:

the signal comprises a random access signal or a physical random access channel (PRACH) transmission;

one or more occasions of the signal are validated by a synchronization signal associated with the signal;

the wireless communication device determines one or more valid or invalid occasions of the signal according to at least one location, time period, periodicity or configuration of the synchronization signal;

the wireless communication device determines one or more valid or invalid repetitions of the signal according to at least one location, time period, periodicity or configuration of the synchronization signal;

at least one synchronization signal in a first time period has a different periodicity as at least one synchronization signal in a second time period; or

at least one synchronization signal with a first index has a different periodicity as at least one synchronization signal with a second index.
The method of claim 1, wherein at least one of:

the signal comprises a random access signal or a physical random access channel (PRACH) transmission;

one or more occasions of the signal are validated by a synchronization signal associated with the signal;

the wireless communication device determines a sequence of the signal according to a sequence of the synchronization signal;

the wireless communication device determines one or more valid or invalid occasions of the signal according to a sequence of the synchronization signal;

the wireless communication device determines a mapping ratio N for mapping between an index of the synchronization signal and an occasion for the signal, wherein the mapping ratio corresponds to the index, a periodicity of the synchronization signal, or a list of synchronization signals, and wherein N is defined as: a number of occasions associated with the index of the synchronization signal, or a number of SSBs corresponding to all candidate SSBs within an association period; or

the wireless communication device determines a number of frequency division multiplexed occasions of the signal, wherein the number of frequency division multiplexed occasions multiplied by the mapping ratio is restricted to be equal to or less than 1.
The method of claim 1, wherein the signal comprises a random access response (RAR) , wherein a window for reception of the signal comprises at least one of:

a window that starts after a start of an active time;

a window that starts after a start of an active time associated with a selected synchronization signal;

a window that ends before an end of the active time;

a window that ends before an end of an active time associated with the selected synchronization signal; or

a window with a length that is adjusted according to a duration of the active time.
The method of claim 1, wherein the signal comprises a configured grant (CG) transmission, wherein a physical uplink shared channel (PUSCH) occasion for the signal comprises at least one of:

a PUSCH occasion that is validated by a synchronization signal associated with the signal;

a PUSCH occasion that is validated by a sequence of a synchronization signal associated with the signal;

a PUSCH occasion that is valid if the PUSCH occasion does not overlap with an inactive time;

a PUSCH occasion that is invalid if the PUSCH occasion overlaps with an inactive time;

a PUSCH occasion that is valid if the PUSCH occasion is within the active time; or

a PUSCH occasion that is invalid if the PUSCH occasion is not within the active time.
A method comprising:

determining, by a wireless communication node, a resource for transmission or reception of a signal; and

performing, by the wireless communication node, the reception or transmission of the signal, according to the resource.
A non-transitory computer readable medium storing instructions, which when executed by at least one processor, cause the at least one processor to perform the method of any one of claims 1-18.
An apparatus comprising:

at least one processor configured to perform the method of any one of claims 1-18.