Preamble transmission for code word based random access communication

Abstract

Certain aspects of this disclosure provide techniques for codeword-based random access communication. A method for wireless communication by an apparatus includes: transmitting a signal in one or more time-frequency resources of a random access channel (RACH), wherein the signal is multiplexed using codewords, the one or more time-frequency resources and the codewords defining a preamble signature; and communicating with a network entity at least in part based on the signal.

Description

Cross-references to related applications

[0001] This patent application claims priority and benefit to U.S. Provisional Application No. 63 / 603,980, filed November 29, 2023, and U.S. Patent Application No. 18 / 899,684, filed September 27, 2024, the entire contents of which are hereby expressly incorporated by reference. Background Technology Technical Field

[0002] Various aspects of this disclosure relate to wireless communications, and more specifically to techniques for random access communications.

[0003] Related technical descriptions

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, broadcasting, or other similar services. These wireless communication systems may employ multiple access technologies that enable communication with several users by sharing available wireless communication system resources.

[0005] Despite significant technological advancements in wireless communication systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and receivers. Therefore, there is a continuous expectation for improving the technical performance of wireless communication systems, including, for example: improving communication speed and data carrying capacity; improving the efficiency of shared communication media; reducing the power used by transmitters and receivers during communication; improving the reliability of wireless communication; avoiding redundant transmission and / or reception and related processing; improving the coverage area of ​​wireless communication; increasing the number and types of devices that can access the wireless communication system; increasing the ability of different types of devices to communicate with each other; and increasing the number and types of available wireless communication media. Therefore, there is a need for further improvements to wireless communication systems to overcome the aforementioned technical challenges and other obstacles. Summary of the Invention

[0006] One aspect provides a method for wireless communication by an apparatus (e.g., user equipment). The method includes: transmitting a signal in one or more time-frequency resources of a random access channel (RACH), wherein the signal is multiplexed using codewords, the one or more time-frequency resources and the codewords define a preamble signature; and communicating with a network entity at least in part based on the signal.

[0007] On the other hand, a method for wireless communication by a device (e.g., a network entity) is provided. The method includes: obtaining a signal in one or more time-frequency resources of a RACH, wherein the signal is multiplexed using codewords, the one or more time-frequency resources and the codewords defining a preamble signature; and communicating with a user equipment (UE) at least in part based on the signal.

[0008] Other aspects provide: one or more means capable of operating to, configured to, or otherwise adapted to perform any part of any method described herein (e.g., such that execution can be implemented by only one means or in a distributed manner across multiple means); one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of the one or more means, cause the one or more means to perform any part of any method described herein (e.g., such that instructions can be included in only one computer-readable medium or in a distributed manner across multiple computer-readable media, such that instructions can be executed by only one processor or by multiple processors in a distributed manner, such that one or more processors can perform any part of any method described herein). Each of the following apparatuses may include one or more processors, and / or enable execution to be performed by only one apparatus or in a distributed manner across multiple apparatuses; one or more computer program products embodied on one or more computer-readable storage media including code for performing any part of any method described herein (e.g., enabling the code to be stored in only one computer-readable medium or in a distributed manner across computer-readable media); and / or one or more apparatuses including one or more components for performing any part of any method described herein (e.g., enabling execution to be performed by only one apparatus or by multiple apparatuses in a distributed manner). By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system cooperating via one or more networks.

[0009] For illustrative purposes, the following description and figures illustrate certain features. Attached Figure Description

[0010] The accompanying drawings depict certain features of the various aspects described herein and should not be considered as limiting the scope of this disclosure.

[0011] Figure 1 An example wireless communication network is depicted.

[0012] Figure 2 An example decomposed base station architecture is described.

[0013] Figure 3Various aspects of the example base station and example user equipment (UE) are described.

[0014] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures used in wireless communication networks are described.

[0015] Figure 5A This is an example process flowchart illustrating an example four-step random access procedure performed between a UE and a network entity.

[0016] Figure 5B This is an example process flowchart illustrating an example two-step random access procedure performed between a UE and a network entity.

[0017] Figure 6 This is a diagram illustrating an example narrowband physical random access channel resource grid using code division multiplexing for random access preamble transmission.

[0018] Figure 7 This is a diagram illustrating an example arrangement for Random Access Channel (RACH) resources.

[0019] Figure 8 The process flow for communication between the UE and network entities in the network is described.

[0020] Figure 9 A method for wireless communication is described.

[0021] Figure 10 Another method for wireless communication is described.

[0022] Figure 11 Various aspects of the example communication device are described.

[0023] Figure 12 Various aspects of the example communication device are described. Detailed Implementation

[0024] This disclosure provides apparatus, methods, processing systems, and computer-readable media for preamble transmission in codeword-based random access communication.

[0025] Certain wireless communications (e.g., narrowband Internet of Things (NB-IoT) communications for Evolved Universal Terrestrial Radio Access (E-UTRA) systems and / or 5G New Radio (NR) systems) may use a designated set of resources for random access to the Radio Access Network (RAN). For example, a certain number of subcarriers may be allocated to an NB-IoT device in a narrowband Physical Random Access Channel (NPRACH) to randomly select random access to the RAN. In some respects, where the RAN is discussed herein as performing one or more operations, such operations may be performed by one or more network entities of the RAN (e.g., base stations and / or their decomposed entities).

[0026] Technical challenges in narrowband communication may include, for example, providing sufficient capacity for random access communication. As the number of deployed NB-IoT devices increases within the RAN's coverage area (e.g., with the increased adoption of IoT devices communicating with Wireless Wide Area Networks (WWANs), the likelihood of NB-IoT devices using the same subcarrier for random access may increase. In such cases, with multiple NB-IoT devices transmitting via the same subcarrier used for random access, the RAN may be unable to decode and respond to certain random access transmissions from the NB-IoT devices (e.g., RACH preambles or MSG3 transmissions). Therefore, NB-IoT devices may perform an increased number of RACH attempts to establish a communication link with the RAN.

[0027] Some aspects of this disclosure can overcome the aforementioned technical problems, for example, by providing an architecture associated with preamble transmission for codeword-based random access communication. Codeword-based random access communication can use code division multiplexing to effectively increase the resources available for random access communication. In some aspects, the UE can (randomly) select codewords for preamble transmission from a set of codewords designated or configured for codeword-based random access communication. In some aspects, codeword-based RACH communication (e.g., preamble transmission) can be assigned certain resources (e.g., frequency resources and / or time resources). In some cases, codeword random access resources can be separated from resources used for other types of random access communication (e.g., non-codeword-based random access communication). In some cases, codeword random access resources can be shared (overlapping) with resources used for other types of random access communication.

[0028] The techniques described herein for codeword-based random access preamble (RACH) communication offer a variety of technical effects and / or advantages. For example, the preamble communication described herein can improve wireless communication performance, including, for example, increased throughput, reduced latency, and / or increased random access channel capacity. The improved performance can be attributed to codeword-based RACH communication, which can be facilitated by preamble communication, as further described herein. For example, codeword-based RACH communication can achieve increased RACH communication capacity; the increased capacity can achieve reduced latency, for example, because network entities are able to successfully decode the preamble transmission and respond accordingly.

[0029] An introduction to wireless communication networks

[0030] The techniques and methods described herein can be used in a variety of wireless communication networks. Although aspects herein may be described using terms commonly associated with 3G, 4G, 5G, 6G, and / or other generations of wireless technologies, aspects of this disclosure are equally applicable to other communication systems and standards not explicitly mentioned herein.

[0031] Figure 1 An example of a wireless communication network 100 in which the aspects described herein can be implemented is depicted.

[0032] Generally, wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). Network entities are typically communication devices and / or communication functions performed by communication devices (e.g., user equipment (UE), base station (BS), components of a BS, servers, etc.). Since such communication devices are part of wireless communication network 100 and facilitate wireless communication, they may be referred to as wireless communication devices. For example, various functions of the network and various devices associated with and interacting with the network may be considered network entities. Furthermore, wireless communication network 100 includes terrestrial and non-terrestrial aspects (also referred to herein as non-terrestrial network entities). Terrestrial aspects include terrestrial network entities such as terrestrial network entities (e.g., BS 102), and non-terrestrial aspects include satellite 140 and aircraft 145. These non-terrestrial aspects may include onboard network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., terrestrial BSs) and UEs.

[0033] In the depicted example, wireless communication network 100 includes BS 102, UE 104 and one or more core networks (such as Evolved Packet Core (EPC) 160 and 5G Core (5GC) network 190) that interoperate to provide communication services over various communication links, including wired and wireless links.

[0034] Figure 1Various example UEs 104 are described, which may more generally include: cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players, cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, Internet of Things (IoT) devices, always-on (AON) devices, edge processing devices, data centers, or other similar devices. UE 104 may also be more generally referred to as mobile devices, wireless devices, stations, mobile stations, subscriber stations, mobile subscriber stations, mobile units, subscriber units, wireless units, remote units, remote devices, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, and others.

[0035] BS 102 communicates wirelessly with UE 104 via communication link 120 (e.g., sending or receiving signals to or from UE 104). Communication link 120 between BS 102 and UE 104 may include uplink (UL) transmission (also referred to as reverse link) from UE 104 to BS 102 and / or downlink (DL) transmission (also referred to as forward link) transmission from BS 102 to UE 104. In various aspects, communication link 120 may utilize multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity.

