Multi-resource allocation mode configuration

Abstract

This invention discloses apparatus, methods, and systems for configuring multiple resource allocation modes. One method (400) includes receiving (402) information indicating multiple resource allocation mode configurations. Each resource allocation mode configuration corresponds to a logical channel among multiple logical channels. The method (400) includes determining (404) multiple data transmission scheduling modes for the multiple logical channels. Based on the resource allocation mode configurations for the logical channels among the multiple logical channels, each data transmission scheduling mode corresponds to that logical channel, and each data transmission scheduling mode includes: a first scheduling mode; a second scheduling mode different from the first scheduling mode; or a third scheduling mode including the first scheduling mode and the second scheduling mode. The method (400) includes transmitting (406) a buffer status report based on the multiple data transmission scheduling modes.

Description

[0001] This application claims priority to U.S. Patent Application Serial No. 62 / 821,266, filed March 20, 2019, by Joachim Loehr, entitled “CONCURRENT MODE 1 AND MODE 2 CONFIGURATION FOR SIDELINKVEHICULAR COMMUNICATION”, which is incorporated herein by reference in its entirety. Technical Field

[0002] The topics disclosed in this article generally relate to wireless communication, and more specifically to the configuration of multiple resource allocation modes. Background Technology

[0003] The following abbreviations are defined herein, and at least some of them are mentioned in the following descriptions: Third Generation Partnership Project (“3GPP”), Fifth Generation (“5G”), Authentication, Licensing and Accounting (“AAA”), Affirmative Response (“ACK”), Authentication and Key Protocol (“AKA”), Aggregation Level (“AL”), Access and Mobility Management Function (“AMF”), Angle of Arrival (“AoA”), Angle of Departure (“AoD”), Access Point (“AP”), Access Layer (“AS”), Authentication Server Function (“AUSF”), Authentication Token (“AUTN”), Beam Failure Detection (“BFD”), Beam Failure Recovery (“BFR”), Binary Phase Shift Keying (“BPSK”), Base Station (“BS”) ), Buffer Status Report (“BSR”), Bandwidth (“BW”), Bandwidth Component (“BWP”), Cell RNTI (“C-RNTI”), Carrier Aggregation (“CA”), Channel Occupancy Rate (“CBR”), Contention-Based Random Access (“CBRA”), Idle Channel Assessment (“CCA”), Common Control Channel (“CCCH”), Control Channel Element (“CCE”), Cyclic Delay Diversity (“CDD”), Code Division Multiple Access (“CDMA”), Control Element (“CE”), Contention-Free Random Access (“CFRA”), Closed Loop (“CL”), Coordinated Multipoint (“CoMP”), Channel Occupancy Time (“COT”), Cyclic Prefix (“CP”), Cyclic Redundancy Correction Verification Code (“CRC”), Channel State Information (“CSI”), Channel State Information-Reference Signal (“CSI-RS”), Common Search Space (“CSS”), Control Resource Set (“CORESET”), Discrete Fourier Transform Extended (“DFTS”), Downlink Control Information (“DCI”), Downlink (“DL”), Demodulation Reference Signal (“DMRS”), Data Radio Bearer (“DRB”), Discontinuous Receive (“DRX”), Dedicated Short Range Communication (“DSRC”), Downlink Pilot Time Slots (“DwPTS”), Enhanced Idle Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), and Scalable... The agreement includes the following protocols: EAP (Effective Isotropic Radiated Power), EIRP (Effective Isotropic Radiated Power), ETSI (European Telecommunications Standards Institute), Frame-Based Equipment (FBE), Frequency Division Duplex (FDD), Frequency Division Multiplexing (FDM), Frequency Division Multiple Access (FDMA), Frequency Division Orthogonal Coverage Code (FD-OCC), Frequency Range 1-6 GHz band and / or 410 MHz to 7125 MHz (FR1), Frequency Range 2-24.25 GHz to 52.6 GHz (FR2), Universal Geographic Area Description (GAD), Group Leader (GL), 5G Node B or Next Generation Node B (gNB), and Global Navigation Satellite System (GNSS).General Packet Radio Service (“GPRS”), Guard Period (“GP”), Global Positioning System (“GPS”), Global System for Mobile Communications (“GSM”), Globally Unique Temporary UE Identifier (“GUTI”), Home AMF (“hAMF”), Hybrid Automatic Repeat Request (“HARQ”), Home Location Register (“HLR”), Handover (“HO”), Home PLMN (“HPLMN”), Home Subscriber Server (“HSS”), Hash Expected Response (“HXRES”), Identity or Identifier (“ID”), Information Element (“IE”), International Mobile Equipment Identity (“IMEI”), International Mobile Subscriber Identity (“IMSI”), International Mobile Telecommunications (“IMT”), Internet of Things (“IoT”), Layer 1 (“LI”), Layer 2 (“L2”), Layer 3 (“L3”), Authorized Auxiliary Access (“LAA”), Local Area Network (“LAN”), Load-Based Device (“LB”) E”), Listen Before You Speak (“LBT”), Logical Channel (“LCH”), Logical Channel Prioritization (“LCP”), Log-Likelihood Ratio (“LLR”), Long Term Evolution (“LTE”), Multiple Access (“MA”), Media Access Control (“MAC”), Multimedia Broadcast Multicast Service (“MBMS”), Modulation-Decoding Scheme (“MCS”), Master Information Block (“MIB”), Multiple Input Multiple Output (“MIMO”), Mobility Management (“MM”), Mobility Management Entity (“MME”), Mobile Network Operator (“MNO”), Massive MTC (“mMTC”), Maximum Power Reduction (“MPR”), Machine Type Communication (“MTC”), Multi-User Shared Access (“MUSA”), Non-Access Stratum (“NAS”), Narrowband (“NB”), Negative Acknowledgment (“NACK”) or (“NAK”), Network Entity (“NE”), Network Function (“NF”), Next Generation (“NG”), NG 5G S-TMSI (“NG-5G-S-TMSI”), Non-Orthogonal Multiple Access (“NOMA”), New Radio (“NR”), NR Unlicensed (“NR-U”), Network Repository Function (“NRF”), Network Slice Instance (“NSI”), Network Slice Selection Assistance Information (“NSSAI”), Network Slice Selection Function (“NSSF”), Network Slice Selection Policy (“NSSP”), Operation, Management and Maintenance System or Operation and Maintenance Center (“OAM”), Orthogonal Frequency Division Multiplexing (“OFDM”), Open Loop (“OL”), Out-of-Coverage (“OOC”), Other System Information (“OSI”), Power Angle Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”), Power Control (“PC”), UE-to-UE Interface (“PC5”), Primary Cell (“PCell”), Policy Control Function (“PCF”), Physical Cell Identity (“PCI”), Physical Downlink Control Channel (“PDCCH”)Packet Data Convergence Protocol (“PDCP”), Packet Data Network Gateway (“PGW”), Physical Downlink Shared Channel (“PDSCH”), Map Division Multiple Access (“PDMA”), Packet Data Unit (“PDU”), Physical Hybrid ARQ Indication Channel (“PHICH”), Power Headroom (“PH”), Power Headroom Report (“PHR”), Physical Layer (“PHY”), Public Land Mobile Network (“PLMN”), Physical Random Access Channel (“PRACH”), Physical Resource Block (“PRB”), Positioning Reference Signal (“PRS”), Physical Sidelink Control Channel (“PSCCH”), Primary and Secondary Cell (“PSCell”), Physical Sidelink Feedback Control Channel (“PSFCH”), Physical Uplink Control Channel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”), Quasi-Co-location (“QCL”), Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”), Registration Area (“RA”), RA RNTI (“RA-RNTI”), Radio Access Network (“RAN”), Random (“RAND”), Radio Access Technology (“RAT”), Random Access Procedure (“RACH”), Random Access Preamble Identifier (“RAPID”), Random Access Response (“RAR”), Resource Element Group (“REG”), Radio Link Control (“RLC”), RLC Acknowledgment Mode (“RLC-AM”), RLC Unacknowledged Mode / Transparent Mode (“RLC-UM / TM”), Radio Link Failure (“RLF”), Radio Link Monitoring (“RLM”), Radio Network Temporary Identifier (“RNTI”), Reference Signal (“RS”), Residual Minimum System Information (“RMSI”), Radio Resource Control (“RRC”), Radio Resource Management (“RRM”), Resource Extended Multiple Access (“RSMA”), Received Reference Signal Power (“RSRP”), Received Signal Strength Indicator (“RSSI”), Round Trip Time (“RTT”), Receive (“RX”), Sparse Code Multiple Access (“SCMA”), SL Radio Bearer (“SLRB”), Scheduling Request (“SR”), Sounding Reference Signal (“SRS”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), Secondary Cell Group (“SCG”), Shared Channel (“SCH”), Sidelink Control Information (“SCI”), Subcarrier Spacing (“SCS”), Serving Data Unit (“SDU”), Secure Anchor Function (“SEAF”), Sidelink Feedback Content Information (“SFCI”), Serving Gateway (“SGW”), System Information Block (“SIB”), System Information Format Block Type 1 (“SIB 1”), System Information Block Type 2 (“SIB 2”), Subscriber Identity / Identification Module (“SIM”), Signal-to-Interference-plus-Noise Ratio (“SINR”), Sidelink (“SL”)Service Level Agreement (“SLA”), SL LCH (“SLLCH”), SL SCH (“SL-SCH”), Sidelink Synchronization Signal (“SLSS”), Session Management Function (“SMF”), Special Cell (“SpCell”), Single Network Slice Selection Auxiliary Information (“S-NSSAI”), Scheduling Request (“SR”), Signaling Radio Bearer (“SRB”), Shortened TMSI (“S-TMSI”), Shortened TTI (“sTTI”), Synchronization Signal (“SS”), Sidelink CSI RS (“S-CSIRS”), Side Link PRS (“S-PRS”), Side Link RSSI (“S-RSSI”), Side Link SSB (“S-SSB”), Synchronization Signal Block (“SSB”), Subscription Hidden Identifier (“SUCI”), Scheduled User Equipment (“SUE”), Supplemental Uplink (“SUL”), Subscriber Permanent Identifier (“SUPI”), Tracking Area (TA), TA Identifier (“TAI”), TA Update (“TAU”), Timed Alignment Timer (“TAT”), Transport Block (“TB”), Transport Block Size (“TB”) Time Division Duplex (“TDD”), Time Division Multiplexing (“TDM”), Time Division Orthogonal Cover Code (“TD-OCC”), Temporary Mobile Subscriber Identity (“TMSI”), Time of Flight (“ToF”), Transmit Power Control (“TPC”), Transmit Receive Point (“TRP”), Transmission Time Interval (“TTF”), Transmission (“TX”), Uplink Control Information (“UCI”), Unified Data Management Function (“UDM”), Unified Data Repository (“UDR”), User Entity / Equipment (Mobile Terminal) (“UE”), Uplink (“UL”), UL SCH (“UL-SCH”), Universal Mobile Telecommunications System (“UMTS”), User Plane (“UP”), UP Function (“UPF”), Uplink Pilot Time Slots (“UpPTS”), Ultra-Reliable and Low-Latency Communication (“URLLC”), UE Route Selection Policy (“URSP”), Vehicle-to-Vehicle (“V2V”), Vehicle-to-Everything (“V2X”), Access AMF (“vAMF”), Access NSSF (“vNSSF”), Access PLMN (“vPLMN”), Wide Area Network (“WAN”), and Global Microwave Access Interoperability (“WiMAX”).

