Choosing Between Code Types for Encoding Information Bits

Abstract

A method and apparatus for selecting a chord type is provided. In one embodiment, a code type is selected from a set of code types for use as an inner code for a concatenated coding scheme for encoding information bits for a channel, the selection being based on one or more channel coding parameters including a false alarm detection strategy for the channel. A codeword is generated by encoding the information bits using the code type selected as the inner code and an outer code. The generated codeword is transmitted.

Description

[Technical field]

[0001] Claiming priority This patent application claims the benefit of U.S. Patent Application No. PCT / CN2017 / 091006, filed Jun. 30, 2017, which is assigned to the assignee of the present application and is expressly incorporated herein by reference.

[0002] The present disclosure relates generally to wireless communication systems, and more particularly to methods and apparatus for selecting between code types for encoding information bits. [Background technology]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power). Examples of such multiple access technologies include Long Term Evolution (LTE) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] In some examples, a wireless multiple-access communication system may include several base stations, each simultaneously supporting communication for several communication devices, also known as user equipment (UE). In an LTE or LTE-A network, a set of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in a next-generation or fifth-generation (5G) network), a wireless multiple-access communication system may include several distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmit reception points (TRPs), etc.) that communicate with several aggregation units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), and a set of one or more distributed units that communicate with the aggregation units may define an access node (e.g., new radio base station (NR BS), new radio node-B (NR NB), network node, 5G NB, eNB, etc.). A base station or a DU may communicate with a set of UEs over a downlink channel (e.g., for transmission from the base station or to the UEs) and an uplink channel (e.g., for transmission from the UEs to the base station or distributed unit).

[0005] These multiple access technologies are being adopted in various telecommunications standards to provide a common protocol that allows different wireless devices to communicate on a city, national, regional, or even global scale. One example of an emerging telecommunications standard is New Radio (NR), e.g., 5G radio access. NR is a set of extensions to the LTE mobile standard promulgated by the Third Generation Partnership Project (3GPP). It is designed to improve spectral efficiency, reduce costs, improve services, take advantage of new spectrum, and better support mobile broadband Internet access by better integrating with other open standards that use OFDMA with cyclic prefixes (CPs) on the downlink (DL) and uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. Summary of the Invention [Problem to be solved by the invention]

[0006] However, as the demand for mobile broadband access continues to grow, further improvements in NR technology are desired, and preferably these improvements should be applicable to other multiple access technologies and the telecommunications standards that use these technologies. [Means for solving the problem]

[0007] The systems, methods, and devices of the present disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed by the following claims, several features will now be briefly described. After considering this description, and especially after reading the section entitled "Description of the Preferred Embodiments," one will understand how the features of the present disclosure provide advantages including improved communications between access points and stations in a wireless network.

[0008] Certain aspects of the present disclosure provide a method for wireless communication that generally includes the steps of selecting a type of code from a set of code types to use as an inner code for a concatenated coding scheme for encoding information bits of a channel, the selection being based on a false alarm detection policy for the channel, generating a codeword by encoding the information bits using the type of code selected as the inner code and an outer code, and transmitting the codeword.

[0009] Certain aspects of the disclosure provide an apparatus for wireless communication that generally includes means for selecting a type of code from a set of code types to use as an inner code for a concatenated coding scheme for encoding information bits of a channel, the selection being based on a false alarm detection policy for the channel, means for generating a codeword by encoding information bits using the type of code selected as the inner code and an outer code, and means for transmitting the codeword.

[0010] Some aspects of the disclosure provide an apparatus for wireless communication. The apparatus generally includes at least one processor and a memory coupled to the at least one processor. The at least one processor is generally configured to: select a type of code from a set of code types to use as an inner code for a concatenated coding scheme for encoding information bits of a channel, the selection being based on a false alarm detection policy for the channel; generate a codeword by encoding the information bits using the type of code selected as the inner code and an outer code; and transmit the codeword.

[0011] Some aspects of the present disclosure provide a computer-readable medium for wireless communication, the computer-readable medium storing instructions that, when executed by at least one processor, perform a method including selecting a type of code from a set of code types to use as an inner code for a concatenated coding scheme for encoding information bits of a channel, the selection being based on a false alarm detection policy for the channel, generating a codeword by encoding the information bits using the type of code selected as the inner code and an outer code, and transmitting the codeword.

[0012] Aspects include methods, apparatus, systems, computer-readable media, and processing systems as generally described fully herein with reference to and illustrated by the accompanying drawings.

[0013] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of the various aspects may be utilized, and the description is intended to include all such aspects and their equivalents.

[0014] So that the above-mentioned features of the present disclosure may be understood in detail, a more particular description, briefly summarized above, may be made by reference to embodiments, some of which are illustrated in the accompanying drawings. It should be noted, however, that the present description may lead to other equally effective embodiments, and that the accompanying drawings illustrate only some typical embodiments of the present disclosure and therefore should not be considered as limiting the scope of the present disclosure. [Brief description of the drawings]

[0015] [Figure 1]FIG. 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure. [Diagram 2] FIG. 2 is a block diagram illustrating an example logical architecture of a distributed RAN, in accordance with certain aspects of the present disclosure. [Diagram 3] FIG. 1 illustrates an example physical architecture of a distributed RAN, in accordance with certain aspects of the present disclosure. [Figure 4] FIG. 1 is a block diagram conceptually illustrating a design of an example BS and user equipment (UE) in accordance with certain aspects of the present disclosure. [Diagram 5] FIG. 2 illustrates an example for implementing a communication protocol stack in accordance with some aspects of the present disclosure. [Figure 6] FIG. 1 illustrates an example of a downlink-centric (DL-centric) subframe, in accordance with certain aspects of the present disclosure. [Figure 7] FIG. 1 illustrates an example of an uplink-centric (UL-centric) subframe, in accordance with certain aspects of the present disclosure. [Figure 8] FIG. 1 illustrates encoding and decoding using concatenated codes in accordance with certain aspects of the present disclosure. [Figure 9] FIG. 9 illustrates example operations 900 that may be performed by a wireless device (e.g., a UE or a gNB) to select a code type for encoding information bits, in accordance with certain aspects of the present disclosure. [Figure 10] FIG. 10 illustrates a decision tree 1000 for determining a concatenated code for encoding information bits by a wireless device (e.g., a gNB or UE) in accordance with certain aspects of the present disclosure. [Figure 11] FIG. 10 illustrates a communications device that may include various components configured to perform operations for the techniques disclosed herein, such as those illustrated in FIG. 9, in accordance with some aspects of the disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] For ease of understanding, the same reference numbers have been used, where possible, to designate identical elements common to the figures. It is contemplated that elements disclosed in one embodiment can be advantageously utilized in other embodiments without specific recitation.

