Random access method for sub-band full duplex time slot in mobile communication

Abstract

Various solutions are described herein for random access of devices in sub-band full duplex slots in mobile communications. The device may determine whether its state satisfies a certain condition. Where the state of the device satisfies the condition, the device may decide to transmit a physical random access channel to a network in a sub-band full duplex slot.

Description

[0001] Cross-references

[0002] This disclosure is part of a non-provisional application claiming priority to U.S. Patent Application No. 63 / 518,573, filed August 10, 2023, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to mobile communications, and more specifically to random access in device-associated sub-band full duplex (SBFD) time slots in mobile communications. Background Technology

[0004] Unless otherwise stated herein, the methods described in this section are not prior art to the claims listed below, nor are they recognized as prior art by virtue of their inclusion in this section.

[0005] In fifth-generation (5G) New Radio (NR) mobile communication, sub-band full duplex (SBFD) technology has been introduced. Typically, SBFD technology allows uplink (UL) and downlink (DL) transmissions within the same frequency band, thereby improving spectrum efficiency and system capacity.

[0006] In certain scenarios, random access procedures can be performed based on SBFD technology. Specifically, messages for the random access procedure (e.g., random access message-1 containing a physical random access channel (PRACH) preamble) can be transmitted within SBFD slots / symbols, which may improve random access performance.

[0007] However, message transmission during random access procedures can cause significant interference, particularly inter-user equipment-cross-link interference (inter-UE-CLI). For example, for user equipment (UE) in idle mode, the base station may be unable to mitigate CLI due to the uncertainty of the random access procedure messages transmitted by the attacker UE (e.g., especially contention-based random access procedures), and CLI processing may be inefficient.

[0008] Therefore, reducing interference during random access procedures within SBFD time slots / symbols has become a crucial issue in newly developed wireless communication networks. Consequently, appropriate solutions are needed to avoid and reduce interference during random access procedures in SBFD communication. Summary of the Invention

[0009] The following is for illustrative purposes only and is not intended to be limiting in any way. That is, the following summary is intended to introduce the concepts, highlights, benefits, and advantages of the novel and non-obvious techniques described herein. Selected embodiments will be further described in the detailed description below. Therefore, the following summary is not intended to identify the essential features of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.

[0010] One objective of this disclosure is to provide a solution or scheme to address the aforementioned problems related to random access of mobile communication devices in subband full-duplex (SBFD) time slots.

[0011] In one aspect, a method may involve a device determining whether a state of the device satisfies a condition. The method may also involve the device, when the state of the device satisfies the condition, determining to send a Physical Random Access Channel (PRACH) to a network within an SBFD time slot.

[0012] In one aspect, an apparatus may include a transceiver that wirelessly communicates with at least one user equipment (UE) of a wireless network during operation. The apparatus may also include a processor communicatively connected to the transceiver. The processor may perform operations during operation, including determining whether a state of the apparatus satisfies a condition. The processor may also perform operations, including determining, when the state of the apparatus satisfies the condition, to send a PRACH to the network within an SBFD time slot.

[0013] It is worth noting that although the descriptions provided herein may be made in the context of certain wireless access technologies, networks, and network topologies (such as Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, 5G, New Radio (NR), Internet-of-Things (IoT), Narrowband Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), and 6G), the proposed concepts, schemes, and any variations / derivatives thereof can be implemented in other types of wireless access technologies, networks, and network topologies. Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0014] The accompanying drawings are included to provide a further understanding of this disclosure and form part of this disclosure. The drawings illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the disclosure. It should be noted that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to their actual dimensions in order to clearly illustrate the concepts of the disclosure.

[0015] Figure 1 This is a schematic diagram of an example scenario under the scheme described according to embodiments of the present disclosure.

[0016] Figure 2 This is a schematic diagram of an example scenario under the scheme described according to embodiments of the present disclosure.

[0017] Figure 3 This is a schematic diagram of an example scenario under the scheme described according to embodiments of the present disclosure.

[0018] Figure 4 This is a schematic diagram of an example scenario under the scheme described according to embodiments of the present disclosure.

[0019] Figure 5 This is a schematic diagram of an example scenario under the scheme described according to embodiments of the present disclosure.

[0020] Figure 6 This is a block diagram of an example communication system according to an embodiment of the present disclosure.

[0021] Figure 7 This is a flowchart of an example process according to an embodiment of the present disclosure. Detailed Implementation

[0022] This specification discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter and may be embodied in various forms. This disclosure may be embodied in many different forms and should not be construed as being limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided to make the description of this disclosure thorough and complete, and to fully convey the scope of this disclosure to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0023] Overview

