Repetition factor adaptation for transport block transmissions based on micro-slots

Abstract

Techniques related to wireless communication are disclosed. Some aspects of the present disclosure relate to a device comprising a processing system configured to obtain first data, where the first data is obtained from a second wireless device, including reliability or rate requirements, initial resource pool configuration, priority, quality of service (QoS), or residual packet delay budget (PDB). Each of the plurality of transmission types is a different pattern that organizes data into a micro-slot reserved for sidelink transmission. The processing system is configured to output the data in one or more micro-slots reserved for sidelink transmission for transmission to the second wireless device according to the determined transmission type.

Description

[0001] This application claims priority to U.S. Patent Application No. 18 / 058,505, filed on November 23, 2022, the entire content of which is incorporated herein by reference. Technical Field

[0002] The techniques discussed below generally relate to wireless communication systems. Background Art

[0003] In a wireless communication system, interference or other factors may cause the transmitted data to be corrupted or lost. Thus, techniques for detecting the corruption or loss of transmitted data are implemented in wireless communication systems. For example, a transmitting device may include an error check code, such as a cyclic redundancy check (CRC) code, in the transmitted data. A receiving device may process the error check code to determine whether the transmitted data is corrupted. The receiving device may respond to the transmitting device with an acknowledgment message (ACK) indicating successful reception or a negative acknowledgment message (NACK) indicating unsuccessful reception. In some cases, the transmitting device automatically retransmits the data without waiting for a NACK message. Preemptively retransmitting the data in this manner can reduce the latency associated with transmitting ACK and NACK messages. Summary of the Invention

[0004] To provide a basic understanding of one or more aspects of the present disclosure, an overview of such aspects is given below. This overview is not an extensive review of all the expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a simplified form as a prelude to the more detailed description that follows. Although some examples may be discussed as including certain aspects or features, all of the examples discussed may include any of the features discussed. And no aspect or feature is necessary for achieving the technical effects or solutions discussed herein unless explicitly described.

[0005] In one example, a system is described that is configured to adapt a transmission type for transmitting data in a micro-slot reserved for sidelink transmission. For example, a transmitting wireless device may include a processing system configured to determine a transmission type from a plurality of transmission types. Each transmission type in the plurality of transmission types is a different pattern for organizing data into the micro-slot reserved for sidelink transmission. The processing system is configured to output the data in one or more micro-slots reserved for sidelink transmission for transmission to a second wireless device according to the determined transmission type. For example, the processing system may obtain first data. The first data may be obtained from the second wireless device, the first data may indicate a reliability or rate requirement, the first data may indicate an initial resource pool configuration, and / or the first data may indicate a priority, quality of service (QoS), or remaining packet delay budget (PDB). In this example, the transmission type may depend on the first data.

[0006] Determining a transmission type for transmitting data in a micro-slot may further reduce the latency in transmitting the data. In the present disclosure, a wireless device is a device configured to perform wireless communication. Example wireless devices may include a base station, a user equipment, an access point, a wireless node, and the like.

[0007] In some examples, the present disclosure describes an apparatus for wireless communication, the apparatus including: one or more processors; and a memory including instructions executable by the one or more processors, wherein the one or more processors are configured to: obtain first data, wherein at least one of the following: the first data is obtained from a second wireless device, the first data indicates a reliability or rate requirement, the first data indicates an initial resource pool configuration, the first data indicates a priority, the first data indicates quality of service (QoS), or the first data indicates a remaining packet delay budget (PDB); output second data in one or more micro-slots reserved for sidelink transmission for transmission to a receiving wireless device according to a transmission type among a plurality of transmission types, wherein: the transmission type depends on the first data, and each transmission type in the plurality of transmission types is a different pattern for organizing the second data into the one or more micro-slots reserved for sidelink transmission.

[0008] In another example, the present disclosure describes a method for wireless communication at a first wireless device, the method comprising: obtaining first data, wherein at least one of the following: the first data is obtained from a second wireless device, the first data indicates a reliability or rate requirement, the first data indicates an initial resource pool configuration, the first data indicates a priority, the first data indicates quality of service (QoS), or the first data indicates a remaining packet delay budget (PDB); outputting second data in one or more micro-slots reserved for sidelink transmission for transmission to a receiving wireless device according to a transmission type among a plurality of transmission types, wherein: the transmission type depends on the first data, and each transmission type among the plurality of transmission types is a different mode of organizing the second data into one or more micro-slots reserved for sidelink transmission.

[0009] In another example, the present disclosure describes an apparatus for wireless communication, the apparatus comprising: one or more processors; and a memory including instructions executable by the one or more processors, wherein the one or more processors are configured to: output an indication of a transmission type among a plurality of transmission types for providing to a second wireless device, each transmission type among the plurality of transmission types being a different mode of organizing data into micro-slots reserved for sidelink transmission; and allocate resources to be used by the second wireless device for sidelink communication.

[0010] In another example, the present disclosure describes a method for wireless communication at a first wireless device, the method comprising: outputting an indication of a transmission type among a plurality of transmission types for providing to a second wireless device, each transmission type among the plurality of transmission types being a different mode of organizing data into micro-slots reserved for sidelink transmission; and allocating resources to be used by the second wireless device for sidelink transmission.

[0011] In another example, the present disclosure describes an apparatus for wireless communication, the apparatus comprising: one or more processors; and a memory including instructions executable by the one or more processors, wherein the one or more processors are configured to: output retransmission request data for transmission to a second wireless device, the retransmission request data indicating the number of repetitions of a transport block (TB); and obtain a set of repetitions of the TB in one or more micro-slots reserved for sidelink transmission from the second wireless device, wherein the set of repetitions of the TB includes the number of repetitions of the TB.

[0012] In another example, the present disclosure describes a method for wireless communication at a first wireless device, the method comprising: outputting repetition request data for transmission to a second wireless device, the repetition request data indicating a number of repetitions of a transport block (TB); and obtaining, from the second wireless device, a set of repetitions of the TB in one or more micro-slots reserved for sidelink transmission, wherein the set of repetitions of the TB includes the number of repetitions of the TB.

[0013] After reading the following detailed description, these and other aspects of the techniques discussed herein will be more fully appreciated. Other aspects and features will become apparent to those of ordinary skill in the art after reading the description of the specific examples in conjunction with the drawings. Although the following description may discuss various advantages and features with respect to certain examples, specific implementations, and drawings, all examples may include one or more of the advantageous features discussed herein. In other words, although the description may discuss one or more examples as having certain advantageous features, one or more such features may also be used in accordance with various other examples discussed herein. In a similar manner, although the description may discuss certain examples as devices, systems, or methods, it should be understood that such examples of the teachings of the present disclosure may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 is a schematic diagram of a wireless communication system in accordance with some aspects of the present disclosure.

[0015] Figure 2 is a conceptual diagram of an example of a radio access network in accordance with some aspects of the present disclosure.

[0016] Figure 3A is a schematic diagram of a user plane protocol stack and a control plane protocol stack in accordance with some aspects of the present disclosure.

[0017] Figure 3B is a schematic diagram of a user plane protocol stack and a control plane protocol stack for a sidelink interface between a pair of UEs in accordance with some aspects of the present disclosure.

[0018] Figure 4 Aspects of the present disclosure are illustrated schematically with reference to an orthogonal frequency division multiplexing (OFDM) waveform.

[0019] Figure 5 is a conceptual diagram illustrating an example transport block (TB).

[0020] Figure 6 is a conceptual diagram illustrating an example micro-slot in sidelink communication.

[0021] Figure 7 is a conceptual diagram illustrating an example alternative design of a micro-slot.

[0022] Figure 8 is a conceptual diagram illustrating an example network system according to the technology of the present disclosure.

[0023] Figure 9 is a conceptual diagram illustrating an example of a micro-slot and a physical side link feedback channel according to the technology of the present disclosure.

[0024] Figure 10 is a block diagram conceptually illustrating an example of a hardware implementation of a network node according to some aspects of the present disclosure.

[0025] Figure 11 is a block diagram conceptually illustrating an example of a hardware implementation for a user equipment (UE) according to some aspects of the present disclosure.

[0026] Figure 12 is a flowchart illustrating an example operation of a transmitting UE (Tx-UE) according to the technology of the present disclosure.

[0027] Figure 13 is a flowchart illustrating an example operation of a receiving UE (Rx-UE) according to the technology of the present disclosure.

[0028] Figure 14 is a flowchart illustrating an example operation of a device according to the technology of the present disclosure. Detailed Description

[0029] Because data may be lost or corrupted during transmission, the transmitting device may include an error check code, such as a cyclic redundancy check (CRC) code, in the data being transmitted. For example, in 5G wireless communication, a transport block (TB) is a data packet passed between the media access control (MAC) layer and the physical layer of the protocol stack. The TB includes a payload and a CRC code.

[0030] The receiving device may process the error check code to determine whether the transmitted data is corrupted. The receiving device may respond to the transmitting device with an acknowledgement message (ACK) indicating successful reception or a negative acknowledgement message (NACK) indicating unsuccessful reception. In some cases, the transmitting device automatically repeats the transmission of the data without waiting for the NACK message. Repeating the transmission of the data preemptively in this way can reduce the latency associated with transmitting ACK and NACK messages. That is, if the transmitting device transmits the same data two or more times in quick succession, the chance of the receiving device successfully receiving the data is relatively high before the receiving device has the opportunity to transmit a NACK message to the transmitting device and the transmitting device responds to the NACK message by retransmitting the data to the receiving device. The repetition factor indicates the number of times the transmitting device repeats the transmission of the data preemptively. However, preemptively repeating the transmission of the data may consume additional bandwidth and energy.

[0031] In 5G wireless communication, a time slot is a period of time during which data can be transmitted. In some versions of the 5G standard, a time slot can be divided into mini-slots. In some cases, using mini-slots can be beneficial, such as when a transmitting user equipment (Tx-UE) transmits a transport block (TB) that is small enough not to require a full time slot. Thus, the use of mini-slots can allow multiple TBs to be transmitted within a single time slot. Therefore, the use of mini-slots can facilitate applications and services with strict latency requirements, such as industrial Internet of Things (IIoT) applications, ultra-reliable low-latency communication (URLLC) applications, and extended reality (XR) applications. When transmitting data in a sidelink channel, transmitting a TB in a mini-slot can be particularly useful. The sidelink channel enables direct communication between two UEs, rather than the two UEs communicating via a third radio device such as a base station.

[0032] The Tx-UE can transmit a TB in a mini-slot according to various transmission types. When data is organized into a mini-slot according to a first transmission type, the one or more mini-slots include multiple mini-slots of one or more time slots and are used to transmit a transport block (TB) containing second data. When data is organized into a mini-slot according to a second transmission type, the TB containing the data is repeated in different mini-slots with the same or different redundancy versions (RVs). When data is organized into a mini-slot according to a third transmission type, the time slot includes a first set of one or more mini-slots and a second set of one or more mini-slots, the data includes third data and fourth data, and a first TB containing the third data is transmitted in the first set of mini-slots, and a second TB containing the fourth data is transmitted in the second set of mini-slots.

[0033] This disclosure describes techniques in a Tx-UE that can determine which transmission type to use to transmit a TB to a receiving UE (Rx-UE) via a sidelink channel. For example, the Tx-UE can determine a transmission type from a variety of transmission types, where each transmission type in the variety of transmission types is a different pattern of organizing data into mini-slots reserved for sidelink transmission. The Tx-UE can transmit data to a second radio device in one or more mini-slots reserved for sidelink transmission according to the determined transmission type. Additionally, this disclosure describes techniques by which the Tx-UE and the Rx-UE can determine a repetition factor for repeated transmission of the TB. Determining the transmission type and the repetition factor for transmitting data in a mini-slot can reduce latency and can better utilize bandwidth resources.

[0034] The following disclosure presents various concepts that can be implemented across a variety of telecommunications systems, network architectures, and communication standards. Figure 1 is a schematic diagram of a wireless communication system in accordance with some aspects of the present disclosure. Now refer to Figure 1, by way of illustrative example and not limitation, this schematic diagram shows various aspects of the present disclosure with reference to a wireless communication system 100. The wireless communication system 100 includes multiple interaction domains: a core network 102, a radio access network (RAN) 104, and a scheduled entity. A scheduled entity can be any type of device configured to send and receive data in the wireless communication system 100 in the scheduling of a device. A user equipment (UE) is a common form of a scheduled entity. Thus, for ease of explanation, the present disclosure refers to the scheduled entity as a UE. Figure 1 The scheduled entity 106 is shown as a user equipment (UE). With the wireless communication system 100, it is possible to enable the UE to perform data communication with an external data network 110 (such as, but not limited to, the Internet).

[0035] The RAN 104 can implement any suitable one or more wireless communication technologies to provide radio access to the scheduled entity 106. As an example, the RAN 104 can operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification (commonly referred to as 5G or 5G NR). In some examples, the RAN 104 can operate under a hybrid of 5G NR and the evolved Universal Terrestrial Radio Access Network (eUTRAN) standard (commonly referred to as Long Term Evolution (LTE)). 3GPP refers to this hybrid RAN as the next generation RAN, or NG-RAN. Of course, many other examples can be utilized within the scope of the present disclosure.

[0036] As shown in the figure, the RAN 104 includes multiple scheduled entities 108, such as base stations. Broadly speaking, a base station is a network element in a radio access network responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, those skilled in the art may refer to a "base station" differently as a transceiver base station (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), Node B (NB), evolved Node B (eNB), gNode B (gNB), 5G NB, transmit receive point (TRP), or some other suitable term.

[0037] RAN 104 supports wireless communication for multiple mobile devices. Those skilled in the art may refer to a mobile device as a UE as in the 3GPP specifications, but may also refer to a UE as a mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, cell phone, terminal, user agent, mobile client, client, or some other suitable term. A UE may be a device that provides access to network services. A UE may take many forms and may include a range of devices.