[0036] BS 102 may typically include: NodeB, enhanced NodeB (eNB), next-generation enhanced NodeB (ng-eNB), next-generation NodeB (gNB or gNodeB), access point, transceiver base station, radio base station, radio transceiver, transceiver functionality, transmit / receive point, and / or others. Each of BS 102 provides communication coverage for a corresponding coverage area 110, which may sometimes be referred to as a cell, and in some cases may overlap (e.g., a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, BS may provide communication coverage for macro cells (covering a relatively large geographic area), pico cells (covering a relatively small geographic area, such as a stadium), femtocells (covering a relatively small geographic area (e.g., a home)), and / or other types of cells.

[0037] Generally, a cell can refer to a portion, partition, or segment of wireless communication coverage served by network entities within a wireless communication network. A cell can have geographical characteristics (such as a geographical coverage area) and radio frequency characteristics (such as time and / or frequency resources dedicated to the cell). For example, multiple cells employing different frequency resources (e.g., bandwidth portions) and / or different time resources can cover a specific geographical coverage area. As another example, a single cell can cover a specific geographical coverage area. In some contexts (e.g., carrier aggregation scenarios and / or multi-connectivity scenarios), the terms "cell" or "serving cell" can refer to or correspond to a specific carrier frequency (e.g., component carrier) used for wireless communication, and "cell group" can refer to or correspond to multiple carriers used for wireless communication. As an example, in a carrier aggregation scenario, a UE can communicate on multiple component carriers corresponding to multiple (serving) cells in the same cell group, and in a multi-connectivity (e.g., dual-connectivity) scenario, a UE can communicate on multiple component carriers corresponding to multiple cell groups.

[0038] Although BS 102 is described as a single communication device in various aspects, it can be implemented in a variety of configurations. For example, to give a few examples, one or more components of the base station can be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC. In another example, various aspects of the base station can be virtualized. More generally, a base station (e.g., BS 102) can include components located at a single physical location or components located at various physical locations. In examples where the base station includes components located at various physical locations, the various components can each perform functions, such that the various components collectively achieve functionality similar to a base station located at a single physical location. In some aspects, a base station including components located at various physical locations can be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0039] Different BSs 102 within the wireless communication network 100 can also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with 5GC 190 via a second backhaul link 184. BSs 102 can communicate directly or indirectly (e.g., via EPC 160 or 5GC 190) on a third backhaul link 134 (e.g., X2 interface), which can be wired or wireless.

[0040] Wireless communication network 100 can subdivide the electromagnetic spectrum into various categories, bands, channels, or other characteristics. In some aspects, subdivision is provided based on wavelength and frequency, where frequency may also be referred to as carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410MHz to 7125MHz, which is often (interchangeably) referred to as “sub-6GHz”. Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250MHz to 71,000MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). In some cases, FR2 can be further defined according to subranges (such as a first subrange FR2-1 including 24,250MHz to 52,600MHz and a second subrange FR2-2 including 52,600MHz to 71,000MHz). Base stations configured to communicate using mmWave / near mmWave radio bands (e.g., mmWave base stations such as BS 180) can utilize beamforming (e.g., 182) with UEs (e.g., 104) to improve path loss and range.

[0041] The communication link 120 between BS 102 and, for example, UE 104 can be via one or more carriers, which may have different bandwidths (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz and / or other MHz) and may be aggregated in various ways. The carriers may be adjacent to each other or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL).

[0042] Compared to lower-frequency communication, communication using higher frequency bands may have higher path loss and shorter range. Therefore, some base stations (e.g., Figure 1 The beamforming 182 of the BS 180 (180) with the UE 104 can be used to improve path loss and range. For example, the BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BS 180 may transmit beamformed signals to the UE 104 in one or more transmit directions 182''. The UE 104 may receive beamformed signals from the BS 180 in one or more receive directions 182''. The UE 104 may also transmit beamformed signals to the BS 180 in one or more transmit directions 182''. The BS 180 may also receive beamformed signals from the UE 104 in one or more receive directions 182''. The BS 180 and UE 104 may then perform beamforming training to determine the optimal receive and transmit directions for each of the BS 180 and UE 104. It is worth noting that the transmit and receive directions of the BS 180 may be the same or different. Similarly, the sending and receiving directions of UE 104 can be the same or different.

[0043] The wireless communication network 100 further includes a Wi-Fi AP 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 in, for example, unlicensed spectrum in 2.4 GHz and / or 5 GHz.

[0044] Some UEs 104 may use device-to-device (D2D) communication link 158 to communicate with each other. The D2D communication link 158 may use one or more sidelink channels, such as physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH), and / or physical sidelink feedback channel (PSFCH).

[0045] EPC 160 may include various functional components, including: Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and / or Packet Data Network (PDN) Gateway 172, as in the illustrated example. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connectivity management.

[0046] Generally, user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP services 176, which may include, for example, the Internet, intranets, IP Multimedia Subsystem (IMS), packet-switched (PS) streaming services, and / or other IP services.

[0047] The BM-SC 170 provides functions for MBMS user service dispatch and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and / or schedule MBMS transmissions. The MBMS Gateway 168 can distribute MBMS services to BS 102 within a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and / or be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0048] 5GC 190 may include various functional components, including: Access and Mobility Management Function (AMF) 192, other AMFs 193, Session Management Function (SMF) 194, and User Plane Function (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196.

[0049] AMF 192 is the control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides services such as Quality of Service (QoS) flow and session management.

[0050] Internet Protocol (IP) packets are transmitted via UPF 195, which connects to IP service 197 and provides UE IP address allocation and other functions for 5GC 190. IP service 197 may include, for example, the Internet, intranet, IMS, PS streaming service, and / or other IP services.

[0051] In various aspects, to give a few examples, network entities or network nodes can be implemented as aggregated base stations, decomposed base stations, components of base stations, integrated access and backhaul (IAB) nodes, relay nodes, and sidelink nodes.

[0052] Figure 2An example decomposed base station 200 architecture is depicted. The decomposed base station 200 architecture may include one or more central units (CUs) 210, which may communicate directly with the core network 220 via a backhaul link, or indirectly with the core network 220 through one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a Service Management and Orchestration (SMO) framework 205, or both. CUs 210 may communicate with one or more distributed units (DUs) 230 via corresponding midhaul links (such as F1 interfaces). DUs 230 may communicate with one or more radio units (RUs) 240 via corresponding fronthaul links. RUs 240 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some specific implementations, UE 104 may be served simultaneously by multiple RUs 240.

[0053] Each unit in a cell (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO frame 205) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the cells, or an associated processor or controller that provides instructions to the cell's communication interface, may be configured to communicate with one or more other cells via the transmission medium. For example, these cells may include a wired interface configured to receive signals or transmit signals to one or more other cells via a wired transmission medium. Additionally or alternatively, a cell may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive signals on a wireless transmission medium or transmit signals to one or more other cells, or both.

[0054] In some aspects, CU 210 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by CU 210. CU 210 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP)), control plane functions (e.g., Central Unit-Control Plane (CU-CP)), or combinations thereof. In some implementations, CU 210 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, CU-UP units can communicate bidirectionally with CU-CP units via an interface such as an E1 interface. CU 210 can be implemented to communicate with DU 230 for network control and signaling, as needed.

[0055] DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 240s. In some aspects, DU 230 may at least partially host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) according to functional splits (such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0056] Lower-layer functionality can be implemented by one or more RU 240s. In some deployments, the RU240 controlled by the DU 230 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both, based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UE 104s. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration allows the DU 230 and CU 210 to be implemented in cloud-based RAN architectures such as vRAN architectures.

[0057] SMO framework 205 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 205 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 205 can be configured to interact with cloud computing platforms such as Open Cloud (O-Cloud) 290 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, SMO framework 205 may communicate with hardware aspects of the 4G RAN, such as Open eNB (O-eNB) 211, via the O1 interface. Additionally, in some implementations, the SMO framework 205 may communicate directly with one or more DU 230s and / or one or more RU 240s via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205.

[0058] The non-RT RIC 215 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 225. The non-RT RIC 215 can be coupled to or communicate with the near-RT RIC 225, such as via an A1 interface. The near-RT RIC 225 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 210s, one or more DU 230s, or both, and O-eNBs to the near-RT RIC 225.

[0059] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 225 and may be received from non-network data sources or network functions at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 205 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0060] Figure 3 Various aspects of examples BS 102 and UE 104 are described.

[0061] Generally, BS 102 includes various processors (e.g., 318, 320, 330, 338, and 340), antennas 334a to 334t (collectively referred to as 334), transceivers 332a to 332t (collectively referred to as 332) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., data source 312) and the wireless reception of data (e.g., data sink 314). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement the various wireless communication-related functions described herein.

[0062] Generally, UE 104 includes various processors (e.g., 358, 364, 366, 370, and 380), antennas 352a to 352r (collectively referred to as 352), transceivers 354a to 354r (collectively referred to as 354) including modulators and demodulators, and other aspects that enable the wireless transmission of data (e.g., retrieval from data source 362) and the wireless reception of data (e.g., provision to data sink 360). UE 104 includes a controller / processor 380 that can be configured to implement the various wireless communication-related functions described herein.

[0063] Regarding example downlink transmission, BS 102 includes a transmission processor 320 that can receive data from data source 312 and control information from controller / processor 340. This control information may be for a Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid Automatic Repeat Request (HARQ) Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GC PDCCH), and / or others. In some examples, this data may be for a Physical Downlink Shared Channel (PDSCH).

[0064] The transmitter processor 320 can process data and control information (e.g., encoding and symbol mapping) to obtain data symbols and control symbols, respectively. The transmitter processor 320 can also generate reference symbols (such as those for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), and channel state information reference signal (CSI-RS)).

[0065] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols where applicable, and can provide the output symbol stream to the modulators (MODs) in transceivers 332a to 332t. Each modulator in transceivers 332a to 332t can process the corresponding output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from the modulators in transceivers 332a to 332t can be transmitted via antennas 334a to 334t, respectively.

[0066] To receive downlink transmissions, UE 104 includes antennas 352a to 352r that receive downlink signals from BS 102 and provide the received signals to demodulators (DEMODs) in transceivers 354a to 354r, respectively. Each demodulator in transceivers 354a to 354r can adjust (e.g., filter, amplify, down-convert, and digitize) the corresponding received signal to obtain an input sample. Each demodulator can further process the input sample to obtain the received symbols.