[0017] In coding theory, concatenated codes form a class of error-correcting codes derived by combining an inner code and an outer code, which are typically used in conjunction to form a stronger combined code.

[0018] In some aspects, different channel coding schemes have different performances in different information bit length (K) domains. In general, when K is very small (e.g., <12 bits), Reed-Muller (RM) codes may perform better than Polar codes. On the other hand, when K is large, Polar codes may outperform RM codes under comparable decoding complexity requirements.

[0019] Thus, in some aspects, it may be beneficial to select a coding scheme (e.g., an RM code or a Polar code) based at least on the number of information bits to be decoded. Furthermore, in addition to the information bit length (K), the selection between an RM code and a Polar code may need to take into account certain other parameters as well, which are described in more detail below.

[0020] Certain aspects of this disclosure describe techniques for selecting between RM and Polar codes for encoding / decoding information bits based on one or more channel coding parameters.

[0021] NR may support various wireless communication services, such as wide bandwidths (e.g., above 80 MHz) for enhanced mobile broadband (eMBB) targets, high carrier frequencies (e.g., 60 GHz) for millimeter wave (mmW) targets, non-backward compatible MTC techniques for massive MTC (mMTC) targets, and / or ultra reliable low latency communication (URLLC) for mission-critical targets. These services may include latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet their respective quality of service (QoS) requirements. In addition, these services may coexist in the same subframe.

[0022] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and configuration of the elements described without departing from the scope of the disclosure. Various examples may omit, substitute, or add various procedures or components as appropriate. For example, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects described herein. In addition, the scope of the disclosure is intended to encompass such apparatus or methods practiced using other structures, functions, or structures and functions in addition to or other than the various aspects of the disclosure described herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects.

[0023] The techniques described herein may be used for various wireless communication networks, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA), and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network may implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). NR is an emerging wireless communications technology under development with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein may be used for the wireless networks and radio technologies mentioned above, as well as other wireless networks and radio technologies. For clarity, aspects may be described herein generally using terminology associated with 3G and / or 4G wireless technologies, although aspects of the present disclosure may be applied in other generation-based communication systems, such as 5G and beyond, including NR technologies.

[0024] Exemplary Wireless Communication System FIG. 1 illustrates an example wireless network 100, such as a New Radio (NR) or 5G network, in which aspects of the disclosure may be implemented.

[0025] As shown in FIG. 1, the wireless network 100 may include several BSs 110 and other network entities. A BS may be a station that communicates with UEs. Each BS 110 may provide communication coverage to a particular geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a Node B and / or a Node B subsystem serving this coverage area, depending on the context in which the term is used. In an NR system, terms such as "cell" and eNB, Node B, 5G NB, AP, NR BS, or TRP may be interchangeable. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move according to the location of a mobile base station. In some examples, the base stations may be interconnected to each other and / or to one or more other base stations or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections, virtual networks, etc., using any suitable transport network.

[0026] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a particular radio access technology (RAT) and may operate at one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, etc. A frequency may also be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR RAT networks or 5G RAT networks may be deployed.

[0027] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having an association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users in the home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In the example shown in FIG. 1, BSs 110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x may be a pico BS for a pico cell 102x. BSs 110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. A BS may support one or multiple (e.g., three) cells.

[0028] Wireless network 100 may also include relay stations. A relay station is a station that receives transmissions of data and / or other information from an upstream station (e.g., a BS or a UE) and sends transmissions of data and / or other information to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that relays transmissions for other UEs. In the example shown in FIG. 1, relay station 110r may communicate with BS 110a and UE 120r to facilitate communication between BS 110a and UE 120r. A relay station may also be referred to as a relay BS, a relay, etc.

[0029] Wireless network 100 may be a heterogeneous network including different types of BSs, e.g., macro BSs, pico BSs, femto BSs, relays, etc. These different types of BSs may have different transmit power levels, different coverage areas, and different impacts on interference in wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 20 watts), while a pico BS, femto BS, and relays may have a lower transmit power level (e.g., 1 watt).

[0030] The wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timing and transmissions from different BSs may not be aligned in time. The techniques described herein may be used for both synchronous and asynchronous operation.

[0031] A network controller 130 may couple to a set of BSs and provide coordination and control for these BSs. The network controller 130 may communicate with the BSs 110 via a backhaul. The BSs 110 may also communicate with each other, e.g., directly or indirectly via a wireless or wired backhaul.

[0032] The UEs 120 (e.g., 120x, 120y, etc.) may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile. A UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, Customer Premises Equipment (CPE), cellular phone, smartphone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet, camera, gaming device, netbook, smartbook, ultrabook, medical device or equipment, biometric sensor / device, wearable device such as smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or vehicle sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate over a wireless or wired medium. Some UEs may be considered as evolved devices or machine type communication (MTC) devices or evolved MTC (eMTC) devices. MTC UEs and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc. that may communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices. In FIG. 1, a solid line with double arrows indicates a desired transmission between a UE and a serving BS, which is a BS designated to serve the UE on the downlink and / or uplink.A dashed line with double arrows indicates an interfering transmission between a UE and a BS.

[0033] Certain wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM partition the system bandwidth (e.g., system frequency band) into multiple (K) orthogonal subcarriers, also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. Generally, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kHz, and the minimum resource allocation (called a "resource block") may be 12 subcarriers (or 180 kHz). As a result, the nominal FFT size may be equal to 128, 256, 512, 1024, or 2048 for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (i.e., 6 resource blocks), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively.

[0034] Although aspects of the examples described herein may be associated with LTE technology, aspects of the present disclosure may be applicable to other wireless communication systems, such as NR. NR may include support for half-duplex operation employing OFDM with CP on the uplink and downlink and using time division duplexing (TDD). A single component carrier bandwidth of 100 MHz may be supported. An NR resource block may span 12 subcarriers with a subcarrier bandwidth of 75 kHz for a duration of 0.1 ms. Each radio frame is composed of 50 subframes having a length of 10 ms. As a result, each subframe may have a length of 0.2 ms. Each subframe may indicate a link direction (i.e., DL or UL) for data transmission, and the link direction per subframe may be dynamically switched. Each subframe may include DL / UL data as well as DL / UL control data. UL and DL subframes for NR may be as described in more detail below with respect to Figures 6 and 7. Beamforming may be supported and the beam direction may be dynamically configured. MIMO transmission with precoding may also be supported. MIMO configurations in DL may support up to 8 transmit antennas with up to 8 streams and multi-layer DL transmission with up to 2 streams per UE. Multi-layer transmission with up to 2 streams per UE may be supported. Aggregation of multiple cells may be supported with up to 8 serving cells. Alternatively, NR may support different air interfaces other than OFDM-based. An NR network may include entities such as a CU and / or a DU.

