Terminal device and method

Abstract

Embodiments of the present disclosure relate to apparatus, methods, and cocomputer-readable media for configuring physical random access channels (PRACH). According to embodiments of the present disclosure, the terminal device receives from a network device a PRACH configuration associated with a first set of PRACH opportunity (RO) for subband non-overlapping full-duplex (SBFD) time units and a second set of RO for non-SBFD time units. The SBFD time units consist of frequency subbands for different link directions. The terminal device then transmits the PRACH to the network device in at least one of the first set of RO and the second set of RO. In this way, the PRACH resources can be appropriately configured for SBFD and non-SBFD time units.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of communications, and more particularly, to an apparatus, a method, and a computer-readable medium for configuring a Physical Random Access Channel (PRACH).

Background Art

[0002] With the development of communication technologies, a time unit (e.g., a symbol, a slot, a frame, a sub-frame, etc.) can be divided into a plurality of frequency sub-bands in the frequency domain. The plurality of frequency sub-bands may be respectively used in different link directions, such as an uplink (UL) or a downlink (DL). This time unit may also be referred to as a SubBand non-overlapping Full Duplex (SBFD) time unit. Conversely, a communication device (e.g., a network device or a terminal device) can improve communication efficiency by simultaneously transmitting and receiving channels in different link directions using these time units.

[0003] Furthermore, random access procedures are designed for a terminal device to access a cell (e.g., a serving cell) or to transition from a non-active state or an idle state to a connected state. In the random access procedure, the terminal device transmits a PRACH to a network device on an assigned uplink resource. Therefore, the PRACH configuration can be further optimized with respect to the SBFD time unit.

Summary of the Invention

[0004] Generally, exemplary embodiments of the present disclosure relate to an apparatus, a method, and a computer-readable medium for configuring a PRACH.

[0005] In a first embodiment, a terminal device is provided. The terminal device comprises a transceiver and a processor communicatively connected to the transceiver. The processor is configured to cause the terminal device to receive PRACH configurations from a network device, associated with a first set of PRACH Occasions (ROs) for SBFD time units and a second set of ROs for non-SBFD time units. The SBFD time units consist of frequency subbands for different link directions. The terminal device is further configured to transmit PRACH to the network device in at least one of the first set of ROs and the second set of ROs.

[0006] In a second embodiment, a network device is provided. The network device comprises a transceiver and a processor communicatively connected to the transceiver. The processor is configured to cause the network device to transmit PRACH configurations associated with a first RO set for SBFD time units and a second RO set for non-SBFD time units to a terminal device. The SBFD time units consist of frequency subbands for different link directions. The network device is further configured to receive PRACH from the terminal device in order to transition to a connected state in at least one of the first RO set and the second RO set.

[0007] A third embodiment provides a method performed by a terminal device. In this method, the terminal device receives from a network device a PRACH configuration associated with a first RO set for SBFD time units and a second RO set for non-SBFD time units. The SBFD time units consist of frequency subbands for different link directions. The terminal device then transmits a PRACH to the network device in at least one of the first RO set and the second RO set.

[0008] A fourth aspect provides a method performed by a network device. In this method, the network device transmits a PRACH configuration to a terminal device associated with a first RO set for SBFD time units and a second RO set for non-SBFD time units. The SBFD time units consist of frequency subbands for different link directions. The network device then receives a PRACH from the terminal device in at least one of the first RO set and the second RO set to transition to a connected state.

[0009] In the fifth aspect, a computer-readable medium containing instructions is provided, and when the instructions are executed on at least one processor, the at least one processor is caused to perform the method according to the third or fourth aspect.

[0010] It should be understood that the summary portion of the invention is not intended to identify any significant or essential features of the exemplary embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the disclosure will be readily apparent through the following description. [Brief explanation of the drawing]

[0011] Here, several exemplary embodiments will be described with reference to the attached drawings.

[0012] [Figure 1] This document provides exemplary environments in which some embodiments of this disclosure can be implemented.

[0013] [Figure 2] This disclosure illustrates a signaling process for PRACH configuration according to several embodiments.

[0014] [Figure 3a] Examples of a first RO set for SBFD time units and a second RO set for non-SBFD time units are shown according to some embodiments of this disclosure. [Figure 3b] Examples of a first RO set for SBFD time units and a second RO set for non-SBFD time units are shown according to some embodiments of this disclosure. [Figure 3c] Examples of a first RO set for SBFD time units and a second RO set for non-SBFD time units are shown according to some embodiments of this disclosure.

[0015] [Figure 4a] Examples of determining valid or invalid RO according to some embodiments of this disclosure are shown. [Figure 4b] Examples of determining valid or invalid RO according to some embodiments of this disclosure are shown.

[0016] [Figure 5a] Examples of mapping relationships between RO and SSB (Synchronization Signal Block) according to several embodiments of this disclosure are shown. [Figure 5b] Examples of mapping relationships between RO and SSB (Synchronization Signal Block) according to several embodiments of this disclosure are shown. [Figure 5c] Examples of mapping relationships between RO and SSB (Synchronization Signal Block) according to several embodiments of this disclosure are shown. [Figure 5d] Examples of mapping relationships between RO and SSB (Synchronization Signal Block) according to several embodiments of this disclosure are shown.

[0017] [Figure 6] Examples of monitoring Random Access Responses (RARs) in SBFD time units according to some embodiments of this disclosure are shown.

[0018] [Figure 7]An example of transmitting a repetition of Message 3 (Msg 3: Message 3) for PRACH according to some embodiments of the present disclosure is shown.

[0019] [Figure 8] A flowchart of an exemplary method executed by a terminal device according to some embodiments of the present disclosure is shown.

[0020] [Figure 9] A flowchart of an exemplary method executed by a network device according to some embodiments of the present disclosure is shown.

[0021] [Figure 10] A simplified block diagram of a device suitable for implementing an exemplary embodiment of the present disclosure is shown.

[0022] Throughout the drawings, the same or similar reference numerals represent the same or similar elements.

Mode for Carrying Out the Invention

[0023] Here, the principles of the present disclosure will be described with reference to some embodiments. These embodiments are described for illustrative purposes only and are to be understood as being helpful for those skilled in the art to understand and implement the present disclosure without suggesting any limitation regarding the scope of the present disclosure. The disclosure described herein can be implemented in various ways other than those described below.

[0024] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0025] As used herein, the term “terminal device” refers to any device equipped with wireless or wired communication capabilities. Examples of terminal devices include user equipment (UE), personal computers, desktops, mobile phones, cellular phones, smartphones, personal digital assistants (PDA), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, ultra-reliable and low-latency communications (URLLC) devices, Internet of Everything (IoE) devices, machine-type communication (MTC) devices, vehicle-mounted devices for V2X communication (where X represents pedestrians, vehicles, or infrastructure / networks), integrated access and backhaul (IAB) devices, small data transmission (SDT), mobility, multicast and broadcast services (MBS), positioning, dynamic / flexible duplexing in commercial networks, reduced capability (RedCap), satellites, and unmanned aerial vehicle systems (UAS). Spaceflights or aerial vehicles within non-terrestrial networks (NTN), including high-altitude platforms (HAP), including systems; extended reality (XR) devices, including various types of reality such as augmented reality (AR), mixed reality (MR), and virtual reality (VR); unmanned aerial vehicles (UAVs), which are aircraft without human pilot intervention, commonly known as drones.Examples of "terminal devices" include, but are not limited to, equipment mounted on aerial vehicles, high-speed trains (HSTs), digital cameras, sensors, game consoles, music storage and playback devices, or internet devices that enable wireless or wired internet access and browsing. "Terminal devices" may also have "multicast / broadcast" capabilities and support public safety and mission-critical, V2X applications, transparent IPv4 / IPv6 multicast distribution, IPTV, smart TV, radio services, wireless software distribution, group communications, and IoT applications. They may also incorporate one or more subscriber identity modules (SIMs), known as multi-SIMs. The term "terminal device" may be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, wireless device, or low-function terminal device.

[0026] As used herein, the term “network device” refers to a device that can provide or host a cell or coverage from which terminal devices can communicate. Examples of network devices include, but are not limited to, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), next-generation Node B (gNB), transmission reception point (TRP), remote radio unit (RRU), radio head (RH), remote radio head (RRH), IAB node, low-power nodes such as femtonodes, piconodes, reconfigurable intelligent surface (RIS), and network control repeaters.

[0027] Terminal or network devices may incorporate artificial intelligence (AI) or machine learning capabilities. These typically include models trained on large amounts of collected data for specific functions and usable to predict certain information. Terminal or network devices can operate across multiple frequency ranges, including FR1 (410MHz–7125MHz), FR2 (24.25GHz–71GHz), 71GHz–114GHz, frequency bands above 100GHz, and terahertz (THz). Furthermore, they can operate in licensed / unlicensed / shared spectrum. In multi-radio dual connectivity (MR-DC) application scenarios, terminal devices may have multiple connections to network devices. Terminal or network devices can operate in full-duplex, flexible-duplex, and cross-split-duplex modes.

[0028] Network devices may include energy-saving network functions, self-organizing network (SON) / minimization of drive test (MDT) functions. Terminals may also include energy-saving functions.

