Mobile device and method for implementing enhanced configured grants

Abstract

Improved configured grants (CGs) can include a designation of a coverage zone corresponding to uplink transmissions by a UE, where the coverage zone is defined at least in part by an occupied transmission time, an occupied transmission frequency, and a transmission power. The coverage zone can be adjusted and / or selected by the UE according to current traffic needs of the UE and within limits set for the coverage zone via prior signaling from a base station to the UE. The UE can indicate the actual coverage zone parameter / value for uplink data transmissions by the UE by transmitting a CG uplink control information (CG-UCI) including the actual coverage zone value to the base station. The UE can transmit the CG-UCI on resources configured according to additional parameter values received from the base station via the prior signaling. The UE can also transmit uplink data on resources configured according to the actual coverage zone value.

Description

Technical Field

[0001] This application relates to wireless communication, and more specifically to providing configuration licensing in wireless communication (e.g., 3GPP NR communication). Background Technology

[0002] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices (i.e., user equipment or UE) now offer access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and are capable of operating complex applications that utilize these capabilities. Furthermore, many different wireless communication technologies and standards exist. Some examples of wireless communication standards include GSM, UMTS (WCDMA, TD-SCDMA), LTE, LTE Advanced (LTE-A), HSPA, 3GPP 2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), IEEE 802.16 (WiMAX), and BLUETOOTH. TM The proposed telecommunications standard that surpasses the International Mobile Telecommunications Advanced (IMT-Advanced) standard is the 5th generation mobile network or 5th generation radio system, called 3GPP NR (also known as 5G New Radio (5G-NR), or simply NR). NR provides higher capacity for higher density mobile broadband users while supporting device-to-device, ultra-reliable and massive machine-type communications, as well as lower latency and lower battery consumption than the LTE standard.

[0003] 3GPP LTE / NR defines several downlink (DL) physical channels, classified as transport or control channels, to carry blocks of information received from the MAC and higher layers. 3GPP LTE / NR also defines uplink (UL) physical layer channels. The Physical Downlink Shared Channel (PDSCH) is a DL transport channel and the primary data bearer channel allocated to users on a dynamic and opportunistic basis. The PDSCH carries data in transport blocks (TBs) corresponding to Medium Access Control Protocol Data Units (MAC PDUs), which are passed from the MAC layer to the physical (PHY) layer once every transmission time interval (TTI). The PDSCH is also used to transmit broadcast information such as System Information Blocks (SIBs) and paging messages.

[0004] The Physical Downlink Control Channel (PDCCH) is a DL control channel that carries UE resource allocations contained in Downlink Control Information (DCI) messages. For example, the DCI may include a Transmission Configuration Indication (TCI) related to beamforming, where the TCI includes configurations such as quasi-co-address (QCL) relationships between downlink reference signals (DL-RS) and PDSCH demodulation reference signals (DMRS) ports within a Channel State Information RS (CSI-RS) set. Each TCI state can contain parameters for configuring QCL relationships between one or two downlink reference signals and DMRS ports of the PDSCH, DMRS ports of the PDCCH, or CSI-RS ports of CSI-RS resources. Multiple PDCCHs can be transmitted in the same subframe using Control Channel Elements (CCEs), each of which is a set of resource elements called a Resource Element Group (REG). The PDCCH may employ Quadrature Phase Shift Keying (QPSK) modulation, where a specific number (e.g., four) of QPSK symbols are mapped to each REG. In addition, depending on the channel conditions, the UE can use a specified number (e.g., 1, 2, 4 or 8) of CCEs to ensure sufficient robustness.

[0005] The Physical Uplink Shared Channel (PUSCH) is a UL channel shared by all devices (User Equipment, UE) in a radio cell to transmit user data to the network. Scheduling for all UEs is under the control of the base station (e.g., eNB or gNB). The base station uses uplink scheduling grants (e.g., in DCI) to inform the UE about resource block (RB) allocations and the modulation and coding schemes to be used. PUSCH typically supports QPSK and Quadrature Amplitude Modulation (QAM). In addition to user data, PUSCH carries any control information required for decoding, such as transport format indicators and Multiple-Input Multiple-Output (MIMO) parameters. Control data is multiplexed with information data before Digital Fourier Transform (DFT) expansion.

[0006] A crucial aspect of wireless data transmission is scheduling. Generally, in communication between a UE (User Equipment) and the wireless network, scheduling is used to specify time slots for uplink communication transmitted from the UE to the base station. For uplink communication, the UE can first send a scheduling request to the base station. In response, the base station can grant permission to transmit uplink data by sending an uplink grant to the UE. In most cases, scheduling is entirely dynamic. In the downlink direction, resources are allocated as data becomes available. For data to be transmitted in the uplink direction, the UE dynamically requests a transmission opportunity whenever data arrives at the UE's uplink buffer. Information about the data to be transmitted in the downlink direction and the uplink transmission opportunity is carried in a radio layer control channel, which is sent at the beginning of each subframe. While dynamic scheduling is effective for infrequent and bandwidth-intensive data transmissions that may result in large data bursts (e.g., internet browsing, video streaming, email), it is less suitable for real-time streaming applications such as voice calls. In the latter case, data is transmitted in short bursts at regular intervals. If the data rate of the stream is very low, such as in the case of a voice call, the overhead of scheduling messages can become very high because only a small amount of data is sent for each scheduling message.

[0007] One solution to this problem is semi-persistent scheduling (SPS). Instead of scheduling every uplink or downlink transmission, a transmission pattern is defined instead of individual opportunities. This significantly reduces scheduling allocation overhead. During quiet periods, the radio voice CODEC in the UE stops transmitting voice data and only sends quiet description information with much longer time intervals between them. Persistent scheduling can be disabled during those quiet periods. In the uplink, the SPS grant scheme is implicitly canceled if there are no available uplink transmission opportunities to send data for the number of times the network is configured. In the downlink direction, SPS is canceled using an RRC (Radio Resource Control) message.

[0008] Using SPS, the base station provides the UE with a predetermined schedule of periodic time slots, where the UE can perform uplink communication. This allows the UE to generate uplink transmissions to the base station without the overhead of scheduling requests and specific (dynamic) uplink grants. Therefore, when the base station configures SPS radio resources, the mobile phone can utilize the periodic resources without an additional scheduling request process. When a device has data to transmit in its buffer, it can transmit that data via the next already configured periodic resource. However, since SPS configuration is implemented on a per-device basis, SPS resources not utilized by a device are wasted when the device does not need the periodic resources, for example, when data must be transmitted only when a specific event occurs. To reduce this waste of periodic resource allocation, multiple devices can be configured to share periodic resources through a function called Configuration Grant (CG). Configuration Grant is initially based on SPS features and allows the base station to allocate configuration grant resources to multiple devices that can utilize the resources as needed (e.g., when they have data to transmit). By allocating the configuration grant resources, the network eliminates packet transmission latency in the scheduling request process while also improving the utilization of the allocated periodic radio resources. However, the current implementation of configuration grants can be inefficient under certain traffic conditions. Therefore, improvements in the art are desired.

[0009] Other corresponding issues related to the prior art will become apparent to those skilled in the art after comparing such prior art with the disclosed embodiments described herein. Summary of the Invention

[0010] This document provides, in particular, an implementation scheme for a method to implement improved configuration authorization (CG) in wireless communications, such as 3GPP New Radio (NR) communications. The document further provides an implementation scheme for a wireless communication system comprising user equipment (UE) and / or base stations communicating with each other within the wireless communication system.

[0011] To improve CG, the coverage area of ​​the UE's uplink transmission can be defined at least in part by the occupied transmission time, the occupied transmission frequency, and the transmission power. This coverage area can be dynamically adjusted / selected by the UE based on the UE's current traffic requirements, and within the constraints set for the coverage area via previous signaling from the base station to the UE. The UE can indicate the actual coverage area parameters / values ​​of the UE's uplink data transmission to the base station by transmitting CG Uplink Control Information (CG-UCI) that includes the actual coverage area value.

