Network access method, apparatus and computer readable medium

Abstract

One wireless communication method includes: obtaining configuration or signaling for determining a RACH operating mode, wherein the RACH operating mode includes full-duplex RACH operation or non-full-duplex RACH operation; and determining the RACH operating mode based on the configuration or signaling. Another wireless communication method includes: providing configuration or signaling for determining a RACH operating mode, wherein the RACH operating mode includes full-duplex RACH operation or non-full-duplex RACH operation.

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, and more specifically to random access procedures for wireless communications. Background Technology

[0002] When a terminal device (UE) wants to connect to a base station, it must perform a RACH (Random Access Procedure) such as Contention-Based Random Access (CBRA) or Contention-Free Random Access (CFRA). In a Contention-Based Random Access procedure, the UE randomly selects a preamble from a pool of preamble candidates shared with another UE. The base station (BS) uses a contention resolution mechanism to handle this type of access request. CBRA is also known as a four-step RACH procedure. In CFRA, the preamble is assigned by the base station, and this preamble is called a dedicated random access preamble. The dedicated preamble is provided to the UE via RRC signaling or PHY layer signaling (such as DCI over PDCCH).

[0003] Subband Full Duplex (SBFD) is a new duplexing mode where a TDD carrier is divided into subbands to allow simultaneous transmission and reception in the same time slot. Together with cross-subband scheduling, the gNB (gear-based network unit) can simultaneously provide high uplink throughput and low latency guarantees to meet the needs of critical vertical applications, and through flexible frame structures, the gNB can work with legacy terminals. SBFD can provide user-level service capability customization, thus flexibly meeting the needs of various B2B and B2C applications. When SBFD technology is adopted, the RACH process is not extensively developed. Summary of the Invention

[0004] This invention provides a brief description of certain aspects of the present disclosure. It is not intended to limit the scope of the disclosure.

[0005] According to some embodiments of this disclosure, a wireless communication method is disclosed. The method includes: obtaining configuration or signaling for determining a RACH operating mode, wherein the RACH operating mode includes full-duplex RACH operation or non-full-duplex RACH operation; and determining the RACH operating mode based on the configuration or signaling.

[0006] According to some embodiments of this disclosure, another wireless communication method is disclosed. The method includes: providing configuration or signaling for determining a RACH operating mode, wherein the RACH operating mode includes full-duplex RACH operation or non-full-duplex RACH operation.

[0007] Another embodiment of this disclosure provides a wireless communication device including one or more memory units storing one or more programs and one or more processors electrically coupled to the one or more memory units and configured to execute one or more programs to perform any method or step or combination thereof of this disclosure.

[0008] Another embodiment of this disclosure provides a non-transient computer-readable storage medium storing one or more programs configured to, when executed by at least one processor, cause it to perform any method or step or combination thereof of this disclosure.

[0009] According to some embodiments of this disclosure, one or more wireless communication methods are further disclosed, which include combinations of certain methods, aspects, elements and steps disclosed in various embodiments of this disclosure (in a general view or a specific view).

[0010] The above and other aspects and their embodiments are described in more detail in the accompanying drawings, description and claims. Attached Figure Description

[0011] Various exemplary embodiments of the present disclosure are described in detail below with reference to the accompanying drawings. The drawings are provided for illustrative purposes only and depict only exemplary embodiments of the present disclosure to facilitate understanding. Therefore, the drawings should not be considered as limiting the breadth, scope, or applicability of the present disclosure. It should be noted that these figures are not necessarily drawn to scale for clarity and ease of illustration.

[0012] Figure 1 The subband full-duplex (SBFD) transmission resource arrangement is shown;

[0013] Figure 2 A flowchart of the wireless communication method is shown;

[0014] Figure 3 The diagram shows the ROs in the subband full-duplex (SBFD) transmission resource arrangement;

[0015] Figure 4 The diagram shows the ROs in the subband full-duplex (SBFD) transmission resource arrangement;

[0016] Figure 5-7 A MAC CE capable of being used to indicate RACH operating mode is shown; and

[0017] Figures 8A-8C A block diagram of an exemplary wireless communication system is shown together. Detailed Implementation

[0018] There are different types of RACH procedures, including contention-based random access (CBRA) and contention-free random access (CFRA). In CBRA, the UE transmits a preamble at the PRACH timing (RO) based on the PRACH transmission configuration and its selected SSB (Synchronization Signal Block), which is the time-frequency domain resource configured for PRACH (physical random access channel) transmission. During this step, the UE can attempt to receive an SSB from the gNB (or base station) and determine the best or suitable SSB, for example, one with the highest RSRP (Reference Signal Received Power) or an RSRP value higher than a predefined threshold. Alternatively, if no SSB with an RSRP value higher than the predefined threshold is available, any SSB can be selected.

[0019] Then, the RO used for transmitting PRACH is determined based on the relationship between SSB and RO. Based on this relationship, the gNB can determine the SSB selected by the UE. The same beam of the determined SSB can be used to transmit subsequent DL transmissions, which include msg2 and msg4. msg2 can also be referred to as RAR (Random Access Response, including RAR PDCCH (Physical Downlink Control Channel) and RAR PDSCH (Physical Data Shared Channel)). msg4 includes a PDSCH with the UE contention resolution identifier and the corresponding PDCCH. According to the current RACH procedure, in response to the reception of PRACH transmissions, RAR is transmitted. The UE monitors the RAR PDCCH within the RAR window. The RAR window starts from the first symbol of the earliest CORESET (control resource set), on which the UE is configured to receive PDCCHs for the Type 1-PDCCH CSS set. The RAR window includes at least a predefined number of symbols after the last symbol of the PRACH timing corresponding to the PRACH transmission.

[0020] For the CFRA procedure, the gNB indicates or configures the specific preamble and SSB to be selected for performing the CFRA procedure. If the SSB is associated with more than one RO, a PRACH mask index can also be indicated to further indicate the selected RO. Since PRACH resources are dedicated to the UE, there are no conflicts for PRACH transmissions between UEs.

[0021] Based on the time-domain and frequency-domain resource configuration, the resources used for PRACH transmission, i.e., ROs, can be determined. Whether an RO is a valid RO can be determined according to the following rules, wherein in the following embodiments, a valid RO determined according to the following existing rules can be referred to as a conventional valid RO. -If the UE is provided with a cell-specific semi-static frame structure configuration (e.g., via...) tdd-UL-DL- ConfigurationCommon Then, the PRACH timing in the PRACH slot is valid under the following conditions: -If it is within the UL symbol, or -If it is not before the SS / PBCH block in the PRACH slot, and starts at least after the last downlink symbol. The symbols, and at least after the last SS / PBCH block symbol 1 symbol, of which Provided in Table 1. For the preamble format B4, =0. Table 1

[0022] Different events may be used to trigger the CFRA procedure. The PRACH configuration / indication signaling differs for each event. Table 2 provides an overview of the triggering events and their corresponding PRACH configurations / indications. Table 2