[0035] In some examples, access to the air interface may be scheduled, and a scheduling entity (e.g., a base station) allocates resources for communication among some or all devices and equipment within its service area or cell. Within this disclosure, as described further below, the scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, the subordinate entities utilize resources allocated by the scheduling entity. A base station is not the only entity that may function as a scheduling entity. That is, in some examples, a UE may function as a scheduling entity that schedules resources for one or more subordinate entities (e.g., one or more other UEs). In this example, the UE is functioning as the scheduling entity, and the other UEs utilize the resources scheduled by the UE for wireless communication. A UE may function as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In a mesh network example, the UEs may communicate directly with each other in some cases in addition to communicating with the scheduling entity.

[0036] Thus, in wireless communication networks with scheduled access to time-frequency resources and having cellular, P2P and mesh configurations, a scheduling entity and one or more subordinate entities may communicate utilizing the scheduled resources.

[0037] As mentioned above, the RAN may include a CU and a DU. An NR BS (e.g., eNB, 5G Node B, Node B, Transmit Reception Point (TRP), Access Point (AP)) may correspond to one or more BSs. An NR cell may be configured as an access cell (ACell) or a data-only cell (DCell). For example, a RAN (e.g., an aggregation unit or a distribution unit) may configure a cell. A DCell may be a cell used for carrier aggregation or dual connectivity but not used for initial access, cell selection / reselection, or handover. In some cases, a DCell may not transmit a synchronization signal, and in some cases, a DCell may transmit a SS. An NR BS may transmit a downlink signal indicating a cell type to a UE. Based on the cell type indication, the UE may communicate with an NR BS. For example, a UE may determine an NR BS to consider for cell selection, access, handover, and / or measurement based on the indicated cell type.

[0038] 2 illustrates an example logical architecture of a distributed radio access network (RAN) 200 that may be implemented within the wireless communication system illustrated in FIG. 1. The 5G access node 206 may include an access node controller (ANC) 202. The ANC may be an aggregation unit (CU) of the distributed RAN 200. A backhaul interface to a next generation core network (NG-CN) 204 may terminate at the ANC. A backhaul interface to a neighboring next generation access node (NG-AN) may terminate at the ANC. The ANC may include one or more TRPs 208 (which may also be referred to as a BS, NR BS, Node B, 5G NB, AP, or some other term). As discussed above, TRP may be used interchangeably with "cell."

[0039] The TRP 208 may be a DU. A TRP may be connected to one ANC (ANC 202) or to two or more ANCs (not shown). For example, for RAN sharing, radio as a service (RaaS), and service-specific ANC deployments, a TRP may be connected to two or more ANCs. A TRP may include one or more antenna ports. A TRP may be configured to serve traffic to a UE individually (e.g., dynamic selection) or together (e.g., joint transmission).

[0040] The local architecture 200 may be used to illustrate a fronthaul definition. An architecture may be defined that supports fronthaul solutions across different deployment types. For example, the architecture may be based on transmission network capabilities (e.g., bandwidth, latency, and / or jitter).

[0041] The architecture may share features and / or components with LTE. According to an aspect, a Next Generation AN (NG-AN) 210 may support dual connectivity with NR. The NG-AN may share a common fronthaul for LTE and NR.

[0042] The architecture may enable cooperation between TRPs 208. For example, cooperation may be preset within the TRPs and / or across the TRPs via the ANC 202. According to aspects, an inter-TRP interface may not be required / existent.

[0043] According to aspects, there may be dynamic configuration of partitioned logical functions within the architecture 200. As described in more detail with reference to FIG. 5, the Radio Resource Control (RRC) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, the Medium Access Control (MAC) layer, and the Physical (PHY) layer may be adaptively arranged in a DU or a CU (e.g., a TRP or an ANC, respectively). According to some aspects, a BS may include a aggregation unit (CU) (e.g., the ANC 202) and / or one or more distributed units (e.g., one or more TRPs 208).

[0044] 3 illustrates an example physical architecture of a distributed RAN 300 in accordance with some aspects of the disclosure. A centralized core network unit (C-CU) 302 may host core network functions. The C-CU may be centrally located. The C-CU functions may be offloaded (e.g., to Advanced Wireless Services (AWS)) to address peak capacity.

[0045] A centralized RAN unit (C-RU) 304 may host one or more ANC functions. In some cases, the C-RU may host core network functions locally. The C-RU may have a distributed deployment. The C-RU may be closer to the network edge.

[0046] The DU 306 may host one or more TRPs (Edge Nodes (EN), Edge Units (EU), Radio Heads (RH), Smart Radio Heads (SRH), etc.). The DU may be located at the edge of the network with radio frequency (RF) capabilities.

[0047] 4 illustrates exemplary components of the BS 110 and UE 120 shown in FIG. 1 that may be used to implement aspects of the present disclosure. As described above, the BS may include a TRP. One or more components of the BS 110 and UE 120 may be used to practice aspects of the present disclosure. For example, the antenna 452, Tx / Rx 222, processor 466, 458, 464, and / or controller / processor 480 of the UE 120, and / or the antenna 434, processor 430, 420, 438, and / or controller / processor 440 of the BS 110 may be used to perform the operations described herein and illustrated with reference to FIGS. 8-11.

[0048] 4 shows a block diagram of a design of a BS 110 and a UE 120, which may be one of the BSs and one of the UEs in FIG. 1. For a limited connectivity scenario, the base station 110 may be the macro BS 110c in FIG. 1, and the UE 120 may be a UE 120y. The base station 110 may also be some other type of base station. The base station 110 may be equipped with antennas 434a-434t, and the UE 120 may be equipped with antennas 452a-452r.

[0049] At the base station 110, the transmit processor 420 may receive data from the data source 412 and control information from the controller / processor 440. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. The processor 420 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor 420 may also generate reference symbols, e.g., for the PSS, SSS, and cell-specific reference signals. The transmit (TX) multiple-input multiple-output (MIMO) processor 430 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, and / or reference symbols, if applicable, and may provide output symbol streams to the modulators (MODs) 432a-432t. For example, the TX MIMO processor 430 may perform some aspects described herein for RS multiplexing. Each modulator 432 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 432 may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 432a-432t may be transmitted via antennas 434a-434t, respectively.