[0038] Within this document, a "mobile" device (also referred to as a UE) does not necessarily need to have the ability to move and can be stationary. The term mobile device or mobile equipment refers to a wide variety of devices and technologies. A UE can include multiple hardware structural components whose size, shape, and arrangement facilitate communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., which are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile stations, cellular (cell) phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), vehicles, and a wide range of embedded systems, such as those corresponding to the "Internet of Things" (IoT). Mobile devices (such as UEs) can additionally be automotive or other transportation vehicles, remote sensors or actuators, robots or robotic devices, satellite radios, Global Positioning System (GPS) devices, object tracking devices, drones, multi-axis aircraft, quadcopters, remote control devices, consumer and / or wearable devices (such as glasses, wearable cameras, virtual reality devices, smart watches, health or fitness trackers, digital audio players (e.g., MP3 players), cameras, game consoles, etc.). Mobile devices can additionally be digital home or smart home devices, such as home audio, video, and / or multimedia devices, appliances, vending machines, smart lighting, home security systems, smart meters, etc. Mobile devices can additionally be smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure devices that control electricity (e.g., smart grid), lighting, water, etc.; industrial automation and enterprise equipment; logistics controllers; and agricultural equipment; and so on. Further still, mobile devices can provide connected drug or telemedicine support, for example, healthcare at a distance. Telemedicine devices can include telemedicine monitoring devices and telemedicine management devices, and their communication can be given priority or precedence over access to other types of information, for example, in terms of priority access for the transmission of critical service data and / or the associated QoS for the transmission of critical service data. Mobile devices can additionally include two or more decomposed devices that communicate with each other, including, for example, wearable devices paired with smart phones, tactile sensors, limb movement sensors, eye movement sensors, etc. In various examples, such decomposed devices can communicate directly with each other via any suitable communication channel or interface, or can communicate indirectly with each other via a network (e.g., a local area network (LAN)).

[0039] The wireless communication between the RAN 104 and the scheduled entity 106 can be described as utilizing an air interface. The transmission from a base station (e.g., one of the scheduling entities 108) to one or more UEs (e.g., the scheduled entity 106) over the air interface can be referred to as a downlink (DL) transmission. According to certain aspects of the present disclosure, the term downlink may refer to a point-to-multipoint transmission originating at one of the scheduling entities 108 (e.g., a base station). Another way to describe this scenario may be to use the term "broadcast channel multiplexing". The transmission from a UE (e.g., the scheduled entity 106) to a base station (e.g., one of the scheduling entities 108) can be called an uplink (UL) transmission. According to further aspects of the present disclosure, the term uplink may refer to a point-to-point transmission originating at the scheduled entity 106 (e.g., a UE).

[0040] In some examples, access to the air interface can be scheduled, where one or more of the scheduling entities 108 (e.g., network nodes) allocate resources for communication among some or all of the devices and equipment within their service area or cell. Within the present disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for the scheduled communication, the UE 106 (which may be a scheduled entity) may utilize the resources allocated by the scheduling entity.

[0041] A base station is not the only entity that can act as a scheduling entity. That is, in some examples, a UE or a network node may act as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more UEs).

[0042] As Figure 1 shown, a network node (e.g., one or more of the scheduling entities 108) can broadcast downlink traffic 112 to one or more UEs 106. Broadly speaking, a network node is a node or device responsible for scheduling traffic in a wireless communication network, which includes downlink traffic 112 and (in some examples) uplink traffic 116 from one or more scheduled entities (e.g., the scheduled entity 106) to the network node. On the other hand, the scheduled entity 106 (e.g., a UE) is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., a grant), synchronization or timing information, or other control information) from another entity in the wireless communication network, such as a network node.

[0043] A network node, such as the scheduling entity 108, may include a backhaul interface for communicating with the backhaul portion 120 of a wireless communication system. The backhaul portion 120 may provide a link between the network node and the core network 102. Additionally, in some examples, the backhaul network may provide an interconnection between the respective network nodes. Various types of backhaul interfaces may be employed, such as direct physical connections, virtual networks, or the like using any suitable transport network.

[0044] The core network 102 may be part of the wireless communication system 100 and may be independent of the radio access technology used in the RAN 104. In some examples, the core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, the core network 102 may be configured according to 4G evolved packet core (EPC) or any other appropriate standard or configuration.

[0045] By way of example and not limitation, Figure 2 a schematic diagram of the RAN 200 is provided. In some examples, the RAN 200 may be the same as the RAN 104 described above and illustrated in Figure 1 The geographical area covered by the RAN 200 may be divided into cellular regions (cells), and the UEs may be uniquely identified based on an identifier broadcast from an access point, base station, or network node. Figure 2 Macro cells 202, 204, and 206 and small cell 208 are illustrated.

[0046] Figure 2 Two of the three network nodes 210, 212, and 214 in cells 202, 204, and 206 are shown. In the illustrated example, cells 202, 204, and 206 may be referred to as macro cells because the network nodes 210, 212, and 214 support cells with large sizes. Additionally, network node 218 is shown in small cell 208 (e.g., micro cell, pico cell, femto cell, home base station, home Node B, home eNode B, etc.), which may overlap with one or more macro cells. In this example, small cell 208 may be referred to as a small cell because network node 218 supports a cell with a relatively small size. Cell sizing may be performed according to system design and component constraints.

[0047] The RAN 200 may include any number of wireless network nodes and cells. Additionally, the RAN 200 may include relay nodes to extend the size or coverage area of a given cell. Network nodes 210, 212, 214, 218 provide a wireless access point to the core network for any number of mobile devices. In some examples, network nodes 210, 212, 214, and / or 218 may be the same as those described above and Figure 1is the same as the scheduling entity 108 illustrated therein.

[0048] Figure 2 Further includes an unmanned aerial vehicle (UAV) 220 (such as a quadcopter or drone), which can be configured to act as a network node. That is, in some examples, the cell may not have to be stationary, and the geographical area of the cell can move according to the location of a mobile network node (such as UAV 220).

[0049] Within the RAN 200, each of the network nodes 210, 212, 214, 218, and UAV 220 can be configured to provide an access point to the core network 102 (see Figure 1 ) to all UEs in the corresponding cell. For example, UEs 222 and 224 can communicate with network node 210; UEs 226 and 228 can communicate with network node 212; UEs 230 and 232 can communicate with network node 214; UE 234 can communicate with network node 218; and UE 236 can communicate with a mobile network node such as UAV 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 can be the same as the UEs / scheduled entities 106 described above and illustrated in Figure 1 is the same as the UE / scheduled entity 106 illustrated therein.

[0050] In some examples, a mobile network node (e.g., UAV 220) can be configured to act as a UE. For example, UAV 220 can operate within cell 202 by communicating with network node 210.

[0051] In another aspect of the RAN 200, sidelink signals can be used between UEs without relying on scheduling or control information from a network node (e.g., a scheduling entity). For example, two or more UEs (e.g., UEs 226 and 228) can communicate with each other using peer-to-peer (P2P) or sidelink signals 227 without relaying the communication through a network node. In another example, UE 238 is illustrated as communicating with UEs 240 and 242. Here, UE 238 can act as a scheduling entity or a primary sidelink device, and UE 240 or 242 can act as a scheduled entity or a non-primary (e.g., secondary) sidelink device. In yet another example, a UE can act as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P), or vehicle-to-vehicle (V2V) network and / or a mesh network. In the mesh network example, UEs 240 and 242 can optionally communicate directly with each other in addition to communicating with a scheduling entity such as UE 238. Thus, in a wireless communication system with scheduled access to time-frequency resources and having a cellular configuration, P2P configuration, or mesh configuration, a scheduling entity and one or more scheduled entities can utilize the scheduled resources to communicate.

[0052] To transmit on the radio access network 200 to obtain a low block error rate (BLER) while still achieving a very high data rate, a transmitter can use channel decoding. That is, wireless communication typically can utilize a suitable error-correcting block code. In a typical block code, the transmitter splits an information message or sequence into code blocks (CBs), and an encoder (e.g., a CODEC) at the transmitting device then mathematically adds redundancy to the information message. This redundancy in the encoded information message can improve the reliability of the message, enabling the correction of bit errors that may occur due to noise.

[0053] In the 5G NR specification (Release 15), data is decoded in different ways. Quasi-cyclic low-density parity-check (LDPC) with two different base graphs can be used to decode user data (e.g., data, data traffic, traffic, etc.). One base graph is for large code blocks and / or high code rates, while the other base graph is for other cases. Polar coding (e.g., based on nested sequences) can be used to decode control information and the physical broadcast channel (PBCH). For control information and PBCH, rate matching is performed using puncturing, shortening, and repetition.

[0054] Those of ordinary skill in the art will understand that aspects of the present disclosure can be implemented using any suitable channel code. Various specific implementations of the scheduling entity 108 and the scheduled entity 106 can include suitable hardware and capabilities (e.g., encoders, decoders, and / or codecs) to perform wireless communication using one or more of these channel codes.

[0055] The air interface in the radio access network 200 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to network node 210, and multiplexing for DL transmissions from network node 210 to one or more UEs 222 and 224 using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP). Additionally, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes. For example, a UE can utilize time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spreading multiple access (RSMA), or other suitable multiple access schemes to provide UL multiple access. Further, a network node can multiplex DL transmissions to a UE using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0056] Figure 3A is a schematic diagram of a user plane protocol stack 300 and a control plane protocol stack 350 according to some aspects of the present disclosure. In a radio communication system, the communication protocol architecture can take various forms depending on the application. For example, in a 3GPP NR system, the signaling protocol stack is divided into a non-access stratum (NAS 358) and an access stratum (AS 302 - 306 and 352 - 357) layers and protocols. The NAS protocol 358 provides the upper layer for signaling between the scheduled entity 106 and the core network 102 (refer to Figure 1 ). The AS protocols 302 - 306 and 352 - 357 provide the lower layers for signaling between the RAN 104 (e.g., gNB, network node, or scheduling entity 108) and the scheduled entity 106.

[0057] The radio bearers between a network node (e.g., one of the scheduling entities 108) and the scheduled entity 106 can be classified as data radio bearers (DRBs) for carrying user plane data corresponding to the user plane protocol stack 30; and signaling radio bearers (SRBs) for carrying control plane data corresponding to the control plane protocol stack 350.

[0058] In AS, the protocols in both the user plane protocol stack 300 and the control plane protocol stack 350 include the Physical Layer (PHY) 302 / 352, the Medium Access Control layer (MAC) 303 / 353, the Radio Link Control layer (RLC) 304 / 354, and the Packet Data Convergence Protocol layer (PDCP) 305 / 355. The PHY 302 / 352 is the lowest layer and implements various physical layer signal processing functions. The MAC layer 303 / 353 provides multiplexing between logical channels and transport channels and is responsible for various functions. For example, the MAC layer 303 / 353 is responsible for reporting scheduling information, priority handling and priority determination, and error correction through Hybrid Automatic Repeat Request (HARQ) operations. The RLC layer 304 / 354 provides functions such as sequence numbering, segmentation and reassembly of upper layer data packets, and duplicate packet detection. The PDCP layer 305 / 355 provides functions including header compression of upper layer data packets to reduce radio transmission overhead, security through encryption of data packets, and integrity protection and verification.

[0059] In the user plane protocol stack 300, the Service Data Adaptation Protocol (SDAP) layer 306 provides services and functions for maintaining the desired Quality of Service (QoS). In the control plane protocol stack 350, the Radio Resource Control (RRC) layer 357 includes a number of functional entities for routing higher layer messages, handling broadcast and paging functions, establishing and configuring radio bearers, NAS message transfer between the NAS and the UE, etc.

[0060] The NAS protocol 358 provides a variety of control functions between the scheduled entity 106 and the core network 102. These functions include, for example, registration management functions, connection management functions, and activation and deactivation of user plane connections.

[0061] Figure 4 Aspects of the present disclosure are schematically illustrated with reference to the OFDM waveform. Those of ordinary skill in the art should appreciate that aspects of the present disclosure can be applied to the DFT-s-OFDMA waveform in substantially the same manner as described below. That is, although some examples of the present disclosure may focus on OFDM links for clarity, it should be appreciated that the same principles can also be applied to the DFT-s-OFDMA waveform.

[0062] In some examples, a frame may refer to a pre-determined time duration for wireless transmission (e.g., 10 ms). Additionally, each frame may include a set of sub-frames (e.g., 10 sub-frames each of 1 ms). A given carrier may include one set of frames in the UL and another set of frames in the DL. Figure 4An expanded view of an exemplary DL subframe 402 is illustrated, showing an OFDM resource grid 404. However, as will be readily appreciated by those skilled in the art, the PHY transmission structure for any application may be different from the examples described herein, depending on any number of factors. Here, time is in OFDM symbols in the horizontal direction; and frequency is in subcarriers or tones in the vertical direction.

[0063] The resource grid 404 may schematically represent the time-frequency resources for a given antenna port. That is, in an MIMO implementation with multiple available antenna ports, a corresponding plurality of resource grids 404 may be available for communication. The resource grid 404 is divided into a plurality of resource elements (REs) 406. An RE (which is 1 subcarrier × 1 symbol) is the smallest discrete portion of the time-frequency grid and may contain a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE may represent one or more information bits. In some examples, a block of REs may be referred to as a physical resource block (PRB), or more simply as a resource block (RB) 408, which contains any suitable number of contiguous subcarriers in the frequency domain. In one example, an RB may span 12 subcarriers (a number independent of the parameter set used). In some examples, depending on the parameter set, an RB may include any suitable number of contiguous OFDM symbols in the time domain.

[0064] A given UE generally utilizes only a subset of the resource grid 404. An RB may be the smallest resource unit that a scheduler can allocate to a UE. Thus, the more RBs scheduled for a UE, and the higher the modulation scheme selected for the air interface, the higher the data rate for the UE.

[0065] In this illustration, the RB 408 occupies less than the entire bandwidth of the subframe 402, with some subcarriers illustrated above and below the RB 408. In a given implementation, the subframe 402 may have a bandwidth corresponding to any number of one or more RBs 408. Additionally, the RB 408 is shown as occupying less than the entire duration of the subframe 402, although this is only one possible example.

[0066] Each 1 ms subframe 402 may include one or more adjacent time slots. In Figure 4Among them, as an illustrative example, a subframe 402 includes four time slots 410. In some examples, a time slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include mini-slots with a shorter duration (e.g., one or two OFDM symbols). In some cases, a network node may occupy resources scheduled for ongoing time slot transmissions for the same or different UEs to transmit these mini-slots.

[0067] An expanded view of one of these time slots 410 illustrates that the time slot 410 includes a control region 412 and a data region 414. Generally, the control region 412 may carry a control channel (e.g., PDCCH), and the data region 414 may carry a data channel (e.g., PDSCH or PUSCH). Of course, a time slot may contain all DL, all UL, or at least one DL portion and at least one UL portion. Figure 4 The structure illustrated in [the relevant content] is merely exemplary in nature, and different time slot structures may be utilized, and these time slot structures may include one or more regions in each of the control region and the data region.

