[go: up one dir, main page]

WO2025213087A2 - Rapport d'état de commande de liaison radio - Google Patents

Rapport d'état de commande de liaison radio

Info

Publication number
WO2025213087A2
WO2025213087A2 PCT/US2025/023249 US2025023249W WO2025213087A2 WO 2025213087 A2 WO2025213087 A2 WO 2025213087A2 US 2025023249 W US2025023249 W US 2025023249W WO 2025213087 A2 WO2025213087 A2 WO 2025213087A2
Authority
WO
WIPO (PCT)
Prior art keywords
rlc
entity
pdu
wireless device
sdu
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/US2025/023249
Other languages
English (en)
Other versions
WO2025213087A3 (fr
Inventor
Hsin-Hsi TSAI
Hyoungsuk Jeon
Esmael Hejazi Dinan
Sungduck Chun
Kyungmin Park
Taehun Kim
Jian Xu
Mohammad Ghadir Khoshkholgh Dashtaki
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ofinno LLC
Original Assignee
Ofinno LLC
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 Ofinno LLC filed Critical Ofinno LLC
Publication of WO2025213087A2 publication Critical patent/WO2025213087A2/fr
Publication of WO2025213087A3 publication Critical patent/WO2025213087A3/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

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/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/1607—Details of the supervisory signal
    • H04L1/1685—Details of the supervisory signal the supervisory signal being transmitted in response to a specific request, e.g. to a polling signal
    • 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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1848—Time-out mechanisms
    • 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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • 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/188—Time-out mechanisms
    • 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/1896—ARQ related signaling

Definitions

  • FIG. 1 A and FIG. 1 B illustrate example mobile communication networks in which embodiments of the present disclosure may be implemented.
  • FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user plane and control plane protocol stack.
  • NR New Radio
  • FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.
  • FIG. 4A illustrates an example downlink data flow through the NR user plane protocol stack of FIG. 2A.
  • FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.
  • FIG. 5A and FIG. 5B respectively illustrate a mapping between logical channels, transport channels, and physical channels for the downlink and uplink.
  • FIG. 6 is an example diagram showing RRC state transitions of a UE.
  • FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped.
  • one or more of the base stations in the RAN 104 may be implemented as a sectored site with more or less than three sectors.
  • One or more of the base stations in the RAN 104 may be implemented as an access point, as a baseband processing unit coupled to several remote radio heads (RRHs), and/or as a repeater or relay node used to extend the coverage area of a donor node.
  • a baseband processing unit coupled to RRHs may be part of a centralized or cloud RAN architecture, where the baseband processing unit may be either centralized in a pool of baseband processing units or virtualized.
  • a repeater node may amplify and rebroadcast a radio signal received from a donor node.
  • a relay node may perform the same/similar functions as a repeater node but may decode the radio signal received from the donor node to remove noise before amplifying and rebroadcasting the radio signal.
  • PDCPs 214 and 224 may perform mapping/de-mapping between a split radio bearer and RLC channels in a dual connectivity scenario.
  • Dual connectivity is a technique that allows a UE to connect to two cells or, more generally, two cell groups: a master cell group (MCG) and a secondary cell group (SCG).
  • MCG master cell group
  • SCG secondary cell group
  • a split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by cell groups in dual connectivity.
  • the PDCPs 214 and 224 may map/de-map the split radio bearer between RLC channels belonging to cell groups.
  • the downlink data flow of FIG. 4A begins when SDAP 225 receives the three IP packets from one or more QoS flows and maps the three packets to radio bearers.
  • the SDAP 225 maps IP packets n and n+1 to a first radio bearer 402 and maps IP packet m to a second radio bearer 404.
  • An SDAP header (labeled with an “H” in FIG. 4A) is added to an IP packet.
  • the data unit from/to a higher protocol layer is referred to as a service data unit (SDU) of the lower protocol layer and the data unit to/from a lower protocol layer is referred to as a protocol data unit (PDU) of the higher protocol layer.
  • SDU service data unit
  • PDU protocol data unit
  • the data unit from the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is a PDU of the SDAP 225.
  • FIG. 4B further illustrates MAC control elements (CEs) inserted into the MAC PDU by a MAC, such as MAC 212 or MAC 222.
  • a MAC such as MAC 212 or MAC 222.
  • FIG. 4B illustrates two MAC CEs inserted into the MAC PDU.
  • MAC CEs may be inserted at the beginning of a MAC PDU for downlink transmissions (as shown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions.
  • MAC CEs may be used for in-band control signaling.
  • Example MAC CEs include: scheduling-related MAC CEs, such as buffer status reports and power headroom reports; activation/deactivation MAC CEs, such as those for activation/deactivation of PDCP duplication detection, channel state information (CSI) reporting, sounding reference signal (SRS) transmission, and prior configured components; discontinuous reception (DRX) related MAC CEs; timing advance MAC CEs; and random access related MAC CEs.
  • a MAC CE may be preceded by a MAC subheader with a similar format as described for MAC SDUs and may be identified with a reserved value in the LCID field that indicates the type of control information included in the MAC CE.
  • PCCH paging control channel
  • a broadcast control channel for carrying system information messages in the form of a master information block (MIB) and several system information blocks (SIBs), wherein the system information messages may be used by the UEs to obtain information about how a cell is configured and how to operate within the cell;
  • MIB master information block
  • SIBs system information blocks
  • COCH common control channel
  • a dedicated control channel for carrying control messages to/from a specific the UE to configure the UE
  • BCH broadcast channel
  • PDSCH physical downlink shared channel
  • a physical downlink control channel for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands;
  • DCI downlink control information
  • PUSCH physical uplink shared channel
  • UCI uplink control information
  • a physical uplink control channel for carrying UCI, which may include HARQ acknowledgments, channel quality indicators (CQI), pre-coding matrix indicators (PMI), rank indicators (Rl), and scheduling requests (SR); and
  • CQI channel quality indicators
  • PMI pre-coding matrix indicators
  • Rl rank indicators
  • SR scheduling requests
  • the physical layer Similar to the physical control channels, the physical layer generates physical signals to support the low-level operation of the physical layer. As shown in FIG. 5A and FIG. 5B, the physical layer signals defined by NR include: primary synchronization signals (PSS), secondary synchronization signals (SSS), channel state information reference signals (CSI-RS), demodulation reference signals (DMRS), sounding reference signals (SRS), and phase-tracking reference signals (PT-RS). These physical layer signals will be described in greater detail below.
  • PSS primary synchronization signals
  • SSS secondary synchronization signals
  • CSI-RS channel state information reference signals
  • DMRS demodulation reference signals
  • SRS sounding reference signals
  • PT-RS phase-tracking reference signals
  • FIG. 2B illustrates an example NR control plane protocol stack.
  • the NR control plane protocol stack may use the same/similar first four protocol layers as the example NR user plane protocol stack. These four protocol layers include the PHYs 211 and 221 , the MAGs 212 and 222, the RLCs 213 and 223, and the PDOPs 214 and 224.
  • the NR control plane stack has radio resource controls (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.
  • RRCs radio resource controls
  • the NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 (e.g., the AMF 158A) or, more generally, between the UE 210 and the ON.
  • the NAS protocols 217 and 237 may provide control plane functionality between the UE 210 and the AMF 230 via signaling messages, referred to as NAS messages. There is no direct path between the UE 210 and the AMF 230 through which the NAS messages can be transported.
  • the NAS messages may be transported using the AS of the Uu and NG interfaces.
  • NAS protocols 217 and 237 may provide control plane functionality such as authentication, security, connection setup, mobility management, and session management.
  • the RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 or, more generally, between the UE 210 and the RAN.
  • the RRCs 216 and 226 may provide control plane functionality between the UE 210 and the gNB 220 via signaling messages, referred to as RRC messages.
  • RRC messages may be transmitted between the UE 210 and the RAN using signaling radio bearers and the same/similar PDCP, RLC, MAC, and PHY protocol layers.
  • the MAC may multiplex control-plane and user-plane data into the same transport block (TB).
  • the RRCs 216 and 226 may provide control plane functionality such as: broadcast of system information related to AS and NAS; paging initiated by the CN or the RAN; establishment, maintenance and release of an RRC connection between the UE 210 and the RAN; security functions including key management; establishment, configuration, maintenance and release of signaling radio bearers and data radio bearers; mobility functions; QoS management functions; the UE measurement reporting and control of the reporting; detection of and recovery from radio link failure (RLF); and/or NAS message transfer.
  • RRCs 216 and 226 may establish an RRC context, which may involve configuring parameters for communication between the UE 210 and the RAN.
  • the base station may be similar to one of the one or more base stations included in the RAN 104 depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG. 1 B, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other base station described in the present disclosure.
  • the base station with which the UE is connected may have the RRC context for the UE.
  • the RRC context referred to as the UE context, may comprise parameters for communication between the UE and the base station.
  • These parameters may include, for example: one or more AS contexts; one or more radio link configuration parameters; bearer configuration information (e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and/or PDU session); security information; and/or PHY, MAC, RLC, PDCP, and/or SDAP layer configuration information.
  • bearer configuration information e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and/or PDU session
  • security information e.g., relating to a data radio bearer, signaling radio bearer, logical channel, QoS flow, and/or PDU session
  • PHY e.g., MAC, RLC, PDCP, and/or SDAP layer configuration information
  • the RAN e.g., the RAN 104 or the NG-RAN 154
  • the UE may measure the signal levels (e.g., reference signal levels) from a serving cell
  • the UE’s serving base station may request a handover to a cell of one of the neighboring base stations based on the reported measurements.
  • the RRC state may transition from RRC connected 602 to RRC idle 604 through a connection release procedure 608 or to RRC inactive 606 through a connection inactivation procedure 610.
  • RRC idle 604 an RRC context may not be established for the UE.
  • the UE may not have an RRC connection with the base station.
  • the UE While in RRC idle 604, the UE may be in a sleep state for the majority of the time (e.g., to conserve battery power).
  • the UE may wake up periodically (e.g., once in every discontinuous reception cycle) to monitor for paging messages from the RAN.
  • Mobility of the UE may be managed by the UE through a procedure known as cell reselection.
  • the RRC state may transition from RRC idle 604 to RRC connected 602 through a connection establishment procedure 612, which may involve a random access procedure as discussed in greater detail below.
  • An RRC state may be associated with a mobility management mechanism.
  • RRC idle 604 and RRC inactive 606 mobility is managed by the UE through cell reselection.
  • the purpose of mobility management in RRC idle 604 and RRC inactive 606 is to allow the network to be able to notify the UE of an event via a paging message without having to broadcast the paging message over the entire mobile communications network.
  • the mobility management mechanism used in RRC idle 604 and RRC inactive 606 may allow the network to track the UE on a cell-group level so that the paging message may be broadcast over the cells of the cell group that the UE currently resides within instead of the entire mobile communication network.
  • the mobility management mechanisms for RRC idle 604 and RRC inactive 606 track the UE on a cell-group level. They may do so using different granularities of grouping. For example, there may be three levels of cell-grouping granularity: individual cells; cells within a RAN area identified by a RAN area identifier (RAI); and cells within a group of RAN areas, referred to as a tracking area and identified by a tracking area identifier (TAI).
  • RAI RAN area identifier
  • TAI tracking area and identified by a tracking area identifier
  • Tracking areas may be used to track the UE at the ON level.
  • the ON e.g., the ON 102 or the 5G-CN 152
  • the ON may provide the UE with a list of TAIs associated with a UE registration area. If the UE moves, through cell reselection, to a cell associated with a TAI not included in the list of TAIs associated with the UE registration area, the UE may perform a registration update with the ON to allow the ON to update the UE’s location and provide the UE with a new the UE registration area.
  • RAN areas may be used to track the UE at the RAN level.
  • the UE may be assigned a RAN notification area.
  • a RAN notification area may comprise one or more cell identities, a list of RAIs, or a list of TAIs.
  • a base station may belong to one or more RAN notification areas.
  • a cell may belong to one or more RAN notification areas. If the UE moves, through cell reselection, to a cell not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the UE’s RAN notification area.
  • a base station storing an RRC context for a UE or a last serving base station of the UE may be referred to as an anchor base station.
  • An anchor base station may maintain an RRC context for the UE at least during a period of time that the UE stays in a RAN notification area of the anchor base station and/or during a period of time that the UE stays in RRC inactive 606.
  • a gNB such as gNBs 160 in FIG. 1 B, may be split into two parts: a central unit (gNB-CU), and one or more distributed units (gNB-DU).
  • a gNB-CU may be coupled to one or more gNB-DUs using an F1 interface.
  • the gNB-CU may comprise the RRC, the PDCP, and the SDAP.
  • a gNB-DU may comprise the RLC, the MAC, and the PHY.
  • OFDM orthogonal frequency divisional multiplexing
  • FAM frequency divisional multiplexing
  • M-QAM M-quadrature amplitude modulation
  • M-PSK M-phase shift keying
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols
  • source symbols
  • the IFFT block may take in F source symbols at a time, one from each of the F parallel symbol streams, and use each source symbol to modulate the amplitude and phase of one of F sinusoidal basis functions that correspond to the F orthogonal subcarriers.
  • the output of the IFFT block may be F time-domain samples that represent the summation of the F orthogonal subcarriers.
  • the F time-domain samples may form a single OFDM symbol.
  • an OFDM symbol provided by the IFFT block may be transmitted over the air interface on a carrier frequency.
  • the F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block.
  • This operation produces Discrete Fourier Transform (DFT)-precoded OFDM symbols and may be used by UEs in the uplink to reduce the peak to average power ratio (PAPR).
  • DFT Discrete Fourier Transform
  • PAPR peak to average power ratio
  • Inverse processing may be performed on the OFDM symbol at a receiver using an FFT block to recover the data mapped to the source symbols.
  • FIG. 7 illustrates an example configuration of an NR frame into which OFDM symbols are grouped.
  • An NR frame may be identified by a system frame number (SFN).
  • the SFN may repeat with a period of 1024 frames.
  • one NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes that are 1 ms in duration.
  • a subframe may be divided into slots that include, for example, 14 OFDM symbols per slot.
  • the duration of a slot may depend on the numerology used for the OFDM symbols of the slot.
  • a flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies below 1 GHz up to cells with carrier frequencies in the mm-wave range).
  • a numerology may be defined in terms of subcarrier spacing and cyclic prefix duration.
  • subcarrier spacings may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz
  • cyclic prefix durations may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 ps.
  • NR defines numerologies with the following subcarrier spacing/cyclic prefix duration combinations: 15 kHz/4.7 ps; 30 kHz/2.3 ps; 60 kHz/1.2 ps; 120 kHz/0.59 ps; and 240 kHz/0.29 ps.
  • a slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols).
  • a numerology with a higher subcarrier spacing has a shorter slot duration and, correspondingly, more slots per subframe.
  • FIG. 7 illustrates this numerology-dependent slot duration and slots-per-subframe transmission structure (the numerology with a subcarrier spacing of 240 kHz is not shown in FIG. 7 for ease of illustration).
  • a subframe in NR may be used as a numerologyindependent time reference, while a slot may be used as the unit upon which uplink and downlink transmissions are scheduled.
  • scheduling in NR may be decoupled from the slot duration and start at any OFDM symbol and last for as many symbols as needed for a transmission. These partial slot transmissions may be referred to as mini-slot or subslot transmissions.
  • FIG. 8 illustrates an example configuration of a slot in the time and frequency domain for an NR carrier.
  • the slot includes resource elements (REs) and resource blocks (RBs).
  • An RE is the smallest physical resource in NR.
  • An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8.
  • An RB spans twelve consecutive REs in the frequency domain as shown in FIG. 8.
  • Such a limitation may limit the NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, where the 400 MHz bandwidth may be set based on a 400 MHz per carrier bandwidth limit.
  • FIG. 8 illustrates a single numerology being used across the entire bandwidth of the NR carrier.
  • multiple numerologies may be supported on the same carrier.
  • NR defines bandwidth parts (BWPs) to support UEs not capable of receiving the full carrier bandwidth and to support bandwidth adaptation.
  • BWP may be defined by a subset of contiguous RBs on a carrier.
  • a UE may be configured (e.g., via RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell).
  • one or more of the configured BWPs for a serving cell may be active. These one or more BWPs may be referred to as active BWPs of the serving cell.
  • the serving cell When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs in the uplink carrier and one or more second active BWPs in the secondary uplink carrier.
  • a base station may sem i-statically configure a UE with a default downlink BWP within a set of configured downlink BWPs associated with a PCell. If the base station does not provide the default downlink BWP to the UE, the default downlink BWP may be an initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on a CORESET configuration obtained using the PBCH.
  • the UE may switch between BWPs at switching points.
  • the UE may switch from the BWP 902 to the BWP 904 at a switching point 908.
  • the switching at the switching point 908 may occur for any suitable reason, for example, in response to an expiry of a BWP inactivity timer (indicating switching to the default BWP) and/or in response to receiving a DOI indicating BWP 904 as the active BWP.
  • the UE may switch at a switching point 910 from active BWP 904 to BWP 906 in response to receiving a DOI indicating BWP 906 as the active BWP.
  • the UE may switch at a switching point 912 from active BWP 906 to BWP 904 in response to an expiry of a BWP inactivity timer and/or in response to receiving a DOI indicating BWP 904 as the active BWP.
  • the UE may switch at a switching point 914 from active BWP 904 to BWP 902 in response to receiving a DOI indicating BWP 902 as the active BWP.
  • a cell comprising a downlink carrier and optionally an uplink carrier, may be assigned with a physical cell ID and a cell index.
  • the physical cell ID or the cell index may identify a downlink carrier and/or an uplink carrier of the cell, for example, depending on the context in which the physical cell ID is used.
  • a physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier.
  • a cell index may be determined using RRC messages.
  • a physical cell ID may be referred to as a carrier ID
  • a cell index may be referred to as a carrier index.
  • a multi-carrier nature of a PHY may be exposed to a MAC.
  • a HARQ entity may operate on a serving cell.
  • a transport block may be generated per assignment/grant per serving cell.
  • a transport block and potential HARQ retransmissions of the transport block may be mapped to a serving cell.
  • a base station may transmit (e.g., unicast, multicast, and/or broadcast) one or more Reference Signals (RSs) to a UE (e.g., PSS, SSS, CSI-RS, DMRS, and/or PT-RS, as shown in FIG. 5A).
  • RSs Reference Signals
  • the UE may transmit one or more RSs to the base station (e.g., DMRS, PT-RS, and/or SRS, as shown in FIG. 5B).
  • the PSS and the SSS may be transmitted by the base station and used by the UE to synchronize the UE to the base station.
  • FIG. 11A illustrates an example of an SS/PBCH block's structure and location.
  • a burst of SS/PBCH blocks may include one or more SS/PBCH blocks (e.g., 4 SS/PBCH blocks, as shown in FIG. 11A). Bursts may be transmitted periodically (e.g., every 2 frames or 20 ms). A burst may be restricted to a half-frame (e.g., a first half-frame having a duration of 5 ms). It will be understood that FIG.
  • 11A is an example, and that these parameters (number of SS/PBCH blocks per burst, periodicity of bursts, position of burst within the frame) may be configured based on, for example: a carrier frequency of a cell in which the SS/PBCH block is transmitted; a numerology or subcarrier spacing of the cell; a configuration by the network (e.g., using RRC signaling); or any other suitable factor.
  • the UE may assume a subcarrier spacing for the SS/PBCH block based on the carrier frequency being monitored, unless the radio network configured the UE to assume a different subcarrier spacing.
  • the location of the SS/PBCH block in the time and frequency domains may not be known to the UE (e.g., if the UE is searching for the cell).
  • the UE may monitor a carrier for the PSS. For example, the UE may monitor a frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20 ms), the UE may search for the PSS at a different frequency location within the carrier, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine, based on a known structure of the SS/PBCH block, the locations of the SSS and the PBCH, respectively.
  • the SS/PBCH block may be a celldefining SS block (CD-SSB).
  • a primary cell may be associated with a CD-SSB.
  • the CD-SSB may be located on a synchronization raster.
  • a cell selection/search and/or reselection may be based on the CD- SSB.
  • the RMSI may include a System Information Block Type 1 (SIB1).
  • SIB1 may contain information needed by the UE to access the cell.
  • the UE may use one or more parameters of the MIB to monitor PDCCH, which may be used to schedule PDSCH.
  • the PDSCH may include the SIB1.
  • the SIB1 may be decoded using parameters provided in the MIB.
  • the PBCH may indicate an absence of SIB1. Based on the PBCH indicating the absence of SIB1 , the UE may be pointed to a frequency.
  • the UE may search for an SS/PBCH block at the frequency to which the UE is pointed.
  • the UE may assume that one or more SS/PBCH blocks transmitted with a same SS/PBCH block index are quasi co-located (QCLed) (e.g., having the same/similar Doppler spread, Doppler shift, average gain, average delay, and/or spatial Rx parameters).
  • QCL quasi co-located
  • SS/PBCH blocks may be transmitted in spatial directions (e.g. , using different beams that span a coverage area of the cell).
  • a first SS/PBCH block may be transmitted in a first spatial direction using a first beam
  • a second SS/PBCH block may be transmitted in a second spatial direction using a second beam.
  • a base station may transmit a plurality of SS/PBCH blocks.
  • a first PCI of a first SS/PBCH block of the plurality of SS/PBCH blocks may be different from a second PCI of a second SS/PBCH block of the plurality of SS/PBCH blocks.
  • the PCIs of SS/PBCH blocks transmitted in different frequency locations may be different or the same.
  • the CSI-RS may be transmitted by the base station and used by the UE to acquire channel state information (CSI).
  • the base station may configure the UE with one or more CSI-RSs for channel estimation or any other suitable purpose.
  • the base station may configure a UE with one or more of the same/similar CSI-RSs.
  • the UE may measure the one or more CSI-RSs.
  • the UE may estimate a downlink channel state and/or generate a CSI report based on the measuring of the one or more downlink CSI-RSs.
  • the UE may provide the CSI report to the base station.
  • the base station may use feedback provided by the UE (e.g., the estimated downlink channel state) to perform link adaptation.
  • the base station may semi-statically configure the UE with one or more CSI-RS resource sets.
  • a CSI-RS resource may be associated with a location in the time and frequency domains and a periodicity.
  • the base station may selectively activate and/or deactivate a CSI-RS resource.
  • the base station may indicate to the UE that a CSI-RS resource in the CSI-RS resource set is activated and/or deactivated.
  • the base station may configure the UE to report CSI measurements.
  • the base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently.
  • periodic CSI reporting the UE may be configured with a timing and/or periodicity of a plurality of CSI reports.
  • the base station may request a CSI report.
  • the base station may command the UE to measure a configured CSI-RS resource and provide a CSI report relating to the measurements.
  • the base station may configure the UE to transmit periodically, and selectively activate or deactivate the periodic reporting.
  • the base station may configure the UE with a CSI-RS resource set and CSI reports using RRC signaling.
  • the CSI-RS configuration may comprise one or more parameters indicating, for example, up to 32 antenna ports.
  • the UE may be configured to employ the same OFDM symbols for a downlink CSI-RS and a control resource set (CORESET) when the downlink CSI-RS and CORESET are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of the physical resource blocks (PRBs) configured for the CORESET.
  • the UE may be configured to employ the same OFDM symbols for downlink CSI-RS and SS/PBCH blocks when the downlink CSI-RS and SS/PBCH blocks are spatially QCLed and resource elements associated with the downlink CSI-RS are outside of PRBs configured for the SS/PBCH blocks.
  • Downlink DMRSs may be transmitted by a base station and used by a UE for channel estimation.
  • the downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g. , PDSCH).
  • An NR network may support one or more variable and/or configurable DMRS patterns for data demodulation.
  • At least one downlink DMRS configuration may support a front-loaded DMRS pattern.
  • a front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols).
  • a base station may semi- statically configure the UE with a number (e.g. a maximum number) of front-loaded DMRS symbols for PDSCH.
  • a DMRS configuration may support one or more DMRS ports. For example, for single user-MIMO, a DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. For multiuser-MI MO, a DMRS configuration may support up to 4 orthogonal downlink DMRS ports per UE.
  • a radio network may support (e.g., at least for CP-OFDM) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and/or a scrambling sequence may be the same or different.
  • the base station may transmit a downlink DMRS and a corresponding PDSCH using the same precoding matrix.
  • the UE may use the one or more downlink DMRSs for coherent demodulation/channel estimation of the PDSCH.
  • a transmitter may use a precoder matrices for a part of a transmission bandwidth.
  • the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth.
  • the first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth.
  • the UE may assume that a same precoding matrix is used across a set of PRBs.
  • the set of PRBs may be denoted as a precoding resource block group (PRG).
  • PRG precoding resource block group
  • a PDSCH may comprise one or more layers.
  • the UE may assume that at least one symbol with DMRS is present on a layer of the one or more layers of the PDSCH.
  • a higher layer may configure up to 3 DMRSs for the PDSCH.
  • Downlink PT-RS may be transmitted by a base station and used by a UE for phase-noise compensation. Whether a downlink PT-RS is present or not may depend on an RRC configuration. The presence and/or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and/or an association with one or more parameters employed for other purposes (e.g., modulation and coding scheme (MCS)), which may be indicated by DCI. When configured, a dynamic presence of a downlink PT-RS may be associated with one or more DCI parameters comprising at least MCS.
  • An NR network may support a plurality of PT-RS densities defined in the time and/or frequency domains.
  • a frequency domain density may be associated with at least one configuration of a scheduled bandwidth.
  • the UE may assume a same precoding for a DMRS port and a PT-RS port.
  • a number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource.
  • Downlink PT-RS may be confined in the scheduled time/frequency duration for the UE.
  • Downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.
  • the UE may transmit an uplink DMRS to a base station for channel estimation.
  • the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels.
  • the UE may transmit an uplink DMRS with a PUSCH and/or a PUCCH.
  • the uplink DM-RS may span a range of frequencies that is similar to a range of frequencies associated with the corresponding physical channel.
  • the base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a front- loaded DMRS pattern.
  • the front-loaded DMRS may be mapped over one or more OFDM symbols (e.g., one or two adjacent OFDM symbols).
  • One or more uplink DMRSs may be configured to transmit at one or more symbols of a PUSCH and/or a PUCCH.
  • the base station may semi-statically configure the UE with a number (e.g. maximum number) of front-loaded DMRS symbols for the PUSCH and/or the PUCCH, which the UE may use to schedule a single-symbol DMRS and/or a double-symbol DMRS.
  • An NR network may support (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-0 F DM)) a common DMRS structure for downlink and uplink, wherein a DMRS location, a DMRS pattern, and/or a scrambling sequence for the DMRS may be the same or different.
  • CP-0 F DM cyclic prefix orthogonal frequency division multiplexing
  • a PUSCH may comprise one or more layers, and the UE may transmit at least one symbol with DMRS present on a layer of the one or more layers of the PUSCH.
  • a higher layer may configure up to three DMRSs for the PUSCH.
  • Uplink PT-RS (which may be used by a base station for phase tracking and/or phase-noise compensation) may or may not be present depending on an RRC configuration of the UE.
  • the presence and/or pattern of uplink PT- RS may be configured on a UE-specific basis by a combination of RRC signaling and/or one or more parameters employed for other purposes (e.g., Modulation and Coding Scheme (MCS)), which may be indicated by DCI.
  • MCS Modulation and Coding Scheme
  • a dynamic presence of uplink PT-RS may be associated with one or more DCI parameters comprising at least MCS.
  • a radio network may support a plurality of uplink PT-RS densities defined in time/frequency domain.
  • a frequency domain density may be associated with at least one configuration of a scheduled bandwidth.
  • the UE may assume a same precoding for a DMRS port and a PT-RS port.
  • a number of PT-RS ports may be fewer than a number of DMRS ports in a scheduled resource.
  • uplink PT-RS may be confined in the scheduled time/frequency duration for the UE.
  • SRS may be transmitted by a UE to a base station for channel state estimation to support uplink channel dependent scheduling and/or link adaptation.
  • SRS transmitted by the UE may allow a base station to estimate an uplink channel state at one or more frequencies.
  • a scheduler at the base station may employ the estimated uplink channel state to assign one or more resource blocks for an uplink PUSCH transmission from the UE.
  • the base station may semi-statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources.
  • An SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter.
  • an SRS resource in an SRS resource set of the one or more SRS resource sets may be transmitted at a time instant (e.g., simultaneously).
  • the UE may transmit one or more SRS resources in SRS resource sets.
  • An NR network may support aperiodic, periodic and/or semi-persistent SRS transmissions.
  • the UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may comprise higher layer signaling (e.g., RRC) and/or one or more DCI formats.
  • At least one DCI format may be employed for the UE to select at least one of one or more configured SRS resource sets.
  • An SRS trigger type 0 may refer to an SRS triggered based on a higher layer signaling.
  • An SRS trigger type 1 may refer to an SRS triggered based on one or more DOI formats.
  • the UE when PUSCH and SRS are transmitted in a same slot, the UE may be configured to transmit SRS after a transmission of a PUSCH and a corresponding uplink DMRS.
  • the base station may semi-statically configure the UE with one or more SRS configuration parameters indicating at least one of following: a SRS resource configuration identifier; a number of SRS ports; time domain behavior of an SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS); slot, minislot, and/or subframe level periodicity; offset for a periodic and/or an aperiodic SRS resource; a number of OFDM symbols in an SRS resource; a starting OFDM symbol of an SRS resource; an SRS bandwidth; a frequency hopping bandwidth; a cyclic shift; and/or an SRS sequence ID.
  • SRS resource configuration identifier e.g., an indication of periodic, semi-persistent, or aperiodic SRS
  • slot, minislot, and/or subframe level periodicity e.g., an indication of periodic, semi-persistent, or aperiodic SRS
  • An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. If a first symbol and a second symbol are transmitted on the same antenna port, the receiver may infer the channel (e.g., fading gain, multipath delay, and/or the like) for conveying the second symbol on the antenna port, from the channel for conveying the first symbol on the antenna port.
  • the channel e.g., fading gain, multipath delay, and/or the like
  • a first antenna port and a second antenna port may be referred to as quasi colocated (QCLed) if one or more large-scale properties of the channel over which a first symbol on the first antenna port is conveyed may be inferred from the channel over which a second symbol on a second antenna port is conveyed.
  • the one or more large-scale properties may comprise at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and/or spatial Receiving (Rx) parameters.
  • FIG. 11B illustrates an example of channel state information reference signals (CSI-RSs) that are mapped in the time and frequency domains.
  • CSI-RSs channel state information reference signals
  • a square shown in FIG. 11 B may span a resource block (RB) within a bandwidth of a cell.
  • a base station may transmit one or more RRC messages comprising CSI-RS resource configuration parameters indicating one or more CSI-RSs.
  • the three beams illustrated in FIG. 11 B may be configured for a UE in a UE-specific configuration. Three beams are illustrated in FIG. 11 B (beam #1 , beam #2, and beam #3), more or fewer beams may be configured.
  • Beam #1 may be allocated with CSI-RS 1101 that may be transmitted in one or more subcarriers in an RB of a first symbol.
  • Beam #2 may be allocated with CSI-RS 1102 that may be transmitted in one or more subcarriers in an RB of a second symbol.
  • Beam #3 may be allocated with CSI-RS 1103 that may be transmitted in one or more subcarriers in an RB of a third symbol.
  • Beamforming at the base station may include, e.g., an Rx beam sweep from a set of beams (shown, in the top rows of U1 and U2, as ovals rotated in a counterclockwise direction indicated by the dashed arrow).
  • Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam.
  • the UE and/or the base station may perform procedure U2 using a smaller set of beams than is used in procedure P1, or using narrower beams than the beams used in procedure P1. This may be referred to as beam refinement
  • the UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.
  • the UE may initiate the random access procedure to request one or more system information blocks (SIBs) (e.g., other system information such as SIB2, SIB3, and/or the like).
  • SIBs system information blocks
  • the UE may initiate the random access procedure for a beam failure recovery request.
  • a network may initiate a random access procedure for a handover and/or for establishing time alignment for an SCell addition.
  • the configuration message 1310 may be transmitted, for example, using one or more RRC messages.
  • the one or more RRC messages may indicate one or more random access channel (RACH) parameters to the UE.
  • RACH parameters may comprise at least one of following: general parameters for one or more random access procedures (e.g., RACH-configGeneral ⁇ ; cell-specific parameters (e.g., RACH-ConfigCommon'); and/or dedicated parameters (e.g., RACH-configDedicated ⁇ .
  • the base station may broadcast or multicast the one or more RRC messages to one or more UEs.
  • the one or more RACH parameters provided in the configuration message 1310 may be used to determine an uplink transmit power of Msg 1 1311 and/or Msg 3 1313.
  • the one or more RACH parameters may indicate a reference power for a preamble transmission (e.g., a received target power and/or an initial power of the preamble transmission).
  • the one or more RACH parameters may indicate: a power ramping step; a power offset between SSB and CSI-RS; a power offset between transmissions of the Msg 1 1311 and the Msg 3 1313; and/or a power offset value between preamble groups.
  • the one or more RACH parameters may indicate one or more thresholds based on which the UE may determine at least one reference signal (e.g. , an SSB and/or CSI-RS) and/or an uplink carrier (e.g. , a normal uplink (NUL) carrier and/or a supplemental uplink (SUL) carrier).
  • at least one reference signal e.g. , an SSB and/or CSI-RS
  • an uplink carrier e.g. , a normal uplink (NUL) carrier and/or a supplemental uplink (SUL) carrier.
  • the Msg 1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions).
  • An RRC message may be used to configure one or more preamble groups (e.g., group A and/or group B).
  • a preamble group may comprise one or more preambles.
  • the UE may determine the preamble group based on a pathloss measurement and/or a size of the Msg 3 1313.
  • the UE may determine the preamble based on the one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a pathloss measurement, an RSRP measurement, and/or a size of the Msg 3 1313.
  • the one or more RACH parameters may indicate: a preamble format; a maximum number of preamble transmissions; and/or one or more thresholds for determining one or more preamble groups (e.g., group A and group B).
  • a base station may use the one or more RACH parameters to configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSBs and/or CSI-RSs).
  • the UE may determine the preamble to include in Msg 1 1311 based on the association.
  • the Msg 1 1311 may be transmitted to the base station via one or more PRACH occasions.
  • the UE may use one or more reference signals (e.g., SSBs and/or CSI-RSs) for selection of the preamble and for determining of the PRACH occasion.
  • One or more RACH parameters e.g., ra-ssb-OccasionMsklndex and/or ra-OccasionList
  • the UE may perform a preamble retransmission if no response is received following a preamble transmission.
  • the UE may increase an uplink transmit power for the preamble retransmission.
  • the UE may select an initial preamble transmit power based on a pathloss measurement and/or a target received preamble power configured by the network.
  • the UE may determine to retransmit a preamble and may ramp up the uplink transmit power.
  • the UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMP/NG_STEP) indicating a ramping step for the preamble retransmission.
  • the ramping step may be an amount of incremental increase in uplink transmit power for a retransmission.
  • the Msg 21312 may include multiple RARs corresponding to multiple UEs.
  • the Msg 2 1312 may be received after or in response to the transmitting of the Msg 1 1311.
  • the Msg 2 1312 may be scheduled on the DL-SCH and indicated on a PDCCH using a random access RNTI (RA-RNTI).
  • RA-RNTI random access RNTI
  • the Msg 21312 may indicate that the Msg 1 1311 was received by the base station.
  • the Msg 2 1312 may include a time-alignment command that may be used by the UE to adjust the UE’s transmission timing, a scheduling grant for transmission of the Msg 3 1313, and/or a Temporary Cell RNTI (TC-RNTI).
  • TC-RNTI Temporary Cell RNTI
  • the UE may determine that the contention resolution is successful and/or the UE may determine that the random access procedure is successfully completed.
  • the UE may be configured with a supplementary uplink (SUL) carrier and a normal uplink (NUL) carrier.
  • An initial access (e.g., random access procedure) may be supported in an uplink carrier.
  • a base station may configure the UE with two separate RACH configurations: one for an SUL carrier and the other for an NUL carrier.
  • a base station may attach one or more cyclic redundancy check (CRC) parity bits to a DCI in order to facilitate detection of transmission errors.
  • CRC cyclic redundancy check
  • the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of the UEs). Scrambling the CRC parity bits with the identifier may comprise Modulo-2 addition (or an exclusive OR operation) of the identifier value and the CRC parity bits.
  • the identifier may comprise a 16-bit value of a radio network temporary identifier (RNTI).
  • RNTI radio network temporary identifier
  • DCIs may be used for different purposes.
  • a purpose may be indicated by the type of RNTI used to scramble the CRC parity bits.
  • a DCI having CRC parity bits scrambled with a paging RNTI may indicate paging information and/or a system information change notification.
  • the P-RNTI may be predefined as “FFFE” in hexadecimal.
  • a DCI having CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of the system information.
  • SI-RNTI may be predefined as “FFFF” in hexadecimal.
  • a DCI having CRC parity bits scrambled with a random access RNTI may indicate a random access response (RAR).
  • a DCI having CRC parity bits scrambled with a cell RNTI may indicate a dynamically scheduled unicast transmission and/or a triggering of PDCCH-ordered random access.
  • a DCI having CRC parity bits scrambled with a temporary cell RNTI may indicate a contention resolution (e.g., a Msg 3 analogous to the Msg 3 1313 illustrated in FIG. 13A).
  • RNTIs configured to the UE by a base station may comprise a Configured Scheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI (INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-Persistent CSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and/or the like.
  • CS-RNTI Configured Scheduling RNTI
  • TPC-PUCCH-RNTI Transmit Power Control-PUSCH RNTI
  • TPC-SRS-RNTI Transmit Power Control-SRS RNTI
  • INT-RNTI Interruption RNTI
  • the base station may transmit the DCIs with one or more DCI formats.
  • DCI format 0_0 may be used for scheduling of PUSCH in a cell.
  • DCI format 0_0 may be a fallback DCI format (e.g., with compact DCI payloads).
  • DCI format 0_1 may be used for scheduling of PUSCH in a cell (e.g., with more DCI payloads than DCI format 0_0).
  • DCI format 1_0 may be used for scheduling of PDSCH in a cell.
  • DCI format 1_0 may be a fallback DCI format (e.g., with compact DCI payloads).
  • the base station may process the DOI with channel coding (e.g. , polar coding), rate matching, scrambling and/or QPSK modulation.
  • a base station may map the coded and modulated DOI on resource elements used and/or configured for a PDCCH. Based on a payload size of the DOI and/or a coverage of the base station, the base station may transmit the DOI via a PDCCH occupying a number of contiguous control channel elements (CCEs).
  • the number of the contiguous CCEs (referred to as aggregation level) may be 1 , 2, 4, 8, 16, and/or any other suitable number.
  • a CCE may comprise a number (e.g., 6) of resource-element groups (REGs).
  • REG may comprise a resource block in an OFDM symbol.
  • the mapping of the coded and modulated DCI on the resource elements may be based on mapping of CCEs and REGs (e.g., CCE-to-REG mapping).
  • FIG. 14A illustrates an example of CORESET configurations for a bandwidth part.
  • the base station may transmit a DCI via a PDCCH on one or more control resource sets (CORESETs).
  • a CORESET may comprise a timefrequency resource in which the UE tries to decode a DCI using one or more search spaces.
  • the base station may configure a CORESET in the time-frequency domain.
  • a first CORESET 1401 and a second CORESET 1402 occur at the first symbol in a slot.
  • the first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain.
  • a third CORESET 1403 occurs at a third symbol in the slot.
  • a fourth CORESET 1404 occurs at the seventh symbol in the slot.
  • CORESETs may have a different number of resource blocks in frequency domain.
  • FIG. 14B illustrates an example of a CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing.
  • the CCE-to-REG mapping may be an interleaved mapping (e.g., for the purpose of providing frequency diversity) or a non-interleaved mapping (e.g., for the purposes of facilitating interference coordination and/or frequency- selective transmission of control channels).
  • the base station may perform different or same CCE-to-REG mapping on different CORESETs.
  • a CORESET may be associated with a CCE-to-REG mapping by RRC configuration.
  • a CORESET may be configured with an antenna port quasi co-location (QCL) parameter.
  • the antenna port QCL parameter may indicate QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET.
  • DMRS demodulation reference signal
  • the base station may transmit, to the UE, RRC messages comprising configuration parameters of one or more CORESETs and one or more search space sets.
  • the configuration parameters may indicate an association between a search space set and a CORESET.
  • a search space set may comprise a set of PDCCH candidates formed by CCEs at a given aggregation level.
  • the configuration parameters may indicate: a number of PDCCH candidates to be monitored per aggregation level; a PDCCH monitoring periodicity and a PDCCH monitoring pattern; one or more DCI formats to be monitored by the UE; and/or whether a search space set is a common search space set or a UE- specific search space set.
  • a set of CCEs in the common search space set may be predefined and known to the UE.
  • a set of CCEs in the UE-specific search space set may be configured based on the UE’s identity (e.g., C-RNTI).
  • the UE may determine a time-frequency resource for a CORESET based on RRC messages.
  • the UE may determine a COE-to-REG mapping (e.g., interleaved or non-interleaved, and/or mapping parameters) for the CORESET based on configuration parameters of the CORESET.
  • the UE may determine a number (e.g., at most 10) of search space sets configured on the CORESET based on the RRC messages.
  • the UE may monitor a set of PDCCH candidates according to configuration parameters of a search space set.
  • the UE may determine a DCI as valid for the UE, in response to CRC checking (e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value).
  • CRC checking e.g., scrambled bits for CRC parity bits of the DCI matching a RNTI value.
  • the UE may process information contained in the DCI (e.g., a scheduling assignment, an uplink grant, power control, a slot format indication, a downlink preemption, and/or the like).
  • the UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to a base station.
  • the uplink control signaling may comprise hybrid automatic repeat request (HARQ) acknowledgements for received DL- SCH transport blocks.
  • HARQ hybrid automatic repeat request
  • the UE may transmit the HARQ acknowledgements after receiving a DL-SCH transport block.
  • Uplink control signaling may comprise channel state information (CSI) indicating channel quality of a physical downlink channel.
  • the UE may transmit the CSI to the base station.
  • the base station based on the received CSI, may determine transmission format parameters (e.g., comprising multi-antenna and beamforming schemes) for a downlink transmission.
  • Uplink control signaling may comprise scheduling requests (SR).
  • SR scheduling requests
  • the UE may transmit an SR indicating that uplink data is available for transmission to the base station.
  • the UE may transmit a UCI (e.g., HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).
  • HARQ-ACK HARQ acknowledgements
  • CSI report CSI report
  • SR SR
  • the UE may transmit the uplink control signaling via a PUCCH using one of several PUCCH formats.
  • PUCCH format 0 may have a length of one or two OFDM symbols and may include two or fewer bits.
  • the UE may transmit UCI in a PUCCH resource using PUCCH format 0 if the transmission is over one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK/SR bits) is one or two.
  • PUCCH format 1 may occupy a number between four and fourteen OFDM symbols and may include two or fewer bits.
  • the UE may use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK/SR bits is one or two.
  • PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits.
  • the UE may use PUCCH format 2 if the transmission is over one or two symbols and the number of UCI bits is two or more.
  • PUCCH format 3 may occupy a number between four and fourteen OFDM symbols and may include more than two bits.
  • the UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more and PUCCH resource does not include an orthogonal cover code.
  • PUCCH format 4 may occupy a number between four and fourteen OFDM symbols and may include more than two bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more and the PUCCH resource includes an orthogonal cover code.
  • the base station may transmit configuration parameters to the UE for a plurality of PUCCH resource sets using, for example, an RRC message.
  • the plurality of PUCCH resource sets (e.g., up to four sets) may be configured on an uplink BWP of a cell.
  • a PUCCH resource set may be configured with a PUCCH resource set index, a plurality of PUCCH resources with a PUCCH resource being identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and/or a number (e.g. a maximum number) of UCI information bits the UE may transmit using one of the plurality of PUCCH resources in the PUCCH resource set.
  • a PUCCH resource identifier e.g., pucch-Resourceid
  • TM mode may be used.
  • SRBs Signaling Radio Bearers
  • DRBs Data Radio Bearers
  • RLC layer The services and functions of the RLC layer depend on the transmission mode and comprise:
  • the receiving side of an AM RLC entity may: either discard the received AMD PDU or place it in the reception buffer; and/or if the received AMD PDU was placed in the reception buffer: update state variables, reassemble and deliver RLC SDUs to upper layer (e.g., PDCP and/or RRC) and start/stop t-Reassembly as needed.
  • the receiving side of an AM RLC entity may update state variables and start t-Reassembly as needed.
  • the receiving side of an AM RLC entity may:
  • ARQ procedures may be performed by an AM RLC entity.
  • the transmitting side of an AM RLC entity may receive a negative acknowledgement (e.g., NACK and/or notification of reception failure by its peer AM RLC entity) for an RLC SDU or an RLC SDU segment by the following: STATUS PDU from its peer AM RLC entity.
  • a negative acknowledgement e.g., NACK and/or notification of reception failure by its peer AM RLC entity
  • the transmitting side of the AM RLC entity may:
  • the transmitting side of an AM RLC entity may: if needed, segment the RLC SDU or the RLC SDU segment; and/or may form a new AMD PDU which will fit within the total size of AMD PDU(s) indicated by lower layer at the particular transmission opportunity; and/or may submit the new AMD PDU to lower layer (e.g., MAC).
  • lower layer e.g., MAC
  • the transmitting side of an AM RLC entity may: only map the original RLC SDU or RLC SDU segment to the Data field of the new AMD PDU; and/or may modify the header of the new AMD PDU; and/or may set the P field.
  • An AM RLC entity may poll its peer AM RLC entity in order to trigger STATUS reporting at the peer AM RLC entity.
  • the transmitting side of an AM RLC entity may:
  • the transmitting side of an AM RLC entity may:
  • both the transmission buffer and the retransmission buffer become empty (excluding transmitted RLC SDUs or RLC SDU segments awaiting acknowledgements) after the transmission of the AMD PDU; and/or if no new RLC SDU can be transmitted after the transmission of the AMD PDU (e.g. due to window stalling): o include a poll in the AMD PDU.
  • the transmitting side of an AM RLC entity may: set the P field of the AMD PDU to "1"; and/or may set PDU_WITHOUT_POLL to 0; and/or may set BYTE_WITHOUT_POLL to 0.
  • the transmitting side of an AM RLC entity may: set the P field of the AMD PDU to "1"; and/or may set PDU_WITHOUT_POLL to 0; and/or may set BYTE_WITHOUT_POLL to 0.
  • RLC entity may:
  • the transmitting side of an AM RLC entity may:
  • the STATUS report comprises a positive (e.g., ACK) or negative acknowledgement (e.g., NACK) for the RLC SDU with sequence number equal to POLL_SN and/or if t-Poll Retransmit is running: Stop and reset t- PollRetransmit.
  • ACK positive
  • NACK negative acknowledgement
  • the transmitting side of an AM RLC entity may:
  • both the transmission buffer and the retransmission buffer are empty (excluding transmitted RLC SDU or RLC SDU segment awaiting acknowledgements); and/or if no new RLC SDU or RLC SDU segment can be transmitted (e.g. due to window stalling): o consider the RLC SDU with the highest SN among the RLC SDUs submitted to lower layer for retransmission; and/or consider any RLC SDU which has not been positively acknowledged (e.g., ACKed) for retransmission. o include a poll in an AMD PDU.
  • An AM RLC entity may send STATUS PDUs to its peer AM RLC entity in order to provide positive and/or negative acknowledgements of RLC SDUs (or portions of them).
  • Triggers to initiate STATUS reporting include:
  • the receiving side of an AM RLC entity may trigger a STATUS report when t-Reassembly expires.
  • the receiving side of an AM RLC entity may:
  • t-StatusProhibit at the first transmission opportunity indicated by lower layer (e.g., MAC), construct a STATUS PDU and submit it to lower layer (e.g., MAC). - else: at the first transmission opportunity indicated by lower layer (e.g. , MAC) after t-StatusProhibit expires, construct a single STATUS PDU even if status reporting was triggered several times while t-StatusProhibit was running and submit it to lower layer (e.g., MAC).
  • lower layer e.g., MAC
  • the receiving side of an AM RLC entity may start t-StatusProhibit.
  • the AM RLC entity may:
  • ⁇ include in the STATUS PDU a NACK_SN which is set to the SN of the RLC SDU. o for a continuous sequence of byte segments of a partly received RLC SDU that have not been received yet:
  • ⁇ include in the STATUS PDU a set of NACK_SN and NACK range
  • the length of the SO end (SOend) field may be 16 bits.
  • the SOend field may indicate the position of the last byte of the portion of the RLC SDU in bytes within the original RLC SDU.
  • the first byte of the original RLC SDU is referred by the SOend field value "0000000000000000", i.e., numbering starts at zero.
  • the special SOend value "1111111111111111” is used to indicate that the missing portion of the RLC SDU includes all bytes to the last byte of the RLC SDU.
  • the SOend field indicates the position of the last byte of the portion of the RLC SDU in bytes within the original RLC SDU.
  • the first byte of the original RLC SDU is referred by the SOend field value "0000000000000000", e.g., numbering starts at zero.
  • the special SOend value "1111111111111111” is used to indicate that the missing portion of the RLC SDU includes all bytes to the last byte of the RLC SDU.
  • the length of the Extension bit 3 (E3) field may be 1 bit.
  • the E3 field may indicate whether or not information about a continuous sequence of RLC SDUs that have not been received follows.
  • the interpretation of the E2 field is provided in Table 8.
  • the length of the NACK range field may be 8 bits. This NACK range field may be the number of consecutively lost RLC SDUs starting from and including NACK_SN.
  • the state variables related to AM data transfer may take values from 0 to 4095 for 12 bit SN and/or from 0 to 262143 for 18 bit SN.
  • the state variables related to UM data transfer may take values from 0 to 63 for 6 bit SN or from 0 to 4095 for 12 bit SN.
  • a modulus base may be used.
  • TX_Next_Ack and RX_Next may be assumed as the modulus base at the transmitting side and receiving side of an AM RLC entity, respectively. This modulus base may besubtracted from all the values involved, and then an absolute comparison is performed.
  • RX_Next_Highest- UM_Window_Size may be assumed as the modulus base at the receiving UM RLC entity. This modulus base may be subtracted from all the values involved, and then an absolute comparison is performed.
  • the transmitting side of each AM RLC entity may maintain the following state variables:
  • TX_Next_Ack may be referred to as Acknowledgement (ACK) state variable and vice versa.
  • TX_Next may be referred to as Send state variable and vice versa.
  • - POLL_SN may be referred to as Poll send state variable and vice versa.
  • the POLL_SN state variable may hold the value of the highest SN of the AMD PDU among the AMD PDUs submitted to lower layer when POLL_SN is set. It is initially set to 0.
  • the transmitting side of each AM RLC entity may maintain the following counters:
  • PDU_WITHOUT_POLL may be referred to as a PDU Poll Counter and vice versa.
  • the PDU_WITHOUT_POLL counter may be initially set to 0. It counts the number of AMD PDUs sent since the most recent poll bit was transmitted.
  • BYTE_WITHOUT_POLL may be referred to as a Byte Poll Counter and vice versa.
  • the BYTE_WITHOUT_POLL counter may be initially set to 0. It counts the number of data bytes sent since the most recent poll bit was transmitted.
  • - RETX_COUNT may be referred to as a Retransmission Counter and vice versa.
  • the - RETX_COUNT counter counts the number of retransmissions of an RLC SDU or RLC SDU segment. There is one RETX_COUNT counter maintained per RLC SDU.
  • RX_Next may be referred to as a Receive state variable and vice versa.
  • RX_Next_Statu s_T rigger may be referred to as a t-Reassembly state variable and vice versa.
  • the RX_Next_Status_T rigger state variable holds the value of the SN following the SN of the RLC SDU which triggered t-Reassembly.
  • RX_Highest_Status may be referred to as a Maximum STATUS transmit state variable and vice versa.
  • the RX_Highest_Status state variable holds the highest possible value of the SN which can be indicated by "ACK_SN" when a STATUS PDU needs to be constructed. It is initially set to 0.
  • RX_Next_Highest may be referred to as a Highest received state variable and vice versa.
  • the RX_Next_Highest state variable holds the value of the SN following the SN of the RLC SDU with the highest SN among received RLC SDUs. It is initially set to 0.
  • Each transmitting UM RLC entity shall maintain the following state variables:
  • Each receiving UM RLC entity shall maintain the following state variables:
  • RX_Next_ Reassembly may be referred to as a UM receive state variable and vice versa.
  • RX_Next_ Reassembly state variable holds the value of the earliest SN that is still considered for reassembly. It is initially set to 0. For groupcast and broadcast of NR sidelink communication or for SL-SRB4 of NR sidelink discovery, it is initially set to the SN of the first received UMD PDU containing an SN. For the receiving UM RLC entity configured for MCCH or MTCH, it is up to UE implementation to set the initial value of RX_Next_ Reassembly to a value before RX_Next_Highest.
  • RX_Timer_T rigger may be referred to as a UM t-Reassembly state variable and vice versa.
  • the RX_Timer_T rigger state variable holds the value of the SN following the SN which triggered t-Reassembly.
  • RX_Next_Highest may be referred to as a UM receive state variable and vice versa.
  • the RX_Next_Highest state variable holds the value of the SN following the SN of the UMD PDU with the highest SN among received UMD PDUs. It serves as the higher edge of the reassembly window. It is initially set to 0.
  • the AM_Window_Size constant may be used by both the transmitting side and the receiving side of each AM RLC entity.
  • timers may be configured by RRC/BS configuration parameters:
  • the t-PollRetransmit timer may be used by the transmitting side of an AM RLC entity in order to retransmit a poll.
  • the t-Poll Retransm it timer may be referred to as a Retransmission timer and vice versa.
  • the t-Reassembly timer may be used by the receiving side of an AM RLC entity and receiving UM RLC entity in order to detect loss of RLC PDUs at lower layer. If t-Reassembly is running, t-Reassembly shall not be started additionally, i.e. only one t-Reassembly per RLC entity is running at a given time.
  • the t-Poll Retransmit timer may be referred to as a Reassembly timer and vice versa.
  • the t-StatusProhibit timer may be used by the receiving side of an AM RLC entity in order to prohibit transmission of a STATUS PDU.
  • the t-StatusProhibit timer may be referred to as a prohibit timer and vice versa.
  • PDU Set Error Rate may define an upper bound for a rate of non-congestion related PDU Set losses between RAN and the UE.
  • a PDU set may be considered as successfully delivered only when all PDUs of a PDU Set are delivered successfully, and if the PSER is available, the usage of PSER supersedes the usage of PER.
  • - Channel-based representation using multiple microphones to capture sounds from different directions and post-processing techniques are well known in the industry, as they have been the standard for decades.
  • - Object-based representations represent a complex auditory scene as a collection of single audio elements, each comprising an audio waveform and a set of associated parameters or metadata.
  • the metadata embody the artistic intent by specifying the transformation of each of the audio elements to playback by the final reproduction system.
  • Sound objects generally use monophonic audio tracks that have been recorded or synthesized through a process of sound design. These sound elements can be further manipulated, so as to be positioned in a horizontal plane around the listener, or in full three-dimensional space using positional metadata.
  • XR applications require highly accurate, low-latency tracking of the device at about 1 kHz sampling frequency.
  • the size of a XR Viewer Pose associated to time typically results in packets of size in the range of 30-100 bytes, such that the generated data is around several hundred kbit/s if delivered over the network with latency requirements in the range of 10-20ms.
  • Pose information has to be delivered with ultra-high reliability, therefore, similar performance as URLLO is expected, e.g., packet loss rate may be lower than 10E-4 for uplink sensor data.
  • PSDB PDU Set Delay Budget
  • PSER PDU Set Error Rate
  • a PDU set may be considered as successfully delivered only when all PDUs of a PDU Set are delivered successfully.
  • PDU Set Integrated Handling Information PSI HI: indicates whether all PDUs of the PDU Set are needed for the usage of PDU Set by application layer.
  • the PDU Set QoS parameters may be common for all PDU Sets within a QoS flow.
  • PSI PDU Set Importance
  • the following traffic assistance information may be provided by 5GC to the gNB:
  • GTP-U GPRS Tunnelling Protocol-User Plan
  • the UE may need to be able to identify PDU Sets and Data Bursts dynamically, including PSI.
  • PSI Packet Control Interconnect
  • the PSI HI is set for a QoS flow, as soon as the number of one PDUs of a PDU set is known to be lost exceeds this number, the remaining PDUs of that PDU Set may be considered as no longer needed by the application and may be subject to discard operation of data.
  • Configured grants may be configured without the need for the UE to monitor possible UL retransmissions, thus increasing the number of power saving opportunities for the UE.
  • One additional buffer size table to reduce the quantization errors in BSR reporting (e.g. for high bit rates): o Whether, for an LOG, the new table can be used in addition to the regular one is configured by the gNB; o When the new table is configured for an LOG, it is used whenever the amount of the buffered data of that LOG is within the range of the new table, otherwise the regular table is used.
  • the PSIHI When the PSIHI is set for a QoS flow, as soon as one PDU of a PDU set is known to be lost, the remaining PDUs of that PDU Set can be considered as no longer needed by the application and may be subject to discard operation at the transmitter to free up radio resources.
  • the UE In uplink, the UE may be configured with PDU Set based discard operation for a specific DRB. When configured, the UE discards all packets in a PDU set when one PDU belonging to this PDU set is discarded, e.g. based on discard timer expiry. In case of congestion, the PSI may be used for PDU set discarding. In uplink, dedicated signaling is used to trigger discard mechanism based on PSI. How SDUs are identified as low importance may be determined by UE. When a PDU Set Importance (PSI) is available, it may be used to classify the PDCP SDUs of a PDU Set.
  • PSI PDU Set Importance
  • the network activates and deactivates PSI-based SDU discard by sending the PSI-Based SDU Discard Activation/Deactivation MAC CE.
  • the PSI-based SDU discard is initially deactivated upon (re-)configuration by upper layers and after reconfiguration with sync.
  • the MAC entity may for each DRB configured with PSI-based SDU discard:
  • UE may receive (e.g., be configured with) a DSR configuration (e.g., LCG-DSR-Config).
  • the DSR configuration may be included in a MAC-CellGroupConfig.
  • the DSR configuration may comprise a LOG ID and/or a threshold (e.g., remainingTimeThreshold).
  • the LOG ID may be associated with the threshold (e.g., remainingTimeThreshold).
  • the LOG ID may be an identifier of the LOG which the DSR configuration refers to.
  • the threshold (e.g., remainingTimeThreshold) may be used for triggering DSR for the LOG.
  • UE may receive (e.g., be configured with) a threshold (e.g., remainingTimeThreshold) on remaining time of UL data configured for triggering DSR for an LOG.
  • the threshold e.g., remainingTimeThreshold
  • the threshold may be configured in a unit of millisecond, second, slot, symbol, subframe.
  • the UE/MAC entity may determine:
  • a MAC PDU may contain at most one DSR MAC CE.
  • the UE/MAC entity shall not include a DSR MAC CE in a MAC PDU if the MAC PDU can accommodate the SDUs associated with all the pending DSRs.
  • DSR MAC CE may comprise one or more data volume information (e.g., via buffer size field) associated with delay information (e.g., remaining time/discard timer value). For example, the UE may transmit DSR MAC CE to report how much data is buffered for which delay value.
  • delay information e.g., remaining time/discard timer value
  • LCGi The LCGi field may indicate the presence of delay information (i.e. the Remaining Time and Buffer Size fields) for the LCG i.
  • the LCGi field set to 1 may indicate that the delay information for the LCG i is reported.
  • the LCGi field set to 0 may indicate that the delay information for the LCG i is not reported;
  • the Remaining Time field may indicate the shortest remaining value of running PDCP discardTimer among all PDCP SDUs that are buffered for an LCG but have not been transmitted in any MAC PDU, at the time of the first symbol of the first PUSCH transmission that includes this DSR MAC CE.
  • the length of this field is 6 bits. This field is present only if the buffer size indicated by the corresponding Buffer Size field is not zero; otherwise, this field is reserved and set to 0. If present, the value r in this field indicates a remaining time within the range of (r, r + 1] msec).
  • BT The BT field may be present only if the corresponding LCG is configured with add ition al B S R- TableAllowed and/or the buffer size indicated by the corresponding Buffer Size field is not zero; otherwise, this field may be reserved and set to 0. If present, the BT field may be set to 1 indicates that the buffer sizes specified in a first table are used to set the value of the Buffer Size field, while the BT field may be set to 0 indicates that the buffer sizes in a second table are used instead.
  • the DSR MAC CE may include delay information of all LCGs which have pending DSRs when the MAC PDU containing this DSR MAC CE is to be built.
  • the Remaining Time, the BT, and the Buffer Size fields for an LCG may be reported in two consecutive octets. These three fields for different LCGs shall be included in a DSR MAC CE in ascending order based on the LCGi.
  • the DSR MAC CE may be identified by MAC subheader with an eLCID.
  • the UE shall estimate the size of the STATUS PDU that will be transmitted in the next transmission opportunity, and consider this as part of RLC data volume for MAC buffer status reporting and as part of delay-critical RLC data volume for MAC delay status reporting.
  • the transmitting PDCP entity may consider the following as delay-critical PDCP data volume:
  • the PDCP Data PDUs to be retransmitted.
  • a PDCP SDU becomes a delay-critical PDCP SDU, and if the corresponding PDCP Data PDU has already been submitted to lower layers, the delay-critical indication for the PDCP Data PDU may be provided to lower layers.
  • the UE/transmitting PDCP entity may maintain the following timers:
  • - dadiscardTimer may be configured only for DRBs.
  • the duration of the timer may be configured by RRC/BS.
  • a new timer may be started upon reception of an SDU from upper layer.
  • - discardTimerForLowl mportance may be configured for SRBs/DRBs.
  • the duration of the timer may be configured by RRC/BS.
  • a new timer may be started upon reception of an SDU belonging to a low importance PDU Set from upper layer.
  • the UE/transmitting PDCP entity may:
  • the UE/transmitting PDCP entity may be: - if pdu-SetDiscard is configured, discard all PDCP SDUs belonging to the PDU Set to which the PDCP SDU belongs along with the corresponding PDCP Data PDUs; else: discard the PDCP SDU along with the corresponding PDCP Data PDU.
  • UE wireless device
  • gNB evolved node
  • NW network node
  • SDAP/RRC/PDCP/RLC/MAC/PHY layer/entity may be a layer/entity of the UE/wireless device.
  • SDAP/RRC/PDCP/RLC/MAC/PHY layer/entity may be a layer/entity of the base station.
  • ID In the present disclosure, the terms “ID”, “index”, “identifier” may be used interchangeably.
  • the terms “indication”, “configuration”, “configuration parameter”, “parameter”, “RRC message”, “RRC configuration”, “RRC configuration parameter”, “RRC parameter”, “information element (IE)”, “MAC control element (CE), “DCI”, “UCI” may be used interchangeably.
  • the UE is configured with a configuration/parameter/IE/RRC message may be referred to as the UE receives the configuration/parameter/IE/RRC message from the BS.
  • Data/Data unit may refer to:
  • the data in this application may be referred to as a data unit.
  • the data unit may be an uplink data unit and/or an downlink data unit.
  • the data unit may be a PDU, a PDU set, a SDU, an IP packet, and/or a data burst.
  • the data unit (e.g., PDU) may be at least one of a SDAP PDU, PDCP PDU, RLC PDU, RLC data PDU, RLC control PDU, MAC PDU, Transport Block (TB).
  • the data unit may be at least one of a SDAP SDU, PDCP SDU, RLC SDU, RLC SDU segment, MAC SDU, PHY SDU.
  • the PDU set may comprise one or more PDUs carrying a payload of one unit of information generated at an application level.
  • the data burst may be a set of multiple PDUs generated and sent by the application in a short period of time.
  • the data burst may comprise one or multiple PDU Sets.
  • the RLC PDU may be either RLC data PDU or RLC control PDU.
  • the data unit may be a delay-critical data unit (e.g., delay-critical RLC SDU and/or delay-critical PDCP SDU).
  • Delay information may refer to:
  • the delay information of a data unit may be referred to as a remaining time of a data unit.
  • the remaining time of a data unit may be determined based on a discard timer value running for the data unit.
  • the remaining time of a data unit may be determined by a PDCP layer of the wireless device.
  • the UE may determine a Logical Channel (LCH)ZLogical Channel Group (LCG) has delay-critical data unit when the UE determines that a (shortest/smallest) remaining time of a data unit among all data units (available for transmission) of the LCH/LCG is shorter/smaller than the one or more thresholds (e.g., remaining time threshold).
  • LCH Logical Channel
  • LCG Logical Channel
  • the UE may determine a LCH/LCG does not have delay-critical data when the UE determines that a (shortest/smallest) remaining time of a data unit among all data units (available for transmission) of the LCH/LCG is not shorter/smaller than the one or more thresholds (e.g. , remaining time threshold).
  • Delay-critical RLC SDU may refer to: RLC SDU corresponding to a PDCP PDU indicated as delay-critical by PDCP.
  • Delay-critical PDCP SDU may refer to: if pdu-SetDiscard is not configured, a PDCP SDU for which the remaining time till discardTimer expiry is less than the remainingTimeThreshold. If pdu-SetDiscard is configured, a PDCP SDU belonging to a PDU Set of which at least one PDCP SDU has the remaining time till discardTimer expiry less than the remainingTimeThreshold.
  • RLC data volume may be the amount of data available for transmission in an RLC entity.
  • RLC SDU segment may be a segment of an RLC SDU.
  • FIG. 19 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • a STATUS report transmitting by receiving RLC entity to transmitting RLC entity, provides ACK/NACK information of each RLC data unit.
  • the transmitting RLC entity may determine whether to retransmit an RLC data unit based on the corresponding ACK/NACK information in the STATUS report.
  • a RLC data unit may become delay-critical. If the RLC data unit becomes delay-critical, the remaining time of the (delay-critical) RLC data unit may be not enough for ARQ retransmission. The transmitting RLC entity may not need to wait for ACK/NACK information for the delay-critical RLC data units. Thus, the ACK/NACK information, for the delay-critical RLC data units, included in the STATUS report is useless and increases the size of the STATUS report PDU, which results in the overhead of the resource usage. [0417] Embodiments of the present disclosure are related to an approach for solving the problems described above. These and other features of the present disclosure are described further below.
  • the transmitting RLC entity may transmit an indication/notification to receiving RLC entity to indicate that one or more of RLC data units becomes delay-critical (and/or no need for ACK/NACK included in STATUS report).
  • a data unit may be a RLC data unit.
  • a data unit may be a RLC PDU.
  • a RLC PDU may comprise AMD PDU, UMD PDU, and/or TMD PDU.
  • a RLC PDU may comprise a RLC SDU and header.
  • a RLC PDU may be associated with (corresponding to) a RLC SDU.
  • a data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) may comprise a data filed an and a header (e.g., AMD PDU header).
  • a header e.g., AMD PDU header
  • the header (e.g., AMD PDU header), of the data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment), may comprise a SN field.
  • the data unit e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the SN field may indicate the sequence number of the corresponding RLC SDU.
  • the SN may be incremented by one for every RLC SDU.
  • FIG. 20 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • a transmitting entity e.g., a UE, a BS, a AM RLC entity, a transmitting AM RLC entity, a PDCP entity, and/or a MAC entity
  • may transmit an indication e.g., to a receiving entity (e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity).
  • the indication may indicate that one or more data units (and/or one or more SNs associated with one or more data units) are delay-critical or not.
  • a first value e.g., 1
  • a second value e.g., 0
  • the indication may indicate that one or more data units (and/or one or more SNs associated with one or more data units) need ACK/NACK information or not.
  • a first value e.g., 1
  • a second value e.g., 0
  • the ACK/NACK information may be used for a STATUS report.
  • the indication may indicate that one or more data units (and/or one or more SNs associated with one or more data units) need (re-)transmission or not.
  • a first value e.g., 1
  • a second value e.g., 0
  • the indication may indicate that one or more data units (and/or one or more SNs associated with one or more data units) are discarded or not.
  • a first value e.g., 1
  • a second value e.g., 0
  • the indication may be a report, a message, a notification, a UE assistance information, a UE capability, and/or a configuration.
  • the indication may comprise delay information (e.g., delay-critical), SNs information, data units’ information, discard data units (SNs) information, missing data units (SNs) information, (segment) offset of SNs (of data units), a first SN (of a data unit), a last SN (of a data unit), a range of SNs (of data units), a number/quantity of SNs (of data units).
  • delay information e.g., delay-critical
  • SNs information e.g., data-critical
  • SNs information e.g., data-critical
  • data units e.g., data units’ information
  • discard data units (SNs) information e.g., missing data units (SNs) information
  • SNs missing data units
  • (segment) offset of SNs (of data units) e.g., a first SN (of a data unit), a last SN (of a data unit), a range of SN
  • the one or more data units may be associated with continues SNs and/or interleaved SNs.
  • the one or more data units may be delay- critical data units.
  • the one or more data units may be non- delay-critical data units.
  • the one or more data units (and/or one or more SNs associated with one or more data units) may be discarded.
  • the range of SNs may comprise a first SN (of a data unit) and a last SN (of a data unit).
  • the indication may be indicated by a RLC PDU, a RLC data PDU, a RLC control PDU.
  • the indication may be indicated by a TMD PDU, a UMD data PDU, an AMD data PDU.
  • the indication may be indicated by a header (e.g., of a TMD PDU, a UMD data PDU, and/or an AMD data PDU).
  • the indication may comprise one or more fields.
  • the indication may comprise delay information field.
  • the indication may comprise one or more fields.
  • the indication may comprise ACK/NACK information of one or more data unit (and/or one or more SNs associated with the one or more data units).
  • the indication may comprise Data/Control (D/C) field.
  • the length of the Data/Control (D/C) field may be 1 bit.
  • the D/C field may indicate whether the RLC PDU is an RLC data PDU or RLC control PDU.
  • the indication may comprise Extension bit 1 (E1) field.
  • the length of the Extension bit 1 (E1) field may be 1 bit.
  • the E1 field may indicate whether or not a set of NACK_SN, E1 , E2 and E3 follows. The interpretation of the E1 field is provided in Table 6.
  • the indication may comprise Extension bit 3 (E3) field.
  • the length of the Extension bit 3 (E3) field may be 1 bit.
  • the E3 field may indicate whether or not information about a continuous sequence of RLC SDUs that have not been received follows. The interpretation of the E2 field is provided in Table 8.
  • the indication may comprise Reserved (R) field.
  • the length of the Reserved (R) field may be 1 bit.
  • the R field may be a reserved field.
  • the transmitting entity may set the R field to "0".
  • the receiving entity may ignore this field.
  • the indication may comprise Negative Acknowledgement SN (NACK_SN) field.
  • the length of the Negative Acknowledgement SN (NACK_SN) field may be 12 bits or 18 bits (which may be configurable, e.g, by RRC/BS).
  • the NACK_SN field may indicate the SN of the RLC SDU (and/or RLC SDU segment) that has been detected as lost at the receiving side of the AM RLC entity.
  • the indication may comprise SO start (SOstart) field.
  • the length of the SO start (SOstart) field may be 16 bits.
  • the SOstart field may indicate the position of the first byte of the portion of the RLC SDU in bytes within the original RLC SDU.
  • the first byte of the original RLC SDU is referred by the SOstart field value "0000000000000000", e.g., numbering starts at zero.
  • the indication may comprise SO end (SOend) field.
  • the length of the SO end (SOend) field may be 16 bits.
  • the SOend field may indicate the position of the last byte of the portion of the RLC SDU in bytes within the original RLC SDU.
  • the first byte of the original RLC SDU is referred by the SOend field value "0000000000000000", i.e, numbering starts at zero.
  • the special SOend value "1111111111111111” is used to indicate that the missing portion of the RLC SDU includes all bytes to the last byte of the RLC SDU.
  • the SOend field indicates the position of the last byte of the portion of the RLC SDU in bytes within the original RLC SDU.
  • the first byte of the original RLC SDU is referred by the SOend field value "0000000000000000", e.g, numbering starts at zero.
  • the special SOend value "1111111111111111” is used to indicate that the missing portion of the RLC SDU includes all bytes to the last byte of the RLC SDU.
  • the indication may comprise NACK range field.
  • the length of the NACK range field may be 8 bits. This NACK range field may be the number of consecutively lost RLC SDUs starting from and including NACK_SN.
  • a receiving entity e.g, a UE, a BS, an AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g, status report
  • a receiving entity e.g., a UE, a BS, an AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, an AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, an AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, an AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, an AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, an AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • the report (e.g., status report) may comprise ACK/NACK information of one or more data unit (and/or one or more SNs associated with the one or more data units).
  • the report may comprise Control PDU Type (CPT) field.
  • the length of the Control PDU Type (CPT) field may be 3 bits.
  • the CPT field may indicate the type of the RLC control PDU. The interpretation of the CPT field is provided in Table 5.
  • the report may comprise Acknowledgement SN (ACK_SN) field.
  • the length of the Acknowledgement SN (ACK_SN) field may be 12 bits or 18 bits (which may be configurable, e.g., by RRC/BS).
  • the ACK_SN field may indicate the SN of the next not received RLC SDU which is not reported as missing in the STATUS PDU.
  • the report may comprise Extension bit 2 (E2) field.
  • the length of the Extension bit 2 (E2) field may be 1 bit.
  • the E2 field may indicate whether or not a set of SOstart and SOend follows. The interpretation of the E2 field is provided in Table 7.
  • the report may comprise Extension bit 3 (E3) field.
  • the length of the Extension bit 3 (E3) field may be 1 bit.
  • the E3 field may indicate whether or not information about a continuous sequence of RLC SDUs that have not been received follows. The interpretation of the E2 field is provided in Table 8.
  • the report may comprise Negative Acknowledgement SN (NACK_SN) field.
  • the length of the Negative Acknowledgement SN (NACK_SN) field may be 12 bits or 18 bits (which may be configurable, e.g., by RRC/BS).
  • the NACK_SN field may indicate the SN of the RLC SDU (and/or RLC SDU segment) that has been detected as lost at the receiving side of the AM RLC entity.
  • the report (e.g., status report) may comprise SO start (SOstart) field.
  • the length of the SO start (SOstart) field may be 16 bits.
  • the report (e.g., status report) may comprise NACK range field.
  • the length of the NACK range field may be 8 bits.
  • This NACK range field may be the number of consecutively lost RLC SDUs starting from and including NACK_SN.
  • FIG. 23 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may receive an indication e.g., from a transmitting entity (e.g., a UE, a BS, a AM RLC entity, a transmitting AM RLC entity, a PDCP entity, and/or a MAC entity).
  • a transmitting entity e.g., a UE, a BS, a AM RLC entity, a transmitting AM RLC entity, a PDCP entity, and/or a MAC entity.
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • FIG. 26 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a state variable e.g., as shown in FIG.
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • the state variable may be maintained/used by RLC entity, AM RLC entity, UM RLC entity, TM RLC entity, transmitting AM RLC entity, receiving AM RLC entity, transmitting UM RLC entity, and/or receiving UM RLC entity.
  • the state variable may be maintained/used for a transmitting window.
  • the UE e.g., RLC entity/AM RLC entity/transmitting AM RLC entity/receiving AM RLC entity
  • the UE may maintain/update the transmitting window based on the state variable.
  • the state variable may be used for determining a lower edge SN of the transmitting window.
  • the state variable may be used for determining an upper edge SN of the transmitting window.
  • the state variable may be used for determining an upper edge SN of the receiving window.
  • the state variable may be an Acknowledgement (ACK) state variable (e.g., TX_Next_Ack).
  • the state variable may be a Send state variable (e.g., TX_Next).
  • the state variable may be a counter.
  • the state variable may be a PDU Poll Counter (e.g., PDU_WITHOUT_POLL).
  • the state variable may be a Byte Poll Counter (e.g., BYTE_WITHOUT_POLL).
  • the state variable may be a Retransmission Counter (e.g., RETX_COUNT).
  • the state variable may be a Receive state variable (e.g., RX_Next).
  • the state variable may be a t-Reassembly state variable (e.g., RX_Next_Status_T rigger).
  • the state variable may be a Maximum STATUS transmit state variable (e.g., RX_Highest_Status).
  • the state variable may be a Highest received state variable (e.g., RX_Next_Highest).
  • the state variable may be a UM send state variable (e.g., TX_Next).
  • the state variable may be a UM receive state variable (e.g., RX_Next_ Reassembly).
  • the state variable may be a UM t-Reassembly state variable (e.g., RX_Timer_T rigger).
  • the state variable may be a UM receive state variable (e.g., RX_Next_Highest).
  • the state variable may be based on a configuration parameter (e.g., received from RRC/BS).
  • the state variable may be maintained/used for ARQ and/or polling.
  • the UE e.g., RLC entity/AM RLC entity/transmitting AM RLC entity/receiving AM RLC entity
  • may determine whether to retransmit a data unit e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • a data unit e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the UE may determine whether to include a poll (e.g., set a polling bitfield to 0/1 in an AMD PDU) based on the state variable.
  • a poll e.g., set a polling bitfield to 0/1 in an AMD PDU
  • the state variable may be maintained/used for (re-)segmentation.
  • the UE e.g., RLC entity/AM RLC entity/transmitting AM RLC entity/receiving AM RLC entity
  • the UE may determine whether to (re- )segment a data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) based on the state variable.
  • a data unit e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the state variable may be maintained/used for discarding one or more data units.
  • the UE e.g., RLC entity/AM RLC entity/transmitting AM RLC entity/receiving AM RLC entity
  • may determine whether to discard one or more data units e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the state variable may be maintained/used for discarding one or more data units.
  • the UE e.g., RLC entity/AM RLC entity/transmitting AM RLC entity/receiving AM RLC entity
  • may determine whether to discard one or more data units e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the state variable may be maintained/used for a transmission buffer.
  • the state variable may be used for a retransmission buffer.
  • FIG. 27 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may receive an indication e.g., from a transmitting entity (e.g., a UE, a BS, a AM RLC entity, a transmitting AM RLC entity, a PDCP entity, and/or a MAC entity).
  • a transmitting entity e.g., a UE, a BS, a AM RLC entity, a transmitting AM RLC entity, a PDCP entity, and/or a MAC entity.
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may determine whether to trigger/transmit a report e.g., status report
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may determine to trigger/transmit a report e.g., status report
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may determine to trigger/transmit a report e.g., status report
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may determine to trigger/transmit a report e.g., status report
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may determine to trigger/transmit a report e.g., status report
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may determine whether to trigger/transmit a report e.g., status report
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may determine to trigger/transmit a report e.g., status report
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may determine to trigger/transmit a report e.g., status report
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may determine to trigger/transmit a report e.g., status report
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may determine to trigger/transmit a report e.g., status report
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may determine to trigger/transmit a report e.g., status report
  • a report e.g., status report
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may determine to trigger/transmit a report e.g., status report
  • a report e.g., status report
  • FIG. 29 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • may receive an indication e.g., from a transmitting entity (e.g., a UE, a BS, a AM RLC entity, a transmitting AM RLC entity, a PDCP entity, and/or a MAC entity).
  • a transmitting entity e.g., a UE, a BS, a AM RLC entity, a transmitting AM RLC entity, a PDCP entity, and/or a MAC entity.
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • FIG. 30 illustrates an example as per an aspect of an embodiment of the present disclosure.
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a receiving entity e.g., a UE, a BS, a AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • the timer may be a poll timer (e.g., t-PollRetransmit timer).
  • the timer may be a retransmission timer (e.g., t-PollRetransmit timer).
  • the timer may be a reassembly timer (e.g., t-Reassembly timer).
  • the timer may be a status timer (e.g., t-StatusProhibit timer).
  • the timer may be a prohibit timer (e.g., t-StatusProhibit timer).
  • the timer may be a discard timer (e.g., discardTimer, discardTimerExt, dicardTimerExt2, and/or discardTimerForLowl mportance).
  • discardTimer e.g., discardTimer, discardTimerExt, dicardTimerExt2, and/or discardTimerForLowl mportance.
  • the timer may be performed, (re-)start, stop, and/or reset a timer by a RLC entity, PDCP entity, and/or MAC entity of the wireless device.
  • a transmitting entity e.g., a UE, a BS, an AM RLC entity, a receiving AM RLC entity, a PDCP entity, and/or a MAC entity
  • a report e.g., status report
  • a transmitting entity e.g., a UE, a BS, a AM RLC entity, a transmitting AM RLC entity, a PDCP entity, and/or a MAC entity
  • a transmitting entity e.g., a UE, a BS, a AM RLC entity, a transmitting AM RLC entity, a PDCP entity, and/or a MAC entity
  • a transmitting entity e.g., a UE, a BS, a AM RLC entity, a transmitting AM RLC entity, a PDCP entity, and/or a MAC entity
  • a transmitting entity e.g., a UE, a BS, a AM RLC entity, a transmitting AM RLC entity, a PDCP entity, and/or a MAC entity
  • ACK/NACK information e.g., indicated as NACK
  • a report e.g., status report
  • the data unit may be a non-delay-critical data unit (e.g., non-delay-critical RLC SDU and/or non-delay-critical PDCP SDU).
  • the data unit may be referred to as one or more data units.
  • the one or more data units may be one or more RLC data units/RLC PDUs/AMD PDUs/RLC SDUs/RLC SDU segments.
  • the one or more data units may be associated with a PDU set/data burst.
  • the data unit may be a data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) that are pending for retransmission.
  • the data unit may be a data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) that has been (and/or was) submitted to lower layer (e.g., MAC and/or PHY) and/or that has not been (and/or was not) submitted to lower layer (e.g., MAC and/or PHY).
  • RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment that has been (and/or was) submitted to lower layer (e.g., MAC and/or PHY).
  • the data unit may be a data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) that was previously submitted to lower layer (e.g., MAC and/or PHY) and/or that was not previously submitted to lower layer (e.g., MAC and/or PHY).
  • RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the data unit may be a data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) that the UE (e.g., RLC entity/AM RLC entity/transmitting AM RLC entity) is waiting for an ACK/NACK for the data unit (and/or has not received an ACK/NACK for the data unit yet).
  • a data unit e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the UE e.g., RLC entity/AM RLC entity/transmitting AM RLC entity
  • the data unit may be a data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) that the UE (e.g., RLC entity/AM RLC entity/transmitting AM RLC entity) has received an ACK/NACK for the data unit).
  • a data unit e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the UE e.g., RLC entity/AM RLC entity/transmitting AM RLC entity
  • the data unit may be a data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) that has not yet been included in an RLC data PDU.
  • RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the data unit may be a data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) that will be transmitted in the next transmission opportunity.
  • RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the data unit e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the data unit may be associated with a SN.
  • the data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) may be associated with a SN, wherein the SN may be equal to a state variable.
  • the data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) may be associated with a SN, wherein the SN may be larger than a state variable.
  • the state variable may be a Receive state variable (e.g., RX_Next).
  • the state variable may be a t-Reassembly state variable (e.g., RX_Next_Status_T rigger).
  • the state variable may be a Maximum STATUS transmit state variable (e.g., RX_Highest_Status).
  • the state variable may be a Highest received state variable (e.g., RX_Next_Highest).
  • the state variable may be a UM send state variable (e.g., TX_Next).
  • the state variable may be a UM receive state variable (e.g., RX_Next_ Reassembly).
  • the state variable may be a UM t-Reassembly state variable (e.g., RX_Timer_T rigger).
  • the state variable may be a UM receive state variable (e.g., RX_Next_Highest).
  • the state variable may be based on a configuration parameter (e.g., received from RRC/BS).
  • the data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) may be associated with a SN, wherein the SN may fall within a range of the transmitting window.
  • the data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) may be associated with a SN, wherein the SN may be equal to or larger than a lower edge SN of the transmitting window.
  • the data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) may be associated with a SN, wherein the SN may be equal to or lower than an upper edge SN of the transmitting window.
  • the data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) may be associated with a SN, wherein the SN may be equal to or larger than a first state variable and/or equal to or lower than a second state variable.
  • the (first/second) state variable may be an Acknowledgement (ACK) state variable (e.g., TX_Next_Ack).
  • the (first/second) state variable may be a Send state variable (e.g., TX_Next).
  • the (first/second) state variable may be a counter.
  • the (first/second) state variable may be a PDU Poll Counter (e.g., PDU_WITHOUT_POLL).
  • the (first/second) state variable may be a Retransmission Counter (e.g., RETX_COUNT).
  • the (first/second) state variable may be a Receive state variable (e.g., RX_Next).
  • the (first/second) state variable may be a Maximum STATUS transmit state variable (e.g.,
  • the (first/second) state variable may be a UM send state variable (e.g., TX_Next)
  • the (first/second) state variable may be a UM receive state variable (e.g., RX_Next_ Reassembly).
  • the (first/second) state variable may be based on a configuration parameter (e.g., received from RRC/BS).
  • the UE may determine a data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) as a delay-critical data unit based on a timer and/or a threshold.
  • a data unit e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the UE may determine a data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) as a delay-critical data unit when a PDCP SDU for which the remaining time till a timer (e.g., discardTimer) expiry is less than a threshold (e.g., remainingTimeThreshold) (e.g., if a configuration parameter (e.g., pdu-SetDiscard) is not configured,).
  • a data unit e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • a threshold e.g., remainingTimeThreshold
  • the UE may determine a data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) as a delay-critical data unit if the data unit corresponding to a PDCP PDU indicated as delay-critical by PDCP.
  • a data unit e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) may be associated with the specific value/SN.
  • the specific value/SN may be associated with the data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment).
  • One or more or all SNs, associated with one or more or all data units, are smaller than (and/or equal to) the specific value/SN.
  • the one or more or all data units are delay-critical data units and/or the one or more or all data units are not delay-critical data units.
  • the data unit (e.g., RLC data unit/RLC PDU/RLO data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) may be associated with the specific value/SN.
  • the specific value/SN may be associated with the data unit (e.g., RLC data unit/RLC PDU/RLO data PDU/RLO control PDU/AMD PDU/RLC SDU/RLC SDU segment).
  • One or more or all SNs, associated with one or more or all data units, are larger than (and/or equal to) the specific value/SN.
  • the one or more or all data units are delay-critical data units.
  • the one or more or all data units are not delay- critical data units.
  • the state variable may be maintained/used by RLC entity, AM RLC entity, UM RLC entity, TM RLC entity, transmitting AM RLC entity, receiving AM RLC entity, transmitting UM RLC entity, and/or receiving UM RLC entity.
  • the state variable may be maintained/used for a transmitting window.
  • the UE e.g., RLC entity/AM RLC entity/transmitting AM RLC entity/receiving AM RLC entity
  • the UE may maintain/update the transmitting window based on the state variable.
  • the state variable may be used for determining an upper edge SN of the transmitting window.
  • the state variable may be a t-Reassembly state variable (e.g., RX_Next_Status_T rigger).
  • the state variable may be a Maximum STATUS transmit state variable (e.g., RX_Highest_Status).
  • the state variable may be a Highest received state variable (e.g., RX_Next_Highest).
  • the state variable may be a UM send state variable (e.g., TX_Next).
  • the state variable may be a UM receive state variable (e.g., RX_Next_ Reassembly).
  • the state variable may be a UM t-Reassembly state variable (e.g., RX_Timer_T rigger).
  • the state variable may be a UM receive state variable (e.g., RX_Next_Highest).
  • the state variable may be based on a configuration parameter (e.g., received from RRC/BS).
  • the state variable may be maintained/used for ARQ and/or polling.
  • the UE e.g., RLC entity/AM RLC entity/transmitting AM RLC entity/receiving AM RLC entity
  • may determine whether to retransmit a data unit e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • a data unit e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the UE may determine whether to include a poll (e.g., set a polling bitfield to 0/1 in an AMD PDU) based on the state variable.
  • a poll e.g., set a polling bitfield to 0/1 in an AMD PDU
  • the state variable may be maintained/used for (re-)segmentation.
  • the UE e.g., RLC entity/AM RLC entity/transmitting AM RLC entity/receiving AM RLC entity
  • the UE may determine whether to (re- )segment a data unit (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) based on the state variable.
  • a data unit e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the state variable may be maintained/used for discarding one or more data units.
  • the UE e.g., RLC entity/AM RLC entity/transmitting AM RLC entity/receiving AM RLC entity
  • may determine whether to discard one or more data units e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the state variable may be maintained/used for discarding one or more data units.
  • the UE e.g., RLC entity/AM RLC entity/transmitting AM RLC entity/receiving AM RLC entity
  • may determine whether to discard one or more data units e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • the timer may be a poll timer (e.g., t-PollRetransmit timer).
  • the timer may be a retransmission timer (e.g., t-PollRetransmit timer).
  • the timer may be a status timer (e.g., t-StatusProhibit timer).
  • the timer may be a prohibit timer (e.g., t-StatusProhibit timer).
  • the timer may be performed, (re-)start, stop, and/or reset a timer by a RLC entity, PDCP entity, and/or MAC entity of the wireless device.
  • a UE may prioritize transmission of RLC control PDUs over AMD PDUs.
  • a UE may prioritize transmission of delay-critical data units (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) over non-delay-critical data units (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment).
  • delay-critical data units e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • non-delay-critical data units e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment.
  • a UE may prioritize transmission of delay-critical data units (e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment) over at least one of: (non-delay-critical) RLC control PDUs, AMD PDUs, AMD PDUs containing previously transmitted RLC SDUs or RLC SDU segments, AMD PDUs containing not previously transmitted RLC SDUs or RLC SDU segments.
  • delay-critical data units e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • delay-critical data units e.g., RLC data unit/RLC PDU/RLC data PDU/RLC control PDU/AMD PDU/RLC SDU/RLC SDU segment
  • delay-critical data units e.g., RLC data unit/RLC PDU/RLC data PDU/
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to transmit an indication indicating that one or more data units (and/or one or more SNs associated with one or more data units) are delay-critical or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to transmit an indication indicating that one or more data units (and/or one or more SNs associated with one or more data units) need (re-)transmission or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to transmit an indication indicating that one or more data units (and/or one or more SNs associated with one or more data units) need to be included in a STATUS report or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to transmit an indication indicating that one or more data units (and/or one or more SNs associated with one or more data units) are missing or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to determine that one or more data units (and/or one or more SNs associated with one or more data units) are delay-critical or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to determine that one or more data units (and/or one or more SNs associated with one or more data units) need ACK/NACK information or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to determine that one or more data units (and/or one or more SNs associated with one or more data units) need (re-)transmission or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to determine that one or more data units (and/or one or more SNs associated with one or more data units) need to be included in a STATUS report or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to determine that one or more data units (and/or one or more SNs associated with one or more data units) are discarded or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to include/exclude ACK/NACK information of one or more data units in/from a report (e.g., status report) based on the indication.
  • a report e.g., status report
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to include/exclude ACK/NACK information of one or more data units in/from a report (e.g., status report) based on one or more data units (and/or one or more SNs associated with one or more data units) need (re-)transmission or not.
  • a report e.g., status report
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to include/exclude ACK/NACK information of one or more data units in/from a report (e.g., status report) based on one or more data units (and/or one or more SNs associated with one or more data units) are discarded or not.
  • a report e.g., status report
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to include/exclude ACK/NACK information of one or more data units in/from a report (e.g., status report) based on one or more data units (and/or one or more SNs associated with one or more data units) are missing or not.
  • a report e.g., status report
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to consider one or more data units as ACK/NACK.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to consider one or more data units as ACK/NACK based on one or more data units (and/or one or more SNs associated with one or more data units) need to be included in a STATUS report or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to consider one or more data units as ACK/NACK based on one or more data units (and/or one or more SNs associated with one or more data units) are discarded or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to update a state variable (and/or set the state variable to a value) based on the indication.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to update a state variable (and/or set the state variable to a value) based on one or more data units (and/or one or more SNs associated with one or more data units) are delay-critical or not
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to update a state variable (and/or set the state variable to a value) based on one or more data units (and/or one or more SNs associated with one or more data units) need ACK/NACK information or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to update a state variable (and/or set the state variable to a value) based on one or more data units (and/or one or more SNs associated with one or more data units) need (re-)transmission or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to update a state variable (and/or set the state variable to a value) based on one or more data units (and/or one or more SNs associated with one or more data units) need to be included in a STATUS report or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to update a state variable (and/or set the state variable to a value) based on one or more data units (and/or one or more SNs associated with one or more data units) are discarded or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to update a state variable (and/or set the state variable to a value) based on one or more data units (and/or one or more SNs associated with one or more data units) are missing or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to trigger/transmit a report (e.g., status report) based on one or more data units (and/or one or more SNs associated with one or more data units) are delay-critical or not
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to trigger/transmit a report (e.g., status report) based on one or more data units (and/or one or more SNs associated with one or more data units) need ACK/NACK information or not.
  • a report e.g., status report
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to trigger/transmit a report (e.g., status report) based on one or more data units (and/or one or more SNs associated with one or more data units) need (re-)transmission or not.
  • a report e.g., status report
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to trigger/transmit a report (e.g., status report) based on one or more data units (and/or one or more SNs associated with one or more data units) need to be included in a STATUS report or not.
  • a report e.g., status report
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to trigger/transmit a report (e.g., status report) based on one or more data units (and/or one or more SNs associated with one or more data units) are discarded or not.
  • a report e.g., status report
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to trigger/transmit a report (e.g., status report) based on one or more data units (and/or one or more SNs associated with one or more data units) are missing or not.
  • a report e.g., status report
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to (re-)start/stop/reset a timer based on the indication.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to (re-)start/stop/reset a timer based on one or more data units (and/or one or more SNs associated with one or more data units) are delay-critical or not
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to (re-)start/stop/reset a timer based on one or more data units (and/or one or more SNs associated with one or more data units) need ACK/NACK information or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to (re-)start/stop/reset a timer based on one or more data units (and/or one or more SNs associated with one or more data units) need (re-)transmission or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to (re-)start/stop/reset a timer based on one or more data units (and/or one or more SNs associated with one or more data units) need to be included in a STATUS report or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to (re-)start/stop/reset a timer based on one or more data units (and/or one or more SNs associated with one or more data units) are discarded or not.
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to ignore ACK/NACK information (and/or consider as ACK for all the ACK/NACK) of one or more data units in/from a report (e.g., status report) based on one or more data units (and/or one or more SNs associated with one or more data units) are delay-critical or not
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to ignore ACK/NACK information (and/or consider as ACK for all the ACK/NACK) of one or more data units in/from a report (e.g., status report) based on one or more data units (and/or one or more SNs associated with one or more data units) need (re-)transmission or not.
  • a report e.g., status report
  • a UE may receive a configuration/indication, from a BS, indicating whether the UE is enabled (or not) to ignore ACK/NACK information (and/or consider as ACK for all the ACK/NACK) of one or more data units in/from a report (e.g., status report) based on one or more data units (and/or one or more SNs associated with one or more data units) are missing or not.
  • a report e.g., status report
  • one or more bits/bitmaps/fields/entries may be used to indicate one or more configuration/indications.
  • a field (e.g., of a bitmap), e.g., of the configuration/indications, may be used to indicate a respective UE/RB/SRB/DRB/RLC entity/PDCP entity/MAC entity/LCH/LCG/Cell/Cell group/BWP/QoS flow.
  • An entry e.g., of a list
  • e.g., of the configuration/indications may be used to indicate a respective UE/RB/SRB/DRB/RLC entity/PDCP entity/MAC entity/LCH/LCG/Cell/Cell group/BWP/QoS flow.
  • the configuration/indication may be indicated by a RB/DRB/SRB configuration, a RLC configuration (e.g., rlc- config, rlc-BearerConfig), a MAC configuration, a MAC cell group configuration, a PDCP configuration, a LCH configuration, a LCG configuration, a DSR configuration, a QoS flow configuration, a serving cell configuration, a BWP configuration.
  • the configuration/indication may be indicated by a PDCP signaling.
  • the configuration/indication may be indicated by a PDCP data PDU and/or a PDCP control PDU.
  • the configuration/indication may be indicated by a RLC signaling.
  • the configuration/indication may be indicated by a RLC data PDU and/or a RLC control PDU.
  • the configuration/indication may be indicated by a MAC signaling (e.g., MAC CE).
  • MAC signaling e.g., MAC CE
  • the configuration/indication may be indicated by a PHY signaling (e.g., DCI).
  • PHY signaling e.g., DCI
  • the UE may receive the configuration/indication only when RLC configuration (e.g., rlc-Config) (without suffix) is set to am.
  • RLC configuration e.g., rlc-Config
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to transmit an indication indicating that one or more data units (and/or one or more SNs associated with one or more data units) are delay-critical or not.
  • an indication e.g., UE capability information
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to transmit an indication indicating that one or more data units (and/or one or more SNs associated with one or more data units) need ACK/NACK information or not.
  • an indication e.g., UE capability information
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to determine that one or more data units (and/or one or more SNs associated with one or more data units) are delay-critical or not.
  • an indication e.g., UE capability information
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to determine that one or more data units (and/or one or more SNs associated with one or more data units) need ACK/NACK information or not.
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to determine that one or more data units (and/or one or more SNs associated with one or more data units) need (re-)transmission or not.
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to include/exclude ACK/NACK information of one or more data units in/from a report (e.g., status report) based on the indication.
  • an indication e.g., UE capability information
  • a report e.g., status report
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to consider one or more data units as ACK/NACK based on one or more data units (and/or one or more SNs associated with one or more data units) are missing or not.
  • an indication e.g., UE capability information
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to update a state variable (and/or set the state variable to a value) based on the indication.
  • an indication e.g., UE capability information
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to update a state variable (and/or set the state variable to a value) based on one or more data units (and/or one or more SNs associated with one or more data units) are delay-critical or not [0773] In some example embodiments, a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to update a state variable (and/or set the state variable to a value) based on one or more data units (and/or one or more SNs associated with one or more data units) need ACK/NACK information or not.
  • an indication e.g., UE capability information
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to update a state variable (and/or set the state variable to a value) based on one or more data units (and/or one or more SNs associated with one or more data units) need (re-)transmission or not.
  • an indication e.g., UE capability information
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to update a state variable (and/or set the state variable to a value) based on one or more data units (and/or one or more SNs associated with one or more data units) need to be included in a STATUS report or not.
  • an indication e.g., UE capability information
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to update a state variable (and/or set the state variable to a value) based on one or more data units (and/or one or more SNs associated with one or more data units) are discarded or not.
  • an indication e.g., UE capability information
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to update a state variable (and/or set the state variable to a value) based on one or more data units (and/or one or more SNs associated with one or more data units) are missing or not.
  • an indication e.g., UE capability information
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to (re-)start/stop/reset a timer based on one or more data units (and/or one or more SNs associated with one or more data units) need ACK/NACK information or not.
  • an indication e.g., UE capability information
  • a UE may transmit an indication (e.g., UE capability information) to indicate that the UE supports to ignore ACK/NACK information (and/or consider as ACK for all the ACK/NACK) of one or more data units in/from a report (e.g. , status report) based on one or more data units (and/or one or more SNs associated with one or more data units) need to be included in a STATUS report or not.
  • an indication e.g., UE capability information
  • a report e.g. , status report
  • a wireless device/base station may determine for a radio link control (RLC) status report, to: exclude acknowledgement (ACK) information of one or more first sequence numbers (SNs) associated with the one or more first data units that are delay-critical; and/or include ACK information of one or more second SNs associated with one or more second data units that are not delay-critical; The wireless device/base station may transmit the RLC status report.
  • RLC radio link control
  • the indication may be a RLC data PDU.
  • the indication indicates that one or more second data units are discarded.
  • the indication indicates that one or more second data units does not need
  • the indication indicates that the status report does not comprise the ACK/NACK information for the one or more data units.
  • the indication further indicating that one or more second data units are not delay- critical.
  • a entity may determine, by a receiving Acknowledgment Mode (AM) Radio Link Control (RLC) entity, not to comprise an ACK/NACK information, for a data unit, in a status report based on the data unit being delay-critical (and/or discarded).
  • the entity may transmit the status report.
  • AM Acknowledgment Mode
  • RLC Radio Link Control
  • a entity may transmit, by a transmitting Acknowledgment Mode (AM) Radio Link Control (RLC) entity to a receiving RLC entity, an indication indicating that one or more data units are delay-critical (and/or discarded).
  • AM Acknowledgment Mode
  • RLC Radio Link Control
  • the receiving AM RLC entity is a peer RLC entity of the transmitting AM RLC entity.
  • the transmitting AM RLC entity is a peer RLC entity of the receiving AM RLC entity.
  • the transmitting AM RLC entity may be a RLC entity of a wireless device.
  • the receiving AM RLC entity may be a RLC entity of a wireless device.
  • the status report is a status PDU.
  • the techniques described herein relate to a method, further including starting the discard timer with a duration.
  • the techniques described herein relate to a method, further including discarding, based on the discard timer expiring, a data unit.
  • the techniques described herein relate to a method, further including constructing the status PDU based on the triggering.
  • the techniques described herein relate to a method, wherein the data unit includes a sequence number (SN) that is lower than a state variable.
  • the techniques described herein relate to a method, wherein the state variable is a receiving state variable.
  • the techniques described herein relate to a method, wherein an AMD PDU includes the RLC SDU.
  • the techniques described herein relate to a method, wherein the RLC SDU has been submitted to a MAC entity of the wireless device.
  • the techniques described herein relate to a method, wherein the RLC SDU has not been submitted to a MAC entity of the wireless device.
  • the techniques described herein relate to a method, wherein the RLC SDU is placed in a transmission buffer or a retransmission buffer.
  • the techniques described herein relate to a method, wherein the configuration is indicated by a radio resource control (RRC) message.
  • RRC radio resource control
  • the techniques described herein relate to a method, wherein the configuration is indicated per RLC entity.
  • the techniques described herein relate to a method, wherein the configuration is indicated per AM RLC entity.
  • the techniques described herein relate to a method, wherein the configuration is indicated by a packet data convergence protocol (PDCP) configuration.
  • PDCP packet data convergence protocol
  • the techniques described herein relate to a method, wherein the configuration is indicated per PDCP entity.
  • the techniques described herein relate to a method, wherein the discard timer is used for discarding one or more RLC SDUs.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un dispositif sans fil reçoit une configuration indiquant une durée d'un temporisateur de rejet. Le dispositif sans fil démarre le temporisateur de rejet conformément à la durée. Le dispositif sans fil détermine que le temporisateur de rejet expire. Le dispositif sans fil, sur la base de la détermination indiquant l'expiration du temporisateur de rejet : rejette une unité de données et déclenche, par un côté de réception d'une entité de commande de liaison radio (RLC) de mode acquitté (AM) du dispositif sans fil, un rapport d'état. Le rapport d'état contient un ou plusieurs accusés de réception positifs ou négatifs d'une ou plusieurs unités de données de service (SDU) de RLC. Le dispositif sans fil transmet le rapport d'état.