[0050] At the UE 120, the antennas 452a-452r may receive downlink signals from the base station 110 and may provide received signals to demodulators (DEMODs) 454a-454r, respectively. Each demodulator 454 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 454 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 456 may obtain the received symbols from all demodulators 454a-454r, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. For example, the MIMO detector 456 may provide the detected RS transmitted using the techniques described herein. A receive processor 458 may process (e.g., demodulate, deinterleave, and decode) the detected symbols and provide decoded data for the UE 120 to a data sink 460 and provide decoded control information to the controller / processor 480. According to one or more examples, the CoMP aspects may include providing antennas as well as some Tx / Rx functionality such that the CoMP aspects reside in a distributed unit. For example, some Tx / Rx processing may occur in a central unit while other processing may occur in a distributed unit. For example, according to one or more aspects shown in the figure, the BS modulator / demodulator 432 may reside in a distributed unit.

[0051] On the uplink, at the UE 120, a transmit processor 464 may receive and process data (e.g., for the Physical Uplink Shared Channel (PUSCH)) from a data source 462 and control information (e.g., for the Physical Uplink Control Channel (PUCCH)) from the controller / processor 480. The transmit processor 464 may also generate reference symbols for a reference signal. The symbols from the transmit processor 464 may be precoded by a TX MIMO processor 466 if applicable, further processed by demodulators 454a-454r (e.g., for SC-FDM, etc.), and transmitted to the base station 110. At the BS 110, uplink signals from the UE 120 may be received by the antennas 434, processed by the modulator 432, detected by a MIMO detector 436 if applicable, and further processed by the receive processor 438 to obtain decoded data and control information sent by the UE 120. The receive processor 438 may provide decoded data to a data sink 439 and decoded control information to a controller / processor 440 .

[0052] The controllers / processors 440 and 480 may direct operation at the base station 110 and the UE 120, respectively. The processor 440 and / or other processors and modules at the base station 110 may, for example, perform or direct the implementation of the functional blocks shown in FIG. 10 and / or other processes for the techniques described herein. The processor 480 and / or other processors and modules at the UE 120 may also perform or direct processes for the techniques described herein. The memories 442 and 482 may store data and program codes for the BS 110 and the UE 120, respectively. The scheduler 444 may schedule UEs for data transmission on the downlink and / or uplink.

[0053] FIG. 5 illustrates a diagram 500 illustrating an example for implementing a communications protocol stack according to an aspect of the disclosure. The illustrated communications protocol stack may be implemented by a device operating in a 5G system (e.g., a system supporting uplink-based mobility). Diagram 500 illustrates a communications protocol stack including a radio resource control (RRC) layer 510, a packet data convergence protocol (PDCP) layer 515, a radio link control (RLC) layer 520, a medium access control (MAC) layer 525, and a physical (PHY) layer 530. In various examples, the layers of the protocol stack may be implemented as separate modules of software, parts of a processor or ASIC, parts of non-colocated devices connected by a communications link, or various combinations thereof. Co-located and non-co-located implementations may be used, for example, in a protocol stack for a network access device (e.g., an AN, a CU, and / or a DU) or a UE.

[0054] The first option 505-a illustrates a split implementation of the protocol stack, where the implementation of the protocol stack is split between a centralized network access device (e.g., ANC 202 in FIG. 2) and a distributed network access device (e.g., DU 208 in FIG. 2). In the first option 505-a, the RRC layer 510 and the PDCP layer 515 may be implemented by the aggregation unit, and the RLC layer 520, the MAC layer 525, and the PHY layer 530 may be implemented by the DU. In various examples, the CU and the DU may or may not be collocated. The first option 505-a may be useful in a macrocell deployment, a microcell deployment, or a picocell deployment.

[0055] The second option 505-b illustrates an integrated implementation of the protocol stack, where the protocol stack is implemented within a single network access device (e.g., an Access Node (AN), a New Radio Base Station (NB BS), a New Radio Node B (NR NB), a Network Node (NN), etc.). In the second option, the RRC layer 510, the PDCP layer 515, the RLC layer 520, the MAC layer 525, and the PHY layer 530 may each be implemented by the AN. The second option 505-b may be useful in femtocell deployments.

[0056] Regardless of whether the network access device implements some or all of the protocol stack, the UE may implement the entire protocol stack (e.g., an RRC layer 510, a PDCP layer 515, an RLC layer 520, a MAC layer 525, and a PHY layer 530).

[0057] FIG. 6 is a diagram 600 illustrating an example of a DL-centric subframe. The DL-centric subframe may include a control portion 602. The control portion 602 may be at the beginning or beginning of the DL-centric subframe. The control portion 602 may include various scheduling and / or control information corresponding to various portions of the DL-centric subframe. In some configurations, the control portion 602 may be a physical DL control channel (PDCCH) as shown in FIG. 6. The DL-centric subframe may also include a DL data portion 604. The DL data portion 604 may sometimes be referred to as the payload of the DL-centric subframe. The DL data portion 604 may include communication resources utilized to communicate DL data from a scheduling entity (e.g., a UE or a BS) to a subordinate entity (e.g., a UE). In some configurations, the DL data portion 604 may be a physical DL shared channel (PDSCH).

[0058] The DL-centric subframe may also include a common UL portion 606. The common UL portion 606 may sometimes be referred to as an UL burst, a common UL burst, and / or various other suitable terms. The common UL portion 606 may include feedback information corresponding to various other portions of the DL-centric subframe. For example, the common UL portion 606 may include feedback information corresponding to the control portion 602. Non-limiting examples of the feedback information may include an ACK signal, a NACK signal, a HARQ indicator, and / or various other suitable types of information. The common UL portion 606 may include additional or alternative information, such as information regarding a random access channel (RACH) procedure, a scheduling request (SR), and various other suitable types of information. As shown in FIG. 6, the end of the DL data portion 604 may be separated in time from the beginning of the common UL portion 606. This separation in time may sometimes be referred to as a gap, a guard period, a guard interval, and / or various other suitable terms. This separation allows time for switching from DL communications (e.g., receiving operations by a subordinate entity (e.g., UE)) to UL communications (e.g., transmitting by a subordinate entity (e.g., UE)). Those skilled in the art will appreciate that the above is only one example of a DL-centric subframe, and that alternative structures having similar characteristics may exist without necessarily departing from the aspects described herein.

