Prach preamble transmission in SBFD system

Abstract

A method in an SBFD aware UE is disclosed. The method comprises receiving (S1) a RACH configuration from a network node, transmitting (S3) a first PRACH preamble in a first PRACH occasion comprising a first symbol type, a symbol type being either non-SBFD symbol or SBFD symbol, and when reception of a RAR related to the 5 first PRACH preamble is unsuccessful, transmitting (S4) a second PRACH preamble in a second PRACH occasion comprising a second symbol type different from the first symbol type.

Description

[0001] TITLE

[0002] PRACH preamble transmission in SBFD system

[0003] TECHNICAL FIELD

[0004] The present disclosure relates to wireless communications, and in particular, to power ramping in subband full duplex (SBFD) physical random access channels (PRACH).

[0005] BACKGROUND

[0006] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipment (UE), as well as communication between network nodes and between UEs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0007] Subband full duplex

[0008] In a conventional time division duplex (TDD) system, entire carrier bandwidth (BW) or all carriers in the same frequency band should use the same downlink (DL) transmission or uplink (UL) reception directions. This is illustrated in the examples of FIGS. 1 and 2.

[0009] For the 3GPP Technical Release 19 (3GPP Rel-19) evolution of the NR system, 3GPP has decided to specify subband full duplex (SBFD) systems.

[0010] In such a system, a portion of a wide bandwidth carrier may be used for a different direction than that of the rest of the carrier. This is illustrated in the example of FIG. 3. That is, unlike a conventional TDD system as shown in FIG. 1, where the entire bandwidth is used for DL transmission in the first three slots, the center portion of the SBFD carrier is used for UL reception while the rest of the carrier continues to be used for DL transmission as shown in FIG. 3.

[0011] Similarly, instead of utilizing all carriers for the same DL or UL directions in a conventional TDD system as shown in FIG. 2, some carriers in the SBFD system may be used for a different direction than that of the other carriers as shown in the example of FIG. 4.In the 3GPP Rel-19 work, the scope has been limited such that in SBFD operation, only gNBs (i. e. , network nodes) transmit DL and receive UL simultaneously. An individual UE is scheduled in only one direction (DL / D or UL / U) at a time. RANI has further agreed to configure one or more orthogonal frequency division multiplexed (OFDM) symbols of a slot with two or more resource block sets (subbands) where each resource block (RB) set corresponds to a frequency domain subband and has a defined transmission direction (D or U). The RB sets may have gaps between them that serve as guard bands where neither DL or UL transmission occurs. The examples of FIGS. 5 and 6 show two example RB set configurations, one with D-U-D configuration (FIG. 5) and the other with U-D-U configuration (FIG. 6). The RB sets are configured either by introduction of new radio resource control (RRC) parameter(s) or enhancement of an existing RRC parameter, e.g., TDD-UL-DL-ConflgDedicated. In either case, the parameter(s) signal the size and frequency domain location of the RB sets as well as which symbols / slots in the TDD UL / DL pattern are configured with RB sets.

[0012] Random access and physical random-access channel (PRACH)

[0013] The physical random access channel (PRACH) is an NR UL physical channel that is used for several purposes. The PRACH is used by UEs for contention-based random access (CBRA) as part of the initial access to the network node. The PRACH may be used for CBRA or contention-free random access (CFRA) based on a physical downlink control channel (PDCCH) order from the network node (e.g., for beam recovery), and it may be used for a system information (SI) request.

[0014] The network node configures specific time-frequency resources for PRACH, referred to as PRACH occasions, or ROs for short. The configuration is indicated by means of several RRC-signaled parameters, one parameter being an index into a PRACH configuration table (Tables 6.3.3.2-1 - 6.3.3.2-3 in 3GPP Technical Standard (TS) 38.211 VI 8.5.0), which in turn defines the values of several more detailed parameters. However, all configured ROs are not necessarily valid; some ROs may be invalidated, e.g., because they occur too close in time to synchronization signal blocks (SSBs) which would cause issues to UEs if they cannot both receive on DL and transmit on UL at the same time.

[0015] The valid ROs or a subset of valid ROS are further associated with / mapped to SSBs by the network node. This association is used e.g., by a UE during initial access, where the UE selects which RO to use based on which SSBs it may receive. The association is also used in conjunction with PDCCH order-based CFRA; the network node indicates an SSB, and the UE then determines which RO to use based on the SSB-to-ROassociations. Hence, the network node does not directly point to an RO but rather indicates it indirectly via the SSB-to-RO associations.

[0016] PRACH power control

[0017] The PRACH preamble transmit power is specified in 3GPP TS 38.213 V18.5.0, Sec. 7.4 as follows:

[0018]

[0019]

[0020] The core of the higher layer random access preamble transmission procedure is specified in 3GPP TS 38.321 V18.4.0 for the general case, where also the power ramping as provided by PREAMBLE RECEIVED TARGET POWER is specified as follows:

[0021] > >

[0022] >

[0023] >

[0024] >

[0025] >

[0026]

[0027] Consequently, the medium access control (MAC) layer provides the physical layer with PPRACH o PREAMBLE RECEIVED TARGET POWER for each PRACH attempt, based on the selected RO or PRACH occasion. The physical layer then adds a path-loss (PL) component and ascertains that the maximum transmit power PCMAX is not exceeded.

[0028] SBFD RACH

[0029] 3GPP has agreed to specify RACH in SBFD using either a single RACHconfiguration or two separate RACH configurations as follows:

[0030]

[0031] The PRACH preamble detection sensitivity may vary substantially between SBFD and non-SBFD symbols, in that SBFD symbols may be exposed to much higher interference levels at the network node due to both its own simultaneous transmissions and transmissions from interfering network nodes. In addition, different PRACH preamble formats may use different transmit powers and transmit durations (see FIG. 7), resulting in different reception properties. Hence, there is a need for novel solutions in order to maintain a desirable power ramping behavior considering the different interference, transmit power and transmit durations that may arise in the same SBFD RACH procedure.

[0032] SUMMARY

[0033] Some embodiments advantageously provide methods, network nodes and user equipment (UE) for transmitting PRACH preambles in SBFD systems and for power ramping in SBFD PRACH.

[0034] According to a first aspect, a method implemented in an SBFD aware UE, configured to communicate with a network node, is provided. The method comprises receiving a RACH configuration from the network node, transmitting a first PRACH preamble, according to the received RACH configuration, in a first PRACH occasioncomprising a first symbol type. A symbol type is either non-SBFD symbol or SBFD symbol. The method further comprises, when reception of a RAR related to the first PRACH preamble is unsuccessful, transmitting a second PRACH preamble, according to the received RACH configuration, in a second PRACH occasion comprising a second symbol type different from the first symbol type.

[0035] According to a second aspect, a method implemented in a network node is provided. The network node is configured to communicate with an SBFD aware UE configured to transmit a first PRACH preamble in a first PRACH occasion comprising a first symbol type, and to transmit a second PRACH preamble in a second PRACH occasion comprising a second symbol type different from the first symbol type when a RAR related to the first PRACH preamble is unsuccessful. A symbol type is either non-SBFD symbol or SBFD symbol. The method implemented in the network node comprises transmitting a RACH configuration to the UE, thereby configuring the UE to transmit the first and the second PRACH preamble.

