Priority-based channel coding for control information

Abstract

Systems, methods, and means for priority-based channel coding of control information are disclosed. A wireless transmit / receive unit (WTRU) may classify control information associated with a first control information type into a first control information group and classify control information associated with a second control information type into a second control information group, for example, based on respective priorities associated with the first and second control information types. The WTRU may group one or more bits of the first control information group into a first bit-level control information group and a second bit-level control information group based on the priority. The WTRU may selectively apply a cyclic redundancy check (CRC) to the first control information group, the second control information group, the first bit-level control information group, and / or the second bit-level control information group.

Description

[0001] This application is a divisional application of Chinese Patent Application No. 201780049244.0, entitled “Priority-Based Channel Coding for Control Information”, filed on August 10, 2017, which is incorporated herein by reference.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Patent Application No. 62 / 373,005 filed on August 10, 2016, U.S. Provisional Patent Application No. 62 / 400,704 filed on September 28, 2016, and U.S. Provisional Patent Application No. 62 / 443,059 filed on January 6, 2017, all of which are incorporated herein by reference. Background Art

[0004] Emerging use cases for 5G systems may include enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable and low latency communications (URLLC). Different use cases may focus on different requirements, such as higher data rates, higher spectral efficiency, low power and higher energy efficiency, lower latency, and / or higher reliability.

[0005] The acquisition of control information may be important for 5G New Radio (NR). Efficient and reliable delivery of control information may be desired. Unreliable control information may affect performance, data rate, latency and / or MIMO system operation. If the acquisition of scheduling grants is unreliable, scheduling time and / or hybrid automatic repeat request (HARQ) delays and retransmissions may be affected. When the acquisition of ACK / NACK is unreliable, HARQ may be affected. If RI / PMI is unreliable, MIMO operation and / or performance may be affected. Summary of the invention

[0006] Systems, methods, and means for priority-based channel coding of control information are disclosed. A wireless transmit / receive unit (WTRU) may determine control information associated with a first control information type, a second control information type, and / or a third control information type. The WTRU may determine the control information based on data transmission. The control information may be associated with multiple control information types. The multiple control information types may include a synchronization signal (SS) block index (SSBI), a rank indicator (RI), a precoding matrix indicator (PMI), a channel quality indicator (CQI), a CSI-RS resource indicator (CRI), a precoder type indicator (PTI), a beam ID (BeamID), ACK / NACK, and / or a scheduling request (SR). The WTRU may classify the control information associated with the first control information type into a first control information group. The WTRU may classify the control information associated with the second control information type into a second control information group. The WTRU may classify the control information associated with the third control information type into a third control information group and a fourth control information group. The third control information group and the fourth control information group may be associated with multi-carrier, multi-spectrum, multi-frequency and / or multi-band. The control information may be sorted based on respective priorities associated with the first control information type and the second control information type.

[0007] The WTRU may group one or more bits of the first control information group into a first bit-level control information group and a second bit-level control group. The first bit-level control information group may be associated with a first priority. The second bit-level control information group may be associated with a second priority. The WTRU may group the first control information group based on the first priority and the second priority. The first bit-level control information group may be a control least significant bit (LSB) group. The second bit-level control information group may be a control most significant bit (MSB) group. The WTRU may group one or more bits of the second control information group into a third bit-level control information group and a fourth bit-level control information group. The third bit-level control information group may be associated with a third priority. The fourth bit-level control information group may be associated with a fourth priority. The bits of the second control information group are grouped based on the third priority and the fourth priority. The third and fourth bit-level control information groups may be associated with multiple carriers, spectrums, frequencies, and / or frequency bands.

[0008] The WTRU may selectively apply a first cyclic redundancy check (CRC) to the first control information group, the second control information group, the first bit-level control information group, and / or the second bit-level control information group. The WTRU may selectively apply the first CRC by determining to append the first CRC to the first bit-level control information group or the second bit-level control information group. The WTRU may selectively apply the first CRC by determining to append the first CRC to both the first and second bit-level control information groups. The WTRU may selectively apply the first CRC by determining to append the first CRC to each MSB bit-level control information group. The WTRU may selectively apply the first CRC by determining to append the first CRC to each MSB bit-level control information group and append the second CRC to each LSB bit-level control information group.

[0009] The WTRU may map the control information to one or more bit channels of a polar encoder, for example, based on the classification, the grouping, and / or the selective application of the CRC. The WTRU may determine whether to use a concatenated polar encoder or a non-concatenated polar encoder, for example, based on performance and / or delay requirements. The WTRU may determine the performance and / or delay requirements based on decoder capabilities, information block size, and / or coding rate. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1A is a system diagram illustrating an example communication system in which one or more disclosed embodiments may be implemented;

[0011] Figure 1B It is shown that according to the embodiment, Figure 1A A system diagram of an example wireless transmit / receive unit (WTRU) used in a communication system shown in FIG.

[0012] Figure 1C It is shown that according to the embodiment, Figure 1A A system diagram of an example radio access network (RAN) and an example core network (CN) used in a communication system shown in FIG.

[0013] Figure 1D It is shown that according to the embodiment, Figure 1A A system diagram of another example RAN and another example CN used in the communication system shown in FIG.

[0014] Figure 2 Depicting an example polar encoder with N=8;

[0015] Figure 3 Depicts example PC polar codes;

[0016] Figure 4 depicts an example concatenated PC polar code with 2 parallel segments;

[0017] Figure 5 depicts an example joint encoding of multiple control information using polar coding;

[0018] Figure 6 depicts example joint encoding of control information using polar coding with priority classification, priority grouping, and bit-channel group priority mapping;

[0019] Figure 7 depicts exemplary prioritized control information channel coding using polarization coding;

[0020] Figure 8 depicts an exemplary prioritization of control information using polar coding;

[0021] Fig. 9 depicts an exemplary prioritization of control information using polar coding;

[0022] Fig.10 Depicting exemplary polar coding prioritization of control information with duplication protection for high priority information;

[0023] Fig.11 depicting exemplary priority-based channel quality indicator (CQI) accuracy;

[0024] Fig.12 depicting exemplary priority-based beam identification (BeamID) accuracy;

[0025] Fig.13 Describing an exemplary prioritized CQI control message accuracy using polar coding;

[0026] Fig.14 depicts an exemplary prioritization control message accuracy using polar coding;

[0027] Fig.15 Depicting an exemplary prioritized control message accuracy with separate CRC using polar coding;

[0028] Fig.16 Depicting exemplary prioritized control message accuracy using polar coding with CRC for MSB protection;

[0029] Fig.17 depicts exemplary prioritization of control message fields and bit levels using polar coding;

[0030] Fig.18 depicts exemplary prioritization of control message fields and bit levels using polar coding;

[0031] Fig.19 depicts exemplary prioritized control message fields;

[0032] Fig. 20 Depicted is an exemplary decision made between concatenated PC polar codes and non-concatenated PC polar codes. DETAILED DESCRIPTION

[0033] A detailed description of illustrative embodiments will now be described with reference to the various drawings.While this description provides detailed examples of possible embodiments, it should be noted that the details are intended to be exemplary and not to limit the scope of the application in any way.

[0034] Figure 1A 1 is a diagram showing an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, broadcast, etc. to multiple wireless users. The communication system 100 allows multiple wireless users to access such content by sharing system resources including wireless bandwidth. For example, the communication system 100 may employ one or more channel access methods such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single carrier FDMA (SC-FDMA), zero tail unique word DFT spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block filtered OFDM, filter bank multi-carrier (FBMC), etc.

[0035] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, public switched telephone network (PSTN) 108, Internet 110 and other networks 112, but it should be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network components. Each WTRU 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, the WTRUs 102a, 102b, 102c, 102d (any of which may be referred to as a "station" and / or "STA") may be configured to transmit and / or receive wireless signals and may include user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in an industrial and / or automated process chain environment), a consumer electronic device, a device operating on a commercial and / or industrial wireless network, etc. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0036] The communication system 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or other networks 112, by wirelessly interfacing with at least one of the WTRUs 102a, 102b, 102c, 102d. By way of example, the base stations 114a, 114b may be base transceiver stations (BTS), Node Bs, eNode Bs, Home Node Bs, Home eNode Bs, gNBs, NR Node Bs, site controllers, access points (APs), wireless routers, and the like. Although each of the base stations 114a, 114b is depicted as a single component, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network components.

[0037] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network components (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, and the like. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies called cells (not shown). These frequencies may be licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for wireless services in a specific geographic area that may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, a cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, that is, each transceiver corresponds to a sector of the cell. In another embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0038] The base stations 114a, 114b may communicate with one or more WTRUs 102a, 102b, 102c, 102d via an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0039] More specifically, as described above, the communication system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), and the technology may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117. WCDMA may include communication protocols such as High Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High Speed ​​UL Packet Access (HSUPA).

[0040] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0041] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR radio access, which may establish the air interface 116 using New Radio (NR).

[0042] In one embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, such as using dual connectivity (DC) principles. Thus, the air interface used by the WTRUs 102a, 102b, 102c may be characterized by multiple radio access technologies and / or transmissions to / from multiple base stations (e.g., NBs and gNBs).

[0043] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as IEEE 802.11 (and, Wireless Fidelity (WiFi)), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), GSM Enhanced Data rates for Evolution (EDGE), GSM EDGE (GERAN), etc.

[0044] Figure 1AThe base station 114b in the example may be, for example, a wireless router, a Home NodeB, a Home eNodeB, or an access point, and may use any appropriate RAT to facilitate wireless connectivity in a local area, such as a business location, a residence, a vehicle, a campus, an industrial facility, an air corridor (e.g., a drone), a road, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless local area network (WLAN) by implementing a radio technology such as IEEE 802.11. In another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a wireless personal area network (WPAN) by implementing a radio technology such as IEEE 802.15. In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may establish a picocell or a femtocell by using a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). Figure 1A As shown, the base station 114b may be directly connected to the Internet 110. Thus, the base station 114b may not necessarily need to access the Internet 110 via the CN 106 / 115.

[0045] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications and / or Voice over Internet Protocol (VoIP) services to one or more WTRUs 102a, 102b, 102c, 102d. The data may have variable quality of service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. The CN 106 / 115 may provide call control, billing services, mobile location-based services, pre-paid calls, Internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication. Although in Figure 1A Although not shown, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT or a different RAT as the RAN 104 / 113. For example, in addition to being connected to the RAN 104 / 113 employing NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0046] The CN 106 / 115 may also act as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer network devices that use a common communication protocol, such as TCP, User Datagram Protocol (UDP), and / or IP in the Transmission Control Protocol (TCP) / Internet Protocol (IP) Internet protocol suite. The networks 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may use the same RAT or a different RAT as the RAN 104 / 113.

