Wireless communication method and related equipment

Abstract

The invention provides a wireless communication method and related equipment, such as user equipment (UE) and a base station (BS) (such as a gNB). The wireless communication method is performed by a UE, and includes configuring a plurality of resources or transmission opportunities (TO) in a configuration grant (CG) configuration, the CG configuration being configured to transmit a plurality of transport blocks (transport blocks, TBs), and transmitting the plurality of transport blocks (transport blocks, TBs) to the UE, the CG configuration being configured to transmit the plurality of transport blocks (transport blocks, TBs), the CG configuration being configured to transmit the plurality of transport blocks (transport blocks, TBs), the CG configuration being configured to transmit the plurality of transport blocks (transport blocks, TBs) to the UE. Through the method, CG configuration with multiple transmission opportunities is realized.

Description

Technical Field

[0001] The present application relates to wireless communication technology, and in particular to a wireless communication method and related equipment, such as user equipment (UE) and base station (BS) (e.g., gNB). Background Art

[0002] Wireless communication systems, such as third-generation (3G) mobile phone standards and technologies, are well known. These 3G standards and technologies were developed by the Third Generation Partnership Project (3GPP). Third-generation wireless communication technologies were typically developed to support macrocell mobile phone communications. Communication systems and networks have been moving towards broadband and mobility. In a cellular wireless communication system, the UE is connected to the radio access network (RAN) via a radio link. The RAN consists of a group of base stations that provide wireless links to the UEs within their coverage cells and are connected to the core network (CN), which is responsible for overall network control. The RAN and CN each perform their respective functions in the network.

[0003] 3GPP has developed the so-called Long-Term Evolution (LTE) system, also known as the Evolved Universal Mobile Telecommunication System Territorial Radio Access Network (E-UTRAN), to support a mobile access network of one or more macro cells, which is supported by base stations called eNodeBs or eNBs (evolved Node Bs). LTE is further evolving into the so-called 5G or NR (New Radio) system, in which one or more cells are supported by base stations called next-generation NodeBs, known as gNodeBs (gNBs).

[0004] The 5G NR standard will support a variety of services with different requirements. These services include enhanced mobile broadband (eMBB) for high data rate transmission, ultra-reliable low latency communication (URLLC) for devices requiring low latency and high link reliability, and massive machine-type communication (mMTC) for energy-efficient communication supporting large numbers of low-power, long-life devices.

[0005] Extended Reality (XR) and cloud gaming are two key 5G media applications that the industry is focusing on. XR is an umbrella term encompassing different types of reality, referring to all environments and human-computer interactions that combine real and virtual reality, generated by computer technology and wearable devices. XR encompasses typical forms such as augmented reality (AR), mixed reality (MR), and virtual reality (VR), as well as the transition areas between them. 3GPP has approved a new Study Item Description (SID) for XR evaluation. The characteristics of XR traffic and the challenges it faces are summarized below:

[0006] High data rate and latency bounded:

[0007] For high-resolution 3D VR videos based on different frame rates, color encoders, bit depths, compression rates, etc., the transmission data rate may be as high as 60Mbps or even higher, while the latency is limited to about 10 to 30 milliseconds.

[0008] Non-integer period and jitter:

[0009] A consensus has been reached that 60 frames per second (fps) is the baseline frame rate for downlink (DL) and uplink (UL) video streams, with 30fps, 90fps, and 120fps also being evaluated as options. Based on the formula for calculating packet arrival time, the corresponding periods are 33.33 milliseconds, 16.67 milliseconds, 11.11 milliseconds, and 8.33 milliseconds, respectively. Furthermore, XR traffic arrivals exhibit jitter. Based on previous 3GPP RAN1 agreement, jitter can be modeled as a truncated Gaussian distribution with a range of [-4, 4] milliseconds (baseline) or [-5, 5] milliseconds (optional).

[0010] Frame size changes:

[0011] In the field of video compression, three main frame types are defined by three different video algorithms, with the following characteristics:

[0012] -I-frames are the frames with the lowest compression ratio and can be decoded independently.

[0013] -P-frames can be decoded using previous frames, and their compression rate is higher than I-frames.

[0014] -B-frames can be decoded using previous and next frames and have the highest data compression rate.

[0015] In the current 3GPP RAN1 meeting, discussions have been underway to increase the number of CG Physical Uplink Shared Channel (PUSCH) TOs for a certain duration, and several consensuses were reached at the 111th RAN1 meeting. The specific agreements are as follows:

[0016] - Protocol 1: supports dynamic indication of unused CG PUSCH transmission opportunities by the UE based on uplink control information (UCI) (e.g., CG-UCI or new UCI).

[0017] - Protocol 2: supports multiple CG PUSCH transmission opportunities within a single CG PUSCH configuration period.

[0018] Because XR video traffic is generated periodically and requires low latency, it is advantageous to use CG resources for uplink (UL) XR video transmission. For XR video, the larger frame size may require multiple PUSCH transmissions within each video frame period. Therefore, including multiple PUSCH transmission opportunities in the CG configuration helps XR cope with the problem of varying frame sizes.

[0019] At the 3GPP 98th RAN online meeting, the scope of the XR work item (WI) in 3GPP Release 18 was approved and is as follows:

[0020] Identify enhancements related to power saving:

[0021] - Support for DRX mechanisms corresponding to XR frame rates with non-integer periodicity (via at least semi-static mechanisms, such as RRC signaling) (responsibility of RAN2).

[0022] Clarify capacity-related enhancements:

[0023] -Support multiple CG PUSCH transmission opportunities within a single CG PUSCH configuration period (responsible for RAN1 and RAN2);

[0024] -Support dynamic indication of unused CG PUSCH transmission opportunities by UE based on UCI (responsible for RAN1);

[0025] -BSR (Buffer Status Report) enhancements, including at least a new BS table (managed by RAN2);

[0026] - Delay reporting of uplink buffered data (responsible for RAN2);

[0027] -Provide XR traffic assistance information for downlink and uplink (e.g. periodic information) (responsible for RAN2);

[0028] -Discarding of PDU sets (responsible for RAN2);

[0029] Identify enhancements related to XR perception (responsible for RAN2 and RAN3): To be determined (detailed objectives will be further clarified at the 99th RAN meeting based on the conclusions of TR38.835, and related work will be initiated after the 99th RAN meeting).

[0030] However, there are still some issues that need to be addressed when configuring CG to include multiple transmission opportunities.

[0031] Other related technologies:

[0032] In the current 3GPP specifications, the ConfiguredGrantConfig information element (IE) is used to configure uplink transmissions without dynamic grants according to two possible schemes. The actual uplink grant can be configured via RRC (Type 1) or provided via the PDCCH (using the CS-RNTI address) (Type 2). Multiple configured grants (CGs) can be configured in a BWP in a serving cell, with a maximum of 12.

[0033] For Type 2, the UE can verify the validity of the PDCCH allocated by downlink semi-persistent scheduling (SPS) or the configured Type 2 uplink grant PDCCH to activate or release scheduling when the following conditions are met:

[0034] -The CRC of the corresponding DCI format is scrambled using the CS-RNTI provided by the cs-RNTI or the G-CS-RNTI provided by the g-cs-RNTI.

[0035] and - the new data indication field in the DCI format for enabling the transport block is set to '0'.

[0036] And - if the DFI flag field is present in the DCI format, this field is set to "0".

[0037] And - the time domain resource allocation field in the DCI format indicates a row with a single SLIV.

[0038] and - if the verification is for scheduling activation and the PDSCH to HARQ feedback time indication field is present in the DCI format, then this field shall not provide an inapplicable value from dl-DataToUL-ACK-r16.

[0039] If the UE is only provided with a configuration for a type 2 uplink grant PUSCH or SPS PDSCH, the validation of the DCI format is completed when all fields in the DCI format are set accordingly.

[0040] If the UE is provided with multiple configurations for Type 2 uplink grants PUSCH or SPS PDSCH, the value of the HARQ Process ID field in the DCI format indicates the activation of the Type 2 uplink grant PUSCH or SPS PDSCH configuration corresponding to the same value provided by ConfiguredGrantConfigIndex or sps-ConfigIndex. Validation of the DCI format is accomplished when the RV (Redundancy Version) field in the DCI format is set accordingly.

[0041] If the UE is provided with multiple configurations for Type 2 uplink grants PUSCH or SPS PDSCH:

[0042] -If the UE is provided with ConfiguredGrantConfigType2DeactivationStateList or sps-ConfigDeactivationStateList, the value of the HARQ process number field in the DCI format indicates the scheduling release items of one or more type 2 uplink grants PUSCH or SPS PDSCH in the corresponding configuration.

[0043] -If the UE is not provided with ConfiguredGrantConfigType2DeactivationStateList or sps-ConfigDeactivationStateList, the value of the HARQ process ID field in the DCI format indicates the release of the type 2 uplink grant PUSCH or SPS PDSCH configuration corresponding to the same value provided by ConfiguredGrantConfigIndex or sps-ConfigIndex.

[0044] When all fields in the DCI format are set accordingly, the verification of the DCI format is completed.

[0045] If the verification succeeds, the UE regards the information in the DCI format as a valid activation or release of the downlink SPS or the configured type 2 uplink grant; if the verification fails, the UE shall discard all information in the DCI format.

[0046] In the existing mechanism, a single CG configuration or multiple CG configurations can be configured. One or more CG configurations can be activated or released through one or more DCIs. In addition, repeated transmissions can be configured in the CG configuration, and two types of PUSCH transmissions are defined, one of which is PUSCH repetition of type A and the other is PUSCH repetition of type B. Type A PUSCH repetition is based on time slots, and is repeated at most once in a time slot, and the time and frequency of each CG configuration in the time slot are the same. For type B PUSCH repetition, the repetition pattern is back-to-back in the time domain, and multiple repeated transmissions can be configured in one time slot. Summary of the Invention

[0047] The purpose of the present application is to provide a wireless communication method and related equipment for implementing the inclusion of multiple transmission opportunities (TOs) in a configuration grant (CG) configuration.

[0048] In a first aspect, an embodiment of the present application provides a wireless communication method performed by a user equipment (UE), the method comprising: being configured with multiple resources or transmission opportunities (TO) in a configuration grant (CG) configuration, the CG configuration being used to transmit multiple transmission blocks (TB).

[0049] In a second aspect, an embodiment of the present application provides a wireless communication method performed by a base station (BS), the method comprising: configuring a user equipment (UE) with multiple resources or transmission opportunities (TO) included in a configuration grant (CG) configuration, the CG configuration being used to transmit multiple transmission blocks (TB).

[0050] In a third aspect, an embodiment of the present application provides a user equipment (UE), comprising a processor, a transceiver, and a memory, wherein the processor, transceiver, and memory communicate with each other via an internal connection path, the memory is used to store instructions, and the processor is used to execute the method described in the first aspect when executing the instructions stored in the memory.

[0051] In a fourth aspect, an embodiment of the present application provides a base station (BS), comprising a processor, a transceiver, and a memory, wherein the processor, transceiver, and memory communicate with each other through an internal connection path, the memory is used to store instructions, and the processor is used to execute the method described in the second aspect when executing the instructions stored in the memory.

[0052] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a computer to execute any method in the first aspect or the second aspect.

[0053] In a sixth aspect, an embodiment of the present application provides a computer program product comprising computer program instructions, enabling a computer to execute any one of the methods in the first aspect or the second aspect.

[0054] In a seventh aspect, an embodiment of the present application provides a computer program, which, when running on a computer, enables the computer to execute any one of the methods in the first aspect or the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] In order to more clearly illustrate the embodiments of the present invention or related technologies, the following briefly introduces the drawings that will be described in the embodiments. Obviously, these drawings are only some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without inventive work.

[0056] Figure 1 Schematic diagram showing a CG configuration with multiple TOs for periodic XR packets.

[0057] Figure 2 Schematic diagram showing XR frame size changes and semi-statically configured CG assets.

[0058] Figure 3 A schematic diagram showing the packet size change and jitter of XR under CG.

[0059] Figure 4 A schematic diagram of a user equipment and a base station in a communication control system according to an embodiment of the present application is shown.

[0060] Figure 5 A schematic diagram showing the radio protocol architecture in gNB and UE.

[0061] Figure 6 A schematic diagram shows that the gNB further includes a centralized unit (CU) and multiple distributed units (DU).

[0062] Figure 7 This is a flowchart of a wireless communication method in an embodiment of the present application.

[0063] Figure 8 A schematic diagram showing an example of repetitive transmission of multiple TBs on multiple TOs.

[0064] Figure 9 A schematic diagram showing another example of repetitive transmission of multiple TBs on multiple TOs.

[0065] Figure 10 Schematic diagram showing the situation where a TB collides with other transmissions.

[0066] Figure 11 A schematic diagram showing multiple HARQ-IDs corresponding to multiple TOs in a CG configuration.

[0067] Figure 12 A schematic diagram showing that UCI indicates unused TOs in a CG configuration. DETAILED DESCRIPTION

[0068] The embodiments of the present invention will be described in detail with reference to the technical content, structural features, implementation objectives and effects thereof in conjunction with the accompanying drawings. It should be noted that the terms in the embodiments of the present invention are only used for the purpose of describing specific embodiments and should not be regarded as limiting the present invention.

[0069] In this document, the term " / " should be understood to mean "and / or". Combinations such as "at least one A, B, or C", "one or more A, B, or C", "at least one A, B and C", "one or more A, B, and C", or "A, B and / or C" may mean only A, only B, only C, A and B, A and C, B and C, or A, B and C, where any combination may include one or more members of A, B, or C.

[0070] In the early stages of energy conservation, when a user equipment (UE) is configured with configured grant (CG) / semi-persistent scheduling (SPS) and discontinuous reception (DRX), the CG or SPS resources may be insufficient to complete packet transmission to accommodate the varying sizes of XR packets. Therefore, some companies have proposed adding additional PDCCH monitoring opportunities after the CG / SPS when DRX is disabled. Furthermore, DRX itself requires additional inactivity time when the DRX duration is insufficient to process a packet due to jitter or packet size variations. When an XR packet is transmitted within the DRX duration, whether the remaining DRX time should be retained also requires consideration. Some companies recommend skipping the remaining DRX time; however, others believe that the PDCCH adaptation mechanism in 3GPP Release 17 can handle this situation by setting an appropriate PDCCH skip value, eliminating the need to skip the remaining DRX time. Similar issues exist regarding XR capacity enhancement. Due to the low latency requirement of XR, in terms of uplink transmission, the main task is to develop suitable transmission mechanisms for XR, such as dynamic grant (DG)-based transmission, CG+DG-based transmission, SR+DG-based transmission, pre-scheduling or enhanced CG transmission mechanism. In the early stages of XR capacity enhancement, a variety of the above mechanisms have been proposed. After several 3GPP meetings, many companies agreed that enhanced CG can be used as a potential method for XR transmission due to its low alignment latency and the ability to work in the DRX off state. However, when considering the jitter and packet size variation of XR at the same time, the existing CG mechanism is still not suitable for XR transmission. Therefore, the CG mechanism needs to be further enhanced. In order to adapt to XR traffic, especially large packet sizes with large variations, it is possible to consider configuring multiple CG transmission opportunities for one CG, such as Figure 1 shown.

[0071] However, further details on configuring multiple TOs in a CG configuration have not yet been discussed and decided.

[0072] One of the issues is how the UE works under the CG configuration mechanism with multiple TOs. The related issues are listed as follows:

[0073] When multiple TOs are configured in one CG configuration, consideration needs to be given to how the number of TOs is indicated to the UE to avoid ambiguity between the gNB and the UE.

[0074] It is necessary to study how to configure or determine the time domain resources of multiple TOs in the CG configuration. It is also necessary to consider whether repeated TOs are supported and the TO types (such as type A or type B, back-to-back mapping, time domain conflicts, etc.).

[0075] In current 3GPP specifications, the HARQ-ID for a CG is calculated based on a formula, and the HARQ process field in the DCI is used to activate the CG. However, for XR, multiple TOs require the transmission of multiple TBs. When a TB fails to transmit successfully on a specific TO, it must be retransmitted. However, in existing 3GPP specifications, HARQ-ID conflicts between TOs may occur. Therefore, research is needed to determine HARQ-IDs for all TOs in a CG configuration to avoid conflicts.

