Channel access method
By setting multiple configuration authorization physical uplink shared channel timings within the configuration authorization period and allowing user devices to report unused resources, the problem of inconsistent data packet frame sizes in video applications in XR services is solved, improving resource utilization efficiency and system capacity.
Patent Information
- Application Number
- CN202480022159.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-03-31
- Filing Date
- 2024-03-29
- Publication Date
- 2025-11-11
AI Technical Summary
During uplink transmission, the video application data packets of XR services vary in size and fluctuate greatly. The existing resource configuration within a single configuration authorization period cannot fully represent the characteristics of the data packets, resulting in over-configuration or under-utilization of resources, which affects system capacity and efficiency.
Multiple configuration authorization physical uplink shared channel opportunities can be set within the configuration authorization period, and user devices can be allowed to report unused opportunities to the base station. The base station can then reallocate these resources to optimize resource utilization.
By configuring multiple authorized physical uplink shared channel timings, resource utilization efficiency is optimized, blind decoding burden is reduced, base station power consumption is saved, and system capacity and resource utilization are improved.
Smart Images

Figure CN120937465A_ABST
Abstract
Description
Invention Field
[0001] This invention relates to the field of communication systems, and more specifically, to a channel access method. 2. Related Technologies
[0002] A report titled TR 38.838 from the 3rd Generation Partnership Project (3GPP) examined how to evaluate Extended Reality (XR) services over 5G New Radio (NR). According to the study, XR services include downlink (DL) / uplink (UL) video application packets, downlink audio application packets, and uplink attitude / control application packets. These different data streams have different traffic characteristics, such as arrival time, bit rate, periodicity or jitter, and different latency requirements in terms of Packet Delay Budget (PDB).
[0003] In the context of XR uplink transmission, particularly for uplink attitude / control application packets, the traffic patterns of these packets are regular and the packet sizes are uniform. Therefore, low-latency transmission using the existing Configured Grant Physical Uplink Shared Channel (CG PUSCH) is feasible without any additional improvements.
[0004] Conversely, when processing uplink video application packets, frames can be large and vary in size. Since XR services require low latency, such as 10 milliseconds (ms), 15 milliseconds (ms), or 30 milliseconds (ms), the Dynamic Grant (DG) process is unsuitable due to the time-consuming sequence of sending a Scheduling Request (SR) / Buffer Status Report (BSR) from the User Equipment (UE) and subsequent uplink grants (UL grants) from the base station (gNodeB, gNB). Alternatively, utilizing Configuration Grant Resources (CG Resources) to transmit uplink video application packets can reduce latency and avoid downlink control information (DCI) overhead. To effectively manage the variability in packet size, a flexible approach to CG Resource usage is recommended. Implementing multiple CG grant physical uplink shared channel (CG PUSCH) transmissions within a single CG Period appears to be an effective strategy to support packets of varying sizes. Technical issues
[0005] In the uplink (UL), the video encoder on the user equipment side is responsible for generating video frames of varying sizes (such as I-frames and P / B frames) at a predetermined frame rate. Each data packet is processed within a strict packet delay budget (PDB).
[0006] Compared to Ultra-Reliable Low-Latency Communication (URLLC) services, XR services exhibit larger and more unpredictable packet sizes. A single configuration license resource configuration within a single configuration license period cannot adequately represent the characteristics of XR packets. Therefore, a method supporting multiple configuration license physical uplink shared channel (PUSCH) transmission occasions within a single configuration license period (referred to as Multiple-CG-PUSCH-Occasions Configuration) is essential.
[0007] In a single configuration grant period, multiple configuration grants are used for physical uplink shared channel timing configuration. Based on the XR traffic mode, some configuration grant resources may be over-configured or underutilized. Therefore, a mechanism that allows the user equipment to communicate with the base station to inform it of unused configuration grant resources is crucial for improving resource utilization efficiency and overall system capacity. Summary of the Invention
[0009] One objective of this invention is to provide a base station and channel access method.
[0010] In a first aspect, embodiments of the present invention provide a channel access method performed by a user equipment, comprising: The configuration for acquiring multiple Physical Uplink Shared Channel (PUSCH) opportunities is used to perform PUSCH transmission within the configuration grant period of the Configuration Grant (CG) configuration, wherein the configuration grant configuration includes information for reporting unused PUSCH opportunity indications within the configuration grant period, and the unused PUSCH opportunity indication information is used for PUSCH transmission; The Hybrid Automatic Repeat Request (HARQ) process identifier (ID) determines the effective physical uplink shared channel timing within the configuration authorization period; On a non-unused first valid physical uplink shared channel opportunity, first uplink control information (UCI) is transmitted in the physical uplink shared channel, wherein the first valid physical uplink shared channel opportunity is associated with a determined hybrid automatic repeat request process identifier, and the first uplink control information includes an indication of a first set of unused physical uplink shared channel opportunities.
[0011] In a second aspect, embodiments of the present invention provide a user equipment, including: a processor configured to invoke and run a computer program stored in a memory, such that a device having the chip mounted performs the method of the disclosed invention and any combination of embodiments of the method of the disclosed invention. In a third aspect, embodiments of the present invention provide a channel access method executable in a base station, including: A configuration for transmitting multiple physical uplink shared channel opportunities, used for physical uplink shared channel transmission within a configuration authorization period of a configuration authorization configuration, wherein the configuration authorization configuration includes information for reporting physical uplink shared channel opportunity indications that are not used within the configuration authorization period, and the information on unused physical uplink shared channel opportunity indications is used for physical uplink shared channel transmission; On a non-unused first valid physical uplink shared channel opportunity, first uplink control information is received in the physical uplink shared channel, wherein the first valid physical uplink shared channel opportunity is associated with a determined hybrid automatic repeat request process identifier, and the first uplink control information includes an indication of a first set of unused physical uplink shared channel opportunities.
[0012] In a fourth aspect, embodiments of the present invention provide a base station, including: a processor configured to invoke and run a computer program stored in a memory to cause a device equipped with the processor to perform the method of the disclosed invention.
[0013] The disclosed method can be programmed as computer-executable instructions stored in a non-transient computer-readable medium. When loaded into a computer, the non-transient computer-readable medium instructs the computer's processor to execute the disclosed method.
[0014] The non-transient computer-readable medium may include at least one of the following: hard disk, read-only optical disk (CD-ROM), optical storage device, magnetic storage device, read-only memory, programmable read-only memory, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory, and flash memory.
[0015] The method of the disclosed invention can be programmed into a computer program product, causing a computer to execute the method of the disclosed invention.
[0016] The method of the disclosed invention can be programmed into a computer program, causing a computer to execute the method of the disclosed invention. Beneficial effects
[0017] Some embodiments of the present invention introduce parameters and a framework for setting multiple configuration grant physical uplink shared channel timings within a single configuration grant cycle.
[0018] Some embodiments of the present invention have developed content and protocols for transmitting signaling to the base station to inform it of the timing when a configured authorized physical uplink shared channel is not being used.
[0019] The embodiments of the disclosed invention can provide the following advantages:
[0020] The optimized configuration authorization settings allow for setting multiple configuration authorization physical uplink shared channel timings within the configuration authorization period, which can better support uplink data transmission with diverse traffic patterns and variable payload sizes.
[0021] Furthermore, the configuration eliminates the additional latency and overhead caused by the need to reconfigure the configuration authorization scheduler or by the scheduling request / buffer status reporter required for dynamic authorization scheduler.
[0022] Since over-configured configuration grant resources can be reallocated to other user equipment, the ability to indicate to the base station when unused configuration grant physical uplink shared channels can enhance system capacity and resource efficiency.
[0023] The method disclosed herein reduces the burden of blind decoding on unused configuration-granted physical uplink shared channel resources, thereby saving power consumption of the base station.
[0024] By fine-tuning the parameters of the configured authorized physical uplink shared channel by the base station, resource allocation that is consistent with the uplink traffic of the user equipment can be improved, and the need for the user equipment to continuously report the timing of unused configured authorized physical uplink shared channels can be reduced. Attached Figure Description
[0025] To more clearly illustrate the embodiments or related technologies of the disclosed invention, the following figures will be briefly described in the embodiments. Obviously, the figures are only some embodiments of the present invention, and those skilled in the art can obtain other figures based on these figures without prior knowledge.
[0026] Figure 1 A schematic diagram of a telecommunications system is shown.
[0027] Figure 2 A schematic diagram illustrating one embodiment of the disclosed inventive method is shown.
[0028] Figure 3 An example of multiple transport blocks (TBs) transmission based on type A repeated transmission is illustrated, including multiple non-contiguous configuration-granted physical uplink shared channel (CG PUSCH) timings.
[0029] Figure 4 An example of multiple transport block transmission based on type B repetition is illustrated, where the nominal physical uplink shared channel (PUSCH) timing spans the slot boundary.
[0030] Figure 5 An example of a Hybrid Automatic Repeat Request Identifier (HARQ ID) indication is shown schematically.
[0031] Figure 6 This diagram schematically illustrates the mapping between the bitmap and the configuration of 15 or 30 kHz subcarrier spacing (SCS) to authorize the physical uplink shared channel timing.
[0032] Figure 7 An example of a cross-configuration licensing cycle indication is shown schematically.
[0033] Figure 8 An example of reusing unused configuration-authorized physical uplink shared channel timing mode is illustrated.
[0034] Figure 9 This diagram illustrates two offsets of two configuration authorization cycles.
[0035] Figure 10 The diagram illustrates the operation between a base station and two user equipment.
[0036] Figure 11 A schematic diagram of the user equipment is shown.
[0037] Figure 12 A schematic diagram of network nodes is shown.
[0038] Figure 13 A schematic diagram of a chip performing the disclosed method in a user equipment is shown.
[0039] Figure 14 A schematic diagram of a chip performing the disclosed method in a network node is shown.
[0040] Figure 15 A schematic diagram of a wireless communication system according to an embodiment of the present disclosure is shown. Detailed Implementation
[0041] The embodiments of the disclosed invention are described in detail below with reference to the accompanying drawings, including the technical aspects, structural features, implementation objectives, and effects. Specifically, the terminology used in the embodiments of the disclosed invention is for the purpose of describing the particular embodiment only and does not limit the scope of this disclosure.
[0042] Supporting multiple configuration-authorized physical uplink shared channel transmission opportunities within a configuration authorization period is beneficial for handling the larger packet sizes of uplink video application data packets, thereby increasing the number of Protocol Data Units (PDUs) required to transmit the video data packets. To enhance Extended Reality (XR) capacity and resource utilization efficiency, it is crucial to avoid maintaining static or excessive configuration-authorized resources due to changes in packet size. An adaptive mechanism can be implemented, allowing user equipment to dynamically signal to the base station any unused configuration-authorized opportunities or resources within the configuration-authorized physical uplink shared channel. Once the base station confirms these unused resources, it can reallocate and reschedule them for use by other user equipment, thereby optimizing resource efficiency.
[0043] Embodiments of this disclosure provide perspectives and strategies regarding enhancements to specific Extended Reality (EPR) scenarios. These enhancements are designed to support the setting of multiple configuration-granted physical uplink shared channel (PHS) transmission opportunities within a configuration grant period and to enable the user equipment (UE) to signal unused PHS ...
[0044] In this description, unless otherwise specified, the term "slot" can be interpreted as a time slot, sub-slot, time slot location, or sub-slot location. Unless otherwise specified, the term "resource"... (Resource) can be interpreted as one or more wireless resources in the time domain and frequency domain.
[0045] refer to Figure 1 The telecommunications system includes user equipment 10a, user equipment 10b, base station (BS) 20a, and network entity equipment 30, and performs the method of the disclosed invention according to embodiments of the present invention. Figure 1For illustrative purposes only and not as a limitation, the system may include further user equipment, base stations, and core network (CN) entities. Connections between devices and device components are indicated by lines and arrows in the figures. User equipment 10a may include processor 11a, memory 12a, and transceiver 13a. User equipment 10b may include processor 11b, memory 12b, and transceiver 13b. Base station 20a may include processor 21a, memory 22a, and transceiver 23a. Network entity device 30 may include processor 31, memory 32, and transceiver 33. Each of processors 11a, 11b, 21a, and 31 may be configured to implement the functions, processes, and / or methods presented in this description. Layers of the wireless interface protocol may be implemented in processors 11a, 11b, 21a, and 31. Each of memories 12a, 12b, 22a, and 32 operatively stores various programs and information to operate the connected processor. Each of the transceivers 13a, 13b, 23a, and 33 is operatively coupled to a connected processor and transmits and / or receives wireless or wired signals. User equipment 10a communicates with user equipment 10b via a sidelink. Base station 20a may be an evolved Node B (eNodeB, eNB), a base station (gNB), or another type of wireless node, and may configure wireless resources for user equipment 10a and user equipment 10b.
[0046] Each of the processors 11a, 11b, 21a, and 31 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits, and / or data processing devices. Each of the memories 12a, 12b, 22a, and 32 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and / or other storage devices. Each of the transceivers 13a, 13b, 23a, and 33 may include baseband circuitry and radio frequency (RF) circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented using modules, processes, functions, entities, etc., that perform the functions described herein. The modules may be stored in memory and executed by the processor. The memory may be implemented internally to the processor or external to the processor; in the latter case, it may be communicatively coupled to the processor in various ways known in the art.
[0047] The network entity device 30 may be a node in the core network. The core network may include a Long Term Evolution (LTE) core network or a 5G Core (5GC), which includes User Plane Function (UPF), Session Management Function (SMF), Mobility Management Function (AMF), Unified Data Management (UDM), Policy Control Function (PCF), Control Plane (CP) / User Plane (UP) Separation (CUPS), Authentication Server (AUSF), Network Slice Selection Function (NSSF), and Network Exposure Function (NEF).
[0048] Examples of user equipment described in this description may include one of user equipment 10a or user equipment 10b. Examples of base stations described in this description may include base station 20a. Sidelink (SL) transmission control signals or data may be transmission operations from one user equipment to another. Uplink (UL) transmission control signals or data may be transmission operations from a user equipment to a base station. Downlink (DL) transmission control signals or data may be transmission operations from a base station to a user equipment. Downlink control signals may include Medium Access Control (MAC) control elements (CE), Downlink Control Information (DCI), or Radio Resource Control (RRC) signals from the base station to the user equipment.
[0049] refer to Figure 2 An embodiment of the channel access method in which a base station (e.g., base station 20a) and user equipment (e.g., user equipment 10a or user equipment 10b) perform the channel access method.
[0050] Step S011: The base station 20a transmits a configuration of multiple Physical Uplink Shared Channel (PUSCH) timings for transmitting PUSCH within the configuration grant period of the configuration grant (CG) configuration. The configuration grant configuration includes information for reporting unused PUSCH timing indications within the configuration grant period; this unused PUSCH timing indication information is used for PUSCH transmission. The user equipment 10a acquires the configuration of the multiple PUSCH timings.
[0051] In some embodiments of the present invention, the user equipment 10a may determine the Hybrid Automatic Repeat Request (HARQ) process identifier (ID) for the effective physical uplink shared channel timing within the configuration grant period.
[0052] Step S012: The user equipment 10a transmits first uplink control information (UCI) in the physical uplink shared channel during a non-unused first valid physical uplink shared channel opportunity. The base station 20a receives the first uplink control information during the first valid physical uplink shared channel opportunity in the physical uplink shared channel. The first valid physical uplink shared channel opportunity is associated with a determined Hybrid Automatic Repeat Request (HARQ) procedure identifier. The first uplink control information includes an indication of a first set of unused physical uplink shared channel opportunities.
[0053] In some embodiments of the present invention, the configuration of multiple physical uplink shared channel timings within the configuration grant period includes the number of consecutive time slots within the configuration grant period.
[0054] In some embodiments of the present invention, each of the consecutive time slots includes one or more physical uplink shared channel opportunities, each of the plurality of physical uplink shared channel opportunities within the configuration grant period is associated with a transport block (TB), and different physical uplink shared channel opportunities are associated with different transport blocks.
[0055] In some embodiments of the present invention, the symbol positions of the physical uplink shared channel timing are the same for each time slot in the consecutive time slots.
[0056] In some embodiments of the present invention, the symbol position is determined based on time-domain resource allocation based on the Start and Length Indicator Value (SLIV).
[0057] In some embodiments of the present invention, the configuration authorization configuration is a type 1 configuration authorization configuration, and the start and length indication values SLIV are derived from Radio Resource Control (RRC) signaling. In some embodiments of the present invention, the configuration authorization configuration is a type 2 configuration authorization configuration, and the start and length indication values SLIV are derived from indications in Activation Downlink Control Information (Activation DCI).
[0058] In some embodiments of the present invention, the effective physical uplink shared channel timing is any physical uplink shared channel timing that does not overlap with a downlink symbol or synchronization signal block (SSB) within a time slot.
[0059] In some embodiments of the present invention, the information for reporting unused physical uplink shared channel timings includes the bit length of a bitmap generated by the user equipment to indicate a first set of unused physical uplink shared channel timings.
[0060] In some embodiments of the present invention, each bit of the bitmap indicates whether the physical uplink shared channel opportunity represented by the bit is unused among the plurality of physical uplink shared channel opportunities.
[0061] In some embodiments of the present invention, each bit of the bitmap is associated with a valid physical uplink shared channel timing among the plurality of physical uplink shared channel timings.
[0062] In some embodiments of the present invention, each bit of the bitmap is associated with a time slot within the configuration authorization period.
[0063] In some embodiments of the present invention, the initial bit indication of the bitmap follows the physical uplink shared channel timing immediately after the physical uplink shared channel timing for transmitting uplink control information carrying the bitmap.
[0064] In some embodiments of the present invention, the initial bit of the bitmap represents a physical uplink shared channel timing located at an offset after the physical uplink shared channel timing for transmitting uplink control information carrying the bitmap, the value or range of which is pre-configured or pre-defined by the user equipment.
[0065] In some embodiments of the present invention, the last bit of the bitmap indicates a physical uplink shared channel timing within the same configuration grant period as the physical uplink shared channel timing used to transmit uplink control information carrying the bitmap.
[0066] In some embodiments of the present invention, the last bit of the bitmap indicates a physical uplink shared channel opportunity within a different configuration grant period than the configuration grant period that transmits uplink control information of the bitmap carrying an opportunity where the physical uplink shared channel is not used.
[0067] In some embodiments of the present invention, the user equipment further determines a second set of unused physical uplink shared channel opportunities according to the configuration authorization configuration, and the user equipment transmits second uplink control information in the physical uplink shared channel on a non-unused second valid physical uplink shared channel opportunity, wherein the second uplink control information is used to carry a bitmap of the second set of unused physical uplink shared channel opportunities, the second valid physical uplink shared channel opportunity is associated with a second hybrid automatic repeat request process identifier, the position of the second valid physical uplink shared channel opportunity is later than the first valid physical uplink shared channel opportunity, and at least one valid physical uplink shared channel opportunity indicated by the bitmap of the first set of unused physical uplink shared channel opportunities is the same as at least one valid physical uplink shared channel opportunity indicated by the bitmap of the second set of unused physical uplink shared channel opportunities.
[0068] In some embodiments of the present invention, for both the first group of bitmaps indicating unused physical uplink shared channel (PHS) opportunities and the second group of bitmaps indicating unused PHS opportunities, the usage status of the effective PHS opportunities indicated by the bitmaps of the second group of unused PHS opportunities is used to cover the usage status indicated by the bitmaps of the first group of unused PHS opportunities.
[0069] In some embodiments of the present invention, the first valid physical uplink shared channel timing for transmitting the first uplink control information and the second valid physical uplink shared channel timing for transmitting the second uplink control information belong to different configuration license periods.
[0070] Example 1: Timing for configuring multiple configuration-granted physical uplink shared channels within a configuration grant period:
[0071] Example 1-1: Configuration grant parameters supporting multiple configuration grant physical uplink shared channel timings within a configuration grant period:
[0072] In one embodiment, the gNB base station (e.g., base station 20a) can provide user equipment (e.g., user equipment 10) with at least one of the following higher-layer parameters or similar parameters via dedicated Radio Resource Control (RRC) signaling to configure multiple Configuration Grant Physical Uplink Shared Channel (CG PUSCH) Occasions (referred to as Multiple-CG-PUSCH-Occasions Configuration): 1. Configure authorization type = 'Multiple CG PUSCH occasions'. 2. Supports multiple configuration authorization physical uplink shared channel timings, including the index or identifier (ID) of the configuration authorization.
[0073] The base station can be configured with multiple sets of configuration authorization configurations that support multiple configuration authorization physical uplink shared channel timings. The number of configuration authorization configurations that support multiple configuration authorization physical uplink shared channel timings is limited by the total number of configuration authorization configurations supported by the user equipment. 3. Parameters for the configuration authorization configuration used to jointly release the timing of multiple configuration authorization physical uplink shared channel.
[0074] The joint release is a release operation that releases the configuration authorization configurations of all multi-configuration authorized physical uplink shared channel timings in batches.
[0075] The downlink control information (DCI) format for the activation or release downlink control information (DCI) of the configuration authorization configuration for multiple configuration authorized physical uplink shared channel timing may include DCI format 0-1, 0-1, or 0-2. The activation downlink control information activates the configuration authorization configuration for multiple configuration authorized physical uplink shared channel timing, while the release downlink control information releases the configuration authorization configuration for multiple configuration authorized physical uplink shared channel timing. The base station may set priorities corresponding to the configuration authorization configuration for multiple configuration authorized physical uplink shared channel timing. 4. Configure the number of Transport Blocks (TBs) within the license period.
[0076] The base station can be configured to map a transport block to a single configured authorized physical uplink shared channel timing or multiple configured authorized physical uplink shared channel timings.
[0077] The base station can be configured to map each transport block in multiple transport block groups to one or more Physical Uplink Shared Channel (PUSCH) timings.
[0078] The base station can be configured to map a retransmission of a transport block to a portion of the configured authorized physical uplink shared channel timing within the configured authorization period. 5. The number of times multiple configuration authorization physical uplink shared channel opportunities are available within the configuration authorization period.
[0079] The periodicity of the configuration grant period can be associated with the value (or numerical index) of the subcarrier spacing (SCS) associated with the uplink bandwidth part (BWP).
[0080] The maximum number of configuration grant physical uplink shared channel moments associated with a configuration grant configuration depends on one or more of the following factors: (1) Configure the authorization period; (2). Subcarrier spacing; (3) User equipment capabilities.
[0081] The minimum number of the plurality of configuration grant physical uplink shared channel opportunities associated with the configuration grant configuration can be one, regardless of the configuration grant period or subcarrier spacing. 6. The time domain location of multiple configuration grant physical uplink shared channel opportunities within the configuration grant period can be determined based on at least one of the following parameters: (1) Periodicity of configuring authorization settings; (2). Subcarrier spacing in the relevant bandwidth portion; (3). The index of the System Frame Number (SFN); (4). Time offset relative to system frame number SFN=0 or system frame number SFN=512; (5) Start and Length Indicator Value (SLIV) of the corresponding time slot associated with the timing of configuring the authorized physical uplink shared channel; i. One or more start and length indication values SLIV may be associated with multiple configuration grant physical uplink shared channel timings within a configuration grant period. ii. If multiple start and length indication values SLIV are configured to map to multiple configuration-granted physical uplink shared channel timings, then each of the multiple start and length indication values SLIV may be associated with one or more of the multiple configuration-granted physical uplink shared channel timings, according to the transport block mapping. iii. If only one start and length indicator value SLIV is configured for multiple configuration-granted physical uplink shared channel timings, then the mapping between the start and length indicator value SLIV and the multiple configuration-granted physical uplink shared channel timings can be one of the following: 1) The start and length indication value SLIV corresponds to the first timing of the plurality of configured authorized physical uplink shared channel timings; 2) The start and length indication value SLIV corresponds to each of the plurality of configuration-authorized physical uplink shared channel timings. (6). The number of configuration authorization physical uplink shared channel opportunities within the configuration authorization period; (7) Configure the number of time slots within the authorization period; (8). The number of configuration-authorized physical uplink shared channel opportunities within a time slot; (9). Time slot format for Time-Division Duplex (TDD) uplink / downlink configuration. 7. The frequency location of multiple configuration grant physical uplink shared channel opportunities within a configuration grant period can be determined based on at least one of the following parameters: (1). Frequency hopping offset value based on at least one of the following frequency hopping schemes: i. Frequency hopping between timings; ii. In-time frequency hopping; iii. Frequency hopping between time slots; iv. Frequency hopping within a time slot. (2). Frequency domain resource allocation for the multiple configuration authorization physical uplink shared channel timing.
[0082] For example, the number of physical resource blocks (PRBs) or modulation and coding schemes (MCS) for each configured authorized physical uplink shared channel timing can be the same or different.
[0083] Example 1-2: Time-domain location configuration of multiple configuration grant physical uplink shared channel timings within the configuration grant period:
[0084] The Type A or Type B repetitive transmission feature in Ultra Reliable Low Latency Communication (URLLC) configuration licensing, or the multiple transport block transmission feature in New Radio Unlicensed Spectrum (NR-U), can be configured in Extended Reality (XR) using either Type 1 or Type 2 configuration licensing to support multiple transport block transmissions within a configuration licensing period. In one embodiment, at least one of the following configurations can be utilized:
[0085] The scheme based on Type A repeated transmission and the Type 1 or Type 2 configuration authorization configuration can be modified to carry different transport blocks. For cases where different configuration authorization physical uplink shared channel opportunities carry different transport blocks, a parameter similar to the number of repeated transmissions can be considered as the number of configuration authorization physical uplink shared channel opportunities within a configuration authorization period.
[0086] For non-continuous time slot configurations, at least one of the following mechanisms can be used: ● An additional bitmap can be used to indicate the actual configuration-granted physical uplink shared channel timing within the configuration grant period. For example, each bit of the bitmap represents a time slot. ● Multiple offsets can be configured (e.g., relative to the configuration authorization period boundary) to indicate the starting time slot for each non-contiguous time slot. If the time slots following the starting time slot are contiguous, each offset may be accompanied by the length of the contiguous time slots.
[0087] The configuration can be extended to situations where the transport block involves repeated transmissions, and a transport block can be carried on multiple configuration-authorized physical uplink shared channel occasions.
[0088] Frequency hopping within / between time slots or within / between time slots can be further configured.
[0089] Figure 3 An example of multiple transport block transmissions based on Type A repetition is demonstrated, including multiple non-contiguous configuration-granted physical uplink shared channel (PLS) timings. Two sets of {offset, length} are configured to indicate two separate consecutive time slots. The symbol position (i.e., start and length indication value SLIV) of the PLS is identical within each of the consecutive time slots.
[0090] The scheme based on type B repeated transmission and the type 1 or type 2 configuration authorization configuration can be modified to carry different transport blocks. For cases where different nominal configuration authorization physical uplink shared channel timings carry different transport blocks, a parameter similar to the repeated transmission factor (i.e., nominal repeated transmission) can be considered as the number of configuration authorization physical uplink shared channel timings within the configuration authorization period.
[0091] For non-continuous time slot configurations, at least one of the following mechanisms can be used: 1. Additional bitmaps may be used to indicate the actual configuration-granted physical uplink shared channel timing within a configuration grant period. For example, each bit of the bitmap may represent a time slot. 2. Multiple offsets (e.g., relative to the configuration authorization period boundary) can be configured to indicate the start time slot for each non-contiguous time slot. If the time slots following the start time slot are contiguous, each offset can be accompanied by the length of the contiguous time slot.
[0092] The configuration can be extended to cases involving repeated transmission of the transport block, where a transport block can be carried on multiple configuration-authorized physical uplink shared channel occasions.
[0093] If a nominally configured licensed physical uplink shared channel timeout is divided into actual configured licensed physical uplink shared channel timeouts, then the same transport block is carried on the actual configured licensed physical uplink shared channel timeouts.
[0094] Frequency hopping within / between time slots or within / between time slots can be further configured.
[0095] Figure 4 An example of multiple transport block transmission based on Type B repetitive transmission is illustrated, where the nominal physical uplink shared channel (PHS) time slot spans time slot boundaries. Eight PHS time slots are configured within a configuration grant period, each configured to carry a different transport block. Since the third and sixth PHS time slots span time slot boundaries, each of the third and sixth nominal PHS time slots is segmented into two actual configuration grant PHS time slots. These two actual configuration grant PHS time slots belong to the same nominal time slot and are used to transmit the same transport block.
[0096] For configurations based on New Radio Unlicensed Spectrum (NR-U), the result obtained by multiplying the parameters of the NR-U configuration, namely the number of consecutive time slots (cg-nrofSlots) and the number of physical uplink shared channels (cg-nrofPUSCH-InSlot) within the configuration license period, can be regarded as the number of multiple configuration license physical uplink shared channel opportunities within the configuration license period.
[0097] A transport block can be carried on one or more configured authorized physical uplink shared channel times, i.e., repeated transmission of the physical uplink shared channel.
[0098] The repetitive transmission factor can be determined from the radio resource control configuration, or it can be obtained by dividing the number of configuration-granted physical uplink shared channel opportunities within the configuration grant period by the number of transport blocks within the configuration grant period.
[0099] The number of transport blocks within the configuration grant period can be determined from the radio resource control configuration, or it can be obtained by dividing the number of configuration grant physical uplink shared channel opportunities within the configuration grant period by the repetition factor.
[0100] For a Type 2 configuration grant using activated downlink control information, the downlink control information may indicate one or more of the following parameters for each of the multiple configuration grant physical uplink shared channel timings: 1. Configure the modulation and coding scheme (MCS) value to be used when the licensed physical uplink shared channel is available; 2. Configure the frequency position to be used when authorizing the physical uplink shared channel; 3. Configure the start and length indication values (SLIV) for when to grant the Physical Uplink Shared Channel.
[0101] Please note that the above parameters can be used to indicate different configuration authorization physical uplink shared channel timings based on tables with multiple rows of values.
[0102] refer to Figure 2 In some embodiments of the present invention, the configuration of multiple physical uplink shared channel timings within the configuration grant period includes the number of consecutive time slots within the configuration grant period.
[0103] In some embodiments of the present invention, each of the consecutive time slots includes one or more physical uplink shared channel opportunities, each of the plurality of physical uplink shared channel opportunities within the configuration grant period is associated with a transport block, and different physical uplink shared channel opportunities are associated with different transport blocks.
[0104] In some embodiments of the present invention, the symbol positions of the physical uplink shared channel timing are the same for each time slot in the consecutive time slots.
[0105] In some embodiments of the present invention, the symbol position is determined based on a time-domain resource allocation based on the start and length indication values SLIV.
[0106] In some embodiments of the present invention, each bit of the bitmap is associated with a time slot within the configuration authorization period.
[0107] Examples 1-3: Configuring the transmission of a single transport block or multiple transport blocks within the authorization period.
[0108] The Time Domain Resource Allocation (TDRA) table, characterized by the use of row indexes to indicate one or more start and length indicator values (SLIVs), can be used in Extended Reality (XR) for Type 1 Configuration Grant (CG) and Type 2 Configuration Grant to support single transport block (TB) or multiple transport block transmissions during multiple Configuration Grant Physical Uplink Shared Channel (CG PUSCH) times configured within a configuration grant period. In one embodiment of this disclosure, at least one of the following configurations can be utilized.
[0109] A base station (e.g., base station 20a) can configure one or more time-domain resource allocation tables via Radio Resource Control (RRC) signaling. The time-domain resource allocation tables can be configured for the following transmission schemes: 1. Scheme 1: Single transport block transmission, wherein one transport block is associated with all configuration-granted Physical Uplink Shared Channel (PUSCH) timings for all configurations within a configuration grant period. This scheme is used to transmit repeated Physical Uplink Shared Channel (PUSCH) transmissions within a configuration grant period. 2. Scheme 2: Multiple transport blocks are transmitted, wherein each transport block is associated with only one configuration-authorized physical uplink shared channel (PHS) opportunity among all configurations within the configuration authorization period. This scheme uses a single PHS for each transport block. 3. Scheme 3: Multiple transport blocks are transmitted, wherein each transport block is associated with multiple configuration-authorized physical uplink shared channel (PHSS) opportunities from all configuration-authorized PHSS opportunities within a configuration authorization period. This scheme uses multiple PHSS opportunities for each transport block.
[0110] For Schemes 1 and 3, the Time Domain Resource Allocation Table (TDRA table) includes a repetition transmission factor, whereby a transport block is carried on multiple configuration-granted physical uplink shared channel opportunities. The total number of transport blocks can be configured by radio resource control signaling or obtained by dividing the number of configuration-granted physical uplink shared channel opportunities within a configuration-granted period by the repetition transmission factor.
[0111] For the repeated transmission scenarios in Schemes 1 and 3, a single start and length indicator value (SLIV) is associated with a single transport block. The SLIV can be applied to the first nominal repeated transmission in Type B repeated transmissions, or to the number of repeated transmissions for the configuration-granted physical uplink shared channel timing in Type A repeated transmissions.
[0112] For multiple transport block transmission scenarios in Schemes 2 and 3, multiple start and length indication values (SLIVs) are provided, each of which corresponds to one or more configuration-authorized physical uplink shared channel timings associated with a transport block.
[0113] In Type 1 or Type 2 configuration authorization settings, a time offset value can be used to indicate the slot position of the configuration authorization physical uplink shared channel timing.
[0114] Different configurations can be configured to grant physical uplink shared channel timing at the same time slot or at different time slots.
[0115] For consecutive time slot locations, an offset value can be used to indicate the first time slot location of the plurality of configuration-authorized physical uplink shared channel timings.
[0116] For discontinuous timeslot locations, multiple offset values are required to indicate each discontinuous timeslot location of the multiple configuration-authorized physical uplink shared channel timings.
[0117] Example 2: Table structure for configuring multiple configuration authorization physical uplink shared channel timings within the authorization period.
[0118] A. For Type 1 or Type 2 configuration authorization configurations, a set of parameters can be configured via row indexes, pointing to a table with multiple entries. The base station (e.g., base station 20a) can configure row indexes associated with the parameter set via Radio Resource Control signaling for different configuration authorization physical uplink shared channel timings. Details of the table structure are as follows: 1. The table may include an extended time-domain resource allocation table, which appends additional parameters to the conventional time-domain resource allocation table for each of the configured authorized physical uplink shared channel timings. 2. The table may include a newly defined table for indicating one or more parameters for different configuration authorization of physical uplink shared channel timing.
[0119] For example, the table may include a Frequency Domain Resource Assignment (FDRA) table, which indicates the frequency domain allocation for each of the configuration-granted physical uplink shared channel timings.
[0120] For example, the table may include a modulation and coding scheme (MCS) table indicating the MCS value for each of the configuration-granted physical uplink shared channel timings.
[0121] B. For the Type 2 configuration grant configuration of Scheme 2 in Examples 1-3, the activation of Downlink Control Information (DCI) can be based on a row index pointing to one or more tables, indicating one or more of the following parameters for each timing of the configuration grant physical uplink shared channel timing: 1. Time slot offset value, i.e., K2; 2. Start and length indicator values SLIV; 3. Modulation and coding scheme (MCS) value; 4. Location of frequency domain resources; 5. Physical uplink shared channel mapping type, namely Type A or Type B, where each type has a specific definition of demodulation reference signal (DMRS) symbol position, initial data symbol position, and data symbol length.
[0122] C. For configuration authorization type 2 in scheme 1 or scheme 3 of embodiments 1-3, the activation downlink control information can be based on row index pointing to one or more tables, indicating one or more of the following parameters for each group of configuration authorization physical uplink shared channel timings, wherein each configuration authorization physical uplink shared channel timing group is associated with a transport block: 1. The time slot offset value, i.e., K2, for the first time slot position of each configuration-authorized physical uplink shared channel group; 2. Start and length indication values (SLIV) for each configured authorized physical uplink shared channel group; 3. Modulation and coding scheme (MCS) value for each configured licensed physical uplink shared channel group; 4. Frequency domain resource location for each configured licensed physical uplink shared channel group; 5. Physical uplink shared channel mapping type for each configured authorized physical uplink shared channel group; 6. Repetition transmission factor.
[0123] D. For type 2 configuration grants, activating / releasing downlink control information can activate / releasing one or more configuration grant configurations, where each configuration grant configuration is associated with a set of parameters in one or more tables configured for multiple configuration grant physical uplink shared channel timings.
[0124] refer to Figure 2 In some embodiments of the present invention, the configuration authorization configuration is a type 1 configuration authorization configuration, and the start and length indication values SLIV are derived from radio resource control signaling.
[0125] In some embodiments of the present invention, the configuration authorization configuration is a type 2 configuration authorization configuration, and the start and length indication values SLIV are derived from the indication in the activated downlink control information.
[0126] Example 3: Transmission conditions for multiple configuration licensed physical uplink shared channel timings within a configuration license period:
[0127] If the location of one of the multiple configuration grant physical uplink shared channel timings within a configuration grant period partially or completely overlaps with the downlink (DL) period, such as a synchronization signal block (SSB), a control-resource set with index zero (CORESET#0), a downlink slot, or a downlink symbol, then at least one of the following transmission schemes may be used.
[0128] The user equipment (e.g., user equipment 10) stops configuration licensed physical uplink shared channel transmission at the configuration licensed physical uplink shared channel timing, provided that a portion of the configuration licensed physical uplink shared channel resources at the configuration licensed physical uplink shared channel timing overlaps with the downlink cycle.
[0129] In scenarios where the timing of the configuration licensed physical uplink shared channel overlaps with the downlink cycle, the configuration licensed physical uplink shared channel symbols that overlap with the downlink cycle are considered invalid symbols. Therefore, the user equipment can perform configuration licensed physical uplink shared channel transmission on the remaining symbols that are considered valid symbols.
[0130] If, during a configuration grant physical uplink shared channel (PHS) period, the location of one PHS PHS opportunity crosses a time slot boundary, the user equipment may employ at least one of the following transmission schemes: 1. The user equipment may suspend configuration-authorized physical uplink shared channel transmissions for any configuration-authorized physical uplink shared channel timing that crosses time slot boundaries. 2. The user equipment may, based on the scheme of Type B repetitive transmission similar to the 3GPP New Radio standard Rel.16 Ultra Reliable Low Latency Communication (URLLC), segment the nominally configured licensed physical uplink shared channel (NLP) timeframe into actual configured licensed NLP timeframes. This can be achieved in two ways: different transport blocks can be transmitted on different NLP timeframes; or, a single transport block or an identical version of the transport block can be transmitted on the actual configured licensed NLP timeframe associated with the NLP timeframe.
[0131] If some configuration-granted physical uplink shared channel opportunities are lost due to overlap with the downlink cycle, at least one of the following schemes shall be adopted: 1. The multiple configuration-granted physical uplink shared channel opportunities within the indicated configuration grant period apply only to the valid configuration-granted physical uplink shared channel opportunities that do not overlap with the downlink period. 2. The bitmap used to indicate when the configured licensed physical uplink shared channel is not used applies only to the valid configured licensed physical uplink shared channel timings that do not overlap with the downlink cycle. 3. The hybrid automatic repeat request identifier is calculated based on the effective configuration authorized physical uplink shared channel timing that does not overlap with the downlink cycle.
[0132] refer to Figure 2 In some embodiments of the present invention, the effective physical uplink shared channel timing is any physical uplink shared channel timing that does not overlap with the downlink symbol or synchronization signal block in the time slot.
[0133] In some embodiments of the present invention, each bit of the bitmap is associated with a valid physical uplink shared channel timing among the plurality of physical uplink shared channel timings.
[0134] Example 4: Determining a Hybrid Automatic Repeat Request (HARQ) procedure identifier (ID) for configuring the timing of multiple Configuration Grant Physical Uplink Shared Channels (CG PUSCH) within a grant period. User equipment (e.g., user equipment 10) is responsible for determining at least one HARQ procedure identifier for the corresponding Configuration Grant Physical Uplink Shared Channel and reporting the determined HARQ procedure identifier to the base station gNB (e.g., base station 20a) via uplink control information (UCI) in at least one transmitted Configuration Grant Physical Uplink Shared Channel. The user equipment may employ at least one of the following HARQ procedure identifier reporting schemes.
[0135] Case 1: Each transport block (TB) is mapped to a configured authorized physical uplink shared channel timing. 1. Scheme 1: The user equipment reports the hybrid automatic repeat request identifier for each time slot of the configured authorized physical uplink shared channel to the base station.
[0136] If each of the configuration-granted physical uplink shared channel timings is not declared as unused, the user equipment can report the hybrid automatic repeat request identifier of the corresponding configuration-granted physical uplink shared channel to the base station through uplink control information in at least one configuration-granted physical uplink shared channel transmitted during the configuration grant period.
[0137] If a portion of the configuration-granted physical uplink shared channel (MPUP) timings is declared unused by the user equipment (UE), the UE reports the hybrid automatic repeat request (HRP) identifier of the MPUP timings not declared unused to the base station only by uplink control information in at least one transmitted MPUP. 2. Scheme 2: The user equipment (e.g., user equipment 10) reports the hybrid automatic repeat request identifier of the transmitted Physical Uplink Shared Channel (PUSCH) to the base station gNB.
[0138] The uplink control information carried in the configuration-authorized physical uplink shared channel of the transmission reports the hybrid automatic repeat request identifier corresponding to the configuration-authorized physical uplink shared channel for each transmission.
[0139] If a Configuration Grant Physical Uplink Shared Channel (MACS) opportunity is declared as unused or no Physical Uplink Shared Channel is transmitted during the MACS opportunity, the User Equipment (UE) skips reporting the Hybrid Automatic Repeat Request (HARQ) identifier for the corresponding MACS opportunity. 3. Scheme 3: The user equipment reports the hybrid automatic repeat request identifier of the first configuration authorized physical uplink shared channel timing to the base station.
[0140] The hybrid automatic repeat request identifier for the first configuration grant physical uplink shared channel timing is carried in the uplink control information of at least one transmitted physical uplink shared channel during the configuration grant period.
[0141] The hybrid automatic repeat request identifier for subsequent configuration of authorized physical uplink shared channel timing can be determined by incrementing the value of the hybrid automatic repeat request process identifier by one from the previous configuration of authorized physical uplink shared channel timing.
[0142] If a portion of the configured authorized physical uplink shared channel timings is declared unused by the user equipment, then the incremental hybrid automatic repeat request identifier calculation is applied only to the configured authorized physical uplink shared channel timings that are not declared unused. 4. Scheme 4: The user equipment reports the hybrid automatic repeat request identifier of the first transmitted physical uplink shared channel to the base station.
[0143] The hybrid automatic repeat request identifier of the first transmitted physical uplink shared channel is carried in the uplink control information of the first transmitted physical uplink shared channel within the configuration grant period.
[0144] The hybrid automatic repeat request (HARQ) identifier for subsequent transmissions of the physical uplink shared channel can be determined by incrementing the value of the HARQ identifier from the physical uplink shared channel of the previous transmission by one.
[0145] Scenario 2: A transport block is mapped to multiple configuration-granted physical uplink shared channel (PHS) times within a configuration grant period, i.e., user equipment (e.g., user equipment 10) transmits repeated PHS transmissions associated with a transport block on some configured PHS times.
[0146] Multiple hybrid automatic repeat request identifiers associated with a single transport block for multiple configuration-authorized physical uplink shared channel timings are identical.
[0147] The scheme for reporting mixed automatic repeat request identifiers as proposed in Case 1 can be used here, with the following exceptions: 1. For the configured authorized physical uplink shared channel timing that carries repeated transmissions of the physical uplink shared channel associated with a transport block, the uplink control information will carry the same hybrid automatic repeat request identifier. 2. The incremental hybrid automatic repeat request identifier calculation is performed based on at least one configuration-authorized physical uplink shared channel timing group, wherein each configuration-authorized physical uplink shared channel timing group includes a configuration-authorized physical uplink shared channel timing that carries repeated transmissions of the physical uplink shared channel associated with a transport block.
[0148] When configuring an authorized physical uplink shared channel, the redundant version (RV) of the physical uplink shared channel is pre-configured by the base station or predefined in the standard.
[0149] like Figure 5 As shown, an example of a hybrid automatic repeat request (HARQ) identifier indication based on scheme 3 described in scenario 1 is provided. The user equipment reports the HARQ identifier of the first physical uplink shared channel (PHS) opportunity within the configuration grant period, and the HARQ identifier of subsequent PHS opportunities increments by one from the previous valid PHS opportunity.
[0150] The hybrid automatic repeat request identifier of physical uplink shared channel #1 is carried in the uplink control information of the transmitted physical uplink shared channel #1.
[0151] If the configured authorized physical uplink shared channel opportunity is not used or the configured authorized physical uplink shared channel opportunity overlaps with the downlink (DL) time slot, then the increment of the hybrid automatic repeat request identifier of the configured authorized physical uplink shared channel opportunity is skipped.
[0152] Example 5: User equipment may use the bit field in the uplink control information to indicate unused configuration-granted physical uplink shared channel timings.
[0153] Example 5-1: Indication based on start and end times
[0154] The user equipment (e.g., user equipment 10) determines the start and end times of the unused physical uplink shared channel timing of the configuration authorization. The start time can be a start time slot or start symbol determined based on the time offset relative to the end of the uplink symbol or uplink time slot carrying the uplink control information in the configured licensed physical uplink shared channel. The minimum value of the time offset (referred to as the minimum time offset) can be configured by the base station or defined in the standard. The minimum time offset can be determined based on at least one of the following factors: ● The processing time required for the base station to process and respond to the indication of the timing of the unused configuration-authorized physical uplink shared channel. ● The preparation time required for transmission uplink grants to reallocate unused physical uplink shared channel resources to other user equipment (e.g., user equipment 10b).
[0155] The end time may be determined based on at least one of the following factors: ● The end gap or end symbol of the configuration authorization period carrying the indication: In this case, the scheme utilizes an implicit indication of the end time. ●The start time plus duration: The end time is derived from the start time plus duration.
[0156] The duration of the time can be represented by at least one of the following parameters: ● The cycle length expressed in terms of time slots or symbolic granularity. ● The number of consecutive configuration licensed physical uplink shared channel opportunities, where each configuration licensed physical uplink shared channel opportunity corresponds to a period length expressed in timeslot or symbol granularity.
[0157] Example 5-2: Indication based on start and end times
[0158] The user equipment (e.g., user equipment 10) determines the start time (i.e., the start time of the configuration-granted physical uplink shared channel) and the end time (i.e., the end time of the configuration-granted physical uplink shared channel) when the configuration-granted physical uplink shared channel timing is not used.
[0159] The start timing can be indicated by a configuration licensed physical uplink shared channel timing index, which can be determined based on the number of valid configuration licensed physical uplink shared channel timings within the configuration license period.
[0160] The termination time can be determined based on at least one of the following schemes: ● The last opportunity within the period to configure the authorized physical uplink shared channel. In this case, the scheme utilizes an implicit indication of the end time. ●Start time and duration: The end time is derived from the start time and duration. The duration can be represented by the number of consecutively configured authorized physical uplink shared channel opportunities.
[0161] Example 5-3: Bitmap Indication
[0162] In one embodiment, the user equipment (e.g., user equipment 10) determines the timing of unused configuration-granted physical uplink shared channels based on a bitmap in a bit field. The bit field may be included in uplink control information. The bit length used to carry the bitmap or the uplink control information format may be configured by a base station (e.g., base station 20a).
[0163] For example, a subset of bits in the bit field can be used to indicate one or a combination of the following fields of the bitmap: ●Time domain; ●Frequency domain; ● Configure the authorization domain.
[0164] For example, a portion of the bits in the bit field can be used to indicate a partition of one of the following domains of the bitmap: ● The time domain, for example, is represented by a configuration license period index. For example, the bitmap is used to indicate unused configuration licensed physical uplink shared channels within a specific time frame. The time frame... The frame can be: ■ The configuration authorization period for transmitting the bitmap, or ■ One of the subsequent configuration authorization cycles following the aforementioned configuration authorization cycle. ● Frequency domain, for example, represented by component carrier (CC) identifiers or bandwidth part (BWP) identifiers. For example, the bitmap is used to indicate the following unused configuration-granted physical uplink shared channel moments: ■ The current component carrier or bandwidth portion carrying the bitmap, or ■One of the other component carriers or bandwidth portions. ●Configure authorization configuration fields, for example, represented by configuration authorization configuration identifiers. For example, the bitmap is used to indicate the following instances where configuration authorization physical uplink shared channels are not used: ■ The configuration authorization configuration carrying the bitmap, or ■One of the other authorized configurations.
[0165] For example, the bitmap in the bit field indicates a set of configuration-granted physical uplink shared channel (PHS) opportunities. Each bit of the bitmap corresponds to a corresponding subset of the PHS opportunities within one or more configuration-granted periods. Each bit indicates whether the indicated unused PHS opportunities are applicable to the corresponding subset of the configured PHS opportunities.
[0166] For example, the granularity of the bitmap depends on one or more of the following parameters: ● The number of configuration licensed physical uplink shared channel opportunities configured within the configuration license period. For example, with a fixed number of bits in the bitmap, a large number of configuration licensed physical uplink shared channel opportunities configured within a period will result in coarser granularity when dividing these opportunities. ● The number of configuration bits in the bitmap. ● Configure the length of the license period. ● Subcarrier spacing. For example, with a fixed number of bits in the bitmap, a larger subcarrier spacing would result in a coarser granularity when dividing these timings. ● Does it support cross-configuration licensing cycle indication?
[0167] When the bitmap is configured to allow cross-CG-period indications, consider a scenario with a 15kHz subcarrier spacing (SCS) as the reference. In this case, the configuration grant period defined by the 15kHz subcarrier spacing is the standard duration used to indicate when the configuration grant physical uplink shared channel (CG PUSCH) is not used. Therefore, for a 30kHz subcarrier spacing, the range of CG PUSCH timings that the bitmap can indicate (referred to as the indication range) can span two configuration grant periods, and for a 60kHz subcarrier spacing, the indication range can extend to four configuration grant periods.
[0168] like Figure 6 As shown, for a 15kHz subcarrier spacing, each bit of the bitmap corresponds to a single configuration-granted physical uplink shared channel opportunity within a configuration grant period. However, for a 30kHz subcarrier spacing, each bit of the bitmap represents two configuration-granted physical uplink shared channel opportunities spanning two configuration grant periods.
[0169] If the bitmap is not configured to support cross-configuration grant period indication, it is limited to indicating unused configuration grant physical uplink shared channel moments within a single configuration grant period, which may result in more granular indication.
[0170] Based on the granularity represented by each bit in the bitmap, the location mapping of the initial configuration authorized physical uplink shared channel timing corresponding to the first bit of the bitmap can be determined using one or more of the following criteria: ● The first configuration-authorized physical uplink shared channel opportunity among the multiple configuration-authorized physical uplink shared channel opportunities configured within the configuration authorization period. ● The configuration of transmitting the bitmap authorizes the physical uplink shared channel timing. ● The configuration-granted physical uplink shared channel timing immediately following the configuration-granted physical uplink shared channel timing used to transmit the bitmap. ● The configuration-granted physical uplink shared channel timing that is at a specified offset from the configuration-granted physical uplink shared channel timing for transmitting the bitmap.
[0171] The offset value can be preconfigured. For example, if the granularity of the configuration-granted physical uplink shared channel timing represented by one bit of the bitmap is one configuration-granted physical uplink shared channel timing, then the index of the starting configuration-granted physical uplink shared channel timing is equal to the index of the configuration-granted physical uplink shared channel timing transmitting the bitmap plus the offset value. Depending on the granularity of one bit in the bitmap, the starting configuration-granted physical uplink shared channel timing, and the length of the bitmap, the position of the ending configuration-granted physical uplink shared channel timing corresponding to the last bit of the bitmap can be within the configuration-granted period carrying the starting configuration-granted physical uplink shared channel timing, or within one of the subsequent configuration-granted periods.
[0172] refer to Figure 7 For example, if there are 8 Physical Uplink Shared Channel (PUSCH) opportunities within a configuration grant period, and the bitmap is 8 bits long, then each bit of the bitmap corresponds to one configuration grant PUSCH opportunity within the configuration grant period. If the user equipment transmits uplink control information (UCI) with the indication during the third configuration grant PUSCH opportunity of the configuration grant period, and if the starting configuration grant PUSCH opportunity is two time slots after the configuration grant PUSCH opportunity indicated in the uplink control information, then the ending configuration grant PUSCH opportunity corresponding to the last bit of the bitmap can be determined based on at least one of the following schemes: ●Option 1: If the uplink control information allows indication across configuration grant periods, and allows it to indicate the timing of configuration grant physical uplink shared channel across multiple configuration grant periods, then the timing of ending configuration grant physical uplink shared channel can be extended to, for example... Figure 7The fourth configuration grant physical uplink shared channel timing for the next configuration grant cycle is shown. ●Solution 2: If the uplink control information is not allowed to indicate across configuration grant periods, meaning that the uplink control information cannot indicate the configuration grant physical uplink shared channel timing across configuration grant periods, then the bitmap can only indicate the configuration grant physical uplink shared channel timing within the configuration grant period carrying the uplink control information. Therefore, the base station (gNB) ignores the last 4 bits of the bitmap.
[0173] refer to Figure 2 In some embodiments of the present invention, the information for reporting unused physical uplink shared channel timings includes the bit length of a bitmap generated by the user equipment for indicating a first set of unused physical uplink shared channel timings.
[0174] In some embodiments of the present invention, each bit of the bitmap indicates whether the physical uplink shared channel opportunity represented by the bit is unused among the plurality of physical uplink shared channel opportunities.
[0175] In some embodiments of the present invention, the initial bit indication of the bitmap follows the physical uplink shared channel timing immediately after the physical uplink shared channel timing for transmitting uplink control information carrying the bitmap.
[0176] In some embodiments of the present invention, the initial bit of the bitmap represents a physical uplink shared channel timing located at an offset after the physical uplink shared channel timing for transmitting uplink control information carrying the bitmap, the value or range of which is pre-configured or pre-defined by the user equipment.
[0177] In some embodiments of the present invention, the last bit of the bitmap indicates a physical uplink shared channel timing within the same configuration grant period as the physical uplink shared channel timing used to transmit uplink control information carrying the bitmap.
[0178] In some embodiments of the present invention, the last bit of the bitmap indicates a physical uplink shared channel opportunity within a different configuration grant period than the configuration grant period that transmits uplink control information of the bitmap carrying an opportunity where the physical uplink shared channel is not used.
[0179] Example 5-4: Indication of Pattern Index
[0180] The user equipment (e.g., user equipment 10) determines the timing of unused configuration-granted physical uplink shared channels based on an index of one of the bitmap patterns.
[0181] A set of bitmap patterns is pre-configured by the base station or user equipment, with each pattern assigned a pattern index. The bitmap pattern set can be determined based on at least one of the following schemes: ● The bitmap pattern group is determined by the base station (e.g., base station 20a) and pre-configured via Radio Resource Control (RRC) signaling. ● The bitmap pattern group is determined by the user equipment, and the user equipment reports the proposed bitmap pattern to the base station.
[0182] The user equipment (e.g., user equipment 10) may select a mode index of one of the bitmap patterns for which the configuration-authorized physical uplink shared channel timing is not used, and report the selected mode index to the base station.
[0183] The location of the configuration authorization physical uplink shared channel timing corresponding to each bit of the bitmap is described in Example 5-3.
[0184] Example 6: Reuse previously indicated unused configuration grant physical uplink shared channel opportunities within a configuration grant period for another configuration grant period.
[0185] The previously indicated unused configuration grant physical uplink shared channel timing within a configuration grant period may be applied to another configuration grant period based on at least one of the following schemes: ●Option 1: Use additional bits in the bit field of the uplink control information of the configuration grant period to indicate whether the indicated unused configuration grant physical uplink shared channel timing within the current configuration grant period can be applied to at least one subsequent configuration grant period.
[0186] For example, such as Figure 8 As shown, the additional bits may indicate the number of subsequent configuration grant periods, wherein each of the subsequent configuration grant periods follows the same indication of when the configuration grant physical uplink shared channel was not used within the configuration grant period carrying the uplink control information.
[0187] exist Figure 8 In this context, based on {offset, length} = {4, 4}, the unused physical uplink shared channel timing within a configuration grant period is indicated. Based on the configuration of reusing the unused physical uplink shared channel timing indication, the indication can be applied to the next configuration grant period.
[0188] For example, the additional bits can set the periodicity for reusing the unused configuration-granted physical uplink shared channel timing indication, wherein the same indication can be recursively applied based on the periodicity.
[0189] For example, the base station (e.g., base station 20a) can configure a set of reuse modes for unused configuration-granted physical uplink shared channel moments via radio resource control signaling. The set of reuse modes can be based on a bitmap corresponding to the configuration-granted period granularity. The user equipment (e.g., user equipment 10) can select one of the reuse modes and report the selected reuse mode to the base station. ●Solution 2: Based on configuration, the base station (e.g., the base station 20a) may assume that the indication of the unused configuration-granted physical uplink shared channel timing in the current configuration grant period can be applied to the next configuration grant period, as long as no other indication of unused configuration-granted physical uplink shared channel timing is received before the end of the next configuration grant period.
[0190] Example 7: Timing of previously indicated unused configuration licensed physical uplink shared channel (CGPUSCH) within the configuration license period.
[0191] The user equipment (e.g., user equipment 10) may update the previously indicated timing of the unused configuration grant physical uplink shared channel within the configuration grant period based on at least one of the following conditions: ● If the user equipment executes a configuration grant indication within a configuration grant period and uses the indication (e.g., uplink control information (UCI)) in the configuration grant physical uplink shared channel timing of the configuration grant period to indicate an unused configuration grant physical uplink shared channel timing, the user equipment may update the indication in a later configuration grant physical uplink shared channel timing within the same configuration grant period. ● If the user equipment executes a cross-cycle configuration grant indication and indicates an unused configuration grant physical uplink shared channel opportunity for one of the subsequent configuration grant cycles, the user equipment may update the indication in the next configuration grant cycle.
[0192] like Figure 9 As shown, the first uplink control information indicates unused physical uplink shared channel timings based on a bitmap that extends to the next configuration grant period. The user equipment updates this indication with the second uplink control information in the next configuration grant period.
[0193] The update of the indication should be carried in the uplink control information of the configuration-authorized physical uplink shared channel timing prior to the previously indicated timing when the configuration-authorized physical uplink shared channel was not used.
[0194] The user equipment (e.g., user equipment 10) updates the latest timing of the indicated unused configuration-granted physical uplink shared channel before the previously indicated timing, which can be represented by a time offset. This minimum time offset may be configured by the base station (e.g., base station 20a) or defined in the standard.
[0195] refer to Figure 9 In the example of two configuration grant periods, the first uplink control information in the first configuration grant period is transmitted at a first time offset before the timing of not using the physical uplink shared channel indicated by the bitmap of the first uplink control information, and the second uplink control information in the first configuration grant period is transmitted at a second time offset before the timing of not using the physical uplink shared channel indicated by the bitmap of the second uplink control information.
[0196] The minimum time offset value (second time offset) used to update the previously indicated timing of unused configuration-granted physical uplink shared channel can be different from the minimum time offset value (first time offset) used to indicate the timing of unused configuration-granted physical uplink shared channel. The second time offset can be greater than the first time offset. The minimum time offset is retained for the base station to process and respond to the update indication.
[0197] refer to Figure 2 In some embodiments of the present invention, the user equipment further determines a second set of unused physical uplink shared channel opportunities according to the configuration authorization configuration, and the user equipment transmits second uplink control information in the physical uplink shared channel on a non-unused second valid physical uplink shared channel opportunity, wherein the second uplink control information is used to carry a bitmap of the second set of unused physical uplink shared channel opportunities, the second valid physical uplink shared channel opportunity is associated with a second Hybrid Automatic Repeat Request (HARQ) process identifier (ID), the position of the second valid physical uplink shared channel opportunity is later than the first valid physical uplink shared channel opportunity, and at least one valid physical uplink shared channel opportunity indicated by the bitmap of the first set of unused physical uplink shared channel opportunities is the same as at least one valid physical uplink shared channel opportunity indicated by the bitmap of the second set of unused physical uplink shared channel opportunities.
[0198] In some embodiments of the present invention, for both the first group of bitmaps indicating unused physical uplink shared channel (PHS) opportunities and the second group of bitmaps indicating unused PHS opportunities, the usage status of the effective PHS opportunities indicated by the bitmaps of the second group of unused PHS opportunities is used to cover the usage status indicated by the bitmaps of the first group of unused PHS opportunities.
[0199] In some embodiments of the present invention, the first valid physical uplink shared channel timing for transmitting the first uplink control information and the second valid physical uplink shared channel timing for transmitting the second uplink control information belong to different configuration license periods.
[0200] Example 8: Content carried in the uplink control information for configuring the authorized physical uplink shared channel transmitted during the configuration authorization physical uplink shared channel timing.
[0201] The user equipment (e.g., user equipment 10) may carry at least one instance of the following information in the bit field carrying the uplink control information indicating the timing of the unused configured authorized physical uplink shared channel: ● The timing of at least one unused configuration-granted physical uplink shared channel may be indicated in the uplink control information of the configuration-granted physical uplink shared channel of the configuration-granted period carrying the uplink control information, or in the uplink control information of the configuration-granted physical uplink shared channel of at least one subsequent configuration-granted period. ■ A bit in the bit field of the uplink control information or a row index of the bit chart can indicate whether there are any unused physical uplink shared channel opportunities. ■ In an embodiment where a portion of the bit field used to configure licensed uplink control information (CG-UCI) in the New Radio Unlicensed Spectrum (NR-U) is reused, the bit field used to indicate Channel Occupancy Time (COT) sharing information may be reused to carry an indication of when the physical uplink shared channel is not being used. ● At least one Hybrid Automatic Repeat Request identifier corresponding to at least one Configuration Authorized Physical Uplink Shared Channel timing or at least one Configuration Authorized Physical Uplink Shared Channel transmitted within the Configuration Authorization Period. In an embodiment where the bit field portion used for configuring licensed uplink control information (CG-UCI) in the New Radio Unlicensed Spectrum (NR-U) is reused, the bit field used to indicate the hybrid automatic repeat request identifier for transmitting the physical uplink shared channel can be expanded to carry a hybrid automatic repeat request identifier that carries the timing of configuring licensed physical uplink shared channel within the license period. ● At least one selected or recommended modulation and coding scheme (MCS) value corresponding to at least one configuration license physical uplink shared channel timing within the configuration license period. ● At least one selected or recommended frequency domain resource corresponding to at least one configuration-granted physical uplink shared channel timing within the configuration grant period.
[0202] The configuration-authorized physical uplink shared channel timing within the configuration authorization period is a configuration-authorized physical uplink shared channel timing configured by the base station (e.g., the base station 20a), wherein at least one configuration-authorized physical uplink shared channel timing can be reported as an unused physical uplink shared channel timing by the user equipment (e.g., user equipment 10a).
[0203] Example 9: Configuration authorization physical uplink shared channel transmission timing carrying the uplink control information.
[0204] The transmission timing of the configuration-authorized physical uplink shared channel carrying the uplink control information can be at least one physical uplink shared channel transmitted within the configuration authorization period.
[0205] The location used to transmit the configuration-authorized physical uplink shared channel carrying the uplink control information can be at least one of the following: ● Configuration-authorized physical uplink shared channel timings that have not yet been declared as unused by the user equipment (e.g., user equipment 10). ■ The location of the physical uplink shared channel used to transmit uplink control information should be at least one time offset earlier than the earliest declared unused physical uplink shared channel. This time offset may be configured by the base station (e.g., base station 20a) or defined in the standard. ■ Subsequent uplink control information can be used to update the previously indicated unused physical uplink shared channel (PHS) timing of the uplink control information transmitted before the earliest declared unused PHS timing. The location for transmitting the PHS carrying subsequent uplink control information for updating the previously indicated unused PHS timing is not limited by the minimum time offset. For example, the unused PHS timing indicated by the first uplink control information can be updated by the unused PHS timing indicated by the second uplink control information. In other words, the unused PHS timing indicated by the second uplink control information can override the unused PHS timing indicated by the first uplink control information. Therefore, the location for transmitting the PHS carrying uplink control information is not limited. ●The earliest configuration-granted physical uplink shared channel timing within the configuration grant period or the duration covering multiple configuration grant periods. ■ For example, if the unused physical uplink shared channel timing indicated in the uplink control information can be a physical uplink shared channel timing that extends to the next configuration grant period, then the earliest configuration grant physical uplink shared channel timing for transmitting the physical uplink shared channel carrying the uplink control information is the earliest configuration grant physical uplink shared channel timing among the configuration grant physical uplink shared channel timings covering a duration exceeding one configuration grant period (i.e., the duration covering multiple configuration grant periods).
[0206] The base station (e.g., base station 20a) may use the indication of the most recently received unused configuration-granted physical uplink shared channel timing as the final determined information, based on which the base station performs one or more of the following functions: ●Reschedule resources to other user equipment, such as user equipment 10b; ● Physical uplink shared channel detection is performed only on configured uplink shared channel opportunities that exclude the unused configured uplink shared channel opportunities; ● Modify the configuration authorization parameters of the user equipment when the configuration authorization physical uplink shared channel is not used as described in the report.
[0207] Example 10: The process of when a base station configures multiple configuration license physical uplink shared channels (CGPUSCH) within a configuration license and when a user equipment reports that a configuration license physical uplink shared channel is not being used.
[0208] Figure 10 An example signaling flow is shown to illustrate the operation of supporting efficient multi-configuration licensed physical uplink shared channel timing configuration between a base station (e.g., base station 20a), user equipment A, and user equipment B. An example of user equipment A may include user equipment 10a, and an example of user equipment B may include user equipment 10b.
[0209] Step S021: The base station 20a transmits a configuration grant configuration with multiple configuration grant physical uplink shared channel (PHS) opportunities to the user equipment 10a via Radio Resource Control (RRC) signaling, or transmits Type B configuration grant activation downlink control information (DCI) to the user equipment 10a. The user equipment 10a obtains the configuration grant configuration from the RRC signaling or the activation downlink control information. The configuration grant configuration includes the configuration of multiple PHS opportunities for PHS transmission within the configuration grant period of the configuration grant (CG) configuration. The configuration grant configuration includes information for reporting unused PHS opportunity indications within the configuration grant period, and the unused PHS opportunity indication information is used for PHS transmission.
[0210] Steps S022 to S024: When an uplink data packet arrives, the user equipment 10a uses the report information to determine unused configuration-granted physical uplink shared channel opportunities and determines the Hybrid Automatic Repeat Request (HARQ) identifier (ID) of the unused configuration-granted physical uplink shared channel opportunity. In determining the HARQ identifier of the configuration-granted physical uplink shared channel opportunity, the user equipment 10a determines the HARQ process identifier of the valid physical uplink shared channel opportunities within the configuration-granted period.
[0211] Step S025: The user equipment 10a transmits uplink control information (UCI) to the base station 20a in a configured authorized physical uplink sharing channel. In one embodiment, the user equipment 10a transmits first uplink control information in a physical uplink sharing channel during a non-unused first valid physical uplink sharing channel opportunity. The first valid physical uplink sharing channel opportunity is associated with a determined hybrid automatic repeat request procedure identifier. The first uplink control information includes an indication of a first set of unused physical uplink sharing channel opportunities.
[0212] Step S026: The base station 20a derives the timing of unused configuration-authorized physical uplink shared channels.
[0213] Step S027: The base station 20a derives the hybrid automatic repeat request identifier of the received configuration authorized physical uplink shared channel.
[0214] Step S028: The base station 20a updates the monitoring period for authorized physical uplink shared channel reception.
[0215] Step S029: The base station 20a schedules unused configuration-authorized physical uplink shared channel resources to user equipment 10b.
[0216] Step S030: The base station 20a updates the configuration authorization parameters through downlink control information or RRC signaling.
[0217] refer to Figure 11 The user equipment 100 may include a processor 11a, a memory 12a, and a transceiver 13a. The processor 11a is configured to invoke and run a computer program stored in the memory 12a to cause the user equipment 100, on which the processor 11a is installed, to perform the methods, steps, and / or functions of the disclosed invention. The user equipment 100 is an example of the user equipment described herein (e.g., user equipment 10a or user equipment 10b). The transceiver 13a may include baseband circuitry and radio frequency (RF) circuitry.
[0218] refer to Figure 12 The network node 200 is a network device and may include a processor 21a, a memory 22a, and a transceiver 23a. The processor 21a is configured to invoke and run a computer program stored in the memory 22a to cause the network node 200, on which the processor 11 is installed, to perform the methods, steps, and / or functions of the network node. The network node 200 is an example of a core network (CN) entity, network node, wireless node, base station, or gNB in this description. The transceiver 23a may include baseband circuitry and radio frequency circuitry.
[0219] refer to Figure 13The embodiments of this disclosure also provide a chip 70, which corresponds to the user equipment in the embodiments of the disclosure. The chip 70 can implement the corresponding processes implemented by the user equipment in the various method embodiments of the disclosure. The chip 70 includes a processor 71, which can call and run computer programs from memory to implement the methods in the embodiments of the disclosure.
[0220] Optionally, the chip 70 may further include a memory 72. Specifically, the processor 71 may retrieve and run the computer program from the memory 72 to implement the method described in the disclosed embodiments of the invention.
[0221] Furthermore, the memory 72 may be a device separate from the processor 71, or it may be integrated into the processor 71.
[0222] Optionally, the chip 70 may further include an input interface 73. Note that the processor 71 can control the input interface 73 to communicate with other devices or chips, specifically, to obtain messages or data sent by other devices or chips.
[0223] Optionally, the chip 70 may further include an output interface 74. Note that the processor 71 can control the output interface 74 to communicate with other devices or chips, specifically, to output messages or data to other devices or chips.
[0224] refer to Figure 14 The embodiments of this disclosure also provide another chip 80, which may correspond to the network devices described herein (e.g., core network entities, network nodes, wireless nodes, base stations, or gNBs), and the chip 80 can implement the corresponding processes implemented by the network devices in the various method embodiments of the disclosure. The chip 80 includes a processor 81, which can call and run computer programs from the memory 82 to implement the methods in the embodiments of the disclosure.
[0225] Optionally, the chip 80 may further include a memory 82. Specifically, the processor 81 may retrieve and run the computer program from the memory 82 to implement the method described in the disclosed embodiments of the invention.
[0226] The memory 82 may be a device separate from the processor 81, or it may be integrated into the processor 81.
[0227] Optionally, the chip 80 may further include an input interface 83. Specifically, the processor 81 can control the input interface 83 to communicate with other devices or chips, specifically, to obtain messages or data sent by other devices or chips.
[0228] Optionally, the chip may further include an output interface 84. Specifically, the processor 81 can control the output interface 84 to communicate with other devices or chips, specifically, to output messages or data to other devices or chips.
[0229] Figure 15 This is a block diagram of an example wireless communication system 700 according to an embodiment of the present disclosure. The embodiments described herein can be implemented into the system using any suitably configured hardware and / or software. Figure 15 The system 700 is shown, including a radio frequency (RF) circuit 710, a baseband circuit 720, a processing unit 730, a memory / storage device 740, a display 750, a camera 760, a sensor 770, and an input / output (I / O) interface 780, which are coupled to each other as shown in the figure.
[0230] The processing unit 730 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors and application processors). The processor may be coupled to the memory / storage device and configured to execute instructions stored in the memory / storage device to enable various applications and / or operating systems to run on the system.
[0231] The baseband circuit 720 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processor may include a baseband processor. The baseband circuitry can handle various radio control functions to enable communication with one or more wireless networks via the radio frequency (RF) circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, and radio frequency shifting. In some embodiments, the baseband circuitry can provide compatible communication with one or more wireless technologies. For example, in some embodiments, the baseband circuitry can support communication with 5G New Radio (5G NR), Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (EUTRAN), and other Wireless Metropolitan Area Networks (WMAN), Wireless Local Area Networks (WLAN), and Wireless Personal Area Networks (WPAN). Embodiments configured to support wireless communication using multiple wireless protocols may be referred to as multimode baseband circuitry. In various embodiments, the baseband circuitry 720 may include circuitry that processes signals that are not strictly considered as baseband frequencies. For example, in some embodiments, the baseband circuit may include circuitry that processes signals having an intermediate frequency between the baseband frequency and the radio frequency.
[0232] The radio frequency (RF) circuit 710 can communicate with a wireless network using modulated electromagnetic radiation via a non-solid medium. In various embodiments, the RF circuit may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. In various embodiments, the RF circuit 710 may include circuitry that processes signals that are not strictly considered radio frequency. For example, in some embodiments, the RF circuitry may include circuitry that processes signals having an intermediate frequency between the baseband frequency and the radio frequency.
[0233] In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry of the user equipment, evolved Node B (eNodeB, eNB), or base station (gNB) (e.g., base station 20a) may be wholly or partially embodied in one or more of the radio frequency circuitry, the baseband circuitry, and / or the processing unit. As used herein, “circuit” may refer to, be part of, or include an application-specific integrated circuit (ASIC), electronic circuitry, a processor (shared, dedicated, or grouped), and / or a memory (shared, dedicated, or grouped) that executes one or more software or firmware programs, combinational logic circuitry, and / or other suitable hardware components that provide the aforementioned functionality. In some embodiments, the electronic device circuitry may be implemented by one or more software or firmware modules, or the functionality associated with the circuitry may be implemented by one or more software or firmware modules. In some embodiments, some or all of the components of the baseband circuitry, the processing unit, and / or the memory / storage device may be implemented together on a system on a chip (SOC).
[0234] The memory / storage device 740 can be used to load and store data and / or instructions, for example, for the system. In one embodiment, the memory / storage device may include any combination of suitable volatile memory (e.g., Dynamic Random Access Memory, DRAM) and / or non-volatile memory (e.g., flash memory). In various embodiments, the input / output (I / O) interface 780 may include one or more user interfaces designed to enable user interaction with the system, and / or peripheral component interfaces designed to enable peripheral components to interact with the system. User interfaces may include, but are not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, Universal Serial Bus (USB) ports, audio jacks, and power interfaces.
[0235] In various embodiments, the sensor 770 may include one or more sensing devices to determine environmental conditions and / or location information associated with the system. In some embodiments, the sensor may include, but is not limited to, a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the baseband circuitry and / or radio frequency circuitry to communicate with components of a positioning network (e.g., Global Positioning System (GPS) satellites). In various embodiments, the display 750 may include a display, such as a liquid crystal display (LCD) or a touchscreen display. In various embodiments, the system 700 may be a mobile computing device, such as, but not limited to, a laptop, tablet, netbook, ultrabook, smartphone, etc. In various embodiments, the system may have more or fewer components and / or different architectures. Where appropriate, the method may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transient storage medium.
[0236] The embodiments described in this disclosure are combinations of technologies / processes that can be employed in the 3rd Generation Partnership Project (3GPP) specifications to create a final product.
[0237] Those skilled in the art will understand that each unit, algorithm, and step of the disclosed invention described in the embodiments is implemented using electronic hardware or a combination of computer software and electronic hardware. Whether the function operates in hardware or software depends on the conditions of the application and the design requirements of the technical solution. Those skilled in the art may implement the function of each specific application in different ways, but such implementation should not exceed the scope of the disclosed invention. Those skilled in the art will understand that since the working process of the system, device, and unit is substantially the same as that of the system, device, and unit in the above embodiments, the working process in the above embodiments can be referred to. For ease of description and simplification, these working processes will not be described in detail.
[0238] It is understood that the systems, devices, and methods described in the disclosed embodiments can be implemented in other ways. The above embodiments are merely exemplary. The division of units is based solely on logical function, and other division methods exist in implementation. Multiple units or components may be combined or integrated into another system. Certain features may also be omitted or skipped. On the other hand, the mutual coupling, direct coupling, or communication coupling shown or discussed operates indirectly or communicatively through some ports, devices, or units in an electrical, mechanical, or other form.
[0239] The units described in the explanation may or may not be physically separate components. The units used for illustration may or may not be physical units, i.e., they may be located in one place or distributed across multiple network units. Some or all of the units are used depending on the purpose of the embodiments. Furthermore, each functional unit in the embodiments may be integrated into a processing unit, physically independent, or two or more units may be integrated into a processing unit.
[0240] If the software functional units are implemented, used, and sold as a product, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions proposed in this disclosure can be implemented essentially or partially in the form of a software product. Alternatively, a portion of the technical solutions that are beneficial to the conventional technology can be implemented in the form of a software product. The software product in the computer is stored in a storage medium and includes multiple instructions for causing a computing device (e.g., a personal computer, server 41, or network device) to perform all or part of the steps in the embodiments of the disclosed invention. The storage medium includes a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other media capable of storing program code.
[0241] While this invention has been described in conjunction with the most practical and preferred embodiments, it is to be understood that this invention is not limited to the disclosed embodiments, but is intended to cover various arrangements without departing from the broadest interpretation of the appended claims.
Claims
1. A channel access method, executed by a user equipment (UE), comprising: The configuration for acquiring multiple Physical Uplink Shared Channel (PUSCH) opportunities is used to perform PUSCH transmission within the configuration grant period of the Configuration Grant (CG) configuration, wherein the configuration grant configuration includes information for reporting unused PUSCH opportunity indications within the configuration grant period, and the unused PUSCH opportunity indication information is used for PUSCH transmission; The Hybrid Automatic Repeat Request (HARQ) process identifier (ID) determines the effective physical uplink shared channel timing within the configuration authorization period; On a non-unused first valid physical uplink shared channel opportunity, first uplink control information (UCI) is transmitted in the physical uplink shared channel, wherein the first valid physical uplink shared channel opportunity is associated with a determined hybrid automatic repeat request process identifier, and the first uplink control information includes an indication of a first set of unused physical uplink shared channel opportunities.
2. The channel access method as described in claim 1, characterized in that, The configuration of multiple physical uplink shared channel timings within the configuration grant period includes the number of consecutive time slots within the configuration grant period.
3. The channel access method as described in claim 2, characterized in that, Each of the consecutive time slots includes one or more physical uplink shared channel opportunities, and each of the plurality of physical uplink shared channel opportunities within the configuration grant period is associated with a transport block. Different physical uplink shared channel timings are associated with different transport blocks (TBs).
4. The channel access method as described in claim 2, characterized in that, The symbol positions of the physical uplink shared channel timings in each of the consecutive time slots are the same.
5. The channel access method as described in claim 4, characterized in that, The symbol position is determined based on time-domain resource allocation based on the Start and Length Indicator Value (SLIV).
6. The channel access method as described in claim 4, characterized in that, The configuration authorization configuration is a type 1 configuration authorization configuration, and the start and length indication values are from the Radio Resource Control (RFC) system. This information is derived from Resource Control (RRC) signaling.
7. The channel access method as described in claim 4, characterized in that, The configuration authorization configuration is a type 2 configuration authorization configuration, and the start and length indication values SLIV are derived from the indication in the Activation Downlink Control Information (Activation DCI).
8. The channel access method as described in claim 1, characterized in that, The effective physical uplink shared channel opportunity is any physical uplink shared channel opportunity among the plurality of physical uplink shared channel opportunities that does not overlap with the downlink symbol or synchronization signal block (SSB) in the time slot.
9. The channel access method as described in claim 1, characterized in that, The information used to report unused physical uplink shared channel timings includes the bit length of a bitmap generated by the user equipment to indicate a first set of unused physical uplink shared channel timings.
10. The channel access method as described in claim 9, characterized in that, Each bit of the bitmap indicates whether the physical uplink shared channel opportunity represented by the bit is unused among the plurality of physical uplink shared channel opportunities.
11. The channel access method as described in claim 10, characterized in that, Each bit of the bitmap is associated with a valid physical uplink shared channel opportunity among the plurality of physical uplink shared channel opportunities.
12. The channel access method as described in claim 10, characterized in that, Each bit of the bitmap is associated with a time slot within the configuration authorization period.
13. The channel access method as described in claim 10, characterized in that, The initial bit indication of the bitmap is the physical uplink shared channel timing immediately following the physical uplink shared channel timing for transmitting uplink control information carrying the bitmap.
14. The channel access method as described in claim 10, characterized in that, The initial bit of the bitmap represents the physical uplink shared channel timing at an offset after the physical uplink shared channel timing for transmitting uplink control information carrying the bitmap, and the value or range of the offset is pre-configured or pre-defined by the user equipment.
15. The channel access method as described in claim 10, characterized in that, The last bit of the bitmap indicates a physical uplink shared channel timing within the same configuration grant period as the physical uplink shared channel timing used to transmit uplink control information carrying the bitmap.
16. The channel access method as described in claim 10, characterized in that, The last bit of the bitmap indicates a physical uplink shared channel opportunity within a different configuration grant period than the configuration grant period that transmits uplink control information of the bitmap carrying unused physical uplink shared channel opportunities.
17. The channel access method as described in claim 10, characterized in that, The user equipment further determines a second set of unused physical uplink shared channel opportunities according to the configuration authorization configuration, and the user equipment transmits second uplink control information in the physical uplink shared channel on a non-unused second valid physical uplink shared channel opportunity. The second uplink control information is used to carry the bitmap of the second set of unused physical uplink shared channel opportunities. The second valid physical uplink shared channel opportunity is associated with a second hybrid automatic repeat request process identifier. The position of the second valid physical uplink shared channel opportunity is later than the first valid physical uplink shared channel opportunity. At least one valid physical uplink shared channel opportunity indicated by the bitmap of the first set of unused physical uplink shared channel opportunities is the same as at least one valid physical uplink shared channel opportunity indicated by the bitmap of the second set of unused physical uplink shared channel opportunities.
18. The channel access method as described in claim 17, characterized in that, For both the first group of unused physical uplink shared channel opportunities and the second group of unused physical uplink shared channel opportunities indicating valid physical uplink shared channel opportunities, the usage status of the valid physical uplink shared channel opportunities indicated by the bitmap of the second group of unused physical uplink shared channel opportunities is used to cover the usage status indicated by the bitmap of the first group of unused physical uplink shared channel opportunities.
19. The channel access method as described in claim 17, characterized in that, The first valid physical uplink shared channel timing for transmitting the first uplink control information and the second valid physical uplink shared channel timing for transmitting the second uplink control information belong to different configuration license periods.
20. A user equipment, comprising: A processor configured to invoke and run a computer program stored in memory to cause a device equipped with the processor to perform the method of any one of claims 1 to 19.
21. A chip, comprising: A processor configured to invoke and run a computer program stored in memory to cause a device on which the chip is mounted to perform the method of any one of claims 1 to 19.
22. A computer-readable storage medium storing a computer program that causes a computer to perform the method of any one of claims 1 to 19.
23. A computer program product comprising a computer program that causes a computer to perform the method of any one of claims 1 to 19.
24. A computer program that causes a computer to perform the method of any one of claims 1 to 19.
25. A channel access method, executed by a base station, comprising: The configuration of multiple Physical Uplink Shared Channel (PUSCH) timings is used to perform PUSCH transmissions within a configuration grant period specified in the Configuration Grant (CG) configuration. The configuration grant configuration includes information for reporting unused PUSCH timing indications within the configuration grant period. This unused PUSCH timing indication information is used for PUSCH transmissions. transmission; On a non-unused first valid physical uplink shared channel opportunity, first uplink control information (UCI) is received in the physical uplink shared channel, wherein the first valid physical uplink shared channel opportunity is associated with a determined Hybrid Automatic Repeat Request (HARQ) process identifier (ID), and the first uplink control information includes an indication of a first set of unused physical uplink shared channel opportunities.
26. The channel access method as described in claim 25, characterized in that, The configuration of multiple physical uplink shared channel timings within the configuration grant period includes the number of consecutive time slots within the configuration grant period.
27. The channel access method as described in claim 26, characterized in that, Each of the consecutive time slots includes one or more physical uplink shared channel opportunities, and each of the plurality of physical uplink shared channel opportunities within the configuration grant period is associated with a transport block. Different physical uplink shared channel timings are associated with different transport blocks (TBs).
28. The channel access method as described in claim 26, characterized in that, The symbol positions of the physical uplink shared channel timings in each of the consecutive time slots are the same.
29. The channel access method as described in claim 28, characterized in that, The symbol position is determined based on time-domain resource allocation based on the Start and Length Indicator Value (SLIV).
30. The channel access method as described in claim 28, characterized in that, The configuration authorization configuration is a type 1 configuration authorization configuration, and the start and length indication values SLIV are derived from Radio Resource Control (RRC) signaling.
31. The channel access method as described in claim 28, characterized in that, The configuration authorization configuration is a type 2 configuration authorization configuration, and the start and length indication values SLIV are derived from the indication in the Activation Downlink Control Information (Activation DCI).
32. The channel access method as described in claim 25, characterized in that, The first valid physical uplink shared channel opportunity is one of the valid physical uplink shared channel opportunities. The valid physical uplink shared channel opportunity is any physical uplink shared channel opportunity among the plurality of physical uplink shared channel opportunities that does not overlap with the downlink symbol or synchronization signal block (SSB) in the time slot.
33. The channel access method as described in claim 25, characterized in that, The information used to report the timing indication of unused physical uplink shared channels includes the bit length of a bitmap transmitted as the indication in the first uplink control information, for indicating the first set of unused physical uplink shared channel timings.
34. The channel access method as described in claim 33, characterized in that, Each bit of the bitmap indicates whether the physical uplink shared channel opportunity represented by the bit is unused among the plurality of physical uplink shared channel opportunities.
35. The channel access method as described in claim 34, characterized in that, Each bit of the bitmap is associated with a valid physical uplink shared channel opportunity among the plurality of physical uplink shared channel opportunities.
36. The channel access method as described in claim 34, characterized in that, Each bit of the bitmap is associated with a time slot within the configuration authorization period.
37. The channel access method as described in claim 34, characterized in that, The initial bit indication of the bitmap is the physical uplink shared channel timing immediately following the physical uplink shared channel timing for transmitting uplink control information carrying the bitmap.
38. The channel access method as described in claim 34, characterized in that, The initial bit of the bitmap represents the physical uplink shared channel timing at an offset following the physical uplink shared channel timing used to transmit uplink control information carrying the bitmap, wherein the value or range of the offset is pre-configured or pre-defined.
39. The channel access method as described in claim 34, characterized in that, The last bit of the bitmap indicates a physical uplink shared channel timing within the same configuration grant period as the physical uplink shared channel timing used to transmit uplink control information carrying the bitmap.
40. The channel access method as described in claim 34, characterized in that, The last bit of the bitmap indicates a physical uplink shared channel opportunity within a different configuration grant period than the configuration grant period that transmits uplink control information of the bitmap carrying unused physical uplink shared channel opportunities.
41. The channel access method as described in claim 34, characterized in that, The base station receives second uplink control information indicating a second group of unused physical uplink shared channel (PHS) opportunities according to the configuration authorization configuration. The second uplink control information is transmitted in a physical uplink shared channel on a non-unused second valid PHS opportunity. The second uplink control information is used to carry a bitmap of the second group of unused PHS opportunities. The second valid PHS opportunity is associated with a second hybrid automatic repeat request (HARQ) process identifier. The position of the second valid PHS opportunity is later than that of the first valid PHS opportunity. At least one valid PHS opportunity indicated by the bitmap of the first group of unused PHS opportunities is the same as at least one valid PHS opportunity indicated by the bitmap of the second group of unused PHS opportunities.
42. The channel access method as described in claim 41, characterized in that, For both the first group of unused physical uplink shared channel opportunities and the second group of unused physical uplink shared channel opportunities indicating valid physical uplink shared channel opportunities, the usage status of the valid physical uplink shared channel opportunities indicated by the bitmap of the second group of unused physical uplink shared channel opportunities is used to cover the usage status indicated by the bitmap of the first group of unused physical uplink shared channel opportunities.
43. The channel access method as described in claim 41, characterized in that, The first valid physical uplink shared channel timing for transmitting the first uplink control information and the second valid physical uplink shared channel timing for transmitting the second uplink control information belong to different configuration license periods.
44. A base station, comprising: A processor configured to invoke and run a computer program stored in memory to cause a device equipped with the processor to perform the method of any one of claims 25 to 43.
45. A chip, comprising: A processor configured to invoke and run a computer program stored in memory to cause a device on which the chip is mounted to perform the method of any one of claims 25 to 43.
46. A computer-readable storage medium storing a computer program that causes a computer to perform the method of any one of claims 25 to 43.
47. A computer program product comprising a computer program that causes a computer to perform the method of any one of claims 25 to 43.
48. A computer program that causes a computer to perform the method of any one of claims 25 to 43.