CN117813902A

CN117813902A - Method and device for executing random access based on full duplex system in wireless communication system

Info

Publication number: CN117813902A
Application number: CN202280053679.3A
Authority: CN
Inventors: M·鲁道夫; A·帕帕萨克拉里奥; C·科佐
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2021-08-04
Filing date: 2022-08-03
Publication date: 2024-04-02

Abstract

The present disclosure relates to 5G or 6G communication systems for supporting higher data transmission rates. In the present disclosure, an apparatus and method for a random access procedure for full duplex operation are provided. A method for a user equipment comprising: first information for a first parameter of a first Random Access Channel (RACH) configuration associated with a first subset of time slots from a set of time slots on a cell and second information for a second parameter of a second RACH configuration associated with a second subset of time slots from the set of time slots on the cell are received. The method further comprises the steps of: determining a RACH configuration for Physical Random Access Channel (PRACH) transmission in a time slot on the cell among the first RACH configuration and the second RACH configuration based on whether the time slot is from the first subset of time slots or the second subset of time slots, and transmitting the PRACH in the time slot on the cell based on the determined RACH configuration.

Description

Method and device for executing random access based on full duplex system in wireless communication system

Technical Field

The present disclosure relates generally to wireless communication systems (or mobile communication systems), and more particularly, to random access procedures for full duplex operation (or full duplex systems or full duplex radios).

Background

The 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services, and can be implemented not only in a "below 6 GHz" band such as 3.5GHz, but also in a "above 6 GHz" band called millimeter wave (mmWave) including 28GHz and 39 GHz. Further, in order to achieve a transmission rate 50 times faster than that of the 5G mobile communication technology and an ultra-low latency of one tenth of that of the 5G mobile communication technology, it has been considered to implement the 6G mobile communication technology (referred to as transcendental 5G system) in a terahertz band (e.g., 95GHz to 3THz band).

In the early stages of the development of 5G Mobile communication technology, in order to support services and meet performance requirements related to enhanced Mobile BroadBand (eMBB), ultra-reliable low latency communication (Ultra Reliable Low Latency Communications, URLLC), and large-scale Machine-type communication (emtc), standardization is underway with respect to the following technologies: beamforming and massive MIMO for reducing radio wave path loss and increasing radio wave transmission distance in millimeter waves, supporting dynamic operation of parameter sets (e.g., operating a plurality of subcarrier intervals) and slot formats for effectively utilizing millimeter wave resources, initial access techniques for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods such as LDPC (low density parity check) codes for mass data transmission and polarization codes for highly reliable transmission of control information, L2 preprocessing, and network slicing for providing a dedicated network dedicated to a specific service.

Currently, in view of services that the 5G mobile communication technology will support, discussions are being made about improvement and performance enhancement of the initial 5G mobile communication technology, and physical layer standards have existed about various technologies such as the following: V2X (vehicle versus everything) for assisting driving determination of an autonomous vehicle based on information sent by the vehicle about the position and status of the vehicle and for enhancing user convenience, NR-U (new radio unlicensed) for system operation meeting various regulatory-related requirements in unlicensed bands, NR UE power saving, non-terrestrial network (Non-Terrestrial Network, NTN), which is UE-satellite direct communication for providing coverage in areas where communication with the terrestrial network is unavailable, and positioning.

Further, in terms of air interface architecture/protocols, standardization is underway with respect to various technologies such as: industrial internet of things (Industrial Internet of Things, IIoT) for supporting new services through interworking and convergence with other industries, IAB (integrated access and backhaul) for providing nodes for network service area extension by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional handover and DAPS (dual active protocol stack) handover, and two-step random access (2-step RACH of NR) for simplifying random access procedures. Standardization is also underway in terms of system architecture/services regarding various techniques: a 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (Network Functions Virtualization, NFV) and Software Defined Networking (SDN) technologies, and mobile edge computing (Mobile Edge Computing, MEC) for receiving services based on UE location.

With commercialization of the 5G mobile communication system, exponentially growing connected devices will be connected to the communication network, and thus, it is expected that enhanced functions and performance of the 5G mobile communication system and integrated operation of the connected devices will be necessary. For this reason, new studies related to the following technologies are planned: new researches on augmented Reality (XR) for effectively supporting AR (augmented Reality), VR (virtual Reality), MR (mixed Reality), etc. have been made by using 5G performance improvement and complexity reduction of artificial intelligence (Artificial Intelligence, AI) and Machine Learning (ML), AI service support, meta space service support, and unmanned aerial vehicle communication.

Further, such development of the 5G mobile communication system will be the basis for developing not only new waveforms for providing coverage in the terahertz band of the 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas and massive antennas, metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum) and RIS (reconfigurable intelligent surface), but also full duplex technology for improving frequency efficiency of the 6G mobile communication technology and improving system network, AI-based communication technology for realizing system optimization by utilizing satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end support functions, and next generation distributed computing technology for realizing a service of a complexity degree exceeding the UE operation capability limit by utilizing ultra-high performance communication and computing resources.

Disclosure of Invention

Solution scheme

The present disclosure relates to a random access procedure for full duplex operation in 5G NR.

In one embodiment, a method performed by a User Equipment (UE) is provided. The method comprises the following steps: first information for a first parameter of a first Random Access Channel (RACH) configuration associated with a first subset of time slots from a set of time slots on a cell and second information for a second parameter of a second RACH configuration associated with a second subset of time slots from the set of time slots on the cell are received. The method further comprises the steps of: determining a RACH configuration for Physical Random Access Channel (PRACH) transmission in a time slot on the cell among the first RACH configuration and the second RACH configuration based on whether the time slot is from the first subset of time slots or the second subset of time slots, and transmitting the PRACH in the time slot on the cell based on the determined RACH configuration.

In another embodiment, a User Equipment (UE) is provided. The UE includes a transceiver configured to receive first information for a first parameter of a first Random Access Channel (RACH) configuration associated with a first subset of time slots from a set of time slots on a cell, and second information for a second parameter of a second RACH configuration associated with a second subset of time slots from the set of time slots on the cell. The UE also includes a transceiver operably coupled to the processor. The processor is configured to: a RACH configuration for PRACH transmission in a slot on a cell is determined among the first RA CH configuration and the second RACH configuration based on whether the slot is from a first subset of slots or a second subset of slots. The transceiver is further configured to: based on the determined RACH configuration, the PRACH is transmitted in a time slot on the cell.

In yet another embodiment, a method performed by a Base Station (BS) is provided. The method comprises the following steps: the method includes transmitting first information for a first parameter of a first Random Access Channel (RACH) configuration associated with a first subset of time slots from a set of time slots on a cell and second information for a second parameter of a second RACH configuration associated with a second subset of time slots from the set of time slots on the cell, determining a RACH configuration for reception of a Physical Random Access Channel (PRACH) in the time slots on the cell based on whether the time slots are from the first subset of time slots or the second subset of time slots, and receiving the PRACH in the time slots based on the determined RACH configuration.

In yet another embodiment, a base station is provided. The base station includes a transceiver configured to transmit first information for a first parameter of a first Random Access Channel (RACH) configuration associated with a first subset of time slots from a set of time slots on the cell and second information for a second parameter of a second RACH configuration associated with a second subset of time slots from the set of time slots on the cell. The base station also includes a transceiver operably coupled to the processor. The processor is configured to determine a RACH configuration for reception of a PRAC H in a slot on a cell based on whether the slot is from a first subset of slots or from a second subset of slots. The transceiver is further configured to: based on the determined RACH configuration, the PRACH is received in a slot.

Other technical features may be readily apparent to one skilled in the art from the following figures, descriptions, and claims.

Advantageous effects

According to various embodiments of the present disclosure, a random access procedure may be effectively enhanced according to a full duplex system.

Drawings

For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:

fig. 1 illustrates an example wireless network according to an embodiment of the disclosure;

fig. 2 illustrates an example Base Station (BS) according to an embodiment of the disclosure;

fig. 3 illustrates an example UE in accordance with an embodiment of the present disclosure;

fig. 4 and 5 illustrate example wireless transmit and receive paths according to embodiments of the present disclosure;

fig. 6 illustrates an example diagram of example Physical Random Access Channel (PRACH) time and frequency domain allocations in accordance with an embodiment of the disclosure;

FIG. 7 illustrates an example diagram of an example E/R/R/BI MAC sub-header in accordance with an embodiment of the disclosure;

FIG. 8 illustrates an example diagram of an example E/T/RAPID Media Access Control (MAC) subheader, according to an embodiment of the present disclosure;

fig. 9 illustrates an example diagram of an example MAC Random Access Response (RAR) in accordance with an embodiment of the present disclosure;

Fig. 10 illustrates an example diagram of a Time Division Duplex (TDD) communication system in accordance with an embodiment of the present disclosure;

fig. 11 is an example diagram illustrating two example full duplex communication system configurations according to an embodiment of the disclosure;

fig. 12 shows an example diagram of an example Random Access Channel (RACH) configuration in a full duplex communication system according to an embodiment of the disclosure;

fig. 13 shows an example diagram of a PRACH resource selection configuration using Reference Signal Received Power (RSRP) in accordance with an embodiment of the present disclosure;

fig. 14 illustrates an example method for a PRACH resource selection processing chain using RSRP in accordance with an embodiment of the disclosure;

fig. 15 illustrates an example diagram of an example determination and use of RACH configuration in accordance with an embodiment of the present disclosure;

fig. 16 shows an example diagram of an example PRACH allocation and configuration in accordance with an embodiment of the present disclosure;

fig. 17 shows a block diagram of a terminal (or UE) according to an embodiment of the present disclosure; and

fig. 18 shows a block diagram of a base station according to an embodiment of the present disclosure.

Detailed Description

Before proceeding with the following detailed description, it may be advantageous to set forth definitions of certain words and phrases used in this patent document. The term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another. The terms "transmit," "receive," and "communicate," and derivatives thereof, include direct and indirect communication. The terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation. The term "or" is inclusive, meaning and/or. The phrase "associated with … …" and its derivatives refer to include, are included, are interconnected with … …, are involved, are connected to or are connected with … …, are coupled to or are coupled with … …, are communicable with … …, are cooperative with … …, are staggered, are juxtaposed, are proximate, are joined to or are joined with … …, have … … properties, have relationships with … … or with … …, or the like. The term "controller" refers to any device, system, or portion thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and/or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. When used with a list of items, at least one of the phrases ". Cndot.is meant that different combinations of one or more of the listed items may be used, and only one item in the list may be required. For example, "at least one of A, B and C" includes any combination of: A. b, C, A and B, A and C, B and C, and a and B and C.

Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code. The phrase "computer readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer readable medium" includes any type of medium capable of being accessed by a computer, such as Read Only Memory (ROM), random Access Memory (RAM), a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), or any other type of memory. "non-transitory" computer-readable media do not include wired, wireless, optical, or other communication links that transmit transitory electrical or other signals. Non-transitory computer readable media include media that can permanently store data and media that can store data and be later overwritten, such as rewritable optical disks or erasable storage devices.

Other definitions for certain words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior as well as future uses of such defined words and phrases.

Figures 1 through 18, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will appreciate that the principles of the present disclosure may be implemented in any suitably arranged system or device.

The following documents are incorporated by reference into this disclosure as if fully set forth in this disclosure: third generation partnership project (3 GPP) Technical Specification (TS) 3GPP TS 38.212v16.6.0, "NR; physical channel and modulation "; GPP TS 38.212v16.6.0, "NR; multiplexing and channel coding "(REF 1); 3GPP TS 38.213v16.6.0, "NR; a physical layer program for control "(REF 2); 3GPP TS 38.214v16.6.0, "NR; physical layer program for data "(REF 3); 3GPP TS 38.321v16.5.0, "NR; medium Access Control (MAC) protocol specification "(REF 4); and 3GPP TS 38.331v16.5.1, "NR; radio Resource Control (RRC) protocol specification "(REF 5).

In order to meet the increasing demand for wireless data services since the deployment of fourth generation (4G) communication systems, efforts have been made to develop and deploy improved fifth generation (5G) or pre-5G/NR communication systems. Thus, a 5G or pre-5G communication system is also referred to as a "super 4G network" or a "Long Term Evolution (LTE) after-system.

A 5G communication system is considered to be implemented in a higher frequency (mmWave) band (e.g., 28GHz or 60GHz band) in order to achieve a higher data rate, or in a lower frequency band (e.g., 6 GHz) in order to achieve robust coverage and mobility support. In order to reduce propagation loss of radio waves and increase transmission distance, beamforming, massive Multiple Input Multiple Output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, massive antenna techniques are discussed in 5G communication systems.

Further, in 5G communication systems, developments for system network improvement are underway based on advanced small cell, cloud Radio Access Network (RAN) ultra-dense network, vehicle-to-everything (V2X), device-to-device (D2D) communication, wireless backhaul (IAB), mobile network, cooperative communication, coordinated multipoint (CoMP), reception end interference cancellation, multiple reception points (multi-TRP), cross Link (CLI) and Remote Interference (RIM) detection and avoidance, NR operation in unlicensed band (NR-U), and the like.