[0012] Therefore, the device can receive from the base station a first set of values ​​corresponding to a first set of transmission parameters used to at least partially configure resources for uplink data transmission (e.g., PUSCH transmission) for the device, and can also receive from the base station a second set of values ​​corresponding to a second set of transmission parameters used to at least partially configure resources for uplink control information transmission (e.g., CG-UCI transmission) for the device. The device can determine a third set of values ​​corresponding to the first set of transmission parameters based at least on the device's current radio traffic requirements and further based on the first set of values, and transmit uplink control information (e.g., CG-UCI) containing at least the third set of values ​​to the base station on resources configured using at least the second set of values. The device can transmit uplink data (e.g., PUSCH) to the base station on resources configured using at least the third set of values. The first set of transmission parameters can be used to define the device's uplink transmission coverage area and can include transmission duration, transmission power, transmission frequency, and modulation and coding scheme level. Therefore, the first set of values ​​can include ranges / limitations corresponding to the aforementioned reference parameters, including maximum transmission duration, maximum transmission power, modulation and coding scheme level range, and / or maximum occupied frequency. The third set of values ​​may include the transmission duration for each repetition, the number of repetitions, the modulation and coding scheme level, the occupied frequency, and / or the cyclic redundancy check bits masked by the device. The second set of values ​​may be used by the device to define / configure the resources on which the device can transmit UCI (which includes at least the third set of values), and may include modulation order, coding rate, time and frequency resource elements, and / or demodulation reference signal configuration.

[0013] It should be noted that the technologies described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to base stations, access points, cellular phones, portable media players, tablets, wearable devices and various other computing devices.

[0014] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0015] Figure 1 Exemplary (and simplified) wireless communication systems according to some implementation schemes are shown;

[0016] Figure 2 An exemplary base station communicating with an exemplary wireless user equipment (UE) device according to some embodiments is shown;

[0017] Figure 3 An exemplary block diagram of a UE according to some implementation schemes is shown;

[0018] Figure 4 An exemplary block diagram of a base station according to some implementation schemes is shown;

[0019] Figure 5 An exemplary simplified block diagram of an illustrative cellular communication circuit according to some embodiments is shown;

[0020] Figure 6 An exemplary diagram is shown illustrating the allocation of Combined Configuration Authorization (CG) for combined traffic of multiple flows according to some implementation schemes.

[0021] Figure 7 A graph showing CG-UCI candidate positions during PUSCH repeat type B transmissions is presented according to some implementation schemes;

[0022] Figure 8 Charts illustrating frequency occupancy for cyclic prefix OFDM transmission and DFT-S-OFDM transmission respectively, according to some implementation schemes, are shown.

[0023] Figure 9 Frequency occupancy for CG-UCI transmission is shown according to some implementation schemes, where CG-UCI exists in some repetitions but not in others;

[0024] Figure 10 A flowchart illustrating an exemplary method for implementing CG on a mobile device according to some embodiments is shown; and

[0025] Figure 11 A flowchart illustrating an exemplary method for implementing a base station for CG according to some implementation schemes is shown.

[0026] While the features described herein are susceptible to various modifications and alternatives, specific embodiments thereof are illustrated by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and their detailed description are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents, and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation

[0027] acronym

[0028] Various acronyms are used throughout this patent application. The definitions of the most prominent acronyms that may appear throughout this patent application are as follows:

[0029] •ACK: Confirmation

[0030] • APR: Application Processor

[0031] •AUL: Autonomous Uplink Transmission

[0032] • BLER: Block Error Rate

[0033] ·BS: Base Station

[0034] • BSR: Buffer Status Report

[0035] • BWP: Bandwidth section

[0036] • CAPC: Channel Access Priority Category

[0037] •CG: Configuration Authorization

[0038] • CMR: Change Mode Request

[0039] • CORESET: Control Channel Resource Set

[0040] •COT: Channel Occupancy Time

[0041] • CRC: Cyclic Redundancy Check

[0042] • CS-RNTI: Configured temporary identifier for the dispatch radio network

[0043] • CSI: Channel State Information

[0044] • DCI: Downlink Control Information

[0045] • DG: Dynamic Licensing

[0046] •DL: Downlink (from BS to UE)

[0047] DMRS: Demodulation Reference Signal

[0048] ·DYN: Dynamic

[0049] ED: Energy Detection

[0050] •Frequency Division Multiplexing

[0051] FT: Frame Type

[0052] • GC-PDCCH: Group Common Physical Downlink Control Channel • GPRS: General Packet Radio Service

[0053] GSM: Global System for Mobile Communications

[0054] • GTP: GPRS Tunneling Protocol

[0055] HARQ: Hybrid Automatic Repeat Request

[0056] •IR: Initialization and refresh status

[0057] LAN: Local Area Network

[0058] LTE: Long Term Evolution

[0059] MAC: Media Access Control

[0060] ·MAC-CE: MAC control element

[0061] • MCS: Modulation and Coding Scheme

[0062] MIB: Master Information Block

[0063] MIMO: Multiple Input Multiple Output

[0064] • NDI: New Data Indication

[0065] • OFDM: Orthogonal Frequency Division Multiplexing

[0066] OSI: Open Systems Interconnection

[0067] ·PBCH: Physical Broadcast Channel

[0068] • PDCCH: Physical Downlink Control Channel

[0069] • PDCP: Packet Data Convergence Protocol

[0070] • PDN: Packet Data Network

[0071] • PDSCH: Physical Downlink Shared Channel

[0072] • PDU: Protocol Data Unit

[0073] • PRB: Physical Resource Block

[0074] • PUCCH: Physical Uplink Control Channel

[0075] • PUSCH: Physical Uplink Shared (Data) Channel • QCL: Quasi-Co-address

[0076] RACH: Random Access Procedure

[0077] • RAT: Radio Access Technology

[0078] ·RB: Resource Block

[0079] RE: Resource Element

[0080] RF: Radio Frequency

[0081] •RMSI: Residual Minimal System Information

[0082] • RNTI: Temporary Identifier for Radio Networks

[0083] ·ROHC: Robust Standard Head Compression

[0084] •RRC: Radio Resource Control

[0085] • RS: Reference signal (symbol)

[0086] • RSI: Root Sequence Indicator

[0087] RTP: Real-time Transport Protocol

[0088] ·RV: Redundant version

[0089] ·RX: Receive

[0090] •SDM: Spatial Division Multiplexing

[0091] • SID: System Identifier

[0092] • SGW: Service Gateway

[0093] •SR: Scheduling Request

[0094] • SRS: Detection Reference Signal

[0095] ·SS: Search Space

[0096] •SSB: Synchronization Signal Block

[0097] • TBS: Transport Block Size

[0098] •TCI: Transmission Configuration Indicator

[0099] • TDM: Time Division Multiplexing

[0100] • TRS: Tracking Reference Signal

[0101] TX: Transmission

[0102] • UCI: Uplink Control Information

[0103] UE: User Equipment

[0104] • UL: Uplink (from UE to BS)

[0105] UMTS: Universal Mobile Telecommunications System

[0106] • Wi-Fi: Wireless local area network based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard

[0107] WLAN RAT

[0108] WLAN: Wireless LAN

[0109] the term

[0110] The following is a glossary of terms that will appear in this application:

[0111] Memory media—any device of any type of memory device or storage device. The term “memory media” is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, such as hard disk drives or optical storage devices; registers, or other similar types of memory elements, etc. Memory media may also include other types of memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In a later example, the second computer system may provide program instructions to the first computer system for execution. The term “memory media” may include two or more memory media that may reside in different locations on different computer systems, for example, connected via a network. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.

[0112] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks, and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals, or digital signals).

[0113] Programmable hardware elements—including a variety of hardware devices comprising multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can vary from fine-grained (combinatorial logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as “configurable logic units.”

[0114] Computer system (or computer) — any of the various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. Generally, the term "computer system" can be broadly defined as any device (or combination of devices) that includes at least one processor that executes instructions from a memory medium.

[0115] User equipment (UE) (or “UE device”) — any of the various types of computer system devices that perform wireless communication. Also referred to as wireless communication devices, many of which can be mobile and / or portable. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). TM Based on Android TM (phones) and tablets such as iPad TM Samsung Galaxy TM etc., gaming devices (such as Sony PlayStation) TM Microsoft Xbox TM etc.), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPod TM Laptops, wearable devices (e.g., Apple Watch) TM Google Glass TM PDAs, portable internet devices, music players, data storage devices or other handheld devices, unmanned aerial vehicles (e.g., drones) and drone controllers, etc. Various other types of devices that include Wi-Fi communication capabilities or both cellular and Wi-Fi communication capabilities and / or other wireless communication capabilities (e.g., via Short Range Radio Access Technology (SRAT) such as BlueTooth). TM (etc.) would fall into this category. Generally, the term "UE" or "UE device" can be broadly defined to cover any electronic device, computing device, and / or telecommunications device (or combination of devices) capable of wireless communication, and can also be portable / mobile.