[0036] According to further aspects, an SBFD aware UE configured to perform the method described according to the first aspect and a network node configured to perform the method described according to the second aspect are provided.

[0037] BRIEF DESCRIPTION OF THE DRAWINGS

[0038] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0039] FIG. 1 illustrates a conventional single carrier TDD system;

[0040] FIG. 2 illustrates a conventional multi-carrier TDD system;

[0041] FIG. 3 illustrates a SBFD single carrier TDD system;

[0042] FIG. 4 illustrates a SBFD multi-carrier TDD system;

[0043] FIG. 5 is a first RB set configuration in an SBFD symbol;

[0044] FIG. 6 is a second RB set configuration in an SBFD symbol;

[0045] FIG. 7 illustrates different PRACH preamble formats with different transmit powers and transmit durations;

[0046] FIG. 8 is a schematic diagram of an example network architecture illustrating a communication system according to principles disclosed herein;

[0047] FIG. 9 is a block diagram of a network node in communication with a userequipment over a wireless connection according to some embodiments of the present disclosure;

[0048] FIG. 10 is a schematic diagram of another example network architecture illustrating a communication system according to principles disclosed herein;

[0049] FIG. 11 A is a flowchart of an example process in a UE according to some embodiments of the present disclosure;

[0050] FIG. 1 IB is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0051] FIG. 12A is a flowchart of an example process in a network node for power ramping in subband full duplex (SBFD) physical random access channels (PRACH) according to some embodiments of the present disclosure;

[0052] FIG. 12B is a flowchart of an example process in a user equipment for power ramping in subband full duplex (SBFD) physical random access channels (PRACH) according to some embodiments of the present disclosure; and

[0053] FIG. 13 is a flowchart of an example process according to principles disclosed herein.

[0054] DETAILED DESCRIPTION

[0055] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to power ramping in subband full duplex (SBFD) physical random access channels (PRACH). Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0056] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements.

[0057] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the artwill appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0058] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0059] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0060] The term “network node” used herein may be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multistandard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node.

[0061] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein may be any type of user equipment capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped(LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device etc.

[0062] Also, in some embodiments the generic term “radio network node” is used. It may be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0063] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR) and / or 6G, may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. It is contemplated that other 3GPP systems may make use of the concepts and arrangements disclosed herein. For example, a disclosure relating to NR may also be implementable in a 6G system and / or an LTE system, a disclosure relating to 6G may also be implementable in a NR and / or LTE system, and a disclosure relating to LTE may also be implementable in a NR and / or 6G system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0064] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, may be distributed among several physical devices.

[0065] Unless otherwise defined, all terms (including 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. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0066] Some embodiments are directed to power ramping in subband full duplex (SBFD) physical random access channels (PRACH).

[0067] Returning to the drawing figures, in which like elements are referred to by likereference numerals, there is shown in FIG. 8 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G) and / or 6G, which comprises an access network 12, such as a radio access network, and a core network 14. The core network 14 includes one or more network nodes 15. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipment 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0068] As one example, in certain embodiments, access network 12 may contain some access network nodes 16 that support 3 GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 16 support (or the same access network nodes 16 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, communication system 10 may support multiple generations of related communication standards (e.g., 4G, 5G and 6G 3GPP communication standards) and, as a result, may include an access network 12 and / or a core network 14 that supports multiple different standard generations or may include multiple access networks 12 and / or multiple core networks 14 with individual networks supporting different standards generations.

[0069] Also, it is contemplated that a UE 22 may be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 may have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 may be in communication with an eNB for LTE / E-UTRAN, a gNB for NR / NG-RAN (i.e. being configured for multiradio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial RadioAccess Network) New Radio - Dual Connectivity (EN-DC) and / or Wi-Fi.

[0070] A network node 16 (eNB or gNB) is configured to include a configuration unit 24 which may be configured to configure the UE with a first preamble receive target power for a first subband full duplex (SBFD) physical random access channel (PRACH) symbol type and a second preamble receive target power for a second non-SBFD symbol type. A user equipment 22 is configured to include a PRACH unit 26 which may be configured to transmit a first PRACH preamble according to the received PRACH configuration with a first transmit power in a first symbol type, and when a random access response (RAR) is not detected, transmit a second PRACH preamble according to the received PRACH configuration with a second transmit power in a second symbol type.

[0071] Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 9.

[0072] The communication system 10 includes a network node 16 provided in a communication system 10 and including hardware 28 enabling it to communicate with the UE 22. The hardware 28 may include a communication interface 29 comprising a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves.

[0073] In the embodiment shown, the hardware 28 of the network node 16 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0074] Thus, the network node 16 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, networkstorage device, etc.) accessible by the network node 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16.

[0075] Processor 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include a configuration unit 24 which may be configured to configure the UE with a first preamble receive target power for a first subband full duplex (SBFD) physical random access channel (PRACH) symbol type and a second preamble receive target power for a second non-SBFD symbol type.

[0076] The network node 16 may be composed of multiple distinct network entities (e.g., aNodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 16 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 16 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 40 or portions of memory 40 for different RATs) and some components may be reused (e.g., a same antenna may be shared by different RATs). The network node 16 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 16, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 16.

[0077] In certain alternative embodiments, network node 16 may be capable of wireless communication but does not include separate radio front-end circuitry, instead, the processing circuitry 36 includes radio front-end circuitry and is connected to the antenna34. Similarly, in some embodiments, all or some of the RF receivers, transmitters and / or transceivers are part of the radio interface 30. In still other embodiments, the communication interface 29 includes one or more ports or terminals, the radio interface 30, and the RF receiver, transmitter and / or transceiver, and the communication interface 31 communicates with baseband processing circuitry, which is part of a digital unit (not shown).

[0078] The antenna 34 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 34 may be coupled to the radio front-end circuitry in radio interface 30 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 34 is separate from the network node 16 and connectable to the network node 16 through one or more interfaces or ports.

[0079] Network node 15 may include one or more components described above with respect to network node 16, e.g., communication interface 29, radio interface 30, antenna 34, ports, processing circuitry 36, processor 38, memory 40 and software 42. These elements of network node 15 may be arranged such that network node 15 may perform various core network functions. Network node 15 may communicate wirelessly or via a wired connection with network nodes 16 via communication link 59.

[0080] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 44 that may include a radio interface 46 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 46 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 46 includes an array of antennas 48 to radiate and receive signal(s) carrying electromagnetic waves.

[0081] Communication functions of the radio interface 46 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA),GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0082] The hardware 44 of the UE 22 further includes processing circuitry 50. The processing circuitry 50 may include a processor 52 and memory 54. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 50 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 52 may be configured to access (e.g., write to and / or read from) memory 54, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0083] Thus, the UE 22 may further comprise software 56, which is stored in, for example, memory 54 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide a service to a human or non-human user via the UE 22. The processing circuitry 50 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 52 corresponds to one or more processors 52 for performing UE 22 functions described herein. The UE 22 includes memory 54 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 and / or the client application 58 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causes the processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 50 of the user equipment 22 may include a PRACH unit 26 which may be configured to transmit a first PRACH preamble according to the received PRACH configuration with a first transmit power in a first symbol type, and when a random access response (RAR) is not detected, transmit a second PRACH preamble according to the received PRACH configuration with a second transmit power in a second symbol typeIn some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG. 9 and independently, the surrounding network topology may be that of FIG. 8.

