WO2018009572A1 - Communications de données à faible latence utilisant un codage avancé - Google Patents

Communications de données à faible latence utilisant un codage avancé Download PDF

Info

Publication number
WO2018009572A1
WO2018009572A1 PCT/US2017/040757 US2017040757W WO2018009572A1 WO 2018009572 A1 WO2018009572 A1 WO 2018009572A1 US 2017040757 W US2017040757 W US 2017040757W WO 2018009572 A1 WO2018009572 A1 WO 2018009572A1
Authority
WO
WIPO (PCT)
Prior art keywords
tier
bit channel
mapping rule
traffic
bit
Prior art date
Application number
PCT/US2017/040757
Other languages
English (en)
Inventor
Kyle Jung-Lin Pan
Kevin T. WANUGA
Fengjun Xi
William E. LAWTON
Alpaslan Demir
Original Assignee
Idac Holdings, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Idac Holdings, Inc. filed Critical Idac Holdings, Inc.
Publication of WO2018009572A1 publication Critical patent/WO2018009572A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/007—Unequal error protection
    • H—ELECTRICITY
    • H03—ELECTRONIC CIRCUITRY
    • H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M13/00—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
    • H03M13/03—Error detection or forward error correction by redundancy in data representation, i.e. code words containing more digits than the source words
    • H03M13/05—Error detection or forward error correction by redundancy in data representation, i.e. code words containing more digits than the source words using block codes, i.e. a predetermined number of check bits joined to a predetermined number of information bits
    • H03M13/09—Error detection only, e.g. using cyclic redundancy check [CRC] codes or single parity bit
    • H—ELECTRICITY
    • H03—ELECTRONIC CIRCUITRY
    • H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M13/00—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
    • H03M13/03—Error detection or forward error correction by redundancy in data representation, i.e. code words containing more digits than the source words
    • H03M13/05—Error detection or forward error correction by redundancy in data representation, i.e. code words containing more digits than the source words using block codes, i.e. a predetermined number of check bits joined to a predetermined number of information bits
    • H03M13/13—Linear codes
    • H—ELECTRICITY
    • H03—ELECTRONIC CIRCUITRY
    • H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M13/00—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
    • H03M13/29—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes combining two or more codes or code structures, e.g. product codes, generalised product codes, concatenated codes, inner and outer codes
    • H03M13/2906—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes combining two or more codes or code structures, e.g. product codes, generalised product codes, concatenated codes, inner and outer codes using block codes
    • H—ELECTRICITY
    • H03—ELECTRONIC CIRCUITRY
    • H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M13/00—Coding, decoding or code conversion, for error detection or error correction; Coding theory basic assumptions; Coding bounds; Error probability evaluation methods; Channel models; Simulation or testing of codes
    • H03M13/63—Joint error correction and other techniques
    • H03M13/635—Error control coding in combination with rate matching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0041—Arrangements at the transmitter end
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0057—Block codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0061—Error detection codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0056—Systems characterized by the type of code used
    • H04L1/0071—Use of interleaving