[0116] A wireless device (or wireless communication device) is any of a variety of computer system devices that perform wireless communication using WLAN communication, SRAT communication, Wi-Fi communication, etc. As used herein, the term "wireless device" can refer to a UE device as defined above or a fixed device such as a fixed wireless client or a wireless base station. For example, a wireless device can be a wireless station of any type of 802.11 system, such as an access point (AP) or client site (UE), or a wireless station of any type of cellular communication system that communicates according to cellular radio access technologies (e.g., LTE, CDMA, GSM), such as a base station or cellular phone.

[0117] A communication device is any of various types of computer systems or devices that perform communication, which may be wired or wireless. A communication device may be portable (or mobile), or it may be stationary or fixed in a location. A wireless device is one example of a communication device. A UE is another example of a communication device.

[0118] Base station (BS) — The term “base station” has the full range of its usual meaning and includes at least a wireless communication station that is installed in a fixed location and used for communication as part of a wireless telephone system or radio system.

[0119] A processor is a component (e.g., circuitry) or combination of components capable of performing functions in a device (e.g., in a user equipment device or a cellular network device). A processor may include, for example: a general-purpose processor and associated memory, portions or circuitry of individual processor cores, an entire processor core or processing circuitry core, an array of processing circuitry or a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

[0120] A channel is a medium used to transmit information from a transmitter to a receiver. It should be noted that because the characteristics of the term "channel" can vary depending on different wireless protocols, the term "channel" as used herein can be considered to be used in a standard manner consistent with the type of device to which the term is referenced. In some standards, the channel width can be variable (e.g., depending on device capabilities, band conditions, etc.). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. In contrast, WLAN channels can be 22 MHz wide, while Bluetooth channels can be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0121] Band (or frequency band) — The term "band" encompasses the full range of its usual meaning and includes at least a segment of the spectrum (e.g., radio frequency spectrum) in which channels are used or reserved for the same purpose. Furthermore, "band" is used to refer to any interval in the frequency domain defined by lower and higher frequencies. The term can refer to radio frequency bands or intervals of some other spectrum. Radio communication signals may occupy a frequency range that carries the signal (or the frequency range in which the signal is carried). Such a frequency range is also called the bandwidth of the signal. Therefore, bandwidth refers to the difference between the upper and lower frequencies in a continuous band. A band can represent a single communication channel, or it can be subdivided into multiple communication channels. The allocation of radio frequency ranges for different purposes is a primary function of radio spectrum allocation.

[0122] Wi-Fi—The term “Wi-Fi” encompasses the full range of its common meaning and includes at least wireless communication networks, or RATs, which are provided by and through wireless LAN (WLAN) access points to provide connectivity to the Internet. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and are marketed under the name “Wi-Fi.” Wi-Fi (WLAN) networks are distinct from cellular networks.

[0123] Automatic—means an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct user input to specify or perform that action or operation. Therefore, the term "automatic" contrasts with an action performed or specified manually by a user, where the user provides input to directly perform that action. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input to specify information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.

[0124] Approximately—means a value close to the correct or precise value. For example, approximately can refer to a value within 1% to 10% of the precise (or expected) value. However, it should be noted that the actual threshold (or tolerance) can vary depending on the application. For example, in some implementations, “approximately” may mean within 0.1% of some specified or expected value, while in various other implementations, the threshold may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of the specific application.

[0125] Concurrency refers to the parallel execution or implementation of tasks, processes, or programs in a manner that at least partially overlaps. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0126] Site (STA) — The term “site” in this document refers to any device capable of wireless communication (e.g., using the 802.11 protocol). A site can be a laptop, desktop PC, PDA, access point, Wi-Fi phone, or any type of device similar to a UE. An STA can be fixed, mobile, portable, or wearable. Generally, in wireless networking terminology, the term site (STA) broadly encompasses any device with wireless communication capabilities, and the terms site (STA), wireless client (UE), and node (BS) are therefore often used interchangeably.

[0127] "Configured as"—Various components can be described as being "configured as" to perform one or more tasks. In such contexts, "configured as" is a broad expression generally meaning "having" a "structure" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, "configured as" can also be a broad expression generally meaning a structure that "has" a "circuit" that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently powered on. Typically, the circuit forming the structure corresponding to "configured as" can include hardware circuitry.

[0128] Transmission scheduling refers to the scheduling of transmissions (such as wireless transmissions). In some specific implementations of cellular radio communications, signal and data transmissions can be organized according to designated time units of a specific duration during which a transmission occurs. As used herein, the term "slot" has the full range of its usual meaning and at least refers to the smallest (or shortest) scheduling time unit in wireless communications. For example, in 3GPP LTE, transmissions are divided into radio frames, each with an equal (time) duration (e.g., 10 ms). Radio frames in 3GPP LTE can be further divided into a specified number (e.g., ten) subframes, each with an equal duration, which are designated as the smallest (shortest) scheduling unit, or the designated time unit for transmission. Thus, in the 3GPP LTE example, a "subframe" can be considered an example of a "slot" as defined above. Similarly, the smallest (or shortest) scheduling time unit for 5G NR (or simply NR) transmissions is called a "slot." The smallest (or shortest) scheduling time unit may also be named differently in different communication protocols.

[0129] Resources—The term “resource” has the full range of its usual meaning and can refer to frequency resources and time resources used during wireless communication. As used herein, a resource element (RE) refers to a specific quantity or number of resources. For example, in the context of time resources, a resource element can be a time period of a specific length. In the context of frequency resources, a resource element can be a specific frequency bandwidth centered at a specific frequency or a specific amount of frequency bandwidth. As a concrete example, a resource element can refer to a resource unit with one symbol (reference time resource, such as a specific frequency bandwidth centered at a specific frequency) for every one subcarrier (reference frequency resource). A resource element group (REG) has the full range of its usual meaning and refers to at least a specified number of consecutive resource elements. In some specific implementations, a resource element group may not include resource elements reserved for a reference signal. A control channel element (CCE) refers to a specified number of consecutive REGs. A resource block (RB) refers to a specified number of resource elements consisting of a specified number of subcarriers per specified number of symbols. Each RB may include a specified number of subcarriers. A resource block group (RBG) refers to a unit comprising multiple RBs. The number of RBs within an RBG can vary depending on the system bandwidth.

[0130] For ease of description, various components may be described as performing one or more tasks. Such descriptions shall be interpreted as including the phrase “configured to”. The statement that a component is configured to perform one or more tasks is expressly intended not to invoke the interpretation of paragraph 6 of section 112 of title 35 of the United States Code.

[0131] Figure 1 and Figure 2 -Exemplary communication system

[0132] Figure 1 Exemplary (and simplified) wireless communication systems according to some implementation schemes are shown. It should be noted that... Figure 1 The system described is merely one example of a possible system, and this implementation can be carried out in any of a variety of systems as needed.

[0133] As shown in the figure, the exemplary wireless communication system includes base stations 102A to 102N, also collectively referred to as multiple base stations 102 or base station 102. Figure 1 As shown, base station 102A communicates with one or more user equipments 106A to 106N via a transmission medium. Each user equipment may be referred to herein as a “User Equipment” (UE) or UE device. Therefore, user equipments 106A to 106N are referred to as UEs or UE devices, and are also collectively referred to as multiple UEs 106 or UE 106. The various UE devices within the UE devices can operate using the configuration licenses disclosed herein.

[0134] Base station 102A can be a transceiver base station (BTS) or a cell site, and may include hardware to enable wireless communication with UEs 106A to 106N. Base station 102A may also be configured to communicate with network 100, such as the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN) and / or the Internet, neutral hosts, or various CBRS (Citizen Broadband Radio Service) deployments, and various other possibilities. Therefore, base station 102A facilitates communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various communication capabilities such as voice, SMS, and / or data services. The communication area (or coverage area) of the base station may be referred to as a “cell.” It should also be noted that a “cell” can also refer to a logical identity for a given coverage area at a given frequency. Typically, any independent cellular wireless coverage area can be referred to as a “cell.” In such a case, the base station may be located at a specific intersection of three cells. In this uniform topology, the base station can serve three 120-degree beamwidth areas called cells. Furthermore, for carrier aggregation, small cells, relays, etc., can all represent cells. Therefore, especially in carrier aggregation, there can be primary and secondary cells that serve at least partially overlapping coverage areas but operate on different corresponding frequencies. For example, a base station can serve any number of cells, and the cells served by the base station can be arranged side-by-side or not (e.g., at a remote radio head). Similarly, as used herein, with respect to the UE, sometimes, considering the UE's uplink and downlink communications, the base station can be considered to represent the network. Therefore, a UE communicating with one or more base stations in the network can also be interpreted as a UE communicating with that network, and can also be considered as at least a part of the UE's communication on or through the network.