[0029] Embodiments of this disclosure may be implemented using test equipment such as signal generators, signal analyzers, spectrum analyzers, network analyzers, test terminal devices, test network devices, and channel emulators.

[0030] Embodiments of the present disclosure may be implemented in accordance with any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include, but are not limited to, first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, 5.5G, 5G-Advanced Network, or sixth-generation (6G) networks.

[0031] In one embodiment, the terminal device may be connected to a first network device and a second network device. One of the first and second network devices may be a master node and the other a secondary node. The first and second network devices may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB, and the second RAT device is a gNB. Information about different RATs may be transmitted to the terminal device from at least one of the first and second network devices. In one embodiment, the first information may be transmitted from the first network device to the terminal device, and the second information may be transmitted directly from the second network device to the terminal device or via the first network device. In one embodiment, information about the settings of the terminal device set by the second network device may be transmitted from the second network device via the first network device. Information regarding the reconfiguration of a terminal device set by the second network device may be transmitted directly from the second network device to the terminal device, or transmitted via the first network device.

[0032] Where used herein, the singular forms “a / an” and “the” are intended to include the plural unless explicitly indicated otherwise in the context. The term “including” and its variations are interpreted as an open term meaning “including, but not limited to.” The term “based on” is interpreted as “at least partially based on.” The terms “one embodiment” and “a certain embodiment” are interpreted as “at least one embodiment.” The term “another embodiment” is interpreted as “at least one other embodiment.” Terms such as “first,” “second,” etc., may refer to different or the same subject. The following may include other explicit and implicit definitions.

[0033] In some examples, values, procedures, or devices are referred to as “best,” “worst,” “highest,” “minimum,” “maximum,” etc. Such descriptions are intended to show that a choice can be made from among many functional options being used, and it will be understood that such a choice does not need to be better, smaller, higher, or more preferable than the other options.

[0034] As used herein, the term “circuit” may refer to a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be a combination of analog and / or digital hardware circuits and software / firmware. As a further example, a circuit may be any part of a software-equipped hardware processor, such as a digital signal processor, software, and memory, which work together to enable a device such as a terminal or network device to perform various functions. In yet another example, a circuit may be a hardware circuit and / or processor, such as a microprocessor or a part of a microprocessor, which requires software / firmware for operation but may not have software when not required for operation. As used herein, the term “circuit” also encompasses implementations of hardware circuits or processors only, or implementations of hardware circuits or parts of processors, as well as implementations of software and / or firmware associated therewith. In this disclosure, subbands and frequency subbands may be used interchangeably without any restriction. The group size of an RGB may be called the RGB size without any restriction. In this disclosure, a control channel may be used interchangeably with a physical downlink control channel (PDCCH) without any restriction.

[0035] A time unit configured by SBFD communication or configuration may also be called an SBFD time unit, and a time unit not configured by SBFD communication may also be called a non-SBFD time unit.

[0036] In this disclosure, the unit of time may be any duration, such as a symbol, slot, subframe, or frame.

[0037] The term “Random Access Channel (RACH)” as used in this disclosure may be used interchangeably with “PRACH” or “Initial Access Process” without any limitation.

[0038] The term "Frequency Division Multiplexing (FDM)" used in this text may also refer to the number of frequency-multiplexed ROs within the same time unit.

[0039] The term "Physical Resource Block (PRB)" or "resource block" may also refer to a basic unit of resources in the frequency domain.

[0040] As used in this disclosure, the term “SBFD-aware UE” may refer to a terminal device that acquires an SBFD configuration for a time unit, such as a subband division or location for a time unit, and supports SBFD operation with a network device.

[0041] The term “SSB-per RO value” refers to the mapping relationship between a synchronous signal block (SSB) and a configured PRACH opportunity (RO). When the SSB-per RO value is greater than 1, multiple SSBs are mapped to one RO. When the SSB-per RO value is less than 1, one SSB is mapped to multiple ROs, or multiple ROs are mapped to one SSB. When the SSB-per RO value is 1, each SSB is mapped to one RO. Without any limitation, embodiments of this disclosure may be applied to at least “4-step RACH” and / or “2-step RACH”.

[0042] As mentioned above, the PRACH configuration can be optimized with respect to SBFD time units. When SBFD operation is introduced, more uplink resources may be allocated to SBFD time units, such as DL time units with SBFD configuration (e.g., DL symbols or DL ​​slots) or special (S) time units with SBFD configuration. In this case, the initial access procedure may improve PRACH by using SBFD time units or operation, as the SBFD time unit can provide more UL resources to increase PRACH capacity. This can reduce PRACH collisions and initial access latency.

[0043] One direct solution is that the RO for transmitting PRACH can be set the same for both SBFD and non-SBFD time units. However, since SBFD time units may have subbands (also called "DL subbands") and guard bands in the DL direction, some allocated ROs that overlap with DL subbands or guard bands cannot be used to transmit PRACH in the UL direction. Therefore, identical ROs between SBFD and non-SBFD time units may be inappropriate. Next, we need to consider how to set ROs within SBFD and non-SBFD time units and how to determine the effectiveness of ROs.

[0044] Furthermore, synchronous signal blocks (SSBs) can be mapped to ROs according to pre-configured rules. Additionally, SSBs may also be associated with specific beams. The terminal device may then transmit a PRACH in the RO to which a specific SSB is mapped to the network device, thereby indicating to the network device the beam associated with the SSB. Once ROs are assigned to both SBFD and non-SBFD time units, the mapping relationships between SSBs and ROs may be further designed.

[0045] Furthermore, the power ramping operation for retransmitting PRACH may be adjusted to take into account the characteristics of SBFD operation. Also, in SBFD operation, other enhancements to the RACH procedure (such as monitoring for transmission of random access responses, RARs, and repeated transmissions of message 3 PUSCH) are important aspects.

[0046] To solve at least the technical problems described above, exemplary embodiments of the present disclosure propose a mechanism for PRACH configurations. In this mechanism, a terminal device receives a PRACH configuration from a network device. The PRACH configuration is associated with a first set of ROs for at least one SBFD time unit and a second set of ROs for at least one non-SBFD time unit. The terminal device then transmits the PRACH to the network device in at least one of the first set of ROs and the second set of ROs.

[0047] In this way, RO can be appropriately configured over both SBFD and non-SBFD time units. This reduces PRACH collisions and initial access latency.

[0048] For illustrative purposes, the principles and exemplary embodiments of this disclosure are described below with reference to Figures 2–10. However, it should be noted that these embodiments are provided to enable those skilled in the art to understand the inventive concepts of this disclosure and to implement the solutions proposed herein, and are not intended to limit the scope of this application in any way.

[0049] Figure 1 shows an exemplary environment 100 in which exemplary embodiments of the present disclosure can be carried out.

[0050] Environment 100 may be part of a communication network and comprises terminal device 110 and network device 120. In some embodiments, the communication network may include NTN, NB-IoT, and / or eMTC. In some other embodiments, the communication network may include any other possible communication network. It should be understood that the number of network devices and terminal devices is for illustrative purposes only and does not imply any limitation. The communication network may include any appropriate number of network devices and / or terminal devices adapted to carry out embodiments of the present disclosure. It will be understood that, although not shown, environment 100 may have one or more terminal devices. Without any limitation, network device 120 supports SBFD communication. For example, network device 120 may transmit a DL channel to terminal device 110 and simultaneously receive a UL channel from another terminal device (not shown in Figure 1A) in an SBFD time unit. In this disclosure, a non-SBFD time unit may be a UL-only time unit or a DL-only time unit.

[0051] Figure 2 shows a signaling process 200 for a PRACH configuration according to several embodiments of the present disclosure. For illustrative purposes, the process 200 will be described with reference to Figure 1.

[0052] In signaling 200, the network device 120 transmits (210) a PRACH configuration 215 associated with a first RO set for SBFD time units and a second RO set for non-SBFD time units to the terminal device 110. Thus, the terminal device 110 may receive (220) the PRACH configuration 215 and determine the first RO set and the second RO set based on the PRACH configuration. The first RO set may include one or more ROs distributed in SBFD time units. The ROs in the first RO set may also be called SBFD ROs. The second RO set may include one or more non-SBFD ROs distributed in non-SBFD time units. The ROs in the second RO set may also be called non-SBFD ROs.

[0053] In some embodiments, the PRACH configuration 215 may represent a common set of resource blocks and at least one additional parameter. The second RO set for non-SBFD time units may be determined based solely on the common set of resource blocks. For example, the second RO set may be equal to the common set of resource blocks in the frequency domain. Without any limitation, the second RO set may also be part of the common set of resource blocks in the frequency domain, and this part may be determined based on predefined rules.

[0054] The first RO set may be determined based on a common set of resource blocks and at least one additional parameter. For example, the additional parameter may be a frequency offset value. The terminal device 110 may then determine the first RO set by shifting the common set of resource blocks by the frequency offset value. Without any limitation, the at least one additional parameter may be any other parameter, such as a scaling factor, a modulo factor, a drop factor, or an FDM factor of the RO. To clarify the discussion, a PRACH configuration showing the common set of resource blocks and at least one additional parameter will be discussed further with reference to Figure 3a.

[0055] Figure 3a shows examples of a first RO set for SBFD time units and a second RO set for non-SBFD time units according to some embodiments of the present disclosure. For illustrative purposes, the embodiments shown in Figure 3a will be described with reference to Figure 1.