[0068] Although not shown in Figure 4 each individual RE 406 within the RB 408 may carry one or more physical channels, including control channels, shared channels, data channels, etc. Other RE 406 within the RB 408 may also carry pilot signals or reference signals. These pilot signals or reference signals may be provided to a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation / detection of the control channel and / or data channel within the RB 408.

[0069] In a DL transmission, a transmitting device (e.g., a network node, such as one of the scheduling entities 108) may allocate one or more RE 406 (e.g., within the control region 412) to carry one or more DL control channels. These DL control channels include DL control information (DCI) 114, which generally carries information from higher layers (such as physical broadcast channel (PBCH), physical downlink control channel (PDCCH), etc.) to one or more UEs 106. Additionally, the network node may allocate one or more DL REs to carry DL physical signals that generally do not carry information from higher layers. These DL physical signals may include a primary synchronization signal (PSS); a secondary synchronization signal (SSS); a demodulation reference signal (DM-RS); a phase tracking reference signal (PT-RS); a channel state information reference signal (CSI-RS); and so on.

[0070] A network node may transmit a synchronization signal PSS and SSS (collectively referred to as SS) in an SS block including 4 consecutive OFDM symbols, and in some examples, transmit a PBCH. In the frequency domain, the SS block may extend over 240 consecutive subcarriers. Of course, the present disclosure is not limited to this particular SS block configuration. Within the scope of the present disclosure, other non-limiting examples may utilize more or fewer than two synchronization signals; may include one or more supplementary channels in addition to the PBCH; may omit the PBCH; and / or may use non-consecutive symbols for the SS block.

[0071] The PDCCH may carry downlink control information (DCI) for one or more UEs in a cell. This may include, but is not limited to, power control commands for DL and UL transmissions, scheduling information, grants, and / or assignments of REs.

[0072] In UL transmission, a transmitting device (e.g., a UE) may utilize one or more REs 406 to carry one or more UL control channels, such as a physical uplink control channel (PUCCH), a physical random access channel (PRACH), etc. These UL control channels include UL control information (UCI) 118, which generally carries information originating from a higher layer. In addition, UL REs may carry UL physical signals that generally do not carry information originating from a higher layer, such as a demodulation reference signal (DM-RS), a phase-tracking reference signal (PT-RS), a sounding reference signal (SRS), etc. In some examples, the control information 118 may include a scheduling request (SR), i.e., a request for a network node (such as one of the scheduling entities 108) to schedule an uplink transmission. Here, in response to an SR transmitted on the UL control channel 118 (e.g., PUCCH), the network node may transmit downlink control information (DCI) 114, which may schedule resources for uplink packet transmission.

[0073] The UL control information may also include hybrid automatic repeat request (HARQ) feedback, such as an acknowledgement (ACK) or a negative acknowledgement (NACK), channel state information (CSI), or any other suitable UL control information. HARQ is a technique well known to those of ordinary skill in the art, where a receiving device may verify the integrity of a packet transmission for accuracy, e.g., using any appropriate integrity verification mechanism, such as a checksum or a cyclic redundancy check (CRC). If the receiving device acknowledges the integrity of the transmission, it may send an ACK, while if it does not acknowledge the integrity of the transmission, it may send a NACK. In response to a NACK, the transmitting device may transmit a HARQ retransmission, which may implement chase combining, incremental redundancy, etc.

[0074] In addition to control information, one or more REs 406 (e.g., within data region 414) may also be allocated for user data or traffic data. Such traffic may be carried on one or more traffic channels, such as, for DL transmission, on the Physical Downlink Shared Channel (PDSCH); or for UL transmission, on the Physical Uplink Shared Channel (PUSCH).

[0075] To enable a UE to obtain initial access to a cell, the RAN may provide system information (SI) characterizing the cell. The RAN may utilize minimum system information (MSI) and other system information (OSI) to provide this system information. The RAN may broadcast the MSI periodically on the cell to provide the most basic information required for the UE to perform initial cell access and to enable the UE to obtain any OSI that the RAN may broadcast periodically or on demand. In some examples, the network may provide the MSI on two different downlink channels. For example, the PBCH may carry the Master Information Block (MIB), while the PDSCH may carry System Information Block type 1 (SIB1). Here, the MIB may provide parameters for the UE to monitor the control resource set. The control resource set may thus provide scheduling information corresponding to the PDSCH to the UE, e.g., the resource location of SIB1. In the art, SIB1 may be referred to as the Remaining Minimum System Information (RMSI).

[0076] The OSI may include any SI not broadcast in the MSI. In some examples, the PDSCH may carry multiple SIBs, not limited to SIB1 discussed above. Here, the RAN may provide the OSI in these SIBs (e.g., SIB2 and above).

[0077] described above and Figure 1 and Figure 4 the channels or carriers illustrated in are not necessarily all the channels or carriers that may be utilized between a network node (e.g., one of the scheduling entities 108) and the scheduled entity 106, and one of ordinary skill in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, may be utilized in addition to the illustrated channels or carriers.

[0078] For example, device-to-device (D2D) communication may employ different channels or resource sets. D2D or peer-to-peer (P2P) communication enables the use of a direct link between devices (i.e., without passing through a base station, relay, or another network node) to discover nearby devices and communicate with nearby devices. D2D enables the implementation of mesh networks and device-to-network relay functionality. Some examples of D2D technologies include Bluetooth, Wi-Fi Direct, Miracast, LTE-D, and sidelink communication.

[0079] Sidelink communication can be provided over the PC5 interface, which uses the PC5 protocol for D2D communication. Within the scope of the present disclosure, other suitable protocols can be used for sidelink communication.

[0080] Resource allocation for radio resources in the sidelink resource pool can be in one of two modes, herein referred to as Mode 1 and Mode 2. Mode 1 is called scheduled resource allocation, where the sidelink resource allocation is provided by the RAN. Mode 2 is called UE autonomous resource allocation, where the UE determines the sidelink transmission resources and timing in the sidelink resource pool.

[0081] Resource allocation Mode 1 can generally be managed by a network node (e.g., gNB). In some examples, the UE can send a sidelink buffer status report (BSR) to the network node to support the scheduling of sidelink resources via Resource Allocation Mode 1. The sidelink BSR indicates that the UE has buffered data or is ready to send it to the destination UE via the sidelink. And in some examples, the network node can use one of several different types of sidelink grants.

[0082] Using a Type 1 sidelink grant (which can be referred to as a static grant), the network node can use higher layer (e.g., RRC) signaling to provide a persistent sidelink grant for sidelink communication.

[0083] Using a Type 2 sidelink grant (which can be referred to as a semi-static grant or a configured grant), the network node can use higher layer (e.g., RRC) signaling to define the resources of the configured sidelink grant, and then can send a suitable signal (e.g., DCI or MAC-CE) to activate or deactivate the configured sidelink grant. Here, the activation signal for the configured grant can indicate the number of repetitions that the UE is to use for sidelink transmission. That is, the activation signal for the configured sidelink grant can command the UE to perform a configured number of blind retransmissions of the sidelink transmission based on the configured grant. Here, blind retransmission refers to the retransmission (e.g., HARQ retransmission) of a message or packet without necessarily being informed (e.g., via HARQ-NACK) that the packet has not been successfully received and decoded. In various examples, the RAN can support any suitable number of blind retransmissions of sidelink data. The number of blind retransmissions used in a given application can depend on, for example, QoS requirements, desired reliability, or communication latency, etc.

[0084] Using a dynamic grant, the network node can send a suitable DCI that includes the sidelink grant itself. Since the dynamic grant can arrive essentially at any time, the UE can continuously monitor the PDCCH for such a dynamic sidelink grant DCI. Similar to the case of the configured grant, in some examples, the dynamic sidelink grant can command the UE to perform a configured number of blind retransmissions of the sidelink transmission.

[0085] Using resource allocation mode 2, the UE can autonomously or independently select resources for sidelink transmission from the sidelink resource pool specified by the RAN. The UE autonomous resource selection procedure involves the UE sensing the resources in the resource pool and, based on that sensing, selecting and reserving sidelink resources. This includes the UE autonomously determining how many times to transmit, repeat, or retransmit (e.g., using blind retransmission) a given transmission. One of ordinary skill in the art will recognize that in many scenarios, resource allocation mode 1 may be more suitable for UEs located within the coverage area of a network node, while resource allocation mode 2 may be more suitable for UEs located outside the coverage area of a network node. Additionally, resource allocation mode 2 can be used for multicast or broadcast transmissions in which negotiation for establishing an RRC connection for the sidelink among UEs is not available.

[0086] Sidelink communication can employ several physical channels and physical signals. For example, the Physical Sidelink Control Channel (PSCCH) can be used to indicate to the UE the resources and other transmission parameters for transmitting data on the Physical Sidelink Shared Channel (PSSCH). Transmission via the PSCCH typically can include DM-RS.

[0087] The UE can use the PSSCH to transmit data information, as well as certain control information for HARQ procedures and CSI feedback triggering, etc. PSSCH transmission typically can include DM-RS and can be associated with PT-RS.

[0088] The Physical Sidelink Feedback Channel (PSFCH) carries HARQ feedback over the sidelink. A UE that is the intended recipient of a PSSCH transmission can send HARQ feedback to the UE that performed the transmission via the PSFCH.

[0089] The sidelink synchronization signals can include a sidelink primary synchronization signal and a sidelink secondary synchronization signal (S-PSS, S-SSS) and can be broadcast together with the Physical Sidelink Broadcast Channel (PSBCH).

[0090] Sidelink HARQ feedback uses the PSFCH. In some examples, the PSFCH can use resources dedicated to the UE of a single transmission PSFCH to transmit an ACK or NACK. In another example, the PSFCH can carry a NACK, or the PSFCH signal may not be transmitted. That is, in some examples, sidelink HARQ feedback via the PSFCH can be disabled. In resource allocation mode 1 for the sidelink, a UE that obtains sidelink HARQ feedback via the PSFCH can report this feedback to the RAN via the PUCCH or PUSCH.

[0091] In some examples, a UE using a sidelink may send channel state information reference signals (CSI-RS) for CSI measurement and reporting in the sidelink. The receiving UE may send a CSI report using an appropriate feedback or control message, e.g., in a media access control - control element (MAC-CE). Additionally, the UE may measure a configured sidelink resource pool for reporting the channel busy rate (CBR). The CBR report may be periodic or triggered by an event based on an overloaded channel and / or an underloaded channel. Based on the CBR, the UE may adapt one or more transmission parameters for sidelink transmission, such as its maximum transmission power, the number of retransmissions to be made, the modulation and coding scheme (MCS), etc.

[0092] Sidelink radio bearers can be divided into two groups: sidelink data radio bearers for user plane data, and sidelink signaling radio bearers for control plane data. Figure 3B is a schematic diagram of a sidelink user plane protocol stack 360 and a sidelink control plane protocol stack 370 for a sidelink interface between a pair of UEs (labeled UE1 106 and UE2 108) according to some aspects of the present disclosure. The sidelink radio protocol architecture is Figure 3B shown by the sidelink user plane protocol stack 360 and the sidelink control plane protocol stack 370, and the corresponding layers or sub-layers of the two protocol stacks are also shown. The radio bearers between UE 106 and UE 108 can be classified as data radio bearers (DRBs) for carrying user plane data corresponding to the sidelink user plane protocol stack 360; and signaling radio bearers (SRBs) for carrying control plane data corresponding to the sidelink control plane protocol stack 370.

[0093] Both the sidelink user plane protocol stack 360 and the sidelink control plane protocol stack 370 include a physical (PHY) layer 362 / 372, a MAC layer 363 / 373, an RLC layer 364 / 374, and a PDCP layer (PDCP) 365 / 375. The PHY layer 362 / 372 is the lowest layer and implements various physical layer signal processing functions. The MAC layer 363 / 373 provides radio resource selection, packet filtering, priority handling between UL and DL transmissions of a given UE, and sidelink CSI reporting. The RLC layer 364 / 374 provides functions such as sequence numbering of upper layer data packets, segmentation and reassembly, and duplicate packet detection. The PDCP layer 365 / 375 provides functions including header compression of upper layer data packets to reduce radio transmission overhead, security through encryption of data packets, and integrity protection and verification.

[0094] In the side - link user - plane protocol stack 360, the Service Data Adaptation Protocol (SDAP) layer 366 provides services and functions for maintaining the desired Quality of Service (QoS), including the mapping between QoS flows and side - link data radio bearers. QoS generally refers to the overall effect of service performance, which determines the user's satisfaction with the service. QoS is characterized by a combination of performance factors applicable to all services, such as: service operability performance; service accessibility performance; service retainability performance; service integrity performance; and other factors specific to each service.

[0095] In the side - link control - plane protocol stack 370, the Radio Resource Control (RRC) layer 376 includes multiple functional entities for transmitting RRC messages between paired UEs 380, 382, for maintaining and releasing the RRC connection between UEs 380, 382, and for detecting side - link radio - link failures.

[0096] The RRC layer corresponding to the Uu interface (i.e., the radio interface between the radio access network and the UE) may also include various side - link - specific services and functions. For example, using the Uu interface, the RRC entity can configure side - link resource allocation via system - information signaling or dedicated signaling. The RRC entity can also be used for measurement configuration and side - link - related reporting, as well as for the conveyance or reporting of UE - assisted information related to the side - link traffic mode. That is, the UE can report the side - link traffic mode to the RAN.

[0097] Side - link communication can be supported by a source identifier (ID) and a destination identifier (ID). For example, the source layer - 2 ID can identify the source or transmitter of the side - link data. The destination layer - 2 ID can identify the target or receiver of the side - link data. In addition, the PC5 link ID can be used to uniquely identify a PC5 unicast link in the UE during the lifetime of the PC5 unicast link.

[0098] Side - link transmissions generally fall into one of the following three transmission types: unicast transmission, multicast transmission, or broadcast transmission. With unicast transmission, paired UEs can establish an RRC connection and negotiate the configuration of their mutual side - link interfaces. The paired UEs can detect radio - link failures in their RRC connection and can send and obtain control information and user traffic via the side - link, including using side - link HARQ feedback.

[0099] With multicast transmission, the transmitting UE can send user traffic in the side - link to one or more UEs belonging to a group. Here, a group can be identified based on the destination layer - 2 ID of the corresponding UE. That is, UEs in a given group for side - link multicast can share the same destination layer - 2 ID. Broadcast transmission is similar to multicast and involves a group of UEs sharing the same destination layer - 2 ID.