[0004] In a specific wireless communication network, user equipment may have a resource allocation mode configuration. Summary of the Invention

[0005] Methods for configuring multiple resource allocation modes are disclosed. Apparatus and systems also perform the functions of these methods. One embodiment of the method includes receiving information indicating multiple resource allocation mode configurations, wherein each of the multiple resource allocation mode configurations corresponds to a logical channel among multiple logical channels. In some embodiments, the method includes determining multiple data transmission scheduling modes for the multiple logical channels, wherein the resource allocation mode configurations are based on the logical channels among the multiple logical channels, each of the multiple data transmission scheduling modes corresponds to that logical channel, and each data transmission scheduling mode includes: a first scheduling mode; a second scheduling mode different from the first scheduling mode; or a third scheduling mode including the first scheduling mode and the second scheduling mode. In various embodiments, the method includes transmitting buffer status reports based on the multiple data transmission scheduling modes.

[0006] An apparatus for configuring multiple resource allocation modes includes a receiver that receives information indicating multiple resource allocation mode configurations, wherein each of the multiple resource allocation mode configurations corresponds to a logical channel among multiple logical channels. In a particular embodiment, the apparatus includes a processor that determines multiple data transmission scheduling modes for the multiple logical channels, wherein the multiple data transmission scheduling modes are based on the resource allocation mode configurations of the logical channels, each of the multiple data transmission scheduling modes corresponds to that logical channel, and each data transmission scheduling mode includes: a first scheduling mode; a second scheduling mode different from the first scheduling mode; or a third scheduling mode including the first scheduling mode and the second scheduling mode. In some embodiments, the apparatus includes a transmitter that transmits buffer status reports based on the multiple data transmission scheduling modes. Attached Figure Description

[0007] A more specific description of the embodiments briefly described above will be presented with reference to the specific embodiments shown in the accompanying drawings. It should be understood that these drawings depict only some embodiments and are therefore not intended to be limiting of the scope; the embodiments will be described and explained with additional features and details using the drawings, wherein:

[0008] Figure 1 This is a schematic block diagram illustrating one embodiment of a wireless communication system for multiple resource allocation mode configuration;

[0009] Figure 2 This is a schematic block diagram illustrating one embodiment of a device that can be used for multi-resource allocation mode configuration;

[0010] Figure 3 This is a schematic block diagram illustrating one embodiment of a device that can be used for multi-resource allocation mode configuration; and

[0011] Figure 4This is a flowchart illustrating one embodiment of a method for configuring multiple resource allocation modes. Detailed Implementation

[0012] As those skilled in the art will understand, aspects of the embodiments can be embodied as a system, apparatus, method, or program product. Therefore, embodiments can take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects, all of which can generally be referred to herein as “circuit,” “module,” or “system.” Furthermore, embodiments can take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device can be tangible, non-transitory, and / or non-transferable. The storage device may not contain signals. In certain embodiments, the storage device uses only signals to access the code.

[0013] Some functional units described in this specification may be designated as modules to more specifically emphasize their implementation independence. For example, a module may be implemented as a hardware circuit containing custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. Modules may also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc.

[0014] Modules can also be implemented in code and / or software for execution by various types of processors. For example, an identified code module may include one or more physical or logical blocks of executable code, which may be organized, for example, as objects, procedures, or functions. However, the executables of an identified module do not need to be physically located together, but may include different instructions stored in different locations, which, when logically connected together, include the module and achieve the module's stated purpose.