[0067] The RX MIMO detector 356 acquires received symbols from all demodulators in transceivers 354a to 354r, performs MIMO detection on the received symbols where applicable, and provides the detected symbols. The receive processor 358 processes the detected symbols (e.g., demodulation, deinterleaving, and decoding), provides the decoded data of UE 104 to data sink 360, and provides the decoded control information to controller / processor 380.

[0068] Regarding the example uplink transmission, UE 104 further includes a transmission processor 364 that receives and processes data from data source 362 (e.g., for PUSCH) and control information from controller / processor 380 (e.g., for Physical Uplink Control Channel (PUCCH)). Transmission processor 364 can also generate reference symbols for reference signals (e.g., for Sounding Reference Signal (SRS)). Symbols from transmission processor 364 may be pre-decoded by TX MIMO processor 366, where applicable, further processed by modulators in transceivers 354a to 354r (e.g., for SC-FDM), and transmitted to BS 102.

[0069] At BS 102, uplink signals from UE 104 can be received by antennas 334a to 334t, processed by demodulators in transceivers 332a to 332t, detected where applicable by RX MIMO detector 336, and further processed by receiver processor 338 to obtain decoded data and control information transmitted by UE 104. Receiver processor 338 can provide the decoded data to data sink 314 and the decoded control information to controller / processor 340.

[0070] Memory 342 and memory 382 can store data and program code for BS 102 and UE 104, respectively.

[0071] Scheduler 344 can schedule UE to send data on the downlink and / or uplink.

[0072] In various respects, BS 102 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 312, scheduler 344, memory 342, transmit processor 320, controller / processor 340, TX MIMO processor 330, transceivers 332a to 332t, antennas 334a to 334t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 334a to 334t, transceivers 332a to 332t, RX MIMO detector 336, controller / processor 340, receive processor 338, scheduler 344, memory 342, and / or other aspects described herein.

[0073] In various respects, UE 104 can also be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms that output data, such as from data source 362, memory 382, ​​transmit processor 364, controller / processor 380, TX MIMO processor 366, transceivers 354a to 354t, antennas 352a to 352t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms that acquire data, such as from antennas 352a to 352t, transceivers 354a to 354t, RX MIMO detector 356, controller / processor 380, receive processor 358, memory 382, ​​and / or other aspects described herein.

[0074] In some respects, the processor can be configured to perform various operations (such as those associated with the methods described herein) and to send (output) data to or receive data from another interface configured to send or receive data, respectively.

[0075] In various aspects, artificial intelligence (AI) processors 318 and 370 may perform AI processing for BS 102 and / or UE 104, respectively. AI processor 318 may include AI accelerator hardware or circuitry, such as one or more neural processing units (NPUs), one or more neural network processors, one or more tensor processors, one or more deep learning processors, etc. AI processor 370 may similarly include AI accelerator hardware or circuitry. As an example, AI processor 370 may perform AI-based beam management, AI-based channel state feedback (CSF), AI-based antenna tuning, and / or AI-based positioning (e.g., Global Navigation Satellite System (GNSS) positioning). In some cases, AI processor 318 may use hardware-accelerated AI inference and / or AI training to process feedback (e.g., CSF) from UE 104. AI processor 318 may, for example, use hardware-accelerated AI inference associated with the CSF to decode compressed CSF from UE 104. In some cases, AI processor 318 may perform certain RAN-based functions, including, for example, network planning, network performance management, energy-efficient network operation, etc.

[0076] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes the use of wireless communication networks (such as Figure 1 All aspects of the data structure of the wireless communication network 100.

[0077] Specifically, Figure 4A Figure 400 is an example of the first subframe within a 5G (e.g., 5G NR) frame structure. Figure 4B Figure 430 illustrates an example of a DL channel within a 5G subframe. Figure 4C Figure 450 illustrates an example of the second subframe within a 5G frame structure, and Figure 4D Figure 480 illustrates an example of a UL channel within a 5G subframe.

[0078] Wireless communication systems can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a cyclic prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single-Carrier Frequency Division Multiplexing (SC-FDM) will (e.g., as...) Figure 4B and Figure 4D The system bandwidth (as depicted in the text) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0079] Wireless communication frame structures can be frequency division duplex (FDD), where for a specific set of subcarriers, subframes within that set are dedicated to either deep (DL) or ultra-low (UL). Wireless communication frame structures can also be time division duplex (TDD), where for a specific set of subcarriers, subframes within that set are dedicated to both DL and UL.

[0080] exist Figure 4A and Figure 4C In this example, the wireless communication frame structure is TDD, where D stands for DL, U for UL, and X is flexibly used between DL and UL. The UE can configure the time slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). In the depicted example, a 10ms frame is divided into 10 equal-sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 12 or 14 symbols, depending on the Cyclic Prefix (CP) type (e.g., 12 symbols per time slot for extended CP, or 14 symbols per time slot for regular CP). Subframes may also include micro-slots, which typically have fewer symbols than the entire time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0081] In some respects, the number of time slots within a subframe (e.g., the time slot duration within a subframe) is based on a parameter set that defines the frequency-domain subcarrier spacing and symbol duration, as further described herein. In some respects, given a parameter set μ, each subframe has 2 μ The number of time slots is 1. Therefore, parameter sets (µ) 0 through 6 allow for 1, 2, 4, 8, 16, 32, and 64 time slots per subframe, respectively. In some cases, extended CP (e.g., 12 symbols per time slot) can be used with specific parameter sets; for example, parameter set 2 allows for 4 time slots per subframe. Subcarrier spacing and symbol length / duration are functions of the parameter set. The subcarrier spacing can be equal to... kHz, where μ is the parameter set from 0 to 6. As an example, the parameter set... Corresponding to a subcarrier spacing of 15 kHz, and the parameter set This corresponds to a subcarrier spacing of 960 kHz. Symbol length / duration is negatively correlated with subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D It provides a slot format with 14 symbols per slot (e.g., regular CP) and a parameter set with 4 slots per subframe. Example. In this case, the slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0082] like Figure 4A , Figure 4B , Figure 4C and Figure 4D As depicted, the resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also known as a physical RB (PRB)) extending for, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme, including, for example, quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM).

[0083] like Figure 4A As illustrated in the example, some REs in the RE carry information for the UE (e.g., Figure 1 and Figure 3 The reference (pilot) signal (RS) for the UE (104) may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0084] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0085] The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is generated by the UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identifier.

[0086] The secondary synchronization signal (SSS) can be located within symbol 4 of a specific subframe of a frame. The SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing.

[0087] Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides the number of RBs and the System Frame Number (SFN) in the system bandwidth. The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information (such as System Information Block (SIB)) not transmitted via the PBCH, and / or paging messages.

[0088] like Figure 4C As illustrated, some REs in the REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE can transmit DMRS for PUCCH and DMRS for PUSCH. PUSCH DMRS can be transmitted, for example, in the first or second symbol before the PUSCH. PUCCH DMRS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and depending on the specific PUCCH format used. UE104 can transmit a Sounding Reference Signal (SRS). SRS can be transmitted, for example, in the last symbol of a subframe. SRS can have a comb structure, and the UE can transmit SRS on one of the comb teeth. SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0089] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0090] Example random access procedure

[0091] Some wireless communication systems (e.g., E-UTRA systems and / or 5G NR systems) can provide designated channels (such as the Random Access Channel (RACH)) and corresponding random access procedures for random access. For example, a UE can use the RACH for initial access to the RAN. Random access procedures can be performed for any of a variety of events, including, for example, initial access from an idle state (e.g., RRC idle), RRC connection re-establishment, handover, downlink (DL) and / or uplink (UL) data arrival (e.g., when the UE is idle), or device location.

[0092] Figure 5A A flowchart illustrating an example four-step RACH procedure 500a performed between UE 504 and network entity 502 is provided. In some respects, UE 504 is about... Figure 1 and Figure 3 The description and depiction of UE 104, and network entity 502 are about Figure 1 and Figure 3 The base station 102 described and depicted or about Figure 2 Decomposed base stations that are described and depicted.

[0093] The RACH procedure 500a may optionally begin at 506, where network entity 502 broadcasts and UE 504 receives the random access configuration, for example, in system information within a synchronization signal block (SSB) or within an RRC message. The random access configuration may indicate or include one or more parameters for random access communication, such as defining the RACH, the number of random access preambles (e.g., preamble sequences) available for random access, power ramp parameters, response window size, etc.

[0094] At 508, UE 504 transmits a first message (MSG1) to network entity 502 on the Physical Random Access Channel (PRACH). In some aspects, MSG1 may indicate or include a RACH preamble. The RACH preamble may indicate or include a preamble signature associated with the RACH preamble. The preamble signature may correspond to a specific preamble sequence (e.g., a Zadoff Chu sequence) generated across the time-frequency resources used for preamble transmission. For contention-based random access, a preamble sequence may be randomly selected from a set of preamble sequences (e.g., in some cases, up to 64 sequences). The preamble signature may be used to identify UE 504 for scheduling communications with network entities (e.g., MSG2 and MSG3). The term "RACH preamble" may refer to or correspond to "random access preamble," "preamble," "preamble sequence," and / or "preamble signature."

[0095] At 510, network entity 502 may respond with a Random Access Response (RAR) message (MSG2). For example, network entity 502 may transmit PDCCH communication including downlink control information (DCI) that schedules the RAR on the PDSCH. The RAR may include, for example, certain parameters for uplink transmission, such as a Random Access (RA) preamble identifier (RAPID), timing advance, uplink (UL) grant (e.g., indicating one or more time-frequency resources for uplink transmission), cell radio network temporary identifier (C-RNTI), and backoff parameter values. The RAPID may correspond to a preamble signature and indicate that the RAR is for UE 504 transmitting MSG1 at 506. As an example, the RAPID may identify a specific frequency resource used for preamble transmission. As further described herein, the backoff parameter values ​​may be used to determine the RACH timing for transmitting subsequent RACH transmissions (e.g., preamble transmissions). The RACH timing may correspond to one or more time resources available for transmitting the preamble in the RACH.

