Method and apparatus for repeated transmission
By configuring the measurement subband in the wireless communication system and using the DCI format 0_0 scheduling mechanism, the problem of PUSCH repeated transmission coverage is solved, and the advance reporting of UE capabilities and effective support for PUSCH transmission is achieved, and the overall efficiency and coverage of the system are improved. Rate.
Patent Information
- Application Number
- CN202280094387.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-12-09
- Publication Date
- 2024-11-22
AI Technical Summary
In wireless communication systems, the repeated transmission of the physical uplink shared channel (PUSCH) has a problem of coverage bottlenecks, especially during the initial access process and before the RRC reconfiguration, it is difficult to effectively support the repeated transmission of the PUSCH and identify the repeated transmission capability of the UE.
Repeated transmission request or capability indication is sent to the base station through the user equipment (UE), and the base station sends repetitive factor indication to the UE, configure the measurement subband to support the repeated transmission of PUSCH, and use RRC reconfiguration and DCI format 0_0 scheduling mechanism to report in advance The UE's ability to facilitate PUSCH transmission.
It improves the coverage rate and network efficiency of PUSCH, ensures timely support of PUSCH transmission before RRC reconfiguration, and enhances the overall performance and coverage capability of the system.
Smart Images

Figure CN119014112A_ABST
Abstract
Description
Technical Field
[0001] The present application relates generally to wireless communications and, more particularly, to methods and apparatus for indicating and / or configuring repeated transmissions of a physical uplink shared channel (PUSCH). Background Art
[0002] Wireless communication technology is pushing the world into an increasingly interconnected and networked society. In wireless communication systems, the physical uplink shared channel (PUSCH) may be one of the potential coverage bottleneck channels in the physical channels used for uplink transmission, and PUSCH may need to be enhanced to meet the growing demand. Repeated transmission of PUSCH is one of the effective ways to improve coverage, but there is at least one problem. For example, one problem may be how to support repeated transmission of PUSCH; and / or another problem may be how to identify one or more UEs with repeated transmission capabilities.
[0003] The present application describes various embodiments for indicating and / or configuring repeated transmission of PUSCH, solving at least one of the problems associated with repeated transmission of PUSCH, providing improvements in the technical field of wireless communication and improving its efficiency and performance. Summary of the invention
[0004] The present application relates to a method, system and apparatus for configuring a measurement subband configuration to indicate and / or configure repeated transmission of a physical uplink shared channel (PUSCH).
[0005] In one embodiment, the present application describes a method for wireless communication. The method includes: a user equipment (UE) sends a request or a capability indication for repeated transmission of a first physical uplink shared channel (PUSCH) to a base station; and
[0006] A repetition factor indication for repeatedly transmitting the first PUSCH is received by the UE from the base station.
[0007] In one embodiment, the present application describes a method for wireless communication. The method includes: receiving, by a base station from a user equipment (UE), a request or a capability indication for repeating transmission of a first physical uplink shared channel (PUSCH); and
[0008] The base station sends a repetition factor indication for repeatedly transmitting the first PUSCH to the UE.
[0009] In some other embodiments, the wireless communication device may include a memory storing instructions and a processing circuit in communication with the memory. When the processing circuit executes the instructions, the processing circuit is configured to perform the above method.
[0010] In some other embodiments, the wireless communication device may include a memory storing instructions and a processing circuit in communication with the memory. When the processing circuit executes the instructions, the processing circuit is configured to perform the above method.
[0011] In some other embodiments, a computer-readable medium includes instructions that, when executed by a computer, cause the computer to perform the above method.
[0012] The above-mentioned aspects and other aspects and their implementations are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] Figure 1A An example of a wireless communication system including a radio network node and one or more user equipments is shown.
[0014] Figure 1B A schematic diagram of one non-limiting embodiment for wireless communication is shown.
[0015] Figure 1C A schematic diagram of another non-limiting embodiment for wireless communication is shown.
[0016] Figure 1D A schematic diagram of yet another non-limiting embodiment for wireless communication is shown.
[0017] Figure 2 An example of a network node is shown.
[0018] Figure 3 An example of a user device is shown.
[0019] Figure 4 A flow chart of a wireless communication method is shown.
[0020] Figure 5 A flow chart of another wireless communication method is shown. DETAILED DESCRIPTION
[0021] The present application will now be described in detail hereinafter with reference to the accompanying drawings, which form a part of the present application and show by way of illustration specific examples of embodiments. However, it should be noted that the present application may be embodied in a variety of different forms and, therefore, the subject matter covered or claimed is intended to be construed as not being limited to any embodiment set forth below.
[0022] Throughout the specification and claims, terms may have nuanced meanings that are suggested or implied in the context rather than explicitly stated. Similarly, the phrases "in one embodiment" or "in some embodiments" used herein do not necessarily refer to the same embodiment, and the phrases "in another embodiment" or "in other embodiments" used herein do not necessarily refer to different embodiments. The phrases "in one implementation" or "in some implementations" used herein do not necessarily refer to the same implementation, and the phrases "in another implementation" or "in other implementations" used herein do not necessarily refer to different implementations. For example, the claimed subject matter includes all or part of a combination of exemplary embodiments or implementations.
[0023] In general, terms can be understood at least in part from their use in context. For example, terms used herein, such as "and", "or", "and / or", can include multiple meanings, which can depend at least in part on the context in which the terms are used. Typically, "or", if used in an associative list, such as A, B, or C, means A, B, and C, which are used here for inclusion, and A, B, or C, which are used here only for exclusion. In addition, the terms "one or more" or "at least one" used herein, depending at least in part on the context, can be used to describe any feature, structure, or characteristic in a singular sense, or can be used to describe a combination of features, structures, and characteristics in a plural sense. Similarly, terms such as "one", "an", or "said", depending at least in part on the context, can also be understood to convey singular or plural usage. In addition, also at least in part on the context, the term "based on" or "determined by..." can be understood to not necessarily be intended to represent a set of exclusive factors, but rather to allow for the presence of other factors that are not necessarily explicitly described.
[0024] The present application describes methods and apparatus for indicating and / or configuring repeated transmissions of a Physical Uplink Shared Channel (PUSCH).
[0025] Next generation (NG) or fifth generation (5G) wireless communications can provide a range of features, from fast downloads to support for real-time low-latency communications. Next generation (NG) mobile communication systems are moving the world towards an increasingly connected and networked society. In order to meet increasing demands, new generation mobile communication technologies (e.g., new radio (NR), 5G, 6G) are developing support for enhanced coverage, because coverage is one of the key factors that operators consider when commercializing cellular communication networks, and coverage directly affects service quality as well as capital expenditure (CAPEX) and operating expenses (OPEX).
[0026] Among the physical channels used for uplink transmission, PUSCH may be one of the potential coverage bottleneck channels and needs to be enhanced accordingly. Repeated transmission is one of the effective ways to improve coverage. In some embodiments, for PUSCH during the initial access process, that is, the initial transmission of Msg.3 of PUSCH scheduled by random access response (RAR) uplink (UL) grant and the retransmission of Msg.3 of PUSCH scheduled by downlink control information (DCI) format 0_0 with cyclic redundancy check (CRC) scrambled by temporary cell radio network temporary identity (TC-RNTI), a repeated transmission scheme may be specified. In some implementations, repeated transmission may be supported for PUSCH after radio resource control (RRC) reconfiguration. Various conditions / problems may be associated with repeated transmission of PUSCH after initial access and before receiving the RRC reconfiguration message, and therefore, the coverage of PUSCH transmission during this period may still be a bottleneck.
[0027] The present application describes a method, a wireless communication apparatus, a wireless communication node, a wireless device and / or a wireless system for indicating and / or configuring repeated transmission of a PUSCH, and solves at least one of the above conditions / problems, such as how to support repeated transmission of a PUSCH, how to identify that a UE has repeated transmission capability, how to indicate the number of repetitions, etc. Using various embodiments of the present application, repeated transmission of a PUSCH can be effectively triggered and / or requested; relevant UE capabilities can be reported in time for PUSCH transmission before RRC reconfiguration; and a repetition factor can be indicated for PUSCH transmission. Effective support for repeated transmission of bottleneck PUSCH can improve overall coverage and network efficiency.
[0028] Figure 1A A wireless communication system 100 is shown that includes a core network (CN) 110, a radio access network (RAN) 130, and one or more user equipment (UE) (152, 154, and 156). The RAN 130 may include a wireless network base station or a NG radio access network (NG-RAN) base station or node, which may include a Node B (NB, e.g., gNB) in a mobile communication environment. In one implementation, the core network 110 may include a 5G core network (5GC), and the interface 125 may include a new generation (NG) interface.
[0029] refer to Figure 1A, the first UE 152 may wirelessly receive one or more downlink communications 142 from the RAN 130 and wirelessly send one or more uplink communications 141 to the RAN 130. Similarly, the second UE 154 may wirelessly receive downlink communications 144 from the RAN 130 and wirelessly send uplink communications 143 to the RAN 130; and the third UE 156 may wirelessly receive downlink communications 146 from the RAN 130 and wirelessly send uplink communications 145 to the RAN 130. For example, but not limitation, the downlink communications may include a physical downlink shared channel (PDSCH) or a physical downlink control channel (PDCCH), and the uplink communications may include a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).
[0030] In some implementations, NR introduces a basic scheme to support initial access in the first frequency range (FR1, below 6GHz band) and the second frequency range (FR2, above 6GHz band). One of the steps is the transmission of PRACH, which can also be called message 1 (Msg1). The relevant schemes include different PRACH formats, PRACH resource configuration, the relationship between SSB (synchronization signal / PBCH block) and PRACH timing, PRACH retransmission mechanism, PRACH power control mechanism, etc.
[0031] In some embodiments, reference Figure 1B, an example of a RACH process is shown. The UE may transmit a preamble in a PRACH opportunity (RO) based on the configuration of the PRACH transmission and the SSB it selects. In this step, when the transmit-receive correspondence on the UE side can be guaranteed, there may be a fixed mapping between the UE's receive beam (Rx beam) and the UE's transmit beam (Tx beam). A unique Tx beam may then be determined based on its reception of the SSB. Specifically, the UE may try to use different Rx beams to receive the SSB from the base station (BS) and determine the best or suitable Rx beam (e.g., with the highest reference signal received power (RSRP)). The best or suitable Tx beam is then determined based on the best or suitable Rx beam. The RO for transmitting the PRACH may be determined based on the relationship between the SSB and the PO. Based on this relationship, the BS may determine the SSB that the UE may select. The same beam can be used to transmit subsequent downlink (DL) transmissions, including message 2 (Msg.2) and message 4 (Msg.4), message 2 can also be called RAR, and message 4 is a PDSCH with a UE contention resolution indicator. According to the traditional RACH process, the RAR can be received within the RAR window after the PRACH is transmitted. The RAR window starts at the first symbol of the earliest control resource set (CORESET) after the end of the PRACH transmission, where the UE is configured to receive the PDCCH for the Type1-PDCCH CSS set. The received PDCCH can then schedule the PDSCH carrying the RAR, where the RAR uplink (UL) grant can be obtained. The RAR UL grant is used to schedule message 3PUSCH (Msg.3PUSCH). When the BS successfully receives Msg.3PUSCH, it sends Msg.4 to the UE. The above process can be called a 4-step RACH process, which is typically applied to the initial access process. In order to improve the coverage of the process, Msg.3PUSCH has supported repeated transmission.
[0032] In some implementations, reference Figure 1C, after the UE performs the 4-step RACH process, the BS may schedule another PUSCH transmission, which may be referred to as message 5 (Msg.5), to complete the radio resource control (RRC) setup. Higher layer signaling RRCsetupcomplete may be carried in Msg.5PUSCH (Msg.5), which is scheduled by DCI format 0_0 with CRC scrambled by the cell RNTI (C-RNTI) and cannot be rescheduled. This means that after implementing Msg.3PUSCH repetition, Msg.5 may become a coverage bottleneck. In some implementations, Msg.5PUSCH (182) may not be scheduled by PUSCH repetition due to some or all of the following reasons: PUSCH scheduled by DCI format 0_0 scrambled by C-RNTI does not support PUSCH repetition; and / or even if supported, the NW does not know whether the UE has such capability before Msg.5 transmission.
[0033] In some implementations, PUSCH repetition may be a UE capability, that is, the BS may schedule PUSCH transmission with repetition only when the UE reports that it supports the capability or the UE requests repetition transmission. For Msg.3 PUSCH repetition, including initial transmission and / or retransmission, some specific PRACH resources (e.g., preamble, RO, etc.) are configured to the UE. When the UE uses the resources for PRACH transmission, the BS may know that the UE supports Msg.3 PUSCH repetition transmission or the UE requests Msg.3 PUSCH repetition transmission.
[0034] In some embodiments, reference Figure 1D , in response to receiving the higher layer parameter 'UECapabilityEnquiry' from the BS, the UE may report its capabilities by transmitting another PUSCH carrying the higher layer parameter 'UECapabilityInformation'. The BS may configure transmission parameters related to PUSCH repetition, as a non-limiting example, by the pusch-AggregationFactor of RRCReconfiguration, and indicate PUSCH repetition by DCI. This method may be used for PUSCH after RRCReconfiguration. When the UE expects to use repeated transmission for PUSCH carrying 'UECapabilityInformation', the capability report should be earlier than this.
[0035] The present application describes a method, a wireless communication apparatus, a wireless communication node, a wireless device and / or a wireless system for indicating and / or configuring repeated transmission of a PUSCH, wherein for a PUSCH transmitted before RRCReconfiguration and not scheduled by a RAR UL grant or DCI format 0-0 with a CRC scrambled by a TC-RNTI, repeated transmission for such a PUSCH can be supported. Typically, such a PUSCH can be a Msg.5PUSCH (carrying RRCSetupComplete) or a PUSCH carrying "UECapabilityInformation".
[0036] Figure 2 An exemplary wireless access network or wireless communication base station 200 is shown. The base station 200 may include radio transmit / receive (Tx / Rx) circuitry 208 for transmitting / receiving communications with one or more UEs and / or one or more other base stations. The base station may also include network interface circuitry 209 for communicating the base station with other base stations and / or a core network (e.g., optical or wired interconnects, Ethernet, and / or other data transmission media / protocols). The base station 200 may optionally include an input / output (I / O) interface 206 to communicate with an operator or the like.
[0037] The base station may also include system circuitry 204. System circuitry 204 may include a processor 221 and / or a memory 222. Memory 222 may include an operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for one or more of processors 124 to perform functions of the base station. Parameters 228 may include parameters for supporting execution of instructions 226. For example, the parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.
[0038] Figure 3An exemplary user equipment (UE) 300 is shown. UE 300 may be a mobile device, such as a smart phone or a mobile communication module provided in a vehicle. UE 300 may include a communication interface 302, a system circuit 304, an input / output interface (I / O) 306, a display circuit 308, and a memory 309. The display circuit may include a user interface 310. System circuit 304 may include any combination of hardware, software, firmware, or other logic / circuits. System circuit 304 may be implemented, for example, with one or more systems on a chip (SoC), application integrated circuits (ASICs), discrete analog and digital circuits, and other circuits. System circuit 304 may be part of the implementation of any desired functionality in UE 300. In this regard, the system circuit 304 may include logic to facilitate, for example, decoding and playing music and videos, such as MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections, such as Internet connections; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 310. The user interface 310 and the input / output (I / O) interface 306 may include a graphical user interface, a touch-sensitive display, tactile feedback or other tactile output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Other examples of the I / O interface 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, universal serial bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of inputs.
[0039] refer to Figure 3, the communication interface 302 may include a radio frequency (RF) transmit (Tx) and receive (Rx) circuit 316 that handles the transmission and reception of signals through one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceiver may be a wireless transceiver that includes modulation / demodulation circuits, digital-to-analog converters (DACs), shaping tables, analog-to-digital converters (ADCs), filters, waveform shapers, filters, preamplifiers, power amplifiers, and / or other logic for transmitting and receiving through one or more antennas or (for some devices) through a physical (e.g., wired) medium. The signals sent and received may follow any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), frequency channels, bit rates, and encodings. As a specific example, the communication interface 302 may include a transceiver that supports transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA) +, 4G / Long Term Evolution (LTE), and 5G standards. However, the techniques described below may be applicable to other wireless communication technologies, whether produced by the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies.
[0040] refer to Figure 3 , the system circuit 304 may include one or more processors 321 and a memory 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to implement the desired functions of the UE 300. The parameters 328 may provide and specify configuration and operating options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G, or other data that the UE 300 will send or has received through the communication interface 302. In various embodiments, the system power for the UE 300 may be provided by a power storage device such as a battery or a transformer.
[0041] The present application describes various embodiments of methods and apparatus for indicating and / or configuring repeated transmission of a PUSCH, which may be partially or completely described in the above Figure 2 and Figure 3 The wireless network base station (or referred to as a wireless communication node) and / or the user equipment (or referred to as a wireless communication device) described in the present invention is implemented on the wireless network base station (or referred to as a wireless communication node) and / or the user equipment (or referred to as a wireless communication device).
[0042] In various embodiments, Figure 4A flow chart of a method 400 for wireless communication is shown. The method 400 may include some or all of the following steps: step 410, a user equipment (UE) sends a request or capability indication for repeated transmission of a first physical uplink shared channel (PUSCH) to a base station; and / or step 420, the UE receives a repetition factor indication for repeated transmission of a first PUSCH from the base station.
[0043] In some implementations, method 400 may also include sending, by the UE, a repetition of the first PUSCH transmission to the base station after sending the second PUSCH transmission and / or before sending the third PUSCH transmission; wherein the second PUSCH transmission includes one of a PUSCH scheduled by a random access response (RAR) uplink (UL) grant and / or a PUSCH scheduled by a downlink control information (DCI) format 0_0 having a cyclic redundancy check (CRC) scrambled by a temporary cell-radio network temporary identifier (TC-RNTI), or the third PUSCH transmission includes a PUSCH carrying radio resource control (RRC) reconfiguration completion information.
[0044] In various embodiments, Figure 5 A flow chart of a method 500 for wireless communication is shown. The method 500 may include some or all of the following steps: step 510, receiving, by a base station, a request or capability indication for repeated transmission of a first physical uplink shared channel (PUSCH) from a user equipment UE; and / or step 520, sending, by the base station, a repetition factor indication for repeated transmission of a first PUSCH to the UE.
[0045] In some implementations, method 500 may also include: receiving, by the base station, a repetition of the first PUSCH transmission from the UE after receiving the second PUSCH transmission and / or before receiving the third PUSCH transmission; wherein the second PUSCH transmission includes a PUSCH scheduled by a random access response (RAR) uplink (UL) grant, or one of a PUSCH scheduled by a downlink control information (DCI) format 0_0 having a cyclic redundancy check (CRC) scrambled by a temporary cell radio network temporary identifier (TC-RNTI), and / or the third PUSCH transmission includes a PUSCH carrying radio resource control (RRC) reconfiguration completion information.
[0046] In some embodiments, in a combination of part or all of one or more embodiments or examples described in the present application, the first PUSCH transmission includes at least one of the following: a PUSCH carrying RRC setup completion information, a PUSCH carrying UE capability information, a PUSCH scheduled by DCI format 0_0 with CRC (wherein the CRC is scrambled by cell RNTI (C-RNTI), configuration scheduling (CS-RNTI) or modulation and coding scheme cell RNTI (MCS-C-RNTI)), and / or a PUSCH scheduled by DCI format 0_1 with CRC (wherein the CRC is scrambled by cell RNTI (C-RNTI), configuration scheduling (CS-RNTI) or modulation and coding scheme cell RNTI (MCS-C-RNTI)).
[0047] In some embodiments, in a combination of part or all of one or more embodiments or examples described in the present application, the UE sends a request or capability indication for repeated transmission of a first PUSCH in response to at least one of the following trigger conditions: a synchronization signal (SS) reference signal received power (RSRP) measured by the UE is lower than an RSRP threshold, the UE has requested repeated transmission of a second PUSCH, and / or repeated transmission of a second PUSCH is being scheduled for the UE.
[0048] In some embodiments, in a combination of part or all of one or more embodiments or examples described in the present application, the RSRP threshold is scheduled by one of the following: by a higher layer parameter, and / or by a higher layer parameter and an offset value.
[0049] In some embodiments, in a combination of part or all of one or more embodiments or examples described in the present application, a request or capability indication for repeated transmission of the first PUSCH is indicated by at least one of the following: PRACH resources of a first PRACH resource set corresponding to repeated transmission of the first PUSCH, signaling information in a second PUSCH, and / or transmission status of the second PUSCH transmission and indication information in the second PUSCH.
[0050] In some implementations, in a combination of part or all of one or more implementations or embodiments described in the present application, the PRACH resource includes at least one of a preamble sequence resource or a RACH opportunity resource.
[0051] In some embodiments, in a combination of part or all of one or more embodiments or examples described in the present application, the request or capability indication for repeating the transmission of the first PUSCH represented by the signaling information in the second PUSCH includes: setting the signaling information to a first value, indicating that the UE has the ability or request to repeat the transmission of the first PUSCH, and / or setting the signaling information to a second value, indicating that the UE does not have the ability or request to repeat the transmission of the first PUSCH.
[0052] In some embodiments, in a combination of part or all of one or more embodiments or examples described in the present application, the request or capability indication for repeating transmission of the first PUSCH represented by the transmission status of the second PUSCH transmission and the indication information in the second PUSCH includes at least one of the following: in response to the UE having requested to repeat transmission of the second PUSCH, no indication information is set in the second PUSCH, indicating that the UE has the capability or request to repeat transmission of the first PUSCH; in response to the UE requesting to repeat transmission of the second PUSCH, indication information is set in the second PUSCH, indicating that the UE does not have the capability or request to repeat transmission of the first PUSCH; in response to the UE not requesting to repeat transmission of the second PUSCH, no indication information is set in the second PUSCH, indicating that the UE does not have the capability or request to repeat transmission of the first PUSCH, and / or in response to the UE not requesting to repeat transmission of the second PUSCH, indication information is set in the second PUSCH, indicating that the UE has the capability or request to repeat transmission of the first PUSCH.
[0053] In some embodiments, in a combination of part or all of one or more embodiments or examples described in the present application, the request or capability indication for repeating transmission of the first PUSCH represented by the transmission status of the second PUSCH transmission and the indication information in the second PUSCH includes at least one of the following: in response to the UE having requested to repeat transmission of the second PUSCH, indicating that the UE has the capability or request to repeat transmission of the first PUSCH; in response to the UE not requesting to repeat transmission of the second PUSCH, setting the indication information in the second PUSCH to a first value, indicating that the UE does not have the capability or request to repeat transmission of the first PUSCH; and / or in response to the UE not requesting to repeat transmission of the second PUSCH, setting the indication information in the second PUSCH to a second value, indicating that the UE has the capability or request to repeat transmission of the first PUSCH.
[0054] In some embodiments, in a combination of part or all of one or more embodiments or examples described in the present application, the request or capability indication for repeating the transmission of the first PUSCH represented by the transmission status of the second PUSCH transmission and the indication information in the second PUSCH includes at least one of the following: in response to the UE having requested to repeat the transmission of the second PUSCH, indicating that the UE has the capability or request to repeat the transmission of the first PUSCH; in response to the UE not requesting to repeat the transmission of the second PUSCH, the presence of indication information in the second PUSCH indicates that the UE does not have the capability or request to repeat the transmission of the first PUSCH, and / or in response to the UE not requesting to repeat the transmission of the second PUSCH, the absence of indication information in the second PUSCH indicates that the UE has the capability or request to repeat the transmission of the first PUSCH.
[0055] In some embodiments, in a combination of part or all of one or more embodiments or examples described in the present application, the request or capability indication for repeating the transmission of the first PUSCH represented by the transmission status of the second PUSCH transmission and the indication information in the second PUSCH includes at least one of the following: in response to the UE not requesting to repeat the transmission of the second PUSCH, indicating that the UE does not have the ability or request to repeat the transmission of the first PUSCH; in response to the UE having requested to repeat the transmission of the second PUSCH, setting the indication information in the second PUSCH to a first value, indicating that the UE does not have the ability or request to repeat the transmission of the first PUSCH, and / or in response to the UE not requesting to repeat the transmission of the second PUSCH, setting the indication information in the second PUSCH to a second value, indicating that the UE has the ability or request to repeat the transmission of the first PUSCH.
[0056] In some embodiments, in a combination of part or all of one or more embodiments or examples described in the present application, the request or capability indication for repeating the transmission of the first PUSCH represented by the transmission status of the second PUSCH transmission and the indication information in the second PUSCH includes at least one of the following: in response to the UE not requesting to repeat the transmission of the second PUSCH, it indicates that the UE does not have the ability or request to repeat the transmission of the first PUSCH; in response to the UE having requested to repeat the transmission of the second PUSCH, there is indication information in the second PUSCH, indicating that the UE has the ability or request to repeat the transmission of the first PUSCH, and / or in response to the UE not requesting to repeat the transmission of the second PUSCH, there is no indication information in the second PUSCH, indicating that the UE does not have the ability or request to repeat the transmission of the first PUSCH.
[0057] In some embodiments, in a combination of part or all of one or more embodiments or examples described in the present application, the UE receives a repetition factor indication for repeatedly transmitting the first PUSCH from the base station through at least one of the following: a higher layer parameter for configuring the repetition factor; a higher layer parameter for configuring the repetition factor list and signaling in the DCI for indicating the repetition factor in the repetition factor list; a higher layer parameter for configuring the list with M repetition factors and log2M most significant bits (MSBs) of the modulation and coding scheme (MCS) field in the DCI for indicating the repetition factor in the list with M repetition factors, (M is a positive integer), and / or a higher layer parameter for configuring the list with N repetition factors and signaling in the modulation and coding scheme (MCS) field in the DCI for indicating the repetition factor in the list with N repetition factors. The most significant bit (MSB), N is a positive integer, Represents the ceiling function.
[0058] In some embodiments, in a combination of part or all of one or more embodiments or examples described in the present application, in response to a higher layer parameter for configuring a list with M repetition factors (a list with M repetition factors for repeating the first PUSCH transmission) not being provided, a configured repetition factor list for repeating the second PUSCH is used to indicate the repetition factor for repeating the first PUSCH; and / or in response to both a list of M or N repetition factors for repeating the first PUSCH and a list of repetition factors for repeating the second PUSCH not being provided, a repetition factor list {1, 2, ..., M} or {1, 2 ..., N} is used to indicate the repetition factor for repeating the first PUSCH transmission.
[0059] In some embodiments, in a combination of part or all of one or more embodiments or examples described in the present application, the 5-log2M or The least significant bit (LSB) indicates an MCS index from an MCS index list for a first PUSCH transmission, a higher layer parameter is used to configure the MCS index list for the first PUSCH transmission, in response to a higher layer parameter for configuring the MCS index list (the MCS index list for the first PUSCH transmission) not being provided, the MCS index list configured for the second PUSCH transmission is used to indicate the MCS index of the first PUSCH transmission, and / or in response to both the MCS index list for the first PUSCH transmission and the MCS index list for the second PUSCH transmission being not provided, the MCS index list {0, 1, 2, ..., P-1} is used to indicate the MCS index of the first PUSCH transmission, where P is a positive integer.
[0060] Example 1
[0061] The present application describes non-limiting embodiments for defining trigger conditions for repeated transmissions. Some trigger conditions may be defined for the UE to determine whether to request repeated transmission of the PUSCH before RRC reconfiguration (i.e., before receiving a higher layer parameter carrying "RRCReconfiguration"). The PUSCH before the RRC reconfiguration may be a PUSCH carrying a higher layer parameter "RRCSetupComplete" (e.g., Msg.5PUSCH), or a PUSCH carrying a higher layer parameter "UECapabilityInformation". In some embodiments, the PUSCH is scheduled by DCI format 0_0 or DCI format 0_1 with CRC, where the CRC is scrambled by C-RNTI or CS-RNTI or MCS-RNTI.
[0062] The trigger condition may be at least one of the following methods.
[0063] For the first method, a synchronization signal (SS)-RSRP threshold is configured for the UE. The UE measures the RSRP of the SS (e.g., a secondary synchronization signal) or a reference signal (e.g., a demodulation reference signal or a channel state information reference signal of a physical broadcast channel), and determines whether the measurement result is lower than the SS-RSRP threshold. When the measurement result is lower than the SS-RSRP threshold, the UE may determine to request repeated transmission of the PUSCH before receiving the RRC reconfiguration. In some other implementations, the SS-RSRP may be referred to as a synchronization signal block (SSB)-RSRP.
[0064] In some implementations, the SS-RSRP threshold may be configured by a higher layer parameter, such as "RSRP-ThresholdMsg3", which is also used to trigger a request to repeat the Msg.3 PUSCH transmission. Alternatively, the SS-RSRP threshold may be obtained based on the higher layer parameter "RSRP-ThresholdMsg3" and an offset value. For example, the SS-RSRP threshold is equal to the value of the higher layer parameter "RSRP-ThresholdMsg3" plus the offset.
[0065] In some implementations, the SS-RSRP threshold is configured through any one of SIB1, random access response (or referred to as RAR or Msg.2), and PDSCH with UE contention resolution indicator (or referred to as Msg.4).
[0066] In some implementations, the offset value is configured through any one of SIB1, random access response (or referred to as RAR or Msg.2), PDSCH with UE contention resolution indicator (or referred to as Msg.4), or provided in the standard.
[0067] For the second method, when the UE has requested repeated transmission of Msg.3 PUSCH (i.e., through RAR UL grant or through PUSCH scheduled by DCI format 0-0 with CRC scrambled by TC-RNTI), this means that before RRC reconfiguration (i.e., before receiving higher layer parameters carrying "RRCReconfiguration"), PUSCH repeated transmission has been triggered.
[0068] In some implementations, alternatively, when a repeated transmission of Msg.3 PUSCH has been scheduled for the UE (i.e., by a RAR UL grant or by a PUSCH scheduled by DCI format 0-0 with a CRC scrambled by TC-RNTI), it indicates that the PUSCH repeated transmission has been triggered before RRC reconfiguration (i.e., before receiving higher layer parameters carrying "RRCReconfiguration").
[0069] In various embodiments, the method includes defining a triggering condition for repeated transmission of the PUSCH before RRC reconfiguration, thereby effectively triggering repeated transmission of the PUSCH.
[0070] Example 2
[0071] The present application describes non-limiting embodiments of requesting repeated transmission of PUSCH before RRC reconfiguration. Some methods may include requesting repeated transmission of PUSCH before RRC reconfiguration (i.e., before receiving a higher layer parameter carrying "RRCReconfiguration"). The PUSCH before RRC reconfiguration may be a PUSCH carrying a higher layer parameter "RRCSetupComplete" (e.g., Msg.5PUSCH), or a PUSCH carrying a higher layer parameter "UECapabilityInformation". In some implementations, the PUSCH is scheduled by DCI format 0_0 or DCI format 01_1 with CRC, where the CRC is scrambled by C-RNTI or CS-RNTI or MCS-RNTI.
[0072] A method of requesting repeated transmission of a PUSCH before RRC reconfiguration may be limited to at least one of the following methods.
[0073] For the first method, a PRACH resource set (or referred to as a first PRACH resource set) may be configured for one or more UEs for requesting repeated transmission of PUSCH before RRC reconfiguration, and the resource set includes one or more PRACH resources. The PRACH resource may be at least one of a preamble sequence resource or a RACH opportunity resource. When the UE wants to request repeated transmission of PUSCH (except Msg.3 PUSCH) before RRC reconfiguration, it may use a PRACH resource from the first PRACH resource set to transmit PRACH.
[0074] In some implementations, the first PRACH resource set for requesting repeated transmission of PUSCH before RRC reconfiguration may partially overlap with the PRACH resource set (or referred to as the second PRACH resource set) for requesting PUSCH transmission, which is scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI. When the UE selects PRACH resources from the overlapping portion between the first PRACH resource set and the second PRACH resource set, this indicates that the UE requests repeated transmission of both the PUSCH before RRC reconfiguration and the PUSCH scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI. When the UE selects a PRACH resource from the first PRACH resource set, but the PRACH resource is not included in the second PRACH resource set, this indicates that the UE only requests repeated transmission of the PUSCH before RRC reconfiguration. When the UE selects a PRACH resource from the second PRACH resource set, but the PRACH resource is not included in the first PRACH resource set, this means that the UE requests only repeated transmission of PUSCH scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI.
[0075] For the second method, repeated transmission of PUSCH before RRC reconfiguration can be requested through Msg.3PUSCH, which is scheduled by RAR UL grant or DCI format 0_0 with CRC scrambled by TC-RNTI. For non-limiting examples, signaling is included in Msg.3PUSCH for requesting repeated transmission of PUSCH before RRC reconfiguration.
[0076] In some implementations, the signaling is 1 bit. When the UE sets the value of this bit to "1", it indicates that the UE requests repeated transmission of PUSCH before RRC reconfiguration. When the UE sets the value of this bit to "0", it indicates that the UE does not request repeated transmission of PUSCH before RRC reconfiguration.
[0077] In some implementations, the signaling has two different values or states. For example, one is "request" and the other is "not request". When the UE sets the value of the signaling to "request", it means that the UE requests repeated transmission of PUSCH before RRC reconfiguration. When the UE sets the value of the signaling to "not request", it means that the UE does not request repeated transmission of PUSCH before RRC reconfiguration.
[0078] In some implementations, the presence of signaling indicates that the UE requests repeated transmission of PUSCH before RRC reconfiguration, while the absence of signaling indicates that the UE does not request repeated transmission of PUSCH before RRC reconfiguration. Therefore, the UE can indicate to the BS whether it requests repeated transmission of PUSCH before RRC reconfiguration by whether to include signaling in Msg.3PUSCH.
[0079] For the third method, the UE indicates to the BS whether to request repeated transmission of PUSCH before the new RRC configuration by using the transmission status of Msg.3 and the indication information in Msg.3PUSCH. The transmission status of Msg.3 includes repeated transmission and non-repeated transmission.
[0080] In some implementations, by default, whether to request repeated transmission of PUSCH before RRC reconfiguration is the same as whether to request repeated Msg.3PUSCH. In addition, when the UE wants to change the request status, it can add indication information in Msg.3PUSCH.
[0081] More specifically, when the UE requests repetition of Msg.3PUSCH, and when there is no additional indication information for changing the request state in Msg.3PUSCH, this indicates that the UE also requests repeated transmission of PUSCH before RRC reconfiguration. When the UE requests repetition of Msg.3PUSCH, and when there is additional indication information for changing the request state of repeated transmission of PUSCH before RRC reconfiguration in Msg.3PUSCH, this indicates that the UE does not request repeated transmission of PUSCH before RRC reconfiguration. When the UE does not request repetition of Msg.3PUSCH, and when there is no additional indication information for changing the request state in Msg.3PUSCH, this indicates that the UE does not request repeated transmission of PUSCH before RRC reconfiguration either. When the UE does not request repetition of Msg.3PUSCH, and when there is additional indication information for changing the request state of repeated transmission of PUSCH before RRC reconfiguration in Msg.3PUSCH, this indicates that the UE requests repeated transmission of PUSCH before RRC reconfiguration.
[0082] In some implementations, when the UE requests to repeat Msg.3PUSCH, this means that by default, the UE also requests repeated transmission of PUSCH before RRC reconfiguration. When the UE does not request to repeat Msg.3PUSCH, there may be additional indication information in Msg.3PUSCH to indicate whether to change the request state for repeated transmission of PUSCH before RRC reconfiguration. For example, the indication information may be "1-bit" signaling. When the UE sets the value of the bit to "0", it indicates that the request state is changed to request repeated transmission of PUSCH before RRC reconfiguration. When the UE sets the value of the bit to "1", it indicates that the UE has not changed the request state, that is, there is still no request for repeated transmission of PUSCH before RRC reconfiguration. In another example, the indication information may be two values or states, such as "request" and "not request". The UE may set the indication information to one of the values for indicating the corresponding request state for repeated transmission of PUSCH before RRC reconfiguration. In another example, the presence or absence of the indication information is used to indicate whether to change the request state. That is, the presence of the indication information indicates that the UE changes the request state to request repeated transmission of PUSCH before RRC reconfiguration. When the indication information does not exist, it indicates that the request state is not changed, that is, repeated transmission of PUSCH is still not requested before RRC reconfiguration.
[0083] In some implementations, by default, when the UE does not request to repeat Msg.3PUSCH, this means that the UE does not request to repeat transmission of PUSCH before RRC reconfiguration. When the UE requests to repeat Msg.3PUSCH, there may be additional indication information in Msg.3PUSCH to indicate whether to change the request state for repeat transmission of PUSCH before RRC reconfiguration. For example, the indication information may be "1-bit" signaling. The UE sets the value of the bit to "0", indicating that the request state is changed to not request to repeat transmission of PUSCH before RRC reconfiguration. The UE sets the value of the bit to "1", indicating that the request state is not changed, that is, the repeated transmission of PUSCH is requested before RRC reconfiguration. In another example, the indication information may be two values or states, such as "request" and "not request". The UE may set the indication information to one of the values for indicating the corresponding request state for repeat transmission of PUSCH before RRC reconfiguration. In another example, the presence or absence of the indication information is used to indicate whether to change the request state. That is, the presence of the indication information indicates that the UE changes the request state to not request repeated transmission of PUSCH before RRC reconfiguration. The absence of the indication information indicates that the request state is not changed, that is, repeated transmission of PUSCH is requested before RRC reconfiguration.
[0084] In various embodiments, the method includes requesting repeated transmission of the PUSCH before RRC reconfiguration, and thus, the repeated transmission of the PUSCH may be effectively requested.
[0085] Example 3
[0086] The present application describes a non-limiting embodiment of a UE capability report for repeated transmission of PUSCH prior to RRC reconfiguration. In some examples, the UE capability is defined for repeated transmission of PUSCH prior to RRC reconfiguration. The UE capability is separate from the ability to repeat PUSCH transmissions scheduled by RARUL grant and DCI format 0_0 with a CRC scrambled by TC-RNTI. In some implementations, PUSCH is scheduled by DCI format 0_0 or DCI format 01_1 with a CRC, where the CRC is scrambled by C-RNTI or CS-RNTI or MCS-RNTI. At least one of the following methods may be defined for UE capability reporting for repeated transmission of PUSCH prior to RRC reconfiguration.
[0087] For the first method, a PRACH resource set (or referred to as a first PRACH resource set) including one or more PRACH resources may be configured for the UE to report the UE capability of repeatedly transmitting PUSCH before RRC reconfiguration. The PRACH resource may be at least one of a preamble sequence resource or a RACH opportunity resource. When the UE wants to report the UE capability of repeatedly transmitting PUSCH before RRC reconfiguration, it may use one PRACH resource from the first PRACH resource set to transmit PRACH.
[0088] For the second method, the UE capability of repeatedly transmitting PUSCH before RRC reconfiguration can be reported through Msg.3PUSCH, which is scheduled by RAR UL grant or DCI format 0_0 with CRC scrambled by TC-RNTI. For example, signaling is included in Msg.3PUSCH for reporting the UE capability of repeatedly transmitting PUSCH before RRC reconfiguration. More specifically, the signaling is 1 bit. The UE can set the value of this bit to "1", indicating that the UE has the UE capability of repeatedly transmitting PUSCH before RRC reconfiguration. The UE can set the value of this bit to "0", indicating that the UE does not have the UE capability of repeatedly transmitting PUSCH before RRC reconfiguration.
[0089] In some implementations, the signaling has two different values or states. For example, one is "capable" and the other is "incapable". The UE may set the value of the signaling to "capable", indicating that the UE has the ability to repeat the transmission of PUSCH before RRC reconfiguration. The UE may set the value of the signaling to "incapable", indicating that the UE does not have the ability to repeat the transmission of PUSCH before RRC reconfiguration.
[0090] In some implementations, the presence of signaling indicates that the UE has the capability to repeatedly transmit PUSCH before RRC reconfiguration, while the absence of signaling indicates that the UE does not have the capability to repeatedly transmit PUSCH before RRC reconfiguration. Therefore, the UE can indicate to the BS whether it has the capability to repeatedly transmit PUSCH before RRC reconfiguration by including signaling in Msg.3PUSCH.
[0091] For the third method, the UE indicates to the BS whether it has the capability to repeatedly transmit PUSCH before RRC reconfiguration by using the transmission status of Msg.3 and the indication information in Msg.3PUSCH. The transmission status of Msg.3 includes repeated transmission and non-repeated transmission.
[0092] In some implementations, when the UE requests to repeat Msg.3PUSCH, and when there is no additional indication information for changing the capability state in Msg.3PUSCH, this indicates that the UE also has the capability of repeatedly transmitting PUSCH before RRC reconfiguration. When the UE requests to repeat Msg.3PUSCH, and when there is additional indication information for changing the capability state of repeatedly transmitting PUSCH before RRC reconfiguration in Msg.3PUSCH, this indicates that the UE does not have the capability of repeatedly transmitting PUSCH before RRC reconfiguration. When the UE does not request to repeat Msg.3PUSCH, and when there is no additional indication information for changing the capability state in Msg.3PUSCH, this indicates that the UE also does not have the capability of repeatedly transmitting PUSCH before RRC reconfiguration. When the UE does not request to repeat Msg.3PUSCH, and when there is additional indication information for changing the capability state of repeatedly transmitting PUSCH before RRC reconfiguration in Msg.3PUSCH, this indicates that the UE has the capability of repeatedly transmitting PUSCH before RRC reconfiguration.
[0093] In some implementations, when the UE requests to repeat Msg.3PUSCH, by default, this indicates that the UE also has the ability to repeat transmission of PUSCH before RRC reconfiguration. When the UE does not request to repeat Msg.3PUSCH, there will be additional indication information in Msg.3PUSCH to indicate whether it has the ability to repeat transmission of PUSCH before RRC reconfiguration. For example, the indication information can be "1-bit" signaling. The UE can set the value of this bit to "0", indicating that the UE has the ability to repeat transmission of PUSCH before RRC reconfiguration. The UE can set the value of this bit to "1", indicating that it does not have the ability to repeat transmission of PUSCH before RRC reconfiguration.
[0094] In some implementations, the indication information may be two values or states, such as “capable” and “incapable.” The UE may set the indication information to one of the values for indicating the corresponding capability state for repeatedly transmitting the PUSCH before RRC reconfiguration.
[0095] In some implementations, the presence or absence of the indication information is used to indicate whether it has the capability. That is, the presence of the indication information indicates that the UE has the capability to repeatedly transmit the PUSCH before RRC reconfiguration. The absence of the indication information indicates that it does not have the capability to repeatedly transmit the PUSCH before RRC reconfiguration.
[0096] In some implementations, the UE capability is limited to repeated transmission of PUSCH before RRC reconfiguration. The UE capability is the same as any one of the UE capability for PUSCH repetition over multiple slots, the UE capability for PUSCH repetition type A, and the UE capability for repeating PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI. When the UE capability has been reported by any of the above methods, it will not be reported in "UECapabilityInformation", or the related report by "UECapability Information" should be consistent with the UE capability reported in the above manner.
[0097] In various embodiments, the method includes a method for repeatedly transmitting a UE capability report for a PUSCH before an RRC reconfiguration, so that the UE capability can be reported efficiently.
[0098] Example 4
[0099] The present application describes a non-limiting embodiment of a repetition factor indication for repeated transmission of PUSCH before RRC reconfiguration. Some methods may be defined to indicate the repetition factor from the BS to the UE for transmitting PUSCH before RRC reconfiguration. The repetition factor is used to indicate the number of repetitions of the PUSCH transmission. The PUSCH before RRC reconfiguration may be a PUSCH (e.g., Msg.5PUSCH) carrying a higher layer parameter "RRCSetupComplete", or a PUSCH carrying a higher layer parameter "UECapabilityInformation". In some implementations, the PUSCH is scheduled by DCI format 0_0 or DCI format 01_1 with CRC, where the CRC is scrambled by C-RNTI or CS-RNTI or MCS-RNTI. The repetition factor for repeated transmission of PUSCH may be indicated by at least one of the following methods.
[0100] For the first method, a higher layer parameter may be used to configure the repetition factor. In some examples, the higher layer parameter is transmitted before the RRC reconfiguration. In some examples, the higher layer parameter may be included in a PDSCH carrying RRCSetup or a PDSCH with a UE contention resolution identifier (e.g., Msg.4PDSCH). In some examples, the higher layer parameter may be included in a system information block 1 (SIB1) PDSCH.
[0101] For the second method, a higher layer parameter (e.g., in BWP-UplinkCommon or Msg.4PDSCH) can be used to configure a time domain resource allocation list (or time domain resource allocation table) for a PUSCH with a number of repetitions. For example, the higher layer parameter may be a "PUSCH TimeDomainResourceAllocationList", which includes "numberOfRepetitions". Then, each time domain resource allocation (TDRA) in the time domain resource allocation list may correspond to the number of repetitions. Then, a DCI format (e.g., DCI format 0-0, DCI format 0-1, or DCI format 0-2) may be used to schedule a PUSCH with repetitions. The repetition factor for the PUSCH is indicated by the time domain resource allocation field in the DCI. The PUSCH may be a PUSCH carrying a higher layer parameter "RRCSetupComplete" (e.g., Msg.5PUSCH), or a PUSCH carrying a higher layer parameter "UECapabilityInformation".
[0102] For a non-limiting example, a higher layer parameter "PUSCH-TimeDomainResourceAllocationList" includes up to X (for a non-limiting example, X=16) different configurations, such as PUSCH-TimeDomainResourceAllization. In each configuration, there is a parameter, such as numberOfRepetitions, which is used to indicate the repetition factor of the PUSCH transmission. Some candidate values of the repetition factor can be predefined, such as {n1, n2, n3, n4, n7, n8, n12, n16, n20, n24, n28, n32, spare4, spare3, spare2, spare1}, where n1 indicates that the repetition factor is equal to 1, which also means no repetition. n2 indicates that the repetition factor is equal to 2, etc.
[0103] For another non-limiting example shown in Table 1, 16 different configurations can be provided by PUSCH-TimeDomainResourceAllocationList. A time domain resource allocation field with 4 bits may be present in the DCI format. The values of these four bits may refer to the indexes in Table 1. More specifically, when the value of the time domain resource allocation field for scheduling PUSCH in the DCI format is set to 0010, a configuration with an index of 2 may be used for PUSCH transmission. Then, the repetition factor of this PUSCH transmission is 4. When the value of the time domain resource allocation field for scheduling PUSCH in the DCI format is set to 0111, a configuration with an index of 7 may be used for PUSCH transmission. The repetition factor of this PUSCH transmission is 8.
[0104] Table 1: Various configurations for repeat factor indication
[0105]
[0106] For the third method, a repetition factor list can be provided to the UE by a higher layer parameter (e.g., in BWP UplinkCommon, or SIB1, or Msg.4PDSCH), the repetition factor list having a maximum of M (e.g., M=4) values for PUSCH transmission before RRC reconfiguration or for PUSCH transmission scheduled via DCI format 0_0 with CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.
[0107] In some embodiments, when the UE requests repeated transmission of PUSCH before RRC reconfiguration, the UE transmits PUSCH on Y time slots, where Y is determined by the log2 of the MCS field of DCI format 0_0. M(For example, 2) MSBs indicate that the DCI format 0_0 comes from the repetition factor list, or, if the repetition factor list is not provided, from the RRC signaling "numberOfMsg3-RepetitionsList", or, if neither numberOfMsg3-RepetitionsList nor the repetition factor list is provided, from {1, 2, 3, ..., M} (for example, {1, 2, 3, 4}). The higher layer parameter numberOfMsg3-RepetitionsList is used to indicate the repetition factor list of Msg.3PUSCH repetition.
[0108] In some implementations, a repetition factor list may be provided to the UE by a higher layer parameter (e.g., in BWP UplinkCommon, SIB1, or Msg.4PDSCH) with a maximum of N (e.g., N=3) values for PUSCH transmissions before RRC reconfiguration or for PUSCH transmissions scheduled via DCI format 0_0 with a CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI. When the UE requests repeated transmission of PUSCH before RRC reconfiguration, the UE transmits PUSCH on Y slots, where Y is determined by the MCS field of DCI format 0_0. (For example, 2) MSBs indicate that the DCI format 0_0 comes from a repetition factor list, or, if no repetition factor list is provided, from RRC signaling "numberOfMsg3-RepetitionsList", or, if neither numberOfMsg3-RepetitionsList nor a repetition factor list is provided, from {1, 2, 3, ..., N} (for example, {1, 2, 3}). The higher layer parameter numberOfMsg3-RepetitionsList is used to indicate the repetition factor list for Msg.3 PUSCH repetition.
[0109] In some implementations, a list of MCS indices with up to eight values may be provided to the UE by higher layer parameters (e.g., in BWP UplinkCommon, or SIB1, or Msg.4PDSCH) for PUSCH transmissions before RRC reconfiguration, or for PUSCH transmissions scheduled by DCI format 0_0 with CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI. The UE may select the MCS index from the 5-log2M or 5-log2M value of the MCS field of DCI format 0_0. The MCS for PUSCH transmission is determined by (e.g., 3) LSBs. Based on the configured MCS index list (e.g., {0, 1, 2, ..., P-1}), or if no MCS index list is configured, based on the higher layer parameter mcs-Msg3-Repetitions, or when neither the MCS index list nor mcs-Msg3-Repetitions is provided, the 3 LSBs of the MCS information field of DCI format 0_0 with a CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI provide a code point to determine the MSC index. Wherein, the higher layer parameter mcs-Msg3-Repetitions is used to indicate the MSC index list for Msg.3 PUSCH repetitions.
[0110] In some implementations, at least some bits of the information field of DCI format 0-0 may be used to indicate a repetition factor. The information field includes frequency domain resource allocation, time domain resource allocation, and / or at least one of a HARQ process number and a TPC command for a scheduled PUSCH.
[0111] In various embodiments, the method includes a factor indication, so that the number of repetitions can be effectively indicated without requiring additional signaling overhead and without significantly increasing the detection complexity of the UE.
[0112] The method in various embodiments includes at least one of trigger condition definition, request for repeated transmission of PUSCH, UE capability report for repeated transmission of PUSCH, and repetition factor indication, which can also be used for PUSCH scheduled by DCI format 0-0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI, whether or not before RRC reconfiguration. In some implementations, a higher layer parameter (e.g., in SIB1 or Msg.4 or UE-specific RRC signaling or MAC layer signaling) indicates whether one of the above methods can be used for PUSCH scheduled by DCI format 0-0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI. In some implementations, whether one of the above methods can be used for PUSCH scheduled by DCI format 0-0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI is related to UE reporting, for example, when the UE reports corresponding UE capabilities or requests, the method described in the present application can be used for PUSCH scheduled by DCI format 0-0 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI.
[0113] The present application describes methods, apparatus, and computer-readable media for wireless communications. The present application solves the problem of repeated transmission of PUSCH. The methods, apparatus, and computer-readable media described in the present application can facilitate the performance of wireless communications by indicating and / or configuring repeated transmission of a physical uplink shared channel (PUSCH), thereby improving efficiency and overall performance. The methods, apparatus, and computer-readable media described in the present application can improve the overall efficiency of a wireless communication system.
[0114] References to features, advantages, or similar language in this specification do not mean that all features and advantages that can be achieved by the present solution should be included or included in any single implementation thereof. Instead, language referring to features and advantages is understood to mean that a particular feature, advantage, or characteristic described in conjunction with an embodiment is included in at least one embodiment of the present solution. Therefore, discussions of features, advantages, and similar language throughout the specification may, but do not necessarily, refer to the same embodiment.
[0115] In addition, the features, advantages and characteristics of the present solution can be combined in any suitable manner in one or more embodiments. Based on the description herein, a person of ordinary skill in the relevant art will recognize that the present solution can be implemented without one or more specific features or advantages of a particular embodiment. In other cases, additional features and advantages can be realized in a particular embodiment that is not presented in all embodiments of the present solution.
Claims
1. A method for wireless communication, comprising: A user equipment (UE) sends a request or a capability indication for repeated transmission of a first physical uplink shared channel (PUSCH) to a base station; as well as The user equipment receives, from the base station, a repetition factor indication for repeating the transmission of the first physical uplink shared channel.
2. The method of claim 1, further comprising: After sending the second physical uplink shared channel transmission or before sending the third physical uplink shared channel transmission, the user equipment transmits a repetition of the first physical uplink shared channel transmission to the base station; wherein, The second physical uplink shared channel transmission includes one of a physical uplink shared channel scheduled by a random access response (RAR) uplink (UL) grant, or a physical uplink shared channel scheduled by a downlink control information (DCI) format 0_0 with a cyclic redundancy check (CRC) scrambled by a temporary cell radio network temporary identifier (TC-RNTI), or The third physical uplink shared channel transmission includes a physical uplink shared channel carrying radio resource control (RRC) reconfiguration completion information.
3. A method for wireless communication, comprising: Receiving, by a base station, a request or a capability indication for repeating transmission of a first physical uplink shared channel (PUSCH) from a user equipment (UE); as well as The base station sends a repetition factor indication for repeatedly transmitting the first physical uplink shared channel to the user equipment.
4. The method of claim 3, further comprising: After receiving the second physical uplink shared channel transmission or before receiving the third physical uplink shared channel transmission, the base station receives a repetition of the first physical uplink shared channel transmission from the user equipment; wherein, The second physical uplink shared channel transmission includes one of a physical uplink shared channel scheduled by a random access response (RAR) uplink (UL) grant, or a physical uplink shared channel scheduled by a downlink control information (DCI) format 0_0 with a cyclic redundancy check (CRC) scrambled by a temporary cell radio network temporary identifier (TC-RNTI), or The third physical uplink shared channel transmission includes a physical uplink shared channel carrying radio resource control (RRC) reconfiguration completion information.
5. The method according to any one of claims 1 to 4, wherein: The first physical uplink shared channel transmission includes at least one of the following: A physical uplink shared channel that carries radio resource control setup completion information. A physical uplink shared channel that carries user equipment capability information. A physical uplink shared channel scheduled by downlink control information format 0_0 with cyclic redundancy check scrambled by a cell radio network temporary identity (C-RNTI), a configuration scheduling (CS-RNTI), or a modulation and coding scheme cell radio network temporary identity (MCS-C-RNTI), or A physical uplink shared channel scheduled by downlink control information format 0_1 with a cyclic redundancy check scrambled by a cell radio network temporary identity (C-RNTI), a configuration scheduling (CS-RNTI) or a modulation and coding scheme cell radio network temporary identity (MCS-C-RNTI).
6. The method according to any one of claims 1 to 4, wherein: In response to at least one of the following triggering conditions, the user equipment sends the request or the capability indication for repeatedly transmitting the first physical uplink shared channel: A synchronization signal (SS) reference signal received power (RSRP) measured by the user equipment is lower than a reference signal received power threshold, The user equipment has requested repeated transmission of the second physical uplink shared channel, or Repeated transmission of the second physical uplink shared channel is scheduled for the user equipment.
7. The method of claim 6, wherein: The reference signal received power threshold is scheduled in one of the following ways: by higher-level parameters, or Consists of high-level parameters and offset values.
8. The method according to any one of claims 1 to 4, wherein: The request or the capability indication for repeatedly transmitting the first physical uplink shared channel is indicated by at least one of the following: a PRACH resource in a first PRACH resource set corresponding to repeated transmission of the first physical uplink shared channel, signaling information in the second physical uplink shared channel, or The transmission status of the second physical uplink shared channel transmission and indication information in the second physical uplink shared channel.
9. The method of claim 8, wherein: The PRACH resource includes at least one of a preamble sequence resource or a RACH opportunity resource.
10. The method of claim 8, wherein: The request or the capability indication for repeatedly transmitting the first physical uplink shared channel represented by the signaling information in the second physical uplink shared channel includes: The signaling information is set to a first value, indicating that the user equipment has the capability or request to repeatedly transmit the first physical uplink shared channel, or The signaling information is set to a second value, indicating that the user equipment does not have the ability or request to repeatedly transmit the first physical uplink shared channel.
11. The method of claim 8, wherein: The request or the capability indication for repeatedly transmitting the first physical uplink shared channel represented by the transmission state transmitted by the second physical uplink shared channel and the indication information in the second physical uplink shared channel includes at least one of the following: In response to the user equipment having requested to repeatedly transmit the second physical uplink shared channel, no indication information is set in the second physical uplink shared channel, indicating that the user equipment has a capability or request for repeatedly transmitting the first physical uplink shared channel; In response to the user equipment having requested to repeatedly transmit the second physical uplink shared channel, setting indication information in the second physical uplink shared channel, indicating that the user equipment does not have a capability or request for repeatedly transmitting the first physical uplink shared channel; In response to the user equipment not requesting repeated transmission of the second physical uplink shared channel, not setting indication information in the second physical uplink shared channel, indicating that the user equipment does not have a capability or request for repeated transmission of the first physical uplink shared channel; or In response to the user equipment not requesting repeated transmission of the second physical uplink shared channel, indication information is set in the second physical uplink shared channel, indicating that the user equipment has a capability or request for repeated transmission of the first physical uplink shared channel.
12. The method of claim 8, wherein: The request or the capability indication for repeatedly transmitting the first physical uplink shared channel represented by the transmission state transmitted by the second physical uplink shared channel and the indication information in the second physical uplink shared channel includes at least one of the following: In response to the user equipment having requested to repeatedly transmit the second physical uplink shared channel, it indicates that the user equipment has a capability or request for repeatedly transmitting the first physical uplink shared channel; In response to the user equipment not requesting repeated transmission of the second physical uplink shared channel, setting the indication information in the second physical uplink shared channel to a first value, indicating that the user equipment does not have a capability or request for repeated transmission of the first physical uplink shared channel; or In response to the user equipment not requesting repeated transmission of the second physical uplink shared channel, setting the indication information in the second physical uplink shared channel to a second value, indicating that the user equipment has a capability or request for repeated transmission of the first physical uplink shared channel.
13. The method of claim 8, wherein: The request or the capability indication for repeatedly transmitting the first physical uplink shared channel represented by the transmission state transmitted by the second physical uplink shared channel and the indication information in the second physical uplink shared channel includes at least one of the following: In response to the user equipment having requested to repeatedly transmit the second physical uplink shared channel, it indicates that the user equipment has a capability or request for repeatedly transmitting the first physical uplink shared channel, In response to the user equipment not requesting repeated transmission of the second physical uplink shared channel, the second physical uplink shared channel contains the indication information, indicating that the user equipment does not have a capability or request for repeated transmission of the first physical uplink shared channel, or In response to the user equipment not requesting repeated transmission of the second physical uplink shared channel, the indication information does not exist in the second physical uplink shared channel, indicating that the user equipment has a capability or request for repeated transmission of the first physical uplink shared channel.
14. The method of claim 8, wherein: The request or the capability indication for repeatedly transmitting the first physical uplink shared channel represented by the transmission state transmitted by the second physical uplink shared channel and the indication information in the second physical uplink shared channel includes at least one of the following: In response to the user equipment not requesting repeated transmission of the second physical uplink shared channel, it indicates that the user equipment does not have a capability or request for repeated transmission of the first physical uplink shared channel, In response to the user equipment having requested to repeatedly transmit the second physical uplink shared channel, setting the indication information in the second physical uplink shared channel to a first value, indicating that the user equipment does not have a capability or request for repeatedly transmitting the first physical uplink shared channel, or In response to the user equipment not requesting repeated transmission of the second physical uplink shared channel, the indication information in the second physical uplink shared channel is set to a second value, indicating that the user equipment has a capability or request for repeated transmission of the first physical uplink shared channel.
15. The method of claim 8, wherein: The request or the capability indication for repeatedly transmitting the first physical uplink shared channel represented by the transmission state transmitted by the second physical uplink shared channel and the indication information in the second physical uplink shared channel includes at least one of the following: In response to the user equipment not requesting repeated transmission of the second physical uplink shared channel, it indicates that the user equipment does not have a capability or request for repeated transmission of the first physical uplink shared channel, In response to the user equipment having requested to repeatedly transmit the second physical uplink shared channel, the second physical uplink shared channel contains the indication information, indicating that the user equipment has a capability or request for repeatedly transmitting the first physical uplink shared channel, or In response to the user equipment not requesting repeated transmission of the second physical uplink shared channel, no indication information exists in the second physical uplink shared channel, indicating that the user equipment does not have a capability or request for repeated transmission of the first physical uplink shared channel.
16. The method according to any one of claims 1 to 4, wherein: The user equipment receives, from the base station, a repetition factor indication for repeatedly transmitting the first physical uplink shared channel in at least one of the following manners: Higher layer parameters for configuring the repetition factor; higher layer parameters for configuring a repetition factor list and signalling in downlink control information for indicating a repetition factor in said repetition factor list; log2M most significant bits (MSBs) of a higher layer parameter for configuring a list with M repetition factors and a modulation and coding scheme (MCS) field in downlink control information for indicating a repetition factor in the list with M repetition factors, where M is a positive integer, or A higher layer parameter for configuring a list with N repetition factors and a modulation and coding scheme (MCS) field in downlink control information for indicating a repetition factor in a list with N repetition factors Most significant bits (MSBs), where N is a positive integer, Represents the ceiling function.
17. The method of claim 16, wherein: In response to the higher layer parameter for configuring the list with M repetition factors not being provided, indicating a repetition factor for repeating transmission of the first physical uplink shared channel using a configured repetition factor list for repeating transmission of the second physical uplink shared channel; or In response to the fact that neither a list of M or N repetition factors for repeatedly transmitting the first physical uplink shared channel nor a list of repetition factors for repeatedly transmitting the second physical uplink shared channel is provided, a repetition factor list {1, 2, ..., M} or {1, 2, ..., N} is used to indicate a repetition factor for repeating the first physical uplink shared channel transmission.
18. The method of claim 17, wherein: 5-log2M or 5-log2M of the modulation and coding scheme field in the downlink control information a least significant bit (LSB) indicating a modulation and coding scheme index from a modulation and coding scheme index list for transmission of the first physical uplink shared channel; The higher layer parameter is used to configure a modulation and coding scheme index list for the first physical uplink shared channel transmission, In response to the higher layer parameter for configuring a modulation and coding scheme index list not being provided, the modulation and coding scheme index list configured for the second physical uplink shared channel transmission is used to indicate a modulation and coding scheme index of the first physical uplink shared channel transmission, wherein the modulation and coding scheme index list is used for the first physical uplink shared channel transmission, or In response to the fact that neither the modulation and coding scheme index list for the first physical uplink shared channel transmission nor the modulation and coding scheme index list for the second physical uplink shared channel transmission is provided, the modulation and coding scheme index list {0, 1, 2, ..., P-1} is used to indicate the modulation and coding scheme index of the first physical uplink shared channel transmission, where P is a positive integer.
19. A wireless communication device, comprising a processor and a memory, wherein: The processor is configured to read the code from the memory and execute the method according to any one of claims 1 to 18.
20. A computer program product comprising computer readable program medium code stored thereon, which, when executed by a processor, causes the processor to perform the method of any one of claims 1 to 18.