[0076] In the current 3GPP specification, a set of allowed periodic parameters P is defined in TS 38.331. The high-level parameter cg-nrofSlots provides the number of consecutive time slots allocated in one CG period. The high-level parameter cg-nrofPUSCH-InSlot provides the number of consecutive PUSCHs allocated in one time slot, where the first PUSCH allocation is based on the high-level parameter timeDomainAllocation (for type 1 PUSCH transmission) or according to the high-level configuration in TS 38.321; for type 2 PUSCH transmission, the uplink grant is received via DCI. The remaining PUSCH allocations have the same length and PUSCH mapping type and are appended consecutively after the previous allocation without any gaps.

[0077] However, CG resources are semi-statically configured and cannot adapt to changes in XR packet size. Figure 2 As shown in the figure, if 4 PUSCHs are configured in one CG cycle, then for video frames that only require less than 4 PUSCHs, resources will be wasted; if only 3 PUSCHs are configured, but the video frame is large, for example, each video frame requires 4 PUSCHs, then additional dynamic scheduling is required, resulting in additional scheduling delays.

[0078] In addition, when packets arrive late due to jitter, the TO in the CG configuration may be insufficient, causing additional delay. Figure 3 As shown in Figure 2, due to jitter, the packet arrives later than predicted at P2, where there are only two available TOs (less than the actual demand). Figure 2 Therefore, it is necessary to study how to indicate unused TOs and extra TOs.

[0079] It is necessary to determine how to indicate unused and additional TOs in the CG configuration. A signaling method for indicating unused or additional TOs should be defined. In addition, when defining this signaling method, it is necessary to consider the issue that the mechanism in the current 3GPP specification is not applicable, and the multiplexing rules between this signaling method and existing uplink control information should be studied.

[0080] In short, this application proposes some methods to enable CG configuration to support large and varying packet sizes of XR. Specifically, the following solutions are provided:

[0081] In order to determine the number of TOs, the CG repetition number parameter can be reused to indicate the number of multiple TOs used to transmit multiple TBs in a CG configuration; the number of TOs in the CG configuration can also be indicated by new signaling or by joint encoding with certain parameters (such as TDRA); some implicit methods can also be used to indicate the number of TOs in the CG configuration, such as inferring through parameters such as the number of TDRAs and the periodicity of CG.

[0082] In order to indicate the HARQ-ID of each TO or each group of TOs, a semi-static method can be provided to determine the HARQ-ID, for example, based on the reference HARQ-ID plus a new parameter or certain information of the TO, or the HARQ-ID can be directly configured.

[0083] To indicate the unused / extra TOs in the CG configuration to the gNB, a solution using CG-UCI, new UCI, and CAS is proposed. The main methods include the following:

[0084] Sequence-based approach: RRC configures a set of values ​​representing unused TOs, then indicates a corresponding index through UCI (for example, the UCI is similar to a scheduling request SR), and defines a default value (for example, a default offset value) to determine the time position of the unused TO.

[0085] Sequence-based approach: RRC configures a set of values ​​representing unused TOs and a corresponding value K (such as an offset value), and then indicates a corresponding index through UCI.

[0086] Non-sequence-based method: A new UCI is carried through PUCCH, and the content of the UCI includes at least one of the following: the number of unused TOs, the K value, the index of unused TOs, or the index of a group of unused TOs, etc., where K is used to determine the time position of the unused TOs.

[0087] CG-UCI: The content of UCI includes at least one of the following parameters: the number of TOs, the K value, the index of a TO or the index of a group of TOs, etc., where K is used to determine the time position of unused TOs.

[0088] Bitmap mode: The size of this field is equal to the total number of TOs.

[0089] In addition, relevant rules for reusing new UCIs and CG-UCIs with current types of UCIs are proposed.

[0090] Figure 4 The present invention illustrates one or more user equipment (UE) 10 and a base station (e.g., gNB or eNB) 20 for wireless communication in a communication network system 30 according to an embodiment of the present application. The communication network system 30 includes one or more UEs 10 and a base station 20. The one or more UEs 10 may include a memory 12, a transceiver 13, and a processor 11 connected to the memory 12 and the transceiver 13. The base station 20 may include a memory 22, a transceiver 23, and a processor 21 connected to the memory 22 and the transceiver 23. The processor 11 or 21 may be configured to perform the functions, processes, and / or methods described in this specification. The various layers of the radio interface protocol may be implemented in the processor 11 or 21. The memory 12 or 22 is operatively connected to the processor 11 or 21 for storing various information required for the execution of the processor 11 or 21. The transceiver 13 or 23 is operatively connected to the processor 11 or 21 for transmitting and / or receiving wireless signals. The base station 20 can also communicate wirelessly or wired with the next generation core network (5GCN). When the communication network system 30 complies with the 3GPP NR standard, the next generation core network is the backend service network system and may include an access and mobility management function (AMF), a user plane function (UPF), and a session management function (SMF). In one aspect, the user equipment 10 can be almost any consumer electronic device or device capable of connecting to a radio access network and a core network, and is applicable to networks of various versions of 3GPP and subsequent versions, such as but not limited to NR networks.

[0091] The processor 11 or 21 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits and / or data processing devices. The memory 12 or 22 may include a read-only memory (ROM), a random access memory (RAM), flash memory, a memory card, a storage medium and / or other storage devices. The transceiver 13 or 23 may include a baseband circuit for processing radio frequency signals. When these embodiments are implemented in software form, the technology described herein may be implemented by modules (such as procedures, functions, etc.) that perform the functions. These modules may be stored in the memory 12 or 22 and executed by the processor 11 or 21. The memory 12 or 22 may be integrated inside the processor 11 or 21 or located outside the processor, in which case they may establish a communication connection with the processor 11 or 21 in various known ways. Figure 5 The wireless protocol architecture of the user plane between gNB and UE is presented, including optional Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Medium Access Control (MAC) protocol layers. In the radio access network (RAN) functional split architecture, the gNB further includes a centralized unit (CU) and multiple distributed units (DU), such as Figure 6 The CU's protocol stack includes the RRC layer, the optional SDAP layer, and the PDCP layer, while the DU's protocol stack includes the RLC layer, the MAC layer, and the PHY layer. The CU and DU are connected via the F1 interface, which is located between the PDCP layer and the RLC layer.

[0092] Figure 7 A wireless communication method according to an embodiment of the present application is illustrated. Figure 7 and Figure 4As shown, method 100 includes the following steps: in step 110, the UE is configured by the BS and is configured with multiple resources or TOs in a CG configuration, and the CG configuration is used to transmit multiple TBs. That is, multiple resources or TOs are configured in the CG configuration for transmitting multiple TBs on the PUSCH. The CG configuration can be a single CG configuration or one of multiple CG configurations. For a single CG configuration, one CG is configured at a certain moment; and for multiple CG configurations, multiple CGs are configured at the same time at a certain moment. Through this method, a CG configuration with multiple transmission opportunities is achieved.

[0093] In one embodiment, the number of TOs in the CG configuration can be determined by the number of repetitions of each TO, and the UE can receive a signaling indicating that the number of TOs in the CG configuration is determined by the number of repetitions of each TO. The signaling can be carried by a field in the downlink control information (DCI) or a column in the time domain resource allocation (TDRA) field in the DCI. In another embodiment, the number of TOs in the CG configuration can be indicated by RRC, MAC CE, DCI or the TDRA field in the DCI. In yet another embodiment, the number of TOs in the CG configuration can be associated with at least one of the following: the periodicity of the CG, the time domain duration of each TO, the type of PUSCH, the number of time slots within the periodicity, or the number of repetitions of each TO.

[0094] In one embodiment, the TBs transmitted through the TOs in the CG configuration are configured for repeated transmission, first transmitting the initial transmission of different TBs, and then continuously transmitting the repeated parts of all different TBs in sequence. In another embodiment, the TBs transmitted through the TOs in the CG configuration are configured for repeated transmission, first transmitting the initial transmission of different TBs, and then continuously transmitting all the repeated parts of a certain TB in sequence. In some embodiments, all TOs of each TB can adopt a frequency hopping method. In the event of a conflict, if some TBs or TOs conflict with other transmissions, a set of supplementary TOs can be added after the last TO of the CG configuration. In the event of a conflict, if some TBs or TOs conflict with other transmissions, the TBs on the conflicting TO can be moved to the next or next available TO, or moved to the next or next available TO carrying the same TB.