[0023] In wireless communication systems, time-domain resources are divided between downlink and uplink using time-division duplex (TDD). Allocating a limited duration for the uplink in TDD results in reduced coverage, increased latency, and decreased capacity. As a potential enhancement to this limitation of conventional TDD operation, it is worthwhile to investigate the feasibility of allowing the simultaneous existence of downlink and uplink on the gNB side within the conventional TDD band, i.e., full-duplex, or more specifically, subband non-overlapping full-duplex (SBFD). Then, for some symbols configured as semi-static downlink resources or flexible resources, a portion of the frequency resource can be configured as UL (uplink) resources, such as UL subbands. Downlink or flexible symbols configured with UL subbands can be referred to as SBFD symbols. For some symbols configured as semi-static uplink resources or flexible resources, a portion of the frequency resource can be configured as DL (downlink) resources, such as DL subbands. Uplink or flexible symbols configured with DL subbands can also be referred to as SBFD symbols. Regardless of the approach, both uplink and downlink will exist in different frequency domain resources within the same time-domain resource. Figure 1 In the example shown, the frame structure is configured as DDDFU, where D represents a downlink symbol, F represents an uplink symbol, and U represents an uplink symbol. Additionally or alternatively, some frequency domain resources of a portion of the downlink resources and / or flexible resources (such as slots 1-3) are configured as UL subbands.

[0024] The UL subband in an SBFD symbol can be used to perform uplink transmissions for UEs with SBFD capability (or full-duplex capability) or SBFD-compatible UEs. In some examples, the intersection between the UL subband in the SBFD symbol and the initial UL BWP can be defined as the UL-available PRB (physical resource block) for SBFD random access operations. That is, uplink transmissions during the RACH procedure can be performed within the UL-available PRB. However, for UEs without SBFD capability, it can only perform UL transmissions using regular UL symbols or flexible symbols. Uplink transmissions during the random access procedure include the PRACH signal, msg3 PUSCH (including initial transmission and retransmission), and HARQ-ACK for msg4 PDSCH, etc. In full-duplex scenarios, SBFD symbols and regular UL symbols or flexible symbols can extend the total time-domain resources for uplink transmissions, thereby increasing available random access resources or enhancing the coverage of random access signals.

[0025] In some examples, the timing of UL transmissions within the UL subband / UL-available PRB differs from the timing of UL transmissions within the UL BWP. Therefore, the UE should obtain two UL transmission timings for subsequent uplink transmissions within the UL subband / UL-available PRB, respectively. For example, a first UL transmission timing and a second UL transmission timing are defined for the UL BWP and the UL subband / UL-available PRB, respectively. In some examples, the first UL transmission timing can be defined as a first time interval earlier than the DL receive timing. The second UL transmission timing can be defined as a second time interval earlier than either the DL receive timing or the first UL transmission timing. Alternatively, the second UL transmission timing can be defined as a time interval later than either the DL receive timing or the first UL transmission timing. In some examples, a fixed / configured time offset exists between the two UL transmission timings, and this fixed / configured time offset can be indicated in at least one of the following signaling: MIB, SIB1, random access response (RAR), or msg4.

[0026] In some examples, the PRACH transmission is sent based on the DL receive timing. The RAR will indicate a first timing advance (TA) value for the UL BWP, and a first UL transmission timing can be determined based on the transmission timing (DL receive timing) of the PRACH transmission and the indicated first timing advance value. A second UL transmission timing can then be calculated based on the first UL transmission timing and a fixed time offset. Alternatively, the RAR indicates a second timing advance value for the UL subband / UL-available PRB, and this second UL transmission timing can then be determined based on the transmission timing (DL receive timing) of the PRACH transmission and the indicated second timing advance value. The first UL transmission can be calculated based on the second UL transmission timing and a fixed / configured time offset.

[0027] In some examples, PRACH transmissions are sent based on the DL receive timing and a third time interval. That is, the PRACH transmission timing is determined by a third time interval earlier / later than the DL receive timing. The RAR indicates a third timing advance value for the UL BWP, and a first UL transmission timing can be determined based on the transmission timing (DL receive timing) of the PRACH transmission and the indicated third timing advance value. The second UL transmission timing can be calculated based on the first UL transmission timing and a fixed time offset. Alternatively, the RAR indicates a fourth timing advance value for the UL subband / UL-available PRB, and the second UL transmission timing can then be determined based on the transmission timing (DL receive timing) of the PRACH transmission and the indicated fourth timing advance value. The first UL transmission can be calculated based on the second UL transmission timing and a fixed / configured time offset.

[0028] In some examples, the transmission timing of the PRACH is determined based on the resource type used to transmit the PRACH. For example, if the PRACH is transmitted in a UL BWP (or a non-SBFD symbol), the transmission timing of the PRACH is determined to be the DL receive timing. Otherwise, if the PRACH is transmitted in an SBFD symbol (i.e., in a UL subband / UL-available PRB), the transmission timing of the PRACH is determined to be the time interval before or after the DL receive timing.

[0029] In some examples, the TA value indicated in the RAR is used to determine the UL transmission timing of msg3. Then, if the msg3 PUSCH is scheduled in a UL BWP (or a non-SBFD symbol), the indicated TA value is used to determine the UL transmission timing for the UL transmission in the UL BWP. Otherwise, if the msg3 PUSCH is scheduled in an SBFD symbol (i.e., in a UL subband / UL-available PRB), the indicated TA value is used to determine the UL transmission timing for the UL transmission in the UL subband / UL-available PRB.

[0030] In some examples, one of the two UL transmission timings is indicated via RAR, and the other UL transmission timing is indicated in msg4. In some examples, both UL transmission timings are indicated via RAR. Preliminary determination of RACH mode by the base station

[0031] This disclosure first describes examples for configuring and enabling a UE to perform RACH on SBFD resources. For example, the RACH procedure can be triggered by a PDCCH instruction, and the RACH mode can be determined by the gNB. Figure 2A flowchart illustrating the configuration or enabling of a device to perform RACH using SBFD resources is shown. In S110, a device, such as a user equipment or base station, receives configuration or signaling for determining the RACH operating mode, which includes full-duplex RACH operation or non-full-duplex RACH operation. In S120, the RACH operating mode is determined based on the configuration or signaling. Different considerations may exist for determining the RACH operating mode based on the configuration or signaling. Details are discussed in different sections of this disclosure.

[0032] In some implementations, the PDCCH instruction is a DCI format (such as DCI format 1-0) in which the CRC is scrambled by the C-RNTI (Cell Radio Network Temporary Identifier) ​​by setting the value of the FDRA (Frequency Domain Resource Allocation) field in the DCI format to all 1s. The remaining fields in this DCI format include a random access preamble index (used to indicate the preamble index), a UL / SUL indicator (used to indicate the carrier), an SS / PBCH block index (used to indicate the SSB index), a PRACH mask index (used to indicate at least a portion of the RO), a cell indicator (used to indicate the cell), and a PRACH retransmission indicator (used to indicate the initial transmission or retransmission of the PRACH), etc. The UE receiving the PDCCH instruction transmits the PRACH using the preamble indicated by the "Random Access Preamble Index" field. This PRACH is transmitted in the RO associated with the SSB indicated by the "SS / PBCH Block Index" field and on the carrier indicated by the "UL / SUL Indicator" field.

[0033] In some implementations, the RACH process includes two RACH modes: an SBFD RACH mode and a non-SBFD RACH mode. For the SBFD RACH mode, RO resources configured within an SBFD symbol that meet certain specific conditions can be considered valid ROs for PRACH transmission. These conditions may include the frequency domain resources of the configured RO being located within the UL subband, and / or the configured RO not preceding the SS / PBCH block in the PRACH time slot, and starting at least after the last downlink symbol. Symbols (in the absence of SBFD configuration), and starting at least after the last SS / PBCH block symbol. There are 1 symbol. Additionally or optionally, RO resources configured within an SBFD symbol will be considered invalid ROs and cannot be used for PRACH transmissions in non-SBFD RACH modes. If the UE is an SBFD-capable UE, for example, when the UE supports performing RACH procedures using SBFD resources, the RACH mode to be used should first be determined according to some examples. The UE can then determine the available resources for PRACH transmissions.