[0015] In practice, a code module can be a single instruction or many instructions, and can even be distributed across several different code segments, different programs, and across several memory devices. Similarly, operational data can be identified and represented within the module, and can be embodied in any suitable form and organized within any suitable type of data structure. Operational data can be collected as a single dataset or can be distributed across different locations, including different computer-readable storage devices. When a module or part of a module is implemented in software, the software portion is stored on one or more computer-readable storage devices.

[0016] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof.

[0017] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires, portable computer floppy disks, hard disks, random access memory (“RAM”), read-only memory (“ROM”), erasable programmable read-only memory (“EPROM” or flash memory), portable compact optical disc read-only memory (“CD-ROM”), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain or store programs used by or in connection with an instruction execution system, apparatus, or device.

[0018] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Python, Ruby, Java, Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" programming language, and / or machine languages ​​such as assembly language. The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer via any type of network including a local area network ("LAN") or a wide area network ("WAN"), or connected to an external computer (e.g., via the Internet provided by an Internet service provider).

[0019] Throughout this specification, references to "an embodiment," "embodiment," or similar language mean that in at least one embodiment, a particular feature, structure, or characteristic described in connection with that embodiment is included. Therefore, unless expressly stated otherwise, the phrases "in one embodiment," "in an embodiment," and similar language throughout this specification may, but not all, refer to the same embodiment, but rather to "one or more, but not all, embodiments." Unless expressly stated otherwise, the terms "comprising," "including," "having," and variations thereof mean "including, but not limited to,". Unless expressly stated otherwise, listing items does not imply that any or all items are mutually exclusive. Unless expressly stated otherwise, the terms "a," "an," and "the" also refer to "one or more".

[0020] Furthermore, the features, structures, or characteristics described in the embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, online transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of the specific details or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments.

[0021] The following description of aspects of embodiments is based on schematic flowcharts and / or schematic block diagrams of methods, apparatus, systems, and program products according to embodiments. It will be understood that each block of the schematic flowcharts and / or schematic block diagrams, and combinations of blocks in the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce machinery, such that instructions executable via the processor of the computer or other programmable data processing apparatus create means for implementing the functions / actions specified in one or more blocks of the schematic flowcharts and / or schematic block diagrams.

[0022] The code may also be stored in a storage device that can instruct a computer, other programmable data processing apparatus or other device to operate in a particular manner, such that the instructions stored in the storage device produce a manufactured article including instructions that implement the function / action specified in one or more blocks in a schematic flowchart and / or schematic block diagram.

[0023] The code may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for implementing the function / action specified in one or more blocks of a flowchart and / or block diagram.

[0024] The schematic flowcharts and / or schematic block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flowcharts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions for implementing a specified logical function.

[0025] It should also be noted that in some alternative implementations, the functions indicated in the blocks may not occur in the order shown in the figures. For example, depending on the functionality involved, two consecutively shown blocks may actually be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order. Other steps and methods that are functionally, logically, or effectively equivalent to one or more blocks or portions thereof shown in the figures can be envisioned.

[0026] While various arrow and line types may be used in flowcharts and / or block diagrams, it should be understood that they do not limit the scope of the corresponding embodiments. In practice, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For example, arrows may indicate wait or monitoring periods of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs the specified function or action.

[0027] The description of elements in each figure may refer to elements in the figure being drawn. In all figures, the same numbers refer to the same elements, including alternative embodiments of the same elements.

[0028] Figure 1 An embodiment of a wireless communication system 100 for multi-resource allocation mode configuration is depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Even in Figure 1 The description depicts a specific number of remote units 102 and network units 104, and those skilled in the art will recognize that any number of remote units 102 and network units 104 can be included in the wireless communication system 100.

[0029] In one embodiment, remote unit 102 may include computing devices such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smartphones, smart TVs (e.g., TVs connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), in-vehicle computers, network devices (e.g., routers, switches, modems), aircraft, drones, etc. In some embodiments, remote unit 102 includes wearable devices such as smartwatches, fitness trackers, optical head-mounted displays, etc. Furthermore, remote unit 102 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, fixed terminal, subscriber station, UE, user terminal, device, or other terms used in the art. Remote unit 102 may communicate directly with one or more of network units 104 via UL communication signals. In certain embodiments, remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0030] Network unit 104 may be distributed across a geographical area. In certain embodiments, network unit 104 may also be referred to as an access point, access terminal, infrastructure, base station, Node B, eNB, gNB, home Node B, relay node, device, core network, air server, radio access node, AP, NR, network entity, AMF, UDM, UDR, UDM / UDR, PCF, RAN, NSSF, or any other term used in the art. Network unit 104 is typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network units 104. The radio access network is typically communicatively coupled to one or more core networks, which may be coupled to other networks such as the Internet and the public switched telephone network, as well as other networks. These and other elements of the radio access and core networks are not described, but they are generally well known to those skilled in the art.

[0031] In one implementation, the wireless communication system 100 conforms to the NR protocol standardized in 3GPP, wherein network unit 104 transmits using an OFDM modulation scheme on DL, and remote unit 102 transmits using an SC-FDMA scheme or an OFDM scheme on UL. However, more generally, the wireless communication system 100 can implement other open or proprietary communication protocols, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, etc. ZigBee, Sigfoxx, and other protocols. This disclosure is not intended to limit it to any particular wireless communication system architecture or protocol implementation.

[0032] Network unit 104 can serve a number of remote units 102 within a service area, such as a cell or cell sector, via a wireless communication link. Network unit 104 transmits DL communication signals to serve remote units 102 in the time domain, frequency domain, and / or spatial domain.

[0033] In various embodiments, remote unit 102 may receive information indicating multiple resource allocation mode configurations, wherein each of the multiple resource allocation mode configurations corresponds to a logical channel among multiple logical channels. In some embodiments, remote unit 102 may determine multiple data transmission scheduling modes for the multiple logical channels, wherein based on the resource allocation mode configuration of the logical channel among the multiple logical channels, each of the multiple data transmission scheduling modes corresponds to that logical channel, and each data transmission scheduling mode includes: a first scheduling mode; a second scheduling mode different from the first scheduling mode; or a third scheduling mode including the first scheduling mode and the second scheduling mode. In various embodiments, remote unit 102 may transmit buffer status reports based on the multiple data transmission scheduling modes. Therefore, remote unit 102 can be used for multiple resource allocation mode configurations.

[0034] Figure 2 One embodiment of an apparatus 200 that can be used for a multi-resource allocation mode configuration is depicted. The apparatus 200 includes one embodiment of a remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, memory 204, transmitter 210, and receiver 212, and may not include the input device 206 and / or display 208.

[0035] In one embodiment, processor 202 may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, processor 202 may be a microcontroller, microprocessor, central processing unit (“CPU”), graphics processing unit (“GPU”), auxiliary processing unit, field-programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, processor 202 executes instructions stored in memory 204 to perform the methods and routines described herein. In various embodiments, processor 202 may determine multiple data transmission scheduling modes for multiple logical channels, wherein each of the multiple data transmission scheduling modes corresponds to that logical channel based on a resource allocation pattern configuration of the logical channels, and each data transmission scheduling mode includes: a first scheduling mode; a second scheduling mode different from the first scheduling mode; or a third scheduling mode including the first and second scheduling modes. Processor 202 is communicatively coupled to memory 204, input device 206, display 208, transmitter 210, and receiver 212.