[0135] Base station 102 and user equipment can be configured to communicate via a transmission medium using any of a variety of Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (WCDMA), LTE, LTE-Advanced (LTE-A), LAA / LTE-U, 5G-NR (abbreviated as NR), 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), Wi-Fi, WiMAX, etc. Note that if base station 102 is implemented in an LTE environment, it may alternatively be referred to as an "eNodeB" or "eNB". Note that if base station 102A is implemented in a 5G NR environment, it may alternatively be referred to as a "gNodeB" or "gNB". In some implementations, base station 102 may be configured with authorization, as described herein. Depending on the given application or specific considerations, for convenience, several different RATs may be functionally grouped according to overall defined characteristics. For example, all cellular RATs can be uniformly considered as representing a first (form / type) RAT, while Wi-Fi communication can be considered as representing a second RAT. In other cases, individual cellular RATs can be considered as distinct RATs. For example, when distinguishing between cellular and Wi-Fi communication, "first RAT" can uniformly refer to all cellular RATs under consideration, while "second RAT" can refer to Wi-Fi. Similarly, where applicable, different forms of Wi-Fi communication (e.g., above 2.4 GHz and above 5 GHz) can be considered to correspond to different RATs. Furthermore, cellular communication performed under a given RAT (e.g., LTE or NR) can be distinguished from each other based on the spectrum in which those communications are performed. For example, LTE or NR communication can be performed on the primary licensed spectrum as well as on secondary spectrum such as unlicensed spectrum and / or spectrum assigned to the Citizens Broadband Radio Service (CBRS). In general, the use of various terms and expressions will always be clearly indicated in relation to the context of the various applications / implementations considered.

[0136] As shown in the figure, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A can facilitate communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide UE 106 with various communication capabilities such as voice, SMS, and / or data services. Base station 102A and other similar base stations (such as base stations 102B…102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping services to UE 106A-106N and similar devices over a geographical area via one or more cellular communication standards.

[0137] Therefore, although base station 102A can act as such Figure 1 The diagram shows the "serving cell" of UEs 106A-106N, but each UE 106 may also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B-102N and / or any other base stations), which may be referred to as "neighboring cells". Such cells may also facilitate communication between user equipments and / or between user equipments and network 100. These cells may include "macro" cells, "micro" cells, "pecimen" cells, and / or any other cells of various other granularities providing a service area size. For example, in Figure 1 Base stations 102A-102B shown can be macro cells, while base station 102N can be a micro cell. Other configurations are also possible.

[0138] In some implementations, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a “gNB”. In some implementations, the gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, a gNB cell may include one or more transmit and receive points (TRPs). Additionally, a UE capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.

[0139] As described above, UE 106 may be able to communicate using multiple wireless communication standards. For example, the UE may be configured to communicate using any or all of the 3GPP cellular communication standards (such as LTE or NR) or 3GPP2 cellular communication standards (such as cellular communication standards in the CDMA2000 series). Base station 102 and other similar base stations operating according to the same or different cellular communication standards can therefore be provided as one or more cell networks that can provide continuous or near-continuous overlapping services to UE 106 and similar devices over a wide geographical area via one or more cellular communication standards.

[0140] UE 106 can also be configured, or alternatively configured, to use WLAN, BLUETOOTH TM BLUETOOTH TM Communication can be made using low-energy, one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one and / or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), etc. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible. Furthermore, UE 106 may also communicate with network 100 via one or more base stations or via other devices, sites, or any apparatus not explicitly shown but considered part of network 100. Therefore, UE 106's communication with the network can be interpreted as UE 106 communicating with one or more network nodes considered part of the network, and interacting with UE 106 to communicate with UE 106, and in some cases affecting at least some communication parameters and / or the use of UE 106's communication resources.

[0141] In addition, such as Figure 1 As shown, at least some of UEs 106 (e.g., UEs 106D and 106E) can represent vehicles communicating with each other and with base station 102A, for example, via cellular communications such as 3GPP LTE and / or 5G-NR. Additionally, UE 106F can similarly represent a pedestrian communicating and / or interacting with the vehicles represented by UEs 106D and 106E. In the context of vehicle-to-everything (V2X) communication (such as communication specified by 3GPP TS 22.185V 14.3.0, etc.), the disclosure... Figure 1 Other aspects of vehicles communicating in the network illustrated in the example.

[0142] Figure 2An exemplary user equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 and access point 112 according to some embodiments is shown. UE 106 may be capable of both cellular and non-cellular communication (e.g., BLUETOOTH). TM Devices such as mobile phones, handheld devices, computers, or tablets, or virtually any type of wireless device (e.g., Wi-Fi, etc.). UE 106 may include a processor configured to execute program instructions stored in memory. UE 106 can perform any of the method embodiments of the present invention by executing such stored instructions. Alternatively or additionally, UE 106 may include programmable hardware elements, such as a field-programmable gate array (FPGA) configured to perform any of the method embodiments of the present invention or any portion thereof. UE 106 may be configured to communicate using any of a plurality of wireless communication protocols. For example, UE 106 may be configured to communicate using two or more of CDMA 2000, LTE, LTE-A, NR, WLAN, or GNSS. Other combinations of wireless communication standards are also possible.

[0143] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols according to one or more RAT standards, such as those previously described above. In some embodiments, UE 106 may share one or more portions of a receive chain and / or transmit chain among multiple wireless communication standards. The shared radio components may include a single antenna, or may include multiple antennas for performing wireless communication (e.g., for MIMO). Alternatively, UE 106 may include independent transmit chains and / or receive chains (e.g., including independent antennas and other radio components) for each wireless communication protocol configured to communicate using it. As another alternative, UE 106 may include one or more radio components or radio circuits shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 may include shared radio components for communicating using either LTE or CDMA2000 1xRTT or NR, and for communicating using Wi-Fi and BLUETOOTH. TM Each component communicates independently. Other configurations are also possible.

[0144] Figure 3 - Block diagram of an exemplary UE

[0145] Figure 3A block diagram of an exemplary UE 106 according to some embodiments is shown. As shown, UE 106 may include a System-on-Chip (SOC) 300, which may include portions for various purposes. For example, as shown, SOC 300 may include a processor 302 capable of executing program instructions for UE 106, and display circuitry 304 capable of performing graphics processing and providing display signals to a display 360. The processor 302 may also be coupled to a memory management unit (MMU) 340, and / or other circuitry or devices (such as display circuitry 304, radio circuitry 330, connector I / F 320, and / or display 360), which may be configured to receive addresses from the processor 302 and translate those addresses into locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310). MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, MMU 340 may be included as part of the processor 302.

[0146] As shown in the figure, the SOC 300 can be coupled to various other circuits of the UE 106. For example, the UE 106 may include various types of memory (e.g., including NAND flash memory 310), connector interface 320 (e.g., for coupling to a computer system), display 360, and wireless communication circuitry (e.g., for LTE, LTE-A, NR, CDMA2000, BLUETOOTH). TM (e.g., Wi-Fi, GPS, etc.). UE device 106 may include at least one antenna (e.g., 335a) and may include multiple antennas (e.g., shown by antennas 335a and 335b) for performing wireless communication with a base station and / or other devices. Antennas 335a and 335b are shown by way of example, and UE device 106 may include fewer or more antennas. Generally, one or more antennas are collectively referred to as antenna 335. For example, UE device 106 may use antenna 335 to perform wireless communication via radio circuitry 330. As described above, in some embodiments, the UE may be configured to use multiple wireless communication standards for wireless communication.