[0047] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). Figure 1A The illustrated WTRU 102c may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0048] Figure 1B is a system diagram showing an example WTRU 102. Figure 1B As shown, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138. It should be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0049] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Figure 1B The processor 118 and the transceiver 120 are depicted as separate components, but it is understood that the processor 118 and the transceiver 120 may be integrated into one electronic package or chip.

[0050] The transmit / receive component 122 may be configured to transmit or receive signals to or from a base station (e.g., base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive component 122 may be an antenna configured to transmit and / or receive RF signals. In another embodiment, as an example, the transmit / receive component 122 may be a transmitter / detector configured to transmit and / or receive IR, UV, or visible light signals. In yet another embodiment, the transmit / receive component 122 may be configured to transmit and receive RF and light signals. It should be appreciated that the transmit / receive component 122 may be configured to transmit and / or receive any combination of wireless signals.

[0051] Although in Figure 1B 102 as a single component, but the WTRU 102 may include any number of transmit / receive components 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive components 122 (e.g., multiple antennas) for transmitting and receiving radio signals via the air interface 116.

[0052] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers that allow the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0053] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keyboard 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may receive user input data from these components. The processor 118 may also output user data to the speaker / microphone 124, the keyboard 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from and store information in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0054] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control power for use by other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (Ni-Cd), nickel-zinc (Ni-Zn), nickel-metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, etc.

[0055] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) related to the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) via the air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information using any suitable positioning method while remaining consistent with an embodiment.

[0056] The processor 118 may also be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands-free headset, module, a frequency modulation (FM) radio unit, a digital music player, a media player, a video game console module, an Internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, etc. The peripheral device 138 may include one or more sensors, which may be a gyroscope, an accelerometer, a Hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geographic location sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor, etc. One or more.

[0057] The WTRU 102 may include a full-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) and downlink (e.g., for reception)) may be concurrent and / or synchronized. The full-duplex radio may include an interference management unit 139 to reduce and / or substantially eliminate self-interference via hardware (e.g., choke) or via signal processing by a processor (e.g., a separate processor (not shown) or via the processor 118). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all signals (e.g., associated with specific subframes for UL (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or synchronized. The full-duplex radio may include an interference management unit 139 to reduce and / or substantially eliminate self-interference via hardware (e.g., choke) or via signal processing by a processor (e.g., a separate processor (not shown) or via the processor 118).

[0058] Figure 1C 1 is a system diagram of the RAN 104 and the CN 106 according to an embodiment. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0059] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. Each of the eNode-Bs 160a, 160b, 160c may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, for example, the eNode-B 160a may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

[0060] Each eNodeB 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. Figure 1C As shown, the eNode-Bs 160a, 160b, 160c may communicate with one another via an X2 interface.

[0061] Figure 1C The illustrated CN 106 may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. Although each of the above components is described as being part of the CN 106, it should be understood that entities other than the CN operator may also own and / or operate any of these components.

[0062] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, activating / deactivating bearers, selecting a particular serving gateway during an initial attach procedure for the WTRUs 102a, 102b, 102c, and the like. The MME 162 may also provide a control plane function to facilitate handover between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0063] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. In addition, the SGW 164 may perform other functions, such as anchoring the user plane during inter-eNode-B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing the contexts of the WTRUs 102a, 102b, 102c, and the like.

[0064] The SGW 164 may be connected to the PGW 166 and may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0065] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks such as the PSTN 108 to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. As an example, the CN 106 may include or communicate with an IP gateway, such as an IP Multimedia Subsystem (IMS) server, which serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0066] Although Figures 1A-1D The WTRU is described as a wireless terminal, but it is contemplated that in some typical embodiments such a terminal may use (eg, temporarily or permanently) a wired communication interface with a communication network.

[0067] In a typical implementation, the other network 112 may be a WLAN.

[0068] A WLAN in infrastructure basic service set (BSS) mode may have an access point (AP) for a BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a distribution system (DS) or another type of wired / wireless network that carries services in and / or out of the BSS. Services originating from outside the BSS to the STA may be reached by the AP and may be delivered to the STA. Services originating from the STA to a destination outside the BSS may be sent to the AP to be delivered to the corresponding destination. Services between STAs within the BSS may be sent through the AP, for example, where the source STA may send services to the AP and the AP may deliver the services to the destination STA. Such services between STAs within the BSS may be considered and / or referred to as peer-to-peer services. Peer-to-peer services may be sent (directly) between the source STA and the destination STA using a direct link setup (DLS). In certain typical embodiments, the DLS may use 802.11e DLS or 802.11z tunneled DLS (TDLS). A WLAN using an independent BSS (IBSS) mode may not have an AP, and STAs (e.g., all STAs) within or using the IBSS may communicate directly with each other. This IBSS mode of communication may sometimes be referred to herein as "ad-hoc" mode of communication.

[0069] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel, such as a primary channel. The primary channel can have a fixed width (e.g., a 20 MHz wide bandwidth), or the width can be dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In certain typical embodiments, carrier sense multiple access with collision avoidance (CSMA / CA) can be implemented, such as in an 802.11 system. For CSMA / CA, STAs (e.g., each STA), including the AP, can listen to the primary channel. If the primary channel is sensed / detected to be busy and / or determined to be busy by a particular STA, the particular STA can back off. One STA (e.g., only one station) can transmit at any given time in a given BSS.

[0070] A high throughput (HT) STA may communicate using a 40 MHz wide channel, for example, by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0071] Very high throughput (VHT) STA can support 20MHz, 40MHz, 80MHz and / or 160MHz wide channels. 40MHz and / or 80MHz channels can be formed by merging continuous 20MHz channels. A 160MHz channel can be formed by merging 8 continuous 20MHz channels or by merging two non-contiguous 80MHz channels, which can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data can be passed through a segment parser that can divide the data into two streams. Each stream is subjected to an inverse fast Fourier transform (IFFT) and time domain processing, respectively. The stream can be mapped onto two 80MHz channels, and the data is transmitted by the transmitting STA. At the receiver of the receiving STA, the above operations for the 80+80 configuration can be flipped, and the combined data is sent to the media access control (MAC).

[0072] 802.11af and 802.11ah support operation in Sub 1GHz mode. Channel operating bandwidth and carrier are reduced relative to those used in 802.11n and 802.11ac. 802.11af supports 5MHz, 10MHz and 20MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1MHz, 2MHz, 4MHz, 8MHz and 16MHz bandwidths using non-TVWS spectrum. According to a typical embodiment, 802.11ah can support instrument type control / mechanical class communications (such as MTC devices) in macro coverage areas. MTC devices may have specific capabilities, such as limited capabilities including support for (e.g., only support for) specific and / or limited bandwidths. MTC devices may include batteries with battery life above a threshold (e.g., maintaining very long battery life).

[0073] A WLAN system that can support multiple channels and channel bandwidths (such as 802.11n, 802.11ac, 802.11af, and 802.11ah) includes a channel that can be designed as a main channel. The main channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the main channel may be set and / or limited by a STA (from all STAs operating in the BSS) that supports the minimum bandwidth operating mode. In the example of 802.11ah, for a STA (e.g., an MTC class device) that supports (e.g., only supports) a 1MHz mode, the main channel may be 1MHz wide even if the AP and other STAs in the BSS support 2MHz, 4MHz, 8MHz, 16MHz, or other channel bandwidth operating modes. Carrier sensing and / or network allocation vector (NAV) settings may depend on the state of the main channel. If the main channel is busy, for example, due to a STA (which only supports a 1MHz operating mode) transmitting to the AP, the entire available band may be considered busy, even if most of the band is idle and available.

[0074] In the United States, the available frequency band that can be used by 802.11ah is from 902MHz to 928MHz. In Korea, the available frequency band that can be used is from 917.5MHz to 923.5MHz. In Japan, the available frequency band is from 916.5MHz to 927.5MHz. Depending on the country code, the total bandwidth available for 802.11ah is 6MHz to 26MHz.

[0075] Figure 1D 1 is a system diagram showing the RAN 113 and the CN 115 in accordance with an embodiment. As noted above, the RAN 113 may employ NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0076] The RAN 113 may include gNBs 180a, 180b, 180c, by which it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, the gNBs 180a, 180b, 180c may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, for example, the gNB 180a may use multiple antennas to transmit wireless signals to and / or receive wireless signals from the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers (not shown) to the WTRU 102a. A subset of these component carriers may be on an unlicensed spectrum, while the remaining component carriers may be on a licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement coordinated multi-point (CoMP) technology. For example, the WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0077] The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using transmissions associated with scalable parameters (numerology). For example, OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different portions of the wireless transmission spectrum, for different cells, and / or for different transmissions. The WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using different or scaled length transmission time intervals (TTIs) or subframes (e.g., containing different numbers of OFDM symbols and / or continuously varying absolute time lengths).

[0078] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c without accessing other RANs (e.g., such as the eNode-Bs 160a, 160b, 160c). In a standalone configuration, the WTRUs 102a, 102b, 102c may utilize one or more of the gNBs 180a, 180b, 180c as mobility anchors. In a standalone configuration, the WTRUs 102a, 102b, 102c may communicate with the gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration, the WTRUs 102a, 102b, 102c may communicate / connect with the gNBs 180a, 180b, 180c while also communicating / connecting with another RAN, such as an eNode-B 160a, 160b, 160c. For example, the WTRUs 102a, 102b, 102c may implement the DC principle to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In a non-standalone configuration, the eNode-Bs 160a, 160b, 160c may serve as mobility anchors for the WTRUs 102a, 102b, 102c and the gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for serving the WTRUs 102a, 102b, 102c.

[0079] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in UL and / or DL, support for network slicing, dual connectivity, interaction between NR and E-UTRA, routing of user plane data to a user plane function (UPF) 184a, 184b, routing of control plane information to an access and mobility management function (AMF) 182a, 182b, and the like. Figure 1D As shown, gNBs 180a, 180b, 180c may communicate with one another via an Xn interface.