[0034] In some implementations, the two RACH modes can share the same time-frequency domain resource configuration signaling set (such as...) used for the PRACH transmission. RACH-ConfigCommon / EarlyUL-SyncConfig (Configuration of the identifier in the middle). For example... Figure 3 The example shown illustrates that, depending on the time-frequency domain resource configuration used for PRACH transmission, the configured RO resource can reside within a DL symbol. In non-SBFD RACH mode, this RO cannot be identified as a valid RO and cannot be associated with any SSB. RO resources residing within a DL symbol are not permitted for this PRACH transmission. For example... Figure 3 The SBFD RACH mode shown has five time slots (slots 0 to 4) in one frame structure period. This frame structure is configured as "DDDFU", where D represents a downlink symbol, U represents an uplink symbol, and F represents a flexible symbol. UL subbands can be introduced into DL or flexible resources, namely slots #1, #2, #3, and #4. These four time slots are then defined as SBFD resources. Configured ROs can reside within SBFD resources, and a configured RO in an SBFD resource may be determined as a valid RO if certain specific conditions are met. These conditions may include the configured RO being located within the frequency range of the UL subband.

[0035] In some implementations, two preamble sets are configured for SBFD RACH mode and non-SBFD RACH mode, respectively. Furthermore, at least one of the following parameters can be configured: a first starting preamble index, a first number of preambles configured for the first RACH mode, a second starting preamble index, a second number of preambles configured for the first RACH mode, a third number of preambles in each set, and the total number of preambles in both sets.

[0036] As an example, a first starting preamble index (e.g., index A) and a first number of preambles (e.g., N) are configured for a first RACH mode (e.g., a non-SBFD RACH mode). A first set of preambles from preamble #A to preamble #(A+N-1) can be used in the first RACH mode. Alternatively or additionally, a second starting preamble index (e.g., index B) and a second number of preambles (e.g., M) are configured for a second RACH mode (e.g., SBFD RACH mode). Here, N can be different from M. A second set of preambles from preamble #B to preamble #(B+M-1) will be used in the second RACH mode. In some implementations, the UE does not want to be configured with preamble indices that are simultaneously in the first and second preamble sets. That is, there is no overlap between the two preamble sets. In some examples, the number of preambles in different sets is the same, i.e., M=N, and a single parameter can be used to configure the number of preambles in different sets.

[0037] As another example, a first starting preamble index (e.g., index A) and a first number of preambles (e.g., N) are configured. A first set of preambles from preamble #A to preamble #(A+N-1) will be used for a first RACH mode (such as an SBFD RACH mode). The starting preamble index of a second set of preambles is determined to be preamble index (N+A), and the number of preambles in this second set is equal to N. A second set of preambles from preamble #(N+1) to preamble #(2N+A-1) will be used for a second RACH mode (such as a non-SBFD RACH mode).

[0038] As another example, the number of preambles in each preamble set is configured (e.g., N). The first preamble index (e.g., index C) to be used for CFRA is defined as the starting preamble index of the first preamble set. The first preamble set from preamble #C to preamble #(C+N-1) will be used for the first RACH mode (such as the SBFD RACH mode). The starting preamble index of the second preamble set is determined to be preamble index (N+C), and the number of this second preamble set is equal to N. The second preamble set from preamble #(N+A) to preamble #(2N+C-1) can be used for the second RACH mode (such as the non-SBFD RACH mode).

[0039] As another example, the total number of preambles that can be used for CFRA (i.e., preambles other than those used for CBRA and / or SI (System Information) requests) is divided into two sets, one for SBFD RACH mode and one for non-SBFD RACH mode. For example, there are P available preambles for CFRA. The first preamble set includes P / 2 preambles, and the second preamble set includes the remaining preambles, such as the last P / 2 preambles. In some examples, P is an odd number. or The first preamble set is formed by the preambles, and the subsequent... or The first preamble forms the second preamble set. Represents the smallest integer greater than or equal to a. It is the largest integer less than or equal to a. Alternatively or otherwise, the P preambles can be divided unevenly. For example, a preamble used for SBFD RACH mode can be larger than a preamble used for non-SBFD RACH mode, and vice versa.

[0040] Alternatively or concurrently, a total of Q preambles that can be used in both SBFD RACH and non-SBFD RACH modes are configured. These Q consecutive preambles are divided into two sets, one for SBFD RACH mode and one for non-SBFD RACH mode. For example, for CFRA, there are Q available preambles. The first set of preambles consists of the first Q / 2 preambles, and the second set consists of the remaining preambles (i.e., the last Q / 2 preambles). In some examples, Q is an odd number. or The first preamble set is formed by the preambles, and the subsequent... or The preambles form a second preamble set. Furthermore, the starting preamble index can be configured or determined as the first available preamble for the CFRA process (i.e., the first preamble other than the preamble used for CBRA and / or SI requests).

[0041] Alternatively, if the preamble index indicated by the PDCCH instruction belongs to the preamble set corresponding to the SBFD RACH mode, the UE may assume that the gNB instructs the UE to initiate the RACH procedure using the SBFD RACH mode. The UE can then determine the valid RO according to the valid RO determination rules for the SBFD RACH mode and select the valid RO corresponding to the SSB indicated by the PDCCH instruction to transmit the preamble indicated by the PDCCH instruction. Otherwise, if the preamble index indicated by the PDCCH instruction belongs to the preamble set corresponding to a non-SBFD RACH mode, the UE may assume that the gNB instructs the UE to initiate the RACH procedure using a non-SBFD RACH mode. The UE can determine the valid RO according to the valid RO determination rules for the non-SBFD RACH mode and select the valid RO corresponding to the SSB indicated by the PDCCH instruction to transmit the preamble indicated by the PDCCH instruction.

[0042] Alternatively, the PDCCH instruction may contain an information field indicating the RACH mode to be used by the UE. For example, this information field may be a "1" bit. This first value (e.g., "0") indicates that the UE initiates the RACH procedure using the SBFD RACH mode. The UE can then determine the valid RO according to the valid RO determination rules for the SBFD RACH mode and select the valid RO corresponding to the SSB indicated by the PDCCH instruction to send the preamble indicated by the PDCCH instruction. Alternatively, a second value (e.g., "1") indicates that the UE initiates the RACH procedure using a non-SBFD RACH mode. The UE can then determine the valid RO according to the valid RO determination rules for the non-SBFD RACH mode and select the valid RO corresponding to the SSB indicated by the PDCCH instruction to send the preamble indicated by the PDCCH instruction.

[0043] Alternatively, the information field in the PDCCH command may include at least three states. The first state indicates that the UE initiates the RACH procedure using the SBFD RACH mode. The second state indicates that the UE initiates the RACH procedure using a non-SBFD RACH mode. The third state indicates that the UE initiates the RACH procedure using either the SBFD RACH mode or a non-SBFD RACH mode. In other words, the third state gives the UE the autonomy to choose between the SBFD RACH mode and a non-SBFD RACH mode.

[0044] Alternatively, this information field may exist only when the UE first reports its SBFD RACH capability to the base station or when the network enables or configures the SBFD RACH function. In some implementations, this information field is absent or has 0 bits when the UE does not report its SBFD RACH capability or the network does not enable or configure the SBFD RACH function. In some implementations, RRC signaling is used to configure whether this information field exists.