[0100] Figure 5 This is a conceptual diagram illustrating an example transport block (TB) 500. A TB is a data packet transmitted between the MAC layer and the physical layer. Thus, a MAC protocol data unit (PDU), i.e., a packet, is contained within one TB. The sender passes the TB from the MAC layer down to the physical layer. The receiver passes the TB from the physical layer up to the MAC layer. When the physical layer at the sender obtains the TB from the MAC layer, the physical layer processes the TB and maps the TB onto a physical channel, such as the physical downlink shared channel (PDSCH) or the physical sidelink shared channel (PSSCH). A cyclic redundancy check (CRC) code is calculated for the TB and appended to the TB. The size of the CRC code may depend on the size of the TB. In Figure 5 the example, a CRC code for the TB (TB-CRC 502) is appended to the TB 500.

[0101] Since a TB can be as large as 1,277,992 bits, retransmitting the entire TB when only a small number of TBs are in error may waste spectrum resources. Thus, if a TB is larger than a threshold size, the TB may be divided into smaller units, i.e., code blocks (CBs). In Figure 5 the example, the TB 500 and the TB-CRC 502 are divided into CBs 504A to 504C. In some examples, a CB has a maximum size of 8448 bits. A separate CRC code is calculated for each CB and appended to these CBs. In Figure 5 the example, CRC codes 506A to 506C (TB-CRC) are appended to the CBs 504A to 504C respectively. CBs may be grouped into code block groups (CBGs). For example, each CBG may include 1, 2, 4, 6, or 8 CBs. Contrary to the TB or CB levels, the receiver of a TB may respond using an acknowledgement (ACK) or a negative acknowledgement (NACK) at the CBG level. Thus, if the sender receives a NACK for a CBG, the sender only needs to retransmit that CBG instead of the entire TB.

[0102] Figure 6 This is a conceptual diagram illustrating an example micro-slot in sidelink communication. In Release 18 of the 5G NR specification, a time slot may be subdivided into two or more micro-slots having a shorter duration than the time slot. The use of micro-slots may reduce scheduling latency and may reduce the turnaround time of sidelink communication. This reduction in scheduling latency and turnaround time may be particularly important for latency-sensitive applications and services, including industrial Internet of Things (IIoT) applications, ultra-reliable low-latency communication (URLLC) applications, and extended reality (XR) applications.

[0103] In Figure 6In the example of, time slot 600 has two sub-channels 602A, 602B (collectively referred to as "sub-channel 602"), and is divided into three mini-slots 604A, 604B, 604C (collectively referred to as "mini-slot 604"). Each sub-channel 602 is a different set of two or more resource blocks. (A resource block may include 12 REs). Figure 6 Each rectangle in represents one or more concurrent RBs. The term "resource pool" can be used to refer to a set of sub-channels. The terms "sub-slot" and "mini-slot" can be used interchangeably.

[0104] In Figure 6 In the example of, there is a time gap of one OFDM symbol after each mini-slot 604. Each mini-slot 604 can carry one or more (e.g., two, four, etc.) OFDM symbols. Each mini-slot has REs for PSCCH data and PSSCH data. In Figure 6 In the example of, the dark spots correspond to the REs for PSSCH data, and the light spots correspond to the REs for PSCCH data. The REs marked with slash shading and cross-hatching can be used, for example, for automatic gain control (AGC).

[0105] Each mini-slot 604 is self-schedulable and decodable. In addition, the UE can select and reserve one or more mini-slots within the time slot. For example, the UE can select and reserve mini-slots 604A and 604B. A mini-slot being self-schedulable means that the data in the PSSCH of the mini-slot is scheduled by the scheduling grant (sidelink control information, SCI) in the PSCCH of the mini-slot. A decodable mini-slot means that the CODEC does not need information from any other mini-slot to decode the data in that mini-slot.

[0106] A larger number of mini-slots within a time slot can improve the scheduling delay and be suitable for small packets, such as 32-bit packets used in IIoT applications. However, as the number of mini-slots per time slot increases, more symbols should be allocated to the gaps between the mini-slots. In some use cases, such as those supporting a large number of UEs, the overhead associated with the gaps may weaken the benefit of reduced delay.

[0107] Figure 7It is a conceptual diagram showing an alternative design of an example of micro-slots. Note that the gap symbol is mainly used for Tx / Rx switching. Since in the 3GPP specifications of 5G NR (Release 16), Tx / Rx switching can only be performed at the slot boundary, the gap can only be used at the end of the slot. Therefore, a slot can be divided into micro-slots according to a specific pattern that specifies the number of micro-slots per slot and the length of each micro-slot (i.e., the number of OFDM symbols). Sidelink control information (SCI) SCI1 / PSCCH data can be included in the REs at the start of each slot. The SCI included at the start of the slot can indicate the transmission or reservation of a certain number of micro-slots in the slot or in future slots. SCI-1 is the Phase 1 sidelink control information. SCI-1 can be carried on the Physical Sidelink Control Channel (PSCCH). On the other hand, SCI-2 (i.e., the Phase 2 sidelink control information) can be carried or multiplexed together with the data on the Physical Sidelink Shared Channel (PSSCH).

[0108] In Figure 7 the example of, slot 700 includes REs for SCI-1 and includes micro-slots 702A, 702B, 702C, and 702D (collectively referred to as "micro-slots 702"), followed by a gap. Therefore, Figure 7 shows an example of a pattern where there is no gap between the micro-slots. In some examples, the first RE of slot 700 is an AGC symbol. In other examples, it may not be necessary to include an AGC symbol in slot 700 because the receiver can set the AGC based on the first symbol of slot 700 and use the same setting for the reception of any PSSCH micro-slots.

[0109] In several cases, the UE may reserve multiple micro-slots for the UE's sidelink transmission. These transmission types may include the transmission types referred to herein as Transmission Type A, Transmission Type B, and Transmission Type C.

[0110] Transmission Type A refers to the case where the reserved micro-slots are bundled and form a super-slot or a super-micro-slot. In other words, the micro-slots of one or more combined slots are used to transmit a single transport block (TB). A super-slot includes multiple slots. A super-micro-slot includes multiple micro-slots that span at least one slot. Therefore, two or more slots may include the micro-slots of a single super-micro-slot. In Figure 7 the context of, the symbols in each micro-slot 702 may contain the data of a single TB. In other words, the multiple micro-slots of one or more slots are used to transmit a TB containing the data to be transmitted.

[0111] Transmission type B refers to the case where a TB is repeated on reserved mini - slots with the same redundancy version (RV) index or different RV indices. In other words, the TB containing the data to be transmitted is repeated with the same or different redundancy versions (RVs) in different mini - slots among one or more mini - slots.

[0112] The bits of the TB can be stored in a conceptually circular buffer. The RV index of the RV version of the TB indicates the starting point of the RV version of the TB within the circular buffer. For example, if the TB is 24 bits long (i.e., the bits of the TB have bit indices 0 to 23), the RV version of the TB with RV index 0 can be bits 0 to 23, the RV version of the TB with RV index 3 can be bits 0 to 2 concatenated with bits 3 to 23, the RV version of the TB with RV index 6 can be bits 0 to 5 concatenated with bits 6 to 23, and so on.

[0113] Thus, in an example of transmission type B where the same RV index is repeated on reserved mini - slots, the same RV of the TB can be transmitted in mini - slots 702A, 702B, 702C, and 704D. In an example of transmission type B where the TB is repeated with different RV indices on reserved mini - slots, the first RV of the TB can be transmitted in mini - slot 702A, the second RV of the TB can be transmitted in mini - slot 702B, the third RV of the TB can be transmitted in mini - slot 702C, and the fourth RV of the TB can be transmitted in mini - slot 702D.

[0114] Transmission type C has two versions. In the first version of transmission type C, multiple mini - slots within a slot are used to transmit one TB, where each mini - slot uses one RV or all resources from one TB. For example, in Figure 7 the example, the first TB can be transmitted in mini - slots 702A and 702B, the second TB can be transmitted in mini - slot 702C, and the third TB can be transmitted in mini - slot 702D. In this case, the TB size can be determined based on the number of allocated resource elements (REs). In some examples, an RB consists of 12 REs.

[0115] The second version of transmission type C is a special case of the first version of transmission type C, where each mini - slot carries a different TB. For example, in Figure 7In the example, the first TB can be transmitted in micro-slot 702A, the second TB can be transmitted in micro-slot 702B, the third TB can be transmitted in micro-slot 702C, and the fourth TB can be transmitted in micro-slot 702D. Thus, in any version of transmission type C, a time slot includes a first set of one or more micro-slots and a second set of one or more micro-slots, the data includes first data and second data, and the first TB containing the first data is in the first set of micro-slots, and the second TB containing the second data is in the second set of micro-slots.

[0116] In some aspects, the present disclosure describes techniques that can reduce retransmission power and save resources for transmission types B and C (i.e., transmission types in which one TB is transmitted across micro-slots with the same RV or different RVs).

[0117] Figure 8 FIG. 7 is a conceptual diagram illustrating an example network system 800 in accordance with the techniques of the present disclosure. The network system 800 includes a gNB 802, a programmable logic controller (PLC) 804, UEs 806 and 808. In other examples, the PLC 804 can be a sidelink controller or a master UE. The PLC 804 can communicate with the UEs 806 and 808 using sidelink channels 810 and 812, respectively. The master UE can be a device that schedules resources for the sidelink channels.

[0118] In some examples, the gNB 802 or the PLC 804 can instruct the UE 806 to use a specific transmission type. For example, the gNB 802 or the PLC 804 can command the UE 806 to use one of transmission type A, transmission type B, or transmission type C. In an example where the gNB 802 commands the UE 806 which transmission type to use, the gNB 802 can command the UE 806 in the form of radio resource control (RRC) / medium access control (MAC)-control element (CE) data or downlink control information (DCI).

[0119] Resource allocation for radio resources in a sidelink resource pool can be in one of two modes, which are referred to herein as Mode 1 and Mode 2. Mode 1 is referred to as scheduled resource allocation, where the sidelink resource allocation is provided by the network. Mode 2 is referred to as UE autonomous resource allocation, where the UE determines the SL transmission resources and timing in the resource pool. Resource allocation Mode 1 can typically be managed by a scheduling entity or gNB. In some examples, UE 806 can send a sidelink buffer status report (BSR) to gNB 802 to support scheduling of sidelink resources via Resource Allocation Mode 1. The sidelink BSR indicates that UE 806 has buffered data or is ready to send it to the destination UE-Rx via the sidelink. In some examples, gNB 802 can use one of several different types of sidelink grants. With a Type 1 sidelink configured grant (which can be referred to as a static grant), the gNB can use higher layer (e.g., RRC) signaling to provide resources for a persistent sidelink grant for sidelink communication. With a Type 2 sidelink configured grant (which can be referred to as a semi-static grant), the gNB can send appropriate DCI on the PDCCH to activate or deactivate resources for the sidelink grant.

[0120] In some examples of the present disclosure, gNB 802 can use Mode 1 resource allocation with dynamic or configured resource grants. In some such examples, gNB 802 can indicate the transmission type to be used by UE 806 within the same DCI that the gNB 802 uses to allocate resources to UE 806.

[0121] In some examples, instead of gNB 802 or PLC 804 commanding UE 806 which transmission type to use, UE 806 can determine which transmission type to use based on reliability or rate requirements. For example, UE 806 can be configured with data (e.g., a table) that maps specific reliability and / or rate requirements to specific transmission types.

[0122] Some modern wireless networks, such as 5G NR networks, can provide radio resources over a very wide frequency range. However, any given UE accessing a cell may have a bandwidth capability that does not span the entire range. Thus, the RAN can configure for the UE a portion or a part of a carrier, called a bandwidth part (BWP), that has a bandwidth less than or equal to the UE's capability. The RAN can configure several BWPs for a UE (in some examples, up to four BWPs); although typically only a single BWP is the active BWP at a time. In the present disclosure, a BWP refers to a set of radio resources (e.g., a set of consecutive physical resource blocks (PRBs)) that is selected as a subset of the radio resources on a given carrier. In some examples, a BWP can be selected from a consecutive set of resource blocks that share a common parameter set (e.g., subcarrier spacing) on a given carrier. The RAN generally does not expect the UE to communicate outside the active BWP.

[0123] The gNB 802 can divide a BWP into two or more resource pools. The initial resource pool configuration specifies how to divide the entire bandwidth into the resource pools. During resource allocation, the gNB 802 can allocate resources from one or more resource pools for sidelink transmission. The resources available for allocation in a resource pool can include subchannels (each subchannel can include one or more resource blocks).

[0124] In some examples of the present disclosure, the initial resource pool configuration can also specify the transmission types for transmitting data in different resource pools. For example, the initial resource pool configuration can specify that transmission types B and C can be used in the resources allocated from the first resource pool, and can specify that transmission type A can be used in the resources allocated from the second resource pool.

[0125] Additionally, the initial resource pool configuration can specify a repetition factor for a resource pool. The repetition factor of a resource pool can specify how many repetitions (with the same or different RV indices) of a TB are to be transmitted. The gNB 802 can determine the repetition factor based on one or more factors such as the priority level of the resource pool or the quality of service (QoS) level of the resource pool. For example, if a first flow associated with a resource pool has a higher priority than a second flow, the gNB 802 can assign a higher repetition factor to the resource pool (and thus have a lower block error rate). The gNB 802 can determine that the first flow has a higher priority than the second flow based on a channel state report collected from the UE, based on the priority of the data, based on the required block error rate (BLER) / reliability, and / or other factors.

[0126] A packet may include one or more transport blocks (TBs). Packet delay may occur due to resources being used for retransmitting a TB in response to a NACK. A Packet Delay Budget (PDB) defines an upper limit on the amount of time a packet may be delayed between a User Equipment (UE) and a User Plane Function (UPF). For example, an XR application may prioritize timely delivery of a packet over the accuracy of the data in the packet. When the accumulated delay approaches the PDB, measures may be taken to reduce the delay, but potentially at the cost of the reliability of the data in the packet. In some examples, the repetition factor indicated by an initial resource pool configuration of a resource pool may be selected based on the PDB of the application that will use the resource pool.