[0084] The wireless connection 32 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

[0085] Although FIGS. 8 and 9 show various “units” such as configuration unit 24 and PRACH unit 26 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0086] FIG. 10 is another example of a communication system 10 according to some embodiments. As used herein, the communication system 10 of FIG. 10 includes multiple access points (APs) 60 (with four example APs 60a, 60b, 60c, and 60d being depicted) and multiple wireless devices, referred to in the context of communication system 10 of FIG.

[0087] 10 as stations (STAs) 62 (referred to individually as STA 62a, STA 62b, STA 62c, STA 62d, and STA 62e). STA 62a is served by AP 60a in a first basic service set (BSS) 64a. STA 60b and STA 60c are served by AP 60b in a second BSS, BSS 64b. STA 62d is served by AP 60c in a third BSS, BSS 64c. STA 62e is served by AP 60d in a fourth BSS, BSS 64d. Stations 62 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like, including UEs 22 that are shown and described with respect to FIGS. 8 and 9. In other words, in some embodiment, STA 62 is a UE 22. Further, stations 62 may, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0088] Each of STAs 62 may connect through a radio link to one of APs 60. For example, depending on location or channel conditions experienced by a given STA 62, the STAmay select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0089] Each AP 60 may provide data connectivity to STAs 62 connected to a particular AP 60. As illustrated, APs 60 may be connected to a data network 66. In this way, APs 60 may also provide data connectivity between STAs 62 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like.

[0090] Accordingly, the radio link established between a given STA 62 and its serving AP 60 may be used for providing various kinds of services to STA 62, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 62 and / or on a device linked to STA 62. By way of example, FIG. 10 illustrates an application service platform 68 provided in data network 66. The application(s) executed on STA 62 and / or on one or more other devices linked to STA 62 may use the radio link for data communication with one or more other STA 62 and / or the application service platform 68, thereby enabling utilization of the corresponding service(s) at STA 62.

[0091] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for power ramping in subband full duplex (SBFD) physical random access channels (PRACH).

[0092] Legacy PRACH assumes a single PRACH preamble format and stationary channel conditions. SBFD PRACH allows for PRACH in both UL / F symbols and SBFD symbols, each of which may have different channel conditions due to different interference conditions. Additionally, different PRACH preamble formats may be used in SBFD, resulting in highly differing PRACH reception sensitivity. Both these effects may result in a need for the network node to, e.g., configure different preamble receive target powers (PREAMBLE RECEIVED TARGET POWER) for the different PRACH alternatives (legacy vs SBFD PRACH). Some embodiments provide solutions to the problem of performing proper PRACH power ramping for SBFD RACH with such varying conditions. As a result, the network node may have increased PRACH capacity and improved UL capacity due to proper power settings of the UE PRACH transmission.Some embodiments may include performing PRACH preamble power ramping in SBFD-aware UEs, attempting to connect to a network node 16 in a cell. The SBFD RACH configuration may be either a single configuration (legacy and SBFD RACH provided by the same configuration) or dual configurations (legacy and SBFD RACH provided in separate configurations).

[0093] FIG. 13 is a flowchart of an example process according to principles disclosed herein. In step 100, the UE 22 receives the RACH configuration(s) (e.g., via cell specific signaling, e.g., system information or RRC signaling).

[0094] In step 110, the UE 22 transmits a first PRACH preamble according to a first RACH configuration with a first transmit power in a first symbol type.

[0095] In step 120, the UE 22 determines to transmit a second PRACH preamble according to a second RACH configuration with a second transmit power in a second symbol type.

[0096] In step 130, the UE 22 transmits a second PRACH preamble according to a second RACH configuration with a second transmit power in a second symbol type.

[0097] In some embodiments, the first and second symbol types are either the same or different, according to a configuration or specification, i.e., the first and second symbol types may both be non-SBFD (UL / F is used interchangeably with non-SBFD when referring to UL transmissions) or SBFD symbols, or the first symbol type may be non-SBFD or SBFD, respectively and the second symbols type may be SBFD or non-SBFD, respectively. ‘Non-SBFD symbols’ may also be referred to as ‘legacy ROs’ and ‘SBFD symbols’ may be referred to ‘SBFD ROs’ or ‘additional ROs’. The terms non-SBFD and UL / F may be used interchangeably.

[0098] In some embodiments, the first and second PRACH preamble format may be either the same or different preamble formats, according to a configuration or specification.

[0099] In some embodiments, the first and second RACH configurations may be either the same or different RACH configurations. If they are the same RACH configuration, still a separate power control configuration may be provided.

[0100] In some embodiments, in determining the second transmit power, a preamble power ramping counter may either be reset, maintained (unchanged) or incremented (by 1). The behavior may further be controlled by a configuration or specification.