[0059] FIG. 7 is a diagram 700 illustrating an example of a UL-centric subframe. The UL-centric subframe may include a control portion 702. The control portion 702 may be present at the beginning or beginning of the UL-centric subframe. The control portion 702 in FIG. 7 may be similar to the control portion described above with reference to FIG. 6. The UL-centric subframe may also include a UL data portion 704. The UL data portion 704 may sometimes be referred to as the payload of the UL-centric subframe. The UL data portion may refer to communication resources utilized to communicate UL data from a subordinate entity (e.g., a UE) to a scheduling entity (e.g., a UE or a BS). In some configurations, the control portion 702 may be a physical DL control channel (PDCCH).

[0060] As shown in FIG. 7, the end of the control portion 702 may be separated in time from the beginning of the UL data portion 704. This separation in time may sometimes be referred to as a gap, a guard period, a guard interval, and / or various other suitable terms. This separation allows time for switching from DL communications (e.g., receiving operations by the scheduling entity) to UL communications (e.g., transmitting by the scheduling entity). The UL-centric subframe may also include a common UL portion 706. The common UL portion 706 in FIG. 7 may be similar to the common UL portion 606 described above with reference to FIG. 6. The common UL portion 706 may additionally or alternatively include information related to a channel quality indicator (CQI), a sounding reference signal (SRS), and various other suitable types of information. Those skilled in the art will appreciate that the above is just one example of a UL-centric subframe, and alternative structures having similar characteristics may exist without necessarily departing from the aspects described herein.

[0061] In some situations, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and / or various other suitable applications. In general, a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying that communication through a scheduling entity (e.g., UE or BS), even though a scheduling entity may be utilized for scheduling and / or control. In some examples, sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use unlicensed spectrum).

[0062] The UE may operate in various radio resource configurations, including configurations related to transmitting pilots using a dedicated set of resources (e.g., a Radio Resource Control (RRC) dedicated state, etc.) or configurations related to transmitting pilots using a common set of resources (e.g., an RRC common state, etc.). When operating in an RRC dedicated state, the UE may select a dedicated set of resources to transmit pilot signals to the network. When operating in an RRC common state, the UE may select a common set of resources to transmit pilot signals to the network. In either case, the pilot signals transmitted by the UE may be received by one or more network access devices, such as an AN or a DU, or portions thereof. Each receiving network access device may be configured to receive and measure pilot signals transmitted on the common set of resources as well as receive and measure pilot signals transmitted on dedicated sets of resources allocated to UEs for which the network access device is a member of a monitoring set of network access devices for the UE. One or more of the receiving network access devices, or a CU to which the receiving network access device transmits measurements of pilot signals, may use the measurements to identify a serving cell for the UE or to initiate a change of serving cell for one or more of the UEs.

[0063] Exemplary Selection Between Code Types for Encoding Information Bits In coding theory, concatenated codes form a class of error-correcting codes derived by combining an inner code and an outer code to form a stronger and more reliable code. The inner code and the outer code are generally used in conjunction to form a stronger combined code. Information bits may first be coded using the outer code, and then the coded information bits may be coded again using the inner code. The operations at the receiver to decode the coded bits are generally in reverse order. For example, at the receiver, decoding of the inner coding is performed first, followed by decoding of the outer coding. In some aspects, the outer code may be any error detection code, erasure code, or any error correction code. The outer code may include a parity bit J for false alarm detection. One example of an outer code is a cyclic redundancy check (CRC) code. The inner code may be any error correction code. The inner code may include an auxiliary parity bit J' to improve the decoding performance of the inner code.

[0064] FIG. 8 illustrates encoding and decoding using concatenated codes according to some aspects of the disclosure. 8a illustrates an encoding operation at a transmitter device 810 (e.g., a gNB or UE). As shown, the transmitter 810 includes an outer coder 812 and an inner coder 814. Information bits are first encoded by the outer coder 812 based on an outer code to output partially encoded information bits including parity bits (J). The encoded bits including the parity bits (J) are then encoded again by the inner coder 814 using an inner code to output coded bits including auxiliary parity bits (J'). The coded bits including the auxiliary parity bits (J') are transmitted by the transmitter 810.

[0065] 8b illustrates a decoding operation by a receiver 820 that corresponds to the encoding operation of 8a. As shown, the receiver 820 includes an inner decoder 822 and an outer decoder 824. The receiver 820 receives coded bits from the transmitter 810. The received coded bits are first decoded by the inner decoder 822 using the same inner code used by the transmitter 810 to output partially decoded bits including a parity bit (J). The partially decoded bits are then further decoded by the outer decoder 824 using the same outer code used by the transmitter 810 to recover the information bits.

[0066] In some aspects, a false alarm is a situation when an incorrectly decoded codeword is indicated as a valid codeword, for example by a cyclic redundancy check (CRC) code. The outer code parity bit length J dictates the false alarm detection accuracy, e.g., how accurate the false alarm detection is. In general, a longer parity bit length J leads to a lower false alarm probability (FAR). In one aspect, the outer code parity bit length J is determined by the false alarm probability (FAR) requirement. A lower (e.g., more stringent) FAR requirement generally requires more outer code parity bits J.

[0067] In some aspects, if a CRC code (or any effective error detection code) with J parity bits is used as the outer code, the false alarm probability can be 2^{-J} when no list-decoding (e.g., list size=1) is used for the inner code. No list-decoding is generally when the decoder has no more than one candidate to decode the codeword. In some aspects, if the inner code uses a list size L, the final false alarm probability can be 2^{-J+log2(list_size, L)}, which is higher compared to no list decoding. A higher false alarm probability is not desirable. However, it is generally a trade-off between having more error detection bits and having more decoding candidates. The larger the list, the better the decoding performance at the receiver. However, a larger list adversely affects false alarm detection in terms of the receiver's ability to detect errors in decoding.

[0068] In some aspects, different channel coding schemes perform differently in different information bit length (K) domains. In general, when K is very small (e.g., <12 bits), Reed-Muller (RM) codes may perform better than Polar codes. On the other hand, when K is large, Polar codes may outperform RM codes under comparable decoding complexity requirements.

[0069] Thus, in some aspects, it may be beneficial to select a coding scheme (e.g., an RM code or a Polar code) based at least on the number of information bits to be decoded. Furthermore, in addition to the information bit length (K), the selection between an RM code and a Polar code may need to take into account certain other parameters as well, which are described in more detail below.