[0127] In some examples, the UE 806 may switch to transmission type C based on approaching the PDB. Thus, in such examples, the UE 806 may change from transmission type B (which may involve a higher repetition factor due to multiple redundancy versions (RVs) of transmitting a TB) to transmission type C. For example, it may be appropriate to use different TBs to complete the transmission of a packet, or use repetition to achieve the reliability of the TBs of a packet. Thus, there may be a trade-off (repeating by a certain factor but still transmitting more than one TB per time slot).

[0128] In some examples, a transmitting UE (e.g., UE 806) may determine the number of repetitions (i.e., the repetition factor) based on a Logical Channel Group (LCG) priority and / or Quality of Service (QoS). A MAC multiplexing function may be used to multiplex multiple logical channels of different priorities (e.g., QoS classes) into the same TB. An LCG is a set of logical channels. The transmitting UE may determine how to prioritize the transmission of these multiplexed TBs. In other words, the transmitting UE may determine the priority of the logical channels. According to the techniques of the present disclosure, the transmitting UE may determine the repetition factor for a TB to be transmitted in an LCG based on the priority of the LCG. For example, the transmitting UE may store data (e.g., a table) that maps a particular repetition factor to the priority of an LCG.

[0129] The UE may then select a repetition factor based on feedback from a receiving UE (Rx-UE) and approaching the PDB deadline to maintain the highest priority of the transmitted signal. In other words, the number of repetitions may be a function of feedback from the Rx-UE, QoS, and / or remaining PDB. For example, to reduce errors or suppress errors (e.g., to reduce the Block Error Rate (BLER) or the likelihood of an error), when approaching the QoS or PDB deadline, the UE may select a repetition factor associated with a larger number of repetitions. The determined number of repetitions may be applied to new TB transmissions and also to retransmissions.

[0130] In this way, the Tx-UE may repeatedly transmit the data for a first number of times, where the first number of times is based on a first repetition factor. The first repetition factor is based on the LCG priority or QoS of the data. The Tx-UE may obtain feedback from a second wireless device. The Tx-UE may repeat the transmission of the data for a second number of times. The second number of times may be based on a second repetition factor, where the second repetition factor is based on the feedback from the second wireless device and the PDB deadline of the packet containing the data.

[0131] In some examples, the transmitting UE may use the number of NACKs within a configurable time interval as an indicator for reducing or increasing the repetition factor (at high signal-to-noise ratio (SINR), low NACKs, the repetition may be as small as 0 or 1). Thus, in such examples, the Tx-UE may repeat the transmission of the data in the micro-slot based on the number of NACKs in a set of one or more NACKs obtained within the time interval. The time interval may be defined at the Layer 1 (e.g., DCI or SCI), Layer 2 (e.g., MAC-CE), or Layer 3 (e.g., RRC) level. For example, the transmitting UE (Tx-UE) may transmit sidelink data to the Rx-UE during a time period from t-x to t-y (where x > y). The Tx-UE may resume transmitting additional sidelink data to the Rx-UE at time t. Before transmitting the additional sidelink data, the Tx-UE may determine the repetition factor based on the number of NACKs obtained from the Rx-UE during the period from t-x to t-y. For example, the transmitting UE may store a lookup table for determining the repetition factor based on the detected number of NACKs. Such a lookup table may be defined in the specification or may be controlled or configured by the gNB or the Rx-UE. That is, in some examples, the gNB, PLC, Rx-UE, or some combination of these entities may use any suitable L1 / L2 / L3 signaling to configure the Tx-UE to implement a given relationship between the number of received NACKs and the repetition count.

[0132] The physical layer of the Rx-UE may apply an LDPC decoder to the data obtained from the Tx-UE. The LDPC decoder uses the parity check bits included in the data to perform linear error correction. The LDPC decoder may maintain statistics regarding the quality of the obtained data before and after applying the linear error correction. For example, the LDPC decoder may maintain a table that defines the relationship between the log-likelihood ratio (LLR) of the data and the number of repetitions of the TB. In some examples, the LDPC decoder may maintain a table that defines the relationship between the number of unsatisfied parity check bits and the number of repetitions of the TB. In some examples, the statistics may include the calculated or estimated signal-to-interference-plus-noise ratio (SINR).

[0133] The MAC layer of the Rx-UE can apply a CRC decoder to the TB or CBG passed up from the physical layer to the MAC layer. For ease of discussion, assume that the TB is not divided into CBs or CBGs. The CRC decoder evaluates the CRC code of the TB to detect changes in the TB. If the CRC decoder determines that there are no changes in the TB, the TB is said to pass the CRC. If the TB passes the CRC, the MAC layer can pass the content of the TB (i.e., the PDU) up to the next higher layer in the protocol stack.

[0134] To enable the TB to pass the CRC, the TB may need to be repeated multiple times. For example, the CRC decoder can obtain multiple repetitions of the TB and compare the corresponding bits within the repetitions of the TB. If the CRC decoder determines an error based on the CRC code of the TB, the CRC decoder does not automatically transmit a NACK to the Tx-UE of the TB. Instead, the CRC decoder can obtain and compare multiple repetitions of the TB. The CRC decoder can use a Chase combining or Incremental redundancy process to determine whether there is an error based on the multiple repetitions. If the CRC decoder determines that there is still an error, the CRC decoder can generate a NACK for the TB.

[0135] The Rx-UE can determine the number of repetitions still required for the TB to pass the CRC based on one of the above statistics or a combination of two or more of the above statistics. For example, the Rx-UE can store data (e.g., a table) that maps the potential values / ranges of the statistics to specific numbers of repetitions. In this example, the Rx-UE can use this data to determine the number of repetitions.

[0136] Figure 9 It is a conceptual diagram illustrating an example of micro-slots 900A to 900F (collectively referred to as "micro-slot 900") according to the technology of the present disclosure and a time slot 902 allocated to the Physical Sidelink Feedback Channel (PSFCH). In Figure 9 the example, micro-slots 900A to 900C belong to the first time slot, and micro-slots 900D to 900F belong to the second time slot. Time slot 902 appears after the first time slot and before the second time slot. The Rx-UE can use the PSFCH to directly provide feedback information to the Tx-UE.

[0137] According to the technology of the present disclosure, the Rx-UE may transmit retransmission request data to the Tx-UE. The retransmission request data may indicate the number of retransmissions required for the TB to pass the CRC. In some examples, the Rx-UE transmits the retransmission request data to the Tx-UE via the PSFCH. The Tx-UE for the sidelink may allocate time slots for PSFCH transmission according to the PSFCH periodicity. The PSFCH periodicity indicates how many time slots allocated for PSSCH transmission occur between the time slots allocated for PSFCH transmission (i.e., PSFCH time slots). The PSFCH periodicity may be set to, for example, one of 0, 1, 2, or 4. If the PSFCH periodicity is set to 0, it means that the PSFCH transmission is disabled. The number of physical resource blocks (PRBs) of the PSSCH associated with the PSFCH time slot may be equal to the PSFCH periodicity multiplied by the number of subchannels and the α value. The α value may be a value of cyclic shift.

[0138] The number of physical resource blocks (PRBs) in the PSFCH time slot associated with each subchannel may be equal to: the number of PRBs of the PSSCH associated with the PSFCH divided by the product of the number of subchannels and the number of PSSCH time slots associated with the PSFCH time slot. For example, in an example where the number of PRBs of the PSSCH associated with the PSFCH is 80, the PSFCH period is 4, and the number of subchannels is 10, the number of PRBs in the PSFCH time slot associated with each subchannel may be equal to 2. In some examples, there may be two PRBs in the concurrent set of PRBs allocated for the PSFCH of each subchannel.

[0139] Each PRB of the PSSCH is mapped to one or more PRBs in the PSFCH time slot. The mapping between the PRB of the PSSCH and the PRB in the PSFCH time slot may be determined based on the following parameters:

[0140] ● The subchannel of the PRB of the PSSCH or the number of subchannels in the PSSCH.

[0141] ● The time slot containing the PRB of the PSSCH

[0142] ● The source ID of the packet transmitted in the PRB, and

[0143] ● The destination ID of the packet transmitted in the PRB.

[0144] In some examples, the Tx-UE stores a table that maps sub-channels, time slots, source IDs, and / or destination IDs to specific PRBs in the PSFCH time slot. In some examples, the table maps a combination of two or more of sub-channels, time slots, source IDs, and destination IDs to a specific PRB in the PSFCH time slot. The table can be configured in various ways. For example, one or more devices such as a gNB or a scheduling entity can transmit data of the table to the Tx-UE.

[0145] The Rx-UE can transmit the retransmission request data to the Tx-UE in one of multiple ways. For example, the Rx-UE can explicitly indicate the retransmission request data in the PRB of the PSFCH. In some examples, the Rx-UE can transmit a predefined sequence to the Tx-UE. The Rx-UE can perform a cyclic shift (CS) on the predefined sequence. In some examples, the Rx-UE can send a first cyclic shift sequence for indicating ACK / NACK and a second cyclic shift sequence for indicating retransmission request data. In other examples, the Rx-UE can use a cyclic shift sequence that jointly indicates ACK / NACK and retransmission request data. Thus, different cyclic shifts can correspond to different combinations of ACK / NACK and retransmission request data. In some such examples, the Rx-UE can use the following table to indicate ACK / NACK and retransmission request data.

[0146] Table 1

[0147] Bit value Representation 0 0 (CS = 0) NACK + Repetition factor 1 (or incremental repetition factor or additional repetition factor) 0 1 (CS = 3) NACK + Repetition factor 2 (or incremental repetition factor or additional repetition factor) 1 0 (CS = 6) ACK + Repetition factor x 1 1 (CS = 9) ACK + Repetition factor y

[0148] In Table 1, the first bit value indicates ACK or NACK, and the second bit value indicates the repetition factor. However, the Rx-UE does not explicitly transmit these two bits. The incremental repetition factor is the positive or negative difference from the previous repetition factor. In some examples, one or more of the cyclic shifts can indicate two or more repetition factors (e.g., a repetition factor and one or more additional repetition factors). In some examples, the repetition factor can correspond to different types of data that the Tx-UE is transmitting. The mapping in Table 1 can change over time. For example, the values of repetition factor 1, repetition factor 2, repetition factor x, and repetition factor y can change over time. For example, the Tx-UE and the Rx-UE can change the values of repetition factor 1, repetition factor 2, repetition factor x, and repetition factor y based on the network conditions. In some examples, the scheduling entity can direct the Tx-UE and / or the Rx-UE to change the values of repetition factor 1, repetition factor 2, repetition factor x, and repetition factor y. Repetition factor 1, 2, x, and y can each be different from one another, or one or more of repetition factor 1 and x and / or repetition factor 2 and y can be the same.

[0149] In this way, the Rx-UE can output feedback data via the physical sidelink feedback channel for transmission to the Tx-UE, where the cyclic shift of the feedback data indicates the ACK or NACK for the data and the repeated request data. Similarly, the Tx-UE can obtain feedback data from the Rx-UE via the physical sidelink feedback channel. The feedback data can have a cyclic shift that identifies which of the ACK or NACK the feedback sequence corresponds to. The Tx-UE can determine the repetition factor based on the cyclic shift of the feedback sequence. The Tx-UE can repeat the transmission of data in a mini-slot a specific number of times. The specific number of times can be based on the cyclic shift of the feedback data (which can be based on the determined repetition factor).

[0150] The Rx-UE can determine the repetition factor for future TBs based on the expected amount of interference. The Rx-UE can determine the expected amount of interference based on LLR statistics and / or signal-to-noise ratio. For example, the Rx-UE can maintain a table that maps ranges of LLR values and / or SINR values to different repetition factors.

[0151] In some examples, the Rx-UE can select the cyclic shift based on the index of the first mini-slot, the index of the last mini-slot, the indices of the mini-slots between the first and last mini-slots, or a combination thereof. For example, if the index of the first mini-slot used for data transmission has a first value (or is in a first range), the Rx-UE can select a first cyclic shift, and if the index of the first mini-slot used for data transmission has a second value (or is in a second range), the Rx-UE can select a second cyclic shift different from the first cyclic shift, and so on. Similarly, if the index of the last mini-slot used for data transmission has a first value (or is in a first range), the Rx-UE can select a first cyclic shift, and if the index of the last mini-slot used for data transmission has a second value (or is in a second range), the Rx-UE can select a second cyclic shift different from the first cyclic shift, and so on. Similar examples can be provided for selecting the cyclic shift using the index of another mini-slot.

[0152] In another example of providing repeated request data to the Tx-UE, ACK and NACK may be signaled in RBs of the PSFCH that are different from the repeated request data. In some such examples, the Rx-UE may use an RB offset to separate the RB of the PSFCH that indicates ACK / NACK from the RB of the PSFCH that indicates repeated request data. Thus, in this example, the Rx-UE may output feedback data for transmission to the Tx-UE via the physical sidelink feedback channel. The feedback data may include a set of RBs that at least includes a first RB and a second RB. The first RB indicates which one of ACK or NACK the feedback data corresponds to. The second RB may include repeated request data that indicates a repetition factor. In this example, the Rx-UE may obtain data a certain number of times in the second mini-slot, where the number of times is based on the repetition factor. Similarly, the Tx-UE may obtain feedback data including the first RB and the second RB from the Rx-UE via the physical sidelink feedback channel. The Tx-UE may determine which one of ACK or NACK the feedback data corresponds to based on the first RB. The Tx-UE may output a repetition of the data a certain number of times in the mini-slot for transmission to the Rx-UE. The number of times is based on the repetition factor. The repetition factor may be based on the second RB.

[0153] The Rx-UE may determine the RB offset between the first RB and the second RB based on the first mini-slot index, the last mini-slot index, the mini-slot indices between the first mini-slot index and the last mini-slot index, or a combination thereof. In some examples, the Rx-UE may store a look-up table that contains multiple entries. Each entry in the look-up table may map the first mini-slot index, the last mini-slot index, the mini-slot indices between the first mini-slot index and the last mini-slot index, or a combination thereof to a specific RB offset. In this example, the Rx-UE may use the look-up table to determine the RB offset to use. For example, if the data received by the Rx-UE starts in a mini-slot with a specific mini-slot index, the Rx-UE may identify the entry in the look-up table associated with that specific mini-slot index. Then, the Rx-UE may use the RB offset indicated by the identified entry.