[0045] Alternatively, the "PRACH mask index" information field can be interpreted as indicating which SSB-RO association period was used for this RACH procedure. For example... Figure 4 As illustrated, there are two associated periods: a first associated period and a second associated period. The first value of the "PRACH Mask Index" field indicates that the first SSB-RO associated period should be used for the RACH procedure. When the valid RO in the first SSB-RO associated period is within an SBFD symbol, the UE can determine that the SBFD RACH mode is used for this RACH procedure. On the other hand, the second value of the "PRACH Mask Index" field can indicate that the second SSB-RO associated period should be used for the RACH procedure. When the valid RO in the second SSB-RO associated period is within a non-SBFD symbol, the non-SBFD RACH mode is used for this RACH procedure. That is, in this example, this information field can indicate which SSB-RO associated period should be used for the RACH procedure, and the UE can determine whether to use the SBFD RACH mode or the non-SBFD RACH mode based on whether the valid RO in the associated period is an SBFD RO.

[0046] Alternatively, the third value of the "PRACH mask index" field indicates that more than one SSB-RO associated period can be used in the RACH procedure. The UE then determines which RACH mode to use. For example, the third value of the "PRACH mask index" field indicates that any SSB-RO associated period can be used. As another example, the third value of the "PRACH mask index" field indicates that any odd-numbered SSB-RO associated period can be used. As yet another example, the third value of the "PRACH mask index" field indicates that any even-numbered SSB-RO associated period can be used. In these cases, the UE can be given the option to determine whether to use the SBFD RACH mode or a non-SBFD RACH mode.

[0047] Alternatively, the "PRACH mask index" field may be interpreted as described above only when the value of the RRC parameter "ssb-perRACH-Occasion" is greater than or equal to 1. In other words, the UE interprets the "PRACH mask index" field differently depending on the value of the RRC parameter "ssb-perRACH-Occasion". The above interpretation can be enabled when the value of the RRC parameter "ssb-perRACH-Occasion" is greater than or equal to a threshold (such as 1).

[0048] Alternatively, separate time-frequency domain resource configuration signaling sets for PRACH transmission are used in both RACH modes.

[0049] Alternatively, different preamble sets can be defined for different RACH modes using the above method. In this case, if the preamble index indicated by the PDCCH instruction belongs to the preamble set corresponding to the RACH mode, the UE understands that the gNB instructs the UE to initiate the RACH procedure using the corresponding RACH mode. Then, the UE can determine the configured RO resources according to the time-frequency domain resource configuration signaling set for the corresponding RACH mode, determine the valid ROs according to the valid RO determination rules for the corresponding RACH mode, and select the valid RO corresponding to the SSB indicated by the PDCCH instruction to send the preamble indicated by the PDCCH instruction.

[0050] Alternatively or concurrently, the information field in the PDCCH instruction is used to indicate the RACH mode.

[0051] Alternatively, if a separate time-frequency domain resource configuration signaling set exists for PRACH transmissions in SBFD RACH mode, the UE understands that SBFD RACH mode will be used for RACH procedures triggered by PDCCH instructions. Otherwise, the UE understands that non-SBFD RACH modes will be used for RACH procedures triggered by PDCCH instructions.

[0052] Alternatively, both configuration signaling sets may not exist simultaneously. Therefore, in this case, the RACH mode used to initiate the RACH procedure is determined by the UE based on which configuration set exists.

[0053] Alternatively, the RACH mode to be used may be determined by the UE based on the resource type used by the PDCCH instruction. For example, if the UE detects a PDCCH instruction in an SBFD resource / symbol, the UE determines that the SBFD RACH mode should be used for the RACH procedure triggered by the PDCCH instruction. Otherwise, if the UE detects a PDCCH instruction in a non-SBFD resource / symbol (i.e., in a DL symbol without SBFD configuration), the UE determines that the non-SBFD RACH mode should be used for the RACH procedure triggered by the PDCCH instruction.

[0054] The above examples provide different methods for configuring and enabling a UE to perform a RACH procedure based on or on non-SBFD resources. The RACH procedure can be triggered by a PDCCH command, and the RACH mode can be determined or indicated to the UE by the gNB. Through this mode, the gNB can effectively control the RACH mode used by the UE for a RACH procedure triggered by a PDCCH command. The UE can be effectively configured and can effectively perform RACH on SBFD resources, improving overall access efficiency. Preliminary determination of RACH mode by UE

[0055] Alternatively, the UE can be configured and enabled to perform RACH on SBFD resources through timing configuration. The RACH procedure can be triggered by a PDCCH command, and the RACH mode can be determined by the UE.

[0056] Alternatively, if the UE reports SBFD RACH capability, the RACH mode used during a RACH process triggered by a PDCCH command can depend on the UE. For example, an RSRP threshold can be configured, and the UE determines the RACH mode based on the RSRP measurement and that threshold. If the RSRP measurement is higher than (or equal to) the RSRP threshold, the SBFD RACH mode is used. Otherwise, if the RSRP measurement is lower than (or equal to) the RSRP threshold, a non-SBFD RACH mode is used. Alternatively, if the RSRP measurement is higher than (or equal to) the RSRP threshold, a non-SBFD RACH mode is used. Otherwise, if the RSRP measurement is lower than (or equal to) the RSRP threshold, the SBFD RACH mode is used.

[0057] Alternatively or concurrently, two timing configuration sets are used separately for SBFD RACH mode and non-SBFD RACH mode. For example, another timing configuration set (e.g., occasions-SBFD) is introduced under RACH-ConfigCommon. The UE determines the RACH mode and selects an RO resource to transmit the preamble based on the timing configuration of the determined RACH mode. The gNB can determine the RACH mode determined by the UE based on which RO resource the preamble transmission is received in.

[0058] Alternatively, SBFD RACH mode and non-SBFD RACH mode share a single timing configuration set. If the UE selects an RO resource in SBFD resources, the base station understands that SBFD RACH mode is used for the RACH procedure; otherwise, if the UE selects an RO resource in non-SBFD resources, the base station understands that non-SBFD RACH mode is used for the RACH procedure. Therefore, the gNB can determine the mode of the current RACH procedure by which type of RO resource the preamble transmission is received.

[0059] Alternatively or concurrently, SBFD RACH mode and non-SBFD RACH models share a single timing configuration set. RO resources located within non-SBFD resources can also be used in SBFD RACH mode. That is, RO resources within non-SBFD resources are shared by both SBFD RACH mode and non-SBFD RACH mode. In this case, two preamble indices can be indicated via PDCCH instructions. The first preamble index corresponds to the first RACH mode (such as SBFD RACH mode), and the second preamble index corresponds to the second RACH mode (such as non-SBFD RACH mode). The UE determines the RACH mode. If the UE selects a shared RO for preamble transmission, the UE selects a preamble from the two indicated preamble indices according to the determined RACH mode. The gNB can determine the mode of the current RACH procedure by recognizing the preamble sent by the UE. That is, if a preamble with the first preamble index is received in a shared RO, the gNB determines to use the first RACH mode. Otherwise, if a preamble with a second preamble index is received in the shared RO, the gNB determines to use the second RACH mode.

[0060] Alternatively or concurrently, the PDCCH instruction may include an information field used to indicate power control parameters. In one example, these power control parameters include at least one of the following: a power offset value, a P0 value for PRACH transmission within an SBFD symbol, an α value for PRACH transmission within an SBFD symbol, the maximum output power configured for PRACH transmission by the UE within an SBFD symbol, a P0 value for PRACH transmission within a non-SBFD symbol, an α value for PRACH transmission within a non-SBFD symbol, and / or the maximum output power configured for PRACH transmission by the UE within a non-SBFD symbol. If the RO in the SBFD symbol is used to transmit PRACH, the power offset value indicates a power adjustment value. P0 indicates the target received power of the gNB. α indicates the path loss compensation factor.