[0101] In some embodiments, the UE 22 may use a specified mapping between non-SBFD and SBFD PRACH preambles taking into account, e.g., configured PRACH target reception powers (PPRACH or PREAMBLE RECEIVED TARGET POWER) and / or asignaled preamble received reference target power (Pref or preambleReceivedTargetPower) and the PRACH preamble lengths. In particular, the relation between a non-SBFD transmit power, PPRACH, non-SBFD, transmitted in Nnon-SBFD non-SBFD symbols associated with a preamble received reference target power (Pref, non-SBFD and SBFD transmit power, PPRACH, SBFD , transmitted in NSBFD SBFD symbols associated with a preamble received reference target power Pref, SBFD may be expressed as follows:

[0102] n n ^ref,SBFD

[0103] PpRACH, SBFD — PpRACH, non-SBFD n

[0104] ref, non-SBFD

[0105] where it is assumed that a difference in preamble length is reflected in the reference preamble received reference target power, Pref. In some embodiments, the UE 22 is configured (through RRC or by specification) to only use one symbol type throughout a whole RACH procedure. In some embodiments, the UE 22 is configured to use only one PRACH preamble format throughout a whole RACH procedure. In one of the embodiments, the UE 22 switches between different symbol types or different RO types when the UE 22 has performed PRACH preamble / Msgl transmissions using the same type of RACH resources (e.g., same symbol type or same RO type) up to a configured number of times, in the same RACH procedure. When a switch / fallback event occurs, the UE 22 continues transmitting PRACH preamble / Msgl in the same RACH procedure.

[0106] For the transmission attempts associated with the same type (i.e., same symbol type or same RO type), the UE 22 determines the transmission power for each transmission attempt according to the same set of transmission power control settings (Q.g.,preambleReceivedTargetPower, power ramp step). When the UE 22 switches to another type (i.e., another symbol type or another RO type) in the same RACH procedure, the UE 22 applies the other set of power control settings associated with the other symbol type or RO type to determine transmission power for subsequent transmission attempts. As an additional embodiment, the UE 22 applies one of the below options to maintain the counter for power ramping for each symbol type or RO type:

[0107] Option 1: different counters are maintained for different symbol types or RO types.

[0108] In this option, the UE 22 updates the corresponding counter for each transmission attempt according to the symbol type or the RO type of the RACH resources which the UE 22 has applied for the transmission attempt. Different counters associated with different symbol types or RO types, are maintained independently without affecting each other. For each transmission attempt associated with a symbol type or a RO type, the UE 22considers the counter associated with the same symbol type or RO type to determine the transmission power for the transmission attempt.

[0109] Option 2: same counter is maintained for all (both) symbols types or RO types. In this option, the UE 22 updates the counter for each transmission attempt regardless of its associated symbol type or RO type. When a fallback / switch between symbol types or RO types occurs, the UE 22 resets the counter to be zero. This is based on an assumption that the UE 22 will only trigger a switch or fallback when the UE 22 has applied transmission attempts using the RACH resources of the same symbol type or RO type, up to a configured number of times, while the UE 22 cannot successfully complete the RACH procedure. In one option, in case the UE 22 uses a specified mapping between non-SBFD and SBFD PRACH preambles as described above, the UE 22 does not reset the counter.

[0110] In some embodiments the determination on whether to reset the counter is done by Layer 1 (or the physical layer) and higher layers are notified of the outcome. In another variant, the determination is done by higher layers.

[0111] In some embodiments, the UE 22 declares a RACH problem / failure when the UE 22 has performed preamble transmissions or Msgl transmissions for up to a configured maximum number of times in the same RACH procedure. However, the UE 22 cannot complete the RACH procedure successfully.

[0112] In some embodiments, the UE 22 only counts / considers the preamble transmission attempts or Msgl transmission attempts according to a configured symbol type or RO type (e.g., may be referred to as the reference symbol type or the reference RO type) when declaring the RACH problem or failure.

[0113] In some embodiments, the UE 22 counts / considers all the preamble transmission attempts or Msgl transmission attempts regardless of symbol type or RO type applied in the RACH procedure when declaring the RACH problem or failure. This also means that one common maximum number of RACH preamble / Msgl transmission attempts is applied for all symbol types or RO types.

[0114] In some embodiments, the UE 22 counts / considers the preamble transmission attempts or Msgl transmission attempts separately for different symbol type or RO types in the RACH procedure when declaring the RACH problem or failure. This also means that different maximum numbers / thresholds of RACH preamble / Msgl transmission attempts may be applied for different symbol types or RO types. Thus, the declared RACH problem / failure may also be associated with a specific symbol type or RO type.In some embodiments, the UE 22 will base subsequent preamble received target powers on a first selected preamble received target power.

[0115] In some embodiments, the UE 22 will base its present preamble received target powers on the selected symbol or RO type.

[0116] In some embodiments, MAC layer provides the symbol or RO type for the physical layer to select which PCMAX parameter to use, legacy / non-SBFD or SBFD.

[0117] In some embodiments, if different PCMAX are configured for the different (symbol or RO) types, and the UE’s power ramping reaches the PCMAX limit for one type, it may change to the other type if PCMAX is not reached for that type for the same power ramping iteration. This may further be conditioned on the UE 22 using the same preamble format for the two types.

[0118] Some examples may include one or more of the following:

[0119] Example 1. A method in a user equipment (UE) for transmitting PRACH to a network node 16 in a cell configured with SBFD and either a single or dual RACH configuration, the method comprising:

[0120] receiving a single or dual PRACH configurations;

[0121] transmitting the first PRACH preamble according to a first RACH configuration with a first transmit power in a first symbol type;

[0122] upon failure to detect a random access response, determining to transmit a second PRACH preamble according to a second RACH configuration with a second transmit power; and / or

[0123] transmitting the second PRACH preamble with a second transmit power in a second symbol type.

[0124] Example 2. Example 1 and where the first and second symbol types are either:

[0125] UL / F and UL / F, respectively;

[0126] SBFD and SBFD, respectively;

[0127] UL / F and SBFD, respectively; and / or

[0128] SBFD and UL / F, respectively.

[0129] Example 3. Examples 1 and 2 and where the first and second PRACH preambles are either:

[0130] the same preamble format, or Option 1; and / or

[0131] different preamble formats or Option 2.

[0132] Example 4. Examples 1-3 and where the first and second RACH configurations are either:the same RACH configuration; and / or

[0133] different RACH configurations.

[0134] Example 5. Examples 2-4 and when determining the second transmit power, the preamble power ramping counter PREAMBLE POWER RAMPING COUNTER) is either:

[0135] reset;

[0136] maintained; and / or

[0137] incremented.

[0138] Example 6. Examples 1-5, and where the transmit power in SBFD symbols is derived from the legacy transmit power in non-SBFD symbols taking into account one or more of the following differences:

[0139] differences in SINR between the two symbol types; and / or differences in PRACH preamble duration between the two symbol types. FIG. 11 A is a flowchart of an example method in an SBFD aware UE according to embodiments of the present disclosure. The UE is configured to communicate with a network node. The method comprises:

[0140] • SI: receiving a random access channel, RACH, configuration from the network node;

[0141] • S3: transmitting a first physical RACH, PRACH, preamble, according to the received RACH configuration, in a first PRACH occasion comprising a first symbol type, a symbol type being either non-SBFD symbol or SBFD symbol; and

[0142] • S4: when reception of a random access response, RAR, related to the first PRACH preamble is unsuccessful, transmitting a second PRACH preamble, according to the received RACH configuration, in a second PRACH occasion comprising a second symbol type different from the first symbol type.

[0143] In one example embodiment referred to as example embodiment E, the first symbol type may be a non-SBFD-symbol, and the second symbol type may be an SBFD symbol.

[0144] In embodiments, the method may further comprise:

[0145] • S2: receiving a configuration parameter from the network node, the parameter indicating a maximum number of PRACH preamble transmission attempts in PRACH occasions comprising the first symbol type before switching to PRACH occasions comprising the second symbol type. The second PRACH preamble istransmited when a number of previous PRACH preamble transmission atempts in PRACH occasions comprising the first symbol type within a same random access procedure has reached the value of the parameter. In embodiments, the configuration parameter is comprised in the received RACH configuration.

[0146] In the example embodiment E, this would mean that the UE switches from PRACH preamble transmission atempts in PRACH occasions comprising non-SBFD symbols to transmission of the second PRACH preamble in a PRACH occasion comprising SBFD symbols, when the number of previous PRACH preamble transmission attempts in PRACH occasions comprising the non-SBFD symbols has reached the maximum number indicated by the value of the received configuration parameter, without having successfully received any RAR.

[0147] The UE 22 thus switches between different symbol types or different RO types when the UE 22 has performed PRACH preamble / Msgl transmissions using the same type of RACH resources (e.g., same symbol type or same RO type) up to a configured number of times, in the same RACH procedure. After a switch event occurs, the UE 22 continues transmitting PRACH preamble / Msgl in the same RACH procedure.