[0056] As shown in Figure 3a, a common PRACH indicating a common set of resource blocks is configured for the SBFD and non-SBFD time units of the cell. In this example, as shown in Figure 3a, the common set of resource blocks may be RO325 in the non-SBFD time unit 320. Furthermore, an additional configuration is configured for RO or PRACH transmission determination within the SBFD symbol. The additional configuration may include the minimum RO starting PRB and the FDM RO number of the time instance, for example, the FDM RO number may be 1. In the additional configuration, the terminal device 110 may determine RO315 in the SBFD time unit 310 based on the common set of resource blocks.

[0057] For example, first, network device 120 may broadcast a RACH configuration including SBFD (e.g., UL / DL subband configuration) and RO325 via, for example, System Information Block (SIB) 1. Next, an SBFD-aware UE (such as terminal device 110) will know the time and frequency position of the UL / DL subband and RO within the initial UL / DL BWP. Then, terminal device 110 can transmit PRACH as needed. In the case of SBFD time units, a new set of parameters for terminal device 110 can be added to determine RO, SBFD time units, and transmit PRACH, after which terminal device 110 can determine different frequency positions and power (if necessary) within the SBFD symbol.

[0058] In Figure 3a, the number of minimum RO starting physical resource blocks (PRBs) and FDM ROs are not the same for SBFD and non-SBFD time units. For SBFD time units, the FDM RO number is 1. For non-SBFD time units, the FDM RO number is 2.

[0059] The above embodiment may also be expressed as follows: TIFF2026509583000002.tif40168

[0060] Thus, RO for SBFD time units and RO for non-SBFD time units can be flexibly configured by a common set of additional parameters and resource blocks.

[0061] Referring back to Figure 2, alternatively, the PRACH configuration may only indicate a set of resource blocks without additional parameters. In this case, the SBFD-aware UE (e.g., terminal device 110) may autonomously determine the first RO set for an SBFD time unit, for example, based on predefined rules. In some embodiments, the PRACH configuration may indicate a set of resource blocks for a start resource block. For an SBFD time unit, terminal device 110 may use the start resource block of the uplink subband within the SBFD time unit (also called the first start resource block) as the start resource block for determining the first RO set. Then, terminal device 110 may determine the set of resource blocks for the first start resource block as the first RO set. For example, terminal device 110 may determine the minimum RO of the first RO set based on the use of the first start resource block.

[0062] In the case of non-SBFD time units, terminal device 110 may use the starting resource block of the Bandwidth Part (BWP), also called the second starting resource block, as the starting resource block for determining the second RO set. The terminal device may then determine the set of resource blocks for the second starting resource block as the second RO set. For example, terminal device 110 may determine the minimum RO of the second RO set based on the use of the second starting resource block. To clarify the discussion, a PRACH configuration showing the set of resource blocks for the starting resource block will be discussed further with reference to Figure 3b.

[0063] Figure 3b shows another example of a first RO set for SBFD time units and a second RO set for non-SBFD time units according to some embodiments of the present disclosure. For illustrative purposes, the embodiments shown in Figure 3b will be described with reference to Figure 1.

[0064] As shown in Figure 3b, for the SBFD time unit, the definition of msg1-FrequencyStart is changed to the start of the UL subband. This may allow the RO to be avoided in the DL subband or guard band for the SBFD time unit.

[0065] The above embodiment may also be expressed as follows: TIFF2026509583000003.tif34168

[0066] Referring back to Figure 2, to avoid overlap between the first RO set in the SBFD time unit and the DL subband or guard band, a common set of resource blocks or a set of resource blocks shown in the PRACH configuration may be determined based on the bandwidth of the UL subband in the SBFD time unit. For example, the SCS settings for msg1-FDM-SBFD, msg1-FrequencyStart-SBFD, and PRACH may be determined according to the UL subband bandwidth. The UE may assume that the configured RO is within the UL subband BW. Example: (msg1-FrequencyStart-SBFD + 6 * SCS value * msg1-FDM-SBFD) <= UL subband BW.

[0067] Furthermore, or alternatively, the first RO set and the second RO set may be determined separately. In some embodiments, the terminal device 110 may receive the PRACH configuration 215 (220) by receiving an SBFD PRACH configuration indicating the first RO set and a non-SBFD PRACH configuration indicating the second RO set. Furthermore, the SBFD PRACH configuration may be configured independently of the non-SBFD PRACH configuration. To clarify the discussion, separately configured SBFD PRACH configurations and non-SBFD PRACH configurations will be discussed further with reference to Figure 3c.

[0068] Figure 3c shows further examples of a first RO set for SBFD time units and a second RO set for non-SBFD time units according to some embodiments of the present disclosure. For illustrative purposes, the embodiments shown in Figure 3c will be described with reference to Figure 1.

[0069] Separate PRACH configurations may be configured for SBFD symbols and non-SBFD symbols. As shown in Figure 3c, an SBFD PRACH configuration including RO330 is configured for SBFD time units. A non-SBFD PRACH configuration including RO340 is configured for non-SBFD time units. For example, a new PRACH configuration can be configured for a cell by the RACH-ConfigGenericSBFD IE of the SIB for the UE, thereby allowing the UE to send PRACHs over SBFD symbols.

[0070] The above embodiment may also be expressed as follows: TIFF2026509583000004.tif215168

[0071] Referring back to Figure 2, the terminal device 110 may also determine whether the RO of the first RO set is enabled or disabled (221).

[0072] In some embodiments, if the first RO set overlaps with or is within the range of SBFD time units or uplink (UL) time units in the time domain, the terminal device 110 may determine that the RO of the first RO set is valid. Conversely, if the first RO set overlaps with DL time units without an SBFD configuration (i.e., DL-only time units), the terminal device 110 may determine that the RO of the first RO set is invalid. For clarification of the discussion, further discussion of how to determine whether an RO is valid or invalid will be discussed with reference to Figure 4a.

[0073] Figure 4a shows examples of determining valid or invalid RO according to some embodiments of the present disclosure.

[0074] As shown in Figure 4a, an SBFD-aware UE may consider ROs that collide with DL symbols configured in the UL subband for SBFD operation to be valid. If the UE receives SIB1 signaling for subband UL locations in the frequency and time domain on a DL symbol or flexible symbol, the ROs assigned to these DL or flexible symbols are valid; otherwise (for example, if the DL or flexible symbol is not configured in the UL subband), the UE may consider the ROs invalid.

[0075] Referring back to Figure 2, further or alternatively, the terminal device 110 may determine whether the ROs of the first RO set are valid in combination with SBFD splitting in SBFD time units. In some embodiments, if the first RO set is in the uplink subband in the SBFD time unit in the frequency domain, the terminal device 110 may determine the ROs of the first RO set to be valid. If at least one RO of the first RO set overlaps at least partially with the guard subband or downlink subband in the SBFD time unit in the frequency domain, the terminal device 110 may determine at least one RO to be invalid. The terminal device 110 may then transmit a PRACH to the network device 120 on at least one RO of the first RO set that has been determined to be valid. For clarity of the discussion, further details on determining whether an RO is valid or invalid will be discussed with reference to Figure 4b.

[0076] Figure 4b shows another example of determining valid or invalid RO according to some embodiments of the present disclosure.

[0077] As shown in Figure 4b, the common PRACH configuration may be configured for SBFD symbols and non-SBFD symbols. If the RO indicated by the common PRACH configuration overlaps with the DL subband / guard band in SBFD time units, the terminal device 110 may consider the RO invalid. In that case, the terminal device 110 will not transmit PRACH on the RO that overlaps with the DL subband / guard band.

[0078] Alternatively, if the PRACH frequency position of an RO exceeds the UL subband bandwidth edge of the SBFD symbol, the terminal device 110 may also consider these ROs invalid. Furthermore, several predefined requirements, such as the symbol number spacing with the SSB symbol, may also apply to these valid ROs. For example, in Figure 4b, the configured RO is invalid because it overlaps with the guard band.

[0079] Referring back to Figure 2, as described above, the mapping relationships between SSBs and ROs may be further designed. In some embodiments, the terminal device may obtain or determine (223) the mapping relationships between SSBs and ROs in the first and second RO sets from the network device 120. Without any limitation, the mapping relationships may also be predefined.

[0080] In some embodiments, one or more SBFD time unit indices in a first RO set and one or more non-SBFD time unit indices in a second RO set may be uniformly numbered. In this case, multiple SSBs may be mapped to uniformly numbered indices of one or more SBFD ROs and one or more non-SBFD ROs by the same SSB-per RO value. To clarify the discussion, the mapping relationship between uniformly numbered ROs and SSBs will be discussed further with reference to Figure 5a.

[0081] Figure 5a shows examples of mapping relationships between RO and SSB according to some embodiments of the present disclosure.

[0082] As shown in Figure 5a, RO#1 205 and RO#2 507 within SBFD time units, and RO#3 508 and RO#4 509 within non-SBFD time units are numbered uniformly. Furthermore, SSB#1 501 and SSB#2 503 are mapped to ROs within SBFD and non-SBFD time units by the same SSB-per RO value. While time units are shown as slots in Figure 5a, it should be understood that time units may be any other time duration. This may also apply to other figures in this disclosure.