[0096] At 512, in response to MSG2, UE 504 sends a third message (MSG3) on the PUSCH to network entity 502. In some aspects, MSG3 may include an RRC connection request, a tracking area update (e.g., for UE mobility), and / or a scheduling request (for UL transmission). As an example, MSG3 uses the time-frequency resources indicated in the UL approval of the RAR.

[0097] At 514, network entity 502 may transmit a contention resolution message (MSG4) in response to MSG3. Network entity 502 may transmit a downlink scheduling command (e.g., DCI) via PDCCH, which is addressed to a specific UE identity associated with UE 504, as discussed below. Network entity 502 may transmit the UE contention resolution identity (e.g., a media access control element) via PDSCH based on the downlink scheduling command. In some cases, multiple UEs may transmit the same preamble at the same random access time. Since network entity 502 may not be able to identify which UE transmitted which preamble, network entity 502 may respond with a single RAR associated with the preamble. MSG3 may include or indicate a specific UE identity associated with UE 504, such as a Radio Network Temporary Identifier (RNTI) or Temporary Mobile Subscriber Identity (TMSI). Network entity 502 may decode MSG3 and determine the UE identity associated with at least one of the UEs (e.g., UE 504). MSG4 can be addressed to the UE identity associated with MSG3, which network entity 502 can successfully decode (e.g., RNTI or TMSI-based RNTI). For example, MSG4 can be scrambled by the RNTI associated with MSG3. If UE 504 obtains the same identity transmitted in MSG3, UE 504 concludes that the random access procedure was successful. In some cases, if UE 504 cannot receive or decode MSG3 and / or MSG4, UE 504 can repeat the RACH procedure, such as the four-step RACH procedure 500a.

[0098] In some cases, a two-step RACH procedure can be used to reduce latency associated with random access. As the name suggests, a two-step RACH procedure can effectively merge the four messages of a four-step RACH procedure into two messages.

[0099] Figure 5B A flowchart of an example two-step RACH procedure 500b performed between UE 504 and network entity 502 is shown.

[0100] Procedure 500b may optionally begin at 550, where network entity 502 broadcasts and UE 504 receives random access configuration, for example in system information within a synchronization signal block or in an RRC message.

[0101] At point 552, UE 504 transmits a first message (MSGA) to network entity 502, which effectively combines the above-mentioned... Figure 5A MSG1 and MSG3 are described. In some aspects, the MSGA includes a RACH preamble and payload for random access. For example, the payload may include the UE-ID and other signaling information, such as buffer status reports or scheduling requests. For example, the RACH preamble of the MSGA may be transmitted on the RACH, and the payload of the MSGA may be transmitted on the PUSCH.

[0102] At 554, network entity 502 may transmit a Random Access Response Message (MSGB), which can effectively combine MSG2 and MSG4 described above. For example, the MSGB may include RAPID, timing advance, backoff parameter values, contention resolution messages, uplink and / or downlink grant and transmit power control commands.

[0103] Example NB-IoT communication

[0104] Certain wireless communication systems (e.g., E-UTRA systems and / or 5G NR systems) can use a physical layer designed for very low power consumption and low-complexity configurations to enable access to network services, which can be beneficial for Internet of Things (IoT) devices that rely on battery power or power harvesting circuitry for operation. These low-power network services are referred to as narrowband IoT (NB-IoT) communication. For NB-IoT communication, for example, via a full-carrier bandwidth of 180kHz-200kHz and subcarrier spacing of 3.75kHz or 15kHz, a UE may be able to support downlink data rates of up to 68kbps and uplink data rates of up to 132kbps. At this low bandwidth, NB-IoT devices can support low-complexity transceivers to achieve low-cost solutions for IoT devices. In some cases, the UE may be equipped with only a single antenna to facilitate low power consumption. Low power consumption allows NB-IoT devices to operate on battery power for at least 10 years, or almost indefinitely using power harvesting. Those skilled in the art will understand that the specifications associated with NB-IoT communication (e.g., data rate, carrier bandwidth, and / or subcarrier spacing) are merely examples. Other specifications may be used as supplements to or alternatives to those described.

[0105] NB-IoT communication can use a specified set of resources (e.g., RACH subcarriers) for random access to the RAN. For example, up to 48 subcarriers can be allocated to an NB-IoT device in NPRACH to select random access to the RAN. As the number of deployed NB-IoT devices in the RAN increases (e.g., with the increased adoption of wirelessly connected IoT devices), the likelihood of NB-IoT devices using the same subcarriers for random access may increase. In such cases, if multiple NB-IoT devices transmit via the same subcarrier used for random access, the RAN may be unable to decode and respond to certain random access transmissions from the NB-IoT devices (e.g., MSG1 or MSG3 transmissions), for example, due to inferences between overlapping transmissions from multiple NB-IoT devices. Therefore, NB-IoT devices may transmit an increased number of RACH attempts to establish a communication link with the RAN, which can lead to increased latency in establishing the communication link with the RAN. Since the random access procedure is used for various events, its performance affects the performance of various wireless communication activities, such as initial access, handover, UL / DL data arrival, etc.

[0106] Various aspects related to preamble transmission for codeword-based random access communication

[0107] Various aspects of this disclosure provide an architecture associated with preamble transmission for codeword-based random access communication. Codeword-based RACH communication can use code division multiplexing (e.g., orthogonal overlay codes (OCC)) to increase the resources available for random access communication and / or RACH communication, for example, as described herein. Figure 6 As further described above. Codeword-based RACH communication may include codeword-based RACH communication (e.g., MSG1) and / or codeword-based random access communication (e.g., MSG2, MSG3, and / or MSG4).

[0108] In some respects, a UE can (randomly) select a codeword for preamble transmission from a set of codewords designated or configured for codeword-based random access communication. As an example, the selected codeword can be used to generate the baseband signal for preamble transmission. For contention-free random access (CFRA), preamble transmission can be scheduled via scheduling from the RAN, and the scheduling can indicate the codeword to be used for preamble transmission. In some respects, codeword-based RACH communication (e.g., preamble transmission) can be assigned certain resources (e.g., frequency resources and / or time resources). In some cases, codeword random access resources can be separated from resources used for other types of random access communication (e.g., non-codeword-based random access communication). In some cases, codeword random access resources can be shared (overlapping) with resources used for other types of random access communication. For example, a UE supporting codeword-based random access communication can be configured with a probability distribution to select resources for other types of random access communication.

[0109] The apparatus and methods described herein for conveying codeword-based random access preambles can provide various technical effects and / or advantages. For example, the preamble communication described herein can improve wireless communication performance, including, for example, increased throughput, reduced latency, an increased number of devices (e.g., NB-IoT devices) that can access the RACH, and increased resources available for random access. In some aspects, the improved performance can be attributed to the increased RACH resources available for random access facilitated by the codeword-based RACH communication, which can be promoted by the preamble communication described herein. As an example, the codeword-based preamble communication described herein can allow multiple UEs to access overlapping frequency resources, which can increase the resources available for random access communication and allow an increased number of devices to access the RACH.

[0110] Figure 6 This is a diagram illustrating an example NPRACH resource grid 600 using code division multiplexing for random access preamble transmission (e.g., MSG1). In this example, the NPRACH resource grid 600 may include a set of one or more symbol groups 602 arranged across a set of one or more subcarriers 604, which may have a subcarrier spacing of, for example, 3.75 kHz (or 15 kHz). As shown, symbol group 602 may correspond to symbol group index (n), and subcarrier 604 may correspond to preamble index (k) in the NPRACH resource grid 600. In some cases, subcarrier 604 may include a consecutive set of subcarriers and a consecutive set of symbol groups. The NPRACH resource grid 600 may correspond to one or more NPRACH resources. In some cases, the NPRACH resource grid 600 may include a certain number of subcarriers, for example, up to 48 subcarriers.

[0111] A random access preamble (e.g., MSG1) may include a sequence of symbol groups 602 (e.g., symbol groups 602a-d). In some cases, the random access preamble may be transmitted repeatedly, for example, to enhance the reliability of preamble transmission and / or to enhance coverage (e.g., transmission range). As an example, the random access preamble may include one or more preamble repetition units (PRUs) 606a-c, and a PRU (e.g., a first PRU 606a) may include a sequence of one or more symbol groups 602 (e.g., symbol groups 602a-d in the first PRU 606a). Each PRU may correspond to an instance of the random access preamble (also referred to as a repetition). A random access preamble of one symbol group can be sent. Second-rate.

[0112] Symbol group 602 may include symbols having a length (e.g., 66µs or 266µs) cyclic prefix (CP) 608 and having a total length of A sequence of symbols 610 (e.g., symbol duration = 266µs). Utilizing code division multiplexing (e.g., applying M orthogonal overlay codes (OCCs) to the symbol group), M codeword-based symbol groups (e.g., M codeword-based signals with the length of the symbol group) can share the same time-frequency resources (e.g., the same subcarriers in the same symbol group index). For example, a specific codeword can be used to form the baseband signal for the preamble transmission associated with symbol group 602. Therefore, time-frequency resources and codewords can be used to define or form a preamble signature associated with the preamble transmission, and the preamble signature can be used to identify the UE's preamble transmission. Codeword-based symbol groups can allow multiple UEs to transmit on the same NPRACH resource, and therefore, the number of UEs that can simultaneously perform random access without conflict on the NPRACH resource for random access can be increased proportionally to the number of codewords used for code division multiplexing. This increase in the number of UEs that can perform random access without conflict can alleviate channel congestion as more NB-IoT devices are deployed in the network.