[0036] In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, memory 204 may include RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and / or static RAM (“SRAM”). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and associated data, such as an operating system or other controller algorithms operating on remote unit 102.

[0037] In one embodiment, input device 206 may include any known computer input device, including a touch panel, buttons, keyboard, stylus, microphone, etc. In some embodiments, input device 206 may be integrated with display 208 as, for example, a touchscreen or similar touch-sensitive display. In some embodiments, input device 206 includes a touchscreen, enabling text input using a virtual keyboard displayed on the touchscreen and / or by handwriting on the touchscreen. In some embodiments, input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0038] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may include, but is not limited to, LCD displays, LED displays, OLED displays, projectors, or similar display devices capable of outputting images, text, etc., to a user. As another non-limiting example, display 208 may include wearable displays, such as smartwatches, smart glasses, head-up displays, etc. Furthermore, display 208 may be a component of a smartphone, personal digital assistant, television, desktop computer, laptop computer, personal computer, vehicle dashboard, etc.

[0039] In certain embodiments, display 208 includes one or more speakers for generating sound. For example, display 208 may generate an auditory alarm or notification (e.g., a buzzer or beep). In some embodiments, display 208 includes one or more haptic devices for generating vibration, motion, or other haptic feedback. In some embodiments, all or part of display 208 may be integrated with input device 206. For example, input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, display 208 may be located near input device 206.

[0040] Transmitter 210 is used to provide UL communication signals to network unit 104, and receiver 212 is used to receive DL communication signals from network unit 104, as described herein.

[0041] In some embodiments, receiver 212 may receive information indicating multiple resource allocation mode configurations, each of which corresponds to a logical channel among multiple logical channels. In various embodiments, transmitter 210 transmits buffer status reports based on multiple data transmission scheduling modes. Although only one transmitter 210 and one receiver 212 are shown, remote unit 102 may have any suitable number of transmitters 210 and receivers 212. Transmitters 210 and receivers 212 may be of any suitable type. In one embodiment, transmitters 210 and receivers 212 may be part of a transceiver.

[0042] Figure 3An embodiment of a device 300 that can be used in a multi-resource allocation mode configuration is depicted. Device 300 includes one embodiment of a network unit 104. Furthermore, network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. It will be understood that the processor 302, memory 304, input device 306, display 308, transmitter 310, and receiver 312 may substantially resemble the processor 202, memory 204, input device 206, display 208, transmitter 210, and receiver 212 of remote unit 102, respectively.

[0043] In various embodiments, transmitter 310 may transmit information to remote unit 102, and / or receiver 312 may receive information from remote unit 102.

[0044] Although only one transmitter 310 and one receiver 312 are shown, network unit 104 can have any suitable number of transmitters 310 and receivers 312. The transmitters 310 and receivers 312 can be of any suitable type. In one embodiment, the transmitters 310 and receivers 312 can be part of a transceiver.

[0045] In some embodiments, two resource allocation modes may be used. For example, LTE V2X communication and / or NR V2X communication may use two resource allocation modes. These two resource allocation modes may be referred to as Mode 3 and Mode 4 for LTE V2X. Mode 3 and Mode 4 can support direct V2X communication, but may differ in how radio resources are allocated. For example, for Mode 3, resources may be allocated by the cellular network (e.g., eNB). In contrast, Mode 4 may not require cellular coverage, and vehicles may autonomously select their radio resources using a distributed scheduling scheme supported by congestion control mechanisms. Mode 4 can be considered a baseline mode and may represent an alternative to 802.11p or DSRC.

[0046] In various embodiments, resource allocation modes 3 and 4 are designed to meet latency requirements, accommodate high Doppler spread, and / or accommodate high-density vehicles for V2X communication. In specific embodiments, depending on the application, the maximum permissible latency can vary between 20 ms and 100 ms. In some embodiments, mode 3 may use a centralized eNB scheduler. In various embodiments, vehicle UEs and eNBs communicate using the Uu interface (e.g., sending BSRs and / or SRs from the UE transmitting V2X to the eNB and receiving SL licenses as a response on the PDCCH (e.g., DCI)). In specific embodiments, mode 4 uses the PC5 interface, which supplies direct LTE SL communication between two vehicle UEs and / or employs distributed UE scheduling. In some embodiments, V2X mode 4 operates without infrastructure support (although the UE may be within eNB coverage). In various embodiments, V2X resources are shared with the LTE uplink. In specific embodiments, V2X mode 4 may support LTE duplex modes (e.g., time-division duplex and frequency-division duplex). In some embodiments, mode 4 may use specific resource pool configurations and SPS to select and reserve resources for transmission.

[0047] In some embodiments, SPS can support services with deterministic latency, such as voice services. In a particular embodiment, Mode 4 can also support services with deterministic latency, and sensing can be used to determine suitable SPS transmission opportunities (e.g., a set of subframes and subchannels for transmission). In some embodiments, depending on the message size, candidate single subframe resources include one or more (e.g., L) consecutive subchannels within a single subframe. In various embodiments, the UE can select a set of candidate resources within a selection window that spans multiple subframes and contains M single subframe resources. In a particular embodiment, the UE can continuously monitor subframes and record decoded SCI and S-RSSI measurements. In some embodiments, the UE can consider the last 1000 subframes for selecting candidate resources according to defined rules.

[0048] In certain embodiments, NR V2X can use LTE V2X operation as a baseline. In various embodiments, centralized and distributed scheduling modes can exist in NRV2X communication (e.g., referred to as Mode 3 and Mode 4 in LTE V2X). The two resource allocation modes in NRV2X can be referred to as Resource Allocation Mode 1 and Mode 2. Unlike LTE V2X communication, an NRV2X UE can be configured with both Resource Allocation Mode 1 and Mode 2 simultaneously. In LTE V2X, a V2X UE can use either Mode 3 or Mode 4, but never both modes simultaneously.

[0049] In some embodiments, if a UE transmitting V2X is configured with two resource allocation modes simultaneously (e.g., the serving cell supports two resource selection modes), rules can be defined for how the UE transmitting V2X uses these two resource allocation modes for SL communication (e.g., when to use mode 1 and when to use mode 2). Without such rules, a UE transmitting V2X can request SL resources by indicating a specific buffer state to the gNB, and the UE can use mode 2 to transmit SL data before receiving an SL grant from the gNB. This can lead to a waste of allocated resources (e.g., the SL grant may allocate SL resources that cannot be fully utilized by the UE because there is not enough remaining data in the buffer for transmission).

[0050] This article describes various methods for efficient SL data transmission for configured resources, where the V2X UE is configured with two resource allocation modes simultaneously.

[0051] As used herein, the terms eNB and / or gNB can be used for base stations, but can be replaced by any other radio access node (e.g., BS, eNB, gNB, AP, NR, etc.). Furthermore, while the various embodiments described herein can be described in the context of 5G NR, these embodiments are equally applicable to other mobile communication systems supporting serving cells and / or carriers, such as systems configured for SL communication via the PC5 interface.