[0083] The setting for the SSB-per RO value "N" may be selected from {oneSixteenth, oneEighth, oneFourth, oneHalf, one, two, four}. The SS / PBCH block index provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon is mapped to valid ROs for SBFD and non-SBFD symbols in the following order: Firstly, the ascending order of preamble indices within a single PRACH opportunity. Secondly, the frequency resource index is ordered in ascending order for frequency multiplexing PRACH opportunities. Thirdly, ascending order of time resource index for time-multiplexed PRACH opportunities within PRACH slots in SBFD slots. Fourth, ascending order of index for non-SBFD slots.

[0084] For example, in Figure 5a, we assume that msg1-FDM=2, i.e., one PRACH time contains two ROs in the frequency domain, and that SSB-per RO value N=2, i.e., one SSB index is associated with two PRACH opportunities. In this case, in the mapping order described above, SSB#1 maps to RO#1 505 and RO#2 507. SSB#2 507 maps to RO#3 508 and RO#4 509.

[0085] Thus, since all ROs are numbered uniformly, there is no need to distinguish between SBFD ROs and non-SBFD ROs in the mapping relationship between SSBs and ROs.

[0086] Referring back to Figure 2, SSBs may be further, or alternatively, grouped into a first group of SSBs for SBFD time units and a second group of SSBs for non-SBFD time units. Then, SSBs in the first group of SSBs are mapped to one or more SBFD ROs in the first RO set. SSBs in the second group of SSBs are mapped to one or more non-SBFD ROs in the second RO set. Furthermore, SSBs in the first group of SSBs do not have to be mapped to non-SBFD time units, and vice versa. Thus, SSBs may be divided into two groups, each dedicated to either SBFD time units or non-SBFD units. To clarify the discussion, the first and second groups of SSBs will be discussed further with reference to Figure 5b.

[0087] Figure 5b shows another example of a mapping relationship between RO and SSB according to some embodiments of the present disclosure.

[0088] As shown in Figure 5b, SSB#1 to #8 are divided into a first group (511) consisting of SSB#1 to #4 and a second group (513) consisting of SSB#5 to #8.