[0080] Figure 1DThe illustrated CN 115 may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF 183a, 183b), and possibly a data network (DN) 185a, 185b. Although each of the aforementioned elements is described as being part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0081] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via the N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, supporting network slicing (e.g., handling different PDU sessions with different requirements), selecting a specific SMF 183a, 183b, management of registration areas, termination of NAS signaling, mobility management, etc. Network slicing may be used by the AMF 182a, 182b to customize support for the WTRUs 102a, 102b, 102c based on the type of service being used by the WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases, such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine-type communications (MTC) access, etc. The AMF 162 may provide control plane functions for switching between the RAN 113 and other RANs (not shown) employing other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0082] The SMF 183a, 183b may be connected to the AMF 182a, 182b in the CN 115 via the N11 interface. The SMF 183a, 183b may also be connected to the UPF 184a, 184b in the CN 115 via the N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of services through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. The PDU session type may be IP-based, non-IP-based, Ethernet-based, and the like.

[0083] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Ethernet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

[0084] The CN 115 may facilitate communications with other networks, for example, the CN 115 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) or may communicate with an IP gateway that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local data network (DN) 185a, 185b through a UPF 184a, 184b via an N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0085] according to Figures 1A-1D ,as well as Figures 1A-1D , one or more or all of the functions described herein with respect to one or more of the following may be performed by one or more emulation devices (not shown): WTRU 102a-d, base station 114a-b, eNodeB 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-ab, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein. The emulation device may be one or more devices configured to emulate one or more or all of the functions described herein. For example, the emulation device may be used to test other devices and / or simulate network and / or WTRU functions.

[0086] The simulation device can be designed to implement one or more tests on other devices in a laboratory environment and / or in an operator network environment. For example, when fully or partially implemented and / or deployed as part of a wired and / or wireless communication network, one or more simulation devices can perform one or more or all functions to test other devices in the communication network. When temporarily implemented and / or deployed as part of a wired and / or wireless communication network, one or more simulation devices can perform one or more or all functions. The simulation device can be directly coupled to another device and / or perform the test using wireless communication over the air for the purpose of testing.

[0087] One or more simulation devices may perform one or more (including all) functions when not implemented / deployed as part of a wired and / or wireless communication network. For example, the simulation device may be used in a test lab and / or in a test scenario in which a wired and / or wireless communication network is not deployed (e.g., testing) to implement testing of one or more components. The one or more simulation devices may be test devices. Direct RF coupling and / or wireless communication via RF circuits (e.g., which may include one or more antennas) may be used by the simulation device to transmit and / or receive data.

[0088] Use cases for emerging 5G systems may include enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Different use cases may focus on different requirements, such as higher data rates, higher spectral efficiency, low power consumption and higher energy efficiency, lower latency and / or higher reliability.

[0089] The acquisition of control information may be important for 5G New Radio (NR). Efficient and reliable delivery of control information may be desired. Unreliable control information may affect performance, data rate, latency and / or MIMO system operation. If the acquisition of scheduling grants is unreliable, scheduling time and / or hybrid AQR (HAQR) delays and retransmissions may be affected. If the acquisition of CQI is unreliable, scheduling, link adaptation and / or MCS may be affected. When the acquisition of ACK / NACK is unreliable, HARQ may be affected. If RI / PMI is unreliable, MIMO operation and / or performance may be affected.

[0090] Polar codes may be capacity achieving codes (eg, similar to turbo codes and LDPC codes). Polar codes may include linear block codes with low encoding and / or decoding complexity, low or no error floor, and well-defined structure.

[0091] Regarding (N,K) polar codes, where K is the information block length and N is the coding block length. The value of N can be set to a power of 2, for example, for some integer n, N=2 n The polar code can be a linear block code. The generator matrix of the polar code can be given by Indicates that B N is the bit-reversal permutation matrix, represents the nth Kronecker product (Kroneckerpower), and In the implementation of polar code, B N The bit reversal operation may be ignored on the encoder side (eg, for simplicity) and the bit reversal operation may be performed on the decoder side.

[0092] Figure 2 An example plan encoder 200 with N=8 is described. Figure 2 As shown, N = 8 can be expressed The codewords of polar codes can be Given.

[0093] Polar coding may include consecutive cancellation (SC) decoding. Polar coding may include consecutive cancellation list (SCL) decoding and / or CRC assisted SCL decoding.

[0094] Polar codes can be well constructed in terms of encoding and decoding. The effectiveness of polar code design can depend on the K information bits to the polar encoder. The K information bits may be allocated to the K best bit channels. The remaining N-K input bits not mapped from the information bits may be frozen bits. The frozen bits may generally be set to 0. The set of positions of the frozen bits may be referred to as a frozen set.

[0095] The determination of the best bit channel may vary and / or depend on channel conditions. The bit channels may be ranked based on reliability (e.g., to determine a set of frozen channels). One or more reliable bit channels may be determined as good bit channels and one or more bit channels of poor reliability may be determined as bad bit channels.

[0096] The reliability of the bit channel can be calculated, for example, using one or more of the following: Bhattacharyya bounds, Monte Carlo estimation, complete transition probability matrix estimation, or Gaussian approximation. Calculating the reliability of the bit channel can be associated with different computational complexities and / or can depend on different channel conditions. The design SNR parameters can be selected before starting the reliability calculation.

[0097] Puncture and / or rate matching may be performed in polar coding. The output of the polar decoder may be a power of 2, which may impose polar coding restrictions. The length of the information bit (K) and / or the coding rate (R) may be predetermined. The codeword block length may be determined as The codeword block length may not be a power of 2. Some puncturing of the output bits may be greater than The minimum number of bits to perform is a power of 2. For example, when K = 100 bits and When , the output codeword length can be expected to be 300 bits. 512 bits can be generated by the polar decoder and 212 bits can be punctured from the 512 bits.

[0098] Parity check (PC) polar codes and / or CRC assisted (CA) polar codes may be provided. PC polar codes may be different from polar codes. For example, in PC polar codes, a subset of a set of frozen subchannels may be selected as PC frozen subchannels. A PC function may be established on selected PC frozen subchannels (e.g., for error correction). In each parity check subchannel position, the decoding bits involved in the PC function on the PC frozen subchannel may help prune the list decoding tree. For example, only paths that comply with the PC function may remain, and the remaining paths may be eliminated, e.g., not functioning. The PC function may be established as forward only to be consistent with any consecutive cancellation-based decoders. Figure 3 An example PC polar code 300 is depicted.

[0099] Chained polar codes may be provided. In chained polar codes, a long codeword may be divided into two or more shorter code fields and the code fields may be decoded in parallel. Figure 4 An example concatenated PC polar code 400 with 2 parallel segments is depicted. As shown, the first segment may not include a set of PC frozen bits, while the second segment may include a set of PC frozen bits. A cross parity check function may be used for the first segment (e.g., when the PC frozen bit set is in the second segment). A self parity check function may be used for the second segment. Both the self parity check function and the cross parity check function may be forward-only functions so that the continuous cancellation property of the polar decoder may be maintained.

[0100] Concatenated polar codes may be able to reduce decoding delay because segments can be decoded in parallel. If the codewords require rate matching, concatenated polar codes may improve the performance of polar codes (e.g., because it can avoid deep puncturing of the mother codeword, which may result in performance degradation).

[0101] The acquisition of control information may be important for 5G NR. Efficient and / or reliable delivery of control information may be desired. Unreliable control information may adversely affect performance, data rate, delay and / or MIMO system operation. If the acquisition of scheduling grant is unreliable, the scheduling time and / or retransmission, delay of hybrid ARQ (HARQ) may be affected (e.g., adversely). If the acquisition of CQI is unreliable, scheduling, link adaptation and / or MCS may be affected. When the acquisition of ACK / NACK is unreliable, it affects HARQ and throughput. When the acquisition of RI / PMI is unreliable, MIMO operation, performance, data rate and / or throughput may be affected (e.g., adversely).

[0102] Priority-based channel coding of control information may be used when a large amount of control information of 5G and / or New Radio (NR) requires more efficient coding for control channels. Priority-based channel coding of control information may be used when control information needs to be transmitted and / or reported jointly and simultaneously.

[0103] When different control information has different importance levels, priority-based channel coding of the control information may be used. The control information may include a control message, a control message field, a control information field, etc. The control information may be associated with multiple control information types. Each control information type may be associated with a corresponding priority.

[0104] When different bits in a control message / field have different levels of importance, priority-based channel coding of the control information may be used.

[0105] When priority-based jointly coded uplink control information is transmitted for WTRU feedback, priority-based channel coding of the control information may be performed.

[0106] The WTRU may be configured to perform joint encoding of multiple control information using polarization codes of control channels in the uplink. The base station (e.g., gNB, eNB, AP, etc.) may be configured to perform joint encoding of multiple control information using polarization codewords of control channels in the downlink.

[0107] Priorities may be predefined and / or configured for control information. For example, if priorities are predefined, the WTRU may prioritize control information based on the predefined priorities and / or one or more priority rules. If priorities are configured, the WTRU may receive an indication to prioritize control information based on the indicated priorities and / or one or more priority rules. Different priorities and / or priority rules may be applied to different levels of control information. For example, different priorities and / or priority rules may be applied to control information, control information types, control messages, instances of control information, control fields, control message fields, bit fields, control bits, and / or other types of control information.

[0108] The WTRU may be configured to perform a prioritization procedure for control information that is jointly encoded with other control information in the uplink. A base station (e.g., a gNB, an eNB, an AP, etc.) may be configured to perform a prioritization procedure for control information that is jointly encoded with other control information in the downlink. For example, the WTRU and / or the base station may prioritize the control information.

[0109] The WTRU may be configured to prioritize control information, for example, at a bit level, for joint coding in the uplink. The base station (e.g., gNb, eNB, AP, etc.) may be configured to prioritize control information, for example, at a bit level, for joint coding in the downlink.

[0110] The WTRU may be configured to perform mixed and / or joint prioritization of bit-level control information and control information, e.g., for joint coding in the uplink. A base station (e.g., gNb, eNB, AP, etc.) may be configured to perform mixed and / or joint prioritization of bit-level control information and control information, e.g., for joint coding in the downlink. For example, the WTRU and / or the base station may jointly prioritize control information and bit-level control information.

[0111] Commonly coded and prioritized control information may be transmitted.The examples described herein may be described with respect to one of the uplink or downlink, but the examples may be applied to both the uplink and the downlink.