[0052] In a first embodiment, the UE transmitting V2X executes two sidelink transmission procedures in parallel. These two sidelink transmission procedures include one for a gNB-scheduled resource selection mode (e.g., mode 1, where the MAC entity is configured to dynamically receive sidelink grants on the PDCCH) and one for a UE-autonomous resource selection mode (e.g., mode 2, where the MAC entity is configured for autonomous resource selection). In some embodiments, executing two sidelink transmission procedures simultaneously may mean that the UE transmitting V2X treats certain SLRBs as mode 1 and certain SLRBs as mode 2. For example, an SLRB or corresponding SL LCH for an SL-SCH data transmission procedure may be considered to use resource allocation mode 1 (e.g., SR and / or BSR procedures, SL grant reception, LCP procedures), while other SLRBs or corresponding SL LCHs for an SL-SCH data transmission procedure may be considered to use resource allocation mode 2. In various embodiments, SLRBs and / or SL LCHs may be configured with supported resource allocation modes. In such embodiments, there may be indications regarding whether the data of the corresponding SL LCH and / or SLRB can be transmitted on the SL-SCH using an SL license allocated by a network entity such as a gNB (e.g., mode 1), an SL license selected by the UE (e.g., mode 2), or both.

[0053] In some embodiments, the UE transmitting V2X considers (e.g., for a sidelink license received from the gNB on the PDCCH) to be configured to use only SL LCHs and / or SLRBs for the TB generation process (e.g., during the LCP process) under resource allocation mode 1 (e.g., a sidelink license allocated by the gNB). In such embodiments, the UE transmitting V2X can perform the LCP / TB generation process by first selecting those LCHs from the set of SL LCHs (e.g., the configured set of SL LCHs) that satisfy resource allocation mode conditions (e.g., the configured allowedResourceAllocationMode includes mode 1). Furthermore, in such embodiments, each MAC PDU and / or TB transmitted on the SL-SCH on the SL resource is associated with a resource allocation mode.

[0054] In one embodiment, the first embodiment can be implemented based on the logical channel priorities shown in Table 1.

[0055]

[0056] In one configuration of the first embodiment, if the serving cell supports two resource allocation modes, or if the UE is configured to use both Mode 1 and Mode 2 resource allocation modes simultaneously, the LCH configuration (e.g., indicating whether data for the corresponding SL LCH and / or SLRB can be transmitted using an SL license allocated by the gNB (Mode 1)), the SL license chosen by the UE (Mode 2), or both can be considered only by the UE transmitting V2X. If only one resource allocation mode is available in the serving cell, or if the UE is in OOC, the UE can ignore the LCH configuration (e.g., IEallowedResourceAllocationMode - data for all SL LCHs can be transmitted under the available resource allocation mode).

[0057] In certain embodiments, a V2X UE can be configured with a ratio of how much of its SL data (e.g., the SL data available for transmission) can be transmitted using resource allocation mode 1 relative to resource allocation mode 2. This ratio can be determined and configured by the gNB. This ratio can be used to control and / or guide load and / or congestion in the resource pool for the corresponding resource allocation mode. In various embodiments, the UE can be configured with a priority threshold to determine which resource allocation mode will be used for the SLLCH. For example, all SL LCHs with a logical channel priority higher than the configured priority threshold can use one resource allocation mode (e.g., mode 1), while SL LCHs with a logical channel priority lower than or equal to the configured priority threshold can use another resource allocation mode (e.g., mode 2). The configured priority threshold can be broadcast in the serving cell or configured individually for the UE.

[0058] In some embodiments, a V2X UE may be configured with a CBR threshold. The CBR threshold can be used to determine whether to use resource allocation mode 2 or resource allocation mode 1 for SL communication. In various embodiments, a V2X UE configured for both mode 1 and mode 2 can perform CBR measurements in the resource pool configured for mode 2. If the CBR value is less than or equal to the configured CBR threshold, in one example, the UE can use resource allocation mode 2 for SL communication; and if the CBR value is greater than the threshold, in one example, the UE can use resource allocation mode 1 for SL communication. The CBR threshold can be broadcast in the serving cell or configured individually for the UE.

[0059] In a second embodiment, the UE transmitting V2X may only consider sidelink logical channels configured to use resource allocation mode 1 for buffer status reporting and / or scheduling request procedures (e.g., sidelink grants are signaled and / or provided by a NE such as a gNB). In such embodiments, each SLRB and / or corresponding SL LCH may be configured with a supported resource allocation mode (e.g., IE-allowed resource allocation mode). This configuration may indicate whether data on the corresponding SL LCH and / or SLRB can be transmitted on the SL-SCH using SL grants allocated by a network entity such as a gNB (e.g., mode 1), UE-selected autonomously (e.g., mode 2), or both. In a particular configuration of the second embodiment, the sidelink LCH may be configured to use only resource allocation mode 2 (e.g., SL grants are autonomously selected by the TX UE) and is not considered for MAC buffer status reporting. In such embodiments, SL LCHs configured to use only autonomously allocated resources may not trigger buffer status reporting (e.g., the arrival of sidelink data configured to use only autonomously allocated sidelink logical channels may not trigger BSR and / or SR). In various embodiments, the sidelink buffer status report does not reflect the amount of sidelink data for logical channels configured to use only the discretionary resource allocation mode. In such embodiments, the sidelink BSR only indicates the amount of data for sidelink logical channels configured to use resource allocation mode 1 (e.g., sidelink licenses provided by the network). In other words, the amount of data for sidelink LCHs configured for discretionary resource allocation mode is set to zero.

[0060] In one configuration of the second embodiment, the buffer status report reports the sidelink LCH configured for autonomous resource allocation mode. However, in such a configuration, the buffer status of the SLLCH configured for scheduling resource allocation mode (e.g., mode 1) may be reported separately from the buffer status of the SL LCH configured for autonomous resource allocation mode (e.g., mode 2).

[0061] In some embodiments, a UE transmitting V2X performs two sidelink transmission procedures in parallel. In such embodiments, one transmission procedure is for a gNB-scheduled resource selection mode (e.g., mode 1, where the MAC entity is configured to dynamically receive sidelink grants on the PDCCH), and the other transmission procedure is for a UE-autonomous resource selection mode (e.g., mode 2, where the MAC entity is configured for autonomous resource selection). In such embodiments, one or more serving cells support both resource selection modes (e.g., mode 1 and mode 2) for V2X sidelink communication. Performing two sidelink transmission procedures simultaneously may mean that if SL data is available for transmission and the UE does not have a valid SL grant, the UE transmitting V2X first sends a BSR and / or SR (e.g., indicating the amount of SL data available for transmission across all SL LCHs and / or SLRBs) to the gNB requesting the SL resource, and then monitors the PDCCH for SL grants. Upon receiving an SL grant, the UE performs the SL transmission on the assigned resource. If, after the SL-SCH transmission, there is still SL data pending in the UE's buffer, the UE can transmit the remaining data on the UE-autonomous SL resource (e.g., based on sensing). It should be noted that after the UE has sent a BSR to the gNB and before receiving the corresponding SL clearance, the UE cannot perform any SL transmissions on resources of its own choosing (e.g., mode 2). It is understood that the motivation for this behavior may be to avoid a situation where the UE's buffer contains less SL data than indicated in the BSR when receiving the SL clearance on the PDCCH, because the UE has autonomously sent some SL data (e.g., mode 2) after the BSR transmission and before receiving the corresponding SL clearance.