[0154] The PSFCH can be organized according to one of multiple formats. In PSFCH 0, the resource indices are fixed according to the ascending order of PRB indices and then according to the ascending order of cyclic shift pair indices from a cyclic shift pair. In some formats of the PSFCH other than PSFCH format 0, the repeated request data transmitted from the Rx-UE to the Tx-UE is multiplexed with HARQ-ACK and / or other data and data ACK / NACK data. The Tx-UE can apply a polarization encoder or a sequence-based encoder to the multiplexed data to determine the repeated request data. In one example, the Rx-UE uses PSFCH format 0 to send ACK / NACK bits. In this example, since the repeated request data may require more bits, the Rx-UE can use another format to send the repeated request data. In some examples, the Rx-UE can send repeated request data indicating the number of repetitions required for the current TB by the CRC, and can also send repeated request data indicating the number of repetitions requested for future TBs.

[0155] In some examples, if there is a NACK, the Rx-UE can indicate which RV indices the Tx-UE is to use during the remaining retransmissions of the current TB. In other words, the Rx-UE can transmit data indicating a set of one or more RV indices for the TB to the Tx-UE. If the Rx-UE fails to successfully decode the TB and thus transmits a NACK to the Tx-UE, the Tx-UE can send a version of the TB with an RV index from the set of RV indices. In some examples, the Rx-UE can indicate the set of RV indices by indicating which micro-slot indices are used for retransmitting the TB. A micro-slot index is an index that identifies a micro-slot. Then, the Tx-UE can determine the RV indices based on the micro-slot indices. For example, the Rx-UE can indicate micro-slot indices 2, 4, and 6, and the Tx-UE can determine that these micro-slot indices correspond to RV indices 2, 4, and 6. In this way, the Rx-UE can output a micro-slot indication for transmission to the second wireless device, the micro-slot indication indicating the micro-slot indices for retransmission. The Rx-UE can obtain a version of the data with the RV indices based on the micro-slot indication from the Tx-UE. In some examples, the Tx-UE can request these RV indices from the Rx-UE. The requested RV indices can be different from the RV indices used in the previous transmission during the previous micro-slot.

[0156] In this way, the Tx-UE can obtain a micro-slot indication from the Rx-UE, the micro-slot indication indicating the micro-slot indices for retransmission. The Tx-UE can determine the RV indices based on the micro-slot indication. The Tx-UE can output a version of the data with the RV indices for transmission to the second wireless device.

[0157] The Tx-UE can implement an LDPC decoder that applies error correction at the physical layer. The decoder maintains input LLR statistics and output LLR statistics. The input LLR statistics provide information about the error rate before error correction. The output LLR statistics provide information about the error rate after error correction. In some examples, the Rx-UE can transmit feedback to the Tx-UE indicating a soft RV start index and a soft RV end index. The CB is stored in a circular buffer. Different repetitions of the Cb can have different repetition versions. Thus, different repetitions of the CB can include different parts of the CB. The soft RV start index indicates the starting point of a repetition in the circular buffer. The soft RV end index indicates the ending point of the repetition in the circular buffer. The Rx-UE can determine the soft RV start index and the soft RV end index based on the input LLR and output LLR of the decoder and based on LDPC statistics.

[0158] In some examples, instead of the Rx-UE providing repetition request data to the Tx-UE, the Tx-UE can apply channel and interference prediction techniques based on channel statistics and interference statistics. The Tx-UE can use the channel and interference prediction techniques to predict the SINR. Based on the predicted SINR, the UE can predict the MCS or predict the amount of resources required to achieve a specific block error rate requirement. Then, based on the current allocation size and the predicted required resources, the UE determines how many repetitions are needed. Thus, the predicted SINR can help the Tx-UE set the number of remaining repetitions required for the TB to pass the CRC. In some examples, when transmitting a new TB, the Tx-UE can use the determined number of repetitions.

[0159] In some examples, when determining the number of repetitions, the Tx-UE can consider other factors such as priority, QoS, and remaining packet delay budget (PDB). In other words, the Tx-UE can determine the repetition factor based on the priority, QoS, or remaining PDB corresponding to the data. The Tx-UE can output repetitions of the data for transmission, where the number of repetitions is based on the priority, QoS, or remaining PDB. In some examples, the Tx-UE can store a lookup table. Each entry in the lookup table maps each factor (e.g., priority, QoS, remaining PDB) to a specific number of repetitions. The Tx-UE can identify the entry in the lookup table associated with one or more factors. The Tx-UE can determine that the number of repetitions is the number of repetitions specified by the identified entry.

[0160] Figure 10 is a block diagram illustrating an example of the hardware implementation of a network node 1000 employing a processing system 1014. For example, the network node 1000 can be a user equipment (UE) as illustrated in any one or more of Figure 1 or Figure 2 In another example, the network node 1000 can be as Figure 1 orFigure 2 a base station exemplified in any one or more of them. For example, network node 1000 may be one of the scheduling entities 108. In some examples, network node 1000 may be Figure 8 the PLC 804 of

[0161] Network node 1000 may include a processing system 1014. The processing system 1014 may have one or more processors 1004. Examples of processors 1004 include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic components, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. In various examples, network node 1000 may be configured to perform any one or more of the functions described herein. For example, the processor 1004 utilized in network node 1000 may be configured to (e.g., in coordination with the memory 1005) implement any one or more of the processes and procedures described below and Figure 10 exemplified in

[0162] The processing system 1014 may be implemented using a bus architecture generally represented by the bus 1002. The bus 1002 may include any number of interconnected buses and bridges, depending on the specific application of the processing system 1014 and overall design constraints. The bus 1002 communicatively couples the various circuits including one or more processors (generally represented by the processor 1004), the memory 1005, and the computer-readable medium (generally represented by the computer-readable storage medium 1006). The bus 1002 may also link various other circuits (such as timing sources, peripherals, voltage regulators, and power management circuits), which are well known in the art and will not be described further herein. The bus interface 1008 provides an interface between the bus 1002 and the transceiver 1010. The transceiver 1010 provides a communication interface or component for communicating with various other devices via a transmission medium. Depending on the nature of the device, a user interface 1012 (e.g., keypad, display, speaker, microphone, joystick) may also be provided. The user interface 1012 is optional and, in some examples, such as for a base station, the user interface 1012 is omitted.

[0163] In some aspects of the present disclosure, the processor 1004 may include a resource allocation circuit 1040 configured (e.g., in coordination with the memory 1005) for various functions. The resource allocation circuit 1040 may be configured to output an indication of a transmission type among a plurality of transmission types for providing to a device (e.g., a TxUE). Each of the plurality of transmission types is a different mode of organizing data into micro-slots reserved for sidelink transmission. The resource allocation circuit 1040 may allocate resources to be used by the device for sidelink transmission.

[0164] The processor 1004 may be responsible for managing the bus 1002 and general processing, including the execution of software stored on the computer-readable storage medium 1006. The software, when executed by the processor 1004, causes the processing system 1014 to perform the various functions described hereinafter for any particular device. The processor 1004 may also use the computer-readable storage medium 1006 and the memory 1005 to store data that the processor 1004 manipulates when executing the software.