[0095] In one embodiment, each TO in the CG configuration may have a different HARQ-ID. Multiple HARQ-IDs may be determined based on the first symbol of each TO in the CG configuration, or the HARQ-IDs of all TOs may be determined based on a reference HARQ-ID and / or the index / number of the corresponding TO. In another embodiment, each group of TOs in the CG configuration may have a different HARQ-ID, and TOs in the same group may have the same HARQ-ID. Multiple HARQ-IDs may be determined based on the first symbol in each group of TOs, or the HARQ-IDs of all TO groups may be determined based on a reference HARQ-ID and / or the index / number of each group of TOs.

[0096] In one embodiment, unused or used TOs in the CG configuration may be indicated by UCI, CG-UCI, or CAS. In one example, a group of values ​​representing unused TOs is configured by RRC, and UCI or CG-UCI is used to indicate an index corresponding to one of the values ​​of the group of unused TOs. A default value may also be defined to determine the temporal position of an unused TO. In another example, UCI or CG-UCI includes at least one of the following parameters: the number of unused TOs, the K value, the index of an unused TO, or the index of a group of unused TOs. In yet another example, a bitmap is used to indicate unused TOs in the CG configuration. In addition, an extra bit of a field in the UCI or CG-UCI may be used to indicate whether an unused TO or a used TO is to be represented; or unused TO or used TO may be indicated by different UCIs or CG-UCIs, respectively.

[0097] In one embodiment, additional TOs may be added after the last TO in the CG configuration. These additional TOs may be indicated by a UCI or CG-UCI, which includes at least one of the following parameters: a reference TO, the number of TOs, a K value, or an index of a TO.

[0098] In one embodiment, when the CG-UCI overlaps with other CG-UCIs in the time domain, the CG-UCI can be connected with the other CG-UCIs. The CG-PUSCH can first carry the CG-UCI and then carry other types of UCIs.

[0099] The following further describes how to determine the number of resources and / or TOs in a CG configuration.

[0100] The present application proposes one or more methods for determining the number of resources and / or TOs in a CG configuration. Multiple TBs can be transmitted on multiple TOs in a CG configuration. The current 3GPP specification supports CG with repeated transmission. When a CG is configured with repeated transmission and the number of repetitions is greater than 1, multiple transmission opportunities can be used to transmit an initial TB and its repeated versions, and the repeated versions can use the same or different redundancy versions (RV). In order to avoid functional ambiguity between multiple TOs, certain parameters can be reused, or new signaling can be introduced to indicate the number of TOs used to transmit multiple TBs.

[0101] In the first feasible solution proposed in the present application, all parameters configured by RRC and / or downlink control information (DCI) can be shared by multiple TOs in the CG configuration. The repetition number parameter in the CG configuration can be reused to determine the number of TOs used to transmit multiple TBs. A new signaling can be introduced to enable or disable this function. For example, the signaling can be RRC, MAC CE or DCI signaling. When the number of repetitions configured by the CG is indicated by the TDRA field in the DCI, a new field can be set in the DCI or a new column can be set in the TDRA to indicate whether the number of repetitions can be reused to determine the number of TOs. For example, the new field or new column can be 1 bit, and the value of "1" or "0" respectively indicates whether the number of repetitions is used to determine the number of TOs.

[0102] In the second feasible solution proposed in the present application, all parameters configured by RRC and / or DCI can be shared by multiple TOs in the CG configuration. In order to achieve the reliability of transmission of multiple TBs or PUSCHs on multiple TOs, although repeated transmission is required, the number of repetitions should not be used as the basis for determining the number of TOs. The number of TOs in the CG configuration can be indicated by new signaling, or implemented in conjunction with existing parameters. New RRC signaling, MAC CE or DCI can be introduced to indicate the number of TOs in the CG configuration. The number of TOs in the CG configuration can also be indicated by TDRA. A new column can be added to the TDRA table to indicate the number of TOs in the CG configuration. When the number of repetitions (whose value is k) is also configured, each TO will enable k repetitions. In some embodiments, the number of TOs in the CG configuration represents the same number of TB / PUSCHs transmitted on multiple TOs.

[0103] In the third feasible solution proposed in the present application, not all parameters configured by RRC and / or DCI are shared among multiple TOs in the CG configuration. In order to achieve the flexibility of TO, some TO parameters are not shared. Among multiple TOs, at least one parameter can be configured independently, such as TDRA, modulation coding scheme (MCS) or RV. Each group of TDRA, MCS and RV can be represented by a joint coding point (the coding point can be used to indicate a group of TDRA, MCS, RV or HARQ-ID). In this way, the number of TDRA, MCS, RV or HARQ-ID can be used to indicate the number of TOs in the CG configuration.

[0104] In the fourth feasible solution proposed in this application, the number of TOs in the CG configuration is associated with at least one of the following: the periodicity of the CG, the time domain duration of each TO, the type of PUSCH, the number of time slots within the periodicity, or the number of repetitions of each TO. For example, when the PUSCH is configured as type A, the total number of TOs is equal to the number of time slots or the number of available time slots within one CG cycle; when the PUSCH is configured as type B, the total number of TOs is equal to: the total number of symbols or the number of available symbols within one CG cycle divided by the time domain duration of one TO, and the result of rounding up or down.

[0105] The above embodiments implement a method for determining the number of resources and / or TOs in the CG configuration for transmitting multiple TBs, avoiding ambiguity between the gNB and the UE. This type of CG enhancement can be applied to application scenarios such as XR.

[0106] The following will further explain how to determine the time / frequency pattern of multiple TOs in a CG configuration.

[0107] This application proposes one or more methods for determining the time / frequency pattern of multiple TOs in a CG configuration and handling the situation where TBs conflict with other transmissions. When multiple TOs are configured in a CG for XR in 3GPP Release 18 or future versions, a direct way to ensure the reliability of PUSCH transmission is to enable repeated transmission of TBs or PUSCH transmissions. In order to reduce the latency of data packet transmission, a time repetition pattern based on TBs can be considered, such as Figure 8 and Figure 9 shown.

[0108] Figure 8This example shows the time domain pattern when multiple TBs are transmitted over multiple TOs in a CG configuration. In this example, when the TBs transmitted over the TOs in the CG configuration are configured for repeated transmission, the initial transmission portion of each TB is transmitted first, followed by the repeated portions of all the different TBs. Assume that in a CG configuration, there are three TBs transmitted over multiple TOs, denoted as TB1, TB2, and TB3. The initial transmissions of the different TBs (i.e., TB1, TB2, TB3) are first mapped to the TOs, followed by the first round of repetitions of these TBs (i.e., R1-1, R2-1, R3-1), followed by the second round of repetitions (R1-2, R2-2, R3-2), and so on. In other words, the rules for mapping TBs to TOs are as follows: 1. Map the initial transmissions of all TBs first; 2. Map the first round of repetitions of all TBs next; 3. Continue mapping subsequent repetitions in the same manner. It should be noted that TB1 in the figure represents the first or initial transmission, R1-1, R1-2, and R1-3 represent repeated transmissions of TB1; TB2 represents the first or initial transmission, R2-1, R2-2, and R2-3 represent repeated transmissions of TB2; the remaining TBs (such as TB3) are defined in the same way. In addition, this definition also applies to Figure 9 、 Figure 10 and Figure 11 .

[0109] Figure 9 Another example of a time domain pattern for transmitting multiple TBs across multiple TOs in a CG configuration is presented. In this example, when the TBs transmitted on the TOs in a CG configuration are configured for repeated transmission, the initial transmissions of the different TBs are transmitted first, followed by all repeated transmissions of a particular TB. Assume that in a CG configuration, there are three TBs transmitted across multiple TOs, denoted as TB1, TB2, and TB3. The initial transmissions of the different TBs (i.e., TB1, TB2, TB3) are first mapped to the TOs, followed by all repeated transmissions of the first TB (i.e., R1-1, R1-2, R1-3), followed by all repeated transmissions of the second TB (i.e., R2-1, R2-2, R2-3), and so on. The repeated transmissions are configured in this manner. In other words, the TB mapping rules to the TOs are as follows: 1. First, the initial transmissions of all TBs are mapped; 2. Then, all repeated transmissions of each TB are mapped sequentially, according to the order of the TBs (smallest to largest).