[0070] Certain aspects of this disclosure describe techniques for selecting between RM and Polar codes for encoding / decoding information bits based on one or more channel coding parameters.

[0071] 9 illustrates example operations 900 that may be performed by a wireless device (e.g., a UE or gNB) to select a code type for coding information bits in accordance with certain aspects of the disclosure. The operations 900 begin at 902 by selecting a type of code from a set of code types to use as an inner code for a concatenated coding scheme for encoding information bits of a channel, the selection being based on a false alarm detection policy for the channel. At 904, the wireless device generates a codeword by encoding the information bits using the type of code selected as the inner code and the outer code. At 906, the wireless device transmits the codeword.

[0072] In some aspects, the set of code types includes at least one or more RM codes and one or more Polar codes. In some aspects, the selection between the RM codes and the Polar codes may be further performed based on additional parameters including the information bit length (K), the number of auxiliary parity bits J' included as part of the inner code, the outer code parity bit length J, and the list size L used in the list decoding algorithm at the receiver. In one aspect, the outer code parity bit length J and the list size L together determine the false alarm probability (FAR). As mentioned above, the FAR for list decoding may be 2^{-J+log2(list_size, L)}.

[0073] In some aspects, a metric may be generated as a function of one or more of the parameters described above, and the selection between RM codes and Polar codes may be performed based on the metric. In one aspect, the metric may be a function of the information bit length (K), the FAR requirement (P_{fa}), where {fa} represents false alarm, and the decoding list requirement L, and the selection between RM codes and Polar codes may be subject to a threshold determination based on this metric.

[0074] In an example scenario, the metric as a function of K, (P_{fa}), and L may be K+log2(1 / P_{fa})+log2(L). In one aspect, if K+log2(1 / P_{fa})+log2(L) is higher than a threshold, a Polar code is selected as the inner code and the outer code parity bits J are set as log2(1 / P_{fa})+log2(L) parity bits. On the other hand, if K+log2(1 / P_{fa})+log2(L) is below the threshold, an RM code is selected as the inner code and the outer code parity bits J are set as log2(1 / P_{fa})+log2(L) parity bits.

[0075] In some aspects, a budget (e.g., number of bits) is generally allocated for J+J' overhead bits. Thus, if J is small (or 0), indicating less stringent or no false alarm requirements, an additional auxiliary parity bit J' may be used to improve decoding performance. For example, if J is below a threshold, J' may be set to 3. On the other hand, if J is above the threshold, J' may be set to 0.

[0076] In some aspects, the false alarm requirement may be determined by a device (eg, a receiver) in a number of ways.

[0077] In one aspect, the false alarm requirement may be implicit in a specification (e.g., a Third Generation Partnership Project, 3GPP specification). For example, the specification may specify the number of hypotheses that a device must check (e.g., during blind decoding) to decode a channel / message. The device may implicitly derive the false alarm requirement based on this information. In general, the more hypotheses a device must check, the higher the false alarm requirement since the probability of error is greater.

[0078] In one aspect, the false alarm requirement may be explicitly signaled to the device, for example, via RRC signaling. For example, the gNB may signal to the UE what false alarm requirement is used for each channel. The UE may perform decoding on the channel based on the received signaling and one or more rules described above.

[0079] In one aspect, the false alarm requirement may depend on the type of channel being encoded / decoded. Different channels may have different false alarm requirements. For example, for some channels (e.g., PDCCH), the receiving device may need to check several hypotheses to decode the channel and may need to determine whether the decoded codeword is valid in each of the hypotheses. This generally leads to higher false alarm (lower and more stringent false alarm probability) requirements. However, for some channels (e.g., PUCCH), the gNB may indicate to the receiving device (e.g., UE) where to look for the channel. This generally leads to lower false alarm requirements. In one aspect, Group Common (GC)-PDCCH has a long CRC and higher FAR requirement, normal PDCCH has a long CRC and lower FAR requirement, UCI on PUCCH has a short CRC and lower FAR requirement, and UCI on PUSCH has a long CRC and higher FAR requirement.

[0080] In one aspect, the false alarm requirement may depend on the number of retransmissions, e.g., the requirement may increase for retransmissions and the requirement may be higher for a larger number of retransmissions.

[0081] In some aspects, based on the determined false alarm requirement, the device may determine a value of J and may use the value to decode the transmission. For example, the device may determine to use RM decoding or Polar decoding for a particular channel / message. In one aspect, if the outer code includes a CRC, the number of parity bits J of the CRC may depend on the false alarm requirement.

[0082] FIG. 10 illustrates a decision tree 1000 for determining a concatenated code for encoding information bits by a wireless device (e.g., a gNB or UE) in accordance with certain aspects of the present disclosure.

[0083] The decision tree 1000 begins at 1002 by determining the length (L) of information bits to be transmitted by the device. At 1004, the device determines a false alarm requirement (P_{fa}). As discussed above, the false alarm requirement (P_{fa}) may be determined by the device in several ways. At 1006, the device determines a list size (L) for transmission. At 1008, the device calculates a metric as a function of K, (P_{fa}), and L given by K+log2(1 / P_{fa})+log2(L).