The discussion of the 5G system and the frequency bands associated therewith is for reference as certain embodiments of the present disclosure may be implemented in a 5G system. However, the present disclosure is not limited to 5G systems or frequency bands associated therewith, and embodiments of the present disclosure may be used in connection with any frequency band. For example, aspects of the present disclosure may also be applied to 5G communication systems, 6G, or even deployments that may use later versions of the terahertz (THz) frequency band.

Depending on the network type, the term "base station" (BS) may refer to any component (or collection of components) configured to provide wireless access to a network, such as a Transmission Point (TP), TRP, enhanced base station (eNodeB or eNB), gNB, macrocell, femtocell, wiFi Access Point (AP), satellite, or other wireless-enabled device. The base station may provide wireless access according to one or more wireless communication protocols (e.g., 5G 3GPP New radio interface/Access (NR), LTE-advanced (LTE-A), high Speed Packet Access (HSPA), wi-Fi 802.11a/b/g/n/ac, etc.). The terms "BS," "gNB," and "TRP" may be used interchangeably in this disclosure to refer to network infrastructure components that provide wireless access to remote terminals. Furthermore, the term "user equipment" (UE) may refer to any component, such as a terminal, mobile station, subscriber station, remote terminal, wireless terminal, receiving point, vehicle, or user equipment, depending on the type of network. For example, the UE may be a mobile phone, a smart phone, a monitoring device, an alarm device, a fleet management device, an asset tracking device, an automobile, a desktop computer, an entertainment device, an infotainment device, a vending machine, an electricity meter, a water meter, a gas meter, a security device, a sensor device, an appliance, and the like.

Fig. 1, 2, and 3 below describe various embodiments implemented in a wireless communication system using Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques. The descriptions of fig. 1-3 are not meant to imply physical or architectural limitations with respect to the manner in which different embodiments may be implemented. The various embodiments of the present disclosure may be implemented in any suitably arranged communication system.

Fig. 1 illustrates an example wireless network 100 according to an embodiment of this disclosure. The embodiment of the wireless network 100 shown in fig. 1 is for illustration only. Other embodiments of wireless network 100 may be used without departing from the scope of this disclosure.

As shown in fig. 1, wireless network 100 includes base stations BS101 (e.g., gNB), BS102, and BS103.BS101 communicates with BS102 and BS103.BS101 is also in communication with at least one network 130, such as the internet, a proprietary Internet Protocol (IP) network, or other data network.

BS102 provides wireless broadband access to network 130 for a first plurality of User Equipment (UEs) within coverage area 120 of BS 102. The first plurality of UEs includes UE 111, which may be located in a small enterprise; UE 112, which may be located in enterprise (E); UE 113, which may be located in a WiFi Hotspot (HS); UE 114, which may be located in a first home (R); a UE 115, which may be located in a second home (R); and UE 116, which may be a mobile device (M), such as a cellular telephone, wireless laptop, wireless PDA, etc. BS103 provides wireless broadband access to network 130 for a second plurality of UEs within coverage area 125 of BS103. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of the BSs 101-103 may communicate with each other and with the UEs 111-116 using 5G/NR, long Term Evolution (LTE), long term evolution-advanced (LTE-A), wiMAX, wiFi, or other wireless communication technology.

The dashed lines illustrate the general extent of coverage areas 120 and 125, which are shown as approximately circular for purposes of illustration and explanation only. It should be clearly understood that the coverage areas associated with the BS, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the BS and the variations in the radio environment associated with the natural and man-made obstructions.

As described in more detail below, one or more of UEs 111-116 include circuitry, programming, or a combination thereof for a random access procedure for full duplex operation. In certain embodiments, one or more of the BSs 101-103 comprise circuitry, programming, or a combination thereof for a random access procedure for full duplex operation.

Although fig. 1 shows one example of a wireless network, various changes may be made to fig. 1. For example, the wireless network may include any number of BSs and any number of UEs in any suitable arrangement. Further, BS101 may communicate directly with any number of UEs and provide these UEs with wireless broadband access to network 130. Similarly, each BS102-103 may communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. In addition, BSs 101, 102, and/or 103 may provide access to other or additional external networks, such as external telephone networks or other types of data networks.

Fig. 2 illustrates an example BS102 according to an embodiment of the disclosure. The embodiment of BS102 shown in fig. 2 is for illustration only, and BSs 101 and 103 of fig. 1 may have the same or similar configurations. However, there are a variety of configurations of BSs, and fig. 2 does not limit the scope of the present disclosure to any particular implementation of a BS.

As shown in fig. 2, BS102 includes a plurality of antennas 205a-205n, a plurality of Radio Frequency (RF) transceivers 210a-210n, transmit (TX) processing circuitry 215, and Receive (RX) processing circuitry 220.BS102 also includes a controller/processor 225, memory 230, and a backhaul or network interface 235.

RF transceivers 210a-210n receive incoming RF signals from antennas 205a-205n, such as signals transmitted by UEs in wireless network 100. The RF transceivers 210a-210n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signal is sent to RX processing circuit 220, and RX processing circuit 220 generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuit 220 sends the processed baseband signals to a controller/processor 225 for further processing.

TX processing circuitry 215 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from controller/processor 225. TX processing circuitry 215 encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceivers 210a-210n receive the output processed baseband or IF signals from TX processing circuitry 215 and up-convert the baseband or IF signals to RF signals for transmission via antennas 205a-205 n.

Controller/processor 225 may include one or more processors or other processing devices that control the overall operation of BS 102. For example, controller/processor 225 may control the reception of uplink channel signals and the transmission of downlink channel signals by RF transceivers 210a-210n, RX processing circuit 220, and TX processing circuit 215 according to well-known principles. The controller/processor 225 may also support additional functions, such as higher-level wireless communication functions. For example, the controller/processor 225 may support beamforming or directional routing operations in which outgoing signals from the plurality of antennas 205a-205 n/incoming signals to the plurality of antennas 205a-205n are weighted differently to effectively direct the output signal in a desired direction. Controller/processor 225 may support any of a variety of other functions in BS 102. In some embodiments, controller/processor 225 includes at least one microprocessor or microcontroller.

The controller/processor 225 is also capable of executing programs and other processes residing in memory 230, such as an OS. Controller/processor 225 may move data into and out of memory 230 as needed to perform the process.

The controller/processor 225 is also coupled to a backhaul or network interface 235. Backhaul or network interface 235 allows BS102 to communicate with other devices or systems through a backhaul connection or network. The network interface 235 may support communication via any suitable wired or wireless connection. For example, when BS102 is implemented as part of a cellular communication system (such as a 5G/NR, LTE, or LTE-a enabled cellular communication system), network interface 235 may allow BS102 to communicate with other BSs over a wired or wireless backhaul connection. When BS102 is implemented as an access point, network interface 235 may allow BS102 to communicate with a larger network, such as the internet, through a wired or wireless local area network, or through a wired or wireless connection. The network interface 235 includes any suitable structure that supports communication over a wired or wireless connection, such as an ethernet or RF transceiver.

Memory 230 is coupled to controller/processor 225. A portion of memory 230 may include RAM and other portions of memory 230 may include flash memory or other ROM.

Although fig. 2 shows one example of BS102, various changes may be made to fig. 2. For example, BS102 may include any number of each of the components shown in fig. 2. As a particular example, an access point may include multiple network interfaces 235 and the controller/processor 225 may support routing functions to route data between different network addresses. As another specific example, BS102 may include multiple instances of each (such as one instance per RF transceiver) although shown as including a single instance of TX processing circuitry 215 and a single instance of RX processing circuitry 220. Furthermore, the various components in fig. 2 may be combined, further subdivided, or omitted, and additional components may be added according to particular needs.

Fig. 3 illustrates an example UE 116 according to an embodiment of this disclosure. The embodiment of UE 116 shown in fig. 3 is for illustration only and UEs 111-115 of fig. 1 may have the same or similar configuration. However, there are a variety of configurations for the UE, and fig. 3 does not limit the scope of the present disclosure to any particular implementation of the UE.

As shown in fig. 3, UE 116 includes an antenna 305, an RF transceiver 310, TX processing circuitry 315, a microphone 320, and Receive (RX) processing circuitry 325.UE 116 also includes speaker 330, processor (or controller) 340, input/output (I/O) Interface (IF) 345, input device 350, display 355, and memory 360. Memory 360 includes an Operating System (OS) 361 and one or more applications 362.

The RF transceiver 310 receives an incoming RF signal transmitted by a BS of the wireless network 100 from the antenna 305. The RF transceiver 310 down-converts the incoming RF signal to generate an Intermediate Frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuit 325, and RX processing circuit 325 generates a processed baseband signal by filtering, decoding, and/or digitizing the baseband or IF signal. The RX processing circuit 325 sends the processed baseband signal to a speaker 330 (such as for voice data) or a processor (or controller) 340 for further processing (such as for web-browsing data).

TX processing circuitry 315 receives analog or digital voice data from microphone 320 or other outgoing baseband data (such as network data, email, or interactive video game data) from processor (or controller) 340. TX processing circuitry 315 encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceiver 310 receives the outgoing processed baseband or IF signal from TX processing circuitry 315 and up-converts the baseband or IF signal to an RF signal, which is transmitted via antenna 305.

Processor (or controller) 340 may include one or more processors or other processing devices and execute OS 361 stored in memory 360 to control the overall operation of UE 116. For example, processor (or controller) 340 may control the reception of uplink signals and the transmission of downlink channel signals by RF transceiver 310, RX processing circuit 325, and TX processing circuit 315 according to well-known principles. In some embodiments, the processor (or controller) 340 includes at least one microprocessor or microcontroller.

The processor (or controller) 340 is also capable of executing other processes and programs resident in the memory 360, such as processes for beam management. The processor (or controller) 340 may move data into or out of the memory 360 as needed to perform the process. In some embodiments, the processor (or controller) 340 is configured to execute the application 362 based on the OS 361 or in response to a signal received from a BS or operator. The processor (or controller) 340 is also coupled to an I/O interface 345, which I/O interface 345 provides the UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. I/O interface 345 is the communication path between these accessories and processor (or controller) 340.

Processor (or controller) 340 is also coupled to input device 350 and display 355. An operator of UE 116 may input data to UE 116 using input device 350. The input device 350 may be a keyboard, touch screen, mouse, trackball, voice input, or other device capable of functioning as a user interface to allow a user to interact with the UE 116. For example, the input device 350 may include a voice recognition process to allow a user to input voice commands. In another example, the input device 350 may include a touch panel, (digital) pen sensor, key, or ultrasonic input device. The touch panel may recognize a touch input in at least one scheme, such as a capacitive scheme, a pressure sensitive scheme, an infrared scheme, or an ultrasonic scheme, for example.

Processor (or controller) 340 is also coupled to display 355. Display 355 may be a liquid crystal display, a light emitting diode display, or other display capable of presenting text and/or at least limited graphics (e.g., from a website).

The memory 360 is coupled to the processor (or controller) 340. A portion of memory 360 may include Random Access Memory (RAM) while other portions of memory 360 may include flash memory or other Read Only Memory (ROM).

Although fig. 3 shows one example of UE 116, various changes may be made to fig. 3. For example, the various components in FIG. 3 may be combined, further subdivided, or omitted, and additional components may be added according to particular needs. As a particular example, the processor (or controller) 340 may be divided into multiple processors, such as one or more Central Processing Units (CPUs) and one or more Graphics Processing Units (GPUs). Further, while fig. 3 shows the UE 116 configured as a mobile phone or smart phone, the UE may be configured to operate as other types of mobile or stationary devices.

Fig. 4 and 5 illustrate example wireless transmit and receive paths according to this disclosure. In the following description, the transmit path 400 of fig. 4 may be described as being implemented in a BS (such as BS 102), while the receive path 500 of fig. 5 may be described as being implemented in a UE (such as UE 116). However, it is understood that the reception path 500 may be implemented in a BS and the transmission path 400 may be implemented in a UE. In some embodiments, receive path 500 is configured to support UL reference signal based beam management as described in embodiments of the present disclosure.

The transmit path 400, as shown in fig. 4, includes a channel coding and modulation block 405, a serial-to-parallel (S-to-P) block 410, an Inverse Fast Fourier Transform (IFFT) block 415 of size N, a parallel-to-serial (P-to-S) block 420, an add cyclic prefix block 425, and an Up Converter (UC) 430. The receive path circuit 500 as shown in fig. 5 includes a down-converter (DC) 555, a remove cyclic prefix block 560, a serial-to-parallel (S-to-P) block 565, a Fast Fourier Transform (FFT) block 570 of size N, a parallel-to-serial (P-to-S) block 575, and a channel decoding and demodulation block 580.

As shown in fig. 4, a channel coding and modulation block 405 receives a set of information bits, applies coding, such as Low Density Parity Check (LDPC) coding, and modulates input bits, such as with Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM), to generate a sequence of frequency domain modulation symbols.

Serial-to-parallel block 410 converts (such as demultiplexes) the serial modulated symbols into parallel data to generate N parallel symbol streams, where N is the size of the IFFT/FFT used in BS102 and UE 116. An IFFT block 415 of size N performs an IFFT operation on the N parallel symbol streams to generate a time domain output signal. Parallel-to-serial block 420 converts (such as multiplexes) the parallel time domain output symbols from IFFT block 415 of size N to generate a serial time domain signal. The add cyclic prefix block 425 inserts a cyclic prefix into the time domain signal. Up-converter 430 modulates (such as up-converts) the output of add cyclic prefix block 425 to an RF frequency for transmission via a wireless channel. The signal may also be filtered at baseband before conversion to RF frequency.