[0113] In some cases, the random access preamble may include a sequence of subcarrier frequency hopping symbol groups 602. As an example, the first PRU 606a may include a first symbol group 602a, a second symbol group 602b, a third symbol group 602c, and a fourth symbol group 602d, respectively arranged with symbol group indices 0-3. According to the example frequency hopping mode, the first symbol group 602a is arranged in the subcarrier corresponding to preamble index 6; the second symbol group 602b is arranged in the subcarrier corresponding to preamble index 7; the third symbol group 602c is arranged in the subcarrier corresponding to preamble index 1; and the fourth symbol group 602d is arranged in the subcarrier corresponding to preamble index 0. Similarly, the symbol groups associated with the second PRU 606b and the third PRU 606c may be arranged in the subcarriers of the NPRACH resource grid 600 according to the frequency hopping mode.

[0114] In some respects, each PRU in PRU 606a-c can be arranged in a frequency hopping mode on different subcarriers. In some cases, the frequency hopping mode can be defined relative to the starting subcarrier used for preamble transmission, such as the starting subcarrier of the first PRU during preamble transmission. For example, if multiple UEs select the same starting subcarrier for preamble transmission (e.g., preamble index 6), the frequency hopping mode may result in overlapping preamble transmissions using the same frequency resources.

[0115] Example NPRACH configurations (e.g., provided by RRC signaling and / or system information) may include NPRACH resource periodicity. (NPRACH-Periodicity) — for example, the periodicity of NPRACH, the frequency position of the first subcarrier assigned to NPRACH. (nprach-SubcarrierOffset), the number of subcarriers allocated to NPRACH (nprach-NumSubcarriers) is the number of initial subcarriers allocated to the UE for random access. (nprach-NumCBRA-StartSubcarriers) — For example, the number of subcarriers allocated for CBRA, the number of NPRACH repetitions per attempt. (numRepetitionsPerPreambleAttempt), NPRACH start time (nprach-StartTime), and / or the score used to calculate the starting subcarrier index for the range of NPRACH subcarriers reserved to indicate UE support for multi-tone MSG3 transmission. (nprach-SubcarrierMSG3-RangeStart).