[0089] Assume that the same SSB-per RO value N>1, i.e., multiple SSBs are associated with one RO. The SSB indices in the first group (511) are mapped to ROs (RO#1 515 and RO#2 517) in SBFD time units, and the SSB indices in the second group (513) are mapped to ROs (RO#3 518 and RO#4 519) in non-SBFD symbols. ROs in SBFD and non-SBFD time units are numbered together, but it should be understood that these ROs may also be numbered separately without any restriction. Furthermore, the SSB-per RO value for the first group of SSBs and ROs in SBFD time units may be different from the SSB-per RO value for the second group of SSBs and ROs in non-SBFD time units. Furthermore, the number of SSBs in these two groups of SSBs may be the same or different.

[0090] As shown in Figure 5b, assuming that four SSBs are associated with ROs in SBFD time units and another four SSBs are associated with ROs in non-SBFD time units, the set SSB number is 8. Assume an SSB-per RO value N = 1 / 2, i.e., two SSB indices are associated with one RO. In this case, SSB#1 to SSB#4 are associated with two ROs within SBFD time units, and SSB#5 to SSB#8 are associated with two ROs within non-SBFD time units.

[0091] Referring back to Figure 2, further or alternatively, in some embodiments, the SSB may be mapped to both SBFD ROs and non-SBFD ROs. Then, the mapping relationship between the SSB and ROs may differ between SBFD ROs and non-SBFD ROs.

[0092] For example, the index of one or more SBFD ROs is numbered independently of the index of one or more non-SBFD ROs. Multiple SSBs are mapped to the index of one or more SBFD ROs by a first SSB-per RO value. Furthermore, multiple SSBs are mapped to the index of one or more SBFD ROs by a second SSB-per RO value. The first and second SSB-per RO values ​​may be the same or different without any restriction. To clarify the discussion, the above mapping relationships will be discussed further with reference to Figure 5c.

[0093] Figure 5c shows further examples of mapping relationships between RO and SSB according to some embodiments of the present disclosure.

[0094] RO indices are numbered separately for SBFD and non-SBFD time units. Furthermore, mapping relationships are determined separately for SBFD and non-SBFD time units. The SSB-per RO value for SSBs mapped to RO, and the number R of contention-based preambles per SSB (e.g., SS / PBCH block) index per valid PRACH opportunity, can be set separately in ssb-perRACH-OccasionAndCB-PreamblesPerSSB and SBFD-ssb-perRACH-OccasionAndCB-PreamblesPerSSB. As mentioned above, a single SSB index may be associated with RO in both SBFD and non-SBFD symbols. Furthermore, SBFD-ssb-perRACH-OccasionAndCB-PreamblesPerSSB may be a newly defined parameter for SBFD-recognized UEs.

[0095] As shown in Figure 5c, for non-SBFD symbols, we assume a second SSB-per-RO value N=1, meaning each SSB maps to one RO in the non-SBFD symbol. For SBFD time units, we assume a first SSB-per-RO value N-SBFD=2, meaning each SSB maps to two ROs in the SBFD time unit, or one SSB maps to two ROs in the SBFD time unit. For example, SSB#1 can be associated with RO#1 and RO#2 in the SBFD unit, and also with RO#1 in the non-SBFD time unit.

[0096] In this way, the number of ROs can be increased. Therefore, terminal device 110 may have more opportunities to send PRACH associated with the same SSB in SBFD time units or non-SBFD time units. This can reduce the latency of the PRACH procedure.

[0097] Referring back to Figure 2, further or alternatively, in some embodiments, the first RO set and the second RO set may have the same frequency resources in the frequency domain, and the index of one or more SBFD ROs is numbered independently of the index of one or more non-SBFD ROs. In this case, multiple SSBs are mapped to the index of one or more SBFD ROs by the SSB-per RO value. Furthermore, multiple SSBs are also mapped to the index of one or more non-SBFD ROs by this same SSB-per RO value. In other words, this embodiment may be a simplified example of the embodiment shown in Figure 5c. In this simplified example, the first RO set and the second RO set are set identically in the frequency domain, and the mapping relationship for SSBs is the same between SBFD ROs and non-SBFD ROs. To clarify the discussion, this simplified example will be discussed further with reference to Figure 5d.

[0098] Figure 5d shows yet another example of a mapping relationship between RO and SSB according to some embodiments of the present disclosure.

[0099] As shown in Figure 5d, ROs within SBFD and non-SBFD time units have the same PRACH configuration, and the mapping between SSBs and SBFD ROs is performed independently of the mapping between SSBs and non-SBFD ROs. Furthermore, the mapping relationships are the same. For example, the SSB-per RO value N for an SSB index associated with an RO, and the number R of contention-based preambles per SS / PBCH block index per valid PRACH opportunity, are the same for SBFD and non-SBFD symbols. The SSB-per RO value N and the number R may also be set by the existing parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB, the setting value can be selected from {oneSixteenth, oneEighth, oneFourth, oneHalf, one, two, four}.

[0100] In Figure 5d, the SSB-per RO value N=1 is set for both non-SBFD and SBFD symbols. That is, each SSB is mapped to one RO for SBFD symbols and one RO for non-SBFD symbols. For example, SSB#1 can be associated with RO#1 in SBFD time units and can also be associated with RO#1 in non-SBFD time units.

[0101] Referring back to Figure 2, terminal device 110 transmits PRACH 235 (230) on at least one of the first RO set and the second RO set. Therefore, network device 120 receives PRACH 235 (240).

[0102] In some embodiments, when certain conditions are met, the terminal device 110 may retransmit (241) PRACH 243 to the network device 120. In some embodiments, the terminal device 110 may retransmit PRACH by power ramping. For example, there may be a power ramping counter for counting the number of PRACH retransmissions. When PRACH is retransmitted, the power ramping counter may be incremented by 1. The terminal device 110 may then retransmit PRACH using updated transmit power equal to the previous transmit power plus one power ramping step.

[0103] When employing existing power ramping steps or power ramping counters, PRACH transmitted in SBFD time units may cause cross-link interference (CLI) in adjacent subbands of the uplink subband. Therefore, power ramping for PRACH / preamble retransmission should be considered with respect to inter / intra subband CLI. In some cases, power ramping should be controlled for PRACH transmission over SBFD symbols for SBFD-recognized UEs.

[0104] In some embodiments, the terminal device 110 may retransmit PRACH on a first RO set using a first power ramping step. Furthermore, the terminal device 110 may retransmit PRACH on a second RO set using a second power ramping step. The first power ramping step may be configured independently of the second ramping step. In some embodiments, the first power ramping step is smaller than the second power ramping step. In this way, the speed of power ramping for retransmitting PRACH can be reduced, and the CLI can be reduced accordingly. As an example, the first power ramping step may be 0 dB, that is, the power ramping operation is disabled in SBFD time units.

[0105] For example, powerRampingStep is set individually, and different power ramping counters are used for PRACH transmissions on SBFD and non-SBFD time units. Furthermore, powerRampingStep may always be equal to dB0 for PRACH retransmissions on SBFD symbols; that is, the UE does not perform power ramping for PRACH retransmissions on SBFD symbols.

[0106] Furthermore, or alternatively, in some embodiments, when transmitting a PRACH on the first RO set, the terminal device 110 may reset the power ramping counter based on the fact that the beam associated with the PRACH has not changed. When transmitting a PRACH on the first RO set, the terminal device 110 may maintain the power ramping counter based on the fact that the beam associated with the PRACH has changed.

[0107] For example, the powerRampingStep is the same, and the same power ramping counter is used for PRACH transmissions on SBFD and non-SBFD symbols. Each beam has its own separate power ramping counter. If the beam has not changed in an SBFD time unit, the power ramping counter for PRACH / preamble retransmission is reset; if the beam has changed, the counter is retained for PRACH retransmission in an SBFD time unit.

[0108] Furthermore, or alternatively, in some embodiments, the terminal device 110 may retransmit PRACH on a first RO set using a first power ramping counter for PRACH retransmission. The terminal device 110 may retransmit PRACH on a second RO set using a second power ramping counter for PRACH retransmission. The first power ramping counter is configured independently of the second power ramping counter. Furthermore, in some embodiments, if the number of PRACH retransmissions on the first RO set exceeds or equals a starting threshold, the terminal device 110 may start the power ramping counter for PRACH retransmission.

[0109] For example, if the PRACH retransmission is on an SBFD time unit, the power ramping counter is not changed for the first two PRACH transmissions after the beam change. Then, the power ramping counter is counted from the third PRACH retransmission on the SBFD symbol. In another example, if the beam has not changed for an SBFD time unit, the power ramping counter for PRACH retransmission on the SBFD symbol is reset. Alternatively, if the retransmission count reaches two or three, the terminal device 110 may perform power ramping for PRACH retransmission. Otherwise, the terminal device 110 may retain power for PRACH retransmission on an SBFD time unit.

[0110] Referring back to Figure 2, terminal device 110 may monitor (246) for random access responses (RARs) in subsequent SBFD time units after transmitting PRACH 235. For example, terminal device 110 may monitor RARs within the DL subband of an SBFD time unit. If terminal device 110 monitors RARs within an SBFD time unit and the SBFD time unit is also configured with ROs to transmit PRACHs, terminal device 110 may omit or drop ROs in this SBFD time unit. To clarify the discussion, monitoring RARs in SBFD time units will be discussed further with reference to Figure 6.

[0111] Figure 6 shows examples of monitoring of random access responses (RARs) in SBFD time units according to some embodiments of the present disclosure.

[0112] As shown in Figure 6, terminal device 110 (e.g., UE) can monitor RAR in the DL subband of the SBFD symbol, and if RO is also set to this symbol, the UE will drop RO and not transmit PRACH.

[0113] The above embodiment may also be expressed as follows: TIFF2026509583000005.tif62168

[0114] Referring back to Figure 2, in SBFD operation, the frequency hopping pattern of message 3 (Msg 3) for the RACH procedure may also be adjusted.

[0115] In-slot frequency hopping for Msg 3 PUSCH, enabled or disabled for an SBFD slot, can be set individually by the RRC or indicated by the RAR UL grant. The value of the hopping bit in the RAR / RRC to indicate the frequency offset used for the second hop for the SBFD symbol can be set / displayed individually. Furthermore, one new parameter for the second hop on the SBFD slot can be defined for the terminal device 110. If this parameter is set, in-slot frequency hopping for msg3 PUSCH is enabled and the frequency offset size for the second hop on the SBFD slot is displayed.

[0116] In some embodiments, the network device 120 may transmit (247) a frequency hopping instruction 249 for Msg 3 to the terminal device 110. Thus, the terminal device 110 may receive (251) the frequency hopping instruction 249.

[0117] In some embodiments, the frequency hopping instruction may indicate the enablement or disablement of frequency hopping for Msg 3 in SBFD time units. Furthermore, the frequency hopping instruction may indicate a frequency offset between the first and second frequency hops of Msg 3. The frequency offset is constructed based on the bandwidth of the UL subband in SBFD time units. Thus, the frequency hopping pattern may be maintained within the UL subband in SBFD time units.

[0118] For example, to avoid overlapping frequency-hopping resources with the DL subband in SBFD time units, the frequency offset for the second hopping or Msg3 Push retransmission in the RAR UL grant can be based on the UL subband size instead of the BWP size. The above embodiment may also be expressed as follows: TIFF2026509583000006.tif31168TIFF2026509583000007.tif123168

[0119] Referring back to Figure 2, the terminal device 110 may transmit Msg 3 repetitions across SBFD and non-SBFD time units. In some embodiments, if multiple Msg 3 repetitions are configured within the UL subband of an SBFD time unit, the terminal device 110 may transmit multiple Msg 3 repetitions across SBFD and non-SBFD time units. To clarify the discussion, Msg 3 repetitions on an SBFD time unit will be discussed further with reference to Figure 7.

[0120] Figure 7 shows examples of sending message 3 repetitions to a RACH procedure according to some embodiments of the present disclosure.

[0121] As described above, in the case of repeated transmission of Msg 3 PUSCH, the terminal device 110 may transmit repeated Msg3 PUSCH transmissions across SBFD time units and non-SBFD units. With respect to the SBFD time unit for repeated transmission of Msg 3 PUSCH, if the allocated FDRA in the RAR is within the UL subband BW, the configured UL subband on the SBFD time unit may be determined as an available resource; otherwise, the UE delays repeated transmission of msg3 PUSCH. The above embodiment may also be expressed as follows: TIFF2026509583000008.tif62168

[0122] Thus, this disclosure provides a method for configuring ROs in SBFD symbols. The validity of RO determination is taken into consideration. The relationship between SSB and RO is also defined for valid ROs in SBFD symbols. This disclosure further includes the following aspects: RO assignment / setting in the UL subband of SBFD symbols, valid RO determination on SBFD symbols, RO mapping relationship with SSB for ROs in SBFD symbols, power control for PRACH, Msg2 / RAR enhancement, Msg3 PUSCH frequency hopping on SBFD symbols, and repeated Msg3 PUSCH transmission across SBFD and non-SBFD symbols.

[0123] Figure 8 shows a flowchart of a communication method 800 performed in a terminal device according to several embodiments of the present disclosure. Method 800 may be performed in the terminal device 110 shown in Figure 1. For clarity, method 800 will be described with reference to Figure 1. Method 800 may include additional actions not shown, and / or some of the actions shown may be omitted, and it should be understood that the scope of the present disclosure is not limited in this respect.

[0124] In 810, the terminal device 110 receives a PRACH configuration from the network device, associated with a first RO set for SBFD time units and a second RO set for non-SBFD time units. The SBFD time units consist of frequency subbands for different link directions. In 820, the terminal device transmits a PRACH to the network device in at least one of the first RO set and the second RO set.

[0125] In some embodiments, the PRACH configuration represents a common set of resource blocks and at least one additional parameter. The terminal device may further determine at least one of the first RO set and the second RO set by determining a first RO set based on the common set of resource blocks and at least one additional parameter, and determining a second RO set based on the common set of resource blocks.

[0126] In some embodiments, the PRACH configuration represents a set of resource blocks relative to a starting resource block. The terminal device may further determine at least one of the first RO set and the second RO set by at least one of the following: using a first starting resource block of the uplink subband within an SBFD time unit as the starting resource block to determine the minimum RO of a first RO set based on the set of resource blocks, or using a second starting resource block of the bandwidth portion as the starting resource block to determine the minimum RO of a second RO set based on the set of resource blocks.

[0127] In some embodiments, a common set of resource blocks or at least one of a set of resource blocks is determined based at least on the bandwidth of the uplink subband within an SBFD time unit.

[0128] In some embodiments, the terminal device 110 may receive a PRACH configuration by receiving an SBFD PRACH configuration indicating a first RO set and a non-SBFD PRACH configuration indicating a second RO set, wherein the SBFD PRACH configuration is configured independently of the non-SBFD PRACH configuration.

[0129] In some embodiments, the terminal device 110 may further perform at least one of the following: determining that the RO of the first RO set is valid based on the fact that the first RO set overlaps with SBFD time units or uplink (UL) time units in the time domain; and determining that the RO of the first RO set is invalid based on the fact that the first RO set overlaps with DL time units without an SBFD configuration in the time domain.

[0130] In some embodiments, the terminal device 110 further performs at least one of the following: determining that the ROs of the first RO set are valid based on the fact that the first RO set is located in the uplink subband in the frequency domain on an SBFD time unit; and determining that at least one RO of the first RO set is invalid based on the fact that at least one RO overlaps at least partially with a guard subband or downlink subband in the frequency domain on an SBFD time unit.

[0131] In some embodiments, the terminal device 110 may send a PRACH to the network device on at least one RO determined to be valid in the first RO set.

[0132] In some embodiments, a first RO set includes one or more SBFD ROs for a terminal device to transmit PRACHs on SBFD time units, and a second RO set includes one or more non-SBFD ROs for a terminal device to transmit PRACHs on non-SBFD time units.

[0133] In some embodiments, at least one of the following is satisfied: one or more SBFD ROs and one or more non-SBFD ROs are uniformly numbered; and multiple synchronization signal blocks (SSBs) are mapped to the same SSB-per RO value to one or more SBFD ROs and one or more non-SBFD ROs with uniformly numbered indices.

[0134] In some embodiments, at least one of the following is satisfied: a plurality of SSBs are grouped into a first group of SSBs for SBFD time units and a second group of SSBs for non-SBFD time units; SSBs in the first group of SSBs are mapped to one or more SBFD ROs; and SSBs in the second group of SSBs are mapped to one or more non-SBFD ROs.

[0135] In some embodiments, at least one of the following is satisfied: one or more SBFD RO indices are numbered independently of one or more non-SBFD RO indices; multiple SSBs are mapped to one or more SBFD RO indices by a first SSB-per RO value; and multiple SSBs are mapped to one or more SBFD RO indices by a second SSB-per RO value.

[0136] In some embodiments, at least one of the following is satisfied: the first RO set and the second RO set have the same resource block location in the frequency domain; the index of one or more SBFD ROs is numbered independently of the index of one or more non-SBFD ROs; multiple SSBs are mapped to the index of one or more SBFD ROs by SSB-per RO values; and multiple SSBs are mapped to the index of one or more non-SBFD ROs by SSB-per RO values.

[0137] In some embodiments, the terminal device 110 may further retransmit PRACH on a first RO set using a first power ramping step and retransmit PRACH on a second RO set using a second power ramping step, wherein the first power ramping step is configured independently of the second ramping step.

[0138] In some embodiments, the terminal device 110 may further retransmit PRACH on a first RO set using a first power ramping counter for PRACH retransmission, and retransmit PRACH on a second RO set using a second power ramping counter for PRACH retransmission, wherein the first power ramping counter is configured independently of the second power ramping counter.

[0139] In some embodiments, the terminal device 110 may further reset the power ramping counter when transmitting PRACH on the first RO set based on the fact that the beam associated with PRACH has not changed, and maintain the power ramping counter when transmitting PRACH on the first RO set based on the fact that the beam associated with PRACH has changed.

[0140] In some embodiments, the terminal device 110 may further start a power ramping counter for PRACH retransmissions based on whether the number of PRACH retransmissions on the first RO set exceeds or equals a starting threshold.

[0141] In some embodiments, the terminal device 110 may further perform at least one of the following: monitoring random access response messages in the downlink (DL) subband on an SBFD time basis, and omitting RO in the UL subband on an SBFD time basis.

[0142] In some embodiments, the terminal device 110 may further receive a frequency hopping instruction for the random access procedure message 3 (Msg 3) from the network device, the frequency hopping instruction indicating the enablement or disablement of frequency hopping of Msg 3 in SBFD time units, wherein the frequency hopping instruction further indicates a frequency offset between the first frequency hopping and the second frequency hopping of Msg 3, the frequency offset being configured based on the bandwidth of the UL subband in SBFD time units.

[0143] In some embodiments, the terminal device 110 may further transmit multiple Msg 3 repetitions over SBFD and non-SBFD time units, wherein the multiple Msg 3 repetitions are configured within the UL subband of the SBFD time unit.

[0144] Figure 9 shows a flowchart of a communication method 900 performed on a network device according to several embodiments of the present disclosure. Method 900 may be performed on the network device 120 shown in Figure 1. For clarity, method 900 will be described with reference to Figure 1. Method 900 may include additional actions not shown, and / or some of the actions shown may be omitted, and it should be understood that the scope of the present disclosure is not limited in this respect.

[0145] At 910, the network device 120 transmits to the terminal device 110 a PRACH configuration associated with a first RO set for SBFD time units and a second RO set for non-SBFD time units. The SBFD time units consist of frequency subbands for different link directions. At 920, the network device receives a PRACH from the terminal device in order to transition to a connected state in at least one of the first RO set and the second RO set.

[0146] In some embodiments, the PRACH configuration represents a common set of resource blocks and at least one additional parameter.

[0147] In some embodiments, the PRACH configuration represents a set of resource blocks relative to a starting resource block, where the set of resource blocks is determined at least on the bandwidth of the uplink subband within an SBFD time unit.

[0148] In some embodiments, the network device 120 may receive PRACH by receiving PRACH from a terminal device on at least one RO determined to be valid in the first RO set.

[0149] In some embodiments, the network device 120 may transmit a PRACH configuration by transmitting an SBFD PRACH configuration indicating a first RO set and a non-SBFD PRACH configuration indicating a second RO set, wherein the SBFD PRACH configuration is configured independently of the non-SBFD PRACH configuration.

[0150] In some embodiments, a first RO set includes one or more SBFD ROs for a terminal device to transmit PRACHs on SBFD time units, and a second RO set includes one or more non-SBFD ROs for a terminal device to transmit PRACHs on non-SBFD time units.

[0151] In some embodiments, at least one of the following is satisfied: one or more SBFD ROs and one or more non-SBFD ROs are uniformly numbered; and multiple synchronization signal blocks (SSBs) are mapped to the same SSB-per RO value to one or more SBFD ROs and one or more non-SBFD ROs with uniformly numbered indices.

[0152] In some embodiments, at least one of the following is satisfied: a plurality of SSBs are grouped into a first group of SSBs for SBFD time units and a second group of SSBs for non-SBFD time units; SSBs in the first group of SSBs are mapped to one or more SBFD ROs; and SSBs in the second group of SSBs are mapped to one or more non-SBFD ROs.

[0153] In some embodiments, the following applies: one or more SBFD RO indices are numbered independently of one or more non-SBFD RO indices,

[0154] At least one of the following conditions is met: multiple SSBs are mapped to one or more SBFD RO indices by a first SSB-per RO value, and multiple SSBs are mapped to one or more SBFD RO indices by a second SSB-per RO value.

[0155] In some embodiments, at least one of the following is satisfied: the first RO set and the second RO set have the same resource block location in the frequency domain; the index of one or more SBFD ROs is numbered independently of the index of one or more non-SBFD ROs; multiple SSBs are mapped to the index of one or more SBFD ROs by SSB-per RO values; and multiple SSBs are mapped to the index of one or more non-SBFD ROs by SSB-per RO values.

[0156] In some embodiments, the network device 120 may further transmit random access response messages within the downlink (DL) subband on an SBFD time unit basis.

[0157] In some embodiments, the network device may further transmit a frequency-hopping instruction for the random access procedure message 3 (Msg 3) to the terminal device, the frequency-hopping instruction indicating the enablement or disablement of frequency hopping of Msg 3 in SBFD time units, wherein the frequency-hopping instruction further indicates a frequency offset between different parts of Msg 3, the frequency offset being configured based on the bandwidth of the UL subband in SBFD time units.

[0158] In some embodiments, the network device 120 may further receive multiple Msg 3 repetitions over SBFD and non-SBFD time units, wherein the multiple Msg 3s are located within the UL subband of the SBFD time unit.

[0159] Figure 10 is a simplified block diagram of a device 1000 suitable for carrying out some embodiments of the present disclosure. The device 1000 can be considered as a further exemplary embodiment of a terminal device 110 or a network device 120, as shown in Figure 1. Thus, the device 1000 can be implemented in, or as at least part of, the above-described network device or terminal device.

[0160] As shown in the figure, the device 1000 includes a processor 1010, a memory 1020 coupled to the processor 1010, a preferred transceiver 1040 coupled to the processor 1010, and a communication interface coupled to the transceiver 1040. The memory 1010 stores at least a portion of the program 1030. The transceiver 1040 may be for bidirectional or unidirectional communication, depending on the requirements. The transceiver 1040 may include at least one transmitter 1042 and a receiver 1044. The transmitter 1042 and receiver 1044 may be functional modules or physical entities. The transceiver 840 has at least one antenna to facilitate communication, but in practice, the access node referred to in this application may have multiple antennas. The communication interface may represent any interface necessary for communication with other network elements, such as the X2 / Xn interface for bidirectional communication between eNBs / gNBs, the S1 / NG interface for communication between Mobility Management Entities (MMEs) / Access and Mobility Management Functions (AMFs) / SGWs / UPEs and eNBs / gNBs, the Un interface for communication between eNBs / gNBs and relay nodes (RNs), or the Uu interface for communication between eNBs / gNBs and terminal devices.

[0161] Program 1030 is assumed to include program instructions, and when the program is executed by the associated processor 1010, it enables the device 1000 to operate according to embodiments of the present disclosure, as described herein with reference to Figures 1 to 9. Embodiments of the present disclosure may be implemented by computer software executable by the processor 1010 of the device 1000, by hardware, or by a combination of software and hardware. The processor 1010 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 1010 and memory 1020 may form processing means 1050 adapted to implement various embodiments of the present disclosure.

[0162] Memory 1020 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, including but not limited to non-temporary computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. Although only one memory 1020 is shown in device 1000, device 1000 may contain multiple physically different memory modules. Processor 1010 may be of any type suitable for a local technology network and may include, but not limited to, one or more of the following: general-purpose computers, dedicated computers, microprocessors, digital signal processors (DSPs), and processors based on multicore processor architectures. Device 1000 may contain multiple processors, such as application-specific integrated circuit chips that are time-dependent to a clock synchronized with the main processor.

[0163] In some embodiments, the terminal device includes a circuit configured to perform method 800.

[0164] In some embodiments, the network device includes a circuit configured to perform method 900.

[0165] The components included in the instruments and / or apparatus of this disclosure may be implemented in a variety of ways, including software, hardware, firmware, or any combination thereof. In one embodiment, one or more units may be implemented using software or firmware, for example, machine-executable instructions stored on a storage medium. In addition to, or instead of, machine-executable instructions, some or all units of the instruments and / or apparatus may be implemented at least partially by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used without limitation include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip systems (SOCs), and complex programmable logic devices (CPLDs).

[0166] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some embodiments may be implemented in hardware, while others may be implemented in firmware or software executed by a controller, microprocessor, or other computing device. Although various embodiments of the present disclosure are illustrated and described using block diagrams, flowcharts, or some other graphical representations, it will be understood that any block, apparatus, system, technical terminal apparatus, or method described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controller, or other computing device, or some combination thereof, as non-limiting examples.

[0167] This disclosure also provides at least one computer program product tangibly stored on a non-temporary computer-readable storage medium. The computer program product includes computer-executable instructions, such as instructions contained in a program module, which are executed on a device on a target real or virtual processor, and which perform the processes or methods described above with reference to any of Figures 2 to 9. Generally, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a specific task or implement a specific abstract data type. The functionality of program modules may be combined or separated as needed in various embodiments. The machine-executable instructions for a program module may be executed in a local or distributed device. In a distributed device, the program module may reside on both local and remote storage media.

[0168] Program code for performing the methods of this disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a dedicated computer, or other programmable data processing device, and when executed by the processor or controller, the functions / operations specified in the flowchart and / or block diagrams will be performed. The program codes may run entirely on the machine, partially on the machine, as a standalone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0169] The above program code may be embodied in a machine-readable medium, which may be any tangible medium that contains or can store a program used by an instruction execution system, apparatus, or device, or a program used in conjunction with such a system or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. More specific examples of machine-readable storage media include electrical connections with one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM, or flash memory), optical fibers, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0170] Furthermore, although the operations are presented in a specific order, it should not be understood that such operations must be performed in the specific order shown, sequentially, or all shown operations must be performed in order to obtain the desired results. In certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although the above description includes several specific embodiments, these should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented individually or in any suitable combination of sub-features in multiple embodiments.