[0110] In some embodiments, all TOs in the CG configuration may adopt frequency hopping rules, and the hopping method may be inter-slot hopping, inter-TO hopping, inter-TB hopping, or intra-slot hopping. In some embodiments, all TOs in the CG configuration may adopt frequency hopping rules based on the time duration of a TB, and the hopping method may also be inter-slot, inter-TO, inter-TB, or intra-slot hopping. Taking inter-TO hopping as an example (see Figure 8 ), when cross-TO hopping is enabled and the number of hops is 2, the first hop contains {TB1, R1-2}, and the second hop contains {R1-1, R1-3}. TOs within the same hop use the same frequency resources, but there is a frequency offset between different hops.

[0111] In addition, when multiple TOs in a CG configuration conflict, some rules need to be formulated to handle the conflict.

[0112] Case 1: When multiple non-repeated TBs are transmitted via multiple TOs in a CG configuration, if some TBs or TOs collide with other transmissions, a set of supplementary TOs can be added after the last TO of the CG configuration. The supplementary TOs can share the parameters of the configured TOs or the parameters of the reference TO, where the reference TO can be pre-defined or indicated by the UE or gNB. In some embodiments, the addition of the supplementary TOs can be indicated by UCI or a demodulation reference signal (DMRS). In some embodiments, the HARQ-ID of the supplementary TO is the same as the HARQ-ID of the TO that collided.

[0113] Case 2: When multiple TBs with duplication are transmitted through multiple TOs in a CG configuration, if some TBs or TOs conflict with other transmissions, the TBs on the conflicting TOs can be moved to the next or next available TO, or to the next or next available TO that carries the same TB. For example, Figure 10As shown, assuming there are 3 different TBs, each TB has 3 repetitions (excluding the initial transmission), which are transmitted through multiple TOs in the CG configuration, and the RV cycle of each TB is {0, 2, 3, 1}. If the initial transmission of a TB (for example, TB2) conflicts with other transmissions, the initial transmission of TB2 can be moved to the position of R2-1. The corresponding RV cycle can be: the RV of TB2 (at the R2-1 position) is 0, the RV of R2-2 is 3, and the RV of R2-3 is 1. In some embodiments, the initial TB2 can be moved to the nearest TO or the nearest available TO, which originally carries a repeated transmission and the RV of the TO is the same as the RV of the initial TB. For example, the initial TB2 can be moved to the position of R1-1, and the original R1-1 and all subsequent repeated transmissions can be postponed to the next TO, or R1-1 is discarded.

[0114] The above embodiments implement the determination of the time / frequency pattern of multiple TOs used to transmit multiple TBs in a CG configuration, as well as the handling of conflicts between TBs and other transmissions, thereby enabling repeated transmission of TOs or TBs in a CG configuration. This type of CG enhancement solution is applicable to application scenarios such as XR.

[0115] The following will further explain how to determine the HARQ-ID of all TOs in the CG configuration.

[0116] This application proposes one or more methods for determining resources / transmission opportunities in a CG configuration, focusing on semi-statically determining the HARQ-IDs of all TOs in the CG configuration, particularly in the presence of repeated transmissions. For multiple TOs capable of transmitting multiple TBs, the HARQ-IDs of each TO or group of TOs must be distinct to avoid ambiguity during retransmissions between the UE and the gNB.

[0117] Case 1: When configuring HARQ-ID in multiple TOs without duplication, each TO in the CG configuration has a different HARQ-ID. In the current 3GPP specification, the HARQ-ID of the CG is calculated based on the position of the first transmission opportunity of the CG, and its calculation formula is as follows:

[0118] HARQ Process ID=[floor(CURRENT_symbol / periodicity)]modulo nrofHARQ-Processes+harq-ProcID-Offset2(1).

[0119] In order to achieve multiple HARQ-IDs for multiple TOs in a CG configuration, the formula in the current 3GPP specification can be reused for calculation, but the "first symbol" is no longer based on the first TO in the CG configuration, but is calculated separately based on the first symbol of each TO in the CG configuration. Multiple HARQ-IDs can be calculated based on the first symbol of each TO in the CG configuration, or a reference HARQ-ID can be calculated according to the current 3GPP specification, and then the HARQ-IDs of all TOs are determined based on the reference HARQ-ID and in combination with a certain configuration parameter, time / frequency resource, time / frequency resource location, TO number or TO index. In some embodiments, the HARQ-IDs of all TOs can also be directly configured by RRC, MAC control unit (CE) or DCI. In this case, the number of different HARQ-IDs is equal to the number of TOs.

[0120] Case 2: When configuring HARQ-ID in multiple TOs with repetition, each group of TOs has a different HARQ identifier (HARQ-ID), and TOs in the same group have the same HARQ-ID, where each group of TOs is used to transmit the same TB, with or without repetition. For example, Figure 11 As shown in the figure, assuming a CG configuration, there are 3 TBs, each with 3 repetitions (excluding the initial transmission), which are transmitted through multiple TOs. TB1 is transmitted through {TB1, R1-1, R1-2, R1-3}, TB2 is transmitted through {TB2, R2-1, R2-2, R2-3}, and TB3 is transmitted through {TB3, R3-1, R3-2, R3-3}. Among them, {TB1, R1-1, R1-2, R1-3} is defined as TO group 1, {TB2, R2-1, R2-2, R2-3} is defined as TO group 2, and {TB3, R3-1, R3-2, R3-3} is defined as TO group 3. In this way, TO groups 1, 2, and 3 each have different HARQ-IDs, while TOs in the same group have the same HARQ-ID.

[0121] In order to achieve multiple HARQ-IDs for multiple TO groups in one CG configuration, the calculation formula in the current 3GPP specification can be reused to calculate the HARQ-ID, but the "first symbol" is no longer based on the symbol of the first TO in the CG configuration, but based on the first symbol of each TO group. Multiple HARQ-IDs can be calculated based on the first symbol of each TO group, or a reference HARQ-ID can be calculated according to the current 3GPP specification, and then the HARQ-IDs of all TO groups can be determined based on the reference HARQ-ID. This process can also be performed in combination with a certain configuration parameter, the first time / frequency resource of the TO group, the first time / frequency resource position of the TO group, the number of TO groups, or the index of the TO group. In some embodiments, the HARQ-IDs of all TO groups can be directly configured by RRC, MAC CE or DCI. In this case, the number of different HARQ-IDs is equal to the number of TO groups.

[0122] The above embodiment determines the HARQ-IDs corresponding to all TOs in the CG configuration for transmitting multiple TBs, solving the HARQ-ID usage issue between the gNB and the UE and avoiding HARQ-ID conflicts. This type of CG enhancement solution can be applied to application scenarios such as XR.

[0123] The following further explains how to indicate unused TOs in the CG configuration.

[0124] This application proposes a method to indicate that TO is not used in the CG configuration through CG-UCI or a new type of UCI. In the current 3GPP specification, UCI can be reported through the physical uplink control channel (PUCCH), mainly including HARQ-ACK information, scheduling request (SR), link recovery request (LRR), channel state information (CSI) and CG-UCI. Among them, the UCI bits include: HARQ-ACK information bit (if any), SR information bit (if any), LRR information bit (if any) and CSI bit (if any). When the above UCI overlaps in the time domain, multiplexing rules must be formulated. In addition, UCI can also be reported through the physical uplink shared channel (PUSCH). For this purpose, a set of offset values ​​is defined for the UE to determine the number of resources in the PUSCH used to multiplex HARQ-ACK information and CSI reports. In CG-PUSCH, an offset value (beta offset) for multiplexing CG-UCI is also defined. In LTE-LAA, CG-UCI (also known as AUL-UCI) has been approved for use to support adaptive retransmission. CG-UCI mainly includes HARQ-ID, RV-ID, new data indicator (NDI), and other contents. In the unlicensed spectrum (NR-U) of 5G NR, a mechanism similar to LTE-LAA is reused, where the CG-UCI content in NR-U includes: HARQ-ID, RV-ID, NDI, channel occupancy time (COT), etc. To avoid wasting resources, a new type of UCI or CG-UCI can be used to indicate unused TO.

[0125] Case 1: At the beginning of the CG configuration, several consecutive TOs are not used. This is because the data packets of a certain service fail to arrive at the expected time position due to jitter, resulting in some TOs in the beginning of the CG configuration being unused.

[0126] The first possible solution of this application is: if RAN2 (the working group studying XR perception or other related topics) studies jitter measurement or changing packet size distribution and makes some predictions, the UE can skip a group of consecutive TOs at the beginning of the CG configuration. In this case, a new type of UCI carried on the PUCCH is required. The content of this new UCI may include:

[0127] Sequence-based approach: A set of unused TO values ​​can be configured by RRC. The UCI is then used to indicate the corresponding index, while a default value (e.g., a default offset) is defined to determine the temporal position of unused TOs. This default value can be predefined and based on symbol granularity, slot granularity, TO duration, or time units in milliseconds. In some embodiments, the default value can be the processing time required by the gNB to process the signaling sent by the UE. In some embodiments, starting from the first symbol, last symbol, or slot of the UCI, the remaining TOs within the default value duration are indicated as unused TOs.

[0128] Sequence-based approach: A set of unused TO values ​​and their corresponding value K (e.g., offset value) are configured by RRC, and the UCI is then used to indicate the corresponding index. The value of unused TO indicates the number of consecutive or non-consecutive TOs. The value of K is a time unit, and its granularity can be slots, symbols, TO duration, or milliseconds. This means that, starting from the signaling time position, a set of unused TOs is indicated after K.

[0129] Non-sequence-based approach: The content of the UCI includes at least one of the following parameters: the number of unused TOs, the K value, the index of an unused TO, or a group of unused TOs, where K is used to determine the time position of an unused TO. The number of TOs represents the number of consecutive or non-consecutive TOs, which is used to determine the total number of unused TOs. The value of K is a time unit, and its granularity can be a time slot, a symbol, a TO duration, or a millisecond. This means that, starting from the time position of the signaling, a group of unused TOs is indicated after K. In this case, the resources of the PUCCH should match the periodicity of the XR.

[0130] Bitmap: The size of this field is equal to the total number of TOs.

[0131] In the second feasible solution of the present application, when there is no data in the UE cache, a matching UCI can be used to indicate the next consecutive unused TO in the CG configuration. If service data arrives before a TO in the CG configuration, UCI can be sent to indicate that the next consecutive TO in the CG configuration will be used. In this way, a set of PUCCH resources needs to be configured to indicate which TOs in the CG configuration are not used or will be used, because the UE side has no predicted information about the packet size or jitter. A trade-off needs to be made between PUCCH overhead and TO resource savings in the CG configuration. In addition, in order to distinguish between UCIs used to indicate unused or used TOs, additional bits need to be added to the UCI field, or multiple types of UCIs need to be designed.

[0132] In the third feasible solution of this application, Channel Associated Signaling (CAS) in the CG configuration is introduced to indicate the unused TO at the beginning of the CG. CAS is associated with a CG and can configure specific resources within or associated with a CG. The information indicating the unused TO is then carried in the resource via PUSCH, MAC CE, UCI, or other uplink channels.

[0133] Case 2: At the end of a CG configuration, multiple consecutive TOs remain unused. This scenario is the original motivation for supporting the "unused TO indication" feature. In this case, after the UE completes transmission of a data packet, if there are still multiple TOs remaining in the CG configuration, the UE can send information to the gNB to indicate these unused TOs, thereby avoiding resource waste. In this case, the use of new UCI types and / or CG-UCI carried on the PUCCH can be considered for implementation. The specific design is as follows:

[0134] Sequence-based: RRC configures a set of values ​​representing unused TOs, and then UCI is used to indicate the corresponding index (for example, UCI is similar to a scheduling request SR), and defines a default value (for example, a default offset) to determine the time position of the unused TOs. For example, Figure 12 As shown, when a UCI indicating that TO is not used is transmitted, the gNB regards the TO after the default value in the CG (e.g., TO8, TO9, TO10) as unused TO.

[0135] Sequence-based: RRC configures a set of values ​​representing unused TOs and their corresponding values ​​K (such as an offset value), and then UCI indicates the corresponding index.

[0136] Non-sequential mode: A new type of UCI carried by PUCCH, whose content includes at least one of the following: the number of unused TOs, the value K, or the index of unused TOs or TO sets, etc., where K is used to determine the time position of unused TOs.

[0137] CG-UCI: The content of the UCI includes at least one of the following parameters: the number of TOs, the K value, or the index of a TO or a group of TOs, etc., where K is used to determine the time position of unused TOs. The number of TOs can be the number of consecutive or non-consecutive TOs, which is used to determine the number of unused TOs. The K value is a time unit, and its time granularity can be a time slot, a symbol, a TO duration, or a millisecond. That is, starting from the time position where the signaling is located, a group of TOs after K is regarded as unused TOs. In some embodiments, the resources used to carry the CG-UCI (e.g., beta-offset) can be configured.

[0138] Bitmap: The size of this field is equal to the total number of TOs.

[0139] Case 3: Any one or more TOs in the CG configuration (except the TO at the beginning) are unused TOs. This case is similar to the above case, and in this case, it seems appropriate to use a bitmap.

[0140] The above embodiments implement the indication of unused TOs in a CG configuration for transmitting multiple TBs, thus avoiding resource waste and potentially reducing additional scheduling delays. Furthermore, these improvements can be applied to XR applications to address issues such as jitter and size variations in XR packets.

[0141] More details on introducing additional TOs after the last TO in the CG configuration are described below.

[0142] When the number of TOs in the CG configuration is not enough to transmit all TBs of a data packet, in order to reduce scheduling delay, additional TOs can be added after the last TO of the CG configuration. These additional TOs can be indicated by a new type of UCI or CG-UCI, and its content may include at least one of the following parameters: the index of the reference TO, the number of TOs to be added, the K value, or the index of a certain TO. The index of the reference TO is used to determine all parameters of the PUSCH, such as frequency domain resource allocation (FDRA), TDRA, MCS, etc. If these parameters are not explicitly stated through UCI or CG-UCI, the default values ​​(i.e., the default reference values) can be used, such as the parameters of the last TO in the CG configuration. The number of TOs is used to indicate the number of additional or supplementary TOs that need to be added, and all these TOs share the parameters of the reference TO or default reference value except for the HARQ-ID. The K value is used to indicate the starting position of these additional or supplementary TOs in the time domain.

[0143] The above embodiment introduces an additional TO after the last TO in a CG configuration to transmit multiple TBs, thereby reducing scheduling latency. Furthermore, these improvements can be applied to XR applications to address issues such as jitter and size variations in XR packets.

[0144] More details about multiple UCI reuse are described below.

[0145] This application proposes a method for handling multiple UCI multiplexing rules, including multiplexing new UCI types with existing UCI types. Hereinafter, "negative new UCI" may indicate that the UCI carries no information and / or does not indicate any TOs as unused; while "positive new UCI" may indicate that the UCI carries some information and / or indicates some TOs as unused. Similarly, a "negative SR" may indicate that no SR needs to be transmitted, while a "positive SR" may carry SR-related information.

[0146] Case 1-1: Negative new UCI, negative SR, and up to two HARQ-ACK information bits in a PUCCH format 0 resource within a slot or a TO. In this case, the UE transmits HARQ-ACK using only PUCCH format 0 and determines the cyclic shift parameter based on the HARQ-ACK information. When an SR transmission opportunity (or new UCI transmission opportunity) overlaps in time with a PUCCH format 0 resource containing up to two HARQ-ACK information bits, the UE transmits only HARQ-ACK information (sequence) based on the HARQ-ACK parameters, and the gNB treats both the SR and the new UCI as negative.

[0147] Case 1-2: New UCI in the negative direction, positive SR, and up to two HARQ-ACK information bits in one TO or timeslot. In this case, transmission is based on the SR resources.

[0148] Case 1-3: New UCI in the positive direction, SR in the negative direction, and up to two HARQ-ACK information bits in one TO or timeslot. In this case, the transmission is based on the resources of the new UCI.

[0149] Case 1-4: New forward UCI, forward SR, and up to two HARQ-ACK information bits in one TO or timeslot. In this case, the resources and cyclic shift values ​​based on the SR and new UCI are transmitted together.

[0150] Case 2: In a time slot or a TO, new UCI and up to two HARQ-ACK information bits are sent in the forward direction using PUCCH format 0. In this case, the new UCI and HARQ-ACK each have their own cyclic shift values, and these cyclic shift values ​​can be predefined. Due to the limited number of cyclic shift values, priority rules can be introduced to handle this situation. The following are several options:

[0151] Alternative 1: Consider the new forward UCI as high priority and the HARQ-ACK transmission as low priority. The UE sends the new UCI using PUCCH format 0, and the cyclic shift parameter is determined by the new UCI configuration.