[0024] The implementations of this disclosure relate to various techniques, methods, schemes, and / or solutions for random access in subband full-duplex (SBFD) time slots associated with mobile communication devices. According to this disclosure, several possible solutions can be implemented individually or in combination. That is, although these possible solutions may be described separately below, two or more of them can be implemented in one or another combination.

[0025] Regarding this disclosure, a Physical Random Access Channel (PRACH) (e.g., a random access message-1 containing a PRACH preamble) can be transmitted within an SBFD time slot if the user equipment (UE) state meets predetermined conditions. Specifically, the UE can determine whether the interference-related state conditions are met. If yes, this means that transmitting the PRACH within the SBFD time slot may not significantly cause interference. Therefore, the UE can transmit the PRACH within the SBFD time slot. If no, this means that transmitting the PRACH within the SBFD time slot may cause significant interference. Therefore, the UE may not transmit the PRACH within the SBFD time slot, but may instead transmit the PRACH within a conventional Time Division Duplex (TDD) time slot.

[0026] Figure 1 Example scenario 100 is illustrated under an implementation of the present disclosure. Scenario 100 involves at least one network node and one UE, which may be part of a wireless communication network (e.g., an LTE network, a 5G / NR network, an IoT network, or a 6G network). Scenario 100 illustrates a current network framework. The UE may connect to the network side. The network side may include one or more network nodes.

[0027] In some embodiments, the UE may receive higher-layer signaling (e.g., Radio Resource Control (RRC) configuration, System Information Block (SIB), etc.) containing condition-related configurations from the network node. In different modes (e.g., idle mode, active mode (connected mode), and inactive mode), before performing a random access procedure with the network node, the UE may determine whether interference-related conditions (e.g., inter-UE-CLI interference) are met. If the conditions are met, it means that transmitting the PRACH for the random access procedure within the SBFD time slot may not significantly cause interference. Therefore, the UE may transmit the PRACH within the SBFD time slot for the random access procedure. If the conditions are not met, it means that transmitting the PRACH within the SBFD time slot may cause significant interference. Therefore, the UE may not transmit the PRACH within the SBFD time slot, but may instead transmit the PRACH within the conventional TDD time slot for the random access procedure.

[0028] Figure 2 Example scenario 200 is illustrated under an implementation of the present disclosure. In some embodiments, interference-related states may include the transmit power of the PRACH, and condition-related configurations may include a power threshold. Specifically, the network node may pre-configure the power threshold for the UE via higher-layer signaling. Therefore, regardless of the mode (e.g., idle mode, active mode (connected mode), and inactive mode), when the UE needs to perform a random access procedure with the network node, the UE can determine whether the current transmit power configured for the PRACH is lower than the power threshold.

[0029] In some cases, if the current transmit power configured for PRACH is below a power threshold, this means that PRACH transmission during the random access procedure within the SBFD time slot may not significantly cause interference. Therefore, the UE may decide to transmit PRACH to the network node within the SBFD time slot for the random access procedure via at least one PRACH occasion (RO).

[0030] In some cases, if the current transmit power configured for PRACH is not lower than the power threshold, this means that PRACH transmission during the random access procedure within the SBFD time slot may significantly cause interference. Therefore, the UE may decide not to transmit PRACH to the network node for the random access procedure within the SBFD time slot. Instead, the UE may transmit PRACH to the network node for the random access procedure within the conventional TDD uplink time slot.

[0031] In some cases, if (1) the current transmit power configured for the PRACH is not lower than the power threshold (i.e., the current transmit power configured for the PRACH exceeds the power threshold), and (2) the PRACH preamble format (e.g., PRACH preamble format 0 as defined in the 3GPP specification) has a smaller bandwidth, this means that the PRACH for the random access procedure may not significantly cause interference when transmitted within the SBFD time slot. Therefore, the UE may decide to transmit the PRACH to the network node within the SBFD time slot using a smaller bandwidth for the random access procedure.

[0032] In some cases, if the current transmit power configured for another PRACH during a PRACH power boost is not lower than a power threshold (i.e., the current transmit power configured for another PRACH during a PRACH power boost exceeds a power threshold), this could significantly cause interference when transmitting another PRACH for a random access procedure within the SBFD time slot during the PRACH power boost. Therefore, the User Equipment (UE) may stop transmitting another PRACH to the network node for a random access procedure within the SBFD time slot during a PRACH power boost. Furthermore, if the current transmit power for another PRACH is lower than a power threshold after the PRACH power boost process has been paused, the UE may decide to transmit the other PRACH to the network node within the SBFD time slot.

[0033] In some implementations, the power threshold can be based on the preamble receive target power (i.e., as defined in the 3GPP specification). preambleReceivedTargetPower The power threshold is determined by parameters or UE-CLI (User Equipment Cross-Link Interference). In some cases, the power threshold can be determined to be a value higher than the preamble receive target power. In other cases, the power threshold can be determined to ensure minimum UE-CLI or to eliminate UE-CLI.