[0165] One or more processors 1004 in the processing system may execute the software. The software should be broadly construed to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. The software may reside on the computer-readable storage medium 1006. The computer-readable storage medium 1006 may be a non-transitory computer-readable medium. Non-transitory computer-readable media include, for example, magnetic storage devices (e.g., hard disks, floppy disks, magnetic strips), optical disks (e.g., compact disc (CD) or digital versatile disc (DVD)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer-readable storage medium 1006 may reside within the processing system 1014, outside the processing system 1014, or be distributed across multiple entities including the processing system 1014. The computer-readable storage medium 1006 may be embodied in a computer program product. For example, the computer program product may include the computer-readable medium in a package material. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure, depending on the particular application and overall design constraints imposed on the overall system.

[0166] In one or more examples, the computer-readable storage medium 1006 may store computer-executable code including resource allocation instructions 1052 that configure the network node 1000 for various functions. For example, the resource allocation instructions 1052 may configure the network node 1000 to output an indication of a transmission type among a plurality of transmission types for providing to a second wireless device (e.g., TxUE). Each transmission type among the plurality of transmission types is a different pattern of organizing data into micro-slots reserved for sidelink transmission. Execution of the resource allocation instructions 1052 may cause the network node 1000 to allocate resources to be used for sidelink transmission to the second wireless device.

[0167] In one configuration, the network node 1000 is a wireless communication device that includes components for: outputting an indication of a transmission type among a plurality of transmission types for providing to a second wireless device, where each transmission type among the plurality of transmission types is a different pattern of organizing data into micro-slots reserved for sidelink transmission. The network node 1000 also includes components for allocating resources to be used for sidelink transmission to the second wireless device. In one aspect, the foregoing components for outputting an indication of the transmission type and the foregoing components for allocating resources may be Figure 10 the processor 1104 shown and configured to perform the functions recited by the foregoing components. In another example, the foregoing components may be a circuit or any device configured to perform the functions recited by the foregoing components.

[0168] In the above example, the circuits included in the processor 1004 are provided merely as examples, and other components for performing the described functions may be included within various aspects of the present disclosure, including but not limited to instructions stored in the computer-readable storage medium 1006 or in Figure 1 and / or Figure 2 any other suitable device or component described in any one of and utilizing, for example, processes and / or algorithms described elsewhere in the present disclosure.

[0169] Figure 11 is a conceptual diagram showing an example of a hardware implementation of an exemplary scheduled entity 1100 employing a processing system 1114. According to various aspects of the present disclosure, the processing system 1114 may include elements having one or more processors 1104, or any portion of an element, or any combination of elements. For example, the scheduled entity 1100 may be a user equipment (UE) as shown in any one or more of Figure 1 or Figure 2 any one or more thereof.

[0170] The processing system 1114 may be associated with Figure 10is substantially the same as the processing system 1014 illustrated therein, which includes a bus interface 1108, a bus 1102, a memory 1105, one or more processors 1104, and a computer-readable storage medium 1106. Additionally, the scheduled entity 1100 may include a user interface 1112 and a transceiver 1110, which are substantially similar to the user interface and transceiver described above in Figure 10 . That is, the processor 1104 utilized in the scheduled entity 1100 may be configured (e.g., in coordination with the memory 1105) to implement any one or more of the processes described elsewhere in the present disclosure.

[0171] In some aspects of the present disclosure, the processor 1104 may include a transmission scheduling circuit 1140 configured (e.g., in coordination with the memory 1105) for various functions. For example, the transmission scheduling circuit 1140 may determine a transmission type from a plurality of transmission types. Each transmission type in the plurality of transmission types is a different pattern for organizing data into micro-slots reserved for sidelink transmission. The transceiver 1110 may output data in one or more micro-slots reserved for sidelink transmission for transmission to a second wireless device according to the determined transmission type.

[0172] In some examples, the transmission scheduling circuit 1140 may determine a repetition factor based on the priority, QoS, or remaining PDB corresponding to the data. The transceiver 1110 may repeat the transmission of the data a number of times, where the number is based on the repetition factor.

[0173] In some examples, the computer-readable storage medium 1106 may store computer-executable code including transmission scheduling instructions 1152 that will configure the scheduled entity 1100 for various functions. For example, the transmission scheduling instructions 1152 may be configured to cause the scheduled entity 1100 to implement one or more of the functions described elsewhere in this disclosure. For example, when executed, the transmission scheduling instructions 1152 may cause the processor 1104 to obtain first data. At least one of the following may be applied to the first data: the first data is obtained from a second wireless device, the first data indicates a reliability or rate requirement, the first data indicates an initial resource pool configuration, or the first data indicates a priority, quality of service (QoS), or remaining packet delay budget (PDB). Execution of the transmission scheduling instructions 1152 may cause the processor 1104 to output second data in one or more micro-slots reserved for sidelink transmission for transmission to the second wireless device according to the determined transmission type. The transmission type may depend on the first data. Each of the various transmission types is a different pattern for organizing data into the micro-slots reserved for sidelink transmission. The second data may include payload data for conveying information to an Rx-UE or another device. For example, the second data may include encoded voice or video data, web page request or response data, API request or response data, sensor data, telemetry data, and so on. In some examples, the components for obtaining the first data and the components for outputting the second data may include one or more processors, such as the processor 1104. Other components for performing these functions may include any suitable processor that executes instructions stored in, for example, the computer-readable storage medium 1106.

[0174] In one configuration, a device for wireless communication (e.g., network node 1000, scheduled entity 1100, etc.) includes components for performing the techniques of this disclosure. In one aspect, the foregoing components may be Figure 10 and Figure 11 the processors 1004, 1104 shown to be configured to perform the functions recited by the foregoing components. In another aspect, the foregoing components may be a circuit or any device configured to perform the functions recited by the foregoing components.

[0175] In the above example, the circuits included in the processor 1004 are provided only as examples, and other components for performing the described functions may be included within aspects of this disclosure, including but not limited to those stored in the computer-readable storage medium 1006, or in Figure 1 or Figure 2 any other suitable device or component described in any of the foregoing and utilizing instructions for processes and / or algorithms described, for example, herein with respect to Figure 10 and / or Figure 11 described.

[0176] Figure 12 is a flowchart illustrating an example operation of a transmitting UE (Tx-UE) according to the techniques of the present disclosure. The Tx-UE may be a scheduled entity 106, UE 806, UE 808, scheduled entity 1100, gNB 802, PLC 804, or another device. In Figure 12 an example, the Tx-UE may obtain first data (1200). In some examples, the Tx-UE obtains the first data from a second wireless device (e.g., an Rx-UE, gNB, scheduled entity, etc.). In some examples where the Tx-UE obtains the first data from a second wireless device, the first data may identify a transmission type. In some examples, the first data may include one or more of reliability or rate requirements, the first data includes an initial resource pool configuration, or the first data includes a priority, quality of service (QoS), or remaining packet delay budget (PDB) corresponding to the data. The Tx-UE may obtain the first data from a data storage system, from one or more devices as user input, or otherwise obtain the first data. In some examples, the Tx-UE determines a transmission type from a plurality of transmission types based on the first data. Each of the plurality of transmission types is a different pattern of organizing data into micro-slots reserved for sidelink transmission.

[0177] In some examples, the plurality of transmission types includes two or more of a first transmission type, a second transmission type, or a third transmission type. When transmitting data according to the first transmission type, multiple micro-slots in one or more time slots are used to transmit a transport block (TB) containing the data. When transmitting data according to the second transmission type, the TB containing the data is repeated with the same or different redundancy versions (RVs) in different micro-slots within the one or more micro-slots. When transmitting data according to the third transmission type, a time slot includes a first set of one or more micro-slots and a second set of one or more micro-slots, the data includes third data and fourth data, and a first TB containing the third data is in the first set of micro-slots, and a second TB containing the fourth data is in the second set of micro-slots.

[0178] The Tx-UE may determine the transmission type based on an indication obtained by the Tx-UE from a third wireless device. Thus, the Tx-UE may obtain data (e.g., first data) including an indication identifying the transmission type obtained from a second device (e.g., the Tx-UE). The third wireless device may be a sidelink controller, a base station, a primary UE device, or another type of device. In some examples, the indication includes radio resource control (RRC) data, media access control - control element (MAC-CE) data, or downlink control information (DCI) data. In some examples, the Tx-UE may determine the transmission type based on one or more of the following: the reliability or rate requirement corresponding to the data, the initial resource pool configuration, or the priority, quality of service (QoS), or remaining packet delay budget (PDB) corresponding to the data.

[0179] Additionally, the Tx-UE may output second data in one or more micro-slots reserved for sidelink transmission for transmission to a receiving wireless device (1202) according to the transmission type among multiple transmission types. For example, in an example where the Tx-UE is the scheduled entity 1100, the transceiver 1110 may output data for transmission to the receiving wireless device. The transmission type depends on the first data. Each of the multiple transmission types is a different mode of organizing data into the micro-slots reserved for sidelink transmission. The receiving wireless device may be the same device or a different device as the wireless device from which the first data is obtained. The second data may include payload data for communicating information to the Rx-UE or another device. For example, the second data may include encoded voice or video data, web page request or response data, API request or response data, sensor data, telemetry data, and so on.

[0180] Additionally, in some examples, the Tx-UE may obtain an indication of the number of repetitions required for cyclic redundancy check from the Rx-UE via a physical sidelink feedback channel. The Tx-UE may output repetitions of the data in the micro-slots according to a repetition factor for transmission to the Rx-UE. The repetition factor is based on the number of repetitions required for cyclic redundancy check.

[0181] Figure 13 is a flowchart illustrating an example operation of a receiving UE (Rx-UE) according to the techniques of the present disclosure. The Rx-UE may be the scheduled entity 106, UE 806, UE 808, the scheduled entity 1100, gNB 802, PLC 804, or another device. In Figure 13In an example, the Rx-UE may output retransmission request data for transmission to a second wireless device, where the retransmission request data indicates the number of repetitions (1300) of the TB. The second wireless device may be a transmitting UE (Tx-UE). In some examples, the Rx-UE outputs the retransmission request data to the second wireless device via a physical sidelink feedback channel. The number of repetitions of the TB may be the number of repetitions of the TB required by the CRC.

[0182] In some examples, the Rx-UE may output feedback data for transmission to a second wireless device via a physical sidelink feedback channel, where a cyclic shift of a known sequence indicates an ACK or NACK for the data as well as the retransmission request data. In another example, the Tx-UE may output feedback data for transmission to the Tx-UE via a physical sidelink feedback channel. The feedback data may include a set of RBs, where the set of RBs includes at least a first RB and a second RB. The first RB indicates which one of an ACK or NACK the feedback data corresponds to. The second RB includes retransmission request data indicating a repetition factor. In this example, the Rx-UE may obtain the second data a certain number of times in a second micro-slot, where the number of times is based on the repetition factor. The second data may include payload data for conveying information to the Rx-UE or another device. For example, the second data may include encoded voice or video data, web request or response data, API request or response data, sensor data, telemetry data, and so on.

[0183] The Rx-UE may obtain a set (1302) of repetitions of the TB in one or more micro-slots reserved for sidelink transmission from the second wireless device. This set of repetitions of the TB includes the number of repetitions of the TB. Additionally, in some examples, the Rx-UE may output a micro-slot indication for transmission to the second wireless device, where the micro-slot indication indicates a micro-slot index for retransmission. The Rx-UE may obtain a version of the data with a redundancy version (RV) index based on the micro-slot indication from the second wireless device.

[0184] In some examples, the components for outputting the retransmission request data, the feedback data, and the micro-slot indication may include one or more processors, such as the processor 1004 of the network device 1000 or the processor 1104 of the scheduled entity 1100. Similarly, the components for obtaining this set of repetitions of the TB or other data may include the processor 1004 of the network device 1000 or the processor 1104 of the scheduled entity 1100. The components for obtaining the data in the micro-slot may include the processor 1004 of the network device 1000 or the processor 1104 of the scheduled entity 1100.

[0185] Figure 14is a flowchart illustrating an example operation of an apparatus according to the techniques of the present disclosure. The apparatus can be one of a scheduling entity 108, a gNB 802, a PLC 804, a network node 1000, or another apparatus. In Figure 14 the example, the apparatus can output an indication of a transmission type among a plurality of transmission types for providing to a second wireless device (1400). For example, the apparatus outputs the indication to cause a transceiver to convey the indication of the transmission type to the second wireless device. The second wireless device can be a scheduled entity 106, a UE 806, a UE 808, a scheduled entity 1100, or another apparatus. Each of the plurality of transmission types is a different pattern of organizing data into a micro-slot reserved for sidelink transmission. The transmission type can include any one of transmission types A, B, or C, as described elsewhere in the present disclosure.

[0186] The apparatus can allocate resources (1402) to be used for sidelink transmission to the second wireless device. For example, the apparatus can identify the resources and convey information identifying the identified resources to the second wireless device.

[0187] The following is a non-limiting list of embodiments according to one or more techniques of the present disclosure.

[0188] Embodiment 1 is a method of wireless communication at a first wireless device, the method comprising: obtaining first data, wherein at least one of the following: the first data is obtained from a second wireless device, the first data indicates a reliability or rate requirement, the first data indicates an initial resource pool configuration, the first data indicates a priority, the first data indicates a quality of service (QoS), or the first data indicates a remaining packet delay budget (PDB); outputting second data in one or more micro-slots reserved for sidelink transmission for transmission to a receiving wireless device according to a transmission type among a plurality of transmission types, wherein: the transmission type depends on the first data, and each of the plurality of transmission types is a different pattern of organizing the second data into the one or more micro-slots reserved for sidelink transmission.

[0189] Embodiment 2 is the method according to Embodiment 1, wherein: the multiple transmission types include two or more of a first transmission type, a second transmission type, or a third transmission type. When the second data is organized into the micro-slots according to the first transmission type, the one or more micro-slots include multiple micro-slots of one or more time slots and are used to transmit a transport block (TB) containing the second data. When the second data is organized into the micro-slots according to the second transmission type, the TB containing the second data is repeated with the same or different redundancy versions (RVs) in different micro-slots among the one or more micro-slots. And when the second data is organized into the micro-slots according to the third transmission type, a time slot includes a first set of one or more of the micro-slots and a second set of one or more of the micro-slots. The second data includes third data and fourth data, and a first TB containing the third data is in the first set of micro-slots, and a second TB containing the fourth data is in the second set of micro-slots.

[0190] Embodiment 3 is the method according to any one of Embodiments 1 and 2, wherein: the first data includes an indication identifying the transmission type obtained from the second wireless device, and the second wireless device is one of a sidelink controller, a base station, or a master user equipment (UE) device.

[0191] Embodiment 4 is the method according to Embodiment 3, wherein the indication includes radio resource control (RRC) data, medium access control - control element (MAC-CE) data, or downlink control information (DCI) data.

[0192] Embodiment 5 is the method according to any one of Embodiments 1 to 4, wherein the method further includes: outputting a repetition of the second data a certain number of times for transmission, wherein the number of repetitions is based on the priority, the QoS, or the remaining PDB.

[0193] Embodiment 6 is the method according to any one of Embodiments 1 to 5, wherein the method further includes: outputting a first number of repetitions of the second data for transmission, wherein the first number is based on a first repetition factor, wherein the first repetition factor is based on the logical channel group (LCG) priority or quality of service (QoS) of the second data; obtaining feedback from the receiving wireless device; and outputting a second number of repetitions of third data for transmission, wherein the second number is based on a second repetition factor, wherein the second repetition factor is based on the feedback from the receiving wireless device and the PDB deadline of the packet containing the third data.

[0194] Example 7 is the method according to any one of Examples 1 to 6, wherein outputting the second data includes: repeating the output of the second data in the mini-slot for transmission according to a repetition factor based on the number of negative acknowledgments (NACKs) in a set of one or more NACKs obtained within a time interval.

[0195] Example 8 is the method according to any one of Examples 1 to 7, wherein: the method further includes: obtaining an indication of the number of repetitions required for cyclic redundancy check from the receiving wireless device via a physical sidelink feedback channel, and outputting the second data includes: repeating the output of the second data in the mini-slot for transmission to the receiving wireless device according to a repetition factor based on the number of repetitions required for the cyclic redundancy check.

[0196] Example 9 is the method according to any one of Examples 1 to 8, wherein: the mini-slot is a first mini-slot, and the method further includes: obtaining feedback data from the receiving wireless device via a physical sidelink feedback channel, wherein the feedback data has a cyclic shift identifying which of an acknowledgment (ACK) or a negative acknowledgment (NACK) the feedback data corresponds to; repeating the output of third data a specific number of times in a second mini-slot for transmission, wherein the specific number is based on the cyclic shift of the feedback data.

[0197] Example 10 is the method according to any one of Examples 1 to 9, wherein: the mini-slot is a first mini-slot, and the method further includes: obtaining feedback data from the receiving wireless device via a physical sidelink feedback channel, the feedback data including a set of resource blocks (RBs), the set of resource blocks (RBs) including at least a first RB and a second RB, wherein the first RB indicates which of an acknowledgment (ACK) or a negative acknowledgment (NACK) the feedback data corresponds to; and repeating the output of third data a certain number of times in the second mini-slot for transmission to the receiving wireless device, wherein the number is based on a repetition factor, and the repetition factor is based on the second RB.

[0198] Example 11 is the method according to any one of Examples 1 to 10, further including obtaining a mini-slot indication from the receiving wireless device, the mini-slot indication indicating a mini-slot index for retransmission; and outputting a version of the second data having a redundancy version (RV) index based on the mini-slot indication for transmission to the receiving wireless device.

[0199] Embodiment 12 is the method according to any one of Embodiments 1 to 11, further comprising: obtaining first PSFCH data formatted in a first physical side link feedback channel (PSFCH) format, the first PSFCH data indicating an acknowledgement (ACK) or a negative acknowledgement (NACK); obtaining second PSFCH data formatted in a second PSFCH format different from the first PSFCH format, the second PSFCH data bits indicating a repetition factor; and outputting a repetition of the second data in the mini-slot according to the repetition factor for transmission to the receiving wireless device.

[0200] Embodiment 13 is a method for wireless communication at a first wireless device, comprising: providing an indication of a transmission type among a plurality of transmission types to a second wireless device, each of the plurality of transmission types being a different mode of organizing data into mini-slots reserved for sidelink transmission; and allocating resources to be used for sidelink transmission to the second wireless device.

[0201] Embodiment 14 is the method according to Embodiment 13, wherein: the plurality of transmission types includes two or more of a first transmission type, a second transmission type, or a third transmission type. When the second data is organized into the mini-slot according to the first transmission type, the one or more mini-slots include a plurality of mini-slots of one or more time slots and are used to transmit a transport block (TB) containing the second data. When the second data is organized into the mini-slot according to the second transmission type, the TB containing the second data is repeated in different mini-slots of the one or more mini-slots with the same or different redundancy versions (RVs). When the second data is organized into the mini-slot according to the third transmission type, the time slot includes a first set of one or more of the mini-slots and a second set of one or more of the mini-slots. The second data includes third data and fourth data, and a first TB containing the third data is in the first set of mini-slots, and a second TB containing the fourth data is in the second set of mini-slots.

[0202] Embodiment 15 is a method for wireless communication at a first wireless device, the method comprising: outputting repetition request data for transmission to a second wireless device, the repetition request data indicating the number of repetitions of a transport block (TB); and obtaining, from the second wireless device, a set of repetitions of the TB in one or more mini-slots reserved for sidelink transmission, wherein the set of repetitions of the TB includes the number of repetitions of the TB.

[0203] Embodiment 16 is the method according to Embodiment 15, wherein outputting the repeated request data for transmission to the second wireless device includes: outputting the repeated request data for transmission to the second wireless device via a physical sidelink feedback channel.

[0204] Embodiment 17 is the method according to any one of Embodiments 15 and 16, wherein the number of repetitions of the TB is the number of repetitions of the TB required for cyclic redundancy check.

[0205] Embodiment 18 is the method according to any one of Embodiments 15 to 17, wherein outputting the repeated request data for transmission to the second wireless device includes: outputting feedback data for transmission to the second wireless device via a physical sidelink feedback channel, wherein a cyclic shift of the feedback data indicates an acknowledgement (ACK) or a negative acknowledgement (NACK) for the data and the repeated request data.

[0206] Embodiment 19 is the method according to any one of Embodiments 15 to 18, wherein: the data is first data, the mini-slot is a first mini-slot, outputting the repeated request data includes outputting feedback data for transmission to the second wireless device via a physical sidelink feedback channel, the feedback data includes a set of resource blocks (RBs), the set of resource blocks (RBs) includes at least a first RB and a second RB, the first RB indicates which one of an acknowledgement (ACK) or a negative acknowledgement (NACK) the feedback data corresponds to, and the second RB includes repeated request data indicating a repetition factor, and the method further includes obtaining the second data a certain number of times in a second mini-slot, wherein the number of times is based on the repetition factor.

[0207] Embodiment 20 is the method according to any one of Embodiments 15 to 19, wherein the method further includes: outputting a mini-slot indication for transmission to the second wireless device, the mini-slot indication indicating a mini-slot index for retransmission; and obtaining, from the second wireless device, a version of the data having a redundancy version (RV) index based on the mini-slot indication.

[0208] Embodiment 21 is an apparatus for wireless communication, the apparatus including: one or more processors; and a memory including instructions executable by the one or more processors, wherein the one or more processors are configured to execute the instructions to cause the apparatus to perform the method according to any one of Embodiments 1 to 12.

[0209] Embodiment 22 is a user equipment (UE), which includes a transceiver, one or more processors, and a memory. The memory includes instructions executable by the one or more processors. Wherein the one or more processors are configured to execute the instructions to cause the UE to perform the method according to any one of Embodiments 1 to 12. Wherein the transceiver is configured to obtain the first data and transmit the second data.

[0210] Embodiment 23 is the UE according to Embodiment 22, wherein the UE is a vehicle.

[0211] Embodiment 24 is a device for wireless communication, which includes one or more processors; and a memory. The memory includes instructions executable by the one or more processors. Wherein the one or more processors are configured to execute the instructions to cause the device to perform the method according to any one of Embodiments 13 to 14.

[0212] Embodiment 25 is a base station, which includes a transceiver, one or more processors, and a memory. The memory includes instructions executable by the one or more processors. Wherein the one or more processors are configured to execute the instructions to cause the base station to perform the method according to any one of Embodiments 13 to 14. Wherein the transceiver is configured to output the indication of the transmission type.

[0213] Embodiment 26 is a device for wireless communication, which includes one or more processors; and a memory. The memory includes instructions executable by the one or more processors. Wherein the one or more processors are configured to execute the instructions to perform the method according to any one of Embodiments 15 to 20.

[0214] Embodiment 27 is a UE, which includes a transceiver, one or more processors, and a memory. The memory includes instructions executable by the one or more processors. Wherein the one or more processors are configured to execute the instructions to cause the UE to perform the method according to any one of Embodiments 15 to 20. And wherein the transceiver is configured to output the repeated request data and obtain the set of repetitions.

[0215] Embodiment 28 is the UE according to Embodiment 25, wherein the UE is a vehicle.

[0216] Embodiment 29 is a device for wireless communication, which includes components for performing the method according to any one of Embodiments 1 to 12.

[0217] Example 30 is a device for wireless communication, the device comprising: components for performing the method according to any one of Examples 13 to 14.

[0218] Example 31 is a device for wireless communication, the device comprising: components for performing the method according to any one of Examples 15 to 20.

[0219] Example 32 is a non-transitory computer-readable medium, the non-transitory computer-readable medium comprising instructions that, when executed by a device, cause the device to perform the method according to any one of Examples 1 to 12.

[0220] Example 33 is a non-transitory computer-readable medium, the non-transitory computer-readable medium comprising instructions that, when executed by a device, cause the device to perform the method according to any one of Examples 13 to 14.

[0221] Example 34 is a non-transitory computer-readable medium, the non-transitory computer-readable medium comprising instructions that, when executed by a device, cause the device to perform the method according to any one of Examples 15 to 20.

[0222] The detailed description set forth above in connection with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. To provide a thorough understanding of the various concepts, the detailed description includes specific details. However, one of ordinary skill in the art will readily recognize that the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0223] Although this specification describes certain aspects and examples with reference to some illustrations, those skilled in the art will understand that additional specific implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, packaging arrangements. For example, various specific implementations and / or uses can be generated via integrated circuit (IC) implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, a wide variety of applicability of the described innovations can occur. Specific implementations can span a spectrum from chip-level or modular components to non-modular, non-chip-level implementations, and further to the spectrum of aggregated, distributed, or original equipment manufacturer (OEM) devices or systems that incorporate one or more aspects of the disclosed technology. In some practical settings, devices incorporating the described aspects and features will necessarily also include additional components and features for the specific implementation and practice of the implementations protected and described by the claims. For example, the transmission and reception of wireless signals includes several components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). It is intended that the disclosed technology can be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. having various sizes, shapes, and configurations.