[0147] As further described herein, UE 106 (and / or base station 102) may include hardware and software components for operating control signaling transmitted and received using an enhanced physical control channel (e.g., PDCCH), as described in further detail herein. The processor 302 of UE device 106 may be configured to implement some or all of the methods described herein, for example by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). In other embodiments, processor 302 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Furthermore, processor 302 may be coupled to, for example, Figure 3 Other components shown and / or interoperable with said other components to enable configuration authorization according to the various embodiments disclosed herein. Processor 302 may also implement various other applications and / or end-user applications running on UE 106.

[0148] In some implementations, the radio circuit 330 may include a separate controller dedicated to controlling communications for various corresponding RAT standards. For example, such as Figure 3 As shown, the radio circuit 330 may include a Wi-Fi controller 356, a cellular controller (e.g., an LTE and / or NR controller) 352, and a BLUETOOTH controller. TM Controller 354, and in at least some embodiments, one or more of these controllers may be implemented as corresponding integrated circuits (referred to as ICs or chips) that communicate with each other and with the SOC 300 (more specifically, with the processor 302). For example, Wi-Fi controller 356 may communicate with cellular controller 352 via a cell-ISM link or WCI interface, and / or BLUETOOTH TM Controller 354 can communicate with cellular controller 352 via a cell-ISM link, etc. Although three independent controllers are shown within radio circuitry 330, other implementations with fewer or more similar controllers for various different RATs can be implemented in UE device 106. For example, in Figure 5 At least one exemplary block diagram illustrating some implementations of the cellular controller 352 is shown, and will be further described below.

[0149] Figure 4 - Block diagram of an exemplary base station

[0150] Figure 4 A block diagram of an exemplary base station 102 according to some implementation schemes is shown. It should be noted that... Figure 4The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include a processor 404 capable of executing program instructions specific to base station 102. Processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuitry or device, which may be configured to receive addresses from processor 404 and translate those addresses into locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0151] Base station 102 may include at least one network port 470. Network port 470 may be configured to be coupled to a telephone network and provide access rights as described above. Figure 1 and Figure 2 The telephone network described herein includes multiple devices such as UE device 106. Network port 470 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices such as UE device 106. In some cases, network port 470 may be coupled to the telephone network via the core network, and / or the core network may provide the telephone network (e.g., in other UE devices served by the cellular service provider).

[0152] Base station 102 may include at least one antenna 434, and may include multiple antennas (e.g., shown by antennas 434a and 434b) for wireless communication with mobile devices and / or other devices. Antennas 434a and 434b are shown as examples, and base station 102 may include fewer or more antennas. Generally, one or more antennas that may include antenna 434a and / or antenna 434b are collectively referred to as antenna 434. Antenna 434 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE device 106 via radio circuit 430. Antenna 434 may communicate with radio circuit 430 via communication link 432. Communication link 432 may be a receive link, a transmit link, or both. Radio circuit 430 may be designed to communicate via various wireless telecommunication standards, including but not limited to LTE, LTE-A, 5G-NR (or simply NR), WCDMA, CDMA2000, etc. The processor 404 of base station 102 may be configured to implement some or all of the methods described herein, for example by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) to enable base station 102 to implement the configuration authorization disclosed herein. Alternatively, processor 404 may be configured as a programmable hardware element such as an FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit) or a combination thereof. In the case of certain RATs (e.g., Wi-Fi), base station 102 may be designed as an access point (AP), in which case network port 470 may be implemented to provide access to a wide area network and / or one or more local area networks, for example, it may include at least one Ethernet port, and radio component 430 may be designed to communicate according to the Wi-Fi standard. Base station 102 may operate to implement configuration authorization according to various methods and embodiments disclosed herein.

[0153] Figure 5 - Block diagram of an exemplary cellular communication circuit

[0154] Figure 5 An exemplary simplified block diagram of an illustrative cellular controller 352 according to some embodiments is shown. It should be noted that... Figure 5The block diagram of the cellular communication circuit is merely one example of possible cellular communication circuits; other circuits, such as those including or coupled to sufficient antennas for different RATs to perform uplink activities using independent antennas, or those including or coupled to fewer antennas, such as those that can be shared among multiple RATs, are also possible. According to some embodiments, the cellular communication circuit 352 may be included in a communication device such as the communication device 106 described above. As mentioned above, among other devices, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop computer, notebook computer, or portable computing device), a tablet computer, and / or a combination of these devices.

[0155] Cellular communication circuitry 352 may be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 335a-b and 336 as shown in the figure. In some embodiments, cellular communication circuitry 352 may include dedicated receive chains for multiple RATs (including and / or coupled (e.g., communicatively; directly or indirectly) to dedicated processors and / or radio components (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as Figure 5 As shown, the cellular communication circuit 352 may include a first modem 510 and a second modem 520. The first modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the second modem 520 may be configured for communication according to a second RAT (e.g., such as 5G NR).

[0156] As shown, the first modem 510 may include one or more processors 512 and a memory 516 communicating with the processors 512. The modem 510 may communicate with a radio frequency (RF) front-end 530. The RF front-end 530 may include circuitry for transmitting and receiving radio signals. For example, the RF front-end 530 may include a receiver circuit (RX) 532 and a transmitter circuit (TX) 534. In some embodiments, the receiver circuitry 532 may communicate with a downlink (DL) front-end 550, which may include circuitry for receiving radio signals via an antenna 335a.

[0157] Similarly, the second modem 520 may include one or more processors 522 and a memory 526 communicating with the processors 522. The modem 520 may communicate with an RF front-end 540. The RF front-end 540 may include circuitry for transmitting and receiving radio signals. For example, the RF front-end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some embodiments, the receiving circuitry 542 may communicate with a DL front-end 560, which may include circuitry for receiving radio signals via an antenna 335b.

[0158] In some implementations, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 336. Therefore, when cellular communication circuitry 352 receives an instruction to transmit according to a first RAT (e.g., supported by a first modem 510), switch 570 may be switched to a first state allowing the first modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 352 receives an instruction to transmit according to a second RAT (e.g., supported by a second modem 520), switch 570 may be switched to a second state allowing the second modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).

[0159] As described herein, the first modem 510 and / or the second modem 520 may include hardware and software components for implementing any of the various features and techniques described herein. For example, processors 512, 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or in addition), processors 512, 522 may be configured as programmable hardware elements, such as FPGAs (Field-Programmable Gate Arrays) or as ASICs (Application-Specific Integrated Circuits). Alternatively (or in addition), processors 512, 522 may be configured to implement some or all of the features described herein by combining with one or more of other components 530, 532, 534, 540, 542, 544, 550, 570, 572, 335, and 336.

[0160] Furthermore, as described herein, processors 512 and 522 may include one or more processing elements. Therefore, processors 512 and 522 may include one or more integrated circuits (ICs) configured to perform the functions of processors 512 and 522. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processors 512 and 522.

[0161] In some embodiments, the cellular communication circuit 352 may include only one transmit / receive chain. For example, the cellular communication circuit 352 may not include modem 520, RF front-end 540, DL front-end 560, and / or antenna 335b. As another example, the cellular communication circuit 352 may not include modem 510, RF front-end 530, DL front-end 550, and / or antenna 335a. In some embodiments, the cellular communication circuit 352 may also not include switch 570, and RF front-end 530 or RF front-end 540 may communicate with UL front-end 572, for example, through direct communication.

[0162] Configuration authorization

[0163] As previously mentioned, to prevent waste from periodically allocated resources, multiple devices can share periodic resources through configuration grants (CGs), which the base station uses to allocate configuration grant resources to multiple devices. By allocating these configuration grant resources, the network (e.g., via the base station) eliminates packet transmission delays in the scheduling request process while also improving the utilization of the allocated periodic radio resources. Currently, there are two types of CGs: Type 1 CG and Type 2 CG. For Type 1 CG, uplink grants are configured via RRC and stored as configured uplink grants. For Type 2 CG, uplink grants are configured via PDCCH (Addressed to CS-RNTI) and are stored or cleared as configured uplink grants based on Layer 1 signaling indicating activation or deactivation of the configured uplink grant. Multiple CG configurations can be configured in a single BWP of a serving cell, and multiple configurations can be activated simultaneously on different serving cells. For Type 2 CG, activation and deactivation can be independent between serving cells. For the same serving cell, a Media Access Control (MAC) entity can be configured with either Type 1 or Type 2 CGs.