[0112] Joint coding of control information may include using polar codes for control information. The control information may include multiple parts. For example, the control information may include multiple instances of control information. An instance of control information may include one or more messages and / or one or more control message fields. An instance of control information may be associated with multiple control information types. The control information type may include one or more of the following: synchronization signal (SS) block index (SSBI), rank indicator (RI), precoding matrix indicator (PMI), channel quality indicator (CQI), CSI-RS resource indicator (CRI), precoder type indicator (PTI), HARQ NACK, beam ID, scheduling request (SR), other WTRU feedback information, etc. The control information may be jointly encoded (e.g., to achieve more efficient channel coding and / or maximize coding gain). Polar coding may outperform other coding schemes such as turbo codes under small loads (e.g., 20 bits or 40 bits), convolutional codes (e.g., tail biting CC (TBCC) and / or trellis termination (TTCC)), and / or LDPC. Polarization coding may be applicable to control information, which may have a relatively small load. Control channels may include uplink control channels, such as PUCCH, PUSCH, etc. Uplink control channels may carry uplink control information (UCI) and / or WTRU feedback. Control channels may include downlink control channels, such as PDCCH, E-PDCCH, etc. Downlink control channels may carry downlink control information (DCI). Additional control information may be proposed for NR and may be included in a variable size and / or jointly and variably encoded.

[0113] The channel coding scheme may be switched (e.g., determined) based on the payload size of the control channel. For example, when the transmission payload size of the control channel is greater than the first predefined payload size, a first coding scheme (e.g., such as a polar code) may be used. When the transmission payload size of the control channel is less than or equal to the first predefined payload size, a second coding scheme (e.g., such as a Reed-Muller code) may be used. When the transmission payload size of the control channel is greater than the second predefined payload size, a third coding scheme (e.g., such as LDPC) may be used. The second predefined payload size may be greater than the first predetermined payload size. Priority and / or CRC may be used based on the payload size of the control channel. For example, when the transmission payload size of the control channel is greater than the predefined payload size, priority and / or CRC may be used for control information and / or control channels. When the transmission payload size of the control channel is less than or equal to the predefined payload size, priority and / or CRC may not be used for control information and / or control channels.

[0114] In an example, there may be J control information (eg, instances of control information), each of which may have S j The size of the control information bits is j = 1, 2, ..., J. An instance of control information may be associated with a control information type; there may be multiple control information types. The total number of control information bits may be denoted as K, where The control information may be transmitted using a polar encoder (e.g., with parameters N, P, K, J, S j , M and R) are jointly encoded. N can be the code block size, K can be the total control information size, P can be the number of puncturing bits, J can be the number of control information, S j may be the control information size of the control information j, M may be the size of the frozen bits, and R may be the code rate. j Can be used. Variable J and fixed S j Can be used. J and S j All can be changed. Different selections can result in different control information report types and report formats. Parameters N, P, K, J, S j ,M and R can be input parameters of the code structure components.

[0115] The size of the control information bits (K) and / or the code rate (R) may be predetermined.

[0116] Joint coding of multiple control information using polarization coding of a control channel may include dynamic joint coding, where one or more of the following may apply.

[0117] For given values ​​of K and R, an optimal joint coding using polar codes can be designed. The control information types and the number of control information bits can be grouped and / or combined in different ways. Different coding designs may need to accommodate different values ​​of K and R or different values ​​of K for a given value of R. For example, if a code rate of 1 / 3 is predetermined, then when K changes, N and P can change to maintain a fixed R. If N is fixed, then the puncturing value P can change to maintain a code rate of 1 / 3, for example, Where N′=NP. Bit rate It can vary according to the design, where N' represents the number of coded bits after puncturing. For the target code rate, the size of the control information can be dynamic, for example, by adjusting P and / or N to meet the target code rate. The control information can be dynamically combined.

[0118] Multiple polar codes of smaller size may be combined. Multiple polar codes of smaller size may be combined to generate a desired coded bit output length. The desired coded bit output length may be a predetermined coded bit output length. For example, a first codeword of a polar code having a first length (e.g., 8 bits) may be combined with a second codeword of a polar code having a second length (e.g., 4 bits) and a combined codeword having a third length (e.g., 12 bits) may be generated. Multiple polar codes of smaller size may be used to encode control information and / or WTRU feedback.

[0119] In the uplink, the WTRU may be configured to determine whether to perform puncturing of codewords and / or whether to combine multiple polar codes of smaller size, for example, based on one or more parameters. In the downlink, a base station (e.g., gNB, eNB, AP, etc.) may be configured to determine whether to perform puncturing of codewords and / or whether to combine multiple polar codes of smaller size, for example, based on one or more parameters. For example, if the number of bits to be punctured is small and / or the puncturing ratio is less than a predetermined threshold, the WTRU and / or the base station may determine to perform puncturing. If the number of bits to be punctured is large and / or the puncturing ratio is greater than or equal to a predetermined threshold, the WTRU and / or the base station may determine to combine multiple polar codes of smaller size, for example, to eliminate the need for a large number of puncturing. The one or more parameters may include the number of bits to be punctured, the information block length, the coding block length, the decoding algorithm, the polar code type, and the like.

[0120] The joint coding of multiple control information using polarization coding for the control channel may include the worst case joint coding. For a given value of N, P, and a code rate ≤ R max , the worst-case joint coding using polar codes can be designed. For example, the maximum code rate R max = 1 / 3 can be predetermined for minimum performance requirements. If N and P do not change, K may not be allowed to exceed a certain threshold. If N and P are fixed, the code rate may increase with K. K may be designed so that K ≤ K max =(NP)·R max When K = K max , maximum bit rate R max = 1 / 3 can be achieved, which can maintain the minimum coding performance requirement without performance degradation. <K max The bit rate can be less than the maximum bit rate R max , for example, the code rate < 1 / 3, which exceeds the minimum requirement and improves the bit error performance. The size of the control information can be controlled to be equal to or less than K for a predetermined maximum code rate max bits. The preset combination of control information can be designed to meet K max Requirements and / or corresponding R max Require.

[0121] Based on the parameters J and S j The code structure component of may be used to calculate K. The code structure component based on N, P, and K may be used to assign the size of the input and output of the polar decoder (e.g., the appropriate size) and the position of the output bit where the output bit should be received. The code structure component may generate one or more frozen bits and may direct the polar encoder to jointly encode control information.