The RF signal transmitted from the BS102 reaches the UE 116 after passing through the wireless channel, and an operation inverse to that at the BS102 is performed at the UE 116.

As shown in fig. 5, down-converter 555 down-converts the received signal to baseband frequency, and remove cyclic prefix block 560 removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel block 565 converts the time-domain baseband signal into a parallel time-domain signal. The FFT block 570 of size N performs an FFT algorithm to generate N parallel frequency domain signals. Parallel-to-serial block 575 converts the parallel frequency domain signal into a sequence of modulated data symbols. Channel decoding and demodulation block 580 demodulates and decodes the modulated symbols to recover the original input data stream.

Each of BSs 101-103 can implement a transmit path 400 as shown in fig. 4 similar to that transmitted in the downlink to UEs 111-116 and can implement a receive path 500 as shown in fig. 5 similar to that received in the uplink from UEs 111-116. Similarly, each of the UEs 111-116 may implement a transmit path 400 for transmitting in the uplink to the BSs 101-103 and may implement a receive path 500 for receiving in the downlink from the BSs 101-103.

Each of the components in fig. 4 and 5 may be implemented using hardware alone or using a combination of hardware and software/firmware. As a specific example, at least some of the components in fig. 4 and 5 may be implemented in software, while other components may be implemented in configurable hardware or a mixture of software and configurable hardware. For example, FFT block 570 and IFFT block 515 may be implemented as configurable software algorithms, where the value of size N may be modified depending on the implementation.