[0171] While this disclosure is described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

[0172] In summary, embodiments of this disclosure can provide the following solutions.

[0173] The terminal device comprises a transceiver and a processor communicatively connected to the transceiver, wherein the processor is configured to cause the terminal device to receive from a network device a physical random access channel (PRACH) configuration associated with a first set of PRACH opportunities (ROs) for subband non-overlapping full-duplex (SBFD) time units and a second set of ROs for non-SBFD time units, wherein the SBFD time units consist of frequency subbands for different link directions, and to transmit PRACHs to the network device in at least one of the first set of ROs and the second set of ROs.

[0174] In one embodiment, the PRACH configuration includes a common set of resource blocks and at least one additional parameter, wherein the terminal device is further configured to determine at least one of the first RO set and the second RO set by determining a first RO set based on the common set of resource blocks and at least one additional parameter, and determining a second RO set based on the common set of resource blocks.

[0175] In one embodiment, the PRACH configuration represents a set of resource blocks relative to a starting resource block, where the terminal device is further configured to determine at least one of the first RO set and the second RO set by at least one of the following: using a first starting resource block of the uplink subband within an SBFD time unit as the starting resource block to determine the minimum RO of a first RO set based on the set of resource blocks, or using a second starting resource block of the bandwidth portion as the starting resource block to determine the minimum RO of a second RO set based on the set of resource blocks.