[0164] The Information Elements (IEs) of a Garbage Controller (CG) include multiple parameters / parameter values ​​for configuring the CG. For example, the current implementation of the CG is described in the standard document 3GPP TS 38.331Rel-16 (38.331g10). Various embodiments disclosed herein propose including additional and / or modified parameters in the CG IE, and further propose additional and / or modified signaling for more efficient CG configuration, as will be described further below.

[0165] CG Uplink Control Information (CG-UCI) in Unlicensed NR Spectrum (NR-U)

[0166] The current implementation of CG-UCI in NR-U includes at least the following information:

[0167] • Hybrid Automatic Repeat Request (HARQ) identifier (ID);

[0168] • New Data Indicator (NDI);

[0169] • Redundant Version (RV); and

[0170] • Channel Occupancy Time (COT) sharing information.

[0171] Additional information, including UEID, will be considered for further research in future implementations.

[0172] CG-UCI is included in every CG-PUSCH transmission. To determine the number of REs used for CG-UCI, the β-offset mechanism used for HARQ-ACK on CG-PUSCH is being (re)used (e.g., when it appears in the 3GPP standard Rel-15 NR). New RRC parameters for configuring the β-offset of CG-UCI have been defined. Therefore, for UE-initiated COT sharing indications, when configuring the Energy Detection (ED) threshold, the Channel Access Priority Class (CAPC) value is also indicated in the CG-UCI. RRC configuration can be provided to the UE indicating whether CG-UCI and HARQ-ACK are multiplexed. When configured for multiplexing, CG-UCI and HARQ-ACK are jointly encoded (CG-UCI is considered to be of the same type as HARQ-ACK) in cases where the PUCCH overlaps with CG-PUSCH within the PUCCH group. When not configured for multiplexing, if the PUCCH overlaps with the CG-PUSCH in the PUCCH group and the PUCCH carries a HARQ ACK feedback, the configuration authorization PUSCH is skipped.

[0173] Autonomous Uplink UCI (AUL-UCI)

[0174] The immediate availability of UL time-frequency resources for transmitting new data is a key factor in reducing latency and improving UL throughput. This is especially important for unlicensed spectrum operations, where access to the channel may undergo a listen-before-tell (LBT) process, and scheduling UL transmissions with a previous DL transmission can be inefficient. For example, autonomous UL (AUL) transmissions in unlicensed spectrum allow UEs to perform UL transmissions without requiring prior scheduling requests or explicit scheduling authorizations from the network (e.g., from base stations such as gNBs).

[0175] The current implementation of AUL-UCI includes at least the following information:

[0176] · HARQ ID (4 bits);

[0177] · NDI (1 bit for TM1, 2 bits for TM2);

[0178] · RV (2 bits);

[0179] · UE ID (16 bits);

[0180] · PUSCH starting point (1 bit: indicating symbol 0 or 1);

[0181] · PUSCH ending point (1 bit: indicating symbol 12 or 13);

[0182] · COT sharing indication (1 bit: indicating whether subframe n+X is a subframe applicable to UL-to-DL sharing); X is configured by the base station as part of the AUL RRC configuration, and 1 < X < 5; if the UE indicates that the subframe is applicable to UL-to-DL COT sharing, the UE stops its AUL PUSCH transmission in the previous subframe at symbol #12, regardless of the RRC configuration of the PUSCH end symbol; and

[0183] · CRC (16 bits).

[0184] Potential problems caused by using CG

[0185] As currently defined (e.g., in Rel-16 NR of the 3GPP standard), multiple CGs are supported on a bandwidth part (BWP), and dynamic grant (DG) is still allowed to cover the CG timeline. If there are multiple UL traffic flows, such as video traffic for flow 1 and audio traffic for flow 2, different flows may have different arrival periodicities and different packet sizes, while still having very similar reliability requirements (e.g., a block error rate BLER of 10 for the first transmission -4 ). Therefore, when traffic arrivals from two flows occur in the same time slot, ideally, they will be combined and carried in the same PUSCH (e.g., for better time diversity, sharing DMRS overhead, and / or achieving better channel estimation with the same overhead, etc.). However, as shown, there is no suitable solution other than allocating another CG for the combined traffic, as Figure 6 shown. As Figure 6As shown, CG1, CG2, and CG3 all appear individually. Furthermore, since the base station (e.g., gNB) may not have complete information about the uplink traffic flow to properly configure each CG, some adaptations within the CGs may be useful, for example, actions taken autonomously and dynamically by the UE to optimally adapt to the current network traffic. Configuring many CGs can also lead to base station scheduling constraints because the Dynamic Grant (DG) timeline is still expected to cover the CG timeline. It should be noted that DG in this context refers to dynamic scheduling using scheduling requests as discussed previously.

[0186] Maximizing the autonomy that the UE can have in uplink transmissions can be beneficial, especially for unlicensed spectrum access. Using the DG (or Scheduling Request-SR Scheduling) paradigm, a UE performing a UL transmission typically requires three steps, each conditional on obtaining channel access from the transmitter or a transmitter sharing a COT obtained by another node. In the first step, the UE transmits an SR (or alternatively, the UE may send a Buffer Status Report, BSR) to the base station to indicate data arrival / status. In the second step, the base station transmits a PDCCH to the UE to schedule the uplink transmission. In the third step, the UE transmits UL data via a PUSCH. In contrast to the DG paradigm, with respect to CG, the UE does not need to perform the first two steps above to achieve the third step. As previously mentioned, the CG-UCI design, initially introduced in AUL-UCI and subsequently extended to NR-U, combines the benefits of both SR-based and SPS-based approaches. In one sense, CG-UCI can be viewed as the inverse of PDCCH, as it coordinates the receiving node to receive the information necessary to decode the transmitted transmission.

[0187] Enhanced CG

[0188] To further improve CG, the coverage area of ​​the UE's uplink transmission can be defined (at least partially) by the occupied transmission time, the occupied transmission frequency, and the transmission power. Therefore, the CG coverage area can be dynamically adjusted / selected by the UE within defined limits based on the UE's current traffic demands, and the UE can indicate the actual coverage area parameters / values ​​to the base station. In other words, the coverage area for the UE's uplink data transmission can be defined, and this coverage area can be selected / determined (or adjusted) by the UE within the limits of the coverage area previously signaled to the UE by the base station (e.g., gNB). It can also be adjusted / selected at least based on the UE's current traffic demands. The UE can signal the actual coverage area to the base station as part of CG uplink control information (CG-UCI) on resources configured at least according to UCI transmission parameters previously signaled to the UE by the base station.

[0189] Therefore, on the network side, the base station (e.g., gNB) can configure the maximum allowable coverage area by setting limits for corresponding parameters that at least partially define the coverage area. The base station can also indicate transmission parameters for configuring the resources on which the UE will transmit UCI. The UE can autonomously select parameter values ​​for uplink data (e.g., PUSCH) transmission based on a range / limit values ​​previously signaled by the base station, thus selecting practical values ​​at least in part based on the UE's current traffic demands. Parameter values ​​for PUSCH transmission can be carried in the UCI as a UCI payload. For example, if the UE selects certain parameters for PUSCH transmission, such parameters can be indicated to the base station in the UCI payload. In some embodiments, the baseline design may include fixed transmission parameters for UCI transmission, so the base station will not authorize different UCI transmissions for the current configuration. In some embodiments, as a further variation, the transmission parameters for UCI transmission can also be allowed to change. For example, the base station can indicate multiple sets of such parameters to the UE, and enable the UE to select one of these sets of parameters from said multiple sets. In this scenario, the base station can perform blind detection to identify ongoing UCI transmissions based on a selected set of parameters. Based on the above, and according to some implementation schemes, CG can be implemented as follows.

[0190] Base station configuration via RRC or via RRC and dynamic signaling

[0191] First, certain parameter sets can be signaled by the base station to the UE to establish (or configure) the CG. For Type 1 CG, all transmission parameters can be signaled via RRC signaling, while for Type 2 CG, some transmission parameters can be signaled via RRC signaling, and some transmission parameters can be signaled via dynamic signaling (i.e., in DCI). It should be noted that, for ease of understanding, only those parameters related to the aforementioned transmission coverage area, as implemented in the improved CG process, will be listed below. The base station may indicate additional parameters (not shown) to the UE as needed to configure the CG. The parameters explicitly shown herein include those used to allow the UE to select the uplink data transmission (e.g., PUSCH) transmission coverage area, as described above.

[0192] Based on the above, when configuring CG, the base station can notify the UE of the following parameter group via signal.