[0152] Alternative 2: Consider HARQ-ACK transmission as high priority and new UCI reporting as low priority. The UE sends HARQ-ACK using PUCCH format 0, and the cyclic shift parameter is determined only by the HARQ-ACK reporting parameters.

[0153] Alternative 3: Consider HARQ-ACK transmission as high priority and new UCI reporting as low priority. The UE sends HARQ-ACK using PUCCH format 0, but the cyclic shift parameter is determined by the new UCI.

[0154] Alternative 4: Consider HARQ-ACK transmission as high priority and new UCI reporting as low priority. The UE sends new UCI using PUCCH format 0, but the cyclic shift parameter is determined by HARQ-ACK.

[0155] Alternative 5: Consider HARQ-ACK transmission and new UCI reporting as having the same priority, and introduce a new cyclic shift parameter combination for sending new UCI and HARQ-ACK simultaneously. For example, see Table 1 below:

[0156]

[0157] Table 1: Mapping relationship between one HARQ-ACK information bit and one new UCI bit in PUCCH format 0.

[0158] Solution 6: The UE sends PUCCH format 0 containing earlier symbols and corresponding information. For example, if the first symbol of PUCCH format 0 for HARQ-ACK is earlier than the first symbol of PUCCH format 0 for new UCI, the UE sends HARQ-ACK. Conversely, if the first symbol of HARQ-ACK is later than the first symbol of new UCI, the UE sends new UCI.

[0159] Case 3: PUCCH format 0 contains both new UCI (multi-bit) and up to two HARQ-ACK information bits, with different priorities configured by the gNB. If the new UCI has a higher priority than the HARQ-ACK, the UE reports the new UCI to the gNB, and the HARQ-ACK is discarded or deferred to the next available transmission opportunity. Conversely, if the HARQ-ACK has a higher priority than the new UCI, the UE should report the HARQ-ACK using PUCCH format 0, with the cyclic shift parameter determined solely by the HARQ-ACK, and the new UCI is discarded or deferred to the next available transmission opportunity. In addition, when a positive new UCI is present, one bit should be added after the HARQ-ACK or new UCI.

[0160] Case 4: For the case where the UE plans to use PUCCH format 0 resources to transmit new UCI and PUCCH format 1 resources to transmit HARQ-ACK information bits in a time slot, if the new UCI and HARQ-ACK have the same priority, a priority rule can be introduced to handle this situation. The following alternative solutions can be considered:

[0161] Alternative solution 1: The UE uses only PUCCH format 0 resources to transmit PUCCH containing new UCI bits.

[0162] Alternative Solution 2: Whether the UE reports new UCI or HARQ-ACK information depends on the first symbol time of each PUCCH format. If the first symbol of PUCCH format 0 is earlier than that of PUCCH format 1, the UE only transmits PUCCH containing new UCI information bits in the resources of PUCCH format 0. If the first symbol of PUCCH format 1 is earlier than that of PUCCH format 0, the UE only transmits PUCCH containing HARQ-ACK information bits in the resources of PUCCH format 1. If the first symbols of the two formats are the same, the UE uses the PUCCH format with the shorter symbol length for information transmission.

[0163] Case 5: For the case where the UE plans to use PUCCH format 1 resources to transmit new UCI information and PUCCH format 0 resources to transmit up to 2 HARQ-ACK information bits in a time slot, if the new UCI and HARQ-ACK have the same priority, a priority rule can be introduced to handle this situation. The following alternative solutions can be considered:

[0164] Alternative 1: The UE transmits PUCCH containing new UCI bits only in resources using PUCCH format 1.

[0165] Alternative solution 2: A new cyclic shift value table can be designed to combine the transmission of new UCI and HARQ-ACK, and use PUCCH format 0 to transmit the combined information.

[0166] Case 6: For the case where the UE plans to transmit new UCI information and up to two HARQ-ACK information bits using PUCCH format 1 resources in one time slot, the UE shall transmit in PUCCH format 1 resources for the new UCI information and / or defer HARQ-ACK to the next (available) transmission opportunity.

[0167] In addition, the UE decides whether to transmit new UCI or HARQ-ACK based on the time position of the PUCCH. If the first symbol of PUCCH format 1 for HARQ-ACK is earlier than that of PUCCH format 1 for new UCI, the UE only transmits HARQ-ACK information bits in the resources using PUCCH format 1; if the first symbol of PUCCH format 1 for new UCI is earlier than that of HARQ-ACK, the UE only transmits new UCI information bits in the resources using PUCCH format 1; if the first symbols of the two PUCCH formats are the same, the UE will use the PUCCH format with the shorter number of symbols to transmit the information bits.

[0168] Case 7: The UE transmits a PUCCH containing HARQ-ACK, CSI, or information bits (denoted as M) in resources using PUCCH format 2, PUCCH format 3, or PUCCH format 4. At the same time, it transmits K PUCCHs in a time slot, each transmitting N bits of new UCI. The new UCI information bits are transmitted in resources using PUCCH format 2, PUCCH format 3, or PUCCH format 4, and all UCI bits are concatenated and processed as a whole.

[0169] The above implementation enables multiplexing of multiple UCIs and establishes a multiplexing rule between the signaling indicating the unused or added TO and the current uplink control information. Therefore, the signaling indicating the unused or added TO becomes achievable, thereby resolving the issues of XR packet jitter and size variation.

[0170] Regarding the multiplexing rules of multiple UCIs, further details are described below.

[0171] The present application proposes a method for processing multiple UCI multiplexing rules, including CG-UCI multiplexing with existing types of UCI.

[0172] In the first feasible solution of this application, the XR CG-UCI is considered to have the same or similar priority as the NR-U CG-UCI and can be reused with the current UCI using a similar mechanism. When the XR CG-UCI and the NR-U CG-UCI overlap in the time domain, the XR CG-UCI and the NR-U CG-UCI are concatenated and processed as a whole.

[0173] In the second feasible solution of the present application, the XR CG-UCI is considered to have the highest priority. The CG-PUSCH first carries the XR CG-UCI and then carries other UCIs.

[0174] In a third feasible solution of the present application, when signaling for multiplexing UCI is enabled, the mapping of CG-UCI appears first in the bit sequence, followed by other UCIs.

[0175] In some embodiments, when the number of UCI types exceeds 3, the CSI may be discarded, or the CG-UCI may be jointly encoded with the HARQ-ACK bits, or two types of CG-UCI may be concatenated.

[0176] The above implementation enables multiplexing of various UCIs and establishes multiplexing rules between the signaling indicating the unused or attached TO and the current uplink control information. Therefore, it is feasible to introduce signaling indicating the unused or attached TO, thereby resolving the issues of XR packet jitter and size variation.

[0177] The commercial benefits of some embodiments of the present application are as follows: solving problems in the prior art; enabling multiple TOs in one CG configuration; enabling indication of unused resources / transmission opportunities in the CG configuration; avoiding HARQ-ID conflicts; supporting multiplexing of multiple UCIs; and providing good communication performance. Some embodiments of the present application are suitable for 5G-NR chipset manufacturers, V2X communication system developers, automobile manufacturers (including cars, trains, trucks, buses, bicycles, locomotives, helmets, etc.), unmanned aerial vehicles (UAVs), smartphone manufacturers, manufacturers of communication equipment for public safety, and manufacturers of AR / VR equipment for games, conferences / seminars, education, etc. Some embodiments of the present application are "technology / process" combinations that can be incorporated into 3GPP specifications to achieve the final product. Some embodiments can also be applied to unlicensed frequency band communications in 5G NR. This application also proposes a number of technical mechanisms.

[0178] The embodiments of the present application also provide a computer-readable storage medium for storing a computer program. This computer-readable storage medium enables a computer to execute the corresponding processes implemented by the user equipment / base station in each embodiment of the present application. For the sake of brevity, the relevant details are not repeated here.

[0179] The embodiments of the present application further provide a computer program product comprising computer program instructions. This computer program product enables a computer to execute the corresponding processes implemented by the user equipment / base station in each embodiment of the present application. For the sake of brevity, the relevant details are not repeated here.

[0180] The embodiments of the present application also provide a computer program. This computer program can enable a computer to execute the corresponding processes implemented by the user equipment / base station in each embodiment of the present application. For the sake of brevity, the relevant details are not repeated here.