[0061] Here, the RACH procedure can be triggered by a PDCCH command, and the RACH mode can initially be determined by the UE. The UE can effectively determine the RACH mode of the RACH procedure triggered by the PDCCH command and indicate it to the gNB. Therefore, the UE can efficiently execute the RACH procedure on SBFD resources, improving overall access efficiency. Switching and Beam Recovery

[0062] Furthermore, a RACH procedure can be triggered for handover / beam failure recovery. For the handover procedure, the first RRC signaling (e.g.) RACH-ConfigDedicated The CFRA resources (including time-frequency domain resources, preamble indexes for each reference signal such as SSB or CSI-RS) are used to configure the target cell for handover. If SBFD resources are configured in the target cell, SBFD configuration can be provided to the UE (e.g., in RRC signaling). ServingCellConfigCommon (In the middle). For beam failure recovery, the second RRC signaling (e.g.) BeamFailureRecoveryConfig It can be used to configure the CFRA resources of the serving cell.

[0063] Alternatively or additionally, the first or second RRC signaling includes a first indication of the RACH mode used to trigger the RACH procedure. In some examples, the first or second RRC signaling includes a second indication of whether the RO resources configured in the first or second RRC signaling are applied to the SBFD RACH mode. In some examples, if the first indication indicates the SBFD RACH mode, or if the configured RO resources are applied to the SBFD RACH mode according to the second indication, the UE can determine the valid RO according to the rules for the SBFD RACH mode. Alternatively or additionally, the UE can use the lowest PRB of the UL subband in the SBFD symbol or the lowest PRB of the available UL PRB to determine the lowest PRB for the PRACH transmission timing. In some examples, if the first indication indicates a non-SBFD RACH mode, or if the RO resources configured according to the second indication are not applied to the SBFD RACH mode, the UE can determine the valid RO according to the rules for the non-SBFD RACH mode. Alternatively, the UE can use the lowest PRB of the UL BWP (i.e., PRB 0) to determine the lowest PRB for PRACH transmission timing.

[0064] Alternatively or concurrently, two sets of preambles are defined for SBFD RACH mode and non-SBFD RACH mode, respectively. The preamble index indicated in the first or second RRC signaling can implicitly indicate the RACH mode used for the triggered RACH procedure.

[0065] Alternatively or additionally, the information element (IE) used to indicate the PRACH mask index (e.g., 'ra-ssb-OccisionMaskIndex') in the first or second signaling can be interpreted as indicating which ssb-RO association period was used in this RACH procedure. As an example, two association periods may exist. Figure 4 As shown, the RO of the first associated period is located within an SBFD symbol, while the RO of the second associated period is located within a non-SBFD symbol. A first value of the information element indicates that the first SSB-RO associated period should be used for the RACH procedure. When the valid RO in the first SSB-RO associated period is located within an SBFD symbol, the UE or BS determines that the SBFD RACH mode is used for this RACH procedure. Conversely, a second value of the information element indicates that the second SSB-RO associated period should be used for the RACH procedure. When the valid RO in the second SSB-RO associated period is located within a non-SBFD symbol, the UE or BS determines that the non-SBFD RACH mode is used for this RACH procedure.

[0066] In some implementations, a first information element (e.g., cfra-sbfd) is defined under the first / second RRC signaling for configuring CFRA resources in SBFD mode. A second information element (e.g., cfra) is also present for configuring CFRA resources in non-SBFD modes. In some examples, only one of the first and second information elements may be configured. The corresponding RACH mode will then be used in the RACH procedure.

[0067] Alternatively, the first and second information elements can be configured simultaneously. Furthermore, the UE can select a RACH mode for the RACH procedure.

[0068] Alternatively, two RO resource sets may be configured under the first or second RRC signaling. The first set is used for SBFD RACH mode, while the second set is used for non-SBFD RACH mode. The UE can determine the RACH mode and use the corresponding RO resource set to transmit the preamble. In some implementations, two preamble indices are indicated for each RS (reference signal) (SSB or CSI-RS). One preamble index is used for SBFD RACH mode, and the other preamble index is used for non-SBFD RACH mode. The UE can determine the RACH mode and transmit the corresponding preamble on the selected RO.

[0069] Here, the RACH procedure is triggered for handover or beam failure recovery. Through this procedure, the UE can effectively determine the RACH mode for the RACH procedure triggered by handover or beam failure recovery. The UE can efficiently perform RACH on SBFD resources, which can improve overall access efficiency. System Information (SI) Request

[0070] Alternatively, a RACH procedure can be triggered in response to an SI request. In NR (New Radio) systems, some SI messages (such as MIB, SIB1, etc.) are sent periodically. Other SI messages are sent as needed or based on requests from lower-level UEs. For SI messages sent as needed, RRC signaling (e.g., SI-RequestConfig) can be used to configure information for that request. This request can be based on msg1, requesting the corresponding SI message type by sending a specific PRACH. The RRC signaling can include RACH resource configuration, which includes a list of SI request resources. Each SI request resource in this list corresponds to a type of SI message. To enable RACH transmission for SI requests using SBFD resources, a similar method used for handover or beam recovery in the last section can be reused.

[0071] In some implementations, SBFD resource configuration information can be carried in SI messages, which are always broadcast periodically, for example, in SIB1. In other implementations, SBFD resource configuration information can be carried in SI messages sent as needed. To request this type of requested SI message (carrying SBFD resource configuration information), for example, the corresponding preamble can be sent only via RO in a non-SBFD symbol. That is, the RACH procedure for requesting this type of SI message should be a non-SBFD RACH mode. In some implementations, to request other SI messages (not carrying SBFD resource configuration information), either SBFD RACH mode or non-SBFD RACH mode can be used in the RACH procedure for SI message requests. Similar methods used in the previous section for handover or beam recovery can then be used.