Definitions

  • a previous (legacy) generation of mobile communication may be, for example, fourth generation (4G) long term evolution (LTE).
  • 4G fourth generation
  • LTE long term evolution
  • An encoder may receive different types of data/traffic.
  • the encoder may sort the different types of traffic such as data and control information into multiple priority tiers of varying priorities.
  • the encoder may attach a tier-level cyclic redundancy check(s) (CRCs) to the priority tiers.
  • CRCs tier-level cyclic redundancy check
  • the encoder may map traffic of varying priority tiers to multiple bit channels associated with varying levels of different reliability and/or robustness of channel coding.
  • One or more CBs (CBs) may be formed from one or more of the bit channels.
  • the encoder may attach a cyclic CRC(s) to one or more of the CBs.
  • the encoder may be implemented in a radio access network (RAN) node (e.g.
  • RAN radio access network
  • the encoder may be implemented in a wireless transmit/receive unit (WTRU), for example if a transmission is to be performed in the uplink.
  • WTRU wireless transmit/receive unit
  • the encoder may receive a bit channel mapping rule indicating how the mapping from priority tiers to bit channels should be performed.
  • the bit channel mapping rule may indicate that a higher priority tier should be mapped to a bit channel associated with a relatively higher level of channel coding reliability and/or that that a lower priority tier should be mapped to a bit channel associated with a relatively lower level of channel coding reliability.
  • the encoder may dynamically receive the bit channel mapping rule such that the mapping of the priority tiers to the bit channels differs from one CB to another CB.
  • the bit channel mapping rule may be determined by the encoder, for example, based on a pre- configuration, a previously-received indicator, and/or based on other scheduling related decisions. Additional control information may be received via a parallel polar encoder and/or encoded before being multiplexed with the CBs.
  • a decoder may receive the multiplexed traffic.
  • the decoder may decode one or more of the encoded CBs to generate a decoded CB(s) and/or perform a CRC check based on the attached CB CRC.
  • the decoder may remove the CB CRC and store the decoded CB.
  • the decoded CB may correspond to a plurality of bit channels.
  • the decoder may receive or determine a bit channel de-mapping rule for the CB.
  • the bit-channel de-mapping rule may indicate how to derive and/or recreate the priority tiers from the bit channels when performing channel decoding (e.g., decoding of the received polar coded data).
  • the decoder may use the determined bit channel de-mapping rule to de-map the priority tiers from one or more of the bit channels.
  • the decoder may determine a priority de-mapping rule for de-mapping data of different tiers from the priority tiers to the different types of data.
  • the decoder may use the determined priority de-mapping rule to generate the different types of traffic.
  • the decoder may be implemented in a RAN node (e.g., gNB), for example if the transmission is to be performed in the uplink.
  • the decoder may be implemented in a WTRU, for example if the transmission is to be performed in the downlink.
  • FIG. 1A is a system diagram of an example communications system in which one or more disclosed embodiments may be implemented.
  • FIG. IB is a system diagram of an example WTRU that may be used within the communications system illustrated in FIG. 1 A.
  • FIG. 1C is a system diagram of an example radio access network and an example core network that may be used within the communications system illustrated in FIG. 1A.
  • FIG. ID is a system diagram of another example radio access network and another example core network that may be used within the communications system illustrated in FIG. 1 A.
  • FIG. IE is a system diagram of another example radio access network and another example core network that may be used within the communications system illustrated in FIG. 1 A.
  • FIG. 2 is an example of an mmW Network.
  • FIG. 3 is an example of a coding processing structure such as polar coding.
  • FIG. 4 is an example of data and/or control prioritization processing multiplexed with additional control signaling.
  • FIG. 5 is an example of data and/or control prioritization processing.
  • FIG. 6 is an example of a transmitter approach for traffic prioritization based on bit channels.
  • FIG. 7 is an example of a receiver approach for traffic prioritization based on bit channels.
  • FIG. 8 is an example of a transmitter approach for prioritization of URLLC data multiplexed with control information based on bit channels.
  • FIG. 9 is an example of a receiver approach for prioritization of URLLC data multiplexed with control information based on bit channels.
  • FIG. 10 is an example of using polar coding bit channels for low requirement data multiplexed with high priority LI (e.g. , Physical Layer - PHY) /L2 control information.
  • high priority LI e.g. , Physical Layer - PHY
  • FIG. 1 1 is an example of using polar coding bit channels for low requirement data multiplexed with high priority higher layer control information.
  • FIG. 1A is a diagram of an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications 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), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single- carrier FDMA
  • the communications system 100 may include wireless transmit/receive units (WTRUs), e.g. , WTRUs, 102a, 102b, 102c and/or 102d (which generally or collectively may be referred to as WTRU 102), a radio access network (RAN) 103/104/105, a core network 106/107/109, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs wireless transmit/receive units
  • RAN radio access network
  • PSTN public switched telephone network
  • Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d 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 pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, consumer electronics, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • the communications system 100 may also include a base station 114a and a base station 114b.
  • Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the core network 106/107/109, the Internet 110, and/or the networks 112.
  • the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • the base station 114a may be part of the RAN 103/104/105, which may also include other base stations and/or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc.
  • BSC base station controller
  • RNC radio network controller
  • the base station 114a and/or the base station 114b may be configured to transmit and/or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown).
  • the cell may further be divided into cell sectors.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, e.g., one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • the base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 115/116/117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, etc.).
  • RF radio frequency
  • IR infrared
  • UV ultraviolet
  • the air interface 115/116/117 may be established using any suitable radio access technology (RAT).
  • RAT radio access technology
  • the communications 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, and the like.
  • the base station 114a in the RAN 103/104/105 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115/116/117 using wideband CDMA (WCDMA).
  • UMTS Universal Mobile Telecommunications System
  • UTRA Universal Mobile Telecommunications System
  • WCDMA wideband CDMA
  • WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
  • HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).
  • HSPA High-Speed Packet Access
  • HSDPA High-Speed Downlink Packet Access
  • HSUPA High-Speed Uplink Packet Access
  • 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 115/116/117 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE- A).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.16 (e.g., 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), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.16 e.g., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 IX, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for Mobile communications
  • GSM Global System for Mobile communications
  • EDGE Enhanced Data rates for GSM Evolution
  • GERAN GSM EDGERAN
  • the base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, and the like.
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN).
  • the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN).
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular- based RAT (e.g. , WCDMA, CDMA2000, GSM, LTE, LTE- A, etc.) to establish a picocell or femtocell.
  • a cellular- based RAT e.g. , WCDMA, CDMA2000, GSM, LTE, LTE- A, etc.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the core network 106/107/109.
  • the RAN 103/104/105 may be in communication with the core network 106/107/109, 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 of the WTRUs 102a, 102b, 102c, 102d.
  • the core network 106/107/109 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
  • VoIP voice over internet protocol
  • the RAN 103/104/105 and/or the core network 106/107/109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103/104/105 or a different RAT.
  • the core network in addition to being connected to the RAN 103/104/105, which may be utilizing an E-UTRA radio technology, the core network
  • 106/107/109 may also be in communication with another RAN (not shown) employing a GSM radio technology.
  • the core network 106/107/109 may also serve 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 circuit-switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • the Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and the internet protocol (IP) in the TCP/IP internet protocol suite.
  • the networks 112 may include wired or wireless communications networks owned and/or operated by other service providers.
  • the networks 112 may include another core network connected to one or more RANs, which may employ the same RAT as the RAN 103/104/105 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications 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.
  • the WTRU 102c shown in FIG. 1A 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.
  • FIG. IB is a system diagram of an example WTRU 102.
  • the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138.
  • GPS global positioning system
  • the base stations 114a and 114b, and/or the nodes that base stations 114a and 114b may represent, such as but not limited to transceiver station (BTS), a Node-B, a site controller, an access point (AP), a home node-B, an evolved home node-B (eNodeB), a home evolved node-B (HeNB or HeNodeB), a home evolved node-B gateway, and proxy nodes, among others, may include some or all of the elements depicted in FIG. IB and described herein.
  • BTS transceiver station
  • Node-B a Node-B
  • AP access point
  • eNodeB evolved home node-B
  • HeNB or HeNodeB home evolved node-B gateway
  • proxy nodes among others, may include some or all of the elements depicted in FIG. IB and described herein.
  • 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 in association with a DSP core, a controller, a microcontroller,
  • DSP digital signal processor
  • 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
  • FIG. IB depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
  • the transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 115/116/117.
  • a base station e.g., the base station 114a
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 122 may be configured to transmit and receive both RF and light signals. It will be appreciated that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.
  • the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in some embodiments, the WTRU 102 may include two or more transmit/receive elements 122 (e.g. , multiple antennas) for transmitting and receiving wireless signals over the air interface 115/116/117.
  • the WTRU 102 may include two or more transmit/receive elements 122 (e.g. , multiple antennas) for transmitting and receiving wireless signals over the air interface 115/116/117.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as UTRA and IEEE 802.11, for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g. , a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the non-removable memory 130 may include random-access memory (RAM), 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.
  • SIM subscriber identity module
  • SD secure digital
  • 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).
  • the processor 118 may receive power from the power source 134, and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • 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) regarding the current location of the WTRU 102.
  • location information e.g. , longitude and latitude
  • the WTRU 102 may receive location information over the air interface 115/116/117 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination implementation while remaining consistent with an embodiment.
  • the processor 118 may further 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.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player
  • FIG. 1C is a system diagram of the RAN 103 and the core network 106 according to an embodiment.
  • the RAN 103 may employ a UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 115.
  • the RAN 103 may also be in communication with the core network 106.
  • the RAN 103 may include Node-Bs 140a, 140b, 140c, which may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 115.
  • the Node-Bs 140a, 140b, 140c may each be associated with a particular cell (not shown) within the RAN 103.
  • the RAN 103 may also include RNCs 142a, 142b. It will be appreciated that the RAN 103 may include any number of Node-Bs and RNCs while remaining consistent with an embodiment.
  • the Node-Bs 140a, 140b may be in communication with the RNC 142a. Additionally, the Node-B 140c may be in communication with the RNC 142b.
  • the Node-Bs 140a, 140b, 140c may communicate with the respective RNCs 142a, 142b via an Iub interface.
  • the RNCs 142a, 142b may be in communication with one another via an Iur interface.
  • Each of the RNCs 142a, 142b may be configured to control the respective Node-Bs 140a, 140b, 140c to which it is connected.
  • each of the RNCs 142a, 142b may be configured to carry out or support other functionality, such as outer loop power control, load control, admission control, packet scheduling, handover control, macrodiversity, security functions, data encryption, and the like.
  • the core network 106 shown in FIG. 1C may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, and/or a gateway GPRS support node (GGSN) 150. While each of the foregoing elements are depicted as part of the core network 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.
  • MGW media gateway
  • MSC mobile switching center
  • SGSN serving GPRS support node
  • GGSN gateway GPRS support node
  • the RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via an IuCS interface.
  • the MSC 146 may be connected to the MGW 144.
  • the MSC 146 and the MGW 144 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.
  • the RNC 142a in the RAN 103 may also be connected to the SGSN 148 in the core network 106 via an IuPS interface.
  • the SGSN 148 may be connected to the GGSN 150.
  • the SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between and the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the core network 106 may also be connected to the networks 1 12, which may include other wired or wireless networks that are owned and/or operated by other service providers.
  • FIG. ID is a system diagram of the RAN 104 and the core network 107 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 1 16.
  • the RAN 104 may also be in communication with the core network 107.
  • 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.
  • the eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, 160c 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 the uplink (UL) and/or downlink (DL), and the like. As shown in FIG. ID, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the core network 107 shown in FIG. ID may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the foregoing elements are depicted as part of the core network 107, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.
  • MME mobility management gateway
  • PDN packet data network
  • the MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S I interface and may serve as a control node.
  • the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer
  • the MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.
  • the serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via the SI interface. The serving gateway 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the serving gateway 164 may also perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the serving gateway 164 may also be connected to the PDN gateway 166, which 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.
  • the PDN gateway 166 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.
  • the core network 107 may facilitate communications with other networks.
  • the core network 107 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.
  • the core network 107 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the core network 107 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the core network 107 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and/or operated by other service providers.
  • FIG. IE is a system diagram of the RAN 105 and the core network 109 according to an embodiment.
  • the RAN 105 may be an access service network (ASN) that employs IEEE 802.16 radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 117.
  • ASN access service network
  • the communication links between the different functional entities of the WTRUs 102a, 102b, 102c, the RAN 105, and the core network 109 may be defined as reference points.
  • the RAN 105 may include base stations 180a, 180b, 180c, and an ASN gateway 182, though it will be appreciated that the RAN 105 may include any number of base stations and ASN gateways while remaining consistent with an embodiment.
  • the base stations 180a, 180b, 180c may each be associated with a particular cell (not shown) in the RAN 105 and may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 117.
  • the base stations 180a, 180b, 180c may implement MIMO technology.
  • the base station 180a for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.
  • the base stations 180a, 180b, 180c may also provide mobility management functions, such as handoff triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, and the like.
  • the ASN gateway 182 may serve as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 109, and the like.
  • the air interface 117 between the WTRUs 102a, 102b, 102c and the RAN 105 may be defined as an Rl reference point that implements the IEEE 802.16 specification.
  • each of the WTRUs 102a, 102b, 102c may establish a logical interface (not shown) with the core network 109.
  • the logical interface between the WTRUs 102a, 102b, 102c and the core network 109 may be defined as an R2 reference point, which may be used for authentication,
  • the communication link between each of the base stations 180a, 180b, 180c may be defined as an R8 reference point that includes protocols for facilitating WTRU handovers and the transfer of data between base stations.
  • the communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 may be defined as an R6 reference point.
  • the R6 reference point may include protocols for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c.
  • the RAN 105 may be connected to the core network 109.
  • the communication link between the RAN 105 and the core network 109 may defined as an R3 reference point that includes protocols for facilitating data transfer and mobility management capabilities, for example.
  • the core network 109 may include a mobile IP home agent (MIP-HA) 184, an authentication, authorization, accounting (AAA) server 186, and a gateway 188. While each of the foregoing elements are depicted as part of the core network 109, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the core network operator.
  • MIP-HA mobile IP home agent
  • AAA authentication, authorization, accounting
  • the MIP-HA may be responsible for IP address management, and may enable the WTRUs 102a, 102b, 102c to roam between different ASNs and/or different core networks.
  • the MIP-HA 184 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.
  • the AAA server 186 may be responsible for user authentication and for supporting user services.
  • the gateway 188 may facilitate interworking with other networks.
  • the gateway 188 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.
  • the gateway 188 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and/or operated by other service providers.
  • RAN 105 may be connected to other ASNs and the core network 109 may be connected to other core networks.
  • the communication link between the RAN 105 the other ASNs may be defined as an R4 reference point, which may include protocols for coordinating the mobility of the WTRUs 102a, 102b, 102c between the RAN 105 and the other ASNs.
  • the communication link between the core network 109 and the other core networks may be defined as an R5 reference, which may include protocols for facilitating interworking between home core networks and visited core networks.
  • a mobile communication system may be configured to support the transmission of, for example, one or more of Enhanced Mobile Broadband (eMBB) type data, Massive Machine Type Communications (mMTC) type data, Ultra Reliable and Low Latency Communications (URLLC) type data, and/or other types of data that may have very diverse Quality of Service (QoS) and/or latency requirements.
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communications
  • URLLC Ultra Reliable and Low Latency Communications
  • QoS Quality of Service
  • the data associated with these differing use cases may have different performance targets, such as higher data rate, higher spectrum efficiency, lower power and higher energy efficiency, lower latency and higher reliability, etc.
  • URLLC may be used, for example, in factory automation, remote tele-surgery, real time mobile control and vehicle-to-vehicle applications, etc.
  • a URLLC deployment may emphasize requirements on availability and reliability of transmission, which may be driven by low error probability and low outage rate targets.
  • URLLC related performance indicators may include, for example, 0.5 ms user plane latency for uplink (UL) and downlink (DL) and/or a reliability target of 10 "5 within 1 ms.
  • LTE may have a block error rate (BLER) target of 10% for data transmission.
  • An eNB may be in control of some or all resource allocation and scheduling.
  • a transport format may be designated as a resource block and/or a TTI with a length of 1 ms in duration. It may be challenging for LTE to meet various performance targets for a 5G radio interface given the expected performance requirements of the diverse services.
  • FIG. 2 is an example of an mmW Network.
  • the mmW network may include for example, an Ultra Dense Network (UDN).
  • a mmW base station (mB) e.g., 202 may serve mmW-capable UEsAVTRU(s) (e.g., referred to sometimes as mUEs or mWTRUs, but may be generally referred to herein as WTRUs, for example such as WTRU 204 through mmW links (e.g. , 206).
  • a base station capable of communicating using mmW (e.g., 202) may be referred to as a mB and/or gNB.
  • the mB e.g.
  • mB 202) may include a small cell (SC) aggregation point for LTE or LTE-A traffic.
  • the mB (e.g. , 202) may be connected to each other wirelessly through mmW links (e.g., 206).
  • the mB may reach a gateway mB (e.g. , 218) through one or more wireless hops.
  • the gateway mB (e.g., 218) may be a node with a wired access to a core network or an IP cloud (e.g. , through mobile edge computing 210).
  • a mmW node (e.g.
  • mmW nodes in a network may have a sub-6 GHz connection to a macro cell 212.
  • a control plane overlay may be used to provide fast and reliable control to systems.
  • An mmW software-defined networking (SDN) controller may be deployed, for example, in an operator core and/or in the Internet cloud (e.g., 214).
  • MEC e.g. , 210) may be shown with mmW small cell (e.g. , mB) but may be deployed in other ways, for example, at the macro 212.
  • Selected IP traffic offload (SIPTO) and/or a local IP access (LIPA (e.g., 208)) may be used.
  • a single hop and/or multi-hop scenarios may occur depending on how a WTRU or gNB accesses the network (e.g. , whether an access link is used).
  • a single-hop scenario may occur, for example, when a WTRU accesses the network or mB via an access link.
  • a single-hop extension or two-hop scenario may occur, for example, when WTRU accesses a cloud radio access network (C-RAN) baseband unit (BBU) via an access link, a fronthaul link, and/or a backhaul link. Latency for data communications may be minimized for an access link and/or a fronthaul link.
  • C-RAN cloud radio access network
  • BBU baseband unit
  • a multi-hop scenario may occur, for example, when a gNB or mB reaches the gateway mB through one or more wireless hops in a wireless mesh topology.
  • a gateway mB may have wired access to a core network or an IP cloud, for example, as shown in FIG. 2.
  • Latency for data communications may increase in a multi-hop scenario.
  • Latency associated with an access link or ajoint access link and fronthaul link may be reduced. Latency associated with data forwarding in a multi-hop environment may be reduced. Use cases may include applications that use one or more of ultra-low latency data transmission and reception in access links, joint access, fronthaul links, or multi-hop networks (e.g. , 5G tactile Internet and front-haul communications).
  • URLLC may be provided, for example, to meet communication requirements for next generation radio (NR) or 5G.
  • Approaches and/or techniques to reduce latency may be used, for example, to provide a higher data rate at a lower latency.
  • RTT round trip time
  • TCP transmission control protocol
  • Latency sources may contribute a total end to end delay for connected WTRUs.
  • Latency sources may include, for example, one or more of a transmission time interval (TTI), transmission/reception (TX/RX) processing time (e.g. , decoding latency, signal processing time, etc.), Hybrid-ARQ (HARQ) round-trip time (RTT), packet error rate, HARQ retransmissions and/or grant acquisition time and scheduling.
  • TTI transmission time interval
  • TX/RX transmission/reception
  • HARQ Hybrid-ARQ
  • RTT Hybrid-ARQ
  • Transmission of a request, grant, HARQ feedback and/or data may be accomplished in and/or according to the timing of blocks or chunks (e.g., subframes), which may have a fixed or known duration (e.g. , 1 ms). The duration may be referred to as a TTI.
  • Processing time may be, or may include, the time needed or used to process information.
  • the information may include data and or control signaling or information.
  • the processing may include, for example, encoding and/or decoding information by a WTRU and/or eNodeB (eNB).
  • Data processing time may be proportional to a transport block (TB) size of the data. Latency may be reduced in access link or joint access and fronthaul/backhaul link for wireless data transmission and reception.
  • Wireless multi-hop networks may involve delays associated with sequential forwarding techniques of wireless packets throughout a network hop-by -hop.
  • the delay may be a function of the number of hops and/or a packet size.
  • the delay of a data packet may increase as the packet size increases or the number of hops between the source and the destination increases.
  • Corresponding data communications may suffer with an increase in latency. Latency in multi-hop wireless data transmission and/or reception may be reduced, for example, using URLLC.
  • Reliable and low latency communications and/or a reduction in hybrid automatic repeat request (HARQ) retransmissions may be achieved, for example, by enhancing reliability and/or reducing BER or packet error rate.
  • Reliability may be enhanced in an access link, fronthaul link, and/or backhaul link.
  • BER or packet error rate for low latency data may be reduced in an access link, fronthaul link, and/or backhaul link.
  • Reliable low latency data communications may be implemented, for example, using advanced coding.
  • a polar code may be used to implement reliable low latency communications.
  • FIG. 3 is an example of a coding processing structure such as polar coding procedure 300 (e.g., for reliable low latency data communications using polar coding).
  • a polar coding structure may decompose a lossy channel into parallel correlated channels or bit channels.
  • a channel or bit channel may have a different level of signal reliability relative to one or more other channels or bit channels.
  • the signal reliability of the channel or bit channel may depend on the manner in which the data of the bit channel is coded by the channel coder with the other bit channels. For example, some bit channels may be encoded such that more redundancy information for that bit channel is included in the resultant channel coded data stream. This may result in that a bit channel that is more reliable than another channel has a higher likelihood of successful decoding than that another bit channel.
  • FIG. 3 illustrates how different bit channels may be associated with different reliability levels, for example based on the amount of mutual information included in the transmission.
  • an indicator of mutual information e.g. , l(W ) 302 of the channels or bit channels (e.g. , Wi) may indicate the amount of mutual information per bit channel, which may represent the relative robustness and/or reliability level of the channel.
  • the indicator may have a value of 0.6836 (e.g. , shown in 306).
  • the indicator may have a value of 0.9961 (e.g. , shown in 310). The value (e.g.
  • the capacity of channel W 8 may be 0.9961 while the capacity of channel W 4 may be 0.6836 for a given transmission.
  • the channel W 8 may be more reliable than the channel W 4 , as indicated by the value 310 that is greater than the value 306 and thus the "capacity" of the channel may be considered higher.
  • a mathematical operation may be performed at, for example, 312. The mathematical operation may be performed on symbols.
  • the mathematical operation may include a bit-wise XOR operation such as modulo-2 addition of two one-bit number.
  • Signal reliability relationships between channels may be given by Eq. 1 based on Eq. 2.
  • Channels corresponding to certain indicator values may be considered reliable or good channels.
  • channels W 8 , W 7 , W 6 , W 4 may be considered as good channels based on the respective I(W ).
  • the capacity of a binary erasure channel (BEC) (1 ⁇ 2) may be 1 ⁇ 2.
  • the capacity may be achieved, for example, by application of a rate 1 ⁇ 2 polar code.
  • a polar code structure may set a coding rate, for example, by selecting a fixed number of available bit channels to the polar encoder (e.g., a fixed
  • a rate (e.g. ,
  • the individual capacity of some or all of k bit channels may be different, for example, providing k different levels of message qualities.
  • an encoder may utilize the bit channels to ensure higher priority data (e.g. , data associated with a more stringent reliability or latency QoS parameter) is sent using a higher reliability bit channel, while lower reliability bit channels can be used for lower priority data (e.g. , other types of traffic that does not have low latency QoS requirements such as best effort traffic, eMBB traffic, etc.).
  • higher priority data e.g. , data associated with a more stringent reliability or latency QoS parameter
  • lower reliability bit channels can be used for lower priority data (e.g. , other types of traffic that does not have low latency QoS requirements such as best effort traffic, eMBB traffic, etc.).
  • bit channels of higher reliability may be mapped to traffic of higher priority based on a bit channel mapping rule(s).
  • a bit channel mapping rule may use one or more of a contiguous, non-contiguous, or hybrid mapping function(s) for one or more code blocks (CBs).
  • CB may refer to a demarcation of data and/or the data to be included in a given transmission.
  • the bit channel mapping rule may be pre-defined, configured (e.g. , via higher layer signaling such as radio resource control (RRC) signaling), and/or dynamically scheduled (e.g. , via a downlink assignment, an uplink grant, other physical layer signaling and/or with other scheduling information).
  • RRC radio resource control
  • the predefinition and/or configuration may be via higher layer signaling such as RRC configuration and/or medium access control control element (MAC CE).
  • the dynamical scheduling may be via LI (e.g., Physical Layer - PHY) control channel or control information that may be carried in an LI DCI control field(s) or a preamble(s).
  • LI e.g., Physical Layer - PHY
  • some or all traffic of higher priority may be mapped to a bit channel(s) of higher quality (e.g. , a bit channel of the highest quality) based on a ranking of bit channels in a contiguous fashion.
  • a bit channel(s) of higher quality e.g. , a bit channel of the highest quality
  • the higher priority traffic or data type may be mapped to one or more of the highest bit channels considered as good channels including channels W 8 , W 7 , W 6 , W 45 .
  • the other traffic or data types may be mapped to other channels.
  • the traffic of the higher priority may be emphasized by using the contiguous mapping function for a CB.
  • a traffic or data type(s) of higher priority and traffic or data types of lower priority may be mapped to some or all bit channels in a noncontiguous fashion.
  • bit channel mappings may be performed based on a distributed pattern and/or in an interleaved fashion.
  • the traffic of the higher priority may be mapped to bit channels and distributed across some or all bit channels uniformly or partially uniform according to a first ratio (e.g. , equally or unequally). Traffic of different priorities may be distributed among across some or all bit channels uniformly or partially uniform according to a second ratio (e.g. , equally or unequally).
  • the high priority data may be mapped to relatively higher priority bit channels (e.g. , W 8 , W 7 , W 6 , W 4 ) for 75% of the bits/transmissions and to lower priority bit channels (e.g., W 5 , W 3 , W 2 , W t ) for 25% of the bits/transmissions.
  • the low priority data may then be mapped to relatively higher priority bit channels (e.g., W 8 , W 7 , W 6 , W 4 ) for 25% of the bits/transmissions and to relatively lower priority bit channels (e.g. , W 5 , W 3 , W 2 , W-y) for 75% of the bits/transmissions.
  • Ratios in this example are exemplary and other ratios may be used depending on the QoS parameters associated with the higher and lower priority data.
  • More than two data types may be mapped to the plurality of channels. For example, there may be a plurality of traffic or data types (e.g. , traffic type 1, traffic type 2, ... , traffic type N) being mapped to a plurality of bit channels (e.g., bit channel 1, bit channel 2, ... , bit channel M).
  • Each traffic or data type may have a selected or specific ratio (e.g. , from 0% to 100%) for mapping to a given bit channel.
  • a hybridization of contiguous and non-contiguous bit channel mappings may be implemented at the encoder.
  • a contiguous mapping function may be used for some portions of a CB and/or one or more CBs for a traffic of higher priority and/or lower priority.
  • a non-contiguous mapping function may be used for some portions of a CB and/or one or more CBs for a traffic of higher priority and/or lower priority.
  • a highest priority data type may be contiguously mapped to the highest reliability bit channels, and a plurality of relatively lower priority data types may use a non-contiguous mapping for the remaining (e.g., lower reliability) bit channels.
  • FIG. 4 is an example of data and/or control prioritization processing multiplexed with additional control signaling.
  • FIG. 4 shows an example of a processing structure 400 (e.g. , for a transport channel on a cell).
  • a processing structure 400 for a transport block of a cell may include one or more of data and/or control multiplexing 408, data and/or control CRC attachment 410, CB segmentation and CRC attachment 412, bit channel mapping 414, channel coding 416, rate match (RM) 420, CB concatenation 422, additional control multiplexing 424, and/or data and control channel multiplexing 426.
  • the bit channel assignment and control 418 may refer to the configuration and/or determination of how to perform the bit channel mapping 414 and/or the channel coding 416. For example, if the transmission is to be performed in the uplink, the bit channel assignment and control 418 may refer to a configuration (e.g. , RRC configuration) received by a WTRU from a base station (e.g. , gNB) that may indicate the mapping of different data types and/or priority tiers to different bit channels. In an example, the bit channel assignment and control 418 may be received dynamically (e.g., in and/or contemporaneously with a downlink assignment/uplink grant), for example if the bit channel mapping is changed dynamically per transmission. [0087] As shown in FIG.
  • data 404 and/or control data 406 may be received, for example, at an encoder.
  • the encoder may be comprised in a WTRU or a network entity such as a base station. For example, if the transmission is to be performed in the uplink, the encoder may be comprised in a WTRU.
  • the data 404 may be a type of URLLC data or the like, which may correspond to a first type of data.
  • the data 404 may include other types of data such as eMBB data, mMTC data, etc.
  • the control 406 may include one or more of higher layer control data, Ll(e.g. , Physical Layer - PHY) /L2 control data, or other control information.
  • the control 406 and/or the data 404 may be an input to the data and control multiplexing 408.
  • the control 406 may be multiplexed with the data 404 at 408.
  • CRC may be added to some or all control (e.g. , control 406) or data (e.g. , data 404), for example separately or together as a single data block.
  • the multiplexed data may be segmented for inclusion into one or more CBs, and/or a CRC(s) may be attached to the CBs.
  • each CB may represent a priority tier of the data.
  • the CBs may be implemented in such a way so as to achieve a non-contiguous inclusion of data of different tiers (e.g. , include a given ratio a data of different type(s) in each CB).
  • a CB CRC may not be attached to all CBs. Whether to attach CB CRC may, for example, depend on an architecture or configuration.
  • the data of one or more CB(s) may be mapped to bit channels associated with channel coding function 416.
  • Channel coding may be performed at 416 (e.g., using polar code), and RM may be performed at 420.
  • One or more CBs may be concatenated at 422 and multiplexed with the other control information 424 at 426.
  • FIG. 5 is an example of data and/or control prioritization processing.
  • FIG. 5 shows an example of a processing structure qos (e.g., for a transport channel on a cell).
  • a processing structure 500 for a transport block of a cell may include one or more of data and/or control multiplexing 506, data and/or control CRC attachment 508, CB segmentation and CRC attachment 510, bit channel mapping 512, channel coding 516, RM 518, and/or CB
  • the bit channel assignment and control 514 may refer to the configuration and/or determination of how to perform bit channel mapping 512 and/or channel coding 516. For example, if the transmission is to be performed in the uplink, the bit channel assignment and control 514 may refer to a configuration (e.g. , RRC configuration) received by a WTRU from a base station (e.g., gNB) that may indicate the mapping of different data types and/or priority tiers to specific bit channels. In an example, the bit channel assignment and control 514 may be received dynamically (e.g., in and/or contemporaneously with a downlink assignment/uplink grant), for example if the bit channel mapping is changed dynamically per transmission. [0089] As shown in FIG.
  • data 502 and/or control data or traffic 504 may be received, for example, at an encoder.
  • the encoder may be comprised in a WTRU or a network entity such as a base station.
  • the data 502 may be a type of URLLC data or the like, which may correspond to a first type of data.
  • the data 404 may include other types of data such as eMBB data, mMTC data, etc.
  • the control 504 may include one or more of higher layer control data, L1/L2 control data or other control information.
  • the control 504 and/or the data 502 may be an input to data and control multiplexing 506.
  • the control 504 may be multiplexed with the data 502 at 506.
  • CRC may be added to some or all control (e.g.
  • the multiplexed data may be segmented for inclusion into one or more CBs, and/or CRC may be attached to the CBs.
  • each CB may represent a priority tier of the data.
  • the CBs may be implemented in such a way so as to achieve a non-contiguous inclusion of data of different tiers (e.g., include a given ratio a data of different type(s) in each CB).
  • CB CRC may not be attached to all CBs. Whether to attach CB CRC may, for example, depend on an architecture or configuration.
  • the data or traffic of one or more CBs may be mapped to bit channels associated with channel coding function 516.
  • Channel coding may be performed at 516 (e.g., using Polar code), and RM may be performed at 518.
  • One or more CBs may be concatenated at 520.
  • a transmitter for supporting multiple traffic or data types with different priorities may use a polar decoder(s) (e.g., as shown in FIG. 6).
  • a transmitter may receive traffic of multiple QoS requirements (e.g. , different throughput or latency requirements).
  • the transmitter may sort the traffic into various tiers (e.g., priority tiers) based on the QoS requirements.
  • the transmitter may map the priority tiers to a subset(s) of polar coding bit channels in a local manner (e.g. , a contiguous mapping). Relatively higher priority tiers may receive the highest capacity bit channels, and relatively lower priority tiers may receive lower capacity bit channels.
  • the transmitter may map the priority tiers to a subset(s) of polar coding bit channels in a distributive manner (e.g. , a non-contiguous mapping or via a distributed bit mapping rule).
  • Some or all sets of polar coding bit channels may be used for each priority tier. Some or all priority tiers may be afforded a probabilistic throughput or latency requirements.
  • the transmitter may map the priority tiers to a subset(s) of polar coding bit channels in a hybrid manner (e.g. , via a hybrid mapping rule). Some high priority traffic may receive highest capacity bit channels on demand, and remaining bit channels may be allocated based on performance requirements. The subset(s) of bit channels may be of varying or equal sizes.
  • Data e.g. , bit channel data
  • a CB-level CRC may be inserted into mapped or dedicated bit channels prior to polar encoding.
  • the encoded blocks may be resized based on a rate matching implementation to meet channel capacity requirements (e.g. , constraints).
  • Control information for a recovery of the encoded blocks may be sent in parallel via another coding approach (e.g. , RM, tail-biting convolutional coding (TBCC), turbo or low-density parity check (LDPC) encoding) or via a dedicated polar encoding approach.
  • RM tail-biting convolutional coding
  • LDPC low-density parity check
  • An approach at a transmitter (e.g. , in a gNB) for supporting multiple traffic types with different priorities using polar codes may include receiving a first traffic (e.g., traffic type) and a second traffic with different priorities, multiplexing and priority sorting the first traffic and the second traffic into tiers (e.g., priority tiers), and mapping the first and second traffic sorted into priority tiers of a transmission according to a tier mapping rule and performing tier level CRC attachment.
  • a tier mapping rule may be based on priority tiers with a same tier size.
  • a tier mapping rule may be based on priority tiers with a same tier size and a same priority.
  • a tier mapping rule may be based on priority tiers with a same tier size and varying priorities.
  • a tier mapping rule may be based on priority tiers with different tier sizes.
  • a tier mapping rule may be based on priority tiers with different tier sizes and a same priority.
  • a tier mapping rule may be based on priority tiers with different tier sizes and varying priorities.
  • the approach may include performing CB segmentation bit-channel mapping by mapping information bits from different tiers (e.g., priority tiers) into component bits of CBs of the transmission according to a bit channel mapping rule.
  • the bit channel mapping rule may include a contiguous (e.g. , localized), a non-contiguous (e.g. , distributed), and/or a hybrid bit channel mapping rule.
  • the contiguous bit channel mapping rule may map higher priority tiers to more reliable bit channels and map lower priority tiers to less reliable bit channels.
  • a noncontiguous bit channel mapping rule may uniformly or partial uniformly map priority tiers to bit channels.
  • a hybrid bit channel mapping rule may map priority tiers to bit channels using a contiguous bit channel mapping rule or a non-contiguous bit channel mapping rule (e.g., dynamically on per CB basis).
  • the approach may include attaching CB level CRC for a CB, executing polar encoding and/or rate matching for a CB, sending a transmission that includes a first traffic (e.g. , URLLC data) with a first priority and a second traffic (e.g. , control signaling) with a second priority that has a lower priority level than the first priority, and sending control information that includes a channel mapping rule (e.g., for a CB, a number of bits for a tier, bit channel mapping rules, etc.) and a tier mapping rule (e.g. , tier mapping rules, tier sizes, etc.) by LI (e.g. , PHY) control signaling via NR-physical downlink control channel (NR-PDCCH), NR-enhanced physical downlink control channel (NR-ePDCCH), or MAC-CE etc.
  • a channel mapping rule e.g., for a CB, a number of bits for a tier, bit channel mapping rules
  • FIG. 6 shows a transmitter approach 600 for traffic prioritization based on bit channels.
  • traffic types including data 602 (e.g., URLLC data and/or various other types of data) and control information 604 may be received, for example, at an encoder.
  • the encoder may multiplex data 602 and control information 604.
  • the control information 604 may include higher layer control information (e.g. , RRC messaging).
  • the control information 604 may be processed or treated differently from the control information 632.
  • the control information 604 may be transmitted with data (e.g., data 602) as a traffic.
  • the control information 632 may be used to facilitate demodulation and/or decoding of the received traffic (e.g. , the multiplexed traffic of URLLC data 602 and control information 604)
  • Multiplexing the data 602 and/or the control information 604 may be scheduled by a network controller.
  • the scheduling may be via a DCI message or RRC signaling or MAC CE.
  • the data 602 and/or the control information 604 may be multiplexed and/or transmitted via a common data frame.
  • Control information e.g., the control information 604 may be processed in a manner that is similar or the same as the way in which data (e.g., the data 602) is processed.
  • the common data frame may comprise one or more of a subframe, a slot, a mini-slot, a symbol, or the like.
  • the multiplexed data 602 and/or control information 604 may be sorted into various tiers that are associated with different priorities.
  • Data prioritization may be performed, for example, according to a pre-defined message priority to allow a receiver to identify relevant messages.
  • the priority sorting may be performed based on a or a set of tier mapping rule(s).
  • the tier mapping rule may assign different traffic or different types of traffic to different tiers.
  • One or more tiers may be associated with a priority, and another tier may be associated with another priority. For example, a traffic type that has more stringent latency requirements may be mapped to a higher priority tier than other traffic types.
  • the number of tiers used may depend on the variety of the traffic (e.g.
  • the tier mapping rule may be received via a DCI message or RRC signaling or MAC CE.
  • an encoder may receive a tier mapping rule and/or sort the multiplexed data 602 and/or control information 604 into a tier 610, a tier 614, a tier 644, and/or a tier 616.
  • the tier 610 may be associated with a priority that is higher than a priority associated with the tier 614, or 616.
  • Traffic e.g. , traffic sorted into tiers
  • CBs may be segmented into CBs.
  • CB segmentation bit-channel mapping may be performed by mapping information bits from different tiers into component bits or a bit channel(s) of CBs of the transmission (e.g., according to a bit channel mapping rule).
  • the tier 610, 614,644, and/or 616 may be segmented into one or more CBs (e.g., CB 640).
  • the segmentation of the tier 610, 614,644, ... and/or 616 into one or more CBs may be used when a size of the tier 610, 614,644, ... and/or 616 is above certain threshold (e.g. , above a size of a CB).
  • the CB(s) may comprise one or more bits and/or bit channels that are associated with various reliabilities.
  • the bits and/or bit channels may be generated via a coding scheme (e.g. , as shown in FIG. 3).
  • the coding scheme may associate the bit channels with different reliabilities.
  • the coding scheme may be based on a polar code. Via polar coding, one or more bit channels may provide a high reliability, and one or more bit channels may provide a reliability that is different from the high reliability.
  • a bit mapping rule may be used to map various tiers to different bits and/or bit channels.
  • Priority tiers may be arranged in a CB(s) according to a bit channel mapping function. For example, a tier of a higher priority may be mapped to bits or a bit channel associated with a higher reliability. The tier of higher priority may be mapped to bits or a bit channel(s) based on contiguous, non-contiguous, and/or a hybridization mapping rules (e.g., as discussed herein).
  • CB 642 may comprise a bit channel(s) 620 that have been assigned to the tier 610.
  • the CB 642 may comprise a bit channel(s) 622 that have been assigned to the tier 614.
  • the CB 642 may comprise a bit channel(s) 624 that have been assigned to the tier 644.
  • the CB 642 may comprise a bit channel(s) 626 that have been assigned to the tier 616.
  • the bit channel mapping rule that enables bit channel assignment and control may be signaled and/or received from a network entity such as a gNB.
  • a gNB may perform bit channel assignment and/or may control bit channel mappings.
  • bit channel allocations and mappings at code level of polar codes may be signaled to a WTRU from the gNB.
  • the gNB may inform the WTRU how bit channel mappings are accomplished.
  • Bit channel mappings may be, for example, based on a dynamic allocation or a pre-defined bit channel mapping rule(s). Mappings may be performed for data, control, CRC, etc.
  • the bit channel mapping rule that enables bit channel assignment and control may be determined by a WTRU or a network entity (e.g. , a base station) based on an indication or a pre- configuration that the WTRU or the network entity received and/or stored.
  • the bit channel mapping rule may be dynamically signaled to the WTRU via a downlink control information, a PDCCH, an ePDCCH, or the like.
  • the bit channel mapping rule applied to CB 642 may differ from the bit channel mapping rule applied to CB 646.
  • the bit channel mapping rule applied to CB 642 may include a contiguous bit channel mapping function where tier 610 may be allocated to the bit channel with the highest reliability and tier 614 may be allocated to other bit channels.
  • the bit channel mapping rule applied to CB 646 may include a non-contiguous bit channel mapping function where tier 610 may be allocated to some or all bit channels with various reliabilities and tier 614 may be allocated to some or all bit channels with various reliabilities.
  • k bit channels (e.g., based on polar coding) may be available for allocation, c out of the k bit channels may be reserved for a CB CRC(s).
  • k— c priority tiers may be permitted if a bit channel is allocated to a tier. Fewer than k— c priority tiers may be permitted if multiple bit channels are allocated to a tier.
  • a tier may have multiple bit channels for allocation.
  • a bit/ bit channel mapping function may be used to map data from tiers (e.g., priority tiers) to bits/bit channels, for example to meet objectives related to message reliability.
  • a bit channel mapping function may map the highest priority messages to the highest quality bit channels to ensure minimum retransmission of vital messages.
  • Data, control, different control information, and/or transport blocks (e.g., regardless data types or message formats) may be sorted into P ⁇ k— c tiers with a tier p £ 1, ... , P.
  • a tier (e.g., priority tier) may be allocated a set of bits, n p E N p .
  • a size of a priority tier, N p (e.g.
  • the number of bits allocated to the priority tier may be determined based on a composition of a data block and a priority of the bits within the data block.
  • a bit mapping function may select /: K j ⁇ W m ⁇ m E 1, ... , p, for example, according to a set of objectives and constraints.
  • a bit channel mapping rule may use a contiguous, non-contiguous, and/or hybrid mapping function for a CB (e.g., as described herein). For a contiguous mapping function, some or all traffic of higher priority may be mapped to a bit channel of the highest quality or several bit channels of higher quality.
  • the contiguous bit channel mapping rule (e.g. , including the contiguous bit channel mapping function) may map higher priority tiers to more reliable bit channels and map lower priority tiers to less reliable bit channels.
  • a non-contiguous bit channel mapping rule (e.g. , including the non-contiguous bit channel mapping function) may uniformly or partial uniformly map priority tiers to bit channels.
  • a hybrid bit channel mapping rule (e.g.
  • contiguous and non-contiguous bit channel mapping functions may map priority tiers to bit channels using a contiguous bit channel mapping function or a non-contiguous bit channel mapping function (e.g. , dynamically on per CB basis).
  • a CB CRC may be allocated and/or attached to one or more of the CBs herein.
  • CB CRC 628 may be attached to the CB 642.
  • bit channel(s) 620, 622, 624, 626 may still be successfully received by the receiver decoder.
  • CB CRC 628 is not passed (e.g. , there is an error somewhere within CB 642), the error may not be present in the bits of bit channel 620, since the bits of bit channel 620 may be more reliable.
  • bit channel 620 may have been correctly received.
  • Bit channel 620 may correspond to tier 610 and/or tier-level CRC 612. If tier-level CRC 612 is successfully passed (even after failure of CB CRC 628), tier 610 data may still be processed while further retransmissions may be used for ensuring proper delivery of the remainder of CB 642.
  • One or more bits or bit channels may be allocated and reserved for CRC.
  • a bit channel may not be reserved for a CB CRC, for example, when a CRC is not attached to CB.
  • a number of (e.g., c) bit channels may be reserved for a CB CRC attachment.
  • Various approaches may be used, alone or in combination, to reserve and/or allocate c bit channels for a CB CRC. When a CRC is attached to a CB, and c bit channels are reserved for the CB CRC, the c lowest priority bit channels may be reserved or allocated for CB CRC.
  • bit channels When a CRC is attached to a CB, and c bit channels are reserved for the CB CRC, the c highest priority bit channels may be reserved or allocated for the CB CRC. When a CRC is attached to a CB, and c bit channels are reserved for the CB CRC, c bit channels may be interleaved across some or all bit channels and reserved or allocated for the CB CRC. When a CRC is attached to a CB, and c bit channels are reserved for the CB CRC, c bit channels may be grouped or divided into L bit channel groups and reserved for CB CRC. A bit channel group may have c/L bit channels. Other variants of bit channels allocation and reservation for CB CRC may be implemented.
  • the CBs including the CB 642 and the CB 646 may be encoded via a polar encoder. And a rate matching may be performed.
  • the encoded CBs including the encoded CB 636 may be multiplexed with other types of CBs such as control CB 638.
  • Control information may be encoded via a parallel encoder (e.g., another polar encoder, or a different encoder, e.g. RM, TBCC, LDPC or Turbo code, etc.). Sending control information via bits or a bit channel(s) associated with reliabilities that are lower than the reliability associated with data (e.g. , data 602) as described herein may not be sufficient to meet signal integrity requirements.
  • Control information or additional control information may be encoded via a parallel encoder(s) or a parallel control channel(s).
  • the additional control information 632 may be encoded separately via a parallel encoder (e.g. , another polar encoder, or a different encoder, e.g.
  • the additional control information 632 may be encoded at 634, and segmented into one or more control CBs including the control CB 638.
  • the control CBs including the control CB 638 may be interleaved and/or multiplexed with the encoded CBs including the encoded CB 636.
  • the implementation may include an approach for a receiver (e.g. , in a UE) that supports multiple traffic types with different priorities using polar decoders (e.g. , as shown in FIG. 7).
  • a receiver e.g. , in a UE
  • polar decoders e.g. , as shown in FIG. 7
  • the receiver may decode dedicated control channel information to identify the bit channel prioritization used by the transmitter.
  • the receiver may decode additional configuration parameters required for proper recovery.
  • the additional configuration parameters required for proper recovery may include bit tier sizes, bit channel mappings, modulation and coding scheme (MCS), etc.
  • MCS modulation and coding scheme
  • the receiver may recover transmitted payload from a CB (e.g. , an individual CB(s)) via polar decoding.
  • the receiver may perform a CRC to verify proper recovery of a CB.
  • the receiver may sort or collect a priority tier(s) from priority bit
  • the receiver may check a priority tier-level CRC(s) to verify the integrity of a priority tier(s) (e.g. , a priority tier for URLLC, a priority tier for control, etc.) If a priority tier-level CRC for a priority tier fails, the receiver may request retransmission of the failed priority tier.
  • the re-transmission may be performed according to a same priority bit channelization as an initial or the failed transmission.
  • the re-transmission may be performed (e.g. , dynamically according to a different priority bit channelization).
  • An approach at a receiver for supporting multiple traffic types with different priorities using polar codes may include receiving control information that includes a bit channel mapping rule (e.g. , for a CB, a number of bits for a tier, bit channel mapping rules, etc.) and a tier mapping rule (e.g. , tier mapping rules, tier sizes, etc.).
  • the approach at a receiver may include receiving a transmission that includes a first traffic (e.g. , URLLC data) with a first priority and a second traffic (e.g. , control signaling) with a second priority that has a lower priority level than the first priority.
  • the approach at a receiver may include de-rate matching and polar decoding for a CB with a CB level CRC check. If a CB level CRC check for a CB fails, the failed CB may be discarded. Alternatively, the CB level CRC for the failed decoded CB may be removed and the failed decoded CB may be sent to the CB to tier de-mapping. If a CB level CRC for a CB passes, the CB level CRC for the passed CB may be removed, and the decoded CB may be sent to the CB to tier de-mapping.
  • the approach at the receiver may include de-mapping component bits of a CB(s) of the transmission into different tiers according to the bit channel mapping rule.
  • the bit channel mapping rule may include a localized or distributed bit channel mapping rule.
  • the localized bit channel mapping rule may map higher priority tiers to more reliable bit channels and map lower priority tiers to less reliable bit channels.
  • a distributed bit channel mapping rule may uniformly or partial uniformly map priority tiers to bit channels.
  • a hybrid bit channel mapping rule may map priority tiers to bit channels using a localized bit channel mapping rule or a distributed bit channel mapping rule (e.g., dynamically on per CB basis).
  • the approach at the receiver may include performing a tier level CRC check and de- mapping tiers of the transmission into the first and second traffic according to a tier mapping rule.
  • a tier mapping rule may be based on priority tiers with a same tier size.
  • a tier mapping rule may be based on priority tiers with a same tier size and a same priority.
  • a tier mapping rule may be based on priority tiers with a same tier size and varying priorities.
  • a tier mapping rule may be based on priority tiers with different tier sizes.
  • a tier mapping rule may be based on priority tiers with different tier sizes and a same priority.
  • a tier mapping rule may be based on priority tiers with different tier sizes and varying priorities.
  • the approach at the receiver may include de-multiplexing the first traffic and the second traffic.
  • FIG. 7 is an example of a receiver approach for traffic prioritization based on bit channels.
  • FIG. 7 shows an example flow 700 for decoding multiplexed information (e.g., data 602, and control information 604 with the assistance of additional control information 632).
  • the multiplexed information may be received via one or more symbols.
  • the received multiplexed information may include the traffic and/or control information.
  • the control information may include a channel mapping rule (e.g., for a CB, a number of bits for a tier, bit channel mapping rules, etc.) and/or a tier mapping rule (e.g., tier mapping rules, tier sizes, etc.).
  • the received multiplexed information may include or be comprised in modulation symbols that may be allocated to one or more resource blocks (RBs) or resource elements (REs).
  • derate matching may be performed on the multiplexed information.
  • the multiplexed information (e.g. , post de-rate matching) may be decoded via a polar decoder.
  • a CB level CRC check may be performed on the multiplexed information. If a CB level CRC check fails, the failed CB may be discarded. Alternatively, if a CB level CRC check fails, the CRC attached to the unsuccessfully decoded CB may be removed at 704. The CRCs attached to the successfully decoded CBs that pass the CRC check may be removed at 704.
  • the decoded CBs without the CRC attached may be stored.
  • the decoded CBs may include decoded CB 708, decoded CB 716, and/or decoded CB 718.
  • a decoded CB may comprise one or more bits or bit channels that are associated with tiers of different priorities.
  • the decoded 708 may comprise bits/bit channels 710 allocated to higher priority tiers, bits/bit channels 712 allocated to lower priority tiers, and bits/bit channels 714 allocated to other priority tiers.
  • the decoded CBs may differ in composition (e.g., different bit channel may be used for different types/priorities of data in different CBs).
  • the composition of the decoded CB 708 may differ from the composition of the decoded CB 718.
  • the decoded CB 708 may comprise bits/bit channels allocated to both higher priority tiers and lower priority tiers.
  • the decoded CB 718 may include bits/bit channels 720 allocated to lower priority tiers and may not include bits/bit channels allocated to higher priority tiers.
  • the flow 700 may include de-mapping component bits of a CB(s) of the transmission into different tiers, for example, according to the bit channel mapping rule.
  • the decoded CBs may be de-mapped to various priority tiers, for example, using the bit channel mapping rule (e.g. , different bit channel may include different types/priorities of data in different CBs).
  • the bit channel mapping rule may be received via Layer 1 (e.g., PHY) or L2 as additional control information on multiplexing configuration. For example, if the decoder is at a WTRU for the downlink, the de-mapping rule may be indicated in the downlink assignment.
  • the additional control information may include the number of bits for a tier, the bit channel mapping rule, and/or other control information for a CB (e.g., CB 708, CB 716, and CB 718).
  • the bit channel mapping rule may be used to de-map various priority tiers from different bits and/or bit channels. For example, a higher priority tier may be de-mapped from bits or a bit channel(s) associated with a higher reliability.
  • CB 708 may comprise a bit channel(s) 710 that have been assigned to the tier 742 and a bit channel(s) 712 that have been assigned to the tier 744.
  • Tier 742 may correspond to URLLC data, tier 744 may correspond to control information, and tier 746 may correspond to other information.
  • the higher priority tier 742 may be de- mapped from the bit channel 710 that is associated with a higher reliability in channel encoding/decoding.
  • the de-mapping may be based on contiguous, non-contiguous, and/or a hybridization mapping rules (e.g., as discussed herein).
  • the localized bit channel mapping rule may map higher priority tiers to more reliable bit channels and map lower priority tiers to less reliable bit channels.
  • a distributed bit channel mapping rule may uniformly or partial uniformly map priority tiers to bit channels.
  • a hybrid bit channel mapping rule may map priority tiers to bit channels using a localized bit channel mapping rule or a distributed bit channel mapping rule (e.g. , dynamically on per CB basis).
  • the higher reliability bit channel 754 may be used for tier 742
  • lower reliability bit channel 756 may be used for tier 744
  • bit channel 734 may be used for tier 746.
  • a portion 736 of the bit channel 748 may be used for tier 742.
  • a portion 738 of the bit channel 748 may be used for tier 744.
  • a portion 740 of the bit channel 748 may be used for tier 746.
  • data types or traffic of various tiers with attached tier-level CRC may be collected and/or stored.
  • data in tier 728 may include data collected from the bit channel 710, data collected from the bit channel 754, and/or the like.
  • Data in tier 730 may include data collected from the bit channel 712, data collected from the bit channel 756, and data collected from the bit channel 720.
  • Data in tier 732 may include data collected from the bit channel 714, data collected from the bit channel 757 and data collected from the bit channel 722.
  • a tier-level CRC check may be performed and tier to traffic de-mapping may be performed.
  • the tier to traffic de-mapping may be based on a tier mapping rule.
  • the tier mapping rule may be received via Layer 1 or Layer 2 control as additional control information on multiplexing configuration.
  • the additional control information may include the tier mapping rule, tier size, and/or other information.
  • the tier mapping rule may correspond different traffic or different types of data to different tiers.
  • the tiers of the traffic may be de-mapped into traffic A (e.g. , a first data or traffic type) and traffic B (e.g., a second data or traffic type).
  • traffic A may include data 602
  • the traffic B may include control information 604.
  • the scheme herein may support multiple traffic or data types which may be mapped to multiple tiers and/or bit-channels of polar code.
  • One or more of the schemes for processing multiple traffic types with different priorities may be used for DL at gNB and/or UL at a WTRU.
  • control information comprising a bit channel mapping rule and/or a tier mapping rule may be configured and signaled as part of UL grant in DL NR- NR-PDCCHor NR-ePDCCH.
  • the control information may be signaled in addition to a control traffic.
  • the channel mapping rule may include, for a CB, a number of bits for a tier, bit channel mapping rules, etc.
  • a tier mapping rule may include a tier mapping rule(s), tier size, etc.
  • Bit channel mapping and/or priority tier mapping may enable prioritization of low latency traffic (e.g. , URLLC) over control information. Some data messages, such as messages arriving infrequently, may have higher priority than some control messages. Reliable reception of messages may be provided to reduce latency. Bit channel mapping functions may provide more reliable reception, for example, by reconfiguring priority sorting based on the composition of a multiplexed data and control message.
  • FIG. 8 is an example of a transmitter approach for prioritization of URLLC data multiplexed with control information based on bit channels.
  • FIG. 8 shows process 800 using polar coding for high priority URLLC data multiplexed with control.
  • a bit channel mapping rule(s) e.g. , rules comprising mapping functions
  • URLLC data 802 and control information 804 may be received, for example, at an encoder.
  • the URLLC data may be transmitted (e.g., randomly and/or infrequently) over a network.
  • the transmission may comprise an indication of the URLLC data and/or an indication of a presence of URLLC or control information.
  • an indication of the URLLC data may be signaled to a WTRU and/or a destination node.
  • the indication of the URLLC data may be signaled to a WTRU in an access link such as mmW access link.
  • the indication of the URLLC data may be signaled to a destination node using mmW link.
  • the indication of the URLLC data may be signaled to a destination node in one or more of fronthaul links, backhaul links, or a multi-hop network.
  • a gNB may indicate to a WTRU whether one or more of data (e.g., URLLC data) or control are present, for example, to support mapping and/or de- mapping accuracy by the WTRU.
  • the indication may be signaled explicitly (e.g., by a control channel).
  • An indication may be signaled implicitly (e.g., by pre-defined configurations of data and control messages). Signaling may be in a form of a DCI message or RRC signaling.
  • the URLLC data 802 and/or the control information 804 may be multiplexed at 806. Multiplexing the URLLC data 802 and/or the control information 804 may be scheduled by a network controller. The scheduling may be via a DCI message or RRC signaling.
  • the URLLC data 802 and/or the control information 804 may be multiplexed and/or transmitted via a common data frame. Control information (e.g., the control information 804) may be processed in a manner that is similar or the same as the way in which data (e.g., the URLLC data 802) is processed.
  • the common data frame may comprise one or more of a subframe, a slot, a symbol, or the like.
  • the multiplexed URLLC data 802 and/or control information 804 may be sorted into various tiers that are associated with different priorities.
  • the priority sorting may be performed based on a or a set of tier mapping rule(s).
  • the tier mapping rule may be used to assign different traffic or different types of traffic with different requirements (e.g. , different QoS, or different reliability requirement such as BLER requirement, or different latency requirements etc.) to different tiers.
  • One or more tiers may be associated with a priority, and another tier may be associated with another priority.
  • the number of tiers used may depend on the variety and/or amount (or size) of the traffic.
  • the tier mapping rule may be pre-defined in the specification, configured by RRC message, and/or signaled by LI control signaling (e.g., a DCI message) or L2 MAC CE.
  • LI control signaling e.g., a DCI message
  • L2 MAC CE L2 MAC CE
  • an encoder may receive a tier mapping rule and/or sort the multiplexed URLLC data 802 and/or control information 804 into a tier 810 and a tier 814.
  • the tier 810 may be associated with a priority that is higher than a priority associated with the tier 814.
  • the multiplexed URLLC data 802 and/or control information 804 may be associated with a CRC, for example, based on the tiers assigned to the URLLC data 802 and/or the control information 804.
  • the tier 810 may be attached with CRC 812
  • the tier 814 may be attached with CRC 816.
  • the CRC may be attached with some tiers but not others.
  • the tier 810 of higher priority may be assigned CRC 812, and the tier 814 of lower priority may not be assigned a CRC.
  • the tier 810 and the CRC 812 may be processed similarly or in a same way.
  • the tier 814 and the assigned CRC 816, if attached, may be processed similarly or in a same way.
  • the tier 810 with CRC 812 and tier 814 with CRC 816 may be segmented into one or more CBs (e.g., CB 820).
  • the segmentation of the tier 810 with CRC 812 and tier 814 with CRC 816 into one or more CBs may be used when a size of the tier 810 with CRC 812 and/or the size of tier 814 with CRC 816 is above certain threshold (e.g., above a size of a CB).
  • the CB may comprise one or more bits and/or bit channels that are associated with various reliabilities. For example, the bits and/or bit channels may be generated via a coding scheme.
  • the coding scheme may associate the bit channels with different reliabilities.
  • the code scheme may be based on a polar code.
  • polar coding one or more bit channels may provide a high reliability, and one or more bit channels may provide a reliability that is different from the high reliability.
  • a bit mapping rule may be used to map various tiers to different bits and/or bit channels. For example, a tier of a higher priority may be mapped to bits or a bit channel associated with a higher reliability. The tier of higher priority may be mapped to bits or a bit channel(s) based on contiguous, non-contiguous, and/or a hybridization mapping rules (e.g., as discussed herein). As shown in FIG. 8, CB 820 may comprise a bit channel(s) 822 that have been assigned to the tier 810. The CB 820 may comprise a bit channel (s) 824 that have been assigned to the tier 814.
  • the bit channel mapping rule that enables bit channel assignment and control may be signaled and/or received from a network entity such as a gNB.
  • a gNB may perform bit channel assignment and/or may control bit channel mappings.
  • bit channel allocations and mappings at code level of polar codes may be signaled to a WTRU from the gNB.
  • the gNB may inform the WTRU how bit channel mappings are accomplished.
  • Bit channel mappings may be, for example, based on a dynamic allocation or a pre-defined bit channel mapping rule. Mappings may be performed for data, control, CRC, etc.
  • the bit channel mapping rule that enables bit channel assignment and control may be determined by a WTRU or a network entity (e.g. , a base station) based on an indication or a pre- configuration that the WTRU or the network entity received and/or or stored.
  • a WTRU or a network entity e.g. , a base station
  • the bit channel mapping rule may be dynamically signaled to the WTRU via a downlink control information, a PDCCH, and NR-PDCCH, an ePDCCH, and NR-ePDCCH, and/or the like.
  • the bit channel mapping rule applied to CB 820 may differ from the bit channel mapping rule applied to CB 828.
  • the bit channel mapping rule applied to CB 820 may include a contiguous bit channel mapping function where tier 810 may be allocated to the bit channel with the highest reliability and tier 814 may be allocated to other bit channels.
  • the bit channel mapping rule applied to CB 828 may include a non-contiguous bit channel mapping function where tier 810 may be allocated to some or all bit channels with various reliabilities and tier 814 may be allocated to some or all bit channels with various reliabilities.
  • a CB CRC may be allocated and/or attached to one or more of the CBs herein.
  • CB CRC 826 may be attached to the CB 820.
  • Another CB CRC may be attached to the CB 828.
  • One or more bits or bit channels may be allocated and reserved for CRC.
  • a bit channel may not be reserved for a CB CRC, for example, when a CRC is not attached to CB.
  • a number of (e.g., c) bit channels may be reserved for a CB CRC attachment.
  • Various approaches may be used, alone or in combination, to reserve and/or allocate c bit channels for a CB CRC. When a CRC is attached to a CB, and c bit channels are reserved for the CB CRC, the c lowest priority bit channels may be reserved or allocated for CB CRC.
  • bit channels When a CRC is attached to a CB, and c bit channels are reserved for the CB CRC, the c highest priority bit channels may be reserved or allocated for the CB CRC. When a CRC is attached to a CB, and c bit channels are reserved for the CB CRC, c bit channels may be interleaved across some or all bit channels and reserved or allocated for the CB CRC. When a CRC is attached to a CB, and c bit channels are reserved for the CB CRC, c bit channels may be grouped or divided into L bit channel groups and reserved for CB CRC. A bit channel group may have c/L bit channels. Other variants of bit channels allocation and reservation for CB CRC may be implemented.
  • the CBs including the CB 820 and the CB 828 may be encoded via a polar encoder. And a rate matching may be performed.
  • the encoded CBs including the encoded CB 832 may be multiplexed with other types of CBs such as control CB 838.
  • Control information may be encoded via a parallel encoder (e.g., another polar encoder). Sending control information via bits or a bit channel(s) associated with reliabilities that are lower than the reliability associated with URLLC data 802 as described herein may not be sufficient to meet signal integrity requirements.
  • Control information or additional control information may be encoded via a parallel encoder(s) or a parallel control channel(s).
  • the additional control information may be encoded separately and/or in parallel with the URLLC data.
  • the additional control information 834 may be encoded at 836, and segmented into one or more control CBs including the control CB 838.
  • the control CBs including the control CB 838 may be interleaved and/or multiplexed with the encoded CBs including the encoded CB 832 at 840.
  • FIG. 9 is an example of a receiver approach for prioritization of URLLC data multiplexed with control information based on bit channels.
  • FIG. 9 shows a flow 900 for decoding multiplexed information (e.g., URLLC data 602 and control information 604 with the assistance of control information 632).
  • the multiplexed information may be received via one or more symbols.
  • the received multiplexed information may include or comprised in modulation symbols that may be allocated to one or more RBs or REs.
  • de-rate matching may be performed on the multiplexed information.
  • the multiplexed information (e.g., post de-rate matching) may be decoded via a polar decoder.
  • a CB level CRC check may be performed on the multiplexed information. If a CB level CRC check fails, the failed CB may be discarded and/or held for a further retransmission. In an example, if a CB level CRC check fails, the CRC attached to the unsuccessfully decoded CB may be removed at 904, for example to attempt to process a portion of the decoded CB (e.g. , one or more bit channels with higher reliability). The CRCs attached to the successfully decoded CBs that pass the CRC check may be removed at 904.
  • the decoded CBs without the CRC attached may be stored.
  • the decoded CBs may include decoded CB 908, decoded CB 916, and/or decoded CB 918.
  • a decoded CB may comprise one or more bits or bit channels that are associated with tiers of different priorities.
  • the decoded 908 may comprise bits/bit channels 910 allocated to higher priority tiers (e.g. , tier 928) and bits/bit channels 912 allocated to lower priority tiers (e.g. , tier 930).
  • the decoded CBs may be de-mapped to various priority tiers, for example, using a
  • the decoded CBs may be de-mapped to various priority tiers, for example, using a bit channel mapping rule (e.g. , different bit channel may be used for different types/priorities of data in different CBs).
  • the bit channel mapping rule may be received via Layer 1 or L2 (e.g., PHY) as additional control information on multiplexing configuration. For example, if the decoder is at a WTRU for the downlink, the de-mapping rule may be indicated in the downlink assignment.
  • the additional control information may include the number of bits for a tier, the bit channel mapping rule, and/or other control information for a CB (e.g. , CB 908, CB 916, and CB 918).
  • the bit channel mapping rule may be used to de-map various priority tiers from different bits and/or bit channels. For example, a higher priority tier may be de-mapped from bits or a bit channel(s) associated with a higher reliability.
  • CB 908 may comprise a bit channel(s) 910 that have been assigned to the tier 942 and a bit channel(s) 912 that have been assigned to the tier 944.
  • Tier 942 may correspond to URLLC data
  • tier 944 may correspond to control information.
  • the higher priority tier 942 may be de-mapped from the bit channel 910 that is associated with a higher reliability in channel encoding/decoding.
  • one or more of decoded CB 908, decoded CB 916, and/or decoded CB 918 may still include bit channels that do not include an error.
  • the CB CRC failure at 904 may be due to error(s) present in one or more less reliable bit channel(s).
  • the decoded CB may comprise one or more bits or bit channels that are associated with tiers of different priorities and/or reliability levels, it may be that one or more of the relatively higher reliability bit channels could be error-free even when there is an error in a lower reliability bit channel.
  • bit channel 910 may have been correctly received while the error(s) are present in bit channel 912.
  • bit channel 910 may correspond to the data of tier 928.
  • the WTRU may check the tier-level CRC for tier 928, which may pass.
  • the tier-level data 928 may still be processed despite the presence of an error elsewhere in the CB (e.g. , in a different bit channel).
  • data such as URLLC data may still be successfully delivered and processed using a first bit channel (e.g. , a higher reliability bit channel) even when there are errors present on a different bit channel (e.g., a lower reliability bit channel) or otherwise elsewhere in the CB.
  • the de-mapping may be based on contiguous, non-contiguous, and/or a hybridization mapping rules (e.g., as discussed herein).
  • the contiguous bit channel mapping rule 950 the higher reliability bit channel 930 may be used for tier 942, and lower reliability bit channel 932 may be used for tier 944.
  • the non-contiguous bit channel mapping rule 952 a portion 936 of the bit channel 948 may be used for tier 942.
  • a portion 938 of the bit channel 948 may be used for tier 944.
  • data of various tiers with attached tier-level CRC may be collected and/or stored.
  • data in tier 934 may include data collected from the bit channel 910, data collected from the bit channel 954, data collected from the bit channel 920, and/or the like.
  • Data in tier 960 may include data collected from the bit channel 912, data collected from the bit channel 956, data collected from the bit channel 922, and/or the like.
  • a tier-level CRC check may be performed and tier to traffic de-mapping may be performed.
  • the tier to traffic de-mapping may be based on a tier mapping rule.
  • the tier mapping rule may be received via Layer 1 or Layer 2 control as additional control information on multiplexing configuration.
  • the additional control information may include the tier mapping rule, tier size, and/or other information.
  • the tier mapping rule may correspond to different traffic or different types of data to different tiers. Based on the tier mapping rule, the tiers of the traffic may be de-mapped into a first traffic such as URLLC data and a second traffic such as control information.
  • Bit channel mapping and/or priority tier mapping may enable prioritization of L1/L2 control information with or over data.
  • the traffic type 602 if treated with higher priority in the transmitter approach 600, may include the L1/L2 control information.
  • the traffic type 604 in the transmitter approach 600 may include the data.
  • An encoder/decoder may be used in parallel to the polar encoder/decoder used for the prioritization of URLLC data.
  • Some control information/messages may not be sent from higher layers and may be available, for example, when CBs have been generated.
  • the control information/messages may be coded in a parallel chain to priority tiered messages and interleaved (e.g., post coding).
  • the control information/messages may include uplink control information (UCI).
  • UCI may include one or more of rank indicator (RI), pre-coding matrix indicator (PMI), or channel quality indicator (CQI).
  • the UCI may be measured (e.g., immediately) prior to transmission to ensure correlation between channel state information (CSI) and link-dependent communication(s) that depends on the CSI.
  • CSI channel state information
  • a control channel parallel to the control channel for the prioritization of the URLLC data may be used.
  • the parallel control channel may be used for prioritizing the control information/messages and/or allocating high priority messages to high quality bit channels.
  • the control information/messages may be prioritized over low requirement data.
  • a separate polar encoder may be used to enable or support the parallel control channel.
  • downlink messages in LTE
  • a PDCCH may be used to recover downlink signals and/or to configure uplink resources for a WTRU.
  • Message fields such as transmit power control (TPC), RB allocation, and/or MCS may be used for data reception and/or network configuration.
  • Control information e.g. , downlink messages in a PDCCH
  • the control information may be treated or used as high priority control information.
  • the high priority control information may be mapped, for example, to the highest priority tier (e.g. , as shown by an example in FIG. 10).
  • Low priority messages may be, for example, assigned to lower priority tiers and mapped to lower quality bit channel tiers.
  • FIG. 10 is an example of an architecture 1000 using polar coding bit channels for low requirement data multiplexed with high priority L1/L2 control information.
  • data 1002 and L1/L2 control information 1004 may be received, for example, at an encoder.
  • the data 1002 and/or the L1/L2 control information 1004 may be multiplexed at 1006.
  • the multiplexed data 1002 and/or the L1/L2 control information 1004 may be sorted into various tiers that are associated with different priorities.
  • the multiplexed data 1002 and/or the L1/L2 control information 1004 may be associated with a CRC, for example, based on the tiers assigned to the data 1002 and/or the L1/L2 control information 1004. For example, as shown in FIG.
  • an encoder may receive a tier mapping rule and/or sort the multiplexed data 1002 and/or the L1/L2 control information 1004 into a tier 1010 and a tier 1014.
  • the tier 1010 may be associated with a priority that is higher than a priority associated with the tier 1014.
  • the multiplexed data 1002 and/or control information 1004 may be associated with a CRC, for example, based on the tiers assigned to the data 1002 and/or the L1/L2 control information 1004.
  • the tier 1010 may be assigned CRC 1012
  • the tier 1014 may be assigned CRC 1016.
  • the CRC may be attached to some tiers but not for others.
  • the tier 1010 with CRC 1012 and tier 1014 with CRC 1016 may be segmented into one or more CBs (e.g. , CB 1032).
  • a bit mapping rule may be used to map various tiers to different bits and/or bit channels. For example, a tier of a higher priority may be mapped to bits or a bit channel associated with a higher reliability. The tier of higher priority may be mapped to bits or a bit channel(s) based on contiguous, non-contiguous, and/or a hybridization mapping rules (e.g. , as discussed herein). As shown in FIG.
  • CB 1032 may comprise a bit channel(s) 1020 that have been assigned to the tier 1010.
  • the CB 1032 may comprise a bit channel(s) 1024 that have been assigned to the tier 1014.
  • a CB CRC may be allocated and/or attached to one or more of the CBs herein.
  • a CB CRC 1022 may be allocated and/or attached to CB 1032.
  • the CBs including the CB 1032 may be encoded via a polar encoder. And a rate matching may be performed.
  • the encoded CBs including the encoded CB 1028 may be multiplexed at 1030.
  • L1/L2 control information may be encoded separately, for example, using polar codes in parallel with data encoding.
  • DCI carried by PDCCH or the like may be encoded using polar codes or convolutional codes in parallel to URLLC data encoding.
  • L1/L2 control information may be encoded jointly with data using polar codes.
  • UCI such as RI, PMI, CQI, etc., may be jointly encoded with data using a polar code.
  • a composition of a resource block(s) may be indicated, for example, to a decoder via signaling.
  • the decoder may include a WTRU or a BS.
  • the signaling of the composition of a resource block(s) may be used for recovery of priority tiers and control fields.
  • Signaling for some or all information (e.g., for the composition of resource blocks) may be established in a data frame structure.
  • Information such as a bit mapping function, may (e.g. , additionally or alternatively) be indicated, for example, in a DCI-like structure or via RRC signaling.
  • the number of bits used for data may be greater than the number of bits used for control information.
  • Some or all CBs (e.g., the first CB) may include a mixture of bits used for data and control information.
  • Some or all CBs may include bits used for data.
  • a URLLC with a relatively small payload size may include a (e.g. , one) CB.
  • the CB may accommodate both data and control.
  • Bit channel mapping and/or priority tier mapping may enable prioritization of higher layer control information with or over data.
  • An encoder/decoder may be used in parallel to the polar encoder/decoder used for the prioritization of URLLC data and/or the polar encoder used for the prioritization of L1/L2 control information.
  • Higher layer control information such as handover commands or radio resource management (RRM) signaling may be multiplexed with data messages (e.g., in addition to control messages from layers 1 and 2). Data and control messages arriving from separate logical channels may be multiplexed into a common data frame.
  • the high layer control information such as RRM signaling may occur infrequently or aperiodically. Scheduling of the high layer control information may be used through separate channels.
  • the high layer control information such as RRM signaling may be prioritized over data, for example, to reduce redundant transmission of information that may be used for a proper network operation.
  • FIG. 11 is an example format 1100 of using polar coding bit channels for low requirement data multiplexed with high priority higher layer control data.
  • data 1102 and higher layer control information 1104 may be received, for example, at an encoder.
  • the traffic type 602 if treated with higher priority in the transmitter approach 600, may include the higher layer control information.
  • the traffic type 604 in the transmitter approach 600 may include the data.
  • the data 1102 and/or the higher layer control information 1104 may be multiplexed at 1106.
  • the multiplexed data 1102 and/ the higher layer control information 1104 may be sorted into various tiers that are associated with different priorities.
  • the multiplexed data 1102 and/or the higher layer control information 1104 may be associated with a CRC, for example, based on the tiers assigned to the data 1102 and/or the higher layer control information 1104.
  • an encoder may receive a tier mapping rule and/or sort the multiplexed the data 1102 and/or the higher layer control information 1104 into a tier 1110 and a tier 1114.
  • the tier 1110 may be associated with a priority that is higher than a priority associated with the tier 1114.
  • the multiplexed data 1102 and/or the higher layer control information 1104 may be associated with a CRC, for example, based on the tiers assigned to the data 1102 and/or the higher layer control information 1104.
  • the tier 1110 may be assigned CRC 1112
  • the tier 1114 may be assigned CRC 1116.
  • the CRC may be attached to some tiers but not for others.
  • the 11021104 tier 1110 with CRC 1112 and tier 1114 with CRC 1116 may be segmented into one or more CBs (e.g., CB 1138).
  • a bit mapping rule may be used to map various tiers to different bits and/or bit channels. For example, a tier of a higher priority may be mapped to bits or a bit channel associated with a higher reliability. The tier of higher priority may be mapped to bits or a bit channel(s) based on contiguous, non-contiguous, and/or a hybridization mapping rules (e.g. , as discussed herein). As shown in FIG.
  • CB 1138 may comprise a bit channel(s) 1120 that have been assigned to the tier 1110.
  • the CB 1138 may comprise a bit channel(s) 1122 that have been assigned to the tier 1114.
  • a CB CRC may be allocated and/or attached to one or more of the CBs herein.
  • a CB CRC 1124 may be allocated and/or attached to CB 1138.
  • the CBs including the CB 1138 may be encoded via a polar encoder. And a rate matching may be performed.
  • the encoded CBs including the encoded CB 1134 may be multiplexed at 1136.
  • lower layer control information 1128 may be encoded at 1130, and segmented into one or more control CBs including the control CB 1132.
  • the control CBs including the control CB 1132 may be interleaved and/or multiplexed with the encoded CBs including the encoded CB 1134 at 1136.
  • Resources that may be used for layer 1 and 2 control may not be available, for example, when bit channels are reserved for higher layer control messaging.
  • Layer 1 and 2 control may be encoded via a separate encoder and interleaved with advanced coding blocks prior to transmission.
  • a WTRU may refer to an identity of the physical device, or to the user's identity such as subscription related identities, e.g., MSISDN, SIP URI, etc.
  • WTRU may refer to application- based identities, e.g., user names that may be used per application.
  • the processes described above may be implemented in a computer program, software, and/or firmware incorporated in a computer-readable medium for execution by a computer and/or processor.
  • Examples of computer-readable media include, but are not limited to, electronic signals (transmitted over wired and/or wireless connections) and/or computer-readable storage media.
  • Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and/or optical media such as CD-ROM disks, and/or digital versatile disks (DVDs).
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and/or any host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Probability & Statistics with Applications (AREA)
  • Theoretical Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des systèmes, des procédures et des instruments pour effectuer des communications de données à faible latence, au moyen d'un codage avancé par l'intermédiaire de codes polaires. Un codeur peut recevoir un trafic de données qui comprend différents types de trafics tels que des données URLLC et des informations de commande. Le codeur peut trier les différents types de trafics en plusieurs niveaux de priorités différentes. Le codeur peut faire correspondre des données comprises dans les niveaux à une pluralité de canaux binaires présentant différentes fiabilités de codage de canal. Le codeur peut recevoir une règle de mappage de canaux de bits indiquant qu'un niveau supérieur correspond à une fiabilité de codage de canal supérieure. Le codeur peut recevoir de manière dynamique la règle de mappage de canaux binaires de telle sorte que le mappage de niveaux de priorité sur des canaux binaires diffère d'un bloc de code à un autre bloc de code.
PCT/US2017/040757 2016-07-05 2017-07-05 Communications de données à faible latence utilisant un codage avancé WO2018009572A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201662358426P 2016-07-05 2016-07-05
US62/358,426 2016-07-05

Publications (1)

Publication Number Publication Date
WO2018009572A1 true WO2018009572A1 (fr) 2018-01-11

Family

ID=59366519

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/040757 WO2018009572A1 (fr) 2016-07-05 2017-07-05 Communications de données à faible latence utilisant un codage avancé

Country Status (1)

Country Link
WO (1) WO2018009572A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10582507B2 (en) 2018-05-17 2020-03-03 At&T Intellectual Property I, L.P. Network coding for bandwidth efficient reliability improvement for URLLC service
US11251908B2 (en) 2017-01-06 2022-02-15 Idac Holdings, Inc. Advanced coding on retransmission of data and control
WO2022089002A1 (fr) * 2020-10-30 2022-05-05 中兴通讯股份有限公司 Procédé et appareil de communication à faible latence à liaisons multiples, et support de stockage et appareil électronique
US11705982B2 (en) 2018-01-23 2023-07-18 Qualcomm Incorporated Methods and apparatus for adjusting wireless communication structure
EP4131810A4 (fr) * 2020-03-23 2023-12-27 Sony Group Corporation Dispositif de communication, et procédé de communication

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Multiplexing and channel coding (FDD) (Release 13)", 3GPP STANDARD; 3GPP TS 25.212, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG6, no. V13.1.0, 30 June 2016 (2016-06-30), pages 1 - 169, XP051295284 *
DU WEI ET AL: "Exploiting the UEP property of polar codes to reduce image distortions induced by transmission errors", 2015 IEEE/CIC INTERNATIONAL CONFERENCE ON COMMUNICATIONS IN CHINA (ICCC), IEEE, 2 November 2015 (2015-11-02), pages 1 - 5, XP032889172, DOI: 10.1109/ICCCHINA.2015.7448741 *
GUO JIANFENG ET AL: "Multi-CRC Polar Codes and Their Applications", IEEE COMMUNICATIONS LETTERS, IEEE SERVICE CENTER, PISCATAWAY, NJ, US, vol. 20, no. 2, 1 February 2016 (2016-02-01), pages 212 - 215, XP011598246, ISSN: 1089-7798, [retrieved on 20160208], DOI: 10.1109/LCOMM.2015.2508022 *
INTERDIGITAL COMMUNICATIONS ET AL: "Transport block to codeword to layer mapping", 3GPP DRAFT; R1-114173, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. San Francisco, CA, USA; 20111114 - 20111119, 9 November 2011 (2011-11-09), XP050562302 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11251908B2 (en) 2017-01-06 2022-02-15 Idac Holdings, Inc. Advanced coding on retransmission of data and control
US11705982B2 (en) 2018-01-23 2023-07-18 Qualcomm Incorporated Methods and apparatus for adjusting wireless communication structure
US10582507B2 (en) 2018-05-17 2020-03-03 At&T Intellectual Property I, L.P. Network coding for bandwidth efficient reliability improvement for URLLC service
US11297624B2 (en) 2018-05-17 2022-04-05 At&T Intellectual Property I, L.P. Network coding for bandwidth efficient reliability improvement for URLLC service
EP4131810A4 (fr) * 2020-03-23 2023-12-27 Sony Group Corporation Dispositif de communication, et procédé de communication
WO2022089002A1 (fr) * 2020-10-30 2022-05-05 中兴通讯股份有限公司 Procédé et appareil de communication à faible latence à liaisons multiples, et support de stockage et appareil électronique

Similar Documents

Publication Publication Date Title
US10868657B2 (en) Wireless network configured to provide mixed services
US11888612B2 (en) Methods for enhanced multiplexing in wireless systems
US11277823B2 (en) Method and apparatus for reporting feedback information for multi-carrier operation
US20210384922A1 (en) Method and apparatus for low-density parity-check (ldpc) coding
CN109155682B (zh) 关于5g系统内的不同类型业务量的phy层复用
WO2018231400A1 (fr) Facilitation de notifications pour indiquer des groupes de blocs de code défaillants dans des réseaux 5g ou d'autres réseaux de prochaine génération
US11251908B2 (en) Advanced coding on retransmission of data and control
WO2018009572A1 (fr) Communications de données à faible latence utilisant un codage avancé
US11711185B2 (en) Method and device in communication node for wireless communication
US11711164B2 (en) Method and device in UE and base station used for channel coding
WO2019160768A1 (fr) Réduction du surdébit de canal de commande dans des réseaux 5g ou dans d'autres réseaux de prochaines générations
JP6952166B2 (ja) 装置、方法、及び集積回路
CN114765746A (zh) 一种用于无线通信的节点中的方法和装置
CN117083908A (zh) 基站、终端及通信方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17740855

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17740855

Country of ref document: EP

Kind code of ref document: A1