[0062] In various embodiments, a UE transmitting V2X may first send SL data on an SL resource of its own choice (e.g., based on sensing the presence of SL data available for transmission and the UE not having a valid SL grant). If, after a transmission in resource allocation mode 2, there is still remaining SL data in the UE's buffer, the UE may send a BSR and / or SR indicating the remaining SL data to the gNB and subsequently monitor for SL grants on the PDCCH. In such embodiments, the UE may not be able to perform any SL transmission on a UE-chosen resource (e.g., mode 2) after sending a BSR to the gNB and before receiving the corresponding SL grant. It is understood that the motivation for this behavior may be to avoid a situation where the UE's buffer has less SL data than indicated in the BSR when receiving an SL grant on the PDCCH, because the UE has autonomously sent some SL data (e.g., mode 2) after the BSR transmission and before receiving the corresponding SL grant.

[0063] In a third embodiment, the UE transmitting V2X excludes subframes and / or slots from a potential transmission subframe and / or slot list (e.g., based on sensing or partial sensing) for transmission in an autonomous resource allocation mode where the UE has received an SL license from the NE (e.g., by means of PDCCH). In such embodiments, if the UE has already been allocated SL resources via SL license (e.g., an SL license allocated by the NE - Mode 1 - may take precedence over an SL license selected by the UE - Mode 2), the UE may not select an SL resource in the slot. In such embodiments, for both the scheduled resource allocation mode and the autonomous resource allocation mode, the UE has data available for transmission (e.g., the UE has more data available for transmission than is allowed to be transmitted according to the SL license issued by the NE).

[0064] In some embodiments, for a UE transmitting V2X (e.g., the UE's MAC entity) configured to dynamically receive sidelink grants on the PDCCH (e.g., scheduled resource allocation mode - mode 1) and simultaneously configured with an autonomous resource allocation mode, the UE performs operations related to both resource allocation modes in parallel. In such embodiments, the UE is only enabled and / or able to perform (e.g., within a serving cell in a time slot) one SL transmission on the SL-SCH (e.g., SL-SCH transmission according to the scheduled resource allocation mode or transmission on the SL-SCH according to the autonomous resource allocation mode). Furthermore, in such embodiments, UE behavior can be defined if the UE has both a PDCCH-allocated SL grant and an autonomously selected SL grant (e.g., sense-based) for the same time slot (e.g., partially or fully overlapping). In a particular embodiment, the UE prioritizes the PDCCH-received SL grant over the autonomously selected SL grant (e.g., sense-based or partially sense-based). If the UE has two SL grants for the same time slot (e.g., one received by the PDCCH and one autonomously selected, such as sense-based), the UE performs the SL transmission according to the PDCCH-received SL grant.

[0065] In various embodiments, the UE selects an SL license for SL transmission based on the priority of the LCH contained in the corresponding TB. If the priority of the highest priority LCH contained in the TB according to the SL license received by the PDCCH is higher than the priority of the highest priority LCH contained in the TB according to the SL license selected by the UE, the UE can select the SL license received by the PDCCH and transmit accordingly. If the priority of the highest priority LCH contained in the TB according to the SL license received by the PDCCH is lower than the priority of the highest priority LCH contained in the TB according to the SL license selected by the UE, the UE can select the self-selected SL license and transmit accordingly (in such cases, the SL license received by the PDCCH can be ignored).

[0066] In a particular embodiment, if the priority of the LCH configured for autonomous resource allocation mode is higher than the priority of the LCH configured for scheduled resource allocation mode, the UE can use the SL resources scheduled by the gNB and can transmit data from the LCH configured for autonomous transmission. In such embodiments, based on the first embodiment, each LCH can be configured for an enabled resource allocation mode.

[0067] In the fourth embodiment, the gNB can configure different power control parameters (e.g., P0 and / or α values) for SL-licensed SL transmissions received by the PDCCH and SL-licensed SL transmissions selected by the UE (e.g., based on sensing). In a specific embodiment, the UE can have two independent power control loops for the two resource allocation modes (e.g., TPC commands maintained separately for the two resource allocation modes). In such embodiments, one motivation for having different power control parameters and two independent power control loops may be that the two resource allocation modes need to meet different QoS requirements. If the UE transmits according to one of the two resource allocation modes, the UE can apply the corresponding power control loop and / or parameters to determine the transmission power used by the PSSCH.

[0068] In some embodiments, if the UE is power-constrained (e.g., the determined TX for SL transmissions on the PSSCH exceeds the total maximum allowed UE TX power for SL), the UE can reduce the TX power of certain PSSCHs (e.g., referred to as power scaling) to take into account the resource allocation pattern of the corresponding PSSCH transmissions. Such power constraints may occur if the UE is configured with multiple uplink carriers in a carrier aggregation scenario, or if the UE is configured for simultaneous uplink transmissions for LTE and NR in a dual-connectivity scenario. In certain embodiments, if power scaling is applied, the UE can prioritize PSSCH transmissions scheduled by the gNB over PSSCH transmissions on resources autonomously selected by the UE. In various embodiments, the relative priority order among SL transmissions on the PSSCH can be used in power-constrained situations (e.g., power scaling). In some embodiments, PSSCH transmissions scheduled by the gNB can take precedence over PSSCH transmissions autonomously allocated by the transmitting UE. In certain embodiments, the UE can reduce the transmission power of UE-autonomous PSSCH transmissions before reducing the transmission power of PSSCH transmissions scheduled by the gNB.

[0069] In the fifth embodiment, the UE transmitting V2X can switch resource allocation modes between different HARQ transmissions (or retransmissions) of a TB. In such embodiments, the initial HARQ transmission of a TB can be completed on SL resources chosen autonomously by the UE (e.g., mode 2), and subsequent HARQ transmissions (or retransmissions) of that TB can be explicitly scheduled by the gNB (e.g., by means of SL grants sent via PDCCH). In some embodiments, because the SL grant for the initial HARQ transmission is chosen by the UE, the gNB may not know the transmission parameters (e.g., TB size, HARQ process ID, etc.) chosen by the UE for the initial TX. Therefore, in order to schedule HARQ retransmissions, the UE provides the gNB with the selected transmission parameters if SL resources for HARQ retransmissions are requested. In various embodiments, the UE signals to the gNB at least one of the following parameters to request S1 resources for HARQ retransmission: 1) the TB size of the initial HARQ transmission; 2) the HARQ process ID for the initial HARQ transmission of the TB (e.g., assuming the UE autonomously selects the HARQ process ID for the SL transmission according to the autonomous resource allocation mode); 3) the ID of the highest priority LCH contained in the TB; and / or 4) the priority of the highest priority LCH contained in the TB.

[0070] In certain embodiments, upon receiving a scheduling request and transmission parameters for HARQ retransmission, the gNB sends an SL grant on the PDCCH to the requesting UE to allocate SL resources for HARQ retransmission (e.g., the TB size should match the size indicated in the retransmission request message from the UE). In various embodiments, the DCI includes an indicator identifying that the SL grant is allocating resources for retransmission. In such embodiments, the DCI may indicate the HARQ process ID signaled from the UE to the gNB in ​​the retransmission request message.

[0071] In some embodiments, the initial HARQ transmission of a TB is completed on an SL resource scheduled by the gNB (e.g., mode 1), and subsequent HARQ transmissions (e.g., retransmissions) of the TB are sent on an SL resource selected by the UE (e.g., sense-based). In a particular embodiment, if the UE transmitting V2X is configured with a feedback resource (e.g., on the PUCCH) to provide the gNB with information about whether an SL resource is needed for a HARQ retransmission of the TB, the UE can avoid indicating the need for a retransmission SL grant if HARQ retransmissions are performed in an autonomous resource allocation mode. Such information can be explicit (e.g., similar to a HARQ ACK) or implicit by the absence of a retransmission request. In various embodiments, the absence of a configuration feedback resource for SL grants received on the PDCCH (e.g., indicating whether an SL resource is necessary for the TB retransmission) implicitly instructs the UE transmitting V2X to perform any potential HARQ retransmissions of the TB initially transmitted by the gNB (e.g., SL grants on the PDCCH) on an SL resource selected by the UE (e.g., sense-based).