[0181] Non-transitory computer-readable media may include at least one of the following: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory (EEPROM), and a flash memory. In embodiments where software is used to implement each component, the software may be stored in a computer-readable medium and loaded into a computing system via, for example, a removable storage drive. The control module (in this case, software instructions or executable computer program code), when executed by a processor in the computing system, may cause the processor to perform the functions described herein. Furthermore, the present invention may be applied to any circuit in a network element that performs signal processing functions. It is further contemplated that, for example, a semiconductor manufacturer may employ the present invention in the design of a stand-alone device such as a digital signal processor or an application-specific integrated circuit or any other subsystem component.

[0182] Furthermore, the present invention is applicable to any circuitry used to perform signal processing functions within a network element. It is further contemplated that, for example, semiconductor manufacturers may employ the present invention in the design of standalone devices, such as microcontrollers, application-specific integrated circuits (ASICs), and / or any other subsystem components of a digital signal processor (DSP).

[0183] Those skilled in the art will appreciate that, in conjunction with the examples described in the embodiments disclosed in this specification, each unit and algorithm step can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether a function is implemented by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may adopt different implementation methods to implement the functions for each specific application, but this should not be considered to be beyond the scope of this application.

[0184] While the present application has been described in connection with what are considered to be the most practical and preferred embodiments, it is to be understood that the application is not limited to the disclosed embodiments, but is intended to cover modifications that may be made without departing from the broadest interpretation of the appended claims.

Claims

1. A wireless communication method, performed by a user equipment UE, characterized in that: The method comprises: A plurality of resources or transmission opportunities TO are configured in the configuration grant CG configuration, and the CG configuration is used to transmit a plurality of transmission blocks TB.

2. The method according to claim 1, characterized in that Also includes: Receive signaling, where the signaling is used to indicate the number of repetitions used to determine the number of TOs in the CG configuration.

3. The method according to claim 2, wherein The signaling is carried by a field in the downlink control information DCI or a column in the time domain resource allocation TDRA field.

4. The method according to claim 1, wherein The TO number in the CG configuration is indicated by the radio resource control RRC, or the media access control MAC control element CE, or DCI, or the TDRA field in the DCI.

5. The method according to claim 1, wherein The number of TOs in the CG configuration is associated with at least one of the following: the periodicity of the CG, the time domain duration of each TO, the type of the physical uplink shared channel PUSCH, the number of time slots within the periodicity, and the number of repetitions of each TO.

6. The method according to claim 1, wherein The TBs transmitted through the TO in the CG configuration are configured for repeated transmission, the initial transmission of different TBs is performed first, and the repeated transmissions of all different TBs are performed in sequence according to the order of the initial transmission.

7. The method according to claim 1, wherein The TBs transmitted through the TO in the CG configuration are configured for repeated transmission, with initial transmission of different TBs being performed first, and after the initial transmission, all repeated transmissions of a certain different TB are performed sequentially and continuously.

8. The method according to claim 1, wherein All TOs in each TB use frequency hopping.

9. The method according to claim 1, wherein Each TO in the CG configuration has a different HARQ-ID.

10. The method according to claim 9, wherein Multiple HARQ-IDs are determined based on the first symbol of each TO in the CG configuration, or the HARQ-IDs of all TOs in the CG configuration are determined based on the reference HARQ-ID and / or the index / number of the corresponding TO.

11. The method according to claim 1, wherein Each group of TOs in the CG configuration has a different HARQ-ID, and TOs in the same group have the same HARQ-ID.

12. The method according to claim 11, wherein Multiple HARQ-IDs are determined based on the first symbol in each group of TO, or the HARQ-IDs of all TO groups in the CG configuration are determined based on the reference HARQ-ID and / or the index / number of each group of TO.

13. The method according to claim 1, wherein The unused or used TO in the CG configuration is indicated by uplink control information UCI, CG-UCI, or configuration authorization status CAS.

14. The method according to claim 13, wherein A set of values ​​representing unused TOs is configured by the radio resource control RRC, and the UCI or the CG-UCI is used to indicate an index corresponding to one of the set of unused TO values.

15. The method according to claim 13, wherein Defines the default value for determining the time position of unused TOs.

16. The method according to claim 13, wherein The UCI or the CG-UCI includes at least one of the following parameters: the number of unused TOs, a K value, an index of unused TOs, or a group of indexes of unused TOs.

17. The method according to claim 13, wherein A bitmap is used to indicate the TOs that are not used in the CG configuration.

18. The method according to claim 1, wherein Add additional TOs after the last TO in the CG configuration.

19. The method according to claim 1, wherein The additional TO is indicated by UCI or CG-UCI, and the UCI or the CG-UCI includes at least one of the following parameters: a reference TO, the number of TOs, a K value, and an index of a certain TO.

20. The method of claim 13, wherein: When the CG-UCI and other CG-UCIs overlap in the time domain, the CG-UCI is connected to the other CG-UCIs.

21. The method according to claim 13, wherein The CG-PUSCH first carries the CG-UCI and then carries other types of UCI.

22. A wireless communication method, performed by a base station BS, characterized in that: The method comprises: A plurality of resources or transmission opportunities TO included in a configuration authorization CG configuration is configured for the user equipment UE, and the CG configuration is used to transmit a plurality of transmission blocks TB.

23. The method according to claim 22, wherein Also includes: Sending signaling to indicate the number of repetitions used to determine the number of TOs in the CG configuration.

24. The method according to claim 23, wherein The signaling is carried by a field in the downlink control information DCI or a column in the time domain resource allocation TDRA field.

25. The method of claim 22, wherein: The number of TOs in the CG configuration is indicated by the radio resource control RRC, or the media access control MAC control element CE, DCI, or the TDRA field in the DCI.

26. The method of claim 22, wherein: The number of TOs in the CG configuration is associated with at least one of: the periodicity of the CG, the time domain duration of each TO, the type of physical uplink shared channel PUSCH, the number of time slots within the periodicity, or the number of repetitions of each TO.

27. The method of claim 22, wherein: The TBs transmitted through the TO in the CG configuration are configured for repeated transmission, the initial transmission of different TBs is performed first, and the repeated transmissions of all different TBs are performed in sequence according to the order of the initial transmission.

28. The method of claim 22, wherein: The TBs transmitted through the TO in the CG configuration are configured for repeated transmission, with initial transmission of different TBs being performed first, and after the initial transmission, all repeated transmissions of a certain different TB are performed sequentially and continuously.

29. The method of claim 22, wherein: All TOs in each TB use frequency hopping.

30. The method of claim 22, wherein: Each TO in the CG configuration has a different HARQ-ID.

31. The method of claim 30, wherein: Multiple HARQ-IDs are determined based on the first symbol of each TO in the CG configuration, or the HARQ-IDs of all TOs in the CG configuration are determined based on the reference HARQ-ID and / or the index / number of the corresponding TO.

32. The method of claim 22, wherein: Each group of TOs in the CG configuration has a different HARQ-ID, and TOs in the same group have the same HARQ-ID.

33. The method of claim 32, wherein: Multiple HARQ-IDs are determined based on the first symbol in each group of TO, or the HARQ-IDs of all TO groups in the CG configuration are determined based on the reference HARQ-ID and / or the index / number of each group of TO.

34. The method of claim 22, wherein: The unused or used TO in the CG configuration is indicated by uplink control information UCI, CG-UCI, or configuration authorization status CAS.

35. The method of claim 34, wherein: A set of values ​​representing unused TOs is configured by the radio resource control RRC, and the UCI or the CG-UCI is used to indicate an index corresponding to one of the set of unused TO values.

36. The method of claim 34, wherein: Defines the default value for determining the time position of unused TOs.

37. The method of claim 34, wherein: The UCI or the CG-UCI includes at least one of the following parameters: the number of unused TOs, a K value, an index of unused TOs, or a group of indexes of unused TOs.

38. The method of claim 34, wherein: A bitmap is used to indicate unused TOs in the CG configuration.

39. The method of claim 22, wherein: Add additional TOs after the last TO in the CG configuration.

40. The method of claim 22, wherein: The additional TO is indicated by UCI or CG-UCI, and the UCI or the CG-UCI includes at least one of the following parameters: a reference TO, the number of TOs, a K value, and an index of a certain TO.

41. A user equipment (UE), comprising a processor, wherein the processor is configured to call and run program instructions stored in a memory to perform the method according to any one of claims 1 to 21.

42. A base station BS, comprising a processor, wherein the processor is configured to call and run program instructions stored in a memory to perform the method according to any one of claims 22 to 40.

Images