[0034] In some implementations, the power threshold can be configured for each PRACH occasion or each PRACH preamble format. More specifically, the power threshold can vary based on different PRACH occasions or different PRACH preamble formats.

[0035] Figure 3 Example scenario 300 of an implementation scheme according to this disclosure is illustrated. In some embodiments, the interference-related state may include PRACH leakage, and the condition-related configuration may include a leakage threshold. Specifically, the network node may pre-configure the leakage threshold to the UE via higher-layer signaling. Therefore, regardless of the mode (e.g., idle mode, active mode (connected mode), and inactive mode), when the UE needs to perform a random access procedure with the network node, the UE can determine whether the PRACH leakage is below the leakage threshold.

[0036] In some cases, if the PRACH leakage is below the leakage threshold, it means that transmitting the PRACH for a random access procedure within the SBFD time slot may not significantly cause interference. Therefore, the UE may decide to transmit the PRACH to the network node via at least one RO within the SBFD time slot for the random access procedure.

[0037] In some cases, if PRACH leakage does not fall below the PRACH threshold, this could significantly cause interference when transmitting the PRACH for a random access procedure within the SBFD time slot. Therefore, the UE may decide not to transmit the PRACH to the network node for a random access procedure within the SBFD time slot. Instead, the UE can transmit the PRACH to the network node for a random access procedure within the conventional TDD time slot.

[0038] In some cases, if (1) the PRACH leakage is not below the leakage threshold (i.e., the PRACH leakage exceeds the leakage threshold), and (2) the PRACH preamble format (e.g., PRACH preamble format 0 as defined in the 3GPP specification) has a smaller bandwidth, this means that transmitting the PRACH for a random access procedure within the SBFD time slot may not significantly cause interference. Therefore, the UE may decide to transmit the PRACH to the network node using a smaller bandwidth within the SBFD time slot for the random access procedure.

[0039] In some implementations, the leakage threshold can be determined based on the level of in-band transmission or UE-CLI interference. In some cases, the leakage threshold can be determined to be below the level of in-band transmission. In some cases, the leakage threshold can be determined to ensure minimum UE-CLI interference or eliminate UE-CLI interference. For example, in-band transmission is defined as: (1) the average transmission across 12 subcarriers (i.e., 1 resource block); and (2) as a function of the resource block offset from the edge of the allocated uplink transmission bandwidth. In-band transmission is measured as the ratio of UE output power in unallocated resource blocks to UE output power in allocated resource blocks. The average value of in-band transmission measurements should not exceed the corresponding value specified in the 3GPP specification. In some scenarios, wider resource block allocations may lead to higher leakage, and resource blocks closer to the edge of the allocated uplink transmission bandwidth may experience higher leakage.

[0040] In some implementations, a PRACH leak may include a leak on the first resource block of the downlink subband within the SBFD time slot. In some implementations, a PRACH leak may include a leak on the reference resource.

[0041] Figure 4Example scenario 400 of an implementation according to this disclosure is illustrated. In some embodiments, interference-related states may include the PRACH frequency resource location (e.g., the frequency resource location of RO), and condition-related configurations may include the center of the uplink subband of the SBFD slot. Specifically, regardless of the mode (e.g., idle mode, active mode (connected mode), and inactive mode), when the UE needs to perform a random access procedure with a network node, the UE can determine whether the PRACH frequency resource location is close to the center of the uplink subband of the SBFD slot.

[0042] In some cases, if the PRACH frequency resource is located near the center of the uplink subband of the SBFD time slot, this means that transmitting the PRACH for a random access procedure within the SBFD time slot may not significantly cause interference. Therefore, the UE may decide to transmit the PRACH to the network node within the SBFD time slot for the random access procedure.

[0043] In some cases, if the PRACH frequency resource location is not close to the center of the uplink subband of the SBFD time slot (i.e., if the PRACH frequency resource location is close to the edge of the uplink subband of the SBFD time slot), this means that when the PRACH for the random access procedure is transmitted within the SBFD time slot, it may cause significant interference. Therefore, the User Equipment (UE) may decide not to transmit the PRACH to the network node for the random access procedure within the SBFD time slot. Instead, the UE may transmit the PRACH to the network node for the random access procedure within a conventional Time Division Duplex (TDD) time slot.