PCT/US2025/023249 2024-04-04 2025-04-04 Rapport d'état de commande de liaison radio Pending WO2025213087A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463574432P 2024-04-04 2024-04-04
US63/574,432 2024-04-04

Publications (2)

Publication Number Publication Date
WO2025213087A2 true WO2025213087A2 (fr) 2025-10-09
WO2025213087A3 WO2025213087A3 (fr) 2025-11-13

Family

ID=95559099

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2025/023249 Pending WO2025213087A2 (fr) 2024-04-04 2025-04-04 Rapport d'état de commande de liaison radio

Country Status (1)

Country Link
WO (1) WO2025213087A2 (fr)

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100996069B1 (ko) * 2006-11-27 2010-11-22 삼성전자주식회사 이동통신 시스템에서 라디오 링크 제어 계층의 데이터 전송 방법 및 장치
CN109348508B (zh) * 2013-11-11 2022-04-12 华为技术有限公司 数据传输方法及装置

Also Published As

Publication number Publication date
WO2025213087A3 (fr) 2025-11-13

Similar Documents

Publication Publication Date Title
US20250267758A1 (en) Discontinuous Reception for Extended Reality
US20250212045A1 (en) Delay Status Reporting
US12245227B2 (en) Hybrid automatic repeat request process for configured grant
EP4666781A1 (fr) Priorisation de canal logique pour rapporter des informations de retard
US20250203622A1 (en) Restriction of Configured Grant Resource Occasion
US20250193722A1 (en) Handling Out of Date Delay Reports
US20240414712A1 (en) Triggering for Transmission of Unused Configured Grant Indication
US20240284449A1 (en) Wireless Resource Usage Reporting
US12500702B2 (en) Handling on retransmission for extended reality
US20250279967A1 (en) Extended Reality (XR) Enhancement
WO2025213087A2 (fr) Rapport d'état de commande de liaison radio
WO2025213074A1 (fr) Fenêtre de transmission pour commande de liaison radioélectrique
US20250344098A1 (en) Extended Reality (XR) enhancement
WO2025213078A1 (fr) Fonctionnement de rejet de commande de liaison radio
WO2025213091A1 (fr) Retransmission de commande de liaison radio
WO2025229178A1 (fr) Gestion de transport de données de média
WO2025117645A1 (fr) Transmission à retard critique par priorisation de canal logique
WO2025175234A1 (fr) Autorisation de liaison montante pour planification sensible au retard
WO2025117644A1 (fr) Priorisation critique en délai
WO2025064880A1 (fr) Rapport d'état de retard
WO2025034957A1 (fr) Rapport d'état de tampon
WO2025175236A1 (fr) Priorisation d'unités de données à partir de canaux logiques
WO2025034953A1 (fr) Rapport d'état de tampon
WO2024259426A1 (fr) Temporisateur d'autorisation configurée en réalité étendue
WO2024259427A1 (fr) Répétition pour de multiples occasions d'autorisation configurées

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: 25722059

Country of ref document: EP

Kind code of ref document: A2