[0193] • Group A parameters: Used for uplink data transmission, such as the parameter range for PUSCH.

[0194] limit:

[0195] ο Maximum transmission duration (Dmax);

[0196] Maximum transmission power;

[0197] οMCS level range (e.g., defined by MCS level A and MCS level B); and

[0198] ο Maximum occupied frequency (e.g., by f) start and f end (Definition).

[0199] • Group B parameters: Transmission parameters used for UCI transmission:

[0200] ο Modulation order (or coding rate if the modulation scheme is fixed to QPSK);

[0201] o Time and frequency resources (RE); and

[0202] οDMRS configuration.

[0203] The UE can then autonomously select / choose / determine parameters as follows, while adhering to the range / restrictions included in Group A parameters received by the UE from the base station. The UE can transmit the following parameter group to the base station as part of the UCI (e.g., CG-UCI) transmitted by the UE to the base station.

[0204] • Group C parameters: Transmission parameters used for PUSH (different from UCI for uplink data):

[0205] ο Duration of each repetition of transmission (L);

[0206] Number of repetitions (K);

[0207] οMCS level (M); and

[0208] ο Occupied frequency (e.g., defined by f1 and f2).

[0209] Group C can be selected / determined by the UE at least in part based on the UE's current radio traffic requirements and according to Group A parameters received from the base station. The MCS level "M" can be selected such that MCS level A ≤ M ≤ MCS level B, the values ​​of "K" and "L" can be selected such that K*L ≤ Dmax, and finally, f1 and f2 can be selected such that f start ≤f1≤f2≤f endThe MCS level can represent the CG-UCI MCS level (or CG-UCI candidate MCS level) and can be considered as the counterpart to the PDCCH candidate. As mentioned above, multiple different sets of group B parameters can be indicated to the UE, whereby the UE selects one of these sets to configure resources for transmitting UCI on it, and the base station can perform blind decoding to detect UCI transmissions of interest, similar to blind decoding of PDCCH. Therefore, the above includes the resource allocation (time and frequency resources) of CG-UCI and the candidate positions of CG-UCI. As an example, in some implementations, the CG-UCI signaled to the base station by the UE may include the following parameters, wherein newly included group C parameters are indicated as applicable:

[0210] • HARQ ID (e.g., 4 digits);

[0211] • NDI;

[0212] •RV (e.g., 2 digits);

[0213] • MCS level (as part of the parameters in group C above);

[0214] • Time-domain resource indications (e.g., K, L, as part of the parameters in group C above);

[0215] • Frequency occupancy information (e.g., start symbol, number of PRBs, as part of the parameters in group C above);

[0216] • COT sharing indication of the PUSCH end symbol; and

[0217] • The CRC (XXX bits) masked by the UE ID.

[0218] In some implementations, CG-UCI can be carried in, for example... Figure 7 The diagram illustrates CG-UCI transmission for PUSCH repetition type B, located at a fixed candidate position indicated by the vertical arrow (e.g., the CG-UCI payload size and frequency / duration can be fixed, if present). For CG-UCI, the MCS level can be fixed. Where UCI transmission resources can be selected by the UE, the coverage area implementation described above can facilitate blind detection on the base station (e.g., gNB) side as needed. It can also allow multiple CG-UCI candidates with different coding rates, similar to PDCCHs with different aggregation levels. CG-UCI can have its own demodulation reference signal (DMRS) for base station decoding, independent of the DMRS of the PUSCH data (or data transmitted on / via the PUSCH).

[0219] TBS determines and adjusts MCS levels and {L,K}

[0220] The TBS size can be determined based on {MCS level, L, and the number of PRBs in the nominal repetition}, and one or more of these can be signaled to the base station. The permissible MCS levels do not need to span the entire range supported in the NR; for example, the base station can configure several permissible MCS levels, or a range around the signaled / configured MCS level (as indicated above regarding the MCS increment range for Group A parameters). As an example, for Type 2 CG, if MCS = 5 is signaled to the UE along with MCS increment range 2, the UE can select from the following MCS levels: 3, 4, 5, 6, 7 (3, 4 and 6, 7 are all within increment range 2 of the signaled value 5).

[0221] For PUSCH repetition type B, L (the number of OFDM symbols in the nominal repetition) can be a factor in determining TBS. By making L adjustable, the UE can configure the current transmission according to traffic requirements, such as carrying packets of audio and video streams in a single PUSCH. Similarly, for video codecs, the payload of the reference frame can be set to be different from the payload of the residual frames of the video stream.

[0222] For PUSCH repetition type B, the base station can also configure a maximum duration Dmax for the CG transmission bundle. As long as K×L <= Dmax (e.g., constrained within the maximum allowable coverage area), the UE is free to choose L (for a single TX) and K (repetition factor).

[0223] Frequency occupancy and UCI / data multiplexing

[0224] The starting PRB and the number of PRBs in the PUSCH transmission can be notified by the UE using signals. To reduce signaling overhead, the starting PRB can be constrained to be the same as the lowest PRB corresponding to the CG-UCI.

[0225] For CP-OFDM (Cyclic Prefix OFDM), for rank 1 transmissions, it can be assumed that the number of PRBs occupied by CG-UCI is different from the number of PRBs occupied by PUSCH, where the remaining REs on symbols with CG-UCI fill the PUSCH. For rank 2 or higher transmissions, the same CG-UCI can be applied to each spatial layer, and precoding can be implemented by the UE. Figure 8 An example of CP-OFDM is provided (802).

[0226] In the case of DFT-S-OFDM, to avoid time-varying TX power levels, it may be preferable to have a residual PUSCH after CG-UCI. Figure 8 An example of DFT-S-OFDM is provided (804).

[0227] like Figure 8 As shown, the new CG-UCI can occupy orthogonal resources regarding PUSCH RE, therefore the UCI multiplexing rules can also be changed, for example, similar to the changes made to the two-level SCI (sidelink control information) design in V2X. In this sense, CG-UCI can be considered to play a role similar to that of Phase 1 SCI.

[0228] UCI / data multiplexing for different repetitions

[0229] In the current NR-U design, the CG-UCI is carried in each PUSCH transmission, which is a reasonable design considering that the transmission duration remains unchanged. In contrast, according to the various embodiments disclosed herein, since L can be adjusted and the CG-UCI can exist in a fixed position, the CG-UCI can exist in some repetitions but not in others, for example, as... Figure 9 As shown.

[0230] Power control

[0231] Power control can be determined based on {MCS level and the number of PRBs in the nominal repetition}. As a baseline solution, the UE can select the MCS level for PUSCH transmission and adjust the transmission power accordingly. More granular solutions are also possible and conceivable. The base station can define a maximum power level, which can be provided as an absolute limit, e.g., in dBm, or it can be a relative power margin, e.g., in dB. The UE can operate such that it does not exceed the power margin / absolute limit. In some implementations, the limit can be provided as a limit on the total transmission power or a limit on PSD. In unlicensed spectrum, PSD limits may exist due to regulatory requirements, and the base station can implement PSD limits to ensure that inter-cell interference is not too severe.

[0232] Configure CG in UE

[0233] Figure 10A flowchart illustrating an exemplary method for implementing CG in a mobile device according to some embodiments is shown. As shown in 1002, the device may receive from a base station a first set of values ​​corresponding to a first set of transmission parameters (e.g., transmission parameters for PUSCH transmission of the device) for at least partially configuring resources for uplink data transmission of the device, and may also receive from the base station a second set of values ​​corresponding to a second set of transmission parameters (e.g., transmission parameters for UCI transmission of the device) for at least partially configuring resources for uplink control information transmission of the device. In 1004, the device may determine a third set of values ​​corresponding to the first set of transmission parameters based at least on the device's current radio traffic requirements and the first set of values. In 1006, the device may transmit uplink control information including at least the third set of values ​​to the base station on resources configured using at least the second set of values. In 1008, the device may transmit uplink data to the base station on resources configured using at least the third set of values.

[0234] CG configured by base station