[0044] Figure 5 Example scenario 500 is illustrated under a scheme according to embodiments of this disclosure. In some embodiments, interference-related states may include the transmit power of the PRACH, and condition-related configurations may include a power threshold determined based on the PRACH frequency resource allocation. Specifically, the network node can pre-configure multiple power thresholds for the UE via higher-layer signaling. The UE can determine a power threshold from the multiple power thresholds based on the current PRACH frequency resource allocation. Therefore, regardless of the mode (e.g., idle mode, active mode (connected mode), and inactive mode), when the UE needs to perform a random access procedure with the network node, the UE can determine whether the current transmit power configured for the PRACH is lower than the power threshold.

[0045] In some implementations, PRACH frequency resource allocation may include at least one of the center of the uplink subband of the SBFD time slot and the number of resource blocks allocated for PRACH.

[0046] Regarding the PRACH frequency resource allocation including the center of the uplink subband of the SBFD time slot, the network node can pre-configure a lookup table for the UE via higher-layer signaling. The lookup table can include multiple power thresholds and relationships between multiple PRACH frequency resource locations. The UE can determine the power threshold based on the current PRACH frequency resource location according to the lookup table. For example, the UE can: (1) determine the power threshold as a first value when the current PRACH frequency resource location is close to the center of the uplink subband of the SBFD time slot, or (2) determine the power threshold as a second value when the PRACH frequency resource location is not close to the center of the uplink subband of the SBFD time slot (i.e., when the PRACH frequency resource location is close to the edge of the uplink subband of the SBFD time slot), and the second value may be lower than the first value. In other words, when the PRACH frequency resource location is close to the center of the uplink subband of the SBFD time slot, the power threshold may be determined to be higher, and when the PRACH frequency resource location is close to the edge of the uplink subband of the SBFD time slot, the power threshold may be determined to be lower.

[0047] Regarding PRACH frequency resource allocation, which includes the number of resource blocks allocated for PRACH, network nodes can pre-configure a lookup table for the UE via higher-layer signaling. The lookup table can include the relationship between multiple power thresholds and multiple resource block numbers allocated for PRACH. The UE can determine the power threshold based on the current number of resource blocks allocated for PRACH according to the lookup table. For example, the UE can: (1) determine the power threshold as a first value when the current number of resource blocks allocated for PRACH is equal to a first number, or (2) determine the power threshold as a second value when the current number of resource blocks allocated for PRACH is equal to a second number lower than the first number, where the first value may be lower than the second value. In other words, when the number of resource blocks allocated for PRACH is configured to be low, the power threshold may be determined to be high, and when the number of resource blocks allocated for PRACH is configured to be high, the power threshold may be determined to be low.

[0048] Regarding PRACH frequency resource allocation, which includes the PRACH frequency resource location and the number of resource blocks allocated to the PRACH, network nodes can pre-configure a lookup table for the UE via higher-layer signaling. The lookup table can include multiple power thresholds, multiple PRACH frequency resource locations, and multiple resource block numbers allocated to the PRACH. The UE can determine the power threshold based on the lookup table according to the current PRACH frequency resource location and the current number of resource blocks allocated to the PRACH. For example, the UE can: (1) determine the power threshold as a first value when the current PRACH frequency resource location is close to the center of the uplink subband of the SBFD time slot and the current number of resource blocks allocated to the PRACH is equal to a first number, or (2) determine the power threshold as a second value when the current PRACH frequency resource location is not close to the center of the uplink subband of the SBFD time slot (i.e., the current PRACH frequency resource location is close to the edge of the uplink subband of the SBFD time slot) and the current number of resource blocks allocated to the PRACH is equal to a second number lower than the first number, where the first value may be lower than the second value. In other words, when the current PRACH frequency resource location is close to the center of the uplink subband of the SBFD time slot and the number of resource blocks allocated to PRACH is configured to be low, the power threshold may be determined to be high; when the current PRACH frequency resource location is not close to the center of the uplink subband of the SBFD time slot and the number of resource blocks allocated to PRACH is configured to be high, the power threshold may be determined to be low.

[0049] In some cases, if the current transmit power configured for PRACH is lower than the power threshold determined based on PRACH frequency resource allocation, this means that transmitting the PRACH for a random access procedure within the SBFD time slot may not significantly cause interference. Therefore, the UE may decide to transmit the PRACH to the network node within the SBFD time slot for the random access procedure.

[0050] In some cases, if the current transmit power configured for the Physical Random Access Channel (PRACH) is not lower than the power threshold determined based on PRACH frequency resource allocation, this could significantly cause interference when transmitting the PRACH for a random access procedure within a Subband Full-Duplex (SBFD) slot. Therefore, the User Equipment (UE) may decide not to transmit the PRACH to the network node for a random access procedure within an SBFD slot. Instead, the UE can transmit the PRACH to the network node for a random access procedure within a conventional Time Division Duplex (TDD) slot.

[0051] Example Implementation