[0122] Figure 5 An example joint encoding of multiple control information using polarization coding 500 is depicted. For example, variable joint encoding of multiple control information may use polarization coding of a control channel. At 502, various control information may be generated (e.g., including multiple instances of multiple types). First control information (e.g., such as control information 1 504), second control information (e.g., such as control information 2 506), and third control information (e.g., such as control information J 508) may be generated and may be sent to a polarization encoder 510. Control information 1 504 may include a first set of bits (e.g., S1 bits 520). Control information 2 506 may include a second set of bits (e.g., S2 bits 522). Control information J 508 may include a Jth set of bits (e.g., S J The polar encoder 510 may generate coded control information bits 526 based on the first bit set, the second bit set, and / or the Jth bit set. For example, the control information (e.g., S1 bit 520, S2 bit 522, S J Bits 524) may be polar coded using code structure 512. Rate matching may be performed for polar coded control information bits 526.

[0123] Control information types may be prioritized for joint coding. Control information may include one or more control fields. Control fields may be prioritized for joint coding. Prioritization of control information for joint coding of multiple control information with different control types, fields, etc. for control channels may be performed.

[0124] Control information, control messages and / or control fields may be prioritized over multiple control information or fields according to control information level and / or control field level. Some control information may be associated with a higher priority than other control information (e.g., for better network performance). For example, one control information type may have a different priority than other control information types, a bit set associated with a control information type may have a different priority than another bit set associated with the control information type, and so on. Some control fields within a control message may have a higher priority. Priority-based joint coding of control information and / or control fields using polarization coding may handle control information and / or control fields of different importance levels. Control information priority classification, control information groups, bit channel grouping, bit channel priority mapping and / or selective CRC attachment may be used and / or performed before polarization coding. Rate matching may be performed for polarization coded bits.

[0125] Figure 6 An example joint encoding 600 of control information using polar coding with control information priority classification and grouping and bit-channel group priority mapping is depicted. At 602, various control information may be generated. First control information (e.g., such as control information 1 604), second control information (e.g., such as control information 2 606), third control information (e.g., such as control information 3 608), and fourth control information (e.g., such as control information J 610) may be generated. The first, second, third, and / or fourth control information may be classified and / or grouped based on priority. Control information 1 604 may include a first set of bits (e.g., S1 bits 620). Control information 2 606 may include a second set of bits (e.g., S2 bits 622). Control information 3 608 may include a third set of bits (e.g., S3 bits 624). Control information J 610 may include a fourth set of bits (e.g., S JBit 626). The control information priority classification and grouping component 612 may classify the control information 1, 2, ..., J from high priority to low priority. The priority may be predetermined according to one or more preset rules. The priority may be configured by the eNB (or gNB) or the network, for example, via higher layer signaling such as RRC signaling or system information. At 612, the control information may be classified based on one or more preset priorities and / or configured priorities (e.g., based on the control information type). At 612, the classified control information may be grouped into Q groups. For example, the classified control information may be classified into a first group (e.g., such as group 1 630), a second group (e.g., such as group 2 632), and / or a third group (e.g., such as group Q 634). Each of the Q groups may include one or more instances of the control information based on priority. The control information may be grouped so that multiple copies of the same control information type with the same or similar priority are in one group. For example, multiple CQIs (e.g., wideband CQIs and / or multi-subband CQIs) may be grouped into the same control information group.

[0126] The control information may be grouped so that different control information types with the same or similar priority are grouped into one control information group. For example, different control information types (such as PMI(s) and / or CQI(s)) may be grouped into the same control information group.

[0127] The control information may be grouped so that control information bits with the same or similar priority are grouped into the same control information group. For example, the MSBs associated with the control information type may be grouped into a first group. The LSBs associated with the control information type may be grouped into a second group.

[0128] The bit channel grouping and priority mapping 640 can be used to divide the bit channels into bit channel groups and map the groups of control information into the bit channel groups. The bit channels of the polar code can be divided into Q groups, for example, based on the required number of groups and / or group (one or more) sizes. The bit channels can be divided based on bit channel capacity, quality, reliability, priority, etc. and can be grouped into multiple groups. For example, bit channels with the same or similar bit channel capacity and / or priority can be divided and / or grouped into the same bit channel group. The bit channel group priority mapping can include mapping the control information groups to the bit channel groups with corresponding priorities (for example, one by one). The bit channel groups can be arranged from high to low based on their priorities and can include a one-to-one mapping of control information groups to bit channel groups. The control information group with the highest priority (for example, control information group 1 630) can be mapped to the first bit channel group with the highest bit channel capacity (for example, bit channel group 1 642). The control information group with the second highest priority (e.g., control information group 2 632) may be mapped to the second bit channel group with the second highest bit channel capacity (e.g., bit channel group 2 644), etc. The last control information group (e.g., control information group Q 634) may be mapped to the last bit channel group (e.g., bit channel group Q 646).

[0129] The bit channel grouping may rearrange the bit channels in the group based on one or more of the following: bit channel capacity, quality, reliability, priority, etc. The bit channel group may form Q groups of control information corresponding to the Q groups. Priority mapping may map the control information groups to the bit channel groups. The bit channel groups may include different bit channels (e.g., localized or distributed manner of the bit channels). The grouping of the bit channels may be determined based on the bit channel capacity, priority, and / or the like. The grouping of the bit channels may be grouped based on the required number of groups and / or the size of the group (one or more). The grouping of the bit channels may be determined dynamically, for example, depending on the number of groups of control information, the number of bits of control information per group, etc. The polarization encoder 650 may generate the coded control information bits 652 based on the first, second, and / or third bit sets. The polarization encoder 650 may generate the coded control information bits 652 based on the first, second, and / or third bit channel groups. For example, the first, second, third, and / or fourth control information may be polarization encoded using the code structure 660.

[0130] Figure 7An exemplary prioritization 700 of control information channel coded using polar codes is depicted. The control information may include a plurality of control messages (e.g., control messages A, B, C, J'). At 702, the control messages may be multiplexed (e.g., prior to prioritization). There may be Q control messages. The control information multiplexing may include multiplexing the control messages. The multiplexing may multiplex and / or select control messages for inclusion in the joint coding. After multiplexing, one or more control messages may be presented at an output of the control message multiplexer. For example, as Figure 7 As shown, messages A, B, ..., J may be multiplexed and may be presented at the output of the control information multiplexer. At 704, the control messages may be classified and / or grouped based on priority. For example, the control information priority classification and grouping may include classifying the control messages based on their priority and the classified control messages may be grouped into appropriate groups. The control messages may be grouped into a plurality of control message groups 706A, 706B, 706C, 706D. The plurality of control message groups may include a first control message group 706A (e.g., control message group A), a second control message group 706B (e.g., control message group B), a third control message group 706C (e.g., control message group C), and / or a fourth control message group 706D (e.g., control message group Q). As Figure 7 As shown, control messages A, B, ..., J may be sorted based on priority from high to low. A first control message group 706A may be associated with the highest priority and a fourth control message group 706D may be associated with the lowest priority.

[0131] At 708, bit channel grouping and priority mapping may be performed on the control message groups. The bit channel group and priority mapping may include mapping the control message groups 706A, 706B, 706C, 706D to appropriate bit channel groups according to the ranked priorities. At 710, the control messages mapped to the bit channel groups may be sent to the input of a polar encoder for joint encoding of the control messages.

[0132] WTRU feedback may be priority based. WTRU feedback may include a plurality of control information, messages, and / or fields, which may include, but are not limited to: synchronization signal (SS) block index (SSBI), rank indicator (RI), precoding matrix indicator (PMI), channel quality indicator (CQI), CSI-RS resource indicator (CRI), precoder type indicator (PTI), HARQ ACK / NACK, beam ID, scheduling request (SR), other WTRU feedback information, etc. Different WTRU feedback types may have different priorities. For example, RI may be more important than PMI and / or CQI (e.g., because PMI and CQI are measured and calculated based on RI). ACK / NACK may be more important than RI, PMI and / or CQI, for example, because ACK / NACK may require lower bit error than other control information. Control messages may be multiplexed, prioritized, mapped and / or encoded based on respective predetermined priorities associated with WTRU feedback. For example, control messages may be classified based on respective priorities associated with control information types. One or more control messages may be grouped, for example, based on respective priorities. Control messages associated with control information types of the same or similar priority may be grouped into control information groups. The bits of the control information groups may be grouped into bit-level control information groups. The control information may be mapped to one or more bit channels of a polar encoder, for example, based on classification and / or grouping. The control messages, control information groups and / or bit-level control information groups may be mapped according to their priority.

[0133] WTRU feedback priority may be network and / or configuration dependent. For example, in LTE and LTE-A, in spatial multiplexing configurations that optimize maximum rate transmission, RI and PMI may play a larger or more important role than CQI. More reliable transmission of RI and PMI may result in a closer to optimal signal configuration. HARQ ACK / NACK may have a higher priority than CQI (e.g., because HARQ ACK / NACK may affect HARQ retransmissions, latency, and throughput, while CQI may only affect scheduling and / or some degradation of CQI may only result in limited degradation of link adaptation).

[0134] Figure 8An example prioritization 800 of control information using polar codes is depicted. For example, the control information may include CQI, RI, and / or PMI control messages. The CQI, RI, and / or PMI control messages may be jointly coded based on priority using polar codes. WTRU feedback such as CQI, RI, and PMI may arrive in the same time slot, subframe, TTI, short TTI, self-contained TTI, self-contained time slot, mini-slot, etc. in a random order to be transmitted. For example, control messages 802 associated with CQI, RI, and / or PMI may be determined. At 804, the control messages 802 may be multiplexed. At 806, the control messages 802 may be classified based on priority. After multiplexing, different control messages such as RI, RI / PMI, or RI / PMI / CQI may be outputs of the multiplexing. For example, the control messages 802 may be grouped into CQI group 808A, PMI group 808B, and RI group 808C. After classification, the ordering of the control messages from high to low according to priority may be in the order of (RI), (PMI), and (CQI), or if PMI and CQI are grouped into a single group, in the grouping order of (RI), (PMI, CQI). At 810, CQI group 808A, PMI group 808B, and RI group 808C may be mapped to one or more bit channel groups 812A, 812B, 812C. For example, the bits of RI group 808C may be mapped to RI bit channel group 812A. RI bit channel group 812 may be the highest priority bit channel group. The bits of PMI group 808B may be mapped to PMI bit channel group 812B. PMI bit channel group 812B may be the second highest priority bit channel group. The bits of CQI group 808A may be mapped to CQI bit channel group 812C. CQI bit channel group 812C may be the third highest priority bit channel group. For example, (RI) may be mapped to a higher bit channel group, and (PMI, CQI) may be mapped to a lower bit channel group. Using polarization coding priority may increase reliability. At 814, the bit channel groups 812A, 812B, 812C may be polarization coded.

[0135] Fig. 9 An example prioritization of control information using polar coding is depicted 900. A control message may be an example of control information, a control field, a bit field, etc. One or more error checking bits may be added to the control information (e.g., such as WTRU feedback), for example, as Fig. 9 The error checking bits may include a CRC, a short CRC with X bits, etc., such as a 4-bit CRC, an 8-bit CRC for X=4 and 8, respectively, and / or the like. X=0 may indicate that no CRC is attached. The CRC may be added to all control messages individually, jointly, or a combination of both. For example, Fig. 9As shown, a CRC may be added to each control information group. A control information group may be a combination of instances and / or a group of instances of control information, control messages, control fields, bit fields, etc. of the same or different control information types.

[0136] A control message 902 associated with CQI, RI, and / or PMI may be determined. At 904, the control message 902 may be multiplexed. Different control messages such as RI, RI / PMI, or RI / PMI / CQI may be outputs of the multiplexing. At 906, the control message 902 may be classified based on priority. For example, the control message 902 may be grouped into a CQI group 908A, a PMI group 908B, and an RI group 908C. After classification, the ordering of the control messages from high to low according to priority may be in the order of (RI), (PMI), and (CQI), or if PMI and CQI are grouped into a single group, in the order of (RI), (PMI, CQI). At 910, the CQI group 908A, the PMI group 908B, and the RI group 908C may be mapped to one or more bit channel groups 912A, 912B, 912C. For example, the bits of RI group 908C may be mapped to RI bit channel group 912A. RI bit channel group 912A may be the highest priority bit channel group. The bits of PMI group 908B may be mapped to PMI bit channel group 912B. PMI bit channel group 912B may be the second highest priority bit channel group. The bits of CQI group 908A may be mapped to CQI bit channel group 912C. CQI bit channel group 912C may be the third highest priority bit channel group. For example, (RI) may be mapped to a higher bit channel group, and (PMI, CQI) may be mapped to a lower bit channel group. Using polarization coding priority may increase reliability. CRC 920, 922, 924 may be added (e.g., selectively applied and / or attached) to one or more channel groups 908A, 908B, 908C and / or one or more bit channel groups 912A, 912B, 912C. CRC 920 may be added to CQI group 908A, CRC 922 may be added to PMI group 908B, and / or CRC 924 may be added to RI group 908C. For example, CRC 922 may be added to PMI group 908B and / or CRC 920CQI group 908A, while CRC may not be added to RI group 908C. CRC 920, 922, 924 may be added jointly to RI group 908C and PMI group 908B, and CRC may not be added to CQI group 908A. A single CRC may be added jointly to RI, PMI, and CQI. At 914, the bit channel groups 912A, 912B, 912C with CRC may be polar coded.

[0137] Fig.10 An exemplary prioritization 1000 of control information with repetition protection for high priority information using polar coding is depicted. Some variable rate coding of the high priority control information may be applied, for example, in addition to the error checking bits added to the WTRU feedback. For example, some repetition coding of the high priority control message (e.g., RI information) may be applied. The repetition coding of the high priority RI information may reduce the effective coding rate of the RI information. For example, the high priority information (e.g., RI information) may be repeated before the CRC protection of the control information. Fig.10 As shown, at 1004, the control messages 1002 may be multiplexed. At 1006, the control messages 1002 may be classified and / or grouped based on priority. For example, the control messages may be grouped into a first group 1008A (e.g., a CQI group), a second group 1008B (e.g., a PMI group), and a third group 1008C (e.g., an RI group). The third group 1008C may include an RI group 1010A and an RI replication group 1010B. The RI replication group 1010B may be a duplication of the RI group 1010A.

[0138] At 1012, the bits of the first group 1008A, the second group 1008B, and the third group 1008C may be mapped to one or more bit channel groups, for example, based on priority. For example, the bits of the first group 1008A may be mapped to the CQI bit channel group 1014D. The bits of the second group 1008B may be mapped to the PMI bit channel group 1014C. The bits of the third group 1008C may be mapped to the RI bit channel group 1014A and / or the RI replica bit channel group 1014B. CRC 1020, 1022, 1024 may be added (e.g., selectively applied) to one or more channel groups 1008A, 1008B, 1008C and / or one or more bit channel groups 1014A, 1014B, 1014C, 1014D. CRC 1020 may be added to the first group 1008A, CRC 1022 may be added to the second group 1008B, and / or CRC 1024 may be added to the third group 1008C. A single CRC may be added jointly to the RI unit, RI replica group, PMI group, and CQI group. At 1016, the bit channel groups 1014A, 1014B, 1014C, 1014D with CRC may be polar coded.

[0139] Variable rate coding and / or CRC protection of control information can be designed in conjunction with priority. For example, repetition of high priority information can include additional protection for control messages, and the priority of the resulting control messages can be reduced when mapped to bit channels due to the additional protection.

[0140] The priority-based WTRU feedback described herein may be applied to wideband feedback, such as wideband PMI, wideband CQI, etc.

[0141] The priority-based WTRU feedback described herein may be applied to subband feedback (e.g., feedback per subband), such as multi-subband PMI, multi-subband CQI. For example, CQI1, CQI2, ..., CQI K are used for subbands 1, 2, ..., K, respectively, PMI1, PMI2, ..., PMI_K are used for subbands 1, 2, ..., K, etc.

[0142] The priority-based WTRU feedback described herein may be applied to feedback for each codeword (CW), e.g., CQI1 for CW1, CQI2 for CW2, ..., CQI K for CW_K. Or ACK / NACK1 for CW1, ACK / NACK2 for CW2, ..., ACK / NACK_K for CW_K, etc.

[0143] The priority-based WTRU feedback described herein may be applied to WTRU feedback for different frequencies, spectrums or bands or for carrier aggregation (e.g., primary component carrier (CC), secondary CC), such as RI1, PMI1, CQI1 for CC1, RI2, PMI2, CQI2 for CC2, ..., RI_K, PMI_K, CC_K for CQI_K, etc. For example, a higher priority may be assigned to a primary CC, and / or a lower priority may be assigned to a secondary CC. A higher priority may be assigned to a serving cell and / or a lower priority may be assigned to a non-serving cell. Control information (e.g., DL / UL control information, WTRU feedback, etc.) associated with a primary CC, a secondary CC, a serving cell, and / or a non-serving cell may be assigned different priorities and may be encoded based on the different priorities using polar codes as described herein. Control information for different frequencies, bands, sub-bands, etc. may be assigned different priorities and may be encoded based on the different priorities using polar codes as described herein.

[0144] The priority-based WTRU feedback described herein may be applied to feedback for azimuth of arrival (AoA), azimuth of departure (AoD), zenith angle of arrival (ZoA), zenith angle of departure (ZoD), beam direction, etc.

[0145] The priority-based WTRU feedback described herein may be applied to WTRU feedback for massive MIMO.For massive antenna systems, additional WTRU feedback may be required.

[0146] The priority-based WTRU feedback described herein may be applied to WTRU feedback for coordinated multi-point (CoMP) transmission and / or network MIMO. Multiple gNBs and / or eNBs in CoMP and / or network MIMO may require additional WTRU feedback.

[0147] The priority-based WTRU feedback described herein may be applied to WTRU feedback for different spectrums. Higher frequency bands and / or spectrums of cmW and / or mmW may require additional WTRU feedback.

[0148] As described herein, priority-based mapping can be combined with RE mapping and / or OFDM symbol mapping so that ACK / NACK and / or RI can be mapped to REs or OFDM symbols close to or adjacent to reference signal (RS) locations for better channel estimation.

[0149] The control information may be prioritized by bit level to perform joint coding of the control channels.

[0150] Single control information bit level can be prioritized.Except for field priority or control information of control field level across multiple control fields, control bits can have different priorities in the same control message and / or field.Some control bits can have higher priority than other control bits.Control messages can be prioritized according to bit level (e.g., for the purpose of ensuring the best minimum level of communication).For example, by mapping the two most significant bits (MSB) to a higher quality bit channel, and the two least significant bits (LSB) can be mapped to a lower quality bit channel, a 4-bit channel quality indicator (CQI) measurement can prioritize the two most significant bits.In the case of bit errors in one or more lower priority bit channels, CQI can provide a rough measurement of channel quality.

[0151] Fig.11Depicting exemplary priority-based control message bit-level accuracy. Bit-channel priority mapping may be used to perform bit-channel mapping for a single individual CQI 1100. Priority mapping may prioritize bit-level control message accuracy for polar-coded CQI 1100. CQI 1100 may be, for example, a 4-bit CQI. CQI 1100 may have bits b0, b1, b2, and b3. The most significant bit (MSB) 1102 of the 4-bit CQI may be assumed to be b3 and b2. The least significant bit (LSB) 1104 of the 4-bit CQI may be assumed to be b1 and b0. The priority mapping function may map MSBs 1102b3 and b2 to the highest and second highest channel capacity bit channels of U8 and U7. LSBs 1104b1 and b0 may be mapped to the next highest and next second highest channel capacity bit channels of U6 and U4. Since U4 may have a higher bit channel capacity (eg, 0.6836) than the bit channel capacity of U5 (eg, 0.3164), LSB 1104b0 may be mapped to U4 (eg, instead of U5 for optimal performance).

[0152] Fig.12 Example beam identification (BeamID) accuracy based on priority is depicted. Bit channel mapping can be performed for a single beam ID 1200 using priority mapping. Priority mapping can prioritize bit level control message accuracy for beam ID 1200 applicable for polarization coding. Beam ID 1200 can be a 5-bit beam ID. MSBs 1202 can be assumed to be b4 and b3 (e.g., in that order). LSBs can be assumed to be b2, b1, and b0. The priority mapping function can map MSBs 1202b4 and b3 to the highest and second highest channel capacity bit channels, such as U8 and U7, while LSBs 1204b2, b1, and b0 can be mapped to the next three highest channel capacity bit channels, such as U6, U4, and U5, as shown. Fig.12 shown.

[0153] The beam ID can prioritize the most significant bits, for example, using bit-channel mapping with polar codes. For example, the most significant bits can be mapped to higher quality bit channels, while less significant bits can be mapped to lower quality bit channels. In the event of bit errors on one or more lower priority bit channels, the beam ID can provide a coarse measure of beam selection, direction, and / or identification.

[0154] A CRC may be attached (e.g., selectively applied) to one or more control messages. Selectively applying a CRC may include determining to attach a CRC to one or more bit-level control information groups (e.g., not all bit-level control information groups). Selectively applying a CRC may include determining to attach a CRC to at least two bit-level control information groups in common. Selectively applying a CRC may include determining to attach a CRC to each MSB control information group. Selectively applying a CRC may include determining to attach a first CRC to each MSB control information group, and attaching a second CRC to each LSB control information group. The accuracy of the CQI may be verified using a priority level CRC value calculated for a message sent over a bit channel. The format of the control message may be determined to properly recover the control information.

[0155] As described herein, when multiple small-size polar codes are combined, priority-based CQI accuracy may be used. Each small-size component polar code may have its own bit channel capacity, quality, and / or reliability level. The WTRU, repeater, and / or base station may perform a joint ranking of the bit channel capacity, quality, and / or reliability of multiple small-size polar codes that may be calculated. For example, the WTRU may perform the joint ranking in an uplink and / or in device-to-device (D2D) communication. The joint ranking may be performed before mapping the MSB / LSB of the CQI information to the appropriate bit channel of a polarization encoder composed of multiple small-size polar codes. For example, the MSB / LSB of the CQI information may be mapped to one or more bit channels of the polarization encoder based on the joint ranking.

[0156] The WTRU, repeater and / or base station may rank (e.g., directly rank) the bit channel capacity, quality and / or reliability of polar coders composed of multiple small polar codes. The WTRU may rank the bit channel capacity, quality and / or reliability in uplink and / or D2D communications. For example, the subsequent bit channel capacity of a polar code of length 8 may be given by [0.0039 0.1211, 0.1914, 0.6836, 0.3164, 0.8086, 0.8789, 0.9961], while the subsequent bit channel capacity of a polar code of length 4 may be given by [0.0625, 0.4375, 0.5625, 0.9375]. The joint (e.g., combined) ordering of two small polar codes may be represented as U_8^8, U_4^4, U_7^8, U_6^8, U_4^8, U_3^4, U_2^4, U_5^8, U_3^8, U_4^8, U_1^4, U_1^8, where U_i^8 represents the i-th bit channel of the polar code of length 8, and U_i^4 represents the i-th bit channel of the polar code of length 4. The most significant bit of the CQI or beam ID may be placed in U_8^8, the second most significant bit of the CQI or beam ID may be placed in U_4^4, and so on. The least significant bit of the CQI or beam ID may be placed in U_1^8. For other control information and / or WTRU feedback, the most significant bit of the control information and / or WTRU feedback may be placed in U_8^8, the second most significant bit of the control information and / or WTRU feedback may be placed in U_4^4, and so on. The least significant bits of control information and / or WTRU feedback may be placed in U_1^8.

[0157] The WTRU and / or base station may match the bit channel capacity, quality, and / or reliability among the multiple component polar codes used to construct the polar encoder (e.g., to achieve better performance). For example, when combining a polar code of length 8 and a polar code of length 4, the bit channel capacity of the polar code of length 4 may be multiplied (e.g., offset) by a factor of X (e.g., before sorting).

[0158] The WTRU and / or base station may apply one or more exclusive OR (XOR) operations to the inputs of the component polar codes. When one or more exclusive OR operations are applied to the inputs of the component polar codes, the resulting codeword may have a larger minimum Hamming distance. The ordering of the resulting bit channels may change and may be adjusted accordingly.

[0159] Multiple polar codes of smaller size may be combined and applied to priority-based channel coding of (eg, all) control information. As described herein, joint ordering of multiple small component polar codes may be used for bit channel grouping and / or priority mapping.

[0160] Fig.13 Depicting exemplary prioritized CQI control message accuracy using polar coding. For multiple reports of the same control information type (e.g., CQI), there may be multiple CQI reports corresponding to multiple subband CQIs. The CQI bits may be grouped into MSB and LSB groups. For example, at 1304, multiple CQI control messages 1302 may be classified based on priority. The CQI control messages 1302 may be classified into CQI LSB groups 1306A and CQI MSB groups 1306B. Priority classification may be performed to assign a higher priority to the MSB bit group and a lower priority to the LSB bit group. After priority classification, at 1308, a CRC 1310, a short CRC, etc. may be attached (e.g., selectively applied) for error checking of the CQI bits. For example, the CRC 1310 may be attached to the CQI LSB group 1306A and the CQI MSB group 1306B together. The CRC may not be attached (e.g., to minimize overhead). Protection of high priority information, such as repeating MSB data, may be applied. Priority mapping may prioritize LSB bit groups and MSB bit groups prepared for the polar encoder. At 1312, priority mapping may map CQI MSB group 1306B to a higher priority bit channel group of the polar encoder, and may map CQI LSB group 1306A to a lower priority bit channel group of the polar encoder. When priority mapping is complete, at 1314, the polar encoder may jointly encode the CQI bits of the MSB and LSB bit groups and the encoded CQI bits of the MSB and LSB. For multiple CQIs (e.g., CQI1, CQI2, ..., CQI J ) may include more protection for the MSB bit group and less protection for the LSB bit group for the same control information type.

[0161] Fig.14Depicting exemplary prioritized control message accuracy using polar coding. Multiple reports of the same control information type may be extended to different control message types, such as RI, PMI, PTI, CRI, beam ID, ACK / NACK, etc. The control message may be divided into two bit groups, such as LSB and MSB bit groups. For example, at 1404, the control message 1402 may be classified into a control LSB group 1406A and a control MSB group 1406B. After the priority classification, a CRC, a short CRC, etc. may be attached for error checking of the control message bits. For example, at 1408, a first CRC 1410 may be attached to the control LSB group 1406A, and a second CRC 1412 may be attached to the control MSB group 1406B. The first CRC 1410 and the second CRC 1412 may be the same CRC. Other protections for high priority information may be applied, such as repeating MSB data. Priority mapping may prioritize the LSB bit groups and MSB bit groups prepared for the polar encoder. At 1414, priority mapping may map control MSB group 1406B to a higher priority bit channel group of the polar encoder and may map control LSB group to a lower priority bit channel group of the polar encoder. When priority mapping is complete, at 1416, the polar encoder may jointly encode control message bits for control MSB group 1406B and control LSB group 1406A. The encoded control message bits may include more protection for the MSB bit group and less protection for the LSB bit group for different control information.

[0162] One or more error check bits may be appended to the control message. The error check bits may be appended to the MSB and LSB bit groups together or individually. The error check bits may be a CRC, a short CRC with X bits, such as a 4-bit or 8-bit CRC with X=4 or 8, etc. X=0 may indicate that no CRC is appended. Fig.14 Depicting an exemplary prioritized control message accuracy using polar coding.A CRC or short CRC (eg, 4-bit CRC, 8-bit CRC, etc.) may be appended to the control MSB and LSB bit groups, eg, collectively, individually, or a combination of both.

[0163] Fig.15Depicting example prioritized control message accuracy with separate CRC using polar coding. At 1504, control message 1502 may be classified into control LSB group 1506A and control MSB group 1506B. Control message 1502 may be classified based on respective priorities associated with the control information type of control message 1502. CRC or short CRC may be appended to the control MSB and LSB bit groups, respectively. For example, at 1508, first CRC 1510 may be appended to the control LSB and second CRC 1512 may be appended to the control MSB group 1506B. In this case, the gNB or receiver may perform error checking on the MSB and LSB, respectively.

[0164] Fig.16 An exemplary prioritized control message accuracy with CRC for MSB protection is depicted. At 1604, control message 1602 may be classified into control LSB group 1606A and control MSB group 1606B. Control message 1602 may be classified based on a respective priority associated with a control information type of control message 1602. Only a CRC or a short CRC may be appended to control MSB group 1606B. For example, at 1608, CRC 1610 or a short CRC may be appended to control MSB group 1606A, and CRC 1610 may not be appended to control LSB group 1606B. The gNB or receiver may perform error checking of the MSB with minimal CRC overhead.

[0165] The control messages, control fields and / or control bits may jointly prioritize the jointly encoded control information.Multi-level priority grouping may include one or more of the following.

[0166] Control information (e.g., control messages, control fields, control message fields, and / or control bits) may be classified (e.g., grouped) based on a priority of the control information, such as at a first level (e.g., at stage 1). For example, the control information may be classified based on a corresponding priority associated with a control information type of the control information. Control information and / or messages having the same or similar priority may be grouped into the same group, such as a control information group.

[0167] For each control information group, one or more control bits within the control information group may be grouped into bit-level groups based on one or more priorities at the bit level, such as at a second level (e.g., at stage 2). For example, the control bits of a control information group may be grouped into MSB and LSB bit-level control information groups associated with the control information group.

[0168] Some control information (e.g., control message, control field, control message field, and / or control bit) may be important, and both the MSB and LSB may require more protection. The control information may include CSI-RS resource indicator (CRI), RI, PMI, CQI, beam ID, HARQ ACK / NACK, SS block index, precoder type indicator (PTI), scheduling request (SR), etc.

[0169] Fig.17 Depicting exemplary use of polar coding to prioritize control message fields and bit-level priority. Control information (e.g., control message 1702) may include RI, PMI, CQI, beam ID, HARQ ACK / NACK, etc. For example, at 1704, control information priority classification and grouping may be performed. Fig.17 As shown, at 1704, the control information may be classified and grouped into groups. For example, the control information may be classified into a first control information group 1706A, a second control information group 1706B, a third control information group 1706C, and / or a fourth control information group 1706D. The first control information group 1706A may be associated with a first control information type (e.g., CQI). The second control information group 1706B may be associated with a second control information type (e.g., PMI) and a third control information type (e.g., beam ID). The third control information group 1706C may be associated with a fourth control information type (e.g., RI). The fourth control information group 1706D may be associated with a fifth control information type (e.g., HARQ ACK / NACK). The first control information group 1706A may be associated with a lowest priority. The second control information group 1706B may be associated with a second lowest priority. The fourth control information group 1706D may be associated with a highest priority. The third control information group 1706C may be associated with a second highest priority. One or more control information types (e.g., beam ID and PMI) may be assumed to have the same or similar priority and may be grouped together into the same group. HARQ ACK / NACK and RI may be assumed to have a higher priority than beam ID and PMI, which in turn may have a higher priority than CQI. Grouping may be based on priority, one or more performance requirements, one or more delay requirements, one or more BER requirements, one or more BLER requirements, SNR, etc.

[0170] At 1708, control bit level priority grouping may be performed. HARQ ACK / NACK and RI may have a higher priority, and further grouping may not be performed on HARQ ACK / NACK and RI. For example, HARQ ACK / NACK and / or RI may not be decomposed into additional fields and / or groups. Beam ID and PMI may be grouped together in the same group. The control bits of the first control information group 1706A and / or the second control information group 1706B may be grouped and divided into MSB and LSB bit groups. For example, PMI MSB and beam ID MSB may be grouped into a first bit level control information group 1710A and PMI LSB and beam ID LSB may be grouped into a second bit level control information group 1710B, as shown in FIG. Fig.17 As shown, the CQI bits may be grouped and / or divided into MSB and LSB bit groups, for example, CQI MSB bit level control information group 1710C and CQI LSB bit level control information group 1710D.

[0171] A CRC may be appended (e.g., selectively appended) to one or more groups. Fig.17 As shown, at 1712, CRC 1714 may be commonly attached to the first and second bit-level control information groups 1710A, 1710B (e.g., selectively attached to the first and second bit-level control information groups 1710A, 1710B but not other control information groups). Other protection schemes, such as repeating high priority information, may be applied to one or more control information groups.

[0172] At 1716, the control information may be mapped to the bit channels of the polar encoder based on the respective priorities of the control groups and / or the respective priorities of the corresponding bit channel groups. At 1716, the control information may be mapped based on classification, grouping, and / or selective CRC attachment. At 1718, the control information may be jointly encoded.

[0173] Fig.18Depicted are exemplary priorities for control message fields and bit-level prioritization using polar coding. At 1804, control information 1802 (e.g., RI, PMI, CQI, beam ID, and HARQ ACK / NACK control messages) may be classified based on priority. It may be assumed that the control information 1802 has different priorities corresponding to the control information type. For example, each control information type may have a corresponding control information group. At 1804, priority classification of the control information 1802 may be performed and grouping may be performed. For example, the control information 1802 may be classified based on the control information type. At 1806, control bit priority grouping may be performed. The beam ID bits may be grouped and divided into beam ID MSB control information group 1808A and beam ID LSB control information group 1808B. The CQI bits may be grouped and divided into CQI MSB control information group 1808C and CQI LSB control information group 1808D. At 1810, a CRC may be optionally attached. For example, a first CRC 1812 may be appended to the beam ID MSB control information group 1808A, and a second CRC 1814 may be appended to the PMI control information group 1808E. At 1816, the control information may be mapped to bit channels and may be jointly encoded using polarization coding.

[0174] Priority-based jointly coded control information can be multiplexed with uncoded control information. In LTE systems with PUCCH format 2a / 2b, channel quality information (CQI) and HARQ-ACK information can be transmitted jointly. When a standard cyclic prefix (CP) is used for uplink transmission, the channel quality information can be encoded (e.g., Reed-Muller encoding). The coded CQI can be multiplexed with HARQ-ACK information (e.g., original HARQ-ACK information). Polarization-coded multiple control information can be multiplexed.

[0175] Fig.19 Depicted are exemplary prioritized control message fields. For example, Figure 7As shown, there may be one or more (e.g., J') first control messages 1902. At 1908, the first control messages 1902 may be multiplexed. At 1910, the multiplexed control messages 1902A may be classified and / or grouped. The multiplexed control messages 1902A may be classified into control message groups 1912 (e.g., control message groups A, B, C, ... Q). The control messages 1902 may be classified into the control message groups 1912 based on priority. At 1914, the control message groups 1912 may be mapped based on priority. At 1916, the control message groups 1912 may be jointly encoded using polar codes. For example, the control message groups 1912 may be jointly encoded to determine polar-coded control messages 1918. At 1906, one or more (eg, J") additional control messages J', ..., J'+J" (eg, the second control message 1904) may be multiplexed with the polar coded control message 1918 (eg, polar jointly coded J' control messages).

[0176] Priority-based jointly coded WTRU feedback may be transmitted via PUCCH, PUSCH, enhanced PUCCH (e-PUCCH), enhanced PUSCH (e-PUSCH), etc. Control information reports (such as CSI reports, which may include but are not limited to RI, PMI, PTI, CQI, AoA, AoD, beam ID, CRI, etc.) and HARQ ACK / NACK, SR for WTRU feedback may be transmitted jointly or separately. Different combinations of control information for WTRU feedback may result in different reports with different priorities, report types and / or report formats and mapping of control messages and bits. Multiple different copies of each control information type may be transmitted due to wideband and subband feedback, such as wideband PMI, subband PMI, wideband CQI, subband CQI, etc. Multiple different copies of each control information type may be transmitted due to feedback per subband (e.g., multiple subband PMIs, multiple subband CQIs, etc.). Multiple different copies of each control information type may be transmitted due to feedback per codeword (CW). Due to feedback per carrier aggregation or similar band, frequency and / or CC, multiple different copies of each control information type may be transmitted. Due to feedback per gNB (or eNB) or per site (e.g., for coordinated multi-point (CoMP) transmissions and network MIMO), multiple different copies of each control information type may be transmitted.

[0177] Periodic or aperiodic PUCCH and / or aperiodic or periodic PUSCH may be used to transmit priority-based jointly coded control information for WTRU feedback. For example, for small payload control information, PUCCH, enhanced PUCCH (e-PUCCH) may be used, while for large payload control information, PUSCH or e-PUSCH, etc. may be used. For large payload control information, extended PUCCH, large-size PUCCH and / or e-PUCCH, etc. may be used. Multiplexing of WTRU feedback and control messages on PUSCH or similar UL-SCH may also be used. New or modified PUSCH or new PUCCH formats, reports or report types may be required to transmit different combinations of control information with different priorities and / or payload sizes (e.g., to accommodate different joint coding of control information fed back by the WTRU).

[0178] Polar coding may be performed on the control information. Polar coding may include a decision between concatenated PC polar codes and non-concatenated PC polar codes.

[0179] As described herein, the "to polar encoder" block can be used to encode multiple control messages, for example, based on their priorities. The polar codes can include concatenated PC polar codes and / or non-concatenated PC polar codes. The non-concatenated PC polar codes may result in desired BLER performance, for example, if there is no deep puncturing. If the non-concatenated PC polar codes must puncture a large number of bits, the BLER performance of the non-concatenated PC polar codes may degrade. In this case, the concatenated PC polar codes can achieve better BLER performance, which can avoid deep puncturing. When compared to non-concatenated PC polar codes, the concatenated PC polar codes may result in reduced decoding delay, for example, because each segment can be decoded in parallel.

[0180] Fig. 20 An exemplary decision 2000 between concatenated PC polar codes and non-concatenated PC polar codes is depicted. A total of K information bits (e.g., from one or more control messages) may be encoded. The K information bits may be ordered based on priority. The overall coding rate R may be known. The size of the coding block may be The coding block size may be determined based on the allocated resource element size and / or the modulation order. At 2002, the mother codeword length may be determined based on the information block size 2004 (e.g., coding block size) and / or the coding rate 2006 (e.g., overall coding rate R).

[0181] If N is greater than The mother code length can be determined as N, and the number of puncturing bits can be

[0182] A transmitter (e.g., a transmitting entity) may estimate a decoding delay. As described herein, the transmitter may be a WTRU. At 2008, the transmitter may determine, for example, based on a decoding capability 2010 of a receiver, whether a delay requirement of the component control information may be achieved using a single PC polar code. The transmitter may estimate the decoding delay based on a code rate R, a mother codeword length N, and / or a decoding capability of one or more receivers. If the estimated decoding delay is greater than the delay requirement of any separate control information, concatenated PC polar codes 2014 may be used. Concatenated PC polar codes 2014 may be required to reduce decoding delay. For example, the transmitter may determine to use concatenated PC polar codes 2014 based on a delay requirement associated with the control information. The transmitter may use concatenated polar codes 2014 or non-concatenated PC polar codes 2016 to send the control information.

[0183] At 2012, the transmitter may determine whether to use concatenated PC polar code 2014 or non-concatenated PC polar code 2016, for example, based on their BLER performance (e.g., if the transmitter has determined that the delay requirements of the component control information can be achieved using a single PC polar code). For example, the transmitter may determine which polar code to use based on the BLER performance of concatenated PC polar code 2014 and non-concatenated PC polar code 2016. When the transmitter determines that concatenated PC polar code 2014 has better performance requirements than non-concatenated PC polar code 2016, the transmitter may determine to use concatenated PC polar code 2014.

[0184] BLER performance justification may be based on multiple puncturing bit amounts P. For example, if P is greater than a predetermined threshold, concatenated PC polar codes 2014 may be used. Deep puncturing may be avoided by using concatenated PC polar codes 2014. If P is less than or equal to a predetermined threshold, non-concatenated PC polar codes 2016 may be used.

[0185] The BLER performance adjustment can be based on the ratio of the punctured bit quantity P to the mother code length N. If the ratio If the ratio is greater than a predetermined threshold, the concatenated PC polar code can be used. If the value is less than or equal to a predetermined threshold, non-concatenated PC polar codes may be used.

[0186] The BLER performance adjustment can be based on the ratio of the number of punctured bits P to the number of information bits K. If the ratio If the ratio is greater than a predetermined threshold, the concatenated PC polar code can be used. If the value is less than or equal to a predetermined threshold, non-concatenated PC polar codes may be used.

[0187] The BLER performance adjustment can be based on any function of (K, N, P).

[0188] The transmitter and the receiver may apply the same adjustment scheme to determine whether to use concatenated PC polar codes or non-concatenated PC polar codes. The transmitter and the receiver may communicate with each other to determine which polar code should be used. The communication may be based on the following exemplary adjustment scheme table. For example, a scheme index may be transmitted between the transmitter and the receiver.

[0189] Table 1: Example adjustment scheme

[0190] plan parameter Threshold 1 P <![CDATA[γ1]]> 2 P / N <![CDATA[γ2]]> 3 P / K <![CDATA[γ3]]> 4 f(P, N, K) <![CDATA[γ4]]>

[0191] Both the transmitter and the receiver can make the same decision on concatenated PC polar codes or non-concatenated PC polar codes, for example Fig. 20 shown.

[0192] For concatenated PC polar codes, the transmitter may determine the number of parallel segments to use. The transmitter may send an indication of the number of parallel segments to use to the receiver. The number of parallel segments to use may be predetermined and may be known to the transmitter and the receiver.

[0193] One or more PC freeze bits may be allocated for control information.

[0194] For PC polar codes (e.g., with or without concatenation), PC freeze bits can be used to detect one or more errors of certain information bits, for example, based on a copy of the information bits and / or an XOR of the information bits. A transmitter (e.g., an encoder at a transmitter) can insert the PC freeze bits into one or more control messages. A receiver (e.g., a decoder at a receiver) can use the PC freeze bits to detect one or more errors. When multiple control messages are to be jointly encoded, an allocation of PC freeze bits set for each component control message can be determined.

[0195] There may be J control messages S1, ..., S that will be jointly encoded by the PC polar code. J , and there may be L PC frozen bits. The total number of information bits from J control messages may be equal to The PC freeze bits may be assigned to control messages in one or more of the following methods.

[0196] The PC freeze bits for control messages may be allocated equally to each control message. For example, each control message may be allocated PC freezes bit.

[0197] PC freezing bits can be allocated to control messages in proportion to the length of each control message. i Can be assigned PC freeze bits.

[0198] The PC freeze bits can be assigned to control messages based on their priority. J , where q1≥q2≥…≥q J , the PC frozen bits allocated to J control messages can be L1≥L2≥…≥L J .

[0199] The PC freeze bits may be assigned to control messages based on the control message priority and the control message length.

[0200] Although features and elements of the invention are described in particular combinations in preferred embodiments, each feature or element may be used alone without the other features and elements of the preferred embodiment, or in different combinations with or without the other features and elements of the invention.

[0201] Although the solution described herein considers New Radio (NR), 5G or LTE, LTE-A specific protocols, it should be understood that the solution described herein is not limited to this scenario and is also applicable to other wireless systems.

[0202] Although the features and elements are described above in particular combinations, it will be understood by those skilled in the art that each feature or element may be used alone or in any combination with other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware embedded in a computer-readable medium and executed by a computer or processor. Examples of computer-readable media include electronic signals (transmitted via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, buffer memory, semiconductor storage devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM discs and digital versatile discs (DVDs). A processor associated with the software may be used to implement a radio frequency transceiver used in a WTRU, a terminal, a base station, an RNC, or any host computer.

Claims

1. A method performed by a wireless transmit receive unit WTRU, the method comprising: generating first control information and second control information; grouping bits from the first control information and the second control information into at least two bit groups, wherein a first bit group includes bits of a first priority from the first control information and the second control information, and a second bit group includes bits of a second priority from the first control information and the second control information; applying cyclic redundancy check (CRC) bits to one or more of the first group of bits or the second group of bits; and mapping the first bit group, the second bit group, and the CRC bits to a bit channel of a polar encoder, wherein each of the bit channels is associated with a respective priority, and wherein the first group of bits, the second group of bits, and the CRC bits are mapped to the bit channels based on the respective priority of the bit channels.

2. The method according to claim 1, wherein: The first control information or the second control information includes one or more of the following: synchronization signal SS block index SSBI, rank indicator RI, precoding matrix indicator PMI, channel quality indicator CQI, CSI-RS resource indicator CRI, precoder type indicator PTI, beam ID, ACK / NACK or scheduling request SR.

3. The method according to claim 1, wherein: The first bit group includes a set of least significant bits (LSBs) from one or more of the first control information or the second control information, and the second bit group includes a set of most significant bits (MSBs) from one or more of the first control information or the second control information.

4. A wireless transmit / receive unit WTRU, the WTRU comprising a processor, the processor being configured to: generating first control information and second control information; grouping bits from the first control information and the second control information into at least two bit groups, wherein a first bit group includes bits of a first priority from the first control information and the second control information, and a second bit group includes bits of a second priority from the first control information and the second control information; applying cyclic redundancy check (CRC) bits to one or more of the first group of bits or the second group of bits; and mapping the first bit group, the second bit group, and the CRC bits to a bit channel of a polar encoder, in, Each of the bit channels is associated with a respective priority, and wherein the first group of bits, the second group of bits, and the CRC bits are mapped to the bit channels based on the respective priority of the bit channels.

5. The WTRU according to claim 4, wherein the first control information or the second control information includes one or more of the following: synchronization signal SS block index SSBI, rank indicator RI, precoding matrix indicator PMI, channel quality indicator CQI, CSI-RS resource indicator CRI, precoder type indicator PTI, beam ID, ACK / NACK or scheduling request SR.

6. The WTRU of claim 4, wherein the first bit group comprises a set of least significant bits (LSBs) from one or more of the first control information or the second control information, and the second bit group comprises a set of most significant bits (MSBs) from one or more of the first control information or the second control information.

Images