[0148] The method may in embodiments further comprise applying a first transmit power for the PRACH preamble transmission in the first PRACH occasion based on the RACH configuration, incrementing a preamble power ramping counter when the reception of the RAR is unsuccessful, and applying a second transmit power for the PRACH preamble transmission in the second PRACH occasion based on the incremented preamble power ramping counter and the RACH configuration.

[0149] In embodiments, the RACH configuration comprises a separate set of power control parameter values for the first and second PRACH occasions respectively.

[0150] For the transmission attempts associated with the same type (i. e. , same symbol type or same RO type), the UE 22 determines the transmission power for each transmission attempt according to a first same set of transmission power control setings (e.g., preambleReceivedTargetPower, power ramp step). When the UE 22 switches to another type (i.e., another symbol type or another RO type) in the same RACH procedure, the UE 22 applies another separate set of power control setings associated with the other symbol type or RO type to determine transmission power for subsequent transmission attempts.

[0151] In embodiments, the RACH configuration comprises different preamble formats for the first and second PRACH occasions respectively.In embodiments, the RACH configuration comprises separate RACH configurations for the first and second PRACH occasions respectively, thus corresponding to the dual PRACH configurations disclosed above.

[0152] In embodiments, the first and the second PRACH preambles are transmitted within a same random access procedure.

[0153] In embodiments, the method further comprises indicating a random access problem to the network node when a total number of PRACH preamble transmissions attempts in PRACH occasions of both first and second symbol types has reached a configured maximum number. As described above, the UE 22 declares a RACH problem / failure when the UE 22 has performed preamble transmissions or Msgl transmissions for up to a configured maximum number of times in the same RACH procedure.

[0154] FIG. 1 IB is a flowchart of an example process in a network node according to embodiments of the present disclosure. The network node is configured to communicate with an SBFD aware UE configured to transmit a first PRACH preamble in a first PRACH occasion comprising a first symbol type, a symbol type being either non-SBFD symbol or SBFD symbol, and to transmit a second PRACH preamble in a second PRACH occasion comprising a second symbol type different from the first symbol type when a RAR related to the first PRACH preamble is unsuccessful. The method comprises:

[0155] • S5: transmitting a random access channel, RACH, configuration to the UE, thereby configuring the UE to transmit the first and the second PRACH preamble.

[0156] In embodiments, the method may further comprise:

[0157] • S6: transmitting a configuration parameter to the UE, the parameter indicating a maximum number of PRACH preamble transmission attempts in PRACH occasions comprising the first symbol type before switching to PRACH occasions comprising the second symbol type, thereby configuring the UE to transmit the second PRACH preamble when a number of previous PRACH preamble transmission attempts in PRACH occasions comprising the first symbol type within a same random access procedure has reached the value of the parameter.

[0158] In embodiments, the RACH configuration comprises a separate set of power control parameter values for the first and second PRACH occasions respectively, therebyconfiguring the UE to use the separate sets for determining a transmit power for the PRACH preamble transmission in the first and the second PRACH occasions respectively. The RACH configuration may in embodiments comprise different preamble formats for the first and second PRACH occasions respectively, thereby configuring the UE to use different preamble formats for the PRACH preamble transmission in the first and the second PRACH occasions respectively. Further, the RACH configuration may comprise separate RACH configurations for the first and second PRACH occasions respectively, thereby configuring the UE to use the separate configurations for the PRACH preamble transmission in the first and the second PRACH occasions respectively.

[0159] In embodiments, the method may further comprise receiving an indication of a random access problem from the UE indicating that a total number of PRACH preamble transmissions attempts in PRACH occasions of both first and second symbol types has reached a configured maximum number.

[0160] FIG. 9 is a block diagram illustrating the network node 16 and the SBFD aware UE 22 configured to perform the example processes described with reference to figures HA and 11B.

[0161] The SBFD aware UE 22 is configured to communicate with a network node 16, and the UE 22 is further configured to receive a RACH configuration from the network node; transmit a first PRACH preamble, according to the received RACH configuration, in a first PRACH occasion comprising a first symbol type, a symbol type being either non-SBFD symbol or SBFD symbol; and when reception of a random access response, RAR, related to the first PRACH preamble is unsuccessful, transmit a second PRACH preamble, according to the received RACH configuration, in a second PRACH occasion comprising a second symbol type different from the first symbol type.

[0162] The UE 22 may be further configured to receive a configuration parameter from the network node, the parameter indicating a maximum number of PRACH preamble transmission attempts in PRACH occasions comprising the first symbol type before switching to PRACH occasions comprising the second symbol type, wherein the second PRACH preamble is transmitted when a number of previous PRACH preamble transmission attempts in PRACH occasions comprising the first symbol type within a same random access procedure has reached the value of the parameter.

[0163] The UE 22 may be further configured to apply a first transmit power for the PRACH preamble transmission in the first PRACH occasion based on the RACHconfiguration, increment a preamble power ramping counter when the reception of the RAR is unsuccessful, and apply a second transmit power for the PRACH preamble transmission in the second PRACH occasion based on the incremented preamble power ramping counter and the RACH configuration.

[0164] In embodiments, the RACH configuration comprises a separate set of power control parameter values for the first and second PRACH occasions respectively. The RACH configuration may comprise different preamble formats for the first and second PRACH occasions respectively. The RACH configuration may comprises separate RACH configurations for the first and second PRACH occasions respectively.

[0165] In embodiments, the first and the second PRACH preambles are transmitted within a same random access procedure. The UE 22 may be further configured to indicate a random access problem to the network node when a total number of PRACH preamble transmissions attempts in PRACH occasions of both first and second symbol types has reached a configured maximum number.

[0166] The network node 16 is configured to communicate with an SBFD aware UE configured to transmit a first PRACH preamble in a first PRACH occasion comprising a first symbol type, a symbol type being either non-SBFD symbol or SBFD symbol, and to transmit a second PRACH preamble in a second PRACH occasion comprising a second symbol type different from the first symbol type when a RAR related to the first PRACH preamble is unsuccessful. The network node is configured to transmit a RACH configuration to the UE, thereby configuring the UE to transmit the first and the second PRACH preamble.

[0167] The network node 16 may be further configured to transmit a configuration parameter to the UE, the parameter indicating a maximum number of PRACH preamble transmission attempts in PRACH occasions comprising the first symbol type before switching to PRACH occasions comprising the second symbol type, thereby configuring the UE to transmit the second PRACH preamble when a number of previous PRACH preamble transmission attempts in PRACH occasions comprising the first symbol type within a same random access procedure has reached the value of the parameter.

[0168] In embodiments, the RACH configuration comprises a separate set of power control parameter values for the first and second PRACH occasions respectively, thereby configuring the UE to use the separate sets for determining a transmit power for the PRACH preamble transmission in the first and the second PRACH occasionsrespectively. The RACH configuration may comprise different preamble formats for the first and second PRACH occasions respectively, thereby configuring the UE to use different preamble formats for the PRACH preamble transmission in the first and the second PRACH occasions respectively. The RACH configuration may comprise separate RACH configurations for the first and second PRACH occasions respectively, thereby configuring the UE to use the separate configurations for the PRACH preamble transmission in the first and the second PRACH occasions respectively.