[0052] Figure 6An example communication system 600 is shown, comprising an example communication device 610 and an example network device 620, consistent with one embodiment of this disclosure. Each of the communication device 610 and the network device 620 can perform various functions to implement the schemes, techniques, processes, and methods described herein, which relate to random access of a UE and a network device in an SBFD time slot in mobile communications, including the scenarios / schemes described above and the process 700 described below.

[0053] Communication device 610 may be part of an electronic device, which may be a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, communication device 610 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device such as a tablet, laptop, or notebook computer. Communication device 610 may also be part of a machine-type device, which may be an Internet of Things (IoT), Narrowband Internet of Things (NB-IoT), or Industrial Internet of Things (IIoT) device, such as a fixed or stationary device, a home appliance, a wired communication device, or a computing device. For example, communication device 610 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. Alternatively, communication device 610 may be implemented in the form of one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more Reduced Instruction Set Computing (RISC) processors, or one or more Complex Instruction Set Computing (CISC) processors. Communication device 610 may include... Figure 6 At least some of the components shown, such as processor 612. Communication device 610 may also include one or more other components unrelated to the scheme of this disclosure (e.g., internal power supply, display device, and / or user interface device), therefore, these components of communication device 610 are not... Figure 6 This is shown in the text and not described below, in order to keep it concise.

[0054] Network device 620 may be part of a network device, which may be a network node such as a satellite, base station, small cell, router, or gateway. For example, network device 620 may be implemented in an eNodeB in an LTE network, a gNB in ​​a 5G / NR, IoT, NB-IoT, or IIoT network, or a satellite or base station in a 6G network. Alternatively, network device 620 may be implemented as one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network device 620 may include... Figure 6At least some of the components shown are included, such as processor 622. Network device 620 may also include one or more other components unrelated to the scheme of this disclosure (e.g., internal power supply, display device, and / or user interface device), therefore, these components of network device 620 are not... Figure 6 This is shown in the text and not described below, in order to keep it concise.

[0055] In one aspect, each of processors 612 and 622 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, although the singular term "processor" is used herein to refer to processors 612 and 622, each of processors 612 and 622 may include multiple processors according to certain embodiments of this disclosure, and may include a single processor in other embodiments. In another aspect, each of processors 612 and 622 may be implemented in hardware (and optionally firmware) comprising, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactor diodes, these components being configured and arranged to achieve a particular purpose of this disclosure. In other words, in at least some embodiments, each of processors 612 and 622 is a dedicated machine specifically designed, arranged, and configured to perform specific tasks, including autonomous reliability enhancements in devices (e.g., represented by communication device 610) and networks (e.g., represented by network device 620) according to various embodiments of this disclosure.

[0056] In some implementations, the communication device 610 may further include a transceiver 616 connected to the processor 612, which is capable of wirelessly transmitting and receiving data. In some implementations, the communication device 610 may further include a memory 614 connected to the processor 612, which can be accessed by the processor 612 to store data. In some implementations, the network device 620 may also include a transceiver 626 connected to the processor 622, which is capable of wirelessly transmitting and receiving data. In some implementations, the network device 620 may further include a memory 624 connected to the processor 622, which can be accessed by the processor 622 to store data. Therefore, the communication device 610 and the network device 620 can communicate wirelessly via transceiver 616 and transceiver 626, respectively. To aid in better understanding, the following description of the operation, functions, and capabilities of communication device 610 and network device 620 is performed in a mobile communication environment, wherein communication device 610 is implemented as or serves as a communication device or user equipment (UE), and network device 620 is implemented as or serves as a network node of a communication network.

[0057] Example Process

[0058] Figure 7 An example flow 700 according to an implementation of this disclosure is shown. Flow 700 may be an example implementation of the above-described scenario / scheme, whether partially or entirely, involving random access in the SBFD time slot of this disclosure. Flow 700 may represent an aspect of the implementation of the features of communication device 610. Flow 700 may include one or more operations, actions, or functions shown by one or more of steps 710 to 720. Although shown as discrete steps, the individual steps of flow 700 may be divided into more steps, combined into fewer steps, or omitted depending on the desired implementation. Furthermore, the steps of flow 700 may be arranged in accordance with... Figure 7 The process 700 may be executed in the order shown, or in a different order. Process 700 may be implemented by communication device 610 or any suitable user equipment or machine type device. For illustrative purposes only and without limitation, process 700 is described below in the context of communication device 610. Process 700 may begin at step 710.

[0059] In step 710, process 700 may involve the processor 612 of communication device 610 determining whether the state of communication device 610 meets a condition. Process 700 can proceed from step 710 to step 720.

[0060] In step 720, process 700 may involve the processor 612 of communication device 610 sending a PRACH to network device 620 in the SBFD time slot when the state of communication device 610 meets the condition.