Further, although described as using an FFT and an IFFT, this is only exemplary and should not be construed as limiting the scope of the present disclosure. Other types of transforms may be used, such as Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions. It is understood that for DFT and IDFT functions, the value of the variable N may be any integer (such as 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of the variable N may be any integer that is a power of 2 (such as 1, 2, 4, 8, 16, etc.).

Although fig. 4 and 5 show examples of wireless transmission and reception paths, various changes may be made to fig. 4 and 5. For example, the various components in fig. 4 and 5 may be combined, further subdivided, or omitted, and additional components may be added according to particular needs. Further, fig. 4 and 5 are intended to illustrate examples of the types of transmit and receive paths that may be used in a wireless network. Any other suitable architecture may be used to support wireless communications in a wireless network.

The communication system includes a Downlink (DL) that refers to transmission from a base station (such as BS 102) or one or more transmission points to a UE (such as UE 116) and an Uplink (UL) that refers to transmission from a UE (such as UE 116) to a base station (such as BS 102) or to one or more reception points.

The time unit for DL signaling or UL signaling on a cell is referred to as a slot and may include one or more symbols. The symbol may also be used as an additional time unit. The frequency (or Bandwidth (BW)) unit is referred to as a Resource Block (RB). One RB includes a plurality of Subcarriers (SCs). For example, a slot may have a duration of 1 millisecond or 0.5 millisecond, including 14 symbols, and an RB may include 12 SCs with an inter-SC spacing of 15kHz or 30kHz, and so on.

The DL signals include data signals conveying information content, control signals conveying DL Control Information (DCI), and Reference Signals (RSs), also referred to as pilot signals. The gNB, such as BS102, transmits data information or DCI over a corresponding Physical DL Shared Channel (PDSCH) or Physical DL Control Channel (PDCCH). PDSCH or PDCCH may be transmitted on a variable number of slot symbols including one slot symbol. For brevity, a DCI format that schedules PDSCH reception of a UE is referred to as a DL DCI format, and a DCI format that schedules Physical Uplink Shared Channel (PUSCH) transmission from the UE is referred to as a UL DCI format.

The gNB, such as BS102, transmits one or more of a plurality of types of RSs including channel state information RSs (CSI-RSs) and demodulation RSs (DM-RSs). CSI-RS is primarily intended for UEs to perform measurements and provide Channel State Information (CSI) to the gNB. For channel measurements, non-zero power CSI-RS (NZP CSI-RS) resources are used. For interference measurement reporting, CSI interference measurement (CSI-IM) resources associated with a zero power CSI-RS (ZP CSI-RS) configuration are used. The CSI process consists of NZP CSI-RS and CSI-IM resources.

The UE, such as UE 116, may determine CSI-RS transmission parameters through DL control signaling or higher layer signaling, such as Radio Resource Control (RRC) signaling, from the gNB. The transmission instance of the CSI-RS may be indicated by DL control signaling or configured by higher layer signaling. DM-RS is transmitted only in BW of the corresponding PDCCH or PDSCH, and the UE may demodulate data or control information using the DM-RS.

The UL signals also include data signals conveying information content, control signals conveying UL Control Information (UCI), DM-RS associated with data or UCI demodulation, sounding RS (SRS) enabling the gNB to perform UL channel measurements, and Random Access (RA) preambles enabling the UE to perform random access (see also NR specifications). The UE transmits data information or UCI through a corresponding PUSCH or Physical UL Control Channel (PUCCH). PUSCH or PUCCH may be transmitted on a variable number of slot symbols including one slot symbol. The gNB may configure the UE to transmit signals on the cell within an active UL bandwidth portion (BWP) of the cell UL BW.

UCI includes hybrid automatic repeat request acknowledgement (HARQ-ACK) information indicating correct or incorrect detection of a data Transport Block (TB) in PDSCH, a Scheduling Request (SR) indicating whether a UE, such as UE 116, has data in a buffer, and CSI reports that enable a gNB, such as BS102, to select appropriate parameters for PDSCH or PDCCH transmission to the UE. The HARQ-ACK information may be configured to have a smaller granularity than each TB, and may be each data Code Block (CB) or each data CB group, wherein the data TB includes a plurality of data CBs.

The CSI report from the UE may include a Channel Quality Indicator (CQI) informing the gNB of a maximum Modulation and Coding Scheme (MCS) for the UE to detect the data TB at a predetermined block error rate (BLER), such as 10% BLER (see NR specifications), a Precoding Matrix Indicator (PMI) informing the gNB of how to combine signals from multiple transmitter antennas according to a Multiple Input Multiple Output (MIMO) transmission principle, and a Rank Indicator (RI) indicating a transmission rank of the PDSCH.

UL RS includes DM-RS and SRS. DM-RS is sent only in BW of the corresponding PUSCH or PUCCH transmission. The gNB may demodulate information in the corresponding PUSCH or PUCCH using DM-RS. SRS is transmitted by the UE to provide UL CSI to the gNB, and for TDD systems, SRS transmission may also provide PMI for DL transmission. In addition, to establish a synchronization or initial higher layer connection with the gNB, the UE may transmit a physical random access channel (PRACH as shown in the NR specifications).

An antenna port is defined such that a channel on which a symbol on the antenna port is transmitted can be inferred from a channel on which another symbol on the same antenna port is transmitted.

For DM-RS associated with PDSCH, the channel on which the PDSCH symbol on one antenna port is transmitted may be inferred from the channel on which the DM-RS symbol on the same antenna port is transmitted only if both symbols are within the same resource, in the same time slot, and in the same Precoding Resource Group (PRG) as the scheduled PDSCH.

For DM-RS associated with PDCCH, the channel on which the PDCCH symbol on one antenna port is transmitted can be inferred from the channel on which the DM-RS symbol on the same antenna port is transmitted only if both symbols are within resources that the UE can assume to use the same precoding.

For DM-RS associated with a Physical Broadcast Channel (PBCH), a channel on which a PBCH symbol on one antenna port is transmitted can be inferred from a channel on which a DM-RS symbol on the same antenna port is transmitted only when two symbols are transmitted in the same slot and in a Synchronization Signal (SS)/PBCH (SS/PBCH is also denoted as SSB) block having the same block index.

Two antenna ports are considered quasi-co-located if the massive nature of the channel over which the symbols on one antenna port are transmitted can be inferred from the channel over which the symbols on the other antenna port are transmitted. The large scale properties include one or more of delay spread, doppler shift, average gain, average delay, and spatial Rx parameters.

A UE, such as UE 116, may assume that SSBs transmitted with the same block index at the same center frequency location are quasi co-sited with respect to doppler spread, doppler shift, average gain, average delay, delay spread, and (where applicable) spatial Rx parameters. The UE may not assume quasi co-location for any other SS/PBCH block transmission.

Without CSI-RS configuration, and unless otherwise configured, the UE may assume PDSCH DM-RS and SSB to be quasi co-sited with respect to doppler shift, doppler spread, average delay, delay spread, and (when applicable) spatial Rx parameters. The UE may assume PDSCH DM-RS within the same Code Division Multiplexing (CDM) group to be quasi co-sited with respect to doppler shift, doppler spread, average delay, delay spread, and spatial Rx. The UE may also assume that the DM-RS port associated with PDSCH is quasi co-located with QCL type a, type D (when applicable) and average gain (QCL). The UE may also assume that no DM-RS collides with SS/PBCH blocks.

In some embodiments, a UE, such as UE 116, may be configured with a list of up to M Transmission Configuration Indication (TCI) status configurations within the higher layer parameters PDSCH-Config (PDSCH-configuration) to decode PDSCH from detected PDCCH with DCI intended for the UE and a given serving cell, where M depends on UE capability maxnumberconfiguredtstatterpercc. Each TCI state contains parameters for configuring a quasi co-sited (QCL) relationship between one or two downlink reference signals and a DM-RS port of a PDSCH, a DM-RS port of a PDCCH, or a CSI-RS port of a CSI-RS resource.

The quasi co-sited relationship is configured (if so) by the higher layer parameters qcl-Type1 for the first DL RS and qcl-Type2 (qcl-Type 2) for the second DL RS. The QCL type may be different for the case of two DL RSs, regardless of whether the references are for the same DL RS or for different DL RSs. The quasi co-location Type corresponding to each DL RS is given by a higher layer parameter QCL-Type (QCL-Type) in QCL-Info (QCL-Info), and may take one of the following values: QCL-TypeA: { Doppler shift, doppler spread, average delay, delay spread }; QCL-TypeB: { Doppler shift, doppler spread; QCL-TypeC: { Doppler shift, average delay }; QCL-TypeD: { spatial Rx parameters }.

A UE, such as UE 116, may receive a MAC-CE activation command to activate up to N]The (e.g., n=8) TCI state maps to the code point of the DCI field "transmission configuration indication". When transmitting the HARQ-ACK corresponding to the PDSCH carrying the activation command in slot n, the mapping of the indication between the TCI state and the code point of the DCI field "transmission configuration indication" may be applied after the MAC-CE application time, e.g. starting from the first slot after the slot (e.g.,)。

the RA procedure is initiated by: RRC (for SI request) -if SIB1 includes scheduling information for (on-demand) SI request; a MAC; and a PDCCH order (PDCCH-order).

The random access procedure may be initiated due to at least one of the following triggers/purposes: (1) Initial access to establish RRC connection (from rrc_idle to rrc_connected); (2) Reestablishing the RRC connection after a Radio Link Failure (RLF); (3) an on-demand System Information (SI) request; (4) switching; (5) UL synchronization; (6) scheduling the request; (7) positioning; and (8) link recovery—also known as Beam Fault Recovery (BFR).

RA may operate in two modes: (i) Contention-based random access (CBRA), in which UEs within a serving cell may share the same RA resources, and thus there is a possibility of collision among RA attempts from different UEs, and (ii) contention-free random access (CFRA), in which UEs have dedicated RA resources indicated by the serving gNB and may not be shared with other UEs, such that RA collisions may be avoided. For example, CBRA may be used for all of the triggers/purposes described above, while CFRA may be used only for triggers/purposes (4) to (8) as shown above.

The 4-step random access procedure, also referred to as type 1 (L1) random access procedure, consists of the following steps/operations of the UE: (i) transmission of a PRACH preamble (Msg 1); (ii) attempting to receive a random access response (RAR or Msg 2); (iii) sending a contention resolution message (Msg 3); and (iv) attempting to receive a contention resolution message (msg 4).

An alternative random access procedure is also considered, which is a so-called 2-step RACH or type 2L 1 random access procedure, where Msg1 and Msg3 are combined into an "MsgA" transmission, and above Msg2 and Msg4 are combined into an "MsgB" reception.

Various embodiments of the present disclosure relate to a 4-step RACH, but these embodiments are generally applicable to a 2-step RACH as well, and for brevity, explicit separate descriptions are generally omitted.

PRACH preamble transmission (for both CBRA and CFRA modes) is associated with DL RS. The association may help the serving gNB identify an uplink spatial receive filter/beam for receiving the PRACH and may also help the UE identify an uplink spatial transmit filter/beam for transmitting the PRACH. For example, the UE may use the same or related (such as having the same quasi co-located (QCL) attribute and/or the same direction but a narrower width) uplink transmission filter/beam as the uplink transmission filter/beam for DL reception of the indicated DL RS of the Msg1 transmission. The association may also be used to provide DL RS resources for path loss estimation to determine PRACH preamble transmit power in the NR specifications.

The DL RS for Msg1 transmission may be one of the following options based on PRACH scenario: SSB: for BFR, CFRA, PDCCH command PRACH, SI request, CBRA; or CSI-RS: for BFR, CFRA, CBRA.

Throughout this disclosure, SSB is used as a short form of SS/PBCH block. The terms SSB and SS/PBCH block are used interchangeably in this disclosure.

Further, the serving cell may be configured with both SSB and CSI-RS for PRACH transmission. For example, some PRACH preambles may be associated with SSBs for QCL determination and some PRACH preambles may be associated with CSI-RS for QCL determination. It is also possible that the secondary serving cell (SCell) does not have any SSB configuration/transmission and only supports PRACH transmission from UEs using CSI-RS for QCL determination. Then, as described in the previous paragraph, certain random access triggers/modes, such as for PDDCH commands PRACH or for SI requests, are not applicable.

The RACH configuration includes RACH slots and RACH Opportunities (ROs) in certain frequency resource blocks that repeat in certain periods.

NR uses a Zadoff-Chu sequence for the PRACH preamble. There are 3 PRACH long preamble formats with a sequence length of 839 and a subcarrier spacing of 1.25 or 5kHz. The long sequence supports an unlimited set and a limited set of types a and B. For beam scanning purposes within RACH opportunities, NR uses a new set of PRACH preamble formats of shorter sequence length 139 on SCS of 1, 2, 4, 6 and 12 OFDM symbols and 15, 30, 60 and 120 kHz. These consist of a single or consecutively repeated RACH sequence. A cyclic prefix is inserted at the beginning of the preamble. A guard time is appended at the end of the preamble, and cyclic prefixes and gaps between RACH sequences are omitted. Short sequences only support unlimited sets. For both short and long PRACH preamble sequences, the network may also perform beam scanning reception between RACH opportunities.

A plurality of RACH preamble formats are defined for one or more PRACH symbols. Possibly, different CP and GT lengths may be used. The PRACH preamble configuration is signaled to the UE through RRC. The UE calculates PRACH transmit power for retransmission of the preamble based on the latest estimate of the pathloss and a power ramp counter. If the UE performs beam switching, the counter for the power ramp is not changed. The RRC informs the UE of the association between the SSB and RACH resources. The threshold for SSB for RACH resource association is RSRP based and configurable by the network.

Prior to RACH preamble transmission, the physical layer of the UE receives the set of SSB indexes and provides the UE RRC sub-layer with a set of RSRP measurements for the SSB candidates with the indexes. The information required by the UE physical layer before PRACH preamble transmission includes a preamble format, time resources, and frequency resources for PRACH transmission, and parameters for determining a root sequence in a set of PRACH preamble sequences and its cyclic shift, including an index of a logical root sequence table, a cyclic shift NCS, and a set type, i.e., an unrestricted, restricted set a, or restricted set B.

The SSB index maps to the PRACH opportunity in ascending order of preamble index within a single PRACH opportunity, then maps to the PRACH opportunity in ascending order of frequency resource index of frequency multiplexed PRACH opportunity, then maps to the PRACH opportunity in ascending order of time resource index of time multiplexed PRACH opportunity within PRACH slot, and finally maps to the PRACH opportunity in ascending order of index of PRACH slot. The association period for mapping SSBs to PRACH opportunities starting from frame 0 is the minimum of the set determined by the PRACH configuration period, such that N _SSB The individual SS/PBCH blocks are mapped to PRACH opportunities at least once within the association period. UE obtains parameter N from RRC _SSB . If there is no mapping to N after an integer number of SSB to PRACH opportunity mapping cycles within the association period _SSB The PRACH opportunities for each SSB are set, then no SSB is mapped to the set of PRACH opportunities. The association pattern period comprises one or more association periods and is calculated such that the pattern between PRACH opportunity and SSB is repeated at most once every 160 milliseconds. PRACH opportunities (if any) not associated with SSBs after an integer number of association periods are not usedIn PRACH transmission.

PRACH preamble transmission may occur within a configurable subset of time slots, referred to as PRACH slots, and be repeated every PRACH configuration period. Within each PRACH slot in the frequency domain there may be multiple PRACH opportunities covering NRBPRACH-preamble NPRACH consecutive RBs, where NRBPRACH-preamble is the preamble bandwidth measured in number of RBs and NPRACH is the number of frequency domain PRACH opportunities.

The next available PRACH opportunity in the PRACH opportunities corresponding to the selected SSB may be further limited by the parameter ra-SSB-occidionmassindex (ra-SSB-opportunity mask index) if configured or indicated by the PDCCH. Otherwise, the UE MAC randomly selects PRACH opportunities with equal probability among consecutive PRACH opportunities. Measurement gaps are also considered in determining the next available PRACH opportunity corresponding to the selected SSB. Similarly, the parameter ra-OccasionList (ra-opportunity list) may limit the PRACH opportunity(s) when associated with a CSI-RS that may transmit a PRACH preamble.

Fig. 6 illustrates an example diagram 600 of example PRACH time and frequency domain allocations and parameter configurations, according to an embodiment of this disclosure. The diagram 600 is for illustration only and other embodiments may be used without departing from the scope of the present disclosure.

For a given preamble type, corresponding to a certain preamble bandwidth, the overall available time-frequency PRACH resources within a cell may be described by the following parameters: a configurable PRACH period that may range from 10 to 160 milliseconds; a set of configurable PRACH slots within a PRACH period; and a configurable frequency domain PRACH resource given by an index of a first RB in the resource and a number of frequency domain PRACH opportunities.

The UE may send the PRACH preamble only in the time resource signaled via the RRC parameter PRACH-configuration index (PRACH-configuration index) and also depends on the frequency range (FR 1 or FR 2) and the spectrum type. The UE may transmit the PRACH preamble only in the frequency resource indicated by the parameter msg1-FrequencyStart (msg 1-frequency start). PRACH frequency resource nra= {0;1, a step of; ..; m-1 (where parameter M is derived from RRC parameter msg 1-FDM) is numbered in ascending order starting from the lowest frequency within the initial active UL bandwidth portion during initial access. In addition to the measured SSB, the determination of PRACH PREAMBLE transmission POWER also requires knowledge of the parameter preamble_received_target_power for active UL BWP on the carrier signaled via RRC.

After RACH preamble transmission, if the UE does not receive a random access response containing a Random Access Preamble Identifier (RAPID) corresponding to a preamble sequence transmitted by the UE within a random access response window (e.g., up to 10 ms) of RRC signaled and configurable size ra-response window, the UE typically increases (steps) the transmission power to some limit, such as a limit defined by the maximum transmission power, using a power ramp counter for subsequent PRACH transmissions. If the UE changes the spatial domain transmission filter before PRACH retransmission, the UE physical layer informs the higher layer to suspend the power ramp counter.

After the UE transmits the PRACH preamble (Msg 1), there are three further steps for the (4 steps) random access procedure of the UE: receiving a random access response (RAR or Msg 2) from the gNB; transmitting a contention resolution message (Msg 3) to the gNB; and receiving a contention resolution response message (Msg 4) from the gNB.

The random access response (RAR or Msg 2) is PDCCH/PDSCH reception on DL BWP of PCell/SpCell, which is either initial DL BWP (for the case of initial access, i.e. the RRC connection is (re) established) or active DL BWP (with the same BWP index as the active UL BWP), as described below (for other random access triggers than initial access). If the active DL BWP index is different from the active UL BWP index, the UE changes the active DL BWP to DL BWP having the same BWP index as the active UL BWP.

The SCS used for PDCCH reception scheduling PDSCH with RAR message is the SCS of the type 1-PDCCH Common Search Space (CSS) set as described in REF 3. The SCS for any subsequent PDCCH/PDSCH reception is also the same as the SCS for PDCCH/PDSCH providing the RAR, unless the UE is configured with a different SCS.

The UE monitors the PDCCH during a configured time window to detect DCI format 1_0 scheduling PDSCH providing RAR in a search space indicated by the recovery search space Id of PCell/SpCell identified by cell-RNTI (C-RNTI) according to type 1-PDCCH CSS set of PCell/SpCell identified by RA Radio Network Temporary Identifier (RNTI) (or, for the case of Beam Failure Recovery (BFR) with CFRA).

The RAR includes information for one or more UEs, some of which are common to the UEs, and the remaining information is UE-specific.

In one example, the RAR includes a 4-bit back-off indicator (BI) that indicates a maximum back-off time required before a next PRACH transmission attempt by the UE. The UE randomly and uniformly selects an actual backoff time between zero and the value indicated by the BI field. BI is typically used to control the loading of PRACH preamble transmissions on the serving cell.

In another example, the RAR includes a Random Access Preamble ID (RAPID), such as through a 6-bit field, that indicates the ID of the preamble transmitted by the UE and is a response to a System Information (SI) request of the UE.

In another example, the gNB sends the RAPID with a MAC payload (MAC RAR) that includes a Timing Advance (TA) command, an uplink grant for scheduling the Msg3 PUSCH, and a temporary C-RNTI (TC-RNTI).

FIG. 7 illustrates an example diagram 700 of an example E/T/R/R/BI MAC sub-header in accordance with an embodiment of the disclosure. The diagram 700 is for illustration only, and other embodiments may be used without departing from the scope of the present disclosure. For example, the embodiment of the E/R/R/BI MAC subheader shown in FIG. 7 is for illustration only.

One or more of the components shown in fig. 7 may be implemented in dedicated circuitry configured to perform the functions, or one or more of the components may be implemented by one or more processors that execute instructions to perform the functions. Other embodiments are used without departing from the scope of this disclosure.

Fig. 8 illustrates an example diagram 800 of an example E/T/RAPID MAC subheader in accordance with an embodiment of the disclosure. The diagram 800 is for illustration only and other embodiments may be used without departing from the scope of the present disclosure. For example, the embodiment of the E/T/RAPID MAC sub-header shown in FIG. 8 is for illustration only.

One or more components shown in fig. 8 may be implemented in dedicated circuitry configured to perform the functions, or one or more components may be implemented by one or more processors that execute instructions to perform the functions. Other embodiments are used without departing from the scope of this disclosure.

Fig. 9 illustrates an example diagram 900 of an example MAC RAR according to an embodiment of the present disclosure. The diagram 900 is for illustration only and other embodiments may be used without departing from the scope of the present disclosure. The embodiment of the MAC RAR 670 shown in fig. 9 is for illustration only.

One or more of the components shown in fig. 9 may be implemented in dedicated circuitry configured to perform the functions, or one or more of the components may be implemented by one or more processors that execute instructions to perform the functions. Other embodiments are used without departing from the scope of this disclosure.

Table (1) describes the MAC RAR grant field size and includes an exemplary random access response grant content field and corresponding size.

TABLE 1

For CFRA-based BFRs, the UE considers RAR reception successful when the UE receives PDSCH scheduled by a DCI format with a Cyclic Redundancy Check (CRC) scrambled by a C-RNTI for the UE, which is provided by PDCCH reception according to the indicated set of search spaces.

For other cases (such as CBRA and SI requests), RAR is successful for the UE when the UE: (i) Receiving a PDCCH according to a type 1-PDCCH CSS set of SpCell during a configured time window, which provides a DCI format addressed to RA-RNTI; and (ii) correctly decoding transport blocks in PDSCH scheduled by DCI format; and (iii) obtaining the same RAPID as the RAPID of the PRACH preamble transmitted in Msg1 from the MAC RAR in the PDSCH. Then, for a serving cell in which the UE transmits PRACH preamble/Msg 1, the UE applies TA to adjust timing between transmission and reception, stores TC-RNTI provided by MAC RAR for future transmission/reception, and processes RAR UL grant to transmit Msg3 PUSCH.

If the UE's RAR reception is unsuccessful, the UE attempts (possibly at backoff and/or UE processing time up to N _T,1 After +0.75 ms, as described in REF 3) a new PRACH preamble transmission with PRACH resource selection (possibly including a different SSB and/or a different preamble) and possibly by applying PRACH preamble power ramping, unless the UE has reached the configured maximum number of PRACH attempts, then the UE reports the random access problem to the higher layer and stops the RA procedure.

The resource allocation for Msg3 PUSCH (as indicated by RAR UL grant) includes the following fields from table (1): a frequency hopping flag; PUSCH time resource allocation; PUSCH frequency resource allocation.

The time resource allocation field indicates the starting symbol and the time domain length of the Msg3 PUSCH transmission.

The frequency domain resource allocation field is used for uplink resource allocation type 1 and indicates the allocation of consecutive (virtual) resource blocks, as described in REF 3. ""

In the present disclosure, the terms "4-step RA", "type 1RA procedure" and "type 1L 1RA procedure" are used interchangeably. Furthermore, the terms "2-step RA", "type 2RA procedure" and "type 2L 1RA procedure" are used interchangeably.

Before the UE initiates a physical Random Access (RA) procedure, layer 1 of the UE receives an indication from a higher layer to perform a type 1RA procedure (4-step RA) or a type 2RA procedure (2-step RA).

From the physical layer perspective, the type 2L 1RA procedure includes transmission of RA preambles (MsgA) in PRACH and PUSCH, and reception of RAR messages (MsgB) with PDCCH/PDSCH. When the RAR for the 2-step RA procedure indicates to fall back to the 4-step RA (i.e., fallback RAR), the 2-step RA procedure continues similarly to the 4-step RA procedure, i.e., PUSCH transmission scheduled by the RAR UL grant, and PDSCH reception for contention resolution.

The PRACH preamble for 2-step RA is separate from the PRACH preamble for 4-step RA, e.g., the contention-based preamble of each SS/PBCH block for each valid PRACH opportunity for a 2-step RA procedure begins after the preamble for a 4-step RA procedure.

The RACH Opportunity (RO) for the 2-step RA procedure may be common/shared with the RO for the 4-step RA procedure, or may be separate from the RO for the 4-step RA procedure.

In response to the PRACH and PUSCH transmissions, the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI/MsgB-RNTI during windows controlled by the higher layers, e.g., as described in REF 3 and REF 4. The window starts at a first symbol of an earliest set of control resources (CORESET) the UE is configured to receive PDCCHs according to a type 1-PDCCH CSS set, e.g., as described in REF 3, which is at least one symbol after a last symbol corresponding to a PUSCH opportunity for PUSCH transmission (associated with a 2-step RA procedure), where the symbol duration corresponds to SCS for the type 1-PDCCH CSS set. The SCS based on the type 1-PDCCH CSS set, the window length in units of the number of slots is provided by RA-ResponseWindow (for 4-step RA procedure), or a separate configuration may be provided for the time window length of 2-step RA procedure.

If the UE detects a transport block in DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI/MsgB-RNTI and corresponding PDSCH within the window, the UE delivers the transport block to higher layers.

The higher layer indicates to the physical layer one of: (a) When the RAR message is for a fallback RAR and an uplink grant is identified for RAPID associated with PRACH transmission, and when the UE detects an RAR UL grant, the UE procedure continues as in the 4-step RA procedure, or (b) when the RAR message is for a success RAR, an ACK is to be provided in PUCCH transmission. When the UE transmits the PUCCH providing the ACK, the PUCCH resource for PUCCH transmission is indicated by a 4-bit PUCCH Resource Indicator (PRI) field in the success rar of the PUCCH resource set provided by PUCCH-resource com mon; the slot for PUCCH transmission is indicated by a 3-bit PDSCH-to-HARQ feedback timing indicator field in the success rar, which has a value k from {1, 2, 3, 4, 5, 6, 7, 8}, and references the slot T for PUCCH transmission _slot The time slot is determined as ceil (n+k+delta+t) _Δ /T _slot ) Where n is the slot of PDSCH reception, deltaFor example as defined in REF 3 for PUSCH transmission or according to different tables provided in the system specification, and t _Δ And is more than or equal to 0. The first symbol of the UE not expecting PUCCH transmission is less than N after the last symbol received by PDSCH _T,1 +0.5+t _Δ Milliseconds, where N _T,1 Is the PDSCH processing time for UE processing capability 1 as described in REF 4. PUCCH transmissions have the same spatial domain transmission filter and are in the same active UL BWP as the last PUSCH transmission.

If the UE detects DCI format 1_0 and a transport block with CRC scrambled by C-RNTI in the corresponding PDSCH within the window, the UE transmits PUCCH with HARQ-ACK information having an ACK value when the UE correctly detects the transport block or transmits a Negative Acknowledgement (NACK) value when the UE incorrectly detects the transport block, and the time alignment timer is running.

The UE does not expect to be instructed to transmit the PUCCH with HARQ-ACK information at a time before the time at which the UE applies the TA command provided by the transport block.

If the UE does not detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI/MsgB-RNTI within the window, or if the UE does not correctly receive a transport block in the corresponding PDSCH within the window, or if the higher layer does not recognize RAPID associated with PRACH transmission from the UE, the higher layer may instruct the physical layer to perform a type 1 RA procedure or a type 2 RA procedure.

If higher layer requests, the UE is expected to N after no later than the last symbol of the window or the last symbol received by PDSCH _T,1 +0.75 ms to transmit PRACH, where N _T,1 Is N ₁ The duration of the number of symbols corresponds to the PDSCH processing time of UE processing capability 1 when additional PDSCH DM-RS is configured. For μ=0, ue assumes N _1,0 =14 as described in REF 3 and REF 4.

For CFRA, and for SI requests, the correct reception of Msg2/RAR is the final step of the RA procedure. However, for CBRA, it is possible that multiple UEs may have used the same preamble and further steps are required to resolve the contention. Further, for random access prior to the rrc_connected state, such as for initial access, the UE and the gNB need to exchange further information to establish a connection, and for a contention resolution request and possibly also for a connection establishment request, an Msg3PUSCH transmission, and for a contention resolution response and possibly for a connection establishment response, an Msg4PDSCH transmission. Contention resolution (and connection establishment, if applicable) is considered successful if the UE receives the Msg4PDSCH within a certain time window after transmitting Msg3, and also if the contention resolution ID in the Msg4PDSCH matches the ID the UE transmits in the Msg3PUSCH when the UE has not received the C-RNTI. Otherwise, the contention resolution Msg3/4 and thus RA attempts are unsuccessful. The UE may make another RA attempt unless the configured maximum number of RA attempts has been reached, and then the entire RA procedure is declared unsuccessful.

Upon failure of the RA attempt (due to no RAR reception, RAPID in RAR does not match RAPID in Msg1, or contention resolution Msg3/4 fails), the UE may perform a new RACH resource selection for the new RA attempt, including selecting DL RS associated with PRACH transmission, selecting PRACH preamble, and selecting RO. Thus, a different SSB/CSI-RS and/or a different PRACH preamble and/or a different RO may be used for PRACH transmission for the new RA attempt than for the previous RA attempt. However, if the same DL RS is used in PRACH transmission for both the new RA attempt and the previous RA attempt, only the power ramp is applied.

In the following and throughout the disclosure, various embodiments of the present disclosure may also be implemented in any type of UE, including, for example, UEs with the same, similar, or more capabilities than a conventional 5G NR UE. Although various embodiments of the present disclosure discuss a 3GPP 5g NR communication system, these embodiments may generally be applied to UEs operating with other RATs and/or standards (e.g., next release/generation of 3GPP, IEEE WiFi, etc.).

In the following, unless explicitly stated otherwise, providing parameter values by higher layers includes providing parameter values by a System Information Block (SIB), such as SIB1, or by common RRC signaling or by UE-specific RRC signaling.

Hereinafter, the association between DL RSs, such as SS/PBCH blocks (SSBs) or CSI-RSs, and PRACH preambles is determined with respect to path loss for calculating the power of PRACH preamble transmission, and with respect to quasi-co-location (QCL) attribute or Transmission Configuration Indicator (TCI) status, as described in REF 3.

The 5G NR radio supports Time Division Duplex (TDD) operation and Frequency Division Duplex (FDD) operation. The use of FDD or TDD depends on the NR frequency band and the allocation of each country. TDD is required in most frequency bands above 2.5 GHz.

Fig. 10 illustrates an example diagram 1000 of an example structure of a slot of a TDD communication system according to an embodiment of the present disclosure. The diagram 1000 is for illustration only, and other embodiments may be used without departing from the scope of the present disclosure.

Diagram 1000 depicts a DDDSU UL-DL configuration. Note that D denotes DL slots, U denotes UL slots, and S denotes special or switching slots with DL portions, flexible portions that can also be used as guard period G for DL-to-UL switching, and optionally UL portions.

TDD has many advantages over FDD. For example, the same frequency band for DL and UL transmissions results in a simpler UE implementation with TDD, as a duplexer is not required. Another advantage is that time resources can be flexibly allocated to UL and DL in consideration of asymmetric ratios of traffic in two directions. DL is typically allocated most of the time resources in TDD to handle DL heavy mobile traffic. Another advantage is that CSI can be more easily acquired via channel reciprocity. This reduces the overhead associated with CSI reporting, especially when there are a large number of antennas.

Although TDD has advantages over FDD, there are drawbacks. The first drawback is that TDD has a smaller coverage due to the fact that typically a small fraction of the time resources are available for UL transmission, whereas with FDD all time resources can be used for UL transmission. Another disadvantage is the time delay. In TDD, the timing gap between DL reception and UL transmission containing hybrid automatic repeat request acknowledgement (HARQ-ACK) information associated with DL reception is typically larger than in FDD, e.g., a few milliseconds. Thus, the HARQ round trip time in TDD is typically longer than that of FDD, especially when DL traffic load is high. This results in increased UL user plane delay in TDD and may lead to data throughput loss or even HARQ stalling when the PUCCH providing HARQ-ACK information needs to be retransmitted in order to improve coverage (an alternative in this case is that the network discards the HARQ-ACK information at least for some transport blocks in DL).

Embodiments of the present disclosure consider that in order to address some of the drawbacks of TDD operation, dynamic adaptation of link direction has been considered, where the symbols of a slot may have a flexible direction (UL or DL) that a UE may determine from scheduling information for transmission or reception, in addition to some symbols in some slots supporting a predetermined transmission such as SSB. The PDCCH may also be used to provide a DCI format, such as DCI format 2_0 as described in REF3, which may indicate the link direction of some flexible symbols in one or more slots. However, in practical deployments, it is difficult for the gNB scheduler to adapt the transmission direction of the symbols without coordination with other gNB schedulers in the network. This is due to Cross Link Interference (CLI), where, for example, DL reception by a UE in a cell may experience large interference from UL transmissions from other UEs in the same or neighboring cells.

Full Duplex (FD) communication offers the potential to increase spectral efficiency, improve capacity, and reduce latency in wireless networks. When FD communication is used, UL and DL signals are received and transmitted simultaneously on fully or partially overlapping or adjacent frequency resources, thereby improving spectral efficiency and reducing latency in the user and/or control plane.

There are several options for operating a full duplex wireless communication system. For example, a single carrier may be used such that transmissions and receptions are scheduled on the same time domain resource (such as a symbol or slot). The transmission and reception on the same symbol or slot may be separated in frequency, for example by placement in non-overlapping subbands. In time domain resources that also include DL frequency subbands, UL frequency subbands may be located in the center of the carrier, or at edges of the carrier, or at selected frequency domain locations of the carrier. The allocations of DL subbands and UL subbands may also overlap partially or even completely. The gNB may use the same physical antennas, antenna ports, antenna panels, and transmitter-receiver units (TRX) to transmit and receive simultaneously in time domain resources. The transmission and reception in the FD may also occur using separate physical antennas, ports, panels or TRXs. The antennas, ports, panels, or TRXs may also be partially reused, or when FD communication is enabled, only the corresponding subset may be active for transmission and reception.

Instead of using a single carrier, different Component Carriers (CCs) may also be used for reception and transmission by the UE. For example, reception by the UE may occur on a first CC and transmission by the UE occurs on a second CC that has a small (including zero) frequency separation from the first CC.

Further, even when the UE is still operating in half-duplex mode, such as when the UE is unable to transmit and receive simultaneously, the gNB (such as BS 102) may operate in full-duplex mode or the UE may be able to do full-duplex operation.

Full duplex transmission/reception is not limited to the gNB, TRP or UE, but may also be used for other types of wireless nodes, such as relay or repeater nodes.

Full duplex operation needs to overcome several challenges in order to work in a practical deployment. When overlapping frequency resources are used, the received signal is affected by co-channel CLI and self-interference. CLI and self-interference cancellation methods include passive methods that rely on isolation between transmit and receive antennas, active methods that utilize RF or digital signal processing, and hybrid methods that use a combination of active and passive methods. Filtering and interference cancellation may be implemented in RF, baseband (BB), or both RF and BB. While mitigating co-channel CLI may require a large complexity at the receiver, it is feasible within current technical limitations. Another aspect of FD operation is to mitigate adjacent channel CLI, because in several cellular band allocations, different operators have adjacent spectrum.

Throughout this disclosure, cross-division duplexing (XDD) is used as a short form of full duplex operation. The terms XDD and full duplex are used interchangeably throughout this disclosure.

Full duplex operation in NR can improve spectral efficiency, link robustness, capacity, and latency of UL transmissions. In an NR TDD system, UL transmission is limited by fewer transmission opportunities than DL reception. For example, for NR TDD with scs=30 kHz, DDDU (2 ms), DDDSU (2.5 ms) or DDDDDDDSUU (5 ms), UL-DL configuration allows DL: UL ratio from 3:1 to 4:1. any UL transmission can only occur in a limited number of UL slots, for example every 2, 2.5 or 5 milliseconds, respectively.

Fig. 11 illustrates an example diagram 1100 of two example full duplex configurations according to embodiments of the disclosure. The diagram 1100 is for illustration only, and other embodiments may be used without departing from the scope of the present disclosure.

For a single carrier TDD configuration with full duplex enabled, the time slot denoted X is a full duplex or XDD time slot. Both DL and UL transmissions may be scheduled for at least one or more symbols in an XDD slot. The term XDD slot is used to refer to a slot in which a UE can simultaneously receive and transmit in at least one or more symbols of the slot if the base station schedules or allocates radio resources. The half duplex UE cannot transmit and receive simultaneously in the XDD slot or on the symbol of the XDD slot. When a half-duplex UE is configured for transmission in the symbols of an XDD slot, another UE may be configured for reception in the symbols of the XDD slot. Full duplex UEs may transmit and receive simultaneously in the symbols of the XDD slot, possibly in the case that there are other UEs in the symbols of the XDD slot that schedule or allocate resources for the DL or UL. The transmission of the UE in the first XDD slot may use the same or different frequency domain resources as in the second XDD slot, wherein the resources may differ in terms of bandwidth, location of the first RB or the center carrier.

For a full duplex enabled dual carrier (carrier aggregation) TDD configuration, the UE receives in a slot on CC #1 and transmits in at least one or more symbols of the slot on CC # 2. Full duplex slots with both transmissions/receptions by the gNB or UE occurring on the same time domain resources (such as slots or symbols) are marked by X, except for D slots for transmission/reception only by the gNB/UE, U slots for reception/transmission only by the gNB/UE, and S slots for supporting DL-UL handover as well. For the example of TDD with scs=30 kHz, single carrier and UL-DL allocation DXXSU (2.5 ms), the second and third time slots allow full duplex operation. UL transmissions may also occur in the last time slot (U) where full UL transmission bandwidth is available. The XDD slot or symbol allocation over the time period/slots may be indicated by the DCI format in PDCCH reception and may then be changed per unit time period, or may be indicated by higher layer signaling, such as via MAC CE or RRC.

Note that robust network operation uses UEs (such as UE 116) that are capable of establishing a connection to the network over a large coverage area without consuming significant resources and without requiring large delays to establish the connection. Accordingly, embodiments of the present disclosure contemplate the need to increase the signal-to-interference-and-noise ratio (SINR) of PRACH reception at a gNB, such as BS102, in order to increase PRACH coverage. Embodiments of the present disclosure also contemplate the need to dimension PRACH capacity in a cell area to achieve a target collision probability for PRACH transmissions from a UE for an expected number of concurrent multiple access attempts by the UE. Embodiments of the present disclosure also contemplate the need to reduce the delay due to UL-DL frame alignment delay during the RA procedure, which represents the delay until the next PRACH transmission opportunity occurs.

The PRACH transmission requires several operational limitations when considering that the UE needs to transmit multiple channels and signals. RBs in UL slots or symbols that are fully or partially occupied by transmission of PRACH preambles are typically not available for other transmissions, such as for PUSCH. For example, in NR, transmission of a short PRACH preamble prevents m×12 RBs per RO in Frequency Division Multiplexing (FDM) from being used for PUSCH transmission. For a 15kHz SC, the long preamble occupies m×6 or m×24 RBs, and for a 30kHz SC, the long preamble occupies m×3 or m×12 RBs, where m=1 …. The first result is a decrease in the absolute number of schedulable UL RBs in UL slot (U) and a corresponding decrease in UL peak data rate. The second result is that PUSCH transmissions cannot be allocated a large continuous BW depending on the placement of RACH opportunities in the carrier bandwidth. In NR Rel-15, the UE is forced to support only UL resource allocation type 1 requiring frequency-continuous PUSCH allocation. Thus, PUSCH frequency allocation can only be completely lower or completely higher than PRACH allocation BW, and PUSCH cannot be scheduled in frequency across ROs. Even if the UE implementation complexity is increased to support UL resource allocation type 0 using RBG-based allocation, additional power backoff of up to several dB is required for the corresponding PUSCH transmission. This results in a significant data rate reduction due to the lower SINR operating point.

Embodiments of the present disclosure address the above-described problems by implementing PRACH transmissions in full duplex time domain resources, such as in slots or symbols that are received and transmitted while supporting a UE or a gNB.

Fig. 12 shows an example diagram 1200 of an example RACH configuration using XDD in accordance with an embodiment of the disclosure. The diagram 1200 is for illustration only, and other embodiments may be used without departing from the scope of the disclosure.

The PRACH preamble transmission is configured in the third and fourth XDD slots in addition to the last UL slot (U). In general, the RA procedure related transmissions may be enabled in the symbols of the XDD slot, including some or all of Msg1 to Msg4 and possibly repetition. The first PRACH transmission in the XDD slot may be followed by a second PRACH transmission in the UL slot (U), or vice versa.

A first motivation to place PRACH transmissions fully or partially in XDD slots is to increase the data rate in U slots, because the absolute number of schedulable RBs is increased, and a large number of consecutive RBs can be allocated to a UE by removing the RBs allocated to the PRACH preamble. The second motivation is the ability to have larger contiguous RB allocations for PRACH transmission. For TDD and scs=30 kHz, only a short PRACH preamble format may be used when a single UL slot (U) is available. Longer PRACH preamble formats necessarily require more than one time slot. By allowing PRACH transmission in N consecutive slots (such as n=2 or n=4 slots) that include XDD slots and may also include UL slots, a long PRACH preamble format may be used, thereby increasing the range of timing estimates and achievable accuracy of PRACH reception. A third motivation is to reduce the complexity of the base station. When one or more UEs transmit corresponding PUSCHs in XDD slots, interference cancellation from DL signals needs to be designed to receive UL signals, which may have substantially different transmission bandwidths or MCS settings, such as for receiving PUSCHs from different UEs, which may be at different power levels at the base station receiver or use different MCSs for the corresponding transport blocks. Transmitting the PRACH preamble in the XDD slot requires that the base station only perform interference cancellation based on one specific signal type, such as the Zadoff-Chu sequence used as the PRACH preamble, thereby simplifying the implementation of interference cancellation. The fourth motivation is that PRACH resources are used only when the UE actually transmits the corresponding PRACH even when the PRACH resources are configured in XDD slots. In several cases, depending on the RACH dimension, PRACH transmission will not occur in XDD slots configuring PRACH transmission. Therefore, the provision of PRACH resources in XDD slots does not generally produce DL-UL interference.

Several problems need to be overcome when considering resource selection and parameterization in the time, frequency and power domains of PRACH resources with full duplex operation in XDD slots. The first problem involves handling delays and signal distortions caused by a Serial Interference Cancellation (SIC) base station at the receiver to completely or partially remove interference from concurrent transmissions on the received signal (e.g., PRACH preamble). SIC processing may produce additional time delay responses due to RF and BB filtering and may cause signal energy loss due to FFT misalignment, which affects PRACH reception reliability in XDD slots.

The second problem relates to the different link conditions that need to be considered for Msg1 and Msg3 transmissions in the normal UL and XDD slots. Similarly, msg2 and Msg4 reception by a UE may be subject to unequal and different reception conditions in XDD slots, where concurrent transmissions from other UEs may be present in some symbols, and in normal DL slots, where concurrent transmissions from other UEs may not be present in any symbols. These different reception conditions are due to antenna and panel design and deployment constraints. The number of TRX chains for transmission or reception, or the area for the transmission or reception antennas available in the normal DL or UL slots and XDD slots may be different between the full duplex implementation and the half duplex implementation. This is due to antenna design constraints that achieve adequate spatial isolation between Tx and Rx antenna ports in full duplex operation. For example, reception at a base station in a normal UL slot may benefit from using 32 TRXs of a 12V x 8H x 2P panel size of 40 x 60cm, while reception at a base station in an XDD slot may use only 16 TRXs and a portion or panel having half the size in the UL slot.

A third problem relates to constraints arising from the need to coexist with legacy UEs. When in rrc_idle or rrc_inactive mode, all UEs acquire the same RACH configuration parameter set from SIB1 through a cell (re) selection procedure using prior art operation. Therefore, it is currently impossible to allocate different RACH configurations to a legacy UE and a XDD operation-supporting UE.

A fourth problem relates to the constraints caused by the currently possible RACH frame, subframe, slot and starting symbol allocations. Not all possible combinations may currently be allocated using a TDD mapping table corresponding to frequency range 1 (FR 1) for carrier frequencies below 6 GHz. For example, it is impossible to allocate RACH in time slot 3-7 or 5-6. This is due to the assumption that only a limited number of PRACH transmission opportunities are available in TDD. However, in the case of full duplex operation, there are more UL transmission opportunities, and the existing RACH configuration then becomes unnecessarily limited.

Embodiments of the present disclosure address the above-described problems and provide additional design aspects for supporting random access procedures, wherein some or all of the associated messages are transmitted in whole or in part in XDD slots, and provide solutions as fully set forth below.

The present disclosure contemplates methods for random access resource selection, determination and selection of PRACH configuration, determination and verification of ROs, and determination of RACH time domain frame, time slot, and starting symbol allocation.

In the following and throughout the disclosure, some configurations, scheduling or resource allocation of the gnbs may assume that the UE is aware of XDD-specific provisions in the gnbs. For example, the UE may signal to the gNB that it supports XDD specific provisioning through a UE capability query procedure. The gNB may also use common DL signaling such as SI to signal XDD specific configuration, scheduling, or resource allocation. When using the asn.1 extension, legacy UEs will ignore such configuration, whereas UEs supporting XDD specific provision may use either or both legacy and XDD configurations. The gNB (such as BS 102) may also derive knowledge of the XDD specific specifications supported by the UE by other means (e.g., implicitly). For example, the gNB may derive knowledge of the specification that a particular UE supports XDD-specific, because the UE uses a set of specified and known (for the gNB) XDD radio resources.

Accordingly, embodiments of the present disclosure describe methods for resource selection and determination of PRACH resources by a UE (such as UE 116) in a wireless system supporting full duplex. Embodiments of the present disclosure describe an RSRP-based PRACH resource selection procedure that distinguishes in the time domain (RACH slot and symbol group) if normal slots and full duplex slots are used for RACH message 1. Embodiments of the present disclosure also describe multiple RACH configurations provided to the UE, including the possibility to use different target Rx power levels for normal (full) UL slots and full duplex slots. Embodiments of the present disclosure further describe network controlled and UE-determined masking of RACH opportunities to selectively enable/disable configured ROs for full duplex slots. In addition, embodiments of the present disclosure describe additional time domain allocations for TDD RACH to enable access to full duplex time slots, which would be DL only in a conventional TDD system.

In certain embodiments, PRACH preamble transmissions configured by RACH configuration in the symbols of XDD slot(s) are associated with an RSRP threshold. The UE, such as UE 116, determines whether PRACH preamble transmission is allowed in the symbols of the XDD slot or whether the RO is valid according to the RSRP threshold.

The first RSRP threshold for XDD slots may be the same or different from the second RSRP threshold in the complete UL slot if the second RSRP threshold is provided. The RSRP threshold may be associated with measurements based on the received SSB or CSI-RS. The UE (such as UE 116) may derive the measurements using one or more samples obtained from one or more measurement instances, may average or filter the measurements, or may use instantaneous sample values. The RSRP threshold may be fixed in the specification or provided by a higher layer, e.g. by the first system information block (SIB 1). The RSRP threshold may be signaled by the MAC CE. The RSRP threshold may be an absolute value or an offset value signaled relative to another RSRP threshold, such as an RSRP value for PRACH transmissions on the primary UL carrier or the supplemental UL carrier. For PRACH transmissions with repetition, different RSRP ranges may be associated with the same number of repetitions in the XDD and full UL slots, or different numbers of repetitions may be associated with the same RSRP ranges in the XDD and full UL slots. The association may be provided, for example, by SIB 1. The association may be applied to a slot, symbol, or set of slots and symbols. The association may be applied to a given timing relationship, for example for the same time slot or for a later time slot or symbol. The motivation is to adjust UL coverage and PRACH link budget during the random access procedure by the UE in XDD slots. The PRACH transmission received by the base station in the XDD slot and the normal UL slot may experience different link conditions due to possibly different beamforming and/or processing gains at the base station. Embodiments may be applied before and/or after the UE operates in RRC connected mode and/or may be provided by UE-specific or common configurations.

For example, when configuring an FR1 unpaired spectrum (TDD) random access configuration with a PRACH configuration index 81, the subframe number 4, 9 in each frame may include ROs using 6 a1 2 symbol groups starting from symbol 0. For scs=30 kHz, slot numbers 8 and 18 are thus configured for RO and may support PRACH transmission. When the first slot is an XDD slot and the second slot is a normal UL slot, a first RSRP threshold and a second RSRP threshold are configured for the first slot and the second slot, respectively. A larger RSRP threshold may be configured for the first slot to account for lower Rx beamforming gain, with less available TRX for reception in the XDD slot.

The RSRP threshold associated with Msg1 transmissions may be the same for a set of slots or symbols (such as XDD slots or UL slots or flexible symbols or UL symbols) and for PRACH preamble type and RO configuration. In another example, the RSRP threshold may include multiple settings for a slot or set of symbols (such as XDD slot or UL slot or flexible symbol or UL symbol) and for PRACH preamble type and RO configuration.

For another example, an RSRP threshold associated with the Msg1 transmission may be used to authenticate or de-authenticate the RO. The RO in the XDD slot may be used for random access if the RSRP threshold associated with the SSB or CSI-RS exceeds a predetermined level. If the RSRP threshold does not exceed the predetermined level, only ROs that meet the selected condition are valid for PRACH transmission. For example, a first subset of time slots is allowed for random access, but a second subset of time slots is not allowed. The predetermined level may be provided by a specification of system operation or may be provided by a higher layer, such as by system information.

Fig. 13 and 14 illustrate an example PRACH resource selection processing chain according to an embodiment of the disclosure. In particular, fig. 13 shows an example diagram 1300 of a PRACH resource selection configuration using RSRP according to an embodiment of the present disclosure. Fig. 14 illustrates an example method 1400 for PRACH resource selection processing chain using RSRP according to an embodiment of this disclosure. The steps of method 1400 of fig. 14 may be performed by any of UEs 111-116 of fig. 1, such as UE 116 of fig. 3. The diagram 1300 and method 1400 are for illustration only, and other embodiments may be used without departing from the scope of the disclosure.

In some embodiments, a UE (such as UE 116) determines one or more RSRP threshold offset values for random access resource selection. The random access resource may include one or more ROs allocated in a symbol of the XDD slot. The UE measures RSRP of one or more received SSB indices or NZP CSI-RS configurations. The UE determines whether the RO occurs in the full/normal UL slot or in the XDD slot. If the RO occurs in the full/normal UL slot, the UE validates the RO when there is an SSB with an SS-RSRP higher than the RSRP-ThresholdSSB. If RO occurs in XDD slots, the UE only if there is an SS-RSRP higher than RSRP-ThresholdSSB+offset _xdd Is to verify the RO at SSB. offset (offset) _xdd The value may be provided by a higher layer, such as by a first system information block (SIB 1), e.g., by the same element that provides rsrp-threshssb. Alternatively, instead of offset _xdd The higher layer may provide the parameter RSRP-threshold SSB-XDD and the UE verifies RO only if there is an SSB with SS-RSRP higher than RSRP-threshold SSB-XDD.

As shown in fig. 14, in step 1410, a UE (such as UE 116) measures SS-RSRP on one or more SSBs. In step 1120, the UE determines whether the RO occurs in the XXD slot. When the RO occurs in the XDD slot (as determined in step 1420), the electronic device adjusts the measured SS-RSRP value by the XDD offset value in step 1430. When the RO does not occur in the XXD slot (as determined in step 1420) or after the UE adjusts the measured SS-RSRP value by the XDD offset value (when the RO occurs in the XXD slot, as determined in step 1420), the electronic device verifies the RO in step 1440 if the measured and adjusted value is greater than a threshold denoted as RSRP-threshold ssb.

Although fig. 14 illustrates method 1400, various changes may be made to fig. 14. For example, while method 1400 is shown as a series of steps, various steps may overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, steps may be omitted or replaced by other steps. For example, the steps of method 1400 may be performed in a different order.

In some embodiments, a UE (such as UE 116) determines and selects an applicable RACH configuration for transmission of a PRACH preamble from a set of candidate RACH configurations.

RACH configuration may be provided by higher layers via common RRC signaling (such as through system information) or via UE-specific RRC signaling. The information may also include conditions for using RACH configuration. The embodiments may be applied before and/or after the UE operates in the RRC connected mode. RACH configuration may be provided by RRC and may be activated or deactivated using MAC CE. The first RACH configuration and the second RACH configuration may differ in at least one configuration parameter. The RACH configuration includes a combination of at least one, some or all of the following configuration parameters. The parameter denoted as 'PRACH-configuration index' represents an available set of PRACH opportunities for transmitting random access preambles. The parameter denoted 'preamble receivedtargetpower' represents the initial random access preamble power. The parameter denoted 'RSRP-ThresholdSSB' represents the RSRP threshold for SSB selection. The parameter denoted 'RSRP-threshold CSI-RS' represents the RSRP threshold for CSI-RS selection. The parameter denoted as 'candidatebeam rslist' represents a list of reference signals (CSI-RS and/or SSB) identifying candidate beams and associated random access parameters for recovery. The parameter denoted as 'recoupersearchspace' represents a search space set identity for monitoring the PDCCH to detect a DCI format providing a response to a beam-fault-recovery request. The parameter denoted 'powerramsingstep' represents the power ramp factor. The parameter denoted 'powerrammingstephighhpority' represents the power ramp factor for the prioritized random access procedure. The parameter denoted 'scalable factor bi' represents a scaling factor for prioritizing the random access procedure. The parameter denoted as 'ra-preambieindex' denotes a random access preamble. The parameter denoted 'ra-SSB-occidionmassindex' defines the PRACH opportunity associated with SSB from which the MAC entity can select for transmission of the random access preamble by the physical layer. A parameter denoted as 'ra-accasionlist' defines the PRACH opportunity associated with CSI-RS from which the MAC entity may select for transmission of the random access preamble by the physical layer. The parameter denoted 'ra-preambisetindex' represents the start index of the random access preamble for the on-demand SI request. The parameter denoted 'preambmantamax' represents the maximum number of random access preamble transmissions. The parameter denoted as 'SSB-perRACH-occidionandbb-preambibesperssb' defines the number of SSBs mapped to each PRACH opportunity and the number of contention-based random access preambles mapped to each SSB. The parameter denoted 'groupBconfigured' indicates whether an indication of the random access preamble group B is configured. The parameter denoted 'ra-Msg3SizeGroupA' represents a threshold value for determining the set of random access preambles. The parameter denoted 'Msg3-DeltaPreamble' represents Δpreamble_msg3. The parameter denoted 'messagePowerOffsetGroupB' represents the power offset for preamble selection. The parameter denoted as 'numberOfRA-preambiresgroup' defines the number of random access preambles in the random access preamble set a of each SSB, such as (i) a set of random access preambles and/or PRACH opportunities (if any) for SI requests; (ii) A set of random access preambles and/or PRACH opportunities (if any) for a beam-failure recovery request; (iii) A set of random access preambles and/or PRACH opportunities for reconfiguration with sync. The parameter denoted as 'RA-ResponseWindow' represents the time window in which RA response is monitored. The parameter denoted as 'ra-contentionresolution timer' represents a contention resolution timer. The parameter denoted 'msg1-FDM' indicates the number of PRACH transmission opportunities for FDM in one time instance. The parameter denoted 'msg1-FrequencyStart' represents the offset of the lowest PRACH transmission opportunity in the frequency domain relative to Physical Resource Block (PRB) zero. The parameter denoted 'powerramsingstep' represents the power ramp step size of the PRACH. The parameter denoted 'preablereceivedtargetpower' represents the target received power level at the base station/network. The parameter denoted as 'zerocorerelationship zoneconfig' represents the NCS configuration. The additional parameters may also be part of the RACH configuration.

For example, when configuring an FR1 unpaired spectrum (TDD) random access configuration with PRACH configuration index 81, the subframe numbers 4, 9 in each frame may carry ROs using 6 a1 2 symbol groups starting from symbol 0. For scs=30 kHz, slot numbers 8 and 18 are thus configured for PRACH transmission. When the first slot is an XDD slot and the second slot is a normal UL slot, a first preamblyReceivedTargetPowerfor-80 dBm is configured for the XDD slot over the first RACH and a second preamblyReceivedTargetPowerwith the largest possible setting of-60 dBm is configured for the normal/full UL slot over the second RACH. The first RACH configuration and the second RACH configuration in this example may be configured the same except that their associated preablereceivedtargetpower values are different. The association of the preamblyreceivedtargetpower value with the RACH slot or RO is provided to the UE. Alternatively, the UE is provided with a RACH configuration (such as with index 81) having an associated preamble receivedtargetpower value and its associated slot or RO. Then, the UE derives the first RACH configuration by applying the standard of preablereceivedtargetpower = -80dBm and derives the second RACH configuration by applying the standard of preablereceivedtargetpower = -60 dBm.

The motivation is to adjust the received power level at the base station during the random access procedure by the UE in the XDD slot. When PRACH transmissions are received in normal/full UL slots, PRACH detection may be handled by the base station without any DL interference, thereby maximizing UL coverage and using full processing gain at the base station. The PRACH transmission received and processed by the base station in XDD slots or symbols may be subject to Rx power constraints in view of the interference cancellation capability of the base station. In addition, by using separate power settings in a full duplex system, control of UL-DL cross link interference generated by UEs transmitting PRACH preambles and affecting UEs received in the DL portion of an XDD slot may be facilitated.

For another example, for FR1 unpaired spectrum random access, a first RACH configuration using PRACH configuration index 77 is provided. Subframe 9 in each frame may include ROs using 6 a 12 symbol groups starting with symbol 0. For scs=30 kHz, slot number 18 is thus configured for PRACH. A second RACH configuration using PRACH configuration index 12 is provided. Subframe 4 (or slot 7) in each frame may include ROs using long preamble format 0 with 1.25kHz, which has a duration exceeding one slot. Thus, PRACH preamble transmission in subframe 4 or 9 uses a different PRACH preamble provided by a separate RACH configuration. The motivation is to enable UEs that do not support XDD/full duplex operation to access a cell using a short preamble in a normal UL slot, whereas UEs that support XDD/full duplex operation may use a preamble format that is more suitable for DL-UL interference conditions that may be experienced by transmission/reception in an XDD slot.

Fig. 15 illustrates an example diagram 1500 of determining the configuration and use of RACH configurations according to an embodiment of this disclosure. The diagram 1500 is for illustration only, and other embodiments may be used without departing from the scope of the present disclosure.

A UE, such as UE 116, determines a first RACH configuration and a second RACH configuration. The UE selects the applicable RACH configuration according to the time slots or symbol resources available for random access (PRACH preamble transmission). The UE then applies some or all of the parameters given by the selected RACH configuration and uses the selected RACH configuration parameters to perform preamble transmission.

In some embodiments, a UE (such as UE 116) uses a bitmap provided by a serving base station (such as through system information) or uses selected rules to verify and/or disable RACH opportunities in full duplex slots or symbols.

For example, when configuring FR1 unpaired spectrum random access configuration with PRACH configuration index 81, the subframe number 4, 9 in each frame may include RO using 6 a1 2 symbol groups starting from symbol 0. For scs=30 kHz, slot numbers 8 and 18 are thus configured for PRACH. When the first slot is an XDD slot and the second slot is a normal UL slot, the UE applies the bit map to determine a time domain RO valid for PRACH transmission in the first XDD slot. For example, a bitmap of size 6 and bitmap value of "010101" disables every other RO in slot 8, where "1" indicates "allowed" RO and "0" indicates "not allowed" RO.

For another example, RACH configuration using PRACH configuration index 108 is provided when using FR1 unpaired spectrum random access. Subframes 1, 3, 5, 7, 9 (or slots 2, 6, 10, 14, 18) in each frame may include ROs using 3 a2 4 symbol groups starting at symbol 0. For example, a bit map of size 5 and having a value of "11110" (where "1" indicates "allowed" RO and "0" indicates "not allowed" RO) disables all ROs in the slot 18.

The motivation is to simplify the base station implementation for interference cancellation and to improve PRACH reception reliability in full duplex slots. Base station interference cancellation removes interference from the transmitted DL signal, which includes nonlinear distortion introduced by base station transmitter RF from the received UL signal during full duplex operation. This creates a filter response that affects the samples of the subsequently received OFDM symbol. The SINR of the received UL signal decreases. In the case of random access, an RO (such as a previous symbol group) may distort signal reception in a next subsequent RO (such as a symbol group). For common PRACH detection implementations, there are constraints on placement of FFT window size and accumulation of detected energy levels across symbols when processing the received RACH preamble in RO. By disabling certain ROs, the base station receiver becomes easier to implement DTX detection (determine that no received signal is present) and enables reliable PRACH detection when the timing uncertainty is greater than 1 symbol. Both the coherent and noncoherent detectors may be implemented by the base station.

The one or more bitmaps of fixed or indicated length may be signaled to the UE (such as UE 116), for example, by system information or by UE-specific RRC. The bitmap applies only to slots that include ROs, where each bit represents a time domain RO or RO over more than one RACH slot. For RACH configurations, multiple bitmaps may be used to determine the effective RO, a first bitmap per symbol group per slot, a second bitmap per slot. The bit map may have a length of change predetermined in the specification of system operation or signaled by common or UE-specific RRC. For example, a bitmap verifying a 6RO configuration per slot with 2 symbols per RO may be 6 bits long, while a bitmap verifying a single 6 symbol group starting at symbol 7 may be 1 bit long.

Alternatively, the UE may verify the RO using specified rules. For example, every other RO in the XDD slot configured for RACH is not allowed and is invalidated. For example, every nth RO starting from ro#m is disabled. RO can be verified in both the time and frequency domains. For example, the bitmap may validate or invalidate ROs allocated across RACH frequency domains in a slot. The value and number of bitmaps used to verify and process ROs may be signaled to the UE by higher layers, such as through RRC or MAC CE. The higher layer signaling may be UE-specific or common to all UEs. The condition may be applied to rrc_idle, rrc_inactive, and rrc_connected modes.

Fig. 16 illustrates an example PRACH allocation and configuration according to an embodiment of this disclosure. The diagram 1600 is for illustration only, and other embodiments may be used without departing from the scope of the present disclosure.

The UE determines at least one RO mask bitmap. The UE applies the RO mask bitmap according to whether the selected slot or symbol configured for the PRACH is used for full duplex transmission. The UE randomly selects ROs from the remaining allowed RO sets for PRACH preamble transmission.

In some embodiments, the UE is configured with different sets of RACH frames, subframes, slots, and starting symbol mappings to determine the applicable RACH subframes, RACH slots, and starting symbols for PRACH preamble transmission in a full duplex slot.

The RACH frame, subframe, slot or starting symbol may be obtained as an additional index value of the parameter prach-configuration index, or by using a second mapping table, or by using the parameter prach-configuration index from an existing mapping table, and then remapping the obtained value by using a fixed or tabulated set or configurable set of subframe, slot or symbol offset values. For example, an FR1 (or FR 2) mapping table for use by a TDD UE may be configured by using an FR1 (or FR 2) FDD mapping table.

The following example uses the A1 preamble format from REF1 table 6.3.3.2, -3 shown in table (2) for illustration purposes. Specifically, table (2) describes preamble A1 format configuration FR1 TDD. For the specific case of RACH frame, subframe and slot mapping of the (non-mixed) A1 preamble format, the allocation case shown in table (2) is currently possible according to the NR specifications. However, the same design considerations may be extended directly to other preamble formats, such as 0, 1, 2, 3 or A1, A2, A3, B1, B4, C0, C2 or any mixed format not shown, as will be apparent to those skilled in the art.

For example, the alternative mapping table is provided by higher layers to the UE for use in full duplex slots. For example, table (3) shows an alternative set of PRACH frames, slots and starting symbol mappings for the A1 format. The RACH frame and slot map is located earlier in the UL-DL frame configuration period to account for UL transmission opportunities provided by full duplex operation in the DL slots. For example, an index value 73 valid for an alternative mapping table as shown in table 3 allows PRACH in subframes 5, 6. Thus, PRACH resources may be allocated to XDD slots in DDXXDDSUU UL-DL frame allocation. For example, SIB or UE specific RRC signaling may provide for configuration of such an alternative mapping table. The use of an alternative PRACH mapping table may also depend on whether the operation is in rrc_idle, or rrc_inactive, or rrc_connected mode.

TABLE 2

For another example, the exemplary values shown in table (3) may be indicated by an additional or extended set of index values for the parameter prach-configurationindex. Specifically, table (3) describes the preamble A1 format configuration of FR1 TDD using the alternative mapping table. For example, using an existing prach-configuration index of 8 bits and providing a prach-configuration index of additional 3 bits, the combinations 67-86 from table (3) are indicated as index values 256+ (67, …, 86) =323, …,342.

TABLE 3

For another example, the higher layer may provide one or more offset or adjustment values to determine the frame, subframe slot, and starting symbol mapping. For example, the frame offset X1, the subframe offset X2, the slot offset X3, and the starting symbol offset X4 can be provided to the UE in conjunction with existing prach-ConfigurationIndex N. Upon receiving PRACH configuration index value N (e.g., n=73), the UE can determine subframes 7 and 9 as providing PRACH allocation. When a set of adjustment values (x1=0, x2=2, x3=0, x4=0) is signaled to the UE, the subframe positions (7-X2, 9-X2) = (5, 7) are used for PRACH transmission in the XDD slots. In this example, all other parameters derived from the table (such as frame, number of slots, start symbol) are unchanged. Alternatively, such applicable relative configuration parameters may be fixed in the system specification. Multiple sets of adjustment values may be used by signaling or by an index set. Furthermore, the use of a specific set of adjustment values may be made and occur only when certain transmission conditions are applicable, such as when certain Tx or Rx power levels are met.

The motivation is to allocate PRACH transmissions from UEs in subframes and slots implemented using full duplex in a cell and to increase the available UL transmission resources in the normal/full UL slots for PUSCH transmissions, thereby enabling an increase in the achievable UL data rate.

Fig. 17 shows a block diagram of a terminal (or User Equipment (UE)) according to an embodiment of the present disclosure.

As shown in fig. 17, a terminal according to an embodiment may include a transceiver 1710, a memory 1720, and a controller 1730. The transceiver 1710, the memory 1720, and the controller 1730 of the terminal may operate according to the communication methods of the terminal described above. However, the components of the terminal are not limited thereto. For example, the terminal may include more or fewer components than those depicted in fig. 17. In addition, the controller 1730, the transceiver 1710, and the memory 1720 may be implemented as a single chip. Further, the controller 1730 may include at least one processor.

The transceiver 1710 is collectively referred to as an end station receiver and a terminal transmitter, and may transmit/receive signals to/from a base station or another terminal. The signals transmitted to or received from the terminal may include control information and data. The transceiver 1710 may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal, and an RF receiver for low noise amplifying and down-converting the frequency of a received signal. However, this is merely an example of the transceiver 1710, and components of the transceiver 1710 are not limited to an RF transmitter and an RF receiver.

Further, the transceiver 1710 may receive and output signals to the controller 1730 through a wireless channel, and transmit signals output from the controller 1730 through a wireless channel.

The memory 1720 may store programs and data required for the operation of the terminal. In addition, the memory 1720 may store control information or data included in a signal obtained by the terminal. Memory 1720 may be a storage medium such as Read Only Memory (ROM), random Access Memory (RAM), hard disk, CD-ROM, and DVD, or a combination of storage media.

The controller 1730 may control a series of processes so that the terminal operates as described above. For example, the controller 1730 may transmit data signals and/or control signals to a base station, and the controller 1730 may receive data signals and/or control signals from the base station.

As shown in fig. 18, a base station of the present disclosure may include a transceiver 1810, a memory 1820, and a controller 1830. The memory 1810 of the transceiver, the base station 1820, and the controller 1830 may operate according to the communication methods of the base station described above. However, the composition of the base station is not limited thereto. For example, the base station may include more or fewer components than those depicted in fig. 18. In addition, the controller 1830, transceiver 1810 and memory 1820 may be implemented as a single chip. Further, the controller 1830 may include at least one processor.

The transceiver 1810 is collectively referred to as a base station receiver and a base station transmitter, and may transmit/receive signals to/from a terminal, another base station, and/or a core network function (or entity). The signals transmitted to or received from the base station may include control information and data. The transceiver 1810 may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal, and an RF receiver for amplifying the frequency of a low noise and down-converted received signal. However, this is merely an example of transceiver 1810 and components of transceiver 1810 are not limited to RF transmitters and RF receivers.

In addition, the transceiver 1810 may receive and output signals to the controller 1830 through a wireless channel, and transmit signals output from the controller 1830 through the wireless channel.

The memory 1820 may store programs and data required for operation of the base station. Further, the memory 1820 may store control information or data included in signals obtained by the base station. The memory 1820 may be a storage medium such as ROM, RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

The controller 1830 may control a series of processes such that the base station operates as described above. For example, the controller 1830 may receive data signals and/or control signals from the terminal, and the controller 1830 may send data signals and/or control signals to the terminal.

The methods according to the embodiments described in the claims or the detailed description of the present disclosure may be implemented in hardware, software, or a combination of hardware and software.

When the electrical structure and method are implemented in software, a computer-readable recording medium having one or more programs (software modules) recorded thereon may be provided. One or more programs recorded on the computer-readable recording medium are configured to be executable by one or more processors in the electronic device. The one or more programs include instructions for performing the methods of the embodiments described in the claims or the detailed description of the disclosure.

The program (e.g., software module or software) may be stored in Random Access Memory (RAM), non-volatile memory including flash memory, read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disk storage devices, compact disk-ROM (CD-ROM), digital Versatile Disks (DVD), another type of optical storage device, or a tape cartridge. Alternatively, the program may be stored in a memory system comprising a combination of some or all of the above memory devices. Further, a plurality of memory devices may be included.

The program may also be stored in an attachable storage device that is accessible through a communication network such as the internet, an intranet, a Local Area Network (LAN), a Wireless LAN (WLAN), or a Storage Area Network (SAN), or a combination thereof. According to embodiments of the present disclosure, a storage device may be connected to an apparatus through an external port. Another storage device on the communication network may also be connected to an apparatus that performs embodiments of the present disclosure.

In the foregoing embodiments of the present disclosure, elements included in the present disclosure are represented in singular or plural form according to the embodiments. However, for convenience of explanation, singular or plural forms are appropriately selected, and the present disclosure is not limited thereto. Thus, elements expressed in plural may also be configured as a single element, and elements expressed in singular may also be configured as a plurality of elements.

Although the figures show different examples of user equipment, various changes may be made to the figures. For example, the user device may include any number of each component in any suitable arrangement. In general, the drawings do not limit the scope of the disclosure to any particular configuration. Further, while the figures illustrate an operating environment in which the various user device features disclosed in this patent document may be used, these features may be used in any other suitable system.

Although the present disclosure has been described with exemplary embodiments, various changes and modifications may be suggested to one skilled in the art. The disclosure is intended to embrace such alterations and modifications that fall within the scope of the appended claims. No description in this application should be construed as implying that any particular element, step, or function is a essential element which must be included in the claims scope. The scope of patented subject matter is defined by the claims.

Claims

1. A method performed by a User Equipment (UE) in a wireless communication system, the method comprising:

and (3) receiving:

first information for a first parameter of a first Random Access Channel (RACH) configuration associated with a first subset of time slots from a set of time slots on a cell, and

Second information for a second parameter of a second RACH configuration associated with a second subset of time slots from the set of time slots on the cell;

determining a RACH configuration for Physical Random Access Channel (PRACH) transmission in a time slot on the cell among the first RACH configuration and the second RACH configuration based on whether the time slot is from a first subset of time slots or a second subset of time slots; and

based on the determined RACH configuration, the PRACH is transmitted in a time slot on the cell.

2. The method according to claim 1, wherein:

the time slots from the first subset of time slots are not indicated for simultaneous transmission and reception during the same time domain resource on the cell, an

The time slots from the second subset of time slots are indicated for simultaneous transmission and reception during the same time domain resource on the cell.

3. The method of claim 1, further comprising:

identifying a first parameter of a first RACH configuration; and

determining a second parameter of the second RACH configuration based on the first parameter and an adjustment value included in the second information,

wherein transmitting the PRACH in the time slot further comprises transmitting the PRACH in the time slot based on the second parameter.

4. The method of claim 1, wherein determining a RACH configuration further comprises: selecting a RACH configuration for transmission of a PRACH in a slot based on a configurable signal power or signal quality threshold for a first subset of slots or a second subset of slots including the slot, and

Wherein receiving the second information comprises receiving the second information in a system information block (SIB 1).

5. A User Equipment (UE) in a wireless communication system, the UE comprising:

a transceiver configured to receive:

second information for a second parameter of a second RACH configuration associated with a second subset of time slots from the set of time slots on the cell; and

a processor operably coupled to the transceiver, the processor configured to: determining a RACH configuration for Physical Random Access Channel (PRACH) transmission in a time slot on the cell among the first RACH configuration and the second RACH configuration based on whether the time slot is from a first subset of time slots or a second subset of time slots,

wherein the transceiver is further configured to transmit the PRACH in a time slot on the cell based on the determined RACH configuration.

6. The UE of claim 5, wherein the transceiver is further configured to receive signaling to:

7. The UE of claim 5, wherein:

the processor is further configured to:

identifying a first parameter of a first RACH configuration

Determining a second parameter of the second RACH configuration based on the first parameter and an adjustment value included in the second information, an

The transceiver is further configured to transmit the PRACH in a time slot based on the second parameter.

8. The UE of claim 5, wherein the processor is further configured to: selecting a RACH configuration for transmission of a PRACH in a slot based on a configurable signal power or signal quality threshold for a first subset of slots or a second subset of slots including the slot, an

Wherein the transceiver is configured to receive the second information in a system information block (SIB 1).

9. A base station in a wireless communication system, the base station comprising:

a transceiver configured to transmit:

A processor operably coupled to the transceiver, the processor configured to: based on whether the time slot is from a first subset of time slots or a second subset of time slots, determining a RACH configuration for reception of a Physical Random Access Channel (PRACH) in a time slot on the cell,

wherein the transceiver is further configured to: based on the determined RACH configuration, the PRACH is received in a slot.

10. The base station of claim 9, wherein the transceiver is further configured to transmit signaling for:

11. The base station of claim 9, wherein:

the processor is further configured to:

identifying a first parameter of a first RACH configuration

The transceiver is further configured to receive the PRACH in a time slot based on the second parameter.

12. The base station of claim 9, wherein:

The processor is further configured to: determining a signal power or signal quality threshold for a first subset of time slots or a second subset of time slots including the time slot to indicate a RACH configuration for transmission of a PRACH in the time slot, an

The transceiver is further configured to transmit information indicative of a signal power or signal quality threshold, and

wherein the transceiver is configured to transmit the second information in a system information block (SIB 1).

13. A method performed by a base station in a wireless communication system, the method comprising:

and (3) transmitting:

determining a Physical Random Access Channel (PRACH) configuration for reception in a time slot on a cell based on whether the time slot is from a first subset of time slots or a second subset of time slots; and

based on the determined RACH configuration, the PRACH is received in a slot.

14. The method of claim 13, further comprising:

Transmitting signaling for:

15. The method of claim 13, further comprising:

identifying a first parameter of a first RACH configuration;

determining a second parameter of the second RACH configuration based on the first parameter and an adjustment value included in the second information;

receiving the PRACH in the slot based on the second parameter;

determining a signal power or signal quality threshold for a first subset of time slots or a second subset of time slots including the time slot to indicate a RACH configuration for transmission of a PRACH in the time slot;

transmitting information indicative of a signal power or signal quality threshold

Wherein the second information is transmitted in a system information block (SIB 1).