[0072] In various embodiments, the SL grant sent by the gNB on the PDCCH can explicitly indicate whether a potential HARQ retransmission can be performed in discretionary resource allocation mode. Such an indication can be accomplished using a single-bit flag within the DCI.

[0073] Figure 4 This is a flowchart illustrating one embodiment of a method 400 for configuring a multi-resource allocation mode. In some embodiments, method 400 is executed by a device such as remote unit 102. In a particular embodiment, method 400 can be executed by a processor that executes program code, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0074] Method 400 may include receiving 402 information indicating a plurality of resource allocation mode configurations, wherein each of the plurality of resource allocation mode configurations corresponds to a logical channel among a plurality of logical channels. In some embodiments, method 400 includes determining 404 a plurality of data transmission scheduling modes for the plurality of logical channels, wherein based on the resource allocation mode configurations of the logical channels among the plurality of logical channels, each of the plurality of data transmission scheduling modes corresponds to that logical channel, and each data transmission scheduling mode includes: a first scheduling mode; a second scheduling mode different from the first scheduling mode; or a third scheduling mode including the first scheduling mode and the second scheduling mode. In various embodiments, method 400 includes transmitting 406 a buffer status report based on the plurality of data transmission scheduling modes.

[0075] In a particular embodiment, if the data transmission scheduling mode of a logical channel among a plurality of logical channels includes a first scheduling mode, then transmitting a buffer status report based on the plurality of data transmission scheduling modes includes only data for that logical channel. In some embodiments, transmitting a buffer status report based on the plurality of data transmission scheduling modes includes including data for all logical channels among the plurality of logical channels. In various embodiments, method 400 further includes triggering the transmission of a buffer status report in response to a logical channel among a plurality of logical channels having a data transmission scheduling mode including the first scheduling mode.

[0076] In one embodiment, a sidelink license received by a control channel has a higher priority than an autonomously generated sidelink license. In a particular embodiment, method 400 further includes receiving a sidelink license from a base station element, wherein, in response to receiving a sidelink license from a base station element, if the data transmission scheduling mode of a logical channel among a plurality of logical channels includes a first scheduling mode, then only data for that logical channel is included. In some embodiments, method 400 further includes selecting a sidelink license, wherein, in response to selecting a sidelink license, if the data transmission scheduling mode of a logical channel among a plurality of logical channels includes a second scheduling mode, then only data for that logical channel is included.

[0077] In various embodiments, in response to autonomous data corresponding to autonomous transmission having a higher priority than scheduling data corresponding to sidelink resources, sidelink resources scheduled by the base station unit are preempted by autonomous transmission. In one embodiment, a first scheduling mode includes a first power control loop, and a second scheduling mode includes a second power control loop, wherein the first power control loop is independent of the second power control loop. In a particular embodiment, the first scheduling mode includes a first power control loop, and the second scheduling mode includes a second power control loop, wherein the first power control loop and the second power control loop are related to each other.

[0078] In some embodiments, method 400 further includes transmitting initial feedback using a first scheduling mode and retransmitting the feedback using a second scheduling mode. In various embodiments, method 400 further includes transmitting initial feedback using a second scheduling mode and retransmitting the feedback using a first scheduling mode.

[0079] In one embodiment, a method includes: receiving information indicating a plurality of resource allocation mode configurations, wherein each of the plurality of resource allocation mode configurations corresponds to a logical channel among a plurality of logical channels; determining a plurality of data transmission scheduling modes for the plurality of logical channels, wherein the resource allocation mode configurations of the logical channels are based on the resource allocation mode configurations of the logical channels, each of the plurality of data transmission scheduling modes corresponds to the logical channel, and each data transmission scheduling mode includes: a first scheduling mode; a second scheduling mode different from the first scheduling mode; or a third scheduling mode including the first scheduling mode and the second scheduling mode; and transmitting a buffer status report based on the plurality of data transmission scheduling modes.

[0080] In a particular embodiment, if the data transmission scheduling mode of a logical channel among multiple logical channels includes a first scheduling mode, then the transmission buffer status report based on the multiple data transmission scheduling modes includes only the data for that logical channel.

[0081] In some embodiments, the transmission buffer status report based on multiple data transmission scheduling modes includes data for all logical channels.

[0082] In various embodiments, the method further includes: triggering the transmission of a buffer status report in response to a logical channel among a plurality of logical channels having a data transmission scheduling mode including a first scheduling mode.

[0083] In one embodiment, a sidelink license received by the control channel has a higher priority than an autonomously generated sidelink license.

[0084] In a particular embodiment, the method further includes receiving a sidelink permission from a base station unit, wherein, in response to receiving the sidelink permission from the base station unit, if the data transmission scheduling mode of a logical channel among a plurality of logical channels includes a first scheduling mode, then data only for that logical channel is included.

[0085] In some embodiments, the method further includes selecting a sidelink license, wherein, in response to selecting a sidelink license, if the data transmission scheduling mode of a logical channel among a plurality of logical channels includes a second scheduling mode, then only data for that logical channel is included.

[0086] In various embodiments, in response to autonomous data corresponding to autonomous transmission having a higher priority than scheduling data corresponding to sidelink resources, sidelink resources scheduled by the base station unit are preempted by autonomous transmission.

[0087] In one embodiment, a first scheduling mode includes a first power control loop, and a second scheduling mode includes a second power control loop, wherein the first power control loop is independent of the second power control loop.

[0088] In a particular embodiment, a first scheduling mode includes a first power control loop, and a second scheduling mode includes a second power control loop, wherein the first power control loop and the second power control loop are related to each other.

[0089] In some embodiments, the method further includes transmitting initial feedback using a first scheduling mode and retransmitting feedback using a second scheduling mode.

[0090] In various embodiments, the method further includes transmitting initial feedback using a second scheduling mode and retransmitting feedback using a first scheduling mode.

[0091] In one embodiment, an apparatus includes: a receiver receiving information indicating a plurality of resource allocation mode configurations, wherein each of the plurality of resource allocation mode configurations corresponds to a logical channel among a plurality of logical channels; a processor determining a plurality of data transmission scheduling modes for the plurality of logical channels, wherein the resource allocation mode configurations are based on the logical channels among the plurality of logical channels, each of the plurality of data transmission scheduling modes corresponds to the logical channel, and each data transmission scheduling mode includes: a first scheduling mode; a second scheduling mode different from the first scheduling mode; or a third scheduling mode including the first scheduling mode and the second scheduling mode; and a transmitter transmitting a buffer status report based on the plurality of data transmission scheduling modes.

[0092] In a particular embodiment, if the data transmission scheduling mode of a logical channel among multiple logical channels includes a first scheduling mode, then the transmitter transmits a buffer status report based on the multiple data transmission scheduling modes, which includes only the data for that logical channel.

[0093] In some embodiments, the transmitter transmits buffer status reports based on multiple data transmission scheduling modes, including data for all logical channels across multiple logical channels.