[0061] In some implementations, the state of communication device 610 may include the transmit power of PRACH, and this condition may include a power threshold. Process 700 may involve processor 612 determining whether the transmit power of PRACH is below the power threshold. Process 700 may involve processor 612 transmitting PRACH to network device 620 within the SBFD time slot when the transmit power of PRACH is below the power threshold.

[0062] In some implementations, the power threshold can be determined based on the preamble received target power or UE-CLI cross-link interference.

[0063] In some implementations, the power threshold can be configured for each PRACH occasion or each PRACH preamble format.

[0064] In some implementations, process 700 may involve processor 612 sending PRACH to network device 620 within the SBFD time slot when the PRACH transmit power exceeds a power threshold and the PRACH preamble format has a small bandwidth.

[0065] In some implementations, process 700 may involve processor 612 stopping the transmission of another PRACH to network device 620 in the SBFD time slot during the PRACH power boosting process, when the transmit power of another PRACH is not lower than the power threshold.

[0066] In some implementations, process 700 may involve processor 612 sending a PRACH to network device 620 in the SBFD time slot after pausing the PRACH power boosting process, provided that the transmit power of another PRACH is below a power threshold.

[0067] In some implementations, the state of communication device 610 may include PRACH leakage, and this condition may include a leakage threshold. Process 700 may involve processor 612 determining whether the PRACH leakage is below the leakage threshold. Process 700 may involve processor 612 sending a PRACH to network device 620 within the SBFD time slot when the PRACH leakage is below the leakage threshold.

[0068] In some implementations, the leakage threshold can be determined based on the level of in-band transmission or UE-CLI cross-link interference.

[0069] In some implementations, a PRACH leak may include a leak on the first resource block of a downlink subband or a leak on a reference resource.

[0070] In some implementations, process 700 may involve processor 612 deciding to send PRACH to network device 620 within the SBFD time slot if PRACH leakage exceeds a leakage threshold and the PRACH preamble format of PRACH has low bandwidth.

[0071] In some implementations, the state of communication device 610 may include the PRACH frequency resource location, and this condition may include the center of the uplink subband of the SBFD time slot. Process 700 may involve processor 612 determining whether the PRACH frequency resource location is close to the center of the uplink subband of the SBFD time slot. Process 700 may involve processor 612 transmitting PRACH to network device 620 within the SBFD time slot when the PRACH frequency resource location is close to the center of the uplink subband of the SBFD time slot.

[0072] In some implementations, the state of communication device 610 may include the transmit power of PRACH, and this condition may include a power threshold determined based on PRACH frequency resource allocation. Process 700 may involve processor 612 determining whether the transmit power of PRACH is lower than the power threshold determined based on PRACH frequency resource allocation. Process 700 may involve processor 612 transmitting PRACH to network device 620 within the SBFD time slot when the transmit power of PRACH is lower than the power threshold determined based on PRACH frequency resource allocation.

[0073] In some implementations, PRACH frequency resource allocation may include at least one of the center of the uplink subband of the SBFD time slot and the number of resource blocks allocated for PRACH.

[0074] In some implementations, process 700 may involve processor 612 determining a power threshold based on the center of the uplink subband of the SBFD time slot, wherein: (1) when the PRACH frequency resource location is close to the center of the uplink subband of the SBFD time slot, the power threshold is determined to be a first value, or (2) when the PRACH frequency resource location is not close to the center of the uplink subband of the SBFD time slot, the power threshold is determined to be a second value, and the second value is lower than the first value.

[0075] In some implementations, the power threshold can be determined based on a lookup table that contains relationships between multiple power thresholds and multiple PRACH frequency resource locations.

[0076] In some implementations, process 700 may involve processor 612 determining a power threshold based on the number of resource blocks allocated to PRACH, wherein: (1) the power threshold is determined to be a first value when the number of resource blocks allocated to PRACH is equal to a first number, or (2) the power threshold is determined to be a second value when the number of resource blocks allocated to PRACH is equal to a second number less than the first number, wherein the first value is less than the second value.

[0077] In some implementations, the power threshold can be determined based on a lookup table that contains relationships between multiple power thresholds and the number of multiple resource blocks allocated to PRACH.

[0078] In some implementations, process 700 may involve processor 612 determining a power threshold based on the center of the uplink subband of the SBFD time slot and the number of resource blocks allocated for PRACH, wherein: (1) the power threshold is determined to be a first value when the PRACH frequency resource location is close to the center of the uplink subband of the SBFD time slot and the number of resource blocks allocated for PRACH is equal to a first number, or (2) the power threshold is determined to be a second value when the PRACH frequency resource location is not close to the center of the uplink subband of the SBFD time slot and the number of resource blocks allocated for PRACH is equal to a second number lower than the first number, wherein the first value is lower than the second value.