[0169] In embodiments, the network node 16 is further configured to receive an indication of a random access problem from the UE indicating that a total number of PRACH preamble transmissions attempts in PRACH occasions of both first and second symbol types has reached a configured maximum number.

[0170] As illustrated in Fig. 9, the UE 22 configured to communicate with a network node, comprises processing circuitry 50 and a memory 54, the processing circuitry configured to receive a RACH configuration from the network node; transmit a first PRACH preamble, according to the received RACH configuration, in a first PRACH occasion comprising a first symbol type, a symbol type being either non-SBFD symbol or SBFD symbol; and when reception of a random access response, RAR, related to the first PRACH preamble is unsuccessful, transmit a second PRACH preamble, according to the received RACH configuration, in a second PRACH occasion comprising a second symbol type different from the first symbol type. The processing circuitry 50 may be further configured to perform the example method in the UE described above with reference to the flowchart in FIG. 11 A.

[0171] Further, as illustrated in Fig. 9, the network node 16 configured to communicate with the SBFD aware UE configured to transmit a first PRACH preamble in a first PRACH occasion comprising a first symbol type, a symbol type being either non-SBFD symbol or SBFD symbol, and to transmit a second PRACH preamble in a second PRACH occasion comprising a second symbol type different from the first symbol type when a RAR related to the first PRACH preamble is unsuccessful, comprises processing circuitry 36 and a memory 40. The processing circuitry 36 is configured to transmit a RACH configuration to the UE, thereby configuring the UE to transmit the first and the second PRACH preamble.

[0172] The processing circuitry 36 may be further configured to perform the example method in the network node described above with reference to the flowchart in FIG.

[0173] 11B.FIG. 12A is a flowchart of an example process in a network node 16 for power ramping in subband full duplex (SBFD) physical random access channels (PRACH). One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the configuration unit 24), processor 38, and / or radio interface 30. Network node 16 such as via processing circuitry 36 and / or processor 38 and / or radio interface 30 is configured to configure the UE with a first preamble receive target power for a first subband full duplex (SBFD) physical random access channel (PRACH) symbol type and a second preamble receive target power for a second non-SBFD symbol type (Block S10). The process also includes configuring the UE with one of a single PRACH configuration and a dual PRACH configuration, at least one of the single and dual PRACH configurations being an SBFD PRACH configuration (Block SI 2).

[0174] In some embodiments, the dual PRACH configuration is a same PRACH configuration as the single PRACH configuration. In some embodiments, the method includes receiving a first PRACH preamble according to the single PRACH configuration and receive a second PRACH preamble according to the dual PRACH configuration. In some embodiments, the first PRACH preamble is of the SBFD symbol type and the second PRACH preamble is of the non-SBFD symbol type. In some embodiments, a first format of the first PRACH preamble is different from a second format of the second PRACH format.

[0175] FIG. 12B is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 50 (including the PRACH unit 26), processor 52, and / or radio interface 46. User equipment 22 such as via processing circuitry 50 and / or processor 52 and / or radio interface 46 is configured to receive one of a single random access channel (PRACH) configuration and a dual PRACH configuration (Block S14). The process includes transmitting a first PRACH preamble according to the received PRACH configuration with a first transmit power in a first symbol type (Block SI 6). The process also includes, when a random access response (RAR) is not detected, transmitting a second PRACH preamble according to the received PRACH configuration with a second transmit power in a second symbol type (Block SI 8).

[0176] In some embodiments, a first one of the first and second symbol types is a subband full duplex (SBFD) symbol type and a second one of the first and second symbol types is anon-SBFD symbol type. In some embodiments, the first symbol type is a same symbol type as the second symbol type. In some embodiments, a first format of the first PRACH preamble is different from a second format of the second PRACH format. In some embodiments, a first PRACH configuration of the received dual PRACH configuration is a same PRACH configuration as a second PRACH configuration of the received dual PRACH configuration. In some embodiments, the method includes determining the second transmit power during a duration of a preamble power ramping counter. In some embodiments, the preamble power ramping counter is one of reset, maintained or incremented when determining the second transmit power. In some embodiments, a transmit power for subband full duplex (SBFD) symbol types is determined based at least in part on a transmit power for non-SBFD symbol types. In some embodiments, the transmit power for SBFD symbol types is determined based at least in part on a difference in signal to noise plus interference ratio (SINR) for the first and second symbol types. In some embodiments, the transmit power for SBFD symbol types is determined based at least in part on a difference in PRACH preamble duration between the first and second symbol types.

[0177] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that may be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0178] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, may be implemented by computer program instructions. These computer program instructionsmay be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0179] These computer program instructions may also be stored in a computer readable memory or storage medium that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0180] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0181] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0182] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may bemade to an external computer (for example, through the Internet using an Internet Service Provider).

[0183] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments may be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0184] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings.

[0185] List of other exemplary embodiments:

[0186] Embodiment Al . A network node configured to communicate with a user equipment (UE), the network node configured to, and / or comprising a radio interface and / or comprising processing circuitry configured to:

[0187] configure the UE with a first preamble receive target power for a first subband full duplex (SBFD) physical random access channel (PRACH) symbol type and a second preamble receive target power for a second non-SBFD symbol type; and

[0188] configure the UE with one of a single PRACH configuration and a dual PRACH configuration, at least one of the single and dual PRACH configurations being an SBFD PRACH configuration.

[0189] Embodiment A2. The network node of Embodiment Al, wherein the dual PRACH configuration is a same PRACH configuration as the single PRACH configuration.

[0190] Embodiment A3. The network node of any of Embodiments Al and A2, wherein the network node, radio interface and / or processing circuitry are configured to receive a first PRACH preamble according to the single PRACH configuration and receive a second PRACH preamble according to the dual PRACH configuration.Embodiment A4. The network node of Embodiment A3, wherein the first PRACH preamble is of the SBFD symbol type and the second PRACH preamble is of the non-SBFD symbol type.

[0191] Embodiment A5. The network node of any of Embodiments A3 and A4, wherein a first format of the first PRACH preamble is different from a second format of the second PRACH format.

[0192] Embodiment Bl. A method implemented in a network node that is configured to communicate with a user equipment, the method comprising:

[0193] configuring the UE with a first preamble receive target power for a first subband full duplex (SBFD) physical random access channel (PRACH) symbol type and a second preamble receive target power for a second non-SBFD symbol type; and

[0194] configuring the UE with one of a single PRACH configuration and a dual PRACH configuration, at least one of the single and dual PRACH configurations being an SBFD PRACH configuration.

[0195] Embodiment B2. The method of Embodiment Bl, wherein the dual PRACH configuration is a same PRACH configuration as the single PRACH configuration.

[0196] Embodiment B3. The method of any of Embodiments Bl and B2, further comprising receiving a first PRACH preamble according to the single PRACH configuration and receive a second PRACH preamble according to the dual PRACH configuration.