[0176] In one embodiment, a common set of resource blocks or at least one of a set of resource blocks is determined based at least on the bandwidth of the uplink subband within an SBFD time unit.

[0177] In one embodiment, the terminal device is configured to receive PRACH configurations by receiving an SBFD PRACH configuration indicating a first RO set and a non-SBFD PRACH configuration indicating a second RO set, wherein the SBFD PRACH configuration is configured independently of the non-SBFD PRACH configuration.

[0178] In one embodiment, the terminal device is further configured to perform at least one of the following: determining that the RO of the first RO set is valid based on the fact that the first RO set overlaps with SBFD time units or uplink (UL) time units in the time domain; and determining that the RO of the first RO set is invalid based on the fact that the first RO set overlaps with DL time units without an SBFD configuration in the time domain.

[0179] In one embodiment, the terminal device is further configured to perform at least one of the following: determining that the ROs of the first RO set are valid based on the fact that the first RO set is located in the uplink subband in the frequency domain on an SBFD time unit; and determining that at least one RO of the first RO set is invalid based on the fact that at least one RO overlaps at least partially with the guard subband or downlink subband in the frequency domain on an SBFD time unit.

[0180] In one embodiment, the terminal device is configured to transmit PRACH by transmitting PRACH to the network device on at least one RO determined to be valid in the first RO set.

[0181] In one embodiment, a first RO set includes one or more SBFD ROs for a terminal device to transmit PRACH on an SBFD time unit, and a second RO set includes one or more non-SBFD ROs for a terminal device to transmit PRACH on a non-SBFD time unit.

[0182] In one embodiment, at least one of the following is satisfied: one or more SBFD ROs and one or more non-SBFD ROs are uniformly numbered; and multiple synchronization signal blocks (SSBs) are mapped to the uniformly numbered indices of one or more SBFD ROs and one or more non-SBFD ROs by the same SSB-per RO value.

[0183] In one embodiment, at least one of the following conditions is met: a plurality of SSBs are grouped into a first group of SSBs for SBFD time units and a second group of SSBs for non-SBFD time units; SSBs within the first group of SSBs are mapped to one or more SBFD ROs; and SSBs within the second group of SSBs are mapped to one or more non-SBFD ROs.

[0184] In one embodiment, at least one of the following is satisfied: one or more SBFD RO indices are numbered independently of one or more non-SBFD RO indices; multiple SSBs are mapped to one or more SBFD RO indices by a first SSB-per RO value; and multiple SSBs are mapped to one or more SBFD RO indices by a second SSB-per RO value.

[0185] In one embodiment, at least one of the following is satisfied: the first RO set and the second RO set have the same resource block location in the frequency domain; the index of one or more SBFD ROs is numbered independently of the index of one or more non-SBFD ROs; multiple SSBs are mapped to the index of one or more SBFD ROs by SSB-per RO values; and multiple SSBs are mapped to the index of one or more non-SBFD ROs by SSB-per RO values.

[0186] In one embodiment, the terminal device is further configured to retransmit PRACH on a first RO set using a first power ramping step and to retransmit PRACH on a second RO set using a second power ramping step, wherein the first power ramping step is configured independently of the second ramping step.

[0187] In one embodiment, the terminal device is further configured to retransmit PRACH on a first RO set using a first power ramping counter for PRACH retransmission, and to retransmit PRACH on a second RO set using a second power ramping counter for PRACH retransmission, wherein the first power ramping counter is configured independently of the second power ramping counter.

[0188] In one embodiment, the terminal device is further configured to reset the power ramping counter when transmitting PRACH on a first RO set, based on the fact that the beam associated with PRACH has not changed, and to maintain the power ramping counter when transmitting PRACH on a first RO set, based on the fact that the beam associated with PRACH has changed.

[0189] In one embodiment, the terminal device is further configured to start a power ramping counter for PRACH retransmissions based on whether the number of PRACH retransmissions on a first RO set exceeds or equals a starting threshold.

[0190] In one embodiment, the terminal device is further configured to perform at least one of the following: monitoring random access response messages in the downlink (DL) subband on an SBFD time unit; and omitting ROs in the UL subband on an SBFD time unit.

[0191] In one embodiment, the terminal device is further configured to receive frequency hopping instructions for the random access procedure massage 3 (Msg 3) from the network device, the frequency hopping instructions indicating the enablement or disablement of frequency hopping of Msg 3 in SBFD time units, wherein the frequency hopping instructions further indicate a frequency offset between the first frequency hopping and the second frequency hopping of Msg 3, the frequency offset being configured based on the bandwidth of the UL subband in SBFD time units.

[0192] In one embodiment, the terminal device is further configured to transmit multiple Msg 3 repetitions over SBFD and non-SBFD time units, wherein the multiple Msg 3 repetitions are configured within the UL subband of the SBFD time unit.

[0193] The network device comprises a transceiver and a processor communicatively connected to the transceiver, the processor being configured to transmit to a terminal device a random access channel (PRACH) configuration associated with a first set of PRACH opportunities (ROs) for subband non-overlapping full-duplex (SBFD) time units and a second set of ROs for non-SBFD time units, wherein the SBFD time units consist of frequency subbands for different link directions, and to receive a PRACH from the terminal device in order to transition to a connected state in at least one of the first set of ROs and the second set of ROs.

[0194] In one embodiment, the PRACH configuration represents a common set of resource blocks and at least one additional parameter.

[0195] In one embodiment, the PRACH configuration represents a set of resource blocks relative to a starting resource block, where the set of resource blocks is determined at least on the bandwidth of the uplink subband within an SBFD time unit.

[0196] In one embodiment, the network device is configured to receive PRACH by receiving PRACH from a terminal device on at least one RO determined to be valid in the first RO set.