[0072] In some implementations, multiple PRACH transmissions (or PRACH repetitions) can also be supported. For the selection of repetition factors for multiple PRACH transmissions, three repetition factors can be available (e.g., 2, 4, 8). Three RSRP thresholds are defined (e.g., rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, rsrp- ThresholdMsg1-RepetitionNum8 If the downlink path loss reference RSRP is less than rsrp- ThresholdMsg1-RepetitionNum8 If so, multiple PRACH transmissions with a repetition factor of 8 will be applied. Otherwise, if the RSRP referenced for downlink path loss is less than 8... rsrp-ThresholdMsg1-RepetitionNum4 If so, multiple PRACH transmissions with a repetition factor of 4 will be applied. Otherwise, if the RSRP referenced for downlink path loss is less than 4... rsrp-ThresholdMsg1- RepetitionNum2 Then, multiple PRACH transmissions with a repetition factor of 2 will be applied.

[0073] In some implementations, the SBFD RACH mode can only be used when multiple PRACH transmissions are used. In other words, if the RSRP referenced for downlink path loss is less than [value missing], then [the SBFD RACH mode is available]. rsrp-ThresholdMsg1-RepetitionNum2 Then, an SBFD RACH mode with multiple PRACH transmissions will be executed. In some implementations, if the RSRP referenced for downlink path loss is less than... rsrp-ThresholdMsg1-RepetitionNum8 In this case, multiple PRACH transmissions with eight repetitions will be performed in SBFD RACH mode. In some implementations, if the RSRP referenced for downlink path loss is less than... rsrp-ThresholdMsg1-RepetitionNum4 In this case, multiple PRACH transfers with four repetitions will be executed in SBFD RACH mode.

[0074] The examples here provide a method for configuring and enabling a UE to perform RACH on SBFD resources. A RACH procedure is triggered in response to an SI request, through which the UE can efficiently determine the RACH mode for the RACH procedure triggered in response to the SI request. The UE can then efficiently perform RACH on SBFD resources accordingly, thereby improving overall access efficiency. Configure using MAC CE

[0075] Alternatively, the RACH procedure is triggered by MAC layer signaling (e.g., MAC CE (MAC control unit)). For L1 / L3 triggered Mobility (LTM) cell handover, RO resources can be transmitted via RRC signaling (e.g., RACH-ConfigDedicated or RACH-ConfigCommon The configuration is done via MAC layer signaling. The preamble index and SS / PBCH block index used during the RACH process can be indicated via MAC layer signaling (e.g., the LTM cell handover command MAC CE). The specific format of the LTM cell handover command MAC CE is as follows: Figure 5 As shown.

[0076] Alternatively or concurrently, the RACH mode (including SBFD RACH mode or non-SBFD RACH mode) can be indicated in the MAC layer signaling. For example, any one of the 'R' bits can be used for RACH mode indication. In some implementations, the MAC layer signaling can indicate that the UE should use SBFD RACH mode, non-SBFD RACH mode, or either of these is acceptable. Then, any two 'R' bits can be used for RACH mode indication.

[0077] Alternatively, the MAC layer signaling may indicate two random access preamble indices, one for the non-SBFD RACH mode and the other for the SBFD RACH mode. That is, a second random access preamble index will be introduced. For example, another line could be added (e.g., Figure 6 The Oct 7 bit in the MAC CE is used to indicate the index of the second random access preamble. In some examples, the 6th 'R' bit of the MAC CE is used to indicate the index of the second random access preamble.

[0078] Alternatively or concurrently, one or more bits will be used to indicate the index offset between the second random access preamble index and the current random access preamble index (indicated in Oct 6). The corresponding 'R' bit in the MAC CE will be used to indicate this index offset. That is, one or more 'R' bits can be used to carry the information field. Figure 7In the example above, the first two bits in Oct 2 are used to indicate the index offset. As another example, the four 'R' bits in Oct 2 of a MAC CE would be defined to indicate the index offset. As yet another example, the three 'R' bits in Oct 1 of a MAC CE would be defined to indicate the index offset. As yet another example, the 'R' bits in Oct 4 of a MAC CE would be defined to indicate the index offset.

[0079] In some implementations, the MAC CE includes an information field used to indicate power control parameters. In one example, these power control parameters include at least one of the following: a power offset value, a P0 value for PRACH transmission within an SBFD symbol, an α value for PRACH transmission within an SBFD symbol, the maximum output power configured for PRACH transmission by the UE within an SBFD symbol, a P0 value for PRACH transmission within a non-SBFD symbol, an α value for PRACH transmission within a non-SBFD symbol, and / or the maximum output power configured for PRACH transmission by the UE within a non-SBFD symbol. If the RO in the SBFD symbol is used to transmit PRACH, the power offset value indicates a power adjustment value. P0 indicates the target received power of the gNB. α indicates a path loss compensation factor. The information field can be carried by introducing one or more newlines. Alternatively, one or more 'R' bits can be used to carry this information field.

[0080] Here, the RACH procedure is triggered by MAC layer signaling (e.g., MAC CE). The UE can effectively determine the RACH mode of the RACH procedure triggered by MAC layer signaling (e.g., MAC CE) through this signaling. This enables the UE to efficiently perform RACH on SBFD resources, improving overall access efficiency.

[0081] Figures 8A-8C A block diagram of an exemplary wireless communication system 20 according to some embodiments of the present disclosure is shown together. System 20 can perform the methods / steps disclosed in this disclosure and combinations or sub-combinations thereof. System 20 may include components and elements configured to support operational features that do not need to be described in detail herein.

[0082] System 20 may include at least one base station (BS) 110 (or RAN node), at least one user equipment (UE) 120, and at least one core network (CN) 130, including NF, RNDF, AF, AMF, CREF, or other functions. BS 110 includes a BS transceiver or transceiver module / circuit 112, a BS antenna system 116, a BS memory or memory module / circuit 114, a BS processor or processor module / circuit 113, and a network interface 111. Components of BS 110 may be electrically coupled and communicate with each other via a data communication bus 190 as needed. Similarly, UE 120 includes a UE transceiver or transceiver module / circuit 122, a UE antenna system 126, a UE memory or memory module / circuit 124, a UE processor or processor module / circuit 123, and an I / O interface 121. Components of UE 120 may be electrically coupled and communicate with each other via a data communication bus 190 as needed. UE 120 communicates with one or more BS 110s via a communication channel therebetween, which may be any wireless channel or other medium known in the art suitable for data transmission as described herein.

[0083] CN 130 includes at least one CN transceiver or transceiver module / circuit 132, at least one CN antenna system 136, at least one CN memory or memory module / circuit 134, at least one CN processor or processor module / circuit 133, and at least one network interface 131. The CN can be formed as a distributed system including multiple devices 130. Components of CN 130 can be electrically coupled and communicate with each other via a data communication bus 190 as needed. The CN can communicate with one or more application servers and one or more base stations (RAN nodes) via wired or wireless communication.

[0084] Processor modules / circuits 113, 123, and 133 may be implemented or realized using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, 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 way, the processor modules / circuits may be implemented as microprocessors, controllers, microcontrollers, state machines, etc. Processor modules / circuits may also be implemented as combinations of computing devices, such as combinations of digital signal processors and microprocessors, multiple microprocessors, one or more microprocessors integrated with a digital signal processor core, or any other such configuration.

[0085] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly embodied in hardware, firmware, software modules executed by processor modules / circuits 113, 123, 133, or any actual combination thereof. Memory modules / circuits 114, 124, 134 can be implemented as RAM memory, flash memory, EEPROM memory, registers, ROM memory, EPROM memory, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this respect, memory modules / circuits 114, 124, and 134 can be coupled to processor modules / circuits 113, 123, and 133, respectively, such that processor modules / circuits 113, 123, and 133 can read information from or write information to memory modules 114, 124, or 134, respectively. Memory modules / circuits 114, 124, and 134 can also be integrated into their respective processor modules / circuits 113, 123, and 133. In some embodiments, memory modules / circuits 114, 124, and 134 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by processor modules / circuits 113, 123, and 133, respectively. Memory modules / circuits 114, 124, and 134 may also each include non-volatile memory for storing instructions executed by processor modules / circuits 113, 123, and 133, respectively.

[0086] This document describes various exemplary embodiments of the present disclosure with reference to the accompanying drawings to enable those skilled in the art to make and use the disclosure. The disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary methods. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes may be rearranged while remaining within the scope of this disclosure. Therefore, those skilled in the art should understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, the disclosure is not limited to the specific order or hierarchy presented.

[0087] This disclosure is intended to cover any possible variations, uses, combinations or adaptations of this disclosure that follow the general principles thereof, and includes knowledge and conventional techniques known in the art that are not disclosed in this application.

[0088] It should be understood that this disclosure is not limited to the precise structures or operations shown above and in the accompanying drawings, and various modifications and changes can be made without departing from the scope of this application. The scope of this application is limited only by the appended claims.

[0089] The methods, apparatus, processes, circuits, and logic described above can be implemented in many different ways and in many different combinations of hardware and software. For example, all or part of the implementation may be a circuit including an instruction processor or controller, such as a central processing unit (CPU), microcontroller, or microprocessor; or as an application-specific integrated circuit (ASIC), programmable logic device (PLD), or field-programmable gate array (FPGA); or as a circuit including discrete logic or other circuit components, including analog circuit components, digital circuit components, or both; or any combination thereof. For example, the circuit may include discrete interconnect hardware components, or may be combined on a single integrated circuit die, distributed among multiple integrated circuit dies, or implemented in a multiple chip module (MCM) of multiple integrated circuit dies in a common package.

[0090] Therefore, circuitry can store or access instructions for execution, or its function can be implemented solely in hardware. Instructions can be stored in tangible storage media such as flash memory, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or on a disk or optical disc such as an optical disc read-only memory (CDROM), hard disk drive (HDD), or other disk or optical disc; or on or in another machine-readable medium. Products such as computer program products may include storage media and instructions stored in or on the media, and when executed by circuitry in the device, these instructions can cause the device to perform any of the processes shown above or in the accompanying drawings.

[0091] These implementations can be distributed. For example, the circuit may include multiple different system components such as multiple processors and memories, and may span multiple distributed processing systems. Parameters, databases, and other data structures may be stored and managed separately, may be incorporated into a single memory or database, may be logically and physically organized in many different ways, and may be implemented in many different ways. Example implementations include linked lists, program variables, hash tables, arrays, records (e.g., database records), objects, and implicit storage mechanisms. Instructions may form parts of a single program (e.g., subroutines or other code segments), may form multiple separate programs, may be distributed across multiple memories and processors, and may be implemented in many different ways. Example implementations include standalone programs, as well as as part of a library such as a dynamic link library (DLL). For example, the library may contain shared data and one or more shared programs that include instructions that, when executed by the circuit, perform any of the processes shown above or in the figures.

[0092] In some examples, each unit, subunit, and / or module of the system may include a logic component. Each logic component may be hardware or a combination of hardware and software. For example, each logic component may include an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), digital logic circuitry, analog circuitry, a combination of discrete circuitry, gates, or any other type of hardware or combination thereof. Alternatively or additionally, each logic component may include memory hardware such as a portion of memory that includes instructions executable by, for example, a processor or other processor to implement one or more features of the logic component. When any logic component includes a portion of memory containing instructions executable by a processor, the logic component may or may not include a processor. In some examples, each logic component may simply be a portion of memory or other physical memory that includes instructions executable by a processor or other processor to implement features of the corresponding logic component, and that logic component may not include any other hardware. Because each logic component includes at least some hardware, even if the included hardware includes software, each logic component may be interchangeably referred to as a hardware logic component.

[0093] The second action can be considered "in response" to the first action, regardless of whether the second action is directly or indirectly caused by the first action. The second action can occur much later than the first action and is still considered a response to the first action. Similarly, even if an intervention occurs between the first and second actions, and even if one or more of the intervention actions directly cause the second action to be performed, the second action can still be considered a response to the first action. For example, if the first action sets a flag, and a third action later initiates the second action at any time the flag is set, the second action can be considered a response to the first action.

[0094] In order to clarify its use and to issue this notice to the public, the phrase " < >、…and <n> at least one of them or< / n> 、< >、… <n> or at least one of the combinations thereof< / n> < >, ... and / or <n> "or"< / n> < >、...or <n> "At least one of" is defined by the applicant in the broadest sense, superseding any other implied definition above or below, and unless the applicant expressly indicates otherwise, means one or more elements selected from the group comprising A, B, ... and N. In other words, the phrase means any combination of one or more of elements A, B, ... or N, including any single element or a combination of that single element with one or more other elements, which may also include other elements not listed.< / n>

Claims

1. A wireless communication method, comprising: Obtain configuration or signaling for determining the RACH operation mode, wherein the RACH operation mode includes full-duplex RACH operation or non-full-duplex RACH operation; and The RACH operating mode is determined based on the configuration or signaling.

2. The method according to claim 1, wherein, Obtaining the configuration or signaling includes obtaining a first preamble set for the full-duplex RACH operation and a second preamble set for the non-full-duplex RACH operation.

3. The method according to claim 2, wherein Obtaining the configuration or signaling includes obtaining a PDCCH message indicating a preamble index; and Determining the RACH operation mode includes determining whether to perform the full-duplex RACH operation or the non-full-duplex RACH operation based on whether the preamble index belongs to the first preamble set or the second preamble set.

4. The method according to claim 1, wherein Obtaining the configuration or signaling includes obtaining a PDCCH message, which includes an indicator indicating whether to perform the full-duplex RACH operation or the non-full-duplex RACH operation.

5. The method according to claim 1, wherein Obtaining the configuration or signaling includes obtaining a PDCCH message, the PDCCH message including an instruction to the terminal to perform the full-duplex RACH operation, the non-full-duplex RACH operation, or to perform any of them based on the terminal's own decision.

6. The method according to claim 1, further comprising: The first communication node reports to the second communication node that the first communication node has the capability of full-duplex RACH operation, wherein obtaining the configuration or signaling includes obtaining a PDCCH message with an indicator indicating the RACH operation mode in response to the report.

7. The method according to claim 1, wherein, Obtaining the configuration or signaling includes obtaining a PDCCH message with a "PRACH mask index" field, which is configured to indicate which SSB-RO associated period was used for the RACH operation.

8. The method according to claim 1, wherein, Obtaining the configuration or signaling includes obtaining a PDCCH message with a "PRACH mask index" field, which is configured to indicate that the terminal is allowed to determine whether to perform the full-duplex RACH operation or the non-full-duplex RACH operation based on the terminal's own decision.

9. The method according to claim 1, wherein, Obtaining the configuration or signaling includes obtaining at least one of the following parameters: First start preamble index used for the full-duplex RACH operation; A first number of preambles configured for the full-duplex RACH operation; The second start preamble index used for the non-full-duplex RACH operation; A second number of preambles configured for the non-full-duplex RACH operation; The third number of preambles in the two preamble sets used respectively for the full-duplex RACH operation and the non-full-duplex RACH operation; and The total number of preambles in the two preamble sets.

10. The method according to claim 1, wherein, Determining the RACH operation mode includes determining whether to perform the full-duplex RACH operation or the non-full-duplex RACH operation based on whether the obtained configuration includes resources for the full-duplex RACH operation.

11. The method of claim 10, further comprising: If the obtained configuration includes resources for the full-duplex RACH operation, then it is determined that the full-duplex RACH operation will be performed; otherwise, it is determined that the non-full-duplex RACH operation will be performed.

12. The method of claim 1, wherein... Obtaining the configuration or signaling includes obtaining PDCCH messages from resources; and Determining the RACH operation mode includes determining whether to perform the full-duplex RACH operation or the non-full-duplex RACH operation based on the type of the resource carrying the PDCCH message.

13. The method of claim 12, wherein, Determining whether to perform the full-duplex RACH operation or the non-full-duplex RACH operation includes determining to perform the full-duplex RACH operation when the resource carrying the PDCCH message is a full-duplex resource.

14. The method of claim 1, wherein... Obtaining the configuration or signaling includes obtaining a first timing configuration set and a second timing configuration set; and Determining the RACH operation mode includes determining to perform the full-duplex RACH operation when using the first timing configuration set, and determining to perform the non-full-duplex RACH operation when using the second timing configuration set.

15. The method of claim 1, wherein... Obtaining the configuration or signaling includes obtaining a single timing configuration set; and Determining the RACH operation mode includes determining whether to perform the full-duplex RACH operation or the non-full-duplex RACH operation based on whether the terminal selects full-duplex or non-full-duplex resources.

16. The method of claim 1, further comprising receiving a PDCCH message, the PDCCH message indicating power control parameters, the power control parameters including a power offset value.

17. The method of claim 1, wherein... Obtaining the configuration or signaling includes providing signaling with an indication; and Determining the RACH operation mode includes determining, based on the signaling, whether to perform the full-duplex RACH operation or the non-full-duplex RACH operation.

18. The method of claim 17, wherein, The signaling having the indicated instruction includes a PRACH mask index.

19. The method of claim 1, wherein... Obtaining the configuration or signaling includes providing signaling having a first information element and a second information element; and Determining the RACH operation mode includes determining to perform the full-duplex RACH operation when the first information element exists, or determining to perform the non-full-duplex RACH operation when the second information element exists.

20. The method according to claim 1, wherein, Obtaining the configuration or signaling includes obtaining the settings or signaling via a System Information (SI) message, and the method further includes requesting the SI message via a RACH timing in one or more non-full-duplex symbols.

21. The method according to claim 1, wherein, Determining the RACH operating mode includes determining to perform the full-duplex RACH operation when multiple PRACH transmissions are present.

22. The method according to claim 1, wherein, Obtaining the configuration or signaling includes obtaining MAC layer signaling.

23. The method according to claim 22, wherein, The MAC layer signaling includes two random access preamble indices to indicate the full-duplex RACH operation and the non-full-duplex RACH operation, respectively.

24. The method according to claim 22, wherein, The MAC layer signaling includes two or more bits configured to indicate an index offset between two random access preamble indices used for the full-duplex RACH operation and the non-full-duplex RACH operation, respectively.

25. The method according to claim 22, wherein, The MAC layer signaling includes fields configured to indicate power control parameters for the full-duplex RACH operation and the non-full-duplex RACH operation.

26. A wireless communication method, comprising: Configuration or signaling is provided for determining the RACH operation mode, wherein the RACH operation mode includes full-duplex RACH operation or non-full-duplex RACH operation.

27. The method of claim 26, wherein, Providing the configuration or signaling includes providing a first preamble set for the full-duplex RACH operation and a second preamble set for the non-full-duplex RACH operation.

28. The method of claim 27, wherein Providing the configuration or signaling includes providing a PDCCH message, the PDCCH message indicating a preamble index; and The RACH operation mode is determined based on whether the preamble index belongs to the first preamble set or the second preamble set.

29. The method of claim 26, wherein Providing the configuration or signaling includes providing a PDCCH message, the PDCCH message including an indicator indicating whether to perform the full-duplex RACH operation or the non-full-duplex RACH operation.

30. The method of claim 26, wherein Providing the configuration or signaling includes providing a PDCCH message, the PDCCH message including an indicator for instructing the terminal to perform the full-duplex RACH operation, the non-full-duplex RACH operation, or to perform any of them based on the terminal's own decision.

31. The method of claim 26, further comprising: The second communication node receives a report from the first communication node that the first communication node has the full-duplex RACH operation capability, wherein providing the configuration or signaling includes providing a PDCCH message with an indicator indicating the RACH operation mode in response to the report.

32. The method according to claim 26, wherein, Providing the configuration or signaling includes providing a PDCCH message with a "PRACH mask index" field, which is configured to indicate which SSB-RO associated period was used for the RACH operation.

33. The method according to claim 26, wherein, Providing the configuration or signaling includes providing a PDCCH message with a "PRACH mask index" field, the "PRACH mask index" field being configured to indicate that the terminal is allowed to determine, based on the terminal's own decision, whether to perform the full-duplex RACH operation or the non-full-duplex RACH operation.

34. The method according to claim 26, wherein, Providing the configuration or signaling includes providing at least one of the following parameters: First start preamble index used for the full-duplex RACH operation; A first number of preambles configured for the full-duplex RACH operation; The second start preamble index used for the non-full-duplex RACH operation; A second number of preambles configured for the non-full-duplex RACH operation; The third number of preambles in the two preamble sets used respectively for the full-duplex RACH operation and the non-full-duplex RACH operation; and The total number of preambles in the two preamble sets.

35. The method according to claim 26, wherein, Providing the configuration or signaling for determining the RACH operation mode includes providing the configuration for determining the mode based on whether the provided configuration includes resources for the full-duplex RACH operation.

36. The method of claim 35, wherein if the provided configuration includes resources for the full-duplex RACH operation, the RACH operation mode is the full-duplex RACH operation, and otherwise, the RACH operation mode is the non-full-duplex RACH operation.

37. The method of claim 26, wherein The configuration or signaling provided for determining the RACH operation mode includes providing a PDCCH message from a resource to determine whether to perform the full-duplex RACH operation or the non-full-duplex RACH operation based on the type of the resource carrying the PDCCH message.

38. The method according to claim 37, wherein, When the resource carrying the PDCCH message is a full-duplex resource, the RACH operation mode is the full-duplex RACH operation.

39. The method of claim 26, wherein: Providing the configuration or signaling for determining the RACH operating mode includes providing a first timing configuration set and a second timing configuration set; and When the first timing configuration set is used, the RACH operation mode is the full-duplex RACH operation, and when the second timing configuration set is used, the RACH operation mode is the non-full-duplex RACH operation.

40. The method of claim 26, wherein Providing the configuration or signaling for determining the RACH operation mode includes providing a single timing configuration set for determining whether to perform the full-duplex RACH operation or the non-full-duplex RACH operation based on whether the terminal selects full-duplex resources or non-full-duplex resources.

41. The method of claim 26, further comprising providing a PDCCH message indicating power control parameters, the power control parameters including a power offset value.

42. The method of claim 26, wherein Providing the configuration or signaling for determining the RACH operation mode includes providing signaling having an indication for determining whether to perform the full-duplex RACH operation or the non-full-duplex RACH operation based on the signaling.

43. The method according to claim 42, wherein, The signaling with the indicated information includes a PRACH mask index.

44. The method of claim 26, wherein: Providing the configuration or signaling for determining the RACH operation mode includes providing signaling having a first information element and a second information element, for determining to perform the full-duplex RACH operation when the first information element is present, or determining to perform the non-full-duplex RACH operation when the second information element is present.

45. The method of claim 26, wherein providing the configuration or signaling for determining the RACH operating mode includes providing the configuration or signaling via a System Information (SI) message, the method further comprising receiving a request for the SI message via a RACH timing in one or more non-full-duplex symbols.

46. ​​The method of claim 26, wherein, When multiple PRACH transmissions are present, the RACH operation mode is determined to be the full-duplex RACH operation.

47. The method according to claim 1, wherein, Providing the configuration or signaling includes providing MAC layer signaling.

48. The method according to claim 47, wherein, The MAC layer signaling includes two random access preamble indices to indicate the full-duplex RACH operation and the non-full-duplex RACH operation, respectively.

49. The method according to claim 47, wherein, The MAC layer signaling includes two or more bits configured to indicate an index offset between two random access preamble indices used for the full-duplex RACH operation and the non-full-duplex RACH operation, respectively.

50. The method of claim 47, wherein, The MAC layer signaling includes fields configured to indicate power control parameters for the full-duplex RACH operation and the non-full-duplex RACH operation.

51. A wireless communication device comprising a memory circuit storing one or more programs and one or more processors electrically coupled to the memory circuit, wherein the one or more processors are configured to execute the one or more programs to perform the method of any one of claims 1 to 50 or a combination or sub-combination thereof.

52. A non-transient computer-readable storage medium storing one or more programs configured to, when executed by at least one processor, perform the method of any one of claims 1 to 50 or a combination or sub-combination thereof.

Images