[0084] In one aspect, the outer and inner codes are determined based on the calculated metric. At 1010, the metric is compared to a threshold. If the metric is greater than the threshold, the outer code parity bit J is set as log2(1 / P_{fa})+log2(L) parity bits at 1012, and a Polar code is selected as the inner code at 1014. Once the outer and inner codes are determined, an auxiliary parity bit (J') is set based on the determined parity bit (J). At 1020, the device compares the determined parity bit (J) to a J threshold. If J is less than the threshold, a longer J' is selected at 1022. On the other hand, if J is greater than the threshold, a shorter value of J' is selected at 1024. In one aspect, as described above, a budget is allocated for J+J' overhead bits, and J' may be allocated based on the budget allocated for J+J'.

[0085] Alternatively, if the UE determines at 1010 that the metric is below the threshold, the outer code parity bit J is set at 1016 as log2(1 / P_{fa})+log2(L) parity bits, and a Reed-Muller code is selected as the inner code at 1018. The auxiliary parity bit J' is selected as described above when the metric is greater than the threshold. For example, at 1026, the device compares the determined parity bit (J) with a threshold value for J. If J is less than the threshold, then at 1028, a longer J' is selected. On the other hand, if J is greater than the threshold, then at 1030, a shorter value of J' is selected.

[0086] In an example scenario, for the UL, if K≦12, then the RM code is selected if there is no FAR requirement and the number of CRC bits=0.

[0087] However, if there is a FAR requirement where K≦12 but the number of CRC bits for error detection (J>threshold, where threshold may be 0), then either CRC Aided (CA)-polar or CA-parity check (PC) polar (or may be PC polar in some cases) is selected. Different types of polar codes may be selected based on the FAR requirement.

[0088] Similarly, in the exemplary case when 12≦K≦22, if there is no FAR requirement and the number of CRC bits=0, then CA-PC polar (or possibly pure PC polar) is used with J′=6 assistant bits (which could be 3 CRC bits and 3 PC bits). However, if there is a FAR requirement where the number of CRC bits for error detection !=0 (e.g. 5-bit to 8-bit CRC), then CA-polar can be used as the opposite of CA-PC.

[0089] In some aspects, for K≦12, for DL ​​PDCCH, FAR needs to be guaranteed for normal PDCCH (not GC PDCCH). In this case, even for very small DCI payloads (e.g., K≦12), a good FAR is needed, and thus some CRC bits are needed. Therefore, in this case, if nFAR=16, polar codes are needed.

[0090] 11 illustrates a communications device 1100 that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as those illustrated in FIG. 9. The communications device 1100 includes a processing system 1102 coupled to a transceiver 1108. The transceiver 1108 is configured to transmit and receive signals for the communications device 1100 via an antenna 1110, such as various signals described herein. The processing system 1102 may be configured to perform processing functions for the communications device 1100, including processing signals received and / or transmitted by the communications device 1100.

[0091] The processing system 1102 includes a processor 1104 coupled to a computer-readable medium / memory 1112 via a bus 1106. In some aspects, the computer-readable medium / memory 1112 is configured to store instructions that, when executed by the processor 1104, cause the processor 1104 to perform the operations illustrated in FIG. 9 or other operations to perform various techniques described herein.

[0092] In some aspects, the computer-readable medium / memory 1112 includes a selection component 1114 that causes the processor to perform the selection operation shown in FIG. 9. Additionally, the computer-readable medium / memory 1112 includes a generation component 1116 that causes the processor 1104 to perform the generation operation shown in FIG. 9. Additionally, the computer-readable medium / memory 1112 includes a transmission component 1118 that causes the processor 1104 to perform the transmission operation shown in FIG. 9. The selection component 1114, the generation component 1116, and the transmission component 1118 may be coupled to the processor 1104 via the bus 1106. In some aspects, the selection component 1114, the generation component 1116, and the transmission component 1118 may be hardware circuits. In some aspects, the selection component 1114, the generation component 1116, and the transmission component 1118 may be software components that are executed and operated on the processor 1104.

[0093] The methods disclosed herein include one or more steps or actions for achieving the described method. The method steps and / or actions may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of specific steps and / or actions may be modified without departing from the scope of the claims.

[0094] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items including single members. As an example, "at least one of a, b, or c" is intended to encompass a, b, c, ab, ac, bc, and abc, as well as any combination having multiples of the same elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or a, b, and c in any other order).

[0095] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, "determining" may include resolving, selecting, electing, establishing, and the like.

[0096] The foregoing description is provided to enable any person skilled in the art to practice the various embodiments described herein. Various modifications of these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments. Thus, the claims are not limited to the embodiments shown herein, but are to be accorded all scope consistent with the claim language, and references to elements in the singular shall mean "one or more" and not "one and only" unless expressly stated otherwise. Unless otherwise stated, the term "several" refers to one or more. All structural and functional equivalents to the elements of the various embodiments described throughout this disclosure that are known or later become known to those skilled in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is made public, regardless of whether such disclosure is expressly set forth in the claims. No claim element is to be construed under the provisions of 35 U.S.C. 112, sixth paragraph, unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, unless the element is recited using the phrase "step for."

[0097] The various operations of the methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs), or processors. In general, where there are operations illustrated in figures, those operations may have corresponding counterpart means-plus-function components that are similarly numbered.

[0098] For example, the means for transmitting and / or the means for receiving may include one or more of the transmit processor 420, the TX MIMO processor 430, the receive processor 438, or the antennas 434 of the base station 110, and / or the transmit processor 464, the TX MIMO processor 466, the receive processor 458, or the antennas 452 of the user equipment 120. In addition, the means for selecting and the means for generating may comprise one or more processors, such as the controller / processor 480 of the user equipment 120 or the controller / processor 440 of the base station 110.

[0099] The various example logic blocks, modules, and circuits described in connection with this disclosure may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0100] When implemented in hardware, an exemplary hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. The bus may include any number of interconnecting buses and bridges depending on the particular application and overall design constraints of the processing system. The bus may link various circuits together, including the processor, the machine-readable medium, and the bus interface. The bus interface may be used to connect a network adapter to the processing system via the bus, among other things. The network adapter may be used to implement the signal processing functions of the PHY layer. In the case of a user terminal 120 (see FIG. 1), a user interface (e.g., keypad, display, mouse, joystick, etc.) may be connected to the bus. The bus may link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, etc., which are well known in the art and therefore will not be described further. The processor may be implemented using one or more general-purpose and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits capable of executing software. Those skilled in the art will recognize how to best implement the above-described functionality for a processing system depending on the particular application and the overall design constraints imposed on the overall system.

[0101] If implemented in software, the functions may be stored on or transmitted over a computer-readable medium as one or more instructions or code. Software should be broadly construed to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media includes both computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored in the machine-readable storage medium. The computer-readable storage medium may be coupled to the processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integral to the processor. By way of example, the machine-readable medium may include a transmission line, a carrier wave modulated by data, and / or a computer-readable storage medium on which instructions are stored separate from the wireless node, all of which may be accessed by the processor via a bus interface. Alternatively or additionally, the machine-readable medium, or any portion thereof, may be integrated into the processor, such as a cache and / or a general-purpose register file. Examples of the machine-readable storage medium may be, by way of example only, a RAM (random access memory), a flash memory, a ROM (read-only memory), a PROM (programmable read-only memory), an EPROM (erasable programmable read-only memory), an EEPROM (electrically erasable programmable read-only memory), a register, a magnetic disk, an optical disk, a hard drive, or any other suitable storage medium, or any combination thereof. The machine-readable medium may be embodied in a computer program product.