[0197] In one embodiment, the network device is configured to transmit PRACH configurations by transmitting an SBFD PRACH configuration indicating a first RO set and a non-SBFD PRACH configuration indicating a second RO set, wherein the SBFD PRACH configuration is configured independently of the non-SBFD PRACH configuration.

[0198] In one embodiment, a first RO set includes one or more SBFD ROs for a terminal device to transmit PRACH on an SBFD time unit, and a second RO set includes one or more non-SBFD ROs for a terminal device to transmit PRACH on a non-SBFD time unit.

[0199] In one embodiment, at least one of the following is satisfied: one or more SBFD ROs and one or more non-SBFD ROs are uniformly numbered; and multiple synchronization signal blocks (SSBs) are mapped to the uniformly numbered indices of one or more SBFD ROs and one or more non-SBFD ROs by the same SSB-per RO value.

[0200] In one embodiment, at least one of the following conditions is met: a plurality of SSBs are grouped into a first group of SSBs for SBFD time units and a second group of SSBs for non-SBFD time units; SSBs within the first group of SSBs are mapped to one or more SBFD ROs; and SSBs within the second group of SSBs are mapped to one or more non-SBFD ROs.

[0201] In one embodiment, at least one of the following is satisfied: one or more SBFD RO indices are numbered independently of one or more non-SBFD RO indices; multiple SSBs are mapped to one or more SBFD RO indices by a first SSB-per RO value; and multiple SSBs are mapped to one or more SBFD RO indices by a second SSB-per RO value.

[0202] In one embodiment, at least one of the following is satisfied: the first RO set and the second RO set have the same resource block location in the frequency domain; the index of one or more SBFD ROs is numbered independently of the index of one or more non-SBFD ROs; multiple SSBs are mapped to the index of one or more SBFD ROs by SSB-per RO values; and multiple SSBs are mapped to the index of one or more non-SBFD ROs by SSB-per RO values.

[0203] In one embodiment, the network device is further configured to transmit random access response messages within the downlink (DL) subband on an SBFD time unit.

[0204] In one embodiment, the network device is further configured to transmit frequency-hopping instructions for the random access procedure message 3 (Msg 3) to the terminal device, the frequency-hopping instructions indicating the enablement or disablement of frequency-hopping of Msg 3 in SBFD time units, wherein the frequency-hopping instructions further indicate frequency offsets between different parts of Msg 3, the frequency offsets being configured based on the bandwidth of the UL subband in SBFD time units.

[0205] In one embodiment, the network device is further configured to receive multiple Msg 3 repetitions over SBFD and non-SBFD time units, wherein the multiple Msg 3s are located within the UL subband of the SBFD time unit.

Claims

1. A terminal device, A walkie-talkie and A processor that is communicatively connected to the transceiver, wherein the processor is connected to the terminal device. Receiving a Physical Random Access Channel (PRACH) configuration from a network device, which is associated with a first set of PRACH Occasions (ROs) for subband non-overlapping full duplex (SBFD) time units and a second set of ROs for non-SBFD time units, wherein the SBFD time units consist of frequency subbands for different link directions. The network device transmits PRAC in at least one of the first RO set and the second RO set, A processor configured to perform the following actions: Terminal device.

2. The PRACH configuration described above represents a common set of resource blocks and at least one additional parameter, where the terminal device further comprises Determining the first RO set based on the common set of resource blocks and the at least one additional parameter, The second RO set is determined based on the aforementioned common set of resource blocks, The system is configured to determine at least one of the first RO set and the second RO set by at least one of the following: The terminal device according to claim 1.

3. The PRACH configuration represents a set of resource blocks for a starting resource block, where the terminal device further includes Using the first start resource block of the uplink subband within the SBFD time unit as the start resource block, and determining the minimum RO of the first RO set based on the set of resource blocks, or Using the second starting resource block of the bandwidth portion as the starting resource block, the minimum RO of the second RO set is determined based on the set of resource blocks. The system is configured to determine at least one of the first RO set and the second RO set by at least one of the following: The terminal device according to claim 1.

4. The terminal device according to claim 2 or 3, wherein at least one of the common set of resource blocks or the set of resource blocks is determined at least on the bandwidth of the uplink subband within the SBFD time unit.

5. The aforementioned terminal device is Receiving the SBFD PRACH configuration indicating the first RO set, Receiving a non-SBFD PRACH configuration indicating the second RO set, wherein the SBFD PRACH configuration is configured independently of the non-SBFD PRACH configuration. The PRACH configuration is configured to receive the PRACH configuration. The terminal device according to claim 1.

6. The aforementioned terminal device further, Based on the fact that the first RO set overlaps with the SBFD time unit or uplink (UL) time unit in the time domain, the RO of the first RO set is determined to be valid, Based on the fact that the first RO set overlaps with DL time units in the time domain without an SBFD configuration, the RO of the first RO set is determined to be invalid, Configured to perform at least one of the following: The terminal device according to claim 1.

7. The aforementioned terminal device further, Based on the fact that the first RO set is within the uplink subband of the SBFD time unit in the frequency domain, the RO of the first RO set is determined to be valid, Determining that at least one RO of the first RO set is invalid based on the fact that at least one RO overlaps at least partially with the guard subband or downlink subband of the SBFD time unit in the frequency domain, Configured to perform at least one of the following: The terminal device according to claim 1.

8. The aforementioned terminal device is Transmitting the PRACH to the network device on at least one RO determined to be valid in the first RO set, The PRAC is configured to transmit by The terminal device according to claim 5 or 6.

9. The terminal device according to claim 1, wherein the first RO set includes one or more SBFD ROs for the terminal device to transmit PRACH on the SBFD time unit, and the second RO set includes one or more non-SBFD ROs for the terminal device to transmit PRACH on the non-SBFD time unit.

10. below: The indices of the one or more SBFD ROs and the one or more non-SBFD ROs are uniformly numbered, Multiple synchronization signal blocks (SSBs) are mapped to the uniformly numbered indices of one or more SBFD ROs and one or more non-SBFD ROs by the same SSB-per RO value, Satisfying at least one of the following: The terminal device according to claim 9.

11. below: Multiple SSBs are grouped into a first group of SSBs for the SBFD time unit and a second group of SSBs for the non-SBFD time unit, The SSBs within the first group of SSBs are mapped to one or more SBFD ROs, The SSBs within the second group of SSBs are mapped to one or more non-SBFD ROs, Satisfying at least one of the following: The terminal device according to claim 9.

12. below: The index of the one or more SBFD ROs is numbered independently of the index of the one or more non-SBFD ROs, Multiple SSBs are mapped to the index of one or more SBFD ROs by the first SSB-per RO value, The plurality of SSBs are mapped to the index of one or more SBFD ROs by the second SSB-per RO value, Satisfying at least one of the following: The terminal device according to claim 9.

13. below: The first RO set and the second RO set have the same resource block location in the frequency domain, The index of the one or more SBFD ROs is numbered independently of the index of the one or more non-SBFD ROs, Multiple SSBs are mapped to the index of one or more SBFD ROs by the SSB-per RO value, The plurality of SSBs are mapped to the index of one or more non-SBFD ROs by the SSB-per RO value, Satisfying at least one of the following: The terminal device according to claim 9.

14. The aforementioned terminal device further, Using the first power ramping step, the PRACH is retransmitted on the first RO set, and The PRACH is configured to be retransmitted on the second RO set using a second power ramping step, and the first power ramping step is configured independently of the second ramping step. The terminal device according to claim 1.

15. The aforementioned terminal device further, Using a first power ramping counter for PRACH retransmission, the PRACH is retransmitted on the first RO set, and The PRACH is configured to be retransmitted on the second RO set using a second power ramping counter for PRACH retransmission, and the first power ramping counter is configured independently of the second power ramping counter. The terminal device according to claim 1.

16. The aforementioned terminal device further, When transmitting the PRACH on the first RO set, the power ramping counter is reset based on the fact that the beam associated with the PRACH has not been changed, and When transmitting the PRACH on the first RO set, the power ramping counter is configured to maintain the power ramping counter based on the change in the beam associated with the PRACH. The terminal device according to claim 1.

17. The aforementioned terminal device further, A power ramping counter for PRACH retransmissions is configured to start based on whether the number of PRACH retransmissions on the first RO set exceeds or is equal to a starting threshold. The terminal device according to claim 1.

18. The aforementioned terminal device further, Monitoring random access response messages within the SBFD time unit downlink (DL) subband, The RO within the UL subband of the aforementioned SBFD time unit is omitted, Configured to perform at least one of the following: The terminal device according to claim 1.

19. The aforementioned terminal device further, The network device is configured to receive frequency hopping instructions for the random access procedure's massage 3 (Msg 3), and the frequency hopping instructions indicate whether the frequency hopping of Msg 3 in the SBFD time unit is enabled or disabled. Here, the frequency hopping instruction further indicates a frequency offset between the first frequency hopping and the second frequency hopping of Msg 3, wherein the frequency offset is configured based on the bandwidth of the UL subband in the SBFD time unit. The terminal device according to claim 1.

20. The aforementioned terminal device further, It is configured to transmit multiple Msg 3 repetitions across SBFD and non-SBFD time units, wherein the multiple Msg 3 repetitions are configured within the UL subband of the SBFD time unit. The terminal device according to claim 1.

Images