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/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/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
  • H04L1/0006—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format
  • H04L1/0007—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format by modifying the frame length
• • 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/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
  • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
  • H04L1/0025—Transmission of mode-switching indication
• • 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/12—Arrangements for detecting or preventing errors in the information received by using return channel
  • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
  • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
  • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
• • 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/12—Arrangements for detecting or preventing errors in the information received by using return channel
  • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
  • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
  • H04L1/1867—Arrangements specially adapted for the transmitter end
  • H04L1/1887—Scheduling and prioritising arrangements
• • 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/20—Arrangements for detecting or preventing errors in the information received using signal quality detector
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04B—TRANSMISSION
  • H04B17/00—Monitoring; Testing
  • H04B17/30—Monitoring; Testing of propagation channels
  • H04B17/309—Measuring or estimating channel quality parameters
  • H04B17/345—Interference values
• • 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

• ARQ Automatic Repeat Request
• HARQ Hybrid ARQ
• HARQ paired with multiple stop-and-wait transmission protocol, is a powerful error correction mechanism that does not throttle throughput as opposed to single stop-and-wait protocol.
• a method performed by a wireless transmit/receive (WTRU) unit may compromise: receiving, from a base station, a first downlink control information (DCI) indicating a first code block group (CBG) size; receiving, from the base station, a transport block (TB) that includes one or more CBGs, wherein the one or more CBGs include one or more code blocks (CBs); performing a cyclic redundancy check (CRC) on the received TB; transmitting, to the base station, feedback based on the CRC; and receiving, from the base station, a second DCI indicating a second CBG size, wherein the second CBG size is based on the transmitted feedback.
• DCI downlink control information
• CBG code block group
• CBs code blocks
• CRC cyclic redundancy check
• the feedback may be an acknowledgement (ACK) or a negative acknowledgement (NACK). If the feedback is an ACK, the second CBG size may be larger than the first CBG size. If the feedback is a NACK, the second CBG size may be smaller than the first CBG size.
• ACK acknowledgement
• NACK negative acknowledgement
• a method performed by a base station may compromise: detecting an interference pattern; determining that the interference pattern impacts one or more code CBs within one or more CBGs; adjusting a size of the one or more CBGs; and transmitting, to a WTRU, information associated with the adjusting of the size of the one or more CBGs.
• the interference pattern may be caused by a radio detection and ranging (RADAR) system.
• the adjusting of the size of the one or more CBGs may compromise increasing the number of CBs within the one or more CBGs.
• the adjusting of the size of the one or more CBGs may compromise decreasing the number of CBs within the one or more CBGs.
• the interference pattern may impact the same CB instance in each CBG.
• the base station may detect the interference pattern based on feedback from one or more WTRUs.
• the transmitting of the information relating to the adjusting of the size of the one or more CBGs may be performed via master information block (MIB) signaling.
• the transmitting of the information relating to the adjusting of the size of the one or more CBGs may be performed via radio resource control (RRC) signaling.
• the RRC signaling may include information indicating a CBG sizing duration.
• the transmitting of the information relating to the adjusting of the size of the one or more CBGs may be performed via downlink control information (DCI) signaling.
• DCI downlink control information
• FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented
• FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;
• WTRU wireless transmit/receive unit
• FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;
• RAN radio access network
• CN core network
• FIG. 1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment
• FIG. 2 is a diagram illustrating an example downlink retransmission of CBGs
• FIG. 3 is a diagram illustrating an example PUSCH HARQ feedback timing
• FIG. 4 is a diagram illustrating an example PDSCH HARQ feedback timing
• FIG. 5 is a diagram illustrating an example dynamic code block regrouping used to adjust the size of the transmitted CBGs based on the presence of interference
• FIG. 6 is a diagram illustrating an example dynamic code block regrouping used to adjust the size of the transmitted CBGs based on the presence of interference
• FIG. 7 is a diagram illustrating an example code block segmentation, filler insertion, CRC insertion and CB grouping
• FIG. 8 is a diagram illustrating an example process of CBG sizing according to an embodiment
• FIG. 9 is a diagram illustrating an example of an RRC configured CBG sizing
• FIG. 10 is a diagram illustrating an example of when interleaving is applied and all CBGs will need to be retransmitted.
• FIG. 11 is a diagram illustrating an example of when interleaving is applied and CBG #1 and CBG #3 are error free and will not need to be re-transmitted;
• FIG. 12 is a diagram illustrating an example process of CBG sizing according to an embodiment.
• FIG. 1A is a diagram illustrating 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 systems 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), singlecarrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S- OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
• CDMA code division multiple access
• TDMA time division multiple access
• FDMA frequency division multiple access
• OFDMA orthogonal FDMA
• SC-FDMA singlecarrier FDMA
• ZT-UW-DFT-S- OFDM zero-tail unique-word discrete Fourier transform Spread OFDM
• UW-OFDM unique word OFDM
• FBMC filter bank multicarrier
• the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (ON) 106, 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 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 a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
• UE user equipment
• PDA personal digital assistant
• HMD head-mounted display
• a vehicle a drone
• the communications systems 100 may also include a base station 114a and/or a base station 114b.
• Each of the base stations 114a, 114b may be any type of device configured to 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 CN 106, the Internet 110, and/or the other networks 112.
• the base stations 114a, 114b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, 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 104, 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, and the like.
• 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 on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum.
• a cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. 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, i.e., one for each sector of the cell.
• the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
• MIMO multiple-input multiple output
• beamforming may be used to transmit and/or receive signals in desired spatial directions.
• the base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.).
• the air interface 116 may be established using any suitable radio access technology (RAT).
• 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 104 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 116 using wideband CDMA (WCDMA).
• WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or Evolved HSPA (HSPA+).
• HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and/or High-Speed Uplink (UL) Packet Access (HSUPA).
• the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
• E-UTRA Evolved UMTS Terrestrial Radio Access
• LTE Long Term Evolution
• LTE-A LTE-Advanced
• LTE-A Pro LTE-Advanced Pro
• the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using NR.
• the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
• the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
• DC dual connectivity
• the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).
• the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, 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.11 i.e., Wireless Fidelity (WiFi)
• IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
• CDMA2000, CDMA2000 1X, CDMA2000 EV-DO Code Division Multiple Access 2000
• IS-95 Interim Standard 95
• IS-856 Interim Standard 856
• GSM Global System for
• 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, LTE-A Pro, NR etc.) to establish a picocell or femtocell.
• a cellular-based RAT e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR 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 ON 106.
• the RAN 104 may be in communication with the ON 106, 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 data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
• QoS quality of service
• the ON 106 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.
• the RAN 104 and/or the ON 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT.
• the ON 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
• the CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the 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/or the internet protocol (IP) in the TCP/IP internet protocol suite.
• the networks 112 may include wired and/or wireless communications networks owned and/or operated by other service providers.
• the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 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. 1 A may be configured to communicate with the base station 114a, which may employ a cellularbased radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
• FIG. 1B is a system diagram illustrating 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/or other peripherals 138, among others.
• GPS global positioning system
• 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, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like.
• the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
• the processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 1B 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 116.
• 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/or 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 one embodiment, 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 116.
• 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. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR 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 116 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 method 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 and/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, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
• FM frequency modulated
• the peripherals 138 may include one or more sensors.
• the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor and the like.
• the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and DL (e.g., for reception) may be concurrent and/or simultaneous.
• the full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118).
• the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)).
• a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the DL (e.g., for reception)).
• FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 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 116.
• the RAN 104 may also be in communication with the CN 106.
• 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/or 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 UL and/or DL, and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
• the CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
• MME mobility management entity
• SGW serving gateway
• PGW packet data network gateway
• PGW packet data network gateway
• the MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node.
• the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation/deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like.
• the MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and/or WCDMA.
• the SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface.
• the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
• the SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
• the SGW 164 may be connected to the PGW 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.
• packet-switched networks such as the Internet 110
• the CN 106 may facilitate communications with other networks.
• the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
• the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
• IMS IP multimedia subsystem
• the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
• the WTRU is described in FIGS. 1A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.
• the other network 112 may be a WLAN.
• a WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP.
• the AP may have access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
• Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
• Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
• Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
• the traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic.
• the peer-to- peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
• the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS).
• a WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
• the IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.
• the AP may transmit a beacon on a fixed channel, such as a primary channel.
• the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width.
• the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
• Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in 802.11 systems.
• the STAs e.g., every STA, including the AP, may sense the primary channel. If the primary channel is sensed/detected and/or determined to be busy by a particular STA, the particular STA may back off.
• One STA (e.g., only one station) may transmit at any given time in a given BSS.
• High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
• VHT STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels.
• the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
• a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two noncontiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
• the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
• Inverse Fast Fourier Transform (IFFT) processing, and time domain processing may be done on each stream separately.
• IFFT Inverse Fast Fourier Transform
• the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
• the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
• MAC Medium Access Control
• Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah.
• the channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and 802.11 ac.
• 802.11 af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
• 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum.
• 802.11 ah may support Meter Type Control/Machine- Type Communications (MTC), such as MTC devices in a macro coverage area.
• MTC Meter Type Control/Machine- Type Communications
• MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
• the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
• WLAN systems which may support multiple channels, and channel bandwidths, such as 802.11 n, 802.11 ac, 802.11af, and 802.11 ah, include a channel which may be designated as the primary channel.
• the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
• the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode.
• the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.
• Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.
• STAs e.g., MTC type devices
• NAV Network Allocation Vector
• the available frequency bands which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.
• FIG. 1 D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
• the RAN 104 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
• the RAN 104 may also be in communication with the CN 106.
• the RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment.
• the gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
• the gNBs 180a, 180b, 180c may implement MIMO technology.
• gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
• the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
• the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
• the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum.
• the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
• WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
• CoMP Coordinated Multi-Point
• the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
• the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a varying number of OFDM symbols and/or lasting varying lengths of absolute time).
• TTIs subframe or transmission time intervals
• the gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and/or a non-standalone configuration.
• WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c).
• WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
• WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
• WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
• WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
• eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
• Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
• UPF User Plane Function
• AMF Access and Mobility Management Function
• the CN 106 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
• SMF Session Management Function
• the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may serve as a control node.
• the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of non-access stratum (NAS) signaling, mobility management, and the like.
• PDU protocol data unit
• Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
• different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and the like.
• URLLC ultra-reliable low latency
• eMBB enhanced massive mobile broadband
• the AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
• radio technologies such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
• the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N11 interface.
• the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 via an N4 interface.
• the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
• the SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, and the like.
• a PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.
• the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, 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 UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and the like.
• the CN 106 may facilitate communications with other networks.
• the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
• IMS IP multimedia subsystem
• the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
• the WTRUs 102a, 102b, 102c may be connected to a local DN 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
• one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown).
• the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
• the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
• the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
• the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
• the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
• the emulation device may be directly coupled to another device for purposes of testing and/or performing testing using over-the-air wireless communications.
• the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
• the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
• the one or more emulation devices may be test equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
• RF circuitry e.g., which may include one or more antennas
• ARQ Automatic Repeat Request
• HARQ Hybrid ARQ
• HARQ paired with multiple stop-and-wait transmission protocol, is a powerful error correction mechanism that does not throttle throughput as opposed to single stop-and-wait protocol.
• chase combining identical replicas of transmitted data bits are sent.
• incremental redundancy combinations of the systematic bits and the parity bits are sent.
• the first transmission may include all the systematic bits.
• 5G incremental redundancy is used by default with order of redundancy versions set as 0, 1, 2, 3.
• Large transport blocks may be appended with CRC and segmented into multiple code blocks (CBs), each appended with its own CRC bits and then grouped into code block groups of two, four, six, or eight CBGs.
• the number of code blocks in a CBG may depend on the number of CBs in the initial transmission.
• the size of the CBG is determined by RRC messages.
• NDI New Data Indicator
• DCI is used to indicate whether new data is being transmitted in the uplink or the downlink. This field has a single bit and works in a toggled mode (i.e., toggling indicates new data transmission). Unlike in the downlink, there is no explicit ACK or NACK in the uplink.
• FIG. 2 illustrates an example downlink retransmission of CBGs.
• the transport block 202 includes four CBGs — CBG #1 210, CBG #2 212, CBG #3 214, and CBG #4 216.
• Each CBG includes two code blocks.
• CBG #1 210 includes CB #1 221 and CB #2 222
• CBG #2 212 includes CB #3 223 and CB #4 224
• CBG #3 214 includes CB #5 225 and CB #6 226,
• CBG #4 216 includes CB #7 227 and CB #8 228.
• CB #1 221 and CB #5 225 experience interference. The interference may be caused by RADAR.
• the WTRU 204 After the WTRU 204 receives the transport block 202 from the transmitter 206, it sends a NACK 230 to the transmitter 206 because CB #1 221 and CB #5 225 were interfered with. Accordingly, transmitter 206 retransmits CBG #1 210 and CBG #3 214 to the WTRU 204.
• CBGTI Code Block Group Transmit Indicator
• CBGFI Code Block Group Flush Indicator
• CBGTI is a bitmap that indicates which CBG is being (re) transmitted in the downlink.
• the CBGFI may be indicated by a single bit, where “1” may indicate a flush command and “0” may indicate that soft combing should be done.
• HARQ ACK and NACK can be multiplexed with SR or CRI over PUCCH or with data over PUSCH.
• HARQ timing may be indicated by a three-bit field in DCI and may represent the ACK timing in the uplink relative to PDSCH reception.
• HARQ timing may point to a value in a RRC configured table.
• RRC parameter K0 may indicate the slot offset in which downlink data scheduled. It may range from 0 to 32 slots.
• the WTRU send UL acknowledgement after K1 slot offset.
• the range of K1 is 0 to 15 slots and depends on the WTRU capability. This WTRU capability is given as N1 which consists of PDSCH decoding delay and on the DMRS configuration as indicated in Table 1 and Table 2 below.
• T able 1 PDSCH Processing Time for PDSCH Processing Capability 1
• Parameter K2 may be the slot offset required from uplink grant to downlink retransmission.
• the offset may also depend on the WTRU capability indicated as N2 which corresponds to the PUSCH preparation time.
• the offset may range from 0 to 32 slots.
• Table 3 below represents values of N2 for PUSCH preparation time for PUSCH timing capability 1.
• Table 4 below represents values of N2 for PUSCH preparation time for PUSCH timing capability 2.
• FIG. 3 illustrates an example of PUSCH HARQ feedback timing.
• base station 302 transmits, to a WTRU 304, a UL DCI for UL data scheduling.
• the UL DCI may indicate that a new UL transmission is granted after K2 slots, where K2 is the offset between the DL slot in which the DCI is received and the UL slot in which the UL data is scheduled to be transmitted via a PUSCH.
• K2 is the offset between the DL slot in which the DCI is received and the UL slot in which the UL data is scheduled to be transmitted via a PUSCH.
• UL data is transmitted by the WTRU 304 to the base station 302 via a PUSCH.
• the base station 302 may transmit, to the WTRU 304, another UL grant for UL data retransmission with New Data Indicator (NDI) bit not toggled and a new K2 value. The same procedure may followed for all subsequent (re)transmissions.
• NDI New Data Indicator
• FIG. 4 illustrates an example PDSCH HARQ feedback timing.
• base station 402 transmits, to WTRU 404, a DL DCI for DL data scheduling.
• the DL DCI may indicate that a new DL transmission is granted after K0 slot, where K0 is the offset between the DL slot in which the DCI for DL scheduling is received and the slot in which the DL data is scheduled to be transmitted via PDSCH.
• the DCI may also indicates K1 value, which may be the offset between the DL slot in where DL data is scheduled and the UL slot in which corresponding ACK/NACK feedback is expected to be sent.
• the DL data is received by the WTRU 404 via PDSCH.
• the WTRU 404 may transmit a NACK after K1 slots indicating unsuccessful decoding.
• the base station 404 may then transmit another DL DCI for DL data retransmission with NDI bit not toggled and indicate a new K0 value. The same procedure may be followed for all (re)transmissions.
• HARQ multiplexing may use multi-bit HARQ feedback message to ACK/NACK multiple transport blocks.
• the base station may communicate to a WTRU regarding which approach to use via RRC configuration messages.
• Semi-static codebook is a matrix that maps time instances with component carriers/CBGs/MIMO layers. A semi-static approach may not be optimal for large number of carrier components because large HARQ reports will need to be transmitted.
• Dynamic codebook resolves the large report issue as the size of the codebook is dynamically changed.
• the key idea is that it eliminates the carriers that are not scheduled (i.e., ACK/NACKs feedback is transmitted only for the scheduled carriers) and uses a special indexing technique to keep track of which feedback is for which carrier. This is handled via downlink assignment index (DAI) reported in the downlink assignment DCI.
• DAI downlink assignment index
• the DAI field has two indices, a counter DAI (cDAI) and a total DAI (tDAI) used for carrier aggregation.
• the cDAI index indicates the number of DL transmissions up to the time of DCI reception. This indexing happen at the carrier level first and then on the temporal level.
• the tDAI indicates the total number of DL transmissions on all carriers up to the time of the DCI reception.
• the number of CBs within a CBG may depend on the initial transmission. Once this number is fixed in the initial transmission, the base station will use the same number for all subsequent retransmissions.
• a periodic interferer such as the RADAR, may impact a single CB within the CBG.
• the base station may retransmit the entire CBG, potentially wasting valuable resources.
• smaller CBGs may result in frequent HARQ feedback, leading to inefficiency.
• the base station may detect identify and analyze an interference pattern and may inform a WTRU of a corresponding HARQ approach as described below .
• the transmitter may statically, semi-dynamically, or dynamically change the size of the code block group to either reduce the amount of unnecessary data transmissions or reduce the amount of ACK/NACK feedback.
• the network may choose to reduce its CBG size to avoid unnecessarily large retransmissions or increase it to avoid frequent HARQ feedback.
• Another embodiment may be based on the ability of the base station to recognize patterns of the interferer.
• This embodiment may utilize CB and/or CBG interleaving techniques to transmit CBGs during interference silence periods. These techniques optimally re-arrange CBs and/or CBGs within a transport block to minimize the impact of interference on transmitted CBGs.
• the network may change the size of the CBGs based on knowledge of the interference presence and the interference pattern.
• an interferer e.g., RADAR
• the network may reduce the size of the CBG such that it contains only the blocks impacted by interference.
• FIG. 5 is a diagram illustrating an example dynamic code block regrouping used to adjust the size of the transmitted CBGs based on the presence of an interference pattern (e.g. RADAR).
• the transport block 502a prior to resizing, the transport block 502a includes two CBGs - CBG #1 504 and CBG #2 506.
• CBG #1 504 and CBG #2 506 each contain four CBs before CBG sizing.
• CBG #1 504 includes CB #1 521 , CB #2, 522, CB #3 523, and CB #4 424.
• CBG #2 includes CB #5 525, CB #6 526, CB #7 527, and CB #8 528.
• the periodic signal is interfering with CB #1 421 and CB #5 525.
• CB #1 421 and CB #5 525 Prior to resizing, retransmission of the entire CBG is inefficient and a waste of valuable resources that may be avoided by reducing the size of the CBGs to one CB (i.e., no grouping).
• CBG resizing allows the network to save on the amount of transmitted data by reducing the amount of unnecessary CB retransmissions, thus improving delay and throughput.
• one way to design the transport block 502b may be to resize each CBG to include only one CB.
• transport block 502b includes eight CBGs - CBG #1 511, CBG #2 512, CBG #3 513, CBG #4 514, CBG #5 515, CBG #6 516, CBG #7 517, and CBG #8 518.
• Each CBG includes one CB.
• each CBG includes only one CB, only CBG #1 511 and CBG #5 515 need to be retransmitted. Conversely, when the interferer is absent, the network may choose to transmit larger CBGs to save on uplink signaling.
• the periodic signal may interfere with the same CB instance in each CBG.
• the periodic signal may interfere with the first CB (i.e., CB #1 521 and CB #5 525) in each of the two CBGs (i.e., CBG #1 504 and CBG #2 506).
• FIG. 6 illustrates another example of dynamic code block regrouping used to adjust the size of the transmitted CBGs based on the presence of interference.
• the network may increase the size of the CBG such that all impacted CBs are contained within one CBG.
• transport block 602a prior to dynamic CBG sizing, transport block 602a includes eight total CBGs - CBG #1 611, CBG #2 612, CBG #3 613, CBG #4 614, CBG #5 615, CBG #6 616, CBG #7 617, and CBG #8 618.
• each CBG includes only one CB.
• CBG #1 611 includes CB #1 621
• CBG #2 612 includes CB #2 622
• CBG #3 613 includes CB #3 623
• CBG #4 614 includes CB #4 624
• CBG #5 615 includes CB #5 625
• CBG #6 616 includes CB #6 626
• CBG #7 617 includes CB #7 627
• CBG #8 618 includes CB #8 628.
• interference e.g., RADAR
• the transport block 602b includes four CBGs - CBG #1 631 , CBG #2 632, CBG #3633, and CBG #4634.
• the four impacted CBs are grouped together in two separate CBGs.
• CBG #1 includes CB #1 611 and CB #2 612
• CBG #3 633 includes CB #5 615 and CB #6 626. Grouping the CBs into CBGs of size two allows savings in uplink ACK/NACKs, thus improving uplink metrics.
• CBG sizing may result in the last CBG having less CBs compared to previous CBGs of the same TB. However, as shown in FIG. 7, this can be resolved by inserting filler CBs either at the start or the end of the transport block.
• FIG. 7 is a diagram illustrating an example code block segmentation, filler insertion, CRC insertion and CB grouping.
• the network segments the CBs in transport block 702.
• the network inserts biller bits into the last CB 720.
• CRC bits are added to each CB, including the CB 720.
• the CBs are grouped.
• FIG. 8. illustrates an example process 800 for CBG sizing.
• the base station may detect an interference pattern.
• the interference pattern may be caused by RADAR.
• the base station may determine that the interference pattern impacts one or more CBs that are within one or more CBGs. For example, as shown in FIG. 5. in a situation where there are two CBGs (each with four CBs), each of the two CBGs may have one CB that is impacted by interference. In another example, as shown in FIG. 6, there may be eight CBGs (each with one CB), where four CBs are impacted by interference.
• the base station may adjust the size of the one or more CBGs.
• the adjustment may involve decreasing the size of each CBG (as shown in FIG. 5). In another embodiment, the adjustment may involve increasing the size of each CGB (as shown in FIG. 6).
• the base station may transmit, to the WTRU, information associated with the adjustment of the one or more CBGs.
• the network may indicate a change in CBG sizing to the WTRU either statically, semi-dynamically, or dynamically.
• the network may communicate whether it uses static CBG sizing or not to emerging UEs via MIB message.
• the network may utilize the spare bit in MIB message to indicate whether it uses CBG sizing or not to emerging UEs.
• This spare bit may be referred to as “staticCbgSizing”.
• a bit value set to “0” may indicates legacy CBG behavior (i.e., the number of CBs depend on the initial transmission).
• a bit value set to “1” may indicate a one CB per CBG HARQ configuration.
• connected WTRUs may continue to use legacy CBG sizing unless a new MIB is received.
• emerging WTRUs may assume that an interferer is present and that all transmitted CBGs consist of only one CB. The emerging WTRUs may continue to use this assumption as long as they are connected to the network and until a new MIB with staticCbgSizing set to “0” is received.
• the network may utilize the spare bit in MIB to indicate whether it uses static CBG sizing. For example, as described above, a bit value of “0” may indicate legacy CBG behavior while a bit value of “1” may indicate one code block per code block group. This approach may be utilized when a short pulse interference signal is present that may impact a single CB (e.g., RADAR signal).
• the MIB message below may be used by the network to communicate to emerging WTRUs as to whether it uses static CBG sizing.
• MIB : SEQUENCE ⁇ systemFrameNumber BIT STRING (SIZE (6) ) , subcarri erspaci ngcommon ENUMERATED ⁇ scsl5or60 , scs30orl20 ⁇ , ssb-subcar ri eroffset INTEGER (0. . 15) , dmrs-TypeA-Position ENUMERATED ⁇ pos2 , pos3 ⁇ , pdcch-conf i gsiBl INTEGER (0.
• connected WTRUs may continue to use legacy CBG sizing.
• emerging WTRUs may assume a narrow band interferer is present and that all transmitted CBGs consist of only one OB. The emerging WTRUs may continue to use this assumption as long as they are connected to the network and until they read a new MIB with staticCbgSizing set to “0”.
• the WTRU may inform the network of its static CBG sizing supportability.
• the network may optionally enable or disable this feature for the WTRU based on the WTRU capability and network’s requirement.
• the WTRU may inform the network of its capability via the information message shown in Table 5 below.
• the network may use legacy behavior for all CBGs transmitted to that WTRU.
• the network may configure the WTRU to periodically apply a different CBG size for a certain duration based on current interference characteristics.
• CBG sizing is configured semi-dynamically at the WTRU via RRC reconfiguration messages.
• New Information Elements are proposed to indicate the number of CBs per CBG, the duration of the CBG sizing ON/OFF cycle, the duration of ON period in slots, the duration in slots after RRC Reconfiguration message to start the CBG sizing cycle, and the consecutive number of slots the WTRU will follow the CBG sizing cycle. After the expiration of the CBG sizing duration, the WTRU reverts to legacy behavior, which assumes that retransmissions have the same CBG size as the initial transmission.
• a RRC reconfiguration message that may contain parameters to support semi-dynamic CBG sizing is shown in bold below.
• PDSCH-servingcel Iconfig :: SEQUENCE ⁇ code bl ockGroupTransmi ssi on setupRelease ⁇ PDSCH-Code blockGroupTransmission ⁇ OPTIONAL, xoverhead ENUMERATED ⁇ xoh6, xohl2 , xohl8 ⁇
• OPTIONAL -- Need s nrofHARQ-ProcessesForPDSCH ENUMERATED ⁇ n2, n4, n6, nlO, nl2 , nl6 ⁇ OPTIONAL, -- Need s pucch-cell servcel 1 index OPTIONAL , -- cond scell Addon! y
• PDSCH-Code blockGroupTransmission : : SEQUENCE ⁇ maxcodebl ockGroupsPerTransportBl ock ENUMERATED ⁇ n2, n4, n6, n8 ⁇ , nrofebsperebg INTEGER (0..335)
• FIG.9 illustrates an example of an RRC configured CBG sizing.
• the following parameters are defined: CbgSizingStartOffset, CbgSizingTimer, CbgSizingOnDurationTimer, and CbgSizingCycle.
• CbgSizingCycle may define the duration of one “CBG sizing ON time” and one “CBG sizing OFF time” in slots.
• CbgSizingOnDurationTimer may define the duration of “CBG sizing ON time” in slots within one CBGSizingCyde.
• CbgSizingStartOffset may define the duration in slots after the RRC reconfiguration message to start CbgSizingCycle.
• CbgSizingTimer may define the consecutive number of slots the WTRU shall follow the CBG sizing cycle after CbgSizingStartOffset.
• semi-dynamic CBG sizing 902 may start after 2 slots and continue for the next 24 slots.
• the CBG sizing 902 cycles may be 6 slots in length with an “on duration” of 2 slots.
• the WTRU may use “nrofCbsPerCbg” as the default CBG size.
• the WTRU may revert to legacy behavior, which assumes that retransmissions have the same CBG size as the initial transmission.
• the WTRU may need to inform the network as to whether is supports semi-dynamic CBG sizing.
• the network may optionally enable or disable this feature for the WTRU based on the WTRU capability and network’s requirement.
• the WTRU may inform the network of its capability via the information message shown in Table 6 below.
• fully dynamic CBG sizing may occur via DCI.
• a new DCI parameter, “CB transmission information,” may indicate the number of CBs in the CBGs.
• the network may dynamically change the CBG size via DCI to adapt to the varying characteristics of the RADAR interference.
• the CBG would be dynamically resized such that the RADAR signal is fitted within a single CBG of minimum size, thus reducing the number of CB retransmissions.
• Each (re)-transmission would follow a CBG sizing indicated by its corresponding DCI message. If this parameter is not configured, the WTRU may follow legacy HARQ behavior (i.e., retransmission have the same CBG size as the initial transmission.
• the RRC reconfiguration message may indicates the maximum code block groups per transport block.
• PDSCH-servi ngcel I confi g : : SEQUENCE ⁇ code bl ockGroupTransmi ssi on setupRel ease ⁇ PDSCH-Code bl ockGroupTransmi ssi on ⁇ OPTIONAL , xoverhead ENUMERATED ⁇ xoh6 , xohl2 , xohl8 ⁇
• OPTIONAL -- Need s nrofHARQ-ProcessesForPDSCH ENUMERATED ⁇ n2 , n4 , n6 , nlO , nl2 , nl6 ⁇ OPTIONAL , -- Need s pucch-cel l servcel 1 index OPTIONAL , -- cond scel l Addon! y
• PDSCH-Code bl ockGroupTransmi ssi on : : SEQUENCE ⁇ maxcodebl ockGroupsPerTransportBl ock ENUMERATED ⁇ n2 , n4 , n6 , n8 ⁇ , code bl ockGroupFl ushlndi cator BOOLEAN ,
• CBG transmission information may be indicated in DCI format 0_1 and format 1_1 .
• a new parameter “CB Transmission Information” may be added to indicate the number of CBs in the CBGs.
• the network may dynamically change the CBG size via DCI to adapt to the characteristics of the inferences, such as RADAR interference.
• the CBG may be resized such that the interferences signal (e.g., RADAR signal) is fitted within a single CBG of minimum size, thus reducing the number of CB retransmissions.
• Table 7 DCI Format for Scheduling PUSCH
• the WTRU may report dynamic CBG sizing support as part of the FeatureSetDownlink within WTRU Capability Information message.
• Table 8 “Yes” in the column by "FDD-TDD DIFF” and “FR1-FR2 DIFF” may indicate that the WTRU capability field can have a different value between FDD and TDD or between FR1 and FR2 and “No” may indicate if it cannot.
• “Yes” in the column “M” may indicate that the associated feature is mandatory and “No” may indicate that the associated feature is optional.
• the “Per” column may indicates the level the associated parameter is included. For example, "WTRU" in the “Per” column may indicate that the associated parameter is signaled per WTRU.
• the base station may continue to transmit legacy DCI formats to the WTRU. If the WTRU is capable of supporting this feature, it would indicate that as part of its WTRU capability report and start reading new DCI format.
• T able 8 DynamicCbgSizingSupport
• the WTRUs in the network can support dynamic CBG sizing
• the WTRUs may assume dynamic CBG sizing to be the default configuration without the need to use the spare bit in MIB.
• the WTRUs may directly use dynamic information provided by the new DCI to determine the number of CBGs and the size of the CBGs on a per-retransmission basis.
• a WTRU is configured to receive CBG based transmissions, i.e., received higher layer parameter codeBlockGroupTransmission, for PDSCH.
• the WTRU may assume that all the code block groups are present.
• the WTRU may assume that the CBGTI field of the scheduling DCI indicates which CBGs of the TB are present in the transmission.
• a bit value of “0” in the CBGTI field may indicate that the corresponding CBG is not transmitted and T indicates that it is transmitted. If the CBG flushing out information (CBGFI) field of the scheduling DCI is present, CBGFI may be set to “0” and indicate that the earlier received instances of the same CBGs being transmitted may be corrupted. A CBGFI set to “1” may indicate that the CBGs being retransmitted are combinable with the earlier received instances of the same CBGs.
• CBGFI CBG flushing out information
• a CBG does not necessarily need to contain the same number of CBs as in the initial transmission of the transport block.
• the WTRU may read field “CB transmission information” of the scheduling DCI to determine the size of the transmitted CBGs. After determining which CBG is transmitted via CBG transmission information, the WTRU reads the CB transmission information to determine the size of the CBGs.
• FIG. 12 is a diagram illustrating an example process 1200 of CBG sizing based on WTRU feedback.
• a WTRU may receive a first DCI, from a base station, a first DCI that indicates a first CBG size.
• the WTRU may receive a TB that includes one or more CBGs.
• the one or more CBGs may include one or more CBs.
• the WTRU may perform a cyclic redundancy check (CRC) on the received TB, including the one or more CBs.
• CRC cyclic redundancy check
• the WTRU may receive, from the base station, a second DCI that indicates a second CBG size.
• the second CBG size may be based on the transmitted feedback.
• the WTRU may then receive, from the base station, transmissions according to the second CBG size.
• the transmitted feedback may be an acknowledgement (ACK) or a negative acknowledgement (NACK). If the WTRU transmits an ACK, the second CBG size may be larger than the first CBG size. If the WTRU transmits a NACK, the second CBG size may be smaller than the first CBG size.
• ACK acknowledgement
• NACK negative acknowledgement
• CB and CBG interleaving may be used to mitigate the impact of burst errors caused by interference (e.g., RADAR interference).
• interference e.g., RADAR interference
• CBs and CBGs may be arranged within the same transport block before being transmitted over the wireless channel. The arrangement happens in such a way that some CBGs can be transmitted during the interferer’s “quiet period”.
• FIG. 10 illustrates an example of the impact of interference with no CB/CBG interleaving.
• the transport block 902 includes four CBGs - CBG #1 1004, CBG #2 1006, CBG #3 1008, and CBG #4 1010.
• CBG #1 1004 includes CB #1 1011 and CB #2 1012.
• CBG #2 1006 includes CB #3 1013 and CB #4 1014.
• CBG #3 1008 includes CB #5 1015 and CB #6 1016.
• CBG #4 1010 includes CB #7 1017 and CB #8 1018.
• the interference signal interferes with CB #2 1012, CB #3 1013, CB #6 1016 and CB #7 1017.
• all CBGs will need to be retransmitted as at least one CB within each CBG is erroneously received.
• FIG. 11 illustrates example of CB/CBG interleaving. Similar to transport block 1002 in FIG. 10, transport block 1102 includes CBG #1 1104, CBG #2 1106, CBG #3 1108, and CBG #4 1110. CBG #1 1104 includes CB #1 1111 and CB #2 1112. CBG #2 1106 includes CB #3 1113 and CB #4 1114. CBG #3 1108 includes CB #5 1115 and CB #6 1116. CBG #4 1110 includes CB #7 1117 and CB #8 1118.
• CBG #1 1104 includes CB #1 1111 and CB #3 1113
• CBG #2 1106 includes CB #4 1114 and CB #2 1112
• CBG #3 1108 includes CB #5 1115 and CB #7 1117
• CBG #4 1110 includes CB #8 1118 and CB #6 1116.
• the transmitter manages to transmit CBG #1 1104 and CBG #3 1108 within the interferer’s silent period. Consequently, CBG #1 1104 and CBG #3 1108 are received without error and will not need to be re-transmitted.
• the network may signal its use of CB/CBG interleaving to the WTRU via MIB message.
• the network may use the spare bit in the MIB to indicate the activation/deactivation of this feature (e.g., “0” to deactivate CB/CBG interleaving and “1” to activate CB/CBG interleaving).
• the network may use a simple form of interleaving such as the odd-even pattern.
• the first CBG may contain the first N odd CBs
• the second CBG contains the first N even CBs
• the third CBG contains the second N odd CBs
• the forth CBG contains the second N even CBs, and so on.
• MIB : SEQUENCE ⁇ systemFrameNumber BIT STRING (SIZE (6) ) , subcarri erspaci ngcommon ENUMERATED ⁇ scsl5or60 , scs30orl20 ⁇ , ssb-subcar ri eroffset INTEGER (0. . 15) , dmrs-TypeA-Position ENUMERATED ⁇ pos2 , pos3 ⁇ , pdcch-conf i gsiBl INTEGER (0.
• the WTRU implementation may support CB/CBG interleaving by reading MIB parameter cb- Cbgl nterleaving.
• the impact of this solution is more prominent in emerging UEs, after CB/CBG interleaving is activated.
• connected UEs may suffer excessive BLER which may require them to drop and reconnect to the network, hence acquiring a new MIB with cb-Cbglnterlaving bit set to “1”.
• the odd-even deinterleaver at the WTRU may regroup the CBs such that the first CBG contains the first N CBs of the first N CBGs, the second CBG contains the second N CBs of the first N CBGs, the third CBG contains the second N CBs of the second N CBGs, the fourth CBG contains the second N CBs of the second N CBGs, and so on.
• Dynamic CBG sizing may allow the transmitter to dynamically change the size of the CBG based on knowledge of the interference pattern.
• the operation may entail the following: (1) the gNB may analyze the interference pattern or an external node sends information characterizing the operation of the interferer to the gNB; (2) the gNB may utilize this information to determine the code blocks that may be impacted by the interference; and (3) the gNB may make dynamic decisions on whether to increase or decrease the size of the CBG to optimize HARQ feedback and amount of data retransmitted.
• CB and CBG interleaving may scramble the locations of the CBs and CBGs based on interference pattern knowledge.
• the scramble operation may entail the following: (1) the gNB may analyze the interference pattern or an external node sends information characterizing the operation of the interferer to the gNB; (2) the gNB may utilize this information to determine the interferer’s silent periods; and (3) the gNB may make dynamic decisions on how to interleave CBs and CBGs such that CBs of a certain CBG fall within those silent periods.
• the detected interference patterns (e.g., RADAR interference patters) may be measured by the base station and/or external sensors. Further, the detected interference patterns may be based on feedback from one or more WTRUs.
• ROM read only memory
• RAM random access memory
• register cache memory
• semiconductor memory devices magnetic media such as internal hard disks and removable disks, magnetooptical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).
• a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Quality & Reliability (AREA)
• Mobile Radio Communication Systems (AREA)
• Physics & Mathematics (AREA)
• Electromagnetism (AREA)

Applications Claiming Priority (3)

Publications (1)

Family

ID=84283181

Family Applications (1)

Country Status (3)

Family Cites Families (4)

• 2022
  • 2022-09-29 KR KR1020247013712A patent/KR20240073918A/ko active Pending
  • 2022-09-29 WO PCT/US2022/045195 patent/WO2023055908A1/en not_active Ceased
  • 2022-09-29 EP EP22801256.3A patent/EP4409784A1/de active Pending

Also Published As

Similar Documents

Legal Events