[0079] In some implementations, the power threshold can be determined based on a lookup table that contains relationships between multiple power thresholds, multiple PRACH frequency resource locations, and multiple resource blocks allocated to PRACH.

[0080] Additional notes

[0081] The topics described herein sometimes demonstrate different components contained within or connected to other components. It should be understood that the architectures depicted are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components to achieve the same functionality is effectively “associated” to achieve the desired function. Therefore, any two components combined in this document to achieve a particular function can be considered “associated” together to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered “operably connected” or “operably coupled” together to achieve the desired function, and any two components that can be so associated can also be considered “operably coupled” together to achieve the desired function. Specific examples of operational coupling include, but are not limited to, physically matable and / or physically interactive components and / or wirelessly interactive components and / or logically interactive and / or logically interactive components.

[0082] Furthermore, regarding the use of virtually any plural and / or singular terms in this document, a person with technical skills may appropriately translate from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be explicitly listed in this document.

[0083] Furthermore, those skilled in the art will understand that, in general, the terminology used herein, particularly in appended claims, such as the body of an appended claim, is often considered "open" terms; for example, the word "comprising" should be interpreted as "comprising but not limited to," the word "having" should be interpreted as "having at least," and the word "including" should be interpreted as "including but not limited to," etc. Those skilled in the art will also understand that if a particular quantity introduced in a claim is intentional, that intention will be explicitly stated in the claim; if no such statement is made, then such intention does not exist. For example, to aid understanding, the appended claims below may contain the use of the introductory phrases "at least one" and "one or more" to introduce the claims. However, the use of these phrases should not be construed as implying that a claim introduced by the indefinite article "a" or "an" is limited to containing only one such claim, even if the same claim includes the introductory phrase "one or more" or "at least one" and indefinite articles such as "a" or "an," for example, "a" and / or "an" should be interpreted as "at least one" or "one or more"; the same applies to definite articles used to introduce claims. Furthermore, even when a specific number of claims is explicitly stated, those skilled in the art will recognize that such a statement should be interpreted as at least that number. For example, simply stating "two claims" without any other modifiers means at least two claims, or two or more claims. Additionally, when using conventions such as "at least one A, B, and C," such a structure is generally understood by those skilled in the art. For example, "a system having at least one A, B, and C" includes, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and systems having both A, B, and C. Similarly, when using conventions such as "at least one A, B, or C," such a structure is generally understood by those skilled in the art. For example, "a system having at least one A, B, or C" includes, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and systems having both A, B, and C. Those skilled in the art will also understand that virtually any extractive word and / or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to include the possibility of containing one term, either term, or both terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B".

[0084] As can be seen from the foregoing, various embodiments of this disclosure have been described herein for illustrative purposes, and various modifications can be made without departing from the scope and spirit of this disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, and their true scope and spirit are indicated by the following claims.

Claims

1. A method comprising: A processor of a device determines whether a state of the device satisfies a condition. as well as When the device's state meets the condition, the processor sends a physical random access channel to a network within a subband full-duplex time slot.

2. The method of claim 1, wherein the state of the device includes a transmit power of the physical random access channel, the condition includes a power threshold, and the step of determining whether the state of the device satisfies the condition includes: Determine whether the transmit power of the physical random access channel is lower than the power threshold; When the device's state meets the condition, the step of sending the physical random access channel to the network within the sub-band full-duplex time slot includes: When the transmit power of the physical random access channel is lower than the power threshold, the physical random access channel is transmitted to the network within the full-duplex time slot of the sub-band.

3. The method of claim 2, wherein the power threshold is determined based on the target power of the preamble or cross-link interference between user equipment.

4. The method of claim 2, wherein the power threshold is configured according to each physical random access channel scenario or each physical random access channel preamble format.

5. The method of claim 1, wherein the state of the device includes a transmit power of the physical random access channel, the condition includes a power threshold, and the step of determining whether the state of the device satisfies the condition includes: Determine whether the transmit power of the physical random access channel exceeds the power threshold; When the device's state meets the condition, the step of sending the physical random access channel to the network within the sub-band full-duplex time slot includes: If the transmit power of the physical random access channel exceeds the power threshold and the physical random access channel preamble format of the physical random access channel has a small bandwidth, the physical random access channel is transmitted to the network within the subband full-duplex time slot.

6. The method of claim 2, further comprising: During the power enhancement process of a physical random access channel, if the transmit power of another physical random access channel is not lower than the power threshold, the processor shall stop transmitting the other physical random access channel to the network within the full-duplex time slot of that subband.

7. The method of claim 6, further comprising: After pausing the power boosting process of the physical random access channel, when the transmit power of the other physical random access channel is lower than the power threshold, the processor sends the other PRACH to the network in the subband full-duplex time slot.