[0094] In various embodiments, the processor triggers the transmission of a buffer status report in response to a logical channel among a plurality of logical channels having a data transmission scheduling mode that includes a first scheduling mode.

[0095] In one embodiment, a sidelink license received by the control channel has a higher priority than an autonomously generated sidelink license.

[0096] In a particular embodiment, the receiver receives a sidelink license from the base station unit, and in response to receiving the sidelink license from the base station unit, if the data transmission scheduling mode of a logical channel among a plurality of logical channels includes a first scheduling mode, then data only for that logical channel is included.

[0097] In some embodiments, the processor selects a sidelink license, and in response to selecting a sidelink license, if the data transmission scheduling mode of a logical channel among a plurality of logical channels includes a second scheduling mode, then only data for that logical channel is included.

[0098] In various embodiments, in response to autonomous data corresponding to autonomous transmission having a higher priority than scheduling data corresponding to sidelink resources, sidelink resources scheduled by the base station unit are preempted by autonomous transmission.

[0099] In one embodiment, a first scheduling mode includes a first power control loop, and a second scheduling mode includes a second power control loop, wherein the first power control loop is independent of the second power control loop.

[0100] In a particular embodiment, a first scheduling mode includes a first power control loop, and a second scheduling mode includes a second power control loop, wherein the first power control loop and the second power control loop are related to each other.

[0101] In some embodiments, the transmitter uses a first scheduling mode to transmit initial feedback and uses a second scheduling mode to retransmit feedback.

[0102] In various embodiments, the transmitter uses a second scheduling mode to transmit initial feedback and uses a first scheduling mode to retransmit feedback.

[0103] The embodiments may be practiced in other specific forms. The described embodiments are to be considered illustrative rather than restrictive in all respects. Therefore, the scope of the invention is indicated by the appended claims rather than by the foregoing description. All variations within the meaning and scope of the equivalence of the claims are to be included within their scope.

Claims

1. A method comprising: Receive information indicating multiple resource allocation mode configurations, wherein each of the multiple resource allocation mode configurations corresponds to a logical channel among multiple logical channels; Multiple data transmission scheduling modes are determined for the plurality of logical channels, wherein a resource allocation mode configuration is based on the logical channels among the plurality of logical channels, each of the plurality of data transmission scheduling modes corresponds to the logical channel, and each data transmission scheduling mode includes: First scheduling mode; A second scheduling mode that is different from the first scheduling mode; or A third scheduling mode that includes the first scheduling mode and the second scheduling mode; as well as The buffer status report is transmitted based on the aforementioned multiple data transmission scheduling modes. A sidelink license is received from a base station unit, wherein, in response to receiving the sidelink license from the base station unit, if each of the data transmission scheduling modes of the plurality of logical channels includes the first scheduling mode, then data for only the logical channel is included, wherein data transmission with the second scheduling mode is not performed before receiving the sidelink license.

2. The method according to claim 1, wherein, If the data transmission scheduling mode of one of the plurality of logical channels includes the first scheduling mode, then transmitting the buffer status report based on the plurality of data transmission scheduling modes includes only the data for the logical channel.

3. The method according to claim 1, wherein, The buffer status report, transmitted based on the multiple data transmission scheduling modes, includes data for all logical channels used by the multiple logical channels.

4. The method of claim 1, further comprising: triggering the transmission of the buffer status report in response to a logical channel among the plurality of logical channels having a data transmission scheduling mode including the first scheduling mode.

5. The method according to claim 1, wherein, Sidelink licenses received by the control channel have a higher priority than autonomously generated sidelink licenses.

6. The method of claim 1, further comprising selecting a sidelink license, wherein, In response to selecting the sidelink permission, if the data transmission scheduling mode of the logical channel among the plurality of logical channels includes the second scheduling mode, then data for only the logical channel is included.

7. The method according to claim 1, wherein, In response to the autonomous data corresponding to autonomous transmission having a higher priority than the scheduling data corresponding to sidelink resources, the sidelink resources scheduled by the base station unit are preempted by the autonomous transmission.

8. The method according to claim 1, wherein, The first scheduling mode includes a first power control loop, and the second scheduling mode includes a second power control loop, wherein the first power control loop is independent of the second power control loop.

9. The method according to claim 1, wherein, The first scheduling mode includes a first power control loop, and the second scheduling mode includes a second power control loop, and the first power control loop and the second power control loop are related to each other.

10. The method of claim 1, further comprising transmitting initial feedback using the first scheduling mode and retransmitting feedback using the second scheduling mode.

11. The method of claim 1, further comprising transmitting initial feedback using the second scheduling mode and retransmitting feedback using the first scheduling mode.

12. An apparatus comprising: A receiver receives information indicating multiple resource allocation mode configurations, wherein each of the multiple resource allocation mode configurations corresponds to a logical channel among multiple logical channels. A processor determines multiple data transmission scheduling modes for the plurality of logical channels, wherein the configuration is based on a resource allocation mode of the logical channels among the plurality of logical channels, each of the plurality of data transmission scheduling modes corresponding to the logical channel, and each data transmission scheduling mode comprising: First scheduling mode; A second scheduling mode that is different from the first scheduling mode; or A third scheduling mode that includes the first scheduling mode and the second scheduling mode; as well as The transmitter transmits buffer status reports based on the plurality of data transmission scheduling modes. The receiver receives a sidelink license from the base station unit, wherein, in response to receiving the sidelink license from the base station unit, if each of the data transmission scheduling modes of the plurality of logical channels includes the first scheduling mode, then data for only the logical channel is included, wherein data transmission with the second scheduling mode is not performed before receiving the sidelink license.

13. The apparatus according to claim 12, wherein, If the data transmission scheduling mode of one of the plurality of logical channels includes the first scheduling mode, then the transmitter transmits the buffer status report based on the plurality of data transmission scheduling modes, which includes only the data for the logical channel.

14. The apparatus according to claim 12, wherein, The transmitter transmits the buffer status report based on the multiple data transmission scheduling modes, which includes data for all logical channels used by the multiple logical channels.

15. The apparatus according to claim 12, wherein, The processor triggers the transmission of the buffer status report in response to a logical channel among the plurality of logical channels having a data transmission scheduling mode that includes the first scheduling mode.

16. The apparatus according to claim 12, wherein, Sidelink licenses received by the control channel have a higher priority than autonomously generated sidelink licenses.

17. The apparatus according to claim 12, wherein, The processor selects a sidelink license, and in response to selecting the sidelink license, if the data transmission scheduling mode of the logical channel among the plurality of logical channels includes the second scheduling mode, then data for only the logical channel is included.

18. The apparatus according to claim 12, wherein, In response to the autonomous data corresponding to autonomous transmission having a higher priority than the scheduling data corresponding to sidelink resources, the sidelink resources scheduled by the base station unit are preempted by the autonomous transmission.

19. The apparatus of claim 12, wherein the first scheduling mode includes a first power control loop, and the second scheduling mode includes a second power control loop, and the first power control loop is independent of the second power control loop.

20. The apparatus according to claim 12, wherein, The first scheduling mode includes a first power control loop, and the second scheduling mode includes a second power control loop, and the first power control loop and the second power control loop are related to each other.

21. The apparatus according to claim 12, wherein, The transmitter uses the first scheduling mode to transmit initial feedback and uses the second scheduling mode to retransmit feedback.

22. The apparatus according to claim 12, wherein, The transmitter uses the second scheduling mode to transmit initial feedback and uses the first scheduling mode to retransmit feedback.

Images