[0116] For contention-based random access (CBRA), the UE can be configured with a codeword set and a subcarrier set, from which the random access preamble is transmitted, for example, as described in this article. Figure 6 As described. As an example, the NPRACH initiation subcarriers assigned to a UE-initiated random access may be arranged in one or more subcarrier sets (e.g., and The second example set (if it exists) can indicate the UE's support for multi-tone MSG3 transmission. If supported by the UE and configured in the narrowband serving cell (Ncell), the OCC codewords to be applied to UE-initiated random access can be selected from the codeword set, which can be specified or configured, for example, by the RAN.

[0117] In some respects, codewords used for codeword-based random access communication can be applied to baseband signals. Baseband signals can be formed at least partially based on codewords. The baseband signals can form a codeword-based preamble signature, or a portion thereof, which can (or may be used to) identify a specific preamble transmission. For example, for a given group of symbols... (such as symbol group 602a) time-continuous random access baseband signals It can be defined by the following formula:

[0118] (1)

[0119] in , It can provide codewords for symbol groups. It can comply with the transmit power control associated with RACH (e.g., The amplitude scaling factor, , This can explain the difference in subcarrier spacing between the random access preamble and uplink data transmission, as well as the parameters. The frequency hopping position in the controlled frequency domain, which can provide the corresponding subcarrier position of a symbol group. Variable This can depend on the preamble format and frame structure, for example, as specified by the 3GPP standard for NB-IoT random access baseband parameters.

[0120] For Contention-Free Random Access (CFRA), the RAN can indicate the codewords for the UE to use for random access preamble transmission. Downlink Control Information (DCI) scheduling random access preamble transmission for CFRA can indicate or include the codewords. For example, DCI format N1 can indicate the starting subcarrier index for NPRACH, the number of repetitions for NPRACH, and the OCC codeword configuration applied across symbol groups. The OCC codeword configuration can indicate the codewords used for preamble transmission. For example, the DCI can indicate the OCC codewords via the OCC indication field in the DCI.

[0121] In some respects, NPRACH resources for codeword-based random access communications can be allocated to the UE in any of various allocations, such as NPRACH resources dedicated to codeword-based RACH communications (dedicated NPRACH resources), a mixture of shared NPRACH resources and dedicated NPRACH resources, and shared NPRACH resources.

[0122] Figure 7 This is a diagram illustrating an example arrangement for RACH resource 700 (e.g., NPRACH resource). In this example, RACH resource 700 may be arranged across frequency bandwidth 702 (e.g., channel bandwidth assigned to the RACH). In some cases, the frequency bandwidth may be or include carrier bandwidth (or any subdivision of the channel or carrier, such as a portion of the bandwidth or a fraction thereof). RACH resource 700 may include one or more first resources 704 and one or more second resources 706. In some cases, each of the first resource 704 and the second resource 706 may include one or more subcarriers 708, such as those described herein. Figure 6 The preamble index described corresponds to the subcarrier. Those skilled in the art will appreciate that one or more first resources 704 and one or more second resources 706 are depicted as adjacent to each other in the frequency domain (e.g., forming a contiguous block of frequency resources) to facilitate understanding. Aspects of this disclosure can be applied to frequency bands arranged between one or more first resources 704 and one or more second resources 706.

[0123] In some respects, NPRACH resources for codeword-based random access communication can be separated from NPRACH resources for other types of random access communication (e.g., non-codeword-based random access). For example, a first set of NPRACH resources can be allocated for codeword-based random access, and a second set of NPRACH resources can be allocated for other types of random access, wherein the first set of NPRACH resources does not overlap with the second set of NPRACH resources. Regarding Figure 7One or more first resources 704 may be dedicated to (e.g., reserved for) codeword-based RACH communication, and one or more second resources 706 may be dedicated to non-codeword-based RACH communication. For example, a UE supporting codeword-based RACH communication may not be allowed to use one or more second resources 706 for codeword-based RACH communication, and a UE not supporting codeword-based RACH communication may not be allowed to use one or more first resources 704 for non-codeword-based RACH communication. The partitioning between one or more first resources 704 and one or more second resources 706 prevents preamble conflicts between OCC-enabled and non-OCC-enabled UEs. Within an OCC partition (e.g., one or more first resources 704), an OCC-enabled UE can use specific OCC codewords that are equivalent to non-codeword-based communication without conflicting with it.

[0124] In some respects, configuration 710 can specify certain characteristics associated with RACH resource 700. Configuration 710 can indicate or include the (total) number 712 of starting subcarriers, the (total) number of subcarriers 714, and / or probability 716 (as further described herein) associated with one or more first resources 704. The number of starting subcarriers 712 and the number of subcarriers 714 can be used to define the frequency position of one or more first resources 704.

[0125] Configuration 710 may be specific to codeword-based RACH communication. For example, control signaling (e.g., system information and / or RRC signaling) may include the `nprach-NumCBRAStartSubcarriers-withOCC` field indicating the value of the number of starting subcarriers 712, and the `nprach-NumSubcarriers-OCC` field indicating the value of the number of subcarriers 714. These fields may be arranged in information elements (IEs), such as `NPRACH-ParametersList-NB-rXX-OCC`. IEs may indicate or include other parameters (carrier-associated) for resources used for OCC enabling. For example, any field associated with the example NPRACH configuration described above may be a codeword-specific field.

[0126] The number of starting subcarriers 712 may indicate the portion of one or more first resources 704 available for codeword-based CBRA (e.g., the number of starting subcarriers allocated to UE-initiated random access), while the number of subcarriers 714 may indicate the total number 708 of subcarriers allocated for codeword-based RACH communication (e.g., CBRA and CFRA), such as the frequency bandwidth (or frequency size) of one or more first resources 704 in terms of subcarriers 708.

[0127] In some respects, a UE supporting codeword-based RACH communication may be allowed to use one or more second resources 706 for RACH communication. Soft partitioning may be used between one or more first resources 704 and one or more second resources 706, and a UE with OCC capability may be configured with statistically defined probabilities. For example, probabilities (e.g., probability distributions) may be specified for a codeword-capable UE to randomly select one or more subcarriers 708 within one or more second resources 706 for codeword-based RACH communication. For example, probability 716 may indicate weights or upper limits used to determine the probabilities. Certain weights or probability values ​​may be included in the OCC IE, where the weights or probability values ​​determine the probability distribution to be used for accessing resources (e.g., one or more second resources 706) in a partition that does not have OCC capability. In some cases, probability 716 may be specific to certain carriers (e.g., NB-IoT carriers). In some cases, the probability 716 for Early Data Transmission (EDT) RA resources may be different for non-EDT RA resources.

[0128] The UE can randomly select one or more second resources 706 from one or more second resources 706 according to a probability distribution configurable based on probability 716. The UE can use a weighted probability for selecting one or more second resources 706 to select resources among one or more first resources 704 and one or more second resources 706. For example, the UE can be configured to use a pseudo-random function to select one or more second resources 706 with a probability of 20%. As an example, a 0% probability can indicate avoiding the use of one or more second resources 706 for codeword-based RACH communication, while a 100% probability can indicate avoiding the use of one or more first resources 704 for codeword-based RACH communication.

[0129] In some aspects, UEs supporting codeword-based RACH communication may be allowed to use any RACH resource in RACH resource 700 for codeword-based RACH communication, and the same applies to UEs that do not support codeword-based RACH communication. For example, UEs without OCC capability and UEs with OCC capability may be allowed to share all NPRACH resources in the NPRACH resource. In some aspects, UEs with OCC capability may not be allowed to use specific codewords for codeword-based RACH communication, such as codewords equivalent to non-codeword-based RACH communication (e.g., codewords all 1s in binary). For example, a UE with OCC capability may receive a configuration indicating one or more values ​​to exclude as codewords (e.g., codewords all 1s in binary). In some cases, UEs with OCC capability may be allowed or disallowed from using codewords equivalent to non-codeword-based RACH communication (e.g., codewords all 1s in binary) based on probability. For example, a UE with OCC capability can receive a configuration indicating the probability of one or more values ​​used to select a codeword, where the values ​​can include a codeword consisting entirely of 1s in binary or any other value. In some cases, the probability can be specific to certain carriers (e.g., NB-IoT carriers). In some cases, the probability for EDT Ra resources can be different for non-EDT Ra resources.

[0130] Example operations of entities in a communication network

[0131] Figure 8 A process flow 800 is described for communication in the network between BS 102 (referred to as a network entity in this example) and UE 104. In some respects, network entity 102 may be relative to... Figure 1 and Figure 3 The base station depicted and described or relative to Figure 2 Examples of decomposed base stations depicted and described herein. However, in other respects, UE 104 may be another type of wireless communication device, and network entity 102 may be another type of network entity or network node, such as those described herein.

[0132] At 802, UE 104 can receive configuration associated with codeword-based random access communication from network entity 102. The configuration may indicate or include any of the various parameters or fields described herein, such as the number of initial subcarriers 712, the number of subcarriers 714, and / or the probability 716. UE 104 can receive the configuration via control signaling, such as system information, RRC signaling, MAC signaling, and / or DCI.

[0133] At 804, UE 104 can determine the resources for codeword-based RACH communication based on its configuration. For example, UE 104 can identify the number of subcarriers allocated for codeword-based RACH communication (e.g., the size of one or more first resources 704) and / or the probability value for selecting shared RACH resources (e.g., one or more second resources 706).

[0134] At position 806, UE 104 sends a random access preamble (MSG1) to network entity 102 in a RACH (such as NPRACH), as described in this document. Figure 6 As described. UE 104 may use one or more of the resources determined at 804 for preamble transmission. The preamble may be multiplexed using codewords, such as codewords associated with orthogonal overlay codes (OCC). In some respects, UE 104 may randomly select codewords from a set of codewords as configured by the RAN and / or specified in certain wireless communication standards, such as the 3GPP standards for NB-IoT communication.

[0135] At 808, UE 104 receives a Random Access Response (RAR) associated with a preamble transmission from network entity 102. The RAR may also be referred to as MSG2. For example, UE 104 may receive a PDCCH transmission that schedules the RAR on the PDSCH from network entity 102. UE 104 may receive a PDSCH transmission carrying the RAR (e.g., a MAC PDU with a RAR payload associated with the preamble) from the network entity according to the scheduling indicated in the DCI. The RAR may provide UL approval for MSG3.

[0136] At 810, in response to MSG2, UE 104 grants permission to send MSG3 to network entity 102 via PUSCH according to the UL indicated in the RAR. In some aspects, MSG3 may include an RRC connection request, a tracking area update, and / or a scheduling request (sent to the UL).

[0137] At 812, UE 104 responds to MSG3 to receive a contention resolution message (MSG4) from network entity 102. In some cases, for example, MSG4 may include an RRC connection establishment message in response to an RRC connection request and / or a UL grant in response to a scheduling request.

[0138] At 814, UE 104 communicates with network entity 102 via RACH communication. As an example, UE 104 can apply any configuration for the communication link between UE 104 and network entity 102, as indicated or included in the RRC connection establishment message. The RRC connection establishment message may indicate or include various configurations, such as configurations for control signaling (e.g., PDCCH or control resource set), PUSCH, PUCCH, PDSCH, transmit power control, channel state feedback reporting (e.g., CSI report), SRS, antenna configuration, and / or scheduling requests. In some respects, the configurations provided in the RRC connection establishment message may facilitate the reception of subsequent configurations. In some cases, UE 104 may grant UL permission to transmit UL signals based on the UL provided in MSG4.

[0139] Those skilled in the art will understand that process flow 800 is an example of a codeword-based CBRA process. Other signaling may be used to supplement or replace the signaling exemplified in process flow 800, such as signaling associated with CFRA processes and / or two-step RACH processes, for example, as described herein. Figure 5B As described herein. As an example, for CFRA, UE 104 can receive DCI based on codeword preamble transmission at schedule 806, as described herein.

[0140] Example operation of user equipment

[0141] Figure 9 It shows a device (such as) Figure 1 and Figure 3 Method 900 for wireless communication of UE 104.

[0142] Method 900 begins at block 905, wherein a signal is transmitted in one or more time-frequency resources of the RACH, wherein the signal is multiplexed using codewords, and the one or more time-frequency resources and codewords define a preamble signature, for example, as described herein regarding Figure 6 As described.

[0143] Method 900 can then proceed to box 910, where a response associated with the preamble signature is received, for example, as described herein. Figure 8 As described.

[0144] Method 900 then proceeds to block 915, wherein communication with network entities is based at least in part on signals or responses, for example, as described herein. Figure 8 As described.

[0145] In some respects, method 900 further includes: receiving an indication including, for example, a configuration of a set of codewords for contention-based random access, as described herein.

[0146] In some respects, signals multiplexed using codewords include, for example, baseband signals generated at least in part based on codewords according to expression (1).

[0147] In some aspects, method 900 further includes: receiving an indication of a codeword, for example, for contention-free random access, as described herein. In some aspects, receiving the indication of the codeword includes: receiving the indication of the codeword in a DCI message of a signal transmitted by an indication device.

[0148] In some aspects, method 900 further includes receiving a configuration indicating one or more RACH resources (e.g., one or more first resources 704) dedicated to codeword-based RACH communication, wherein the one or more RACH resources include one or more time-frequency resources. In some aspects, the configuration indicates the number of subcarriers in the one or more RACH resources (e.g., the number of subcarriers 714) and the number of starting subcarriers (e.g., the number of starting subcarriers 712). The number of subcarriers may represent the total number of subcarriers corresponding to the size of the RACH used for codeword-based random access communication, and the number of starting subcarriers may represent the total number of subcarriers corresponding to the portion of the RACH allocated for contention-based random access.

[0149] In some aspects, method 900 further includes receiving a configuration indicating one or more shared RACH resources (e.g., one or more second resources 706) shared with both codeword-based and non-codeword-based RACH communication. In some aspects, the configuration further indicates that one or more dedicated RACH resources (e.g., one or more first resources 704) are dedicated to codeword-based RACH communication. In some aspects, the configuration indicates a probability for selecting one or more shared RACH resources for codeword-based RACH communication. In some aspects, a specific value of the probability (e.g., 0%) indicates avoiding the use of one or more shared RACH resources for codeword-based RACH communication.

[0150] In some respects, method 900 also includes receiving a configuration indicating that one or more values ​​to be excluded as codewords (e.g., codewords that are all 1s in binary).

[0151] In some respects, method 900 also includes: receiving a configuration indicating the probability of one or more values ​​for selecting a codeword.

[0152] In some respects, RACH includes NPRACH. In some respects, the device includes IoT devices.

[0153] In some respects, codewords are associated with code division multiplexing. In other respects, codewords are associated with orthogonal overlay codes.

[0154] In some respects, method 900 or any aspect thereof may be made by means of a device (such as...) Figure 11 The communication device 1100 performs the execution, and the device includes various components capable of operating, being configured, or adapted to perform the method 900. The communication device 1100 is described in further detail below.

[0155] It should be noted that Figure 9 This is merely one example of a method, and other methods that include fewer, more, or alternative operations may also conform to this disclosure. It should be noted that any operation illustrated with a dashed line indicates that the operation may be optional or alternative.

[0156] Example operations of network entities

[0157] Figure 10 A method 1000 for wireless communication by a device, such as... is shown. Figure 1 and Figure 3 BS102 or as about Figure 2 The decomposed base station under discussion.

[0158] Method 1000 begins at box 1005, wherein a signal is obtained in one or more time-frequency resources of the RACH, wherein the signal is multiplexed using codewords, and the one or more time-frequency resources and codewords define a preamble signature, for example, as described herein regarding Figure 6 As described.

[0159] Method 1000 can then proceed to box 1010, where a response associated with the preamble signature is transmitted, for example, as described herein. Figure 8 As described.

[0160] Method 1000 then proceeds to block 1015, wherein communication with the UE is based at least in part on signals or responses, for example, as described herein. Figure 8 As described.

[0161] In some respects, method 1000 further includes: a transmission indication including, for example, a configuration of a set of codewords for contention-based random access, as described herein.

[0162] In some respects, signals multiplexed using codewords include baseband signals used to generate signals.

[0163] In some aspects, method 1000 further includes: transmitting an indication of a codeword, for example, for contention-free random access, as described herein. In some aspects, transmitting the indication of the codeword includes: transmitting the indication of the codeword in a DCI message instructing the user equipment to transmit a signal.

[0164] In some aspects, method 1000 further includes: transmitting a configuration indicating one or more RACH resources (e.g., one or more first resources 704) dedicated to codeword-based RACH communication, wherein the one or more RACH resources include one or more time-frequency resources. In some aspects, the configuration indicates the number of subcarriers in the one or more RACH resources and the number of initial subcarriers.

[0165] In some aspects, method 1000 further includes transmitting a configuration indicating one or more shared RACH resources (e.g., one or more second resources 706) shared with both codeword-based and non-codeword-based RACH communication. In some aspects, the configuration further indicates that one or more dedicated RACH resources (e.g., one or more first resources 704) are dedicated to codeword-based RACH communication. In some aspects, the configuration indicates a probability for selecting one or more shared RACH resources for codeword-based RACH communication. In some aspects, a specific value of the probability (e.g., 0%) indicates avoiding the use of one or more shared RACH resources for codeword-based RACH communication.

[0166] In some respects, method 1000 also includes: transmitting a configuration indicating that one or more values ​​to be excluded as codewords (e.g., codewords that are all 1s in binary).

[0167] In some respects, method 1000 also includes: transmitting a configuration indicating the probability of selecting one or more values ​​of a codeword.

[0168] In some respects, RACH includes NPRACH.

[0169] In some respects, codewords are associated with code division multiplexing. In other respects, codewords are associated with orthogonal overlay codes.

[0170] In some respects, method 1000 or any aspect thereof may be made by means of a device (such as...) Figure 12 The communication device 1200 is used to perform the method 1000. The device includes various components that are operable to, configured to, or adapted to perform the method 1000. The communication device 1200 is described in further detail below.

[0171] It should be noted that Figure 10 This is merely one example of a method, and other methods that include fewer, more, or alternative operations may also conform to this disclosure. It should be noted that any operation illustrated with a dashed line indicates that the operation may be optional or alternative.

[0172] Example communication device

[0173] Figure 11Various aspects of the example communication device 1100 are described. In some aspects, the communication device 1100 is user equipment, such as those described above. Figure 1 and Figure 3 The UE 104 described.

[0174] Communication device 1100 includes a processing system 1105 coupled to a transceiver 1155 (e.g., a transmitter and / or receiver). Transceiver 1155 is configured to transmit and receive signals for communication device 1100 via antenna 1160, such as various signals as described herein. Processing system 1105 may be configured to perform processing functions of communication device 1100, including processing signals received by and / or to be transmitted by communication device 1100.

[0175] Processing system 1105 includes one or more processors 1110. In various aspects, the one or more processors 1110 may represent one or more of a receive processor 358, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380, as per [reference to...]. Figure 3 As described. One or more processors 1110 are coupled to a computer-readable medium / memory 1130 via a bus 1150. In some aspects, the computer-readable medium / memory 1130 is configured to store instructions (e.g., computer-executable code or processor-executable instructions) that, when executed by one or more processors 1110, enable one or more processors 1110 to execute and cause the one or more processors to perform actions related to... Figure 9 The described method 900 or any aspect thereof, including regarding Figure 9 Any additional operations described. Note that references to processors performing the functions of communication device 1100 may include one or more processors, such as performing the functions of communication device 1100 in a distributed manner.

[0176] In the depicted example, computer-readable medium / memory 1130 stores code 1135 for transmission, code 1140 for reception, and code 1145 for communication. Processing of codes 1135 to 1145 enables communication device 1100 to perform and allow the communication device to perform actions related to... Figure 9 The method described 900 or any aspect thereof.

[0177] One or more processors 1110 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 1130, including circuitry 1115 for transmission, circuitry 1120 for reception, and circuitry 1125 for communication. Processing using circuitry 1115 to 1125 enables communication device 1100 to execute and perform actions related to... Figure 9 The method described 900 or any aspect thereof.

[0178] More generally, components used for communication, sending, transmitting, or outputting for transmission may include Figure 3 The UE104 illustrated includes a transceiver 354, an antenna 352, a transmit processor 364, a TX MIMO processor 366, and / or a controller / processor 380. Figure 11 The transceiver 1155 and / or antenna 1160 of the communication device 1100 in the middle Figure 11 One or more processors 1110 of the communication device 1100. Components for transmitting, receiving, or acquiring may include... Figure 3 The UE 104 illustrated includes a transceiver 354, an antenna 352, a receiver processor 358, and / or a controller / processor 380. Figure 11 The transceiver 1155 and / or antenna 1160 of the communication device 1100 in the middle Figure 11 One or more processors 1110 of the communication device 1100 in the middle.

[0179] Figure 12 Various aspects of the example communication device 1200 are described. In some aspects, the communication device 1200 is a network entity, such as... Figure 1 and Figure 3 BS 102 or as about Figure 2 The decomposed base station under discussion.

[0180] Communication device 1200 includes a processing system 1205 coupled to a transceiver 1255 (e.g., a transmitter and / or receiver) and / or a network interface 1265. Transceiver 1255 is configured to transmit and receive signals for communication device 1200 via antenna 1260, such as various signals as described herein. Network interface 1265 is configured to transmit and receive signals for communication device 1200 via a communication link (such as those described herein). Figure 2 The described backhaul link, midhaul link, and / or fronthaul link receive and transmit signals for the communication device 1200. The processing system 1205 can be configured to perform the processing functions of the communication device 1200, including processing signals received by the communication device 1200 and / or to be transmitted by the communication device.

[0181] Processing system 1205 includes one or more processors 1210. In various aspects, the one or more processors 1210 may represent one or more of a receive processor 338, a transmit processor 320, a TX MIMO processor 330, and / or a controller / processor 340, as per [reference to...]. Figure 3As described. One or more processors 1210 are coupled to a computer-readable medium / memory 1230 via a bus 1250. In some aspects, the computer-readable medium / memory 1230 is configured to store instructions (e.g., computer-executable code or processor-executable instructions) that, when executed by one or more processors 1210, enable one or more processors 1210 to execute and cause the one or more processors to perform actions related to... Figure 10 The described method 1000 or any aspect thereof, including regarding Figure 10 Any additional operations described. Note that references to the processor of the communication device 1200 performing the function may include one or more processors of the communication device 1200, such as performing the function in a distributed manner.

[0182] In the depicted example, computer-readable medium / memory 1230 stores code 1235 for obtaining, code 1240 for transmitting, and code 1245 for conveying. Processing of codes 1235 to 1245 enables communication device 1200 to perform and cause the communication device to perform actions related to... Figure 10 The method described is 1000 or any aspect thereof.

[0183] One or more processors 1210 include circuitry configured to implement (e.g., execute) code stored in computer-readable medium / memory 1230, the circuitry including circuitry 1215 for acquisition, circuitry 1220 for transmission, and circuitry 1225 for communication. Processing using circuitry 1215 to 1225 enables communication device 1200 to execute and perform actions related to... Figure 10 The method 1000 described or any aspect thereof.

[0184] More generally, components used for conveying, sending, transmitting, or outputting for transmission may include Figure 3 The BS102 illustrated includes a transceiver 332, an antenna 334, a transmit processor 320, a TX MIMO processor 330, and / or a controller / processor 340. Figure 12 The transceiver 1255 and / or antenna 1260 of the communication device 1200 in the middle Figure 12 One or more processors 1210 of the communication device 1200. Components for transmitting, receiving, or acquiring may include... Figure 3 The BS 102 illustrated includes transceiver 332, antenna 334, receiver processor 338, and / or controller / processor 340. Figure 12 The transceiver 1255 and / or antenna 1260 of the communication device 1200 in the middle Figure 12 One or more processors 1210 of the communication device 1200.

[0185] Example Terms

[0186] Specific implementation examples are described in the following numbered clauses:

[0187] Clause 1: A method for wireless communication by a device, the method comprising: transmitting a signal in one or more time-frequency resources of a RACH, wherein the signal is multiplexed using codewords, the one or more time-frequency resources and the codewords defining a preamble signature; receiving a response associated with the preamble signature; and communicating with a network entity at least in part based on the response.

[0188] Clause 2: The method according to Clause 1 further includes: receiving a configuration indicating a set of codewords including the codewords.

[0189] Clause 3: The method according to any one of Clauses 1 to 2, wherein the signal multiplexed using the codeword comprises a baseband signal generated at least in part based on the codeword.

[0190] Clause 4: The method according to any one of Clauses 1 to 3 further includes: receiving an instruction for the codeword.

[0191] Clause 5: The method according to Clause 4, wherein receiving the indication for the codeword comprises: receiving the indication for the codeword in a DCI message instructing the device to transmit the signal.

[0192] Clause 6: The method according to any one of Clauses 1 to 5, the method further comprising: receiving a configuration indicating one or more RACH resources dedicated to codeword-based RACH communication, wherein the one or more RACH resources include the one or more time-frequency resources.

[0193] Clause 7: The method described in Clause 6, wherein the configuration indicates the number of subcarriers in the one or more RACH resources and the number of initial subcarriers.

[0194] Clause 8: The method according to any one of Clauses 1 to 7 further includes: receiving a configuration indicating one or more shared RACH resources shared with codeword-based RACH communication and non-codeword-based RACH communication.

[0195] Clause 9: The configuration described in Clause 8 further indicates that one or more dedicated RACH resources are dedicated to codeword-based RACH communication.

[0196] Clause 10: The method according to Clause 8, wherein the configuration indicates the probability of selecting the one or more shared RACH resources for codeword-based RACH communication.

[0197] Clause 11: The method according to Clause 10, wherein a specific value of the probability indicates avoiding the use of the one or more shared RACH resources for the codeword-based RACH communication.

[0198] Clause 12: The method according to any one of Clauses 1 to 11, the method further comprising: receiving a configuration indicating to exclude one or more values ​​used as the codeword.

[0199] Clause 13: The method according to any one of Clauses 1 to 12, the method further comprising: receiving a configuration indicating the probability of selecting one or more values ​​of the codeword.

[0200] Clause 14: The method according to any one of Clauses 1 to 13, wherein the RACH includes NPRACH.

[0201] Clause 15: The method according to any one of Clauses 1 to 14, wherein the device includes an IoT device.

[0202] Clause 16: The method according to any one of Clauses 1 to 15, wherein the codeword is associated with code division multiplexing.

[0203] Clause 17: The method according to any one of Clauses 1 to 16, wherein the codeword is associated with an orthogonal overlay code.

[0204] Clause 18: A method for wireless communication by a device, the method comprising: obtaining a signal in one or more time-frequency resources of a RACH, wherein the signal is multiplexed using codewords, the one or more time-frequency resources and the codewords defining a preamble signature; transmitting a response associated with the preamble signature; and communicating with a UE at least in part based on the response.

[0205] Clause 19: The method according to Clause 18 further includes: transmitting a configuration of a codeword set including the codeword.

[0206] Clause 20: The method according to any one of Clauses 18 to 19, wherein the signal multiplexed using the codeword comprises a baseband signal generated at least in part based on the codeword.

[0207] Clause 21: The method according to any one of Clauses 18 to 20, the method further comprising: transmitting an instruction for the codeword.

[0208] Clause 22: The method according to Clause 18, wherein transmitting the indication for the codeword comprises: transmitting the indication for the codeword in a DCI message instructing the user equipment to transmit the signal.

[0209] Clause 23: The method according to any one of Clauses 18 to 22, the method further comprising: transmitting a configuration of one or more RACH resources dedicated to codeword-based RACH communication, wherein the one or more RACH resources include the one or more time-frequency resources.

[0210] Clause 24: The method according to Clause 20, wherein the configuration indicates the number of subcarriers in the one or more RACH resources and the number of initial subcarriers.

[0211] Clause 25: The method according to any one of Clauses 18 to 24, the method further comprising: transmitting a configuration indicating one or more shared RACH resources shared with codeword-based RACH communication and non-codeword-based RACH communication.

[0212] Clause 26: The method described in Clause 25, wherein the configuration further indicates that one or more dedicated RACH resources are dedicated to codeword-based RACH communication.

[0213] Clause 27: The method according to Clause 25, wherein the configuration indicates the probability of selecting the one or more shared RACH resources for codeword-based RACH communication.

[0214] Clause 28: The method according to Clause 27, wherein a specific value of the probability indicates avoiding the use of the one or more shared RACH resources for the codeword-based RACH communication.

[0215] Clause 29: The method according to any one of Clauses 18 to 28, the method further comprising: transmitting an indication to exclude one or more values ​​used as the codeword.

[0216] Clause 30: The method according to any one of Clauses 18 to 29, the method further comprising: transmitting a configuration indicating the probability of selecting one or more values ​​of the codeword.

[0217] Clause 31: The method according to any one of Clauses 18 to 30, wherein the RACH includes NPRACH.

[0218] Clause 32: The method according to any one of Clauses 18 to 31, wherein the codeword is associated with code division multiplexing.

[0219] Clause 33: The method according to any one of Clauses 18 to 32, wherein the codeword is associated with an orthogonal overlay code.

[0220] Clause 34: One or more means comprising: one or more memories, the one or more memories including; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the one or more means to perform the method according to any one of Clauses 1 to 33.

[0221] Clause 35: One or more apparatuses, said apparatuses comprising components for performing the method according to any one of Clauses 1 to 33.

[0222] Clause 36: One or more non-transitory computer-readable media, the one or more non-transitory computer-readable media comprising executable instructions that, when executed by one or more processors of one or more devices, cause the one or more devices to perform the method according to any one of Clauses 1 to 33.

[0223] Clause 37: One or more computer program products embodied on one or more computer-readable storage media, the one or more computer-readable storage media including code for performing the method according to any one of Clauses 1 to 33.

[0224] Additional Notes

[0225] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability, or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, the function and arrangement of the elements discussed may be changed without departing from the scope of this disclosure. Various processes or components may be omitted, substituted, or added as appropriate in various examples. For example, the described methods may be performed in a different order than described, and various actions may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement an apparatus or practice. Additionally, the scope of this disclosure is intended to cover such apparatuses or methods practiced using other structures, functionalities, or structures and functionalities that complement or replace the various aspects of this disclosure set forth herein. It should be understood that any aspect of this disclosure disclosed herein may be embodied by one or more elements of these claims.

[0226] The various exemplary logic blocks, modules, and circuits described in this disclosure can be implemented or executed using a general-purpose processor, AI processor, digital signal processor (DSP), ASIC, field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic element, discrete hardware component, or any combination thereof designed to perform the functions described herein. While the general-purpose processor may be a microprocessor, in alternative embodiments, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, a system-on-a-chip (SoC), or any other such configuration.

[0227] As used in this article, the phrase “at least one of the items” refers to any combination of these items, including a single member. As an example, “at least one of a, b, or c” is intended to cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbb, cc, and ccc, or any other ordering of a, b, and c).

[0228] As used herein, the term "determine" encompasses a wide variety of actions. For example, "determine" can include calculation, operation, processing, deduction, investigation, lookup (e.g., searching in a table, database, or other data structure), assertion, etc. Additionally, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. Furthermore, "determine" can include parsing, selecting, picking, building, etc.

[0229] As used herein, unless otherwise stated, “coupled to” and “coupled with” generally encompass both direct and indirect coupling (e.g., including intermediate aspects of coupling). For example, stating that a processor is coupled to memory allows for direct coupling or coupling via an intermediate aspect such as a bus.

[0230] The methods disclosed herein include one or more actions for implementing the methods. These method actions may be interchanged without departing from the scope of the claims. In other words, unless a specified order of actions is given, the order and / or use of a particular action may be modified without departing from the scope of the claims. Furthermore, the various operations of the methods described above can be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or software components and / or modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors.

[0231] The following claims are not intended to be limited to the aspects shown herein, but should be given the full scope consistent with the language of the claims. References to singular elements are not intended to mean “only one” (unless specifically stated as “only one”), but rather “one or more”. Unless otherwise specified, definite articles (e.g., “the” or “described”) subsequently used with an element (e.g., “processor”) are not intended to give that element a singular meaning (e.g., “only one”). For example, unless otherwise specified, references to elements (e.g., “processor”, “controller”, “memory”, “transceiver”, “antenna”, “the processor”, “the controller”, “the memory”, “the transceiver”, “the antenna”, etc.) should be understood to refer to one or more elements (e.g., “one or more processors”, “one or more controllers”, “one or more memories”, “a plurality of transceivers”, etc.). The terms “set” and “group” are intended to include one or more elements and may be used interchangeably with “one or more”. In the case of references to one or more elements performing a function (e.g., steps of a method), one element may perform all the functions, or more than one element may collectively perform those functions. When more than one element performs these functions together, each function does not need to be performed by every single element (e.g., different functions can be performed by different elements), and / or each function does not need to be performed by only one element as a whole (e.g., different elements can perform different sub-functions of a function). Similarly, when referring to one or more elements configured to cause another element (e.g., a device) to perform a function, one element may be configured to cause another element to perform all functions, or more than one element may be jointly configured to cause another element to perform these functions. Unless otherwise specifically stated, the term "some" refers to one or more. All structural and functional equivalents of the various aspects described throughout this disclosure that are currently or hereafter known to those skilled in the art are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly recited in the claims.

Claims

1. An apparatus configured for wireless communication, the apparatus comprising: One or more memory units; and One or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to: Signals are transmitted in one or more time-frequency resources of a random access channel (RACH), wherein the signals are multiplexed using codewords, the one or more time-frequency resources and the codewords define a preamble signature, and Communicating with network entities is based at least in part on the signals mentioned above.

2. The apparatus of claim 1, wherein the one or more processors are configured to cause the apparatus to: receive a configuration indicating a set of codewords including the codewords.

3. The apparatus of claim 1, wherein the signal multiplexed using the codeword comprises a baseband signal generated at least in part based on the codeword.

4. The apparatus of claim 1, wherein the one or more processors are configured to cause the apparatus to: receive an instruction for the codeword.

5. The apparatus of claim 4, wherein, in order to receive the indication for the codeword, the one or more processors are configured to cause the apparatus to receive the indication for the codeword in a downlink control information (DCI) message instructing the apparatus to transmit the signal.

6. The apparatus of claim 1, wherein the one or more processors are configured to cause the apparatus to: receive a configuration indicating one or more RACH resources dedicated to codeword-based RACH communication, wherein the one or more RACH resources include the one or more time-frequency resources.

7. The apparatus of claim 6, wherein the configuration indicates the number of subcarriers in the one or more RACH resources and the number of initial subcarriers.

8. The apparatus of claim 1, wherein the one or more processors are configured to cause the apparatus to: receive a configuration indicating one or more shared RACH resources shared with codeword-based RACH communication and non-codeword-based RACH communication.

9. The apparatus of claim 8, wherein the configuration further indicates that one or more dedicated RACH resources are dedicated to codeword-based RACH communication.

10. The apparatus of claim 8, wherein the configuration indicates the probability of selecting the one or more shared RACH resources for codeword-based RACH communication.

11. An apparatus configured for wireless communication, the apparatus comprising: One or more memory units; and One or more processors coupled to the one or more memory, the one or more processors being configured to cause the device to: A signal is obtained in one or more time-frequency resources of a random access channel (RACH), wherein the signal is multiplexed using codewords, the one or more time-frequency resources and the codewords define a preamble signature, and Communication with the user equipment (UE) is based at least in part on the signal.

12. The apparatus of claim 11, wherein the one or more processors are configured to cause the apparatus to: transmit a configuration indicating a set of codewords including the codewords.

13. The apparatus of claim 11, wherein the signal multiplexed using the codeword comprises a baseband signal generated at least in part based on the codeword.

14. The apparatus of claim 11, wherein the one or more processors are configured to cause the apparatus to: transmit an indication of the codeword.

15. The apparatus of claim 14, wherein, in order to transmit the indication of the codeword, the one or more processors are configured to cause the apparatus to transmit the indication of the codeword in a downlink control information (DCI) message instructing a user equipment to transmit the signal.

16. The apparatus of claim 11, wherein the one or more processors are configured to cause the apparatus to: transmit a configuration indicating one or more RACH resources dedicated to codeword-based RACH communication, wherein the one or more RACH resources include the one or more time-frequency resources.

17. The apparatus of claim 16, wherein the configuration indicates the number of subcarriers in the one or more RACH resources and the number of initial subcarriers.

18. The apparatus of claim 11, wherein the one or more processors are configured to cause the apparatus to: transmit a configuration indicating one or more shared RACH resources shared with codeword-based RACH communication and non-codeword-based RACH communication.

19. The apparatus of claim 18, wherein the configuration further indicates that one or more dedicated RACH resources are dedicated to codeword-based RACH communication.

20. A method for wireless communication by a device, the method comprising: Signals are transmitted in one or more time-frequency resources of a random access channel (RACH), wherein the signals are multiplexed using codewords, and the one or more time-frequency resources and the codewords define a preamble signature; and Communicating with network entities is based at least in part on the signals mentioned above.

Images