[0197] Embodiment B4. The method of Embodiment B3, wherein the first PRACH preamble is of the SBFD symbol type and the second PRACH preamble is of the non-SBFD symbol type.

[0198] Embodiment B5. The method of any of Embodiments B3 and B4, wherein a first format of the first PRACH preamble is different from a second format of the second PRACH format.

[0199] Embodiment Cl. A user equipment (UE) configured to communicate with a network node, the UE configured to, and / or comprising a radio interface and / or processing circuitry configured to:

[0200] receive one of a single random access channel (PRACH) configuration and a dual PRACH configuration;

[0201] transmit a first PRACH preamble according to the received PRACH configuration with a first transmit power in a first symbol type; andwhen a random access response (RAR) is not detected, transmit a second PRACH preamble according to the received PRACH configuration with a second transmit power in a second symbol type.

[0202] Embodiment C2. The UE of Embodiment Cl, wherein a first one of the first and second symbol types is a subband full duplex (SBFD) symbol type and a second one of the first and second symbol types is a non-SBFD symbol type.

[0203] Embodiment C3. The UE of Embodiment C2, wherein the first symbol type is a same symbol type as the second symbol type.

[0204] Embodiment C4. The UE of any of Embodiments C1-C3, wherein a first format of the first PRACH preamble is different from a second format of the second PRACH format.

[0205] Embodiment C5. The UE of any of Embodiments C1-C4, wherein a first PRACH configuration of the received dual PRACH configuration is a same PRACH configuration as a second PRACH configuration of the received dual PRACH configuration.

[0206] Embodiment C6. The UE of any of Embodiments C1-C5, wherein the UE, radio interface and / or processing circuitry are configured to determine the second transmit power during a duration of a preamble power ramping counter.

[0207] Embodiment C7. The UE of Embodiment C6, wherein the preamble power ramping counter is one of reset, maintained or incremented when determining the second transmit power.

[0208] Embodiment C8. The UE of any of Embodiments C1-C7, wherein a transmit power for subband full duplex (SBFD) symbol types is determined based at least in part on a transmit power for non-SBFD symbol types.

[0209] Embodiment C9. The UE of Embodiment C8, wherein the transmit power for SBFD symbol types is determined based at least in part on a difference in signal to noise plus interference ratio (SINR) for the first and second symbol types.

[0210] Embodiment CIO. The UE of Embodiment C8, wherein the transmit power for SBFD symbol types is determined based at least in part on a difference in PRACH preamble duration between the first and second symbol types.

[0211] Embodiment DI. A method implemented in a user equipment (UE) that is configured to communicate with a network node, the method comprising:

[0212] receiving one of a single random access channel (PRACH) configuration and a dual PRACH configuration;transmiting a first PRACH preamble according to the received PRACH configuration with a first transmit power in a first symbol type; and

[0213] when a random access response (RAR) is not detected, transmitting a second PRACH preamble according to the received PRACH configuration with a second transmit power in a second symbol type.

[0214] Embodiment D2. The method of Embodiment D 1 , wherein a first one of the first and second symbol types is a subband full duplex (SBFD) symbol type and a second one of the first and second symbol types is a non-SBFD symbol type.

[0215] Embodiment D3. The method of Embodiment D2, wherein the first symbol type is a same symbol type as the second symbol type.

[0216] Embodiment D4. The method of any of Embodiments D1-D3, wherein a first format of the first PRACH preamble is different from a second format of the second PRACH format.

[0217] Embodiment D5. The method of any of Embodiments D1-D4, wherein a first PRACH configuration of the received dual PRACH configuration is a same PRACH configuration as a second PRACH configuration of the received dual PRACH configuration.

[0218] Embodiment D6. The method of any of Embodiments D1-D5, further comprising determining the second transmit power during a duration of a preamble power ramping counter.

[0219] Embodiment D7. The method of Embodiment D6, wherein the preamble power ramping counter is one of reset, maintained or incremented when determining the second transmit power.

[0220] Embodiment D8. The method of any of Embodiments D1-D7, wherein a transmit power for subband full duplex (SBFD) symbol types is determined based at least in part on a transmit power for non-SBFD symbol types.

[0221] Embodiment D9. The method of Embodiment D8, wherein the transmit power for SBFD symbol types is determined based at least in part on a difference in signal to noise plus interference ratio (SINR) for the first and second symbol types.

[0222] Embodiment DIO. The method of Embodiment D8, wherein the transmit power for SBFD symbol types is determined based at least in part on a difference in PRACH preamble duration between the first and second symbol types.

Claims

1. CLAIMS1. A method implemented in a sub band full duplex, SBFD, aware user equipment, UE, (22) configured to communicate with a network node (16), the method comprising:receiving (SI) a random access channel, RACH, configuration from the network node;transmitting (S3) a first physical RACH, PRACH, preamble, according to the received RACH configuration, in a first PRACH occasion comprising a first symbol type, a symbol type being either non-SBFD symbol or SBFD symbol; andwhen reception of a random access response, RAR, related to the first PRACH preamble is unsuccessful, transmitting (S4) a second PRACH preamble, according to the received RACH configuration, in a second PRACH occasion comprising a second symbol type different from the first symbol type.

2. The method according to claim 1, further comprising receiving (S2) a configuration parameter from the network node, the parameter indicating a maximum number of PRACH preamble transmission attempts in PRACH occasions comprising the first symbol type before switching to PRACH occasions comprising the second symbol type, wherein the second PRACH preamble is transmitted when a number of previous PRACH preamble transmission attempts in PRACH occasions comprising the first symbol type within a same random access procedure has reached the value of the parameter.

3. The method according to any of the preceding claims, further comprising:applying a first transmit power for the PRACH preamble transmission in the first PRACH occasion based on the RACH configuration,incrementing a preamble power ramping counter when the reception of the RAR is unsuccessful, andapplying a second transmit power for the PRACH preamble transmission in the second PRACH occasion based on the incremented preamble power ramping counter and the RACH configuration.

4. The method according to any of the preceding claims, wherein the RACH configuration comprises a separate set of power control parameter values for the first and second PRACH occasions respectively.

5. The method according to any of the preceding claims, wherein the RACH configuration comprises different preamble formats for the first and second PRACH occasions respectively.

6. The method according to any of the preceding claims, wherein the RACH configuration comprises separate RACH configurations for the first and second PRACH occasions respectively.

7. The method according to any of the preceding claims, wherein the first and the second PRACH preambles are transmitted within a same random access procedure.

8. The method according to any of the preceding claims, further comprising:indicating a random access problem to the network node when a total number of PRACH preamble transmissions attempts in PRACH occasions of both first and second symbol types has reached a configured maximum number.

9. A method implemented in a network node (16) configured to communicate with a sub band full duplex, SBFD, aware user equipment, UE, (22) configured to transmit a first physical RACH, PRACH, preamble in a first PRACH occasion comprising a first symbol type, a symbol type being either non-SBFD symbol or SBFD symbol, and to transmit a second PRACH preamble in a second PRACH occasion comprising a second symbol type different from the first symbol type when a random access response, RAR, related to the first PRACH preamble is unsuccessful, the method comprising:transmitting (S5) a random access channel, RACH, configuration to the UE, thereby configuring the UE to transmit the first and the second PRACH preamble.