[0224] By way of example, various aspects of the present disclosure can be implemented within systems defined by 3GPP, such as Fifth Generation New Radio (5G NR), Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). The various aspects can also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standards, network architectures, and / or communication standards employed will depend on the specific application and the overall design constraints imposed on the system.

[0225] The present disclosure uses the term "exemplary" to mean "serving as an example, instance, or illustration". Any particular implementation or aspect described herein as "exemplary" is not necessarily to be construed as superior to or better than other aspects of the present disclosure. Similarly, the term "aspect" does not require that all aspects of the present disclosure include the described features, advantages, or modes of operation. The present disclosure uses the terms "coupled" and / or "communicatively coupled" to refer to either a direct or an indirect coupling between two objects. For example, if object A physically contacts object B and object B contacts object C, then objects A and C can still be considered to be coupled to each other even if they do not directly physically contact each other. For example, a first object can be coupled to a second object even if the first object has never directly physically contacted the second object. The present disclosure uses the term "circuit" in a broad sense to include both a hardware implementation of electronic devices and conductors (where these electronic devices and conductors, when connected and configured, perform the functions described in the present disclosure, without limitation as to the type of electronic circuit) and a software implementation of information and instructions (where these information and instructions, when executed by a processor, perform the functions described in the present disclosure).

[0226] Figures 1 to 14 One or more of the components, steps, features, and / or functions illustrated therein may be rearranged and / or combined into a single component, step, feature, or function or embodied in several components, steps, or functions. Additional elements, components, steps, and / or functions may also be added without departing from the novel features disclosed herein. Figures 1 to 14 The apparatuses, devices, and / or components illustrated therein may be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein may also be effectively implemented in software and / or embedded in hardware.

[0227] It should be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. It should be understood that based on design preferences, the specific order or hierarchy of steps in these methods may be rearranged. The appended method claims present the elements of the various steps in an example order, but are not meant to be limited to the specific order or hierarchy presented unless expressly stated herein.

[0228] The applicant provides this description to enable any person skilled in the art to practice the various aspects described herein. Those skilled in the art will readily recognize various modifications to these aspects, and can apply the general principles defined herein to other aspects. The applicant does not intend the claims to be limited to the aspects shown herein, but should be accorded the full scope consistent with the language of the claims, where a reference to an element in the singular is not intended to mean "one and only one" but "one or more" unless specifically stated otherwise. Unless specifically stated otherwise, the present disclosure uses the term "some" to refer to one or more. A phrase referring to "at least one" of a list of items means any combination of those items, including a single member. As an example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are known or later will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is explicitly recited in the claims. No claim element shall be construed under the provisions of 35 U.S.C. § 112(f) unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, the phrase "step for".

Claims

1. An apparatus for wireless communication, the apparatus comprising: one or more processors; and a memory including instructions executable by the one or more processors, wherein the one or more processors are configured to: obtain first data, where at least one of the following: the first data is obtained from a second wireless device, the first data indicates a reliability or rate requirement, the first data indicates an initial resource pool configuration, the first data indicates a priority, the first data indicates quality of service (QoS), or the first data indicates a remaining packet delay budget (PDB); output second data in one or more micro-slots reserved for sidelink transmission for transmission to a receiving wireless device according to a transmission type among multiple transmission types, where: the transmission type depends on the first data, and each transmission type among the multiple transmission types is a different mode of organizing the second data into the one or more micro-slots reserved for sidelink transmission.

2. The apparatus according to claim 1, where: the multiple transmission types include two or more of a first transmission type, a second transmission type, or a third transmission type, when the second data is organized into the micro-slots according to the first transmission type, the one or more micro-slots include multiple micro-slots of one or more time slots and are used to transmit a transport block (TB) containing the second data, when the second data is organized into the micro-slots according to the second transmission type, the TB containing the second data is repeated in different micro-slots of the one or more micro-slots with the same or different redundancy versions (RVs), and when the second data is organized into the micro-slots according to the third transmission type, a time slot includes a first set of one or more of the micro-slots and a second set of one or more of the micro-slots, the second data includes third data and fourth data, and a first TB containing the third data is in the first set of micro-slots, and a second TB containing the fourth data is in the second set of micro-slots.

3. The apparatus according to claim 1, where: the first data includes an indication identifying the transmission type obtained from the second wireless device, and the second wireless device is one of a sidelink controller, a base station, or a master user equipment (UE) device.

4. The apparatus according to claim 3, where the indication includes radio resource control (RRC) data, medium access control - control element (MAC-CE) data, or downlink control information (DCI) data.

5. The apparatus according to claim 1, where the one or more processors are further configured to: output a repetition of the second data for transmission, where the number of repetitions is based on the priority, the QoS, or the remaining PDB.

6. The apparatus according to claim 1, where the one or more processors are further configured to: Output a first number of repetitions of the second data for transmission, where the first number is based on a first repetition factor, and the first repetition factor is based on the logical channel group (LCG) priority or quality of service (QoS) of the second data; Obtain feedback from the receiving wireless device; and Output a second number of repetitions of the third data for transmission, where the second number is based on a second repetition factor, and the second repetition factor is based on the feedback from the receiving wireless device and the PDB deadline of the packet containing the third data.

7. The apparatus according to claim 1, wherein the one or more processors are further configured to: output a repetition of the second data in the mini-slot for transmission according to a repetition factor based on the number of negative acknowledgments (NACKs) in a set of one or more NACKs obtained within a time interval.

8. The apparatus according to claim 1, wherein the one or more processors are further configured to: Obtain an indication of the number of repetitions required for cyclic redundancy check from the receiving wireless device via a physical sidelink feedback channel, and Output a repetition of the second data in the mini-slot for transmission to the receiving wireless device according to a repetition factor, where the repetition factor is based on the number of repetitions required for the cyclic redundancy check.

9. The apparatus according to claim 1, wherein: The mini-slot is a first mini-slot, and The one or more processors are further configured to: Obtain feedback data from the receiving wireless device via a physical sidelink feedback channel, where the feedback data has a cyclic shift indicating which of an acknowledgment (ACK) or a negative acknowledgment (NACK) the feedback data corresponds to; and Output a specific number of repetitions of the third data in a second mini-slot for transmission, where the specific number is based on the cyclic shift of the feedback data.

10. The apparatus according to claim 1, wherein: The mini-slot is a first mini-slot, The one or more processors are further configured to: Obtain feedback data from the receiving wireless device via a physical sidelink feedback channel, the feedback data including a set of resource blocks (RBs), the set of resource blocks (RBs) including at least a first RB and a second RB, where the first RB indicates which of an acknowledgment (ACK) or a negative acknowledgment (NACK) the feedback data corresponds to; and Output a certain number of repetitions of the third data in the second mini-slot for transmission to the receiving wireless device, where the number is based on a repetition factor, and the repetition factor is based on the second RB.

11. The apparatus according to claim 1, wherein the one or more processors are further configured to: Obtain a mini-slot indication from the receiving wireless device, the mini-slot indication indicating a mini-slot index for retransmission; and Output a version of the second data having a redundancy version (RV) index based on the mini-slot indication for transmission to the receiving wireless device.

12. The apparatus according to claim 1, wherein the one or more processors are further configured to: obtain first Physical Sidelink Feedback Channel (PSFCH) data formatted in a first PSFCH format, the first PSFCH data indicating an Acknowledgment (ACK) or a Negative Acknowledgment (NACK); obtain second PSFCH data formatted in a second PSFCH format different from the first PSFCH format, the second PSFCH data bits indicating a repetition factor; and output a repetition of the second data in the mini-slot according to the repetition factor for transmission to the receiving wireless device.

13. The apparatus according to claim 1, the apparatus further comprising a transceiver configured to transmit the second data in the one or more mini-slots reserved for sidelink transmission, wherein the apparatus is configured as a scheduled entity, a User Equipment (UE), or a Programmable Logic Controller (PLC).

14. An apparatus for wireless communication, the apparatus comprising: one or more processors; and a memory including instructions executable by the one or more processors, wherein the one or more processors are configured to: output an indication of a transmission type among a plurality of transmission types for providing to a second wireless device, each of the plurality of transmission types being a different mode of organizing data into mini-slots reserved for sidelink transmission; and allocate resources to be used by the second wireless device for sidelink communication.

15. The apparatus according to claim 14, wherein: the plurality of transmission types includes two or more of a first transmission type, a second transmission type, or a third transmission type, when the second data is organized into the mini-slot according to the first transmission type, the one or more mini-slots include a plurality of mini-slots of one or more time slots and are used to transmit a Transport Block (TB) containing the second data, when the second data is organized into the mini-slot according to the second transmission type, the TB containing the second data is repeated in different mini-slots of the one or more mini-slots with the same or different Redundancy Versions (RVs), and when the second data is organized into the mini-slot according to the third transmission type, a time slot includes a first set of one or more of the mini-slots and a second set of one or more of the mini-slots, the second data includes third data and fourth data, and a first TB containing the third data is in the first set of mini-slots, and a second TB containing the fourth data is in the second set of mini-slots.

16. The apparatus according to claim 14, the apparatus further comprising a transceiver configured to send the indication of the transmission type to a second device, wherein the apparatus is configured as a gNode B (gNB), a scheduled entity, or a network node.

17. An apparatus for wireless communication, the apparatus comprising: one or more processors; and A memory, the memory including instructions executable by the one or more processors, wherein the one or more processors are configured to: Output repeat request data for transmission to a second wireless device, the repeat request data indicating a number of repetitions of a transport block (TB); and Obtain, from the second wireless device, a set of repetitions of the TB in one or more micro-slots reserved for sidelink transmission, wherein the set of repetitions of the TB includes the number of repetitions of the TB.

18. The apparatus according to claim 17, wherein the one or more processors are configured to: output the repeat request data for transmission to the second wireless device via a physical sidelink feedback channel.

19. The apparatus according to claim 17, wherein the number of repetitions of the TB is the number of repetitions of the TB required for cyclic redundancy check.

20. The apparatus according to claim 17, wherein the one or more processors are configured to: output feedback data for transmission to the second wireless device via a physical sidelink feedback channel, wherein a cyclic shift of the feedback data indicates an acknowledgement (ACK) or a negative acknowledgement (NACK) for the data and the repeat request data.

21. The apparatus according to claim 17, wherein: The data is first data, and the micro-slot is a first micro-slot, The one or more processors are further configured to: output feedback data for transmission to the second wireless device via a physical sidelink feedback channel, the feedback data including a set of resource blocks (RBs), the set of resource blocks (RBs) including at least a first RB and a second RB, the first RB indicating which one of an acknowledgement (ACK) or a negative acknowledgement (NACK) the feedback data corresponds to, and the second RB including the repeat request data indicating a repetition factor, and The one or more processors are further configured to obtain the second data a certain number of times in a second micro-slot, wherein the number of times is based on the repetition factor.

22. The apparatus according to claim 17, wherein the one or more processors are further configured to: Output a micro-slot indication for transmission to the second wireless device, the micro-slot indication indicating a micro-slot index for retransmission; and Obtain, from the second wireless device, a version of the data having a redundancy version (RV) index based on the micro-slot indication.

23. The apparatus according to claim 17, the apparatus further including a transceiver configured to transmit the repeat request data to the second wireless device, wherein the apparatus is configured as a scheduled entity, a user equipment (UE), or a programmable logic controller (PLC).

Images