8. The method of claim 1, wherein the state of the device includes a physical random access channel leakage, the condition includes a leakage threshold, and the step of determining whether the state of the device satisfies the condition includes: Determine whether the leakage of the physical random access channel is below the leakage threshold; The step of sending the physical random access channel to the network when the device's state meets the condition includes: When the leakage of the physical random access channel is below the leakage threshold, the physical random access channel is sent to the network within the full-duplex time slot of the sub-band.

9. The method of claim 8, wherein the leakage threshold is determined based on the level of in-band transmission or cross-link interference between user equipment.

10. The method of claim 8, wherein the physical random access channel leakage includes leakage on a first resource block of a downlink subband or leakage on a reference resource.

11. The method of claim 1, wherein the state of the device includes a physical random access channel leakage, the condition includes a leakage threshold, and the step of determining whether the state of the device satisfies the condition includes: Determine whether the leakage of the physical random access channel exceeds the leakage threshold; When the device's state meets the condition, the step of sending the physical random access channel to the network within the sub-band full-duplex time slot includes: When the leakage of the physical random access channel exceeds the leakage threshold and the physical random access channel preamble format of the physical random access channel has a small bandwidth, the physical random access channel is transmitted to the network within the subband full-duplex time slot.

12. The method of claim 1, wherein the state of the device includes a physical random access channel frequency resource location, the condition includes a center of an uplink subband of the subband full-duplex time slot, and the step of determining whether the state of the device satisfies the condition includes: Determine whether the physical random access channel frequency resource location is close to the center of the uplink subband of the full-duplex time slot of the subband; When the device's state meets the condition, the step of sending the physical random access channel to the network within the sub-band full-duplex time slot includes: When the physical random access channel frequency resource location is close to the center of the uplink subband of the subband full-duplex time slot, the physical random access channel is transmitted to the network within the subband full-duplex time slot.

13. The method of claim 1, wherein the state of the device includes a transmit power of the physical random access channel, the condition includes a power threshold determined based on a physical random access channel frequency resource allocation, and the step of determining whether the state of the device satisfies the condition includes: Determine whether the transmit power of the physical random access channel is lower than the power threshold determined based on the frequency resource allocation of the physical random access channel; When the device's state meets the condition, the step of sending the physical random access channel to the network within the sub-band full-duplex time slot includes: When the transmit power of the physical random access channel is lower than the power threshold determined based on the frequency resource allocation of the physical random access channel, the physical random access channel is transmitted to the network within the full-duplex time slot of the sub-band.

14. The method of claim 13, wherein the physical random access channel frequency resource allocation includes at least one of a center of an uplink subband of the subband full-duplex time slot and a number of resource blocks allocated for the physical random access channel.

15. The method of claim 14, further comprising: The processor determines the power threshold based on the center of the uplink subband in the full-duplex time slot of the subband, wherein: When the physical random access channel frequency resource location is close to the center of the uplink subband of the full-duplex time slot of the subband, the power threshold is determined to be a first value, or When the physical random access channel frequency resource location is not close to the center of the uplink subband of the subband full-duplex time slot, the power threshold is determined to be a second value, and the second value is lower than the first value.

16. The method of claim 15, wherein the power threshold is determined based on a lookup table comprising a plurality of power thresholds and a plurality of physical random access channel frequency resource locations.

17. The method of claim 14, further comprising: The power threshold is determined based on the number of resource blocks allocated to the physical random access channel, where: When the number of resource blocks allocated to the physical random access channel is equal to a first number, the power threshold is determined to be a first value, or When the number of resource blocks allocated to the physical random access channel is equal to or less than the first number, the power threshold is determined to be a second value, wherein the first value is less than the second value.

18. The method of claim 15, wherein the power threshold is determined based on a lookup table comprising a plurality of power thresholds and a plurality of resource blocks allocated for the physical random access channel.

19. The method of claim 14, further comprising: The power threshold is determined based on the center of the uplink subband in the full-duplex time slot of the subband and the number of resource blocks allocated to the physical random access channel, wherein: When a physical random access channel frequency resource location is close to the center of the uplink subband of the full-duplex time slot of that subband, and the number of resource blocks allocated to the physical random access channel is equal to a first number, the power threshold is determined to be a first value, or When the physical random access channel frequency resource location is not close to the center of the uplink subband of the subband full-duplex time slot and the number of resource blocks allocated to the physical random access channel is equal to or less than the first number, the power threshold is determined to be a second value, wherein the first value is lower than the second value.

20. The method of claim 19, wherein the power threshold is determined based on a lookup table comprising a plurality of power thresholds, a plurality of physical random access channel frequency resource locations, and a plurality of resource blocks allocated to the physical random access channel.

Images