10. The method according to claim 9, further comprising transmitting (S6) a configuration parameter to the UE, the parameter indicating a maximum number of PRACH preamble transmission attempts in PRACH occasions comprising the first symbol type before switching to PRACH occasions comprising the second symbol type, thereby configuring the UE to transmit the second PRACH preamble when a number of previous PRACH preamble transmission attempts in PRACH occasions comprising the first symbol type within a same random access procedure has reached the value of the parameter.

11. The method according to any of claims 9-10, wherein the RACH configuration comprises a separate set of power control parameter values for the first and second PRACH occasions respectively, thereby configuring the UE to use the separate sets for determining a transmit power for the PRACH preamble transmission in the first and the second PRACH occasions respectively.

12. The method according to any of claims 9-11, wherein the RACH configuration comprises different preamble formats for the first and second PRACH occasions respectively, thereby configuring the UE to use different preamble formats for the PRACH preamble transmission in the first and the second PRACH occasions respectively.

13. The method according to any of claims 9-12, wherein the RACH configuration comprises separate RACH configurations for the first and second PRACH occasions respectively, thereby configuring the UE to use the separate configurations for the PRACH preamble transmission in the first and the second PRACH occasions respectively.

14. The method according to any of claims 9-13, further comprising:receiving an indication of a random access problem from the UE indicating that a total number of PRACH preamble transmissions attempts in PRACH occasions of both first and second symbol types has reached a configured maximum number.

15. A sub band full duplex, SBFD, aware user equipment, UE, (22) configured to communicate with a network node (16), the UE being further configured to:receive a random access channel, RACH, configuration from the network node; transmit a first physical RACH, PRACH, preamble, according to the received RACH configuration, in a first PRACH occasion comprising a first symbol type, a symbol type being either non-SBFD symbol or SBFD symbol; andwhen reception of a random access response, RAR, related to the first PRACH preamble is unsuccessful, transmit a second PRACH preamble, according to the received RACH configuration, in a second PRACH occasion comprising a second symbol type different from the first symbol type.

16. The UE according to claim 15, further configured to receive a configuration parameter from the network node, the parameter indicating a maximum number ofPRACH preamble transmission attempts in PRACH occasions comprising the first symbol type before switching to PRACH occasions comprising the second symbol type, wherein the second PRACH preamble is transmitted when a number of previous PRACH preamble transmission attempts in PRACH occasions comprising the first symbol type within a same random access procedure has reached the value of the parameter.

17. The UE according to any of claims 15-16, further configured to:apply a first transmit power for the PRACH preamble transmission in the first PRACH occasion based on the RACH configuration,increment a preamble power ramping counter when the reception of the RAR is unsuccessful, andapply a second transmit power for the PRACH preamble transmission in the second PRACH occasion based on the incremented preamble power ramping counter and the RACH configuration.

18. The UE according to any of claims 15-17, wherein the RACH configuration comprises a separate set of power control parameter values for the first and second PRACH occasions respectively.

19. The UE according to any of claims 15-18, wherein the RACH configuration comprises different preamble formats for the first and second PRACH occasions respectively.

20. The UE according to any of claims 15-19, wherein the RACH configuration comprises separate RACH configurations for the first and second PRACH occasions respectively.

21. The UE according to any of claims 15-20, wherein the first and the second PRACH preambles are transmitted within a same random access procedure.

22. The UE according to any of claims 15-21, further configured to:indicate a random access problem to the network node when a total number of PRACH preamble transmissions attempts in PRACH occasions of both first and second symbol types has reached a configured maximum number.

23. A network node (16) configured to communicate with a sub band full duplex, SBFD, aware user equipment, UE, (22) configured to transmit a first physical RACH, PRACH, preamble in a first PRACH occasion comprising a first symbol type, a symbol type being either non-SBFD symbol or SBFD symbol, and to transmit a second PRACH preamble in a second PRACH occasion comprising a second symbol type different from the first symbol type when a random access response, RAR, related to the first PRACH preamble is unsuccessful, the network node configured to:transmit a random access channel, RACH, configuration to the UE, thereby configuring the UE to transmit the first and the second PRACH preamble.

24. The network node according to claim 23, further configured to transmit a configuration parameter to the UE, the parameter indicating a maximum number of PRACH preamble transmission attempts in PRACH occasions comprising the first symbol type before switching to PRACH occasions comprising the second symbol type, thereby configuring the UE to transmit the second PRACH preamble when a number of previous PRACH preamble transmission attempts in PRACH occasions comprising the first symbol type within a same random access procedure has reached the value of the parameter.

25. The network node according to any of claims 23-24, wherein the RACH configuration comprises a separate set of power control parameter values for the first and second PRACH occasions respectively, thereby configuring the UE to use the separate sets for determining a transmit power for the PRACH preamble transmission in the first and the second PRACH occasions respectively.

26. The network node according to any of claims 23-25, wherein the RACH configuration comprises different preamble formats for the first and second PRACH occasions respectively, thereby configuring the UE to use different preamble formats for the PRACH preamble transmission in the first and the second PRACH occasions respectively.

27. The network node according to any of claims 23-26, wherein the RACH configuration comprises separate RACH configurations for the first and second PRACH occasions respectively, thereby configuring the UE to use the separate configurations forthe PRACH preamble transmission in the first and the second PRACH occasions respectively.

28. The network node according to any of claims 23-27, further configured to:receive an indication of a random access problem from the UE indicating that a total number of PRACH preamble transmissions attempts in PRACH occasions of both first and second symbol types has reached a configured maximum number.

29. A sub band full duplex, SBFD, aware user equipment, UE, configured to communicate with a network node, the UE comprising processing circuitry and a memory, the processing circuitry configured to:receive a random access channel, RACH, configuration from the network node; transmit a first physical RACH, PRACH, preamble, according to the received RACH configuration, in a first PRACH occasion comprising a first symbol type, a symbol type being either non-SBFD symbol or SBFD symbol; andwhen reception of a random access response, RAR, related to the first PRACH preamble is unsuccessful, transmit a second PRACH preamble, according to the received RACH configuration, in a second PRACH occasion comprising a second symbol type different from the first symbol type.

30. The UE according to claim 29, wherein the processing circuitry is further configured to perform the methods of any of claims 2-8.

31. A network node configured to communicate with a sub band full duplex, SBFD, aware user equipment, UE, configured to transmit a first physical RACH, PRACH, preamble in a first PRACH occasion comprising a first symbol type, a symbol type being either non-SBFD symbol or SBFD symbol, and to transmit a second PRACH preamble in a second PRACH occasion comprising a second symbol type different from the first symbol type when a random access response, RAR, related to the first PRACH preamble is unsuccessful, the network node comprising processing circuitry () and a memory (), the processing circuitry configured to:transmit a random access channel, RACH, configuration to the UE, thereby configuring the UE to transmit the first and the second PRACH preamble.

32. The network node according to claim 31, wherein the processing circuitry is further configured to perform the methods of any of claims 10-14.

Images