[0235] Figure 11 A flowchart illustrating an exemplary method for implementing a CG (Cyclic Context) by a base station according to some embodiments is shown. As shown in 1102, the base station may transmit configuration parameters / values ​​to the device as part of configuring the CG of the device. Therefore, the base station may correspondingly transmit a first set of values ​​corresponding to a first set of transmission parameters (e.g., transmission parameters for the device's PUSCH transmission) used to at least partially configure resources for uplink data transmission of the device, and may also transmit to the device a second set of values ​​corresponding to a second set of transmission parameters (e.g., transmission parameters for the device's UCI transmission) used to at least partially configure resources for uplink control information transmission of the device. In 1104, the base station may receive uplink control information from the device on resources configured using at least the second set of values, wherein the uplink control information includes at least a third set of values ​​corresponding to the first transmission parameters and is determined by the device at least based on the device's current radio traffic requirements and the first set of values. In 1106, the base station may receive uplink data from the device on resources configured using at least the third set of values.

[0236] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0237] Embodiments of the present invention can be implemented in any of a variety of forms. For example, in some embodiments, the invention can be implemented as a computer-implemented method, a computer-readable storage medium, or a computer system. In other embodiments, the invention can be implemented using one or more custom-designed hardware devices such as ASICs. In still other embodiments, the invention can be implemented using one or more programmable hardware elements such as FPGAs.

[0238] In some embodiments, a non-transitory computer-readable storage medium (e.g., a non-transitory memory element) may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system performs a method, such as any of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any method embodiments described herein, or any combination of such subsets.

[0239] In some embodiments, a device (e.g., a UE) may be configured to include a processor (or a set of processors) and a memory medium (or memory elements), wherein the memory medium stores program instructions, and wherein the processor is configured to read from and execute the program instructions, wherein the program instructions are executable to implement any of the various method embodiments described herein (or any combination of the method embodiments described herein, or any subset or any combination of such subsets of any method embodiments described herein). The device may be implemented in any of a variety of forms.

[0240] By interpreting each message / signal X received by a user equipment (UE) or device in the downlink as a message / signal X transmitted by a base station / network node, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by a base station / network node, any method described herein for operating a UE can serve as the basis for a corresponding method for operating the base station or appropriate network node.

[0241] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. A baseband processor configured to perform operations including: Receives a value limit from the base station for limiting a value corresponding to a first transmission parameter, the first transmission parameter being used to at least partially configure resources for uplink data transmission of the device, wherein the value limit includes a maximum transmission duration Dmax for the uplink data transmission; The device receives a first set of values ​​corresponding to a second transmission parameter from the base station, the second transmission parameter being used to at least partially configure resources for uplink control information transmission of the device. A second set of values ​​corresponding to the first transmission parameter is determined within the value limit, at least based on the current wireless traffic requirements of the device and the value limit, wherein the second set of values ​​includes values ​​for the transmission duration L and the number of repetitions K for each repetition, which are determined such that K * L ≤ Dmax; Uplink control information, including at least the second set of values, is transmitted to the base station on resources configured using at least the first set of values. as well as Uplink data transmission is carried out using Transport Block Size (TBS), where: (1) The TBS is determined at least based on the transmission duration L, the modulation and coding scheme MCS level, and the number of physical resource blocks (PRBs) in the nominal repetition; or (2) For Physical Uplink Shared Channel (PUSCH) repetition type B, the TBS is determined at least based on the transmission duration L.

2. The baseband processor of claim 1, wherein the baseband processor is configured to perform additional operations including: Uplink data is transmitted to the base station using resources configured with at least the second set of values.

3. The baseband processor of claim 1, wherein the value limitation includes a corresponding limitation for limiting the corresponding value of each of the first transmission parameters.

4. The baseband processor of claim 1, wherein the value limit and the first set of values ​​are received as part of configuration information for configuration authorization.

5. The baseband processor of claim 1, wherein the second set of values ​​further includes values ​​for one or more of the following: Modulation coding scheme level; Frequency occupied; or Cyclic redundancy check bits masked by the device.

6. The baseband processor of claim 1, wherein the value limitation further includes one or more of the following: Maximum transmission power; Modulation coding scheme level range; or Maximum frequency of use.

7. The baseband processor according to claim 1, wherein the second transmission parameter includes one or more of the following: Modulation sequence; Encoding rate; Time and frequency resource elements; or Demodulation reference signal configuration.

8. A device for wireless communication, the device comprising: A radio circuit configured to facilitate wireless communication of the device; as well as A processor, communicatively coupled to the radio circuit and configured to perform operations including: Receives a value limit from the base station for limiting a value corresponding to a first transmission parameter, the first transmission parameter being used to at least partially configure resources for uplink data transmission of the device, wherein the value limit includes a maximum transmission duration Dmax for the uplink data transmission; The device receives a first set of values ​​corresponding to a second transmission parameter from the base station, the second transmission parameter being used to at least partially configure resources for uplink control information transmission of the device. A second set of values ​​corresponding to the first transmission parameter is determined within the value limit, at least based on the current wireless traffic requirements of the device and the value limit, wherein the second set of values ​​includes values ​​for the transmission duration L and the number of repetitions K for each repetition, which are determined such that K * L ≤ Dmax; Uplink control information, including at least the second set of values, is transmitted to the base station on resources configured using at least the first set of values. as well as Uplink data transmission is carried out using Transport Block Size (TBS), where: (1) The TBS is determined at least based on the transmission duration L, the modulation and coding scheme MCS level, and the number of physical resource blocks (PRBs) in the nominal repetition; or (2) For Physical Uplink Shared Channel (PUSCH) repetition type B, the TBS is determined at least based on the transmission duration L.

9. The device of claim 8, wherein the processor is configured to perform additional operations including: Uplink data is transmitted to the base station using resources configured with at least the second set of values.

10. The device of claim 8, wherein the value limitation includes a corresponding limitation for limiting the corresponding value of each of the first transmission parameters.

11. The device of claim 8, wherein the value limit and the first set of values ​​are received as part of configuration information for configuration authorization.

12. The device of claim 8, wherein the second set of values ​​further includes values ​​for one or more of the following: Modulation coding scheme level; Frequency occupied; or Cyclic redundancy check bits masked by the device.

13. The device of claim 8, wherein the value limitation further includes one or more of the following: Maximum transmission power; Modulation coding scheme level range; or Maximum frequency of use.

14. The device of claim 8, wherein the second transmission parameter includes one or more of the following: Modulation sequence; Encoding rate; Time and frequency resource elements; or Demodulation reference signal configuration.

15. A non-transitory memory element for storing instructions, said instructions being executable by a processor to perform operations including: Receives a value limit from the base station for limiting a value corresponding to a first transmission parameter, the first transmission parameter being used to at least partially configure resources for uplink data transmission of the device, wherein the value limit includes a maximum transmission duration Dmax for the uplink data transmission; The device receives a first set of values ​​corresponding to a second transmission parameter from the base station, the second transmission parameter being used to at least partially configure resources for uplink control information transmission of the device. A second set of values ​​corresponding to the first transmission parameter is determined within the value limit, at least based on the current wireless traffic requirements of the device and the value limit, wherein the second set of values ​​includes values ​​for the transmission duration L and the number of repetitions K for each repetition, which are determined such that K * L ≤ Dmax; Uplink control information, including at least the second set of values, is transmitted to the base station on resources configured using at least the first set of values. as well as Uplink data transmission is carried out using Transport Block Size (TBS), where: (1) The TBS is determined at least based on the transmission duration L, the modulation and coding scheme MCS level, and the number of physical resource blocks (PRBs) in the nominal repetition; or (2) For Physical Uplink Shared Channel (PUSCH) repetition type B, the TBS is determined at least based on the transmission duration L.

16. The non-transitory memory element of claim 15, wherein the instructions are executable by the processor to perform additional operations including: Uplink data is transmitted to the base station using resources configured with at least the second set of values.

17. The non-transitory memory element of claim 15, wherein the value limit and the first set of values ​​are received as part of configuration information for configuration authorization; and The value restrictions include corresponding restrictions for limiting the corresponding values ​​of each parameter in the first transmission parameters.

18. The non-transitory memory element of claim 15, wherein the second set of values ​​further includes values ​​for one or more of the following: Modulation coding scheme level; Frequency occupied; or Cyclic redundancy check bits masked by the device.

19. The non-transitory memory element of claim 18, wherein the value limitation further includes one or more of the following: Maximum transmission power; Modulation coding scheme level range; or Maximum frequency of use.

20. The non-transitory memory element of claim 15, wherein the second transfer parameter includes one or more of the following: Modulation sequence; Encoding rate; Time and frequency resource elements; or Demodulation reference signal configuration.

Images