[0102] A software module may include a single instruction or many instructions and may be distributed across several different code segments, among different programs, and across multiple storage media. A computer-readable medium may include several software modules. The software modules include instructions that, when executed by a device such as a processor, cause a processing system to perform various functions. The software modules may include a transmitting module and a receiving module. Each software module may reside in a single storage device or may be distributed across multiple storage devices. As an example, a software module may be loaded from a hard drive into RAM when a trigger event occurs. During execution of a software module, the processor may load some of the instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general-purpose register file to be executed by the processor. When referring to a function of a software module below, it will be understood that such function is implemented by the processor when executing instructions from that software module.

[0103] Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Thus, in some aspects, computer-readable medium may include non-transitory computer-readable medium (e.g., tangible media). In addition, for other aspects, the computer-readable medium may include a transitory computer-readable medium (eg, a signal). Combinations of the above should also be included within the scope of computer-readable media.

[0104] Accordingly, some aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having stored thereon (and / or encoded thereon) instructions executable by one or more processors to perform the operations described herein.

[0105] Furthermore, it should be understood that modules and / or other suitable means for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by a user terminal and / or base station, where applicable. For example, such devices may be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, the various methods described herein may be provided via a storage means such that the user terminal and / or base station may obtain the various methods upon coupling or providing the storage means (e.g., RAM, ROM, physical storage medium such as a compact disk (CD) or floppy disk, etc.) to the device. Furthermore, any other suitable technique for providing the methods and techniques described herein to a device may be utilized.

[0106] It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims. [Explanation of symbols]

[0107] 100 Wireless Network 102a Macro Cell 102b Macrocell 102c Macrocell 102x picocell 102y Femtocell 102z Femtocell 110 Base Station (BS) 110a BS 110b BS 110c BS, Macro BS 110r relay station 110x BS 110y BS 110z BS 120 UE, user equipment, user terminal 120r UE 120x UE 120y UE 130 Network Controller 200 Distributed Radio Access Network (RAN), Local Architecture, Architecture 202 Access Node Controller (ANC) 204 Next Generation Core Network (NG-CN) 206 5G access nodes 208 TRP, D.U. 210 Next generation AN (NG-AN) 222 Tx / Rx 300 Distributed RAN 302 Centralized Core Network Unit (C-CU) 304 Centralized RAN Unit (C-RU) 306DU 412 Data Source 420 Processor, Transmitting Processor 432 Modulator, BS Modulator / Demodulator 432a~432t Modulators (MOD) 434 Antenna 434a~434t Antenna 436 MIMO Detector 438 Processor, Receiving Processor 439 Data Sink 440 Controller / Processor, Processor 442 Memory 444 Scheduler 452 Antenna 452a~452r Antenna 454 Demodulator 454a~454r Demodulator (DEMOD) 456 MIMO Detector 458 Processor, Receiving Processor 462 Data Sources 464 Processor, Transmit Processor 466 processor, TX MIMO processor 480 Controller / Processor, Processor 500 Figures 505-a First Option 505-b Second Option 510 Radio Resource Control (RRC) Layer 515 Packet Data Convergence Protocol (PDCP) Layer 520 Radio Link Control (RLC) Layer 525 Medium Access Control (MAC) Layer 530 Physical (PHY) Layer 600 Figures 604 DL data part 606 Common UL part 700 Figures 702 Control section 704 UL Data Part 706 Common UL part 810 Transmitter Device 812 External Coder 814 Internal Coda 820 Receiver 822 Internal Decoder 824 External Decoder 900 operations 1000 Decision Trees 1100 Communication Devices 1102 Processing System 1104 Processor 1106 Bus 1108 Transceiver 1110 Antenna 1112 Computer-readable medium / memory 1114 Selection Component 1116 Generated Component 1118 Transmission Component

Claims

1. 1. A method of wireless communication, comprising: selecting a type of code from a set of code types to use as an inner code for a concatenated coding scheme for encoding information bits of a channel, said selecting being based at least on a number of information bits of the channel to be encoded, said set of code types including at least a Reed-Muller code type and a polar code type; generating a codeword by encoding the information bits using the code type selected as the inner code and an outer code, the outer code including a cyclic redundancy check (CRC), the number of bits for the CRC being 0 if the inner code is the Reed-Muller code type, and the number of bits for the CRC being greater than 0 if the inner code is the polar code type; and transmitting said codeword.

2. The method of claim 1 , wherein the selecting is further based on a false alarm detection policy for the channel, the false alarm detection policy depending on a type of physical channel.

3. The method of claim 1 , wherein the selecting is further based on a false alarm detection policy for the channel, the false alarm detection policy depending on a number of retransmissions for the channel.

4. 2. The method of claim 1, wherein the selecting is further based on a false alarm detection policy for the channel, information regarding the false alarm detection policy being signaled via radio resource control (RRC) signaling.

5. 2. The method of claim 1, wherein selecting comprises selecting further based on at least one of a false alarm detection strategy for the channel, or a list decoding size.

6. 2. The method of claim 1, further comprising determining a number of auxiliary parity bits to use for the inner code in the concatenated coding scheme based at least in part on a code parity bit length of the outer code.

7. 1. An apparatus for wireless communication, comprising: means for selecting a type of code from a set of code types to use as an inner code for a concatenated coding scheme for encoding information bits of a channel, said selecting being based at least on a number of information bits of the channel to be encoded, said set of code types including at least a Reed-Muller code type and a polar code type; means for generating a codeword by encoding the information bits using the type of code selected as the inner code and an outer code, the outer code including a cyclic redundancy check (CRC), the number of bits for the CRC being 0 if the inner code is the Reed-Muller code type, and the number of bits for the CRC being greater than 0 if the inner code is the polar code type; and means for transmitting said codeword.

8. The apparatus of claim 7 , wherein the selecting is further based on a false alarm detection policy for the channel, the false alarm detection policy depending on a type of physical channel.

9. The apparatus of claim 7 , wherein the selecting is further based on a false alarm detection policy for the channel, the false alarm detection policy depending on a number of retransmissions for the channel.

10. 8. The apparatus of claim 7, wherein the selecting is further based on a false alarm detection policy for the channel, information regarding the false alarm detection policy being signaled via radio resource control (RRC) signaling.

11. 8. The apparatus of claim 7, wherein the means for selecting selects further based on at least one of a false alarm detection policy for the channel, or a list decoding size.

12. 8. The apparatus of claim 7, further comprising: means for determining a number of auxiliary parity bits to use for the inner code in the concatenated coding scheme based at least in part on a code parity bit length of the outer code.

13. 7. A computer program comprising instructions which, when executed by at least one processor of an apparatus for wireless communication, cause said apparatus to perform the method of any one of claims 1 to 6.

Images