Method, device, apparatus, medium and program product for indicating uplink shared channel
Patent Information
- Application Number
- CN202510422138.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-03
- Publication Date
- 2026-10-16
AI Technical Summary
[0004]本公开的目的在于提供一种指示上行共享信道的方法、指示上行共享信道的装置、终端设备、网络设备、存储介质和计算机程序产品,至少在一定程度上克服相关技术中多载波增强的DCI不能直接复用现有格式0_1的DCI或现有格式0_3的DCI对UL-SCH指示器的域的设计的问题
[0029] The uplink shared channel indication scheme provided by the embodiments of this disclosure, for DCIs that support scheduling multiple physical resource units and at least one physical resource unit supports scheduling multiple PUSCHs, enables the DCI to support a 1-bit UL-SCH indicator. This allows the DCI to set the UL-SCH indicator to 0 bits or 1 bit according to the actual scheduling situation, thereby meeting the UL-SCH indication requirements when scheduling different numbers of PUSCHs. This not only enables the DCI to support the function of scheduling PUSCHs that do not carry UL-SCHs, but also reduces the bit overhead of the DCI. In addition, the terminal's explicit execution of sending or not sending UL-SCH operations on the PUSCHs (a specified PUSCH among one or more PUSCHs) scheduled by the DCI based on this indicator is also beneficial to improving the accuracy of uplink data transmission.
Smart Images

Figure CN122934516A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of wireless communication technology, and in particular to a method for indicating an uplink shared channel, an apparatus for indicating an uplink shared channel, a terminal device, a network device, a computer-readable storage medium, and a computer program product. Background Technology
[0002] The multi-carrier enhancement of 3GPP (3rd Generation Partnership Project) Rel-19 (Release 19) requires the design of DCI (Downlink Control Information) that can schedule one or more cells. Each cell can schedule one or more PUSCH (Physical Uplink Shared Channel). That is, the DCI supports scheduling multiple cells, and at least one cell supports scheduling multiple PUSCH. The above DCI cannot directly reuse the design of the UL-SCH indicator field of the existing format 0_1 DCI or the existing format 0_3 DCI.
[0003] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention
[0004] The purpose of this disclosure is to provide a method, apparatus, terminal device, network device, storage medium, and computer program product for indicating an uplink shared channel, which at least to some extent overcomes the problem in the related art that multi-carrier enhanced DCI cannot directly reuse the existing format 0_1 DCI or the existing format 0_3 DCI for the design of the UL-SCH indicator field.
[0005] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.
[0006] According to one aspect of this disclosure, a method for indicating an uplink shared channel is provided, applied to a terminal device, comprising: receiving downlink control information (DCI) sent by a network device, the DCI supporting scheduling of multiple physical resource units (PRUs), at least one of the PRUs supporting scheduling of multiple physical uplink shared channels (PUSCHs), the DCI supporting an uplink shared channel UL-SCH indicator including a 1-bit bit; and transmitting or not transmitting UL-SCH based on the UL-SCH indicator for one of the PUSCHs scheduled by the DCI, or transmitting or not transmitting UL-SCH for a specified PUSCH among the multiple PUSCHs scheduled by the DCI.
[0007] In one embodiment of this disclosure, if the DCI schedules multiple PUSCHs in at least one of the physical resource units, the UL-SCH indicator is 0 bits; otherwise, the UL-SCH indicator is 1 bit.
[0008] In one embodiment of this disclosure, if the DCI schedules the maximum number of PUSCHs that can be scheduled in all the physical resource units that support scheduling, the UL-SCH indicator is 0 bits; otherwise, the UL-SCH indicator is 1 bit.
[0009] In one embodiment of this disclosure, the designated PUSCH is the earliest PUSCH scheduled by the DCI in the first physical resource unit or the earliest PUSCH that satisfies the channel state information (CSI) processing time requirement, and the first physical resource unit is the physical resource unit with the smallest unit index among the physical resource units scheduled by the DCI.
[0010] In one embodiment of this disclosure, the designated PUSCH is the earliest PUSCH among all PUSCHs scheduled by the DCI, or the earliest PUSCH that meets the CSI processing time requirement. If the earliest PUSCH includes multiple PUSCHs, then the earliest PUSCH on the physical resource unit with the smallest unit index among the physical resource units where the multiple earliest PUSCHs are located is taken as the designated PUSCH.
[0011] In one embodiment of this disclosure, if the DCI schedules multiple PUSCHs in each of the scheduled physical resource units, the UL-SCH indicator is 0 bits; if the physical resource unit scheduled by the DCI includes a second physical resource unit, and a single PUSCH is scheduled in the second physical resource unit, the UL-SCH indicator is 1 bit.
[0012] In one embodiment of this disclosure, the designated PUSCH is the PUSCH scheduled in the second physical resource unit with the smallest cell index.
[0013] In one embodiment of this disclosure, the UL-SCH indicator in the DCI is 1 bit.
[0014] In one embodiment of this disclosure, the designated PUSCH is the earliest PUSCH scheduled by the DCI in the first physical resource unit or the earliest PUSCH that satisfies the channel state information (CSI) processing time requirement, and the first physical resource unit is the physical resource unit with the smallest unit index among the physical resource units scheduled by the DCI.
[0015] In one embodiment of this disclosure, the designated PUSCH is the earliest PUSCH among all PUSCHs scheduled by the DCI, or the earliest PUSCH that meets the CSI processing time requirement. If the earliest PUSCH includes multiple PUSCHs, then the earliest PUSCH on the physical resource unit with the smallest unit index among the physical resource units where the multiple earliest PUSCHs are located is taken as the designated PUSCH.
[0016] In one embodiment of this disclosure, if the physical resource unit scheduled by the DCI includes a second physical resource unit, a single PUSCH is scheduled in the second physical resource unit, and the designated PUSCH is the PUSCH scheduled in the second physical resource unit with the smallest unit index; if the physical resource unit scheduled by the DCI does not include the second physical resource unit, the designated PUSCH is the earliest PUSCH scheduled by the DCI in the first physical resource unit or the earliest PUSCH that meets the CSI processing time requirement, and the first physical resource unit is the physical resource unit with the smallest unit index among the physical resource units scheduled by the DCI.
[0017] In one embodiment of this disclosure, if the physical resource unit scheduled by the DCI includes a second physical resource unit, a single PUSCH is scheduled in the second physical resource unit, and the designated PUSCH is the PUSCH scheduled in the second physical resource unit with the smallest unit index; if the physical resource unit scheduled by the DCI does not include the second physical resource unit, the designated PUSCH is the earliest PUSCH among all the PUSCHs scheduled by the DCI, or the earliest PUSCH that meets the CSI processing time requirement, wherein if the earliest PUSCH includes multiple PUSCHs, the earliest PUSCH in the physical resource unit with the smallest unit index among the multiple earliest PUSCHs is taken as the designated PUSCH.
[0018] In one embodiment of this disclosure, if the physical resource unit scheduled by the DCI includes a second physical resource unit, a single PUSCH is scheduled in the second physical resource unit, and the designated PUSCH is the PUSCH scheduled in the second physical resource unit with the smallest unit index; if the physical resource unit scheduled by the DCI does not include the second physical resource unit, the indication value of the UL-SCH indicator is invalid.
[0019] In one embodiment of this disclosure, if the DCI schedules a single PUSCH in a first physical resource unit among the scheduled physical resource units, the designated PUSCH is the PUSCH scheduled in the first physical resource unit, and the first physical resource unit is the physical resource unit with the smallest unit index among the physical resource units scheduled by the DCI; if the DCI schedules multiple PUSCHs in the first physical resource unit, the indication value of the UL-SCH indicator is invalid.
[0020] In one embodiment of this disclosure, the DCI supports a domain including a CSI request, the domain of which applies to the specified PUSCH.
[0021] In one embodiment of this disclosure, the physical resource unit includes a cell and / or a carrier.
[0022] According to another aspect of this disclosure, a method for indicating an uplink shared channel is provided, applied to a network device, comprising: sending a DCI to a terminal device, the DCI supporting scheduling of a plurality of physical resource units, at least one of the plurality of physical resource units supporting scheduling of a plurality of PUSCHs, the DCI supporting a UL-SCH indicator including a 1-bit UL-SCH indicator, such that the terminal device may send or not send a UL-SCH based on the UL-SCH indicator for one of the PUSCHs scheduled by the DCI, or send or not send a UL-SCH for a specified PUSCH among the plurality of PUSCHs scheduled by the DCI.
[0023] According to another aspect of this disclosure, an apparatus for indicating an uplink shared channel is provided, applied to a terminal device, comprising: a receiving module for receiving downlink control information (DCI) sent by a network device, the DCI supporting the scheduling of multiple physical resource units (PRUs), at least one of the PRUs supporting the scheduling of multiple physical uplink shared channels (PUSCHs), the DCI supporting an uplink shared channel UL-SCH indicator including a 1-bit bit; and a first transmitting module for transmitting or not transmitting UL-SCH based on the UL-SCH indicator for one of the PUSCHs scheduled by the DCI, or transmitting or not transmitting UL-SCH for a specified PUSCH among the multiple PUSCHs scheduled by the DCI.
[0024] According to another aspect of this disclosure, an apparatus for indicating an uplink shared channel is provided, applied to a network device, comprising: a second transmitting module for transmitting a DCI to a terminal device, the DCI supporting the scheduling of multiple physical resource units, at least one of the multiple physical resource units supporting the scheduling of multiple PUSCHs, the DCI supporting a 1-bit UL-SCH indicator, such that the terminal device transmits or does not transmit UL-SCH based on the UL-SCH indicator for one of the PUSCHs scheduled by the DCI, or transmits or does not transmit UL-SCH for a specified PUSCH among the multiple PUSCHs scheduled by the DCI.
[0025] According to another aspect of this disclosure, a terminal device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; the processor being configured to perform the method of instructing an uplink shared channel as described in the first aspect by executing the executable instructions.
[0026] According to another aspect of this disclosure, a network device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; the processor being configured to perform the method of instructing an uplink shared channel described above by executing the executable instructions.
[0027] According to another aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the above-described method for instructing an uplink shared channel.
[0028] According to another aspect of this disclosure, a computer program product is provided having a computer program stored thereon, which, when executed by a processor, implements the above-described method for instructing an uplink shared channel.
[0029] The uplink shared channel indication scheme provided by the embodiments of this disclosure, for DCIs that support scheduling multiple physical resource units and at least one physical resource unit supports scheduling multiple PUSCHs, enables the DCI to support a 1-bit UL-SCH indicator. This allows the DCI to set the UL-SCH indicator to 0 bits or 1 bit according to the actual scheduling situation, thereby meeting the UL-SCH indication requirements when scheduling different numbers of PUSCHs. This not only enables the DCI to support the function of scheduling PUSCHs that do not carry UL-SCHs, but also reduces the bit overhead of the DCI. In addition, the terminal's explicit execution of sending or not sending UL-SCH operations on the PUSCHs (a specified PUSCH among one or more PUSCHs) scheduled by the DCI based on this indicator is also beneficial to improving the accuracy of uplink data transmission.
[0030] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description
[0031] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.
[0032] Figure 1 A flowchart illustrating a method for indicating an uplink shared channel according to an embodiment of this disclosure is shown;
[0033] Figure 2 A schematic diagram of a DCI indicator UL-SCH is shown in an embodiment of this disclosure;
[0034] Figure 3 A schematic diagram of another DCI indicator UL-SCH is shown in an embodiment of this disclosure;
[0035] Figure 4 A schematic diagram of another DCI indicator UL-SCH is shown in an embodiment of this disclosure;
[0036] Figure 5 A schematic diagram of yet another DCI indicator UL-SCH in an embodiment of this disclosure is shown;
[0037] Figure 6 A schematic diagram of yet another DCI indicator UL-SCH in an embodiment of this disclosure is shown;
[0038] Figure 7 A schematic diagram of yet another DCI indicator UL-SCH in an embodiment of this disclosure is shown;
[0039] Figure 8 A flowchart illustrating yet another method for indicating an uplink shared channel according to an embodiment of this disclosure is shown;
[0040] Figure 9 A schematic diagram of an apparatus for indicating an uplink shared channel is shown in an embodiment of the present disclosure;
[0041] Figure 10 A schematic diagram of an apparatus for indicating an uplink shared channel is shown in an embodiment of the present disclosure;
[0042] Figure 11 A structural block diagram of a computer device according to an embodiment of the present disclosure is shown. Detailed Implementation
[0043] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0044] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.
[0045] The 5G NR (New Radio) standard defines the PDCCH (Physical Downlink Control Channel), whose payload is called DCI. The DCI is sent from network devices to terminal devices and includes scheduling information related to the PUSCH (Physical Downlink Shared Channel) for carrying uplink data, scheduling information related to the PDSCH (Physical Downlink Shared Channel) for carrying downlink data, uplink power control information, time slot format configuration information, and resource preemption information. DCI is divided into several different formats depending on its function, among which formats 0_0, 0_1, 0_2, and 0_3 are mainly used for scheduling the PUSCH.
[0046] The DCI in formats 0_1, 0_2, and 0_3 supports fields including a UL-SCH indicator to indicate whether UL-SCH is transmitted on the PUSCH, i.e., whether uplink data is transmitted on the PUSCH. When it is indicated that UL-SCH is not transmitted on the PUSCH, the PUSCH can be used to carry CSI (Channel State Information) reports without carrying uplink data (the uplink data payload size is 0), or the DCI can be used only to trigger SRS (Sounding Reference Signal).
[0047] For a DCI of format 0_1, one or more PUSCHs within a cell can be scheduled. If the number of scheduled PUSCHs is greater than one, the UL-SCH indicator in this DCI has 0 bits, meaning the DCI does not include the UL-SCH indicator field. Otherwise, if the number of scheduled PUSCHs is one, the UL-SCH indicator in this DCI has 1 bit, with a value of 1 indicating that the UL-SCH is transmitted on the PUSCH, and a value of 0 indicating that the UL-SCH is not transmitted on the PUSCH.
[0048] For DCI format 0_3, one or more cells can be scheduled, and each cell supports scheduling one PUSCH. The UL-SCH indicator in this DCI is 1 bit; a bit value of 1 indicates that the UL-SCH is transmitted on the PUSCH, and a bit value of 0 indicates that the UL-SCH is not transmitted on the PUSCH. The UL-SCH indicator in this DCI applies to the cell with the smallest serving cell index among the cells scheduled by this DCI. Specifically, it indicates whether the PUSCH scheduled by the cell with the smallest serving cell index transmits the UL-SCH. For other cells in the scheduled cells, PUSCHs that do not carry UL-SCH are not supported.
[0049] DCI formats 0_1, 0_2, and 0_3 also support fields including CSI request fields, used to request CSI reporting from terminal devices. For DCI format 0_3, the CSI request field applies to the cell with the smallest serving cell index among the cells scheduled by that DCI; that is, it only supports requesting CSI reporting from the cell with the smallest serving cell index among the scheduled cells.
[0050] One of the goals of the multi-carrier enhancement in 3GPP (3rd Generation Partnership Project) Rel-19 (Release 19) is to design a DCI that can schedule one or more cells, and each cell can schedule one or more PUSCHs. This DCI supports scheduling multiple cells, with at least one cell supporting the scheduling of multiple PUSCHs. However, this DCI cannot directly reuse the existing format 0_1 DCI or the existing format 0_3 DCI for the UL-SCH indicator field design; a mechanism for the DCI to indicate the UL-SCH needs to be designed.
[0051] To facilitate understanding, the following is an explanation of several terms used in this application.
[0052] DCI (Downlink Control Information): This control information is sent from network devices to terminal devices. It includes scheduling information related to the physical shared channel used to carry uplink and downlink data, uplink power control information, time slot format configuration information, resource preemption information, etc.
[0053] UL-SCH (Uplink Shared Channel) indicator: Included in DCI of format 0_1, 0_2, 0_3, used to indicate whether UL-SCH is transmitted on PUSCH (Physical Uplink Shared Channel).
[0054] CSI-RS (Channel State Information-Reference Signal): This is a downlink reference signal transmitted by the base station, used by the terminal equipment (UE) to measure the quality and status of the downlink channel to support functions such as link adaptation, beam management, and power control.
[0055] CSI-IM (CSI Interference Management) is a specific reference signal location configured by the base station for terminal equipment to measure inter-cell interference to support interference coordination (such as eICIC) and resource scheduling optimization.
[0056] NZP CSI-RS (Non-Zero Power CSI-RS): NZP CSI-RS is a type of CSI-RS with non-zero transmit power, in contrast to zero power (ZP) CSI-RS.
[0057] The steps of the method for indicating an uplink shared channel in this exemplary embodiment will now be described in more detail with reference to the accompanying drawings and embodiments.
[0058] Figure 1 A flowchart illustrating a method for indicating an uplink shared channel is shown in an embodiment of this disclosure.
[0059] like Figure 1 As shown, a method for indicating an uplink shared channel according to an embodiment of the present disclosure, applied to a terminal device, includes:
[0060] Step S102: Receive downlink control information (DCI) sent by the network device. The DCI supports scheduling multiple physical resource units (PRUs). At least one of the PRUs supports scheduling multiple physical uplink shared channels (PUSCHs). The DCI supports an uplink shared channel (UL-SCH) indicator including a 1-bit bit.
[0061] In some embodiments, a physical resource unit may be a cell or a carrier.
[0062] In the embodiments described below, a cell is used as an example to illustrate the specific implementation of DCI indicating UL-SCH.
[0063] In some embodiments, the terminal device receives a DCI sent by the network device. The DCI supports scheduling multiple cells, and at least one of the multiple cells supports scheduling multiple PUSCHs. The DCI supports a 1-bit UL-SCH indicator.
[0064] In some embodiments, DCI supports scheduling multiple cells, and the actual number of cells scheduled can be one or more. DCI supports scheduling multiple PUSCHs in at least one of the multiple cells, and the actual number of PUSCHs scheduled in a single scheduling cell can be one or more.
[0065] In some embodiments, DCI supports including a 1-bit UL-SCH indicator, which may include a 1-bit UL-SCH indicator in some scheduling scenarios and a 0-bit UL-SCH indicator (i.e., excluding the UL-SCH indicator) in other scheduling scenarios; or it may include a 1-bit UL-SCH indicator in all scheduling scenarios.
[0066] Step S104: Based on the UL-SCH indicator, send or not send UL-SCH on a PUSCH in the DCI schedule, or send or not send UL-SCH on a specified PUSCH among multiple PUSCHs in the DCI schedule.
[0067] In some embodiments, the terminal device may or may not send a UL-SCH according to the specified PUSCH in one or more PUSCHs scheduled by the DCI based on the UL-SCH indicator.
[0068] In some embodiments, when the bit value of the 1-bit UL-SCH indicator is set to 1, the terminal device sends UL-SCH at the specified PUSCH; when the bit value is set to 0, the terminal device does not send UL-SCH at the specified PUSCH.
[0069] In this embodiment, for a DCI that supports scheduling multiple physical resource units and at least one physical resource unit supports scheduling multiple PUSCHs, by supporting a 1-bit UL-SCH indicator in the DCI, the DCI can set the UL-SCH indicator to 0 bits or 1 bit according to the actual scheduling situation to meet the UL-SCH indication requirements when scheduling different numbers of PUSCHs. This not only enables the DCI to support the function of scheduling PUSCHs that do not carry UL-SCHs, but also reduces the bit overhead of the DCI. In addition, the terminal's explicit execution of sending or not sending UL-SCH operations on the PUSCH (a specified PUSCH among one or more PUSCHs) scheduled by the DCI based on this indicator is also beneficial to improving the accuracy of uplink data transmission.
[0070] In one embodiment of this disclosure, if the DCI schedules multiple PUSCHs in at least one physical resource unit, the UL-SCH indicator is 0 bits; otherwise, the UL-SCH indicator is 1 bit.
[0071] In some embodiments, if the DCI schedules multiple PUSCHs in at least one physical resource unit, the UL-SCH indicator is 0 bits; if the DCI schedules a single PUSCH in each of the one or more scheduled physical resource units, the UL-SCH indicator is 1 bit.
[0072] In some embodiments, if multiple PUSCHs exist in one cell among the multiple PUSCHs actually scheduled by DCI, the UL-SCH indicator in DCI is 0 bits.
[0073] In some embodiments, if each of the one or more cells actually scheduled by the DCI actually schedules a single PUSCH, the DCI includes a 1-bit UL-SCH indicator. This 1-bit UL-SCH indicator applies to the cell with the smallest serving cell index among the cells scheduled by the DCI, indicating whether the terminal device should send or not send the UL-SCH for the specified PUSCH scheduled by the cell with the smallest serving cell index among the scheduled cells. That is, in scheduling scenarios similar to DCI format 0_3, the DCI includes a 1-bit UL-SCH indicator.
[0074] like Figure 2 As shown, when at least one cell in the DCI-scheduled cell schedules multiple PUSCHs (e.g., cell #2 schedules PUSCH1 and PUSCH2, and cell #3 schedules PUSCH1, 2, and 3), the UL-SCH indicator is 0 bits. By setting it to 0 bits, the bit overhead of DCI is reduced, and there is no need to provide additional indication of the UL-SCH transmission status of multiple PUSCHs.
[0075] like Figure 3 As shown, this scenario presents a single PUSCH scheduling per cell. When all cells scheduled by DCI (e.g., cells #1, #2, #3, #4) each schedule only a single PUSCH, DCI includes a 1-bit UL-SCH indicator. This indicator operates on the cell with the smallest serving cell index among the scheduled cells, instructing the terminal to send or not send UL-SCH on the specified PUSCH in that cell. This approach is compatible with the existing DCI function in format 0_3 while precisely controlling the UL-SCH transmission status.
[0076] In this embodiment, when each cell of one or more cells actually schedules a single PUSCH in the DCI scheduling, the DCI includes a 1-bit UL-SCH indicator, which is compatible with the format 0_3 DCI and supports the function of scheduling PUSCHs that do not carry UL-SCH. When at least one cell schedules multiple PUSCHs, the UL-SCH indicator is 0 bits, which can reduce the bit overhead of DCI that supports scheduling multiple cells and at least one cell supports scheduling multiple PUSCHs. By dynamically adjusting the number of bits of the UL-SCH indicator, an optimized balance between signaling efficiency and control flexibility is achieved in the multi-carrier enhancement scenario.
[0077] In another embodiment of this disclosure, if the DCI schedules the maximum number of PUSCHs supported for scheduling across all physical resource units that support scheduling, the UL-SCH indicator is 0 bits; otherwise, the UL-SCH indicator is 1 bit.
[0078] In some embodiments, if the DCI schedules the maximum number of PUSCHs that can be scheduled across all physical resource units that support scheduling, the UL-SCH indicator is 0 bits; if the DCI does not schedule all physical resource units that support scheduling, or does not schedule the maximum number of PUSCHs that can be scheduled across at least one physical resource unit, the UL-SCH indicator is 1 bit. In this embodiment, if the actual number of PUSCHs scheduled by the DCI reaches the maximum number of PUSCHs that can be scheduled, the UL-SCH indicator is 0 bits, thereby reducing the bit overhead of the DCI that supports scheduling multiple cells, with at least one cell supporting the scheduling of multiple PUSCHs. If the actual number of PUSCHs scheduled by the DCI does not reach the maximum number of PUSCHs that can be scheduled, the UL-SCH indicator is 1 bit, enabling the DCI to support scheduling PUSCHs that do not carry UL-SCHs. This allows for an optimized balance between DCI bit overhead and scheduling flexibility by dynamically adjusting the number of bits in the UL-SCH indicator.
[0079] In another embodiment described above, the PUSCH is further specified as the earliest PUSCH scheduled by DCI in the first physical resource unit or the earliest PUSCH that satisfies the channel state information (CSI) processing time requirement. The first physical resource unit is the physical resource unit with the smallest unit index among the physical resource units scheduled by DCI.
[0080] In some embodiments, the cell index may include the serving cell index.
[0081] In some embodiments, among multiple physical resource units scheduled by DCI, the first physical resource unit is determined based on its unit index. The unit index is a unique identifier assigned to each physical resource unit, and the physical resource unit with the smallest unit index is defined as the first physical resource unit.
[0082] In some embodiments, within the first physical resource unit, the earliest PUSCH is selected as the designated PUSCH in chronological order, which means that the PUSCH is the earliest transmitted in the time dimension.
[0083] In some embodiments, the earliest PUSCH may be the PUSCH with the earliest start symbol or the earliest end symbol in the time dimension.
[0084] In some embodiments, CSI processing requires a certain amount of time. The terminal device needs to select PUSCHs that can meet the CSI processing time requirements in the first physical resource unit according to its own CSI processing capabilities and processes. Then, it selects the earliest one among these PUSCHs that meet the conditions as the designated PUSCH.
[0085] In this embodiment, by using the earliest PUSCH scheduled by DCI in the first physical resource unit or the earliest PUSCH that meets the CSI processing time requirement as the designated PUSCH, selecting the earliest PUSCH can enable CSI or SRS to be transmitted as early as possible, thereby reducing waiting latency. Determining the earliest PUSCH based on the CSI processing time requirement can ensure that the CSI report can be prepared in time and transmitted on the designated PUSCH, preventing the situation where the CSI report cannot be transmitted due to not being prepared when the UL-SCH is not transmitted on the PUSCH but the PUSCH is used to carry the CSI report. At the same time, it is beneficial to minimize transmission waiting latency.
[0086] In another embodiment described above, the PUSCH is further designated as the earliest PUSCH among all PUSCHs scheduled by DCI, or the earliest PUSCH that meets the CSI processing time requirement. If the earliest PUSCH includes multiple PUSCHs, then the earliest PUSCH on the physical resource unit with the smallest unit index among the physical resource units where the multiple earliest PUSCHs are located is designated as the PUSCH.
[0087] In some embodiments, the PUSCH is specified as the PUSCH of the cell with the smallest serving cell index among the earliest PUSCHs scheduled by DCI or the earliest PUSCHs that meet the CSI processing time requirements.
[0088] In some embodiments, a 1-bit UL-SCH indicator is used to specify the PUSCH.
[0089] In some embodiments, specifying the PUSCH as the PUSCH of the cell with the smallest serving cell index among the cells scheduled by DCI facilitates compatibility with the existing DCI UL-SCH indicator of format 0_3.
[0090] In some embodiments, specifying the PUSCH as the earliest or the earliest PUSCH that meets the CSI processing time requirements can help reduce CSI reporting latency.
[0091] In some embodiments, for DCI-triggered CSI reporting on the PUSCH, the UE needs a certain amount of time to calculate and report the CSI. The required calculation time is the CSI processing time requirement. The start symbol of the PUSCH that meets the CSI processing time requirement is no earlier than a preset number of symbols after the end symbol of the PDCCH carrying the DCI, and no earlier than a preset number of symbols after the end symbol of the latest aperiodic CSI-RS, CSI-IM, and NZP CSI-RS resources.
[0092] In some embodiments, it should be noted that the earliest PUSCH refers to the PUSCH with the earliest start symbol or the earliest end symbol.
[0093] In some embodiments, when the DCI supports scheduling up to 4 cells, and each cell supports scheduling up to 4 PUSCHs, a schematic diagram of the corresponding DCI UL-SCH indicator is shown below. Figure 4 and Figure 5 As shown. In Figure 4 In this scenario, DCI schedules 16 PUSCHs, reaching the maximum number of PUSCHs that can be scheduled, and the UL-SCH indicator is at bit 0. Figure 5 In this process, DCI scheduled 12 PUSCHs, which is less than the maximum number of PUSCHs that can be scheduled, and the UL-SCH indicator is 1 bit.
[0094] like Figure 5 As shown, the designated PUSCH is the earliest PUSCH that satisfies the CSI processing time requirement among the cells scheduled by DCI, which is the cell with the smallest serving cell index among the cells that meet the CSI processing time requirement. PUSCH3 scheduled in cell #1 is the designated PUSCH. Based on the designation of the earliest PUSCH that satisfies the CSI processing time requirement among the PUSCHs scheduled by DCI, the candidate designated PUSCHs include PUSCH4 scheduled in cell #2 and PUSCH4 scheduled in cell #3, where PUSCH4 scheduled in cell #2 is the designated PUSCH.
[0095] In this embodiment, when there are multiple earliest PUSCHs, the earliest PUSCH on the physical resource unit with the smallest unit index is selected as the designated PUSCH, providing a clear and executable rule for UL-SCH scheduling. This deterministic rule enables network devices and terminal devices to reach a consensus on UL-SCH scheduling and whether to send, reducing negotiation costs and errors caused by unclear rules.
[0096] In another embodiment of this disclosure, if the DCI schedules multiple PUSCHs in each of the scheduled physical resource units, the UL-SCH indicator is 0 bits; if the physical resource unit scheduled by the DCI includes a second physical resource unit, and a single PUSCH is scheduled in the second physical resource unit, the UL-SCH indicator is 1 bit.
[0097] In some embodiments, if the DCI schedules multiple PUSCHs in all scheduled physical resource units, the UL-SCH indicator is 0 bits; otherwise, the UL-SCH indicator is 1 bit.
[0098] In some embodiments, unlike the first physical resource unit, the second physical resource unit refers to at least one of the multiple physical resource units scheduled by DCI that schedules a single PUSCH cell or carrier.
[0099] In some embodiments, if a scheduled cell schedules a single PUSCH, the UL-SCH indicator is 1 bit. This scheme reduces the bit overhead of DCI when all cells scheduled by DCI schedule multiple PUSCHs.
[0100] In this embodiment, when the terminal device parses and finds that the DCI has scheduled multiple PUSCHs in all scheduled cells, it sets the UL-SCH indicator to 0 bits. This indicates that, by default, all scheduled PUSCHs do not support carrying UL-SCH and no additional indication information is needed. However, if there is a cell scheduling a single PUSCH, the UL-SCH indicator is set to 1 bit. This 1-bit indicator is used to indicate whether the specified PUSCH transmits UL-SCH. If it is 1, it is transmitted; if it is 0, it is not transmitted. While reducing the DCI bit overhead, in the scenario where there is a cell scheduling a single PUSCH, the 1-bit indicator can flexibly control whether the PUSCH transmits UL-SCH, increasing the scheduling flexibility.
[0101] In another embodiment described above, the PUSCH is specified as the PUSCH scheduled in the second physical resource unit with the smallest cell index.
[0102] In some embodiments, the 1-bit UL-SCH indicator is applicable to PUSCHs scheduled in cells where DCI schedules a single PUSCH, specifically the PUSCH scheduled in the cell with the smallest serving cell index.
[0103] In this embodiment, the UL-SCH indicator is applicable to cells that have only scheduled a single PUSCH, simplifying the complexity of determining the specific PUSCH to which the UL-SCH indicator applies.
[0104] In some embodiments, a schematic diagram of the DCI UL-SCH indicator is shown below. Figure 6 and Figure 7 As shown.
[0105] like Figure 6 As shown, in DCI-scheduled cells (such as cells #1, #2, #3, and #4), each cell schedules multiple PUSCHs (e.g., cell #1 schedules PUSCH1 and PUSCH2, and cell #3 schedules PUSCH1-PUSCH4). The UL-SCH indicator is set to 0 bits. By using the 0-bit design, there is no need to provide additional indication of the UL-SCH transmission status of multiple PUSCHs, thus reducing the bit overhead of DCI.
[0106] like Figure 7 As shown, in DCI-scheduled cells, there are cells that schedule a single PUSCH (e.g., cells #2 and #4 schedule a single PUSCH1 respectively). In this case, a 1-bit UL-SCH indicator is applicable to cells that schedule a single PUSCH, where the cell with the smallest serving cell index schedules the PUSCH. This design simplifies the complexity of determining the target of the indicator. The terminal can directly perform UL-SCH sending or not sending operations on the PUSCH of the specified cell based on the 1-bit indicator, which supports the indication function of UL-SCH and simplifies the processing complexity.
[0107] In yet another embodiment of this disclosure, the UL-SCH indicator in the DCI is 1 bit.
[0108] In some embodiments, when DCI schedules one or more physical resource units (such as cells or carriers), each physical resource unit may schedule multiple PUSCHs. One bit can be used to indicate whether a specific PUSCH in the scheduled PUSCH needs to carry UL-SCH data.
[0109] In this embodiment, the DCI scheme includes a 1-bit UL-SCH indicator in all scheduling scenarios, maximizing the support for DCI scheduling of PUSCH that does not carry UL-SCH.
[0110] In another embodiment described above, the PUSCH is designated as the earliest PUSCH scheduled by DCI in the first physical resource unit or the earliest PUSCH that meets the channel state information (CSI) processing time requirement. The first physical resource unit is the physical resource unit with the smallest unit index among the physical resource units scheduled by DCI.
[0111] In some embodiments, unlike the embodiment where "if the DCI schedules the maximum number of PUSCHs that can be scheduled in all physical resource units that support scheduling, the UL-SCH indicator is 0 bits; otherwise, the UL-SCH indicator is 1 bit. Further, the PUSCH is specified as the earliest PUSCH scheduled by the DCI in the first physical resource unit or the earliest PUSCH that satisfies the Channel State Information (CSI) processing time requirement, and the first physical resource unit is the physical resource unit with the smallest unit index among the physical resource units scheduled by the DCI", in this embodiment, the DCI includes a 1-bit UL-SCH indicator in all scheduling cases, and other similarities will not be repeated.
[0112] In this embodiment, once the designated PUSCH is determined, the terminal device can decide whether to send UL-SCH on the designated PUSCH based on the value of the 1-bit UL-SCH indicator in the DCI. If the indicator value is 1, UL-SCH is sent on the designated PUSCH; if the indicator value is 0, UL-SCH is not sent on the designated PUSCH. This enables the UL-SCH indication function to be supported in all scheduling scenarios. The base station and the terminal can adopt a unified method for determining the designated PUSCH, ensuring consistency in the understanding of scheduling information.
[0113] In another embodiment described above, the designated PUSCH is the earliest PUSCH among all PUSCHs scheduled by DCI, or the earliest PUSCH that meets the CSI processing time requirement. If the earliest PUSCH includes multiple PUSCHs, then the earliest PUSCH on the physical resource unit with the smallest unit index among the physical resource units where the multiple earliest PUSCHs are located is taken as the designated PUSCH.
[0114] In some embodiments, the designated PUSCH is the earliest PUSCH among those scheduled by DCI or the PUSCH in the cell with the smallest serving cell index among the earliest PUSCHs that meet the CSI processing time requirement. This is similar to the above embodiment where "if DCI schedules the maximum number of PUSCHs that can be scheduled in all physical resource units that support scheduling, the UL-SCH indicator is 0 bits; otherwise, the UL-SCH indicator is 1 bit. Further, the designated PUSCH is the earliest PUSCH among all PUSCHs scheduled by DCI, or the earliest PUSCH that meets the CSI processing time requirement. If the earliest PUSCH includes multiple PUSCHs, then the earliest PUSCH in the physical resource unit with the smallest cell index among the physical resource units where the multiple earliest PUSCHs are located is taken as the designated PUSCH." The difference is that DCI includes a 1-bit UL-SCH indicator in all scheduling cases, and the similarities will not be repeated.
[0115] In this embodiment, regarding data transmission timeliness, the earliest PUSCH among all PUSCHs or the earliest PUSCH that meets the CSI processing time requirement is preferentially selected, enabling the terminal device to quickly execute uplink data transmission and effectively reduce latency. When multiple earliest PUSCHs exist, the PUSCH on the physical resource unit with the smallest unit index is selected, providing a selection rule for the selection of a specified PUSCH and ensuring consistency in the understanding of scheduling information between the base station and the terminal. Furthermore, combined with a 1-bit UL-SCH indicator, the UL-SCH indication function can be supported in all scheduling situations, maximizing the applicability of this function.
[0116] In another embodiment described above, if the physical resource unit scheduled by DCI includes a second physical resource unit, a single PUSCH is scheduled in the second physical resource unit, and the PUSCH is designated as the PUSCH scheduled in the second physical resource unit with the smallest unit index; if the physical resource unit scheduled by DCI does not include a second physical resource unit, the PUSCH is designated as the earliest PUSCH scheduled by DCI in the first physical resource unit or the earliest PUSCH that meets the CSI processing time requirement, and the first physical resource unit is the physical resource unit with the smallest unit index among the physical resource units scheduled by DCI.
[0117] In some embodiments, if a scheduled cell schedules a single PUSCH, the first PUSCH is the PUSCH scheduled by the cell with the smallest serving cell index among the cells that schedule a single PUSCH in DCI; otherwise, the first PUSCH is the earliest PUSCH scheduled by the cell with the smallest serving cell index among the cells scheduled in DCI, or the earliest PUSCH that meets the CSI processing time requirement.
[0118] In this embodiment, when there is no second physical resource unit, the earliest PUSCH in the first physical resource unit or the earliest PUSCH that meets the CSI processing time requirement is selected, which can enable CSI or SRS to be transmitted as early as possible and reduce waiting latency. When there is a second physical resource unit, the PUSCH is designated as the PUSCH scheduled by DCI in the second physical resource unit with the smallest unit index. This provides a selection rule for the selection of the designated PUSCH and ensures the consistency of the base station and terminal's understanding of the scheduling information.
[0119] In another embodiment described above, if the physical resource unit scheduled by DCI includes a second physical resource unit, a single PUSCH is scheduled in the second physical resource unit, and the PUSCH is designated as the PUSCH scheduled in the second physical resource unit with the smallest unit index; if the physical resource unit scheduled by DCI does not include a second physical resource unit, the PUSCH is designated as the earliest PUSCH among all PUSCHs scheduled by DCI, or the earliest PUSCH that meets the CSI processing time requirement. If the earliest PUSCH includes multiple PUSCHs, the earliest PUSCH in the physical resource unit with the smallest unit index among the physical resource units where the multiple earliest PUSCHs are located is designated as the PUSCH.
[0120] In this embodiment, when there is no second physical resource unit, the earliest PUSCH among all PUSCHs or the earliest PUSCH that meets the CSI processing time requirement is selected. When multiple earliest PUSCHs exist, the designated PUSCH is determined based on the physical resource unit with the smallest unit index. This allows CSI or SRS to be transmitted as early as possible, reducing waiting latency. When there is a second physical resource unit, the designated PUSCH is the PUSCH scheduled by DCI in the second physical resource unit with the smallest unit index. This also provides a selection rule for the selection of the designated PUSCH, ensuring the consistency of the base station and terminal's understanding of the scheduling information.
[0121] In another embodiment described above, if the physical resource unit scheduled by DCI includes a second physical resource unit, a single PUSCH is scheduled in the second physical resource unit, and the PUSCH is specified as the PUSCH scheduled in the second physical resource unit with the smallest unit index; if the physical resource unit scheduled by DCI does not include the second physical resource unit, the indication value of the UL-SCH indicator is invalid.
[0122] In some embodiments, if the physical resource unit scheduled by the DCI includes a second physical resource unit, the terminal device will find the second physical resource unit with the smallest unit index and determine the PUSCH scheduled in that unit as the designated PUSCH. Then, the terminal will decide whether to send the UL-SCH on this designated PUSCH based on the value of the 1-bit UL-SCH indicator in the DCI. If the indicator is 1, it will be sent; if it is 0, it will not be sent.
[0123] In some embodiments, when the physical resource unit scheduled by DCI does not include the second physical resource unit, the indication value of the UL-SCH indicator is invalid, indicating that the terminal device does not need to rely on the indicator to decide whether to send UL-SCH, and may adopt the default sending strategy or operate according to other configuration information.
[0124] In some embodiments, when the indication value of the UL-SCH indicator is invalid, all PUSCHs scheduled by the DCI carry the UL-SCH, meaning that PUSCHs that do not carry the UL-SCH are not supported. By interpreting the indication value of the UL-SCH indicator as invalid, the field can be made to have a fixed size, simplifying the terminal's parsing of the field and reducing the complexity of determining the specified PUSCH to which the UL-SCH indicator applies.
[0125] In another embodiment described above, if the DCI schedules a single PUSCH in the first physical resource unit of the scheduled physical resource units, the PUSCH is designated as the PUSCH scheduled in the first physical resource unit, and the first physical resource unit is the physical resource unit with the smallest unit index among the physical resource units scheduled by the DCI; if the DCI schedules multiple PUSCHs in the first physical resource unit, the indication value of the UL-SCH indicator is invalid.
[0126] In some embodiments, when the indication value of the UL-SCH indicator is invalid, all PUSCHs scheduled by the DCI carry the UL-SCH, meaning that PUSCHs that do not carry the UL-SCH are not supported. By interpreting the indication value of the UL-SCH indicator as invalid, the field can be made to have a fixed size, simplifying the terminal's parsing of the field and reducing the complexity of determining the specified PUSCH to which the UL-SCH indicator applies.
[0127] In some embodiments of this disclosure, DCI supports a domain that includes a CSI request, the domain of which is applicable to a specified PUSCH.
[0128] In some embodiments, the CSI request field is used to request the terminal device to report CSI at a specified PUSCH. In all embodiments from one to another of this disclosure, DCI support includes a CSI request field that is applicable to the definition of the specified PUSCH. Specifying the PUSCH to which the CSI request field applies is the same as the PUSCH to which the UL-SCH indicator applies, thereby enabling the transmission of CSI reports using a PUSCH that does not carry the UL-SCH.
[0129] like Figure 8 As shown, a method for instructing an uplink shared channel according to another embodiment of this disclosure, applied to a network device, includes:
[0130] Step S802: Send DCI to the terminal device. DCI supports scheduling multiple physical resource units. At least one of the multiple physical resource units supports scheduling multiple PUSCHs. DCI supports a 1-bit UL-SCH indicator, so that the terminal device can send or not send UL-SCH on a PUSCH scheduled by DCI based on the UL-SCH indicator, or send or not send UL-SCH on a specified PUSCH among the multiple PUSCHs scheduled by DCI.
[0131] In some embodiments, the network device sends a DCI to the terminal device. The DCI supports scheduling multiple cells, and at least one of the multiple cells supports scheduling multiple PUSCHs. The DCI supports a 1-bit UL-SCH indicator so that the terminal device can send or not send a UL-SCH in one or more PUSCHs scheduled by the DCI according to the UL-SCH indicator.
[0132] It should be noted that the above figures are merely illustrative of the processes included in the method according to exemplary embodiments of the present invention, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal order of these processes. Furthermore, it is readily understood that these processes may, for example, be executed synchronously or asynchronously in multiple modules.
[0133] The following reference Figure 9 This describes an apparatus 900 for indicating an uplink shared channel according to an embodiment of the present invention. Figure 9 The device 900 shown for indicating the uplink shared channel is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of the present invention.
[0134] The uplink shared channel indication device 900 is manifested in the form of a hardware module. Components of the uplink shared channel indication device 900 may include, but are not limited to: a receiving module 902, used to receive downlink control information (DCI) sent by a network device, the DCI supporting the scheduling of multiple physical resource units (PRUs), at least one of the PRUs supporting the scheduling of multiple physical uplink shared channels (PUSCHs), and the DCI supporting an uplink shared channel UL-SCH indicator including a 1-bit bit; and a first transmitting module 904, used to transmit or not transmit UL-SCH based on the UL-SCH indicator for a PUSCH scheduled by the DCI, or to transmit or not transmit UL-SCH for a specified PUSCH among the multiple PUSCHs scheduled by the DCI.
[0135] The following reference Figure 10 This describes an apparatus 1000 for indicating an uplink shared channel according to an embodiment of the present invention. Figure 10 The illustrated device 1000 for indicating an uplink shared channel is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of the present invention.
[0136] The uplink shared channel indication device 1000 is manifested in the form of a hardware module. Components of the uplink shared channel indication device 1000 may include, but are not limited to: a second transmitting module 1002, used to transmit a DCI to a terminal device, the DCI supporting the scheduling of multiple physical resource units, at least one of the multiple physical resource units supporting the scheduling of multiple PUSCHs, and the DCI supporting a 1-bit UL-SCH indicator, so that the terminal device may transmit or not transmit UL-SCH based on the UL-SCH indicator in a PUSCH scheduled by the DCI, or transmit or not transmit UL-SCH in a specified PUSCH among the multiple PUSCHs scheduled by the DCI.
[0137] Those skilled in the art will understand that various aspects of the present invention can be implemented as systems, methods, or program products. Therefore, various aspects of the present invention can be specifically implemented in the following forms: entirely hardware implementations, entirely software implementations (including firmware, microcode, etc.), or implementations combining hardware and software aspects, collectively referred to herein as “circuits,” “modules,” or “systems.”
[0138] The following reference Figure 11 To describe an electronic device 1100 according to this embodiment of the present invention, it may be a network device or a terminal. Figure 11 The electronic device 1100 shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of the present invention.
[0139] like Figure 11 As shown, the electronic device 1100 is manifested in the form of a general-purpose computing device. The components of the electronic device 1100 may include, but are not limited to: at least one processing unit 1110, at least one storage unit 1120, and a bus 1130 connecting different system components (including storage unit 1120 and processing unit 1110).
[0140] The storage unit stores program code that can be executed by the processing unit 1110, causing the processing unit 1110 to perform the steps described in the "Exemplary Methods" section of this specification according to various exemplary embodiments of the present invention. For example, the processing unit 1110 can perform actions such as... Figure 1 The described solution.
[0141] Storage unit 1120 may include a readable medium in the form of a volatile storage unit, such as random access memory (RAM) 11201 and / or cache memory 11202, and may further include a read-only memory (ROM) 11203.
[0142] Storage unit 1120 may also include a program / utility 11204 having a set (at least one) of program modules 11205, such program modules 11205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.
[0143] Bus 1130 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.
[0144] Electronic device 1100 can also communicate with one or more external devices 1170 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 1100, and / or with any device that enables electronic device 1100 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 1150. Furthermore, electronic device 1100 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 1160. As shown, network adapter 1160 communicates with other modules of electronic device 1100 via bus 1130. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 1100, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0145] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.
[0146] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the methods described above is stored. In some possible embodiments, various aspects of the invention may also be implemented as a program product comprising program code that, when the program product is run on an electronic device, causes the electronic device to perform the steps of the various exemplary embodiments of the invention described in the "Exemplary Methods" section above.
[0147] According to embodiments of the present invention, a program product for implementing the above-described method may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may run on an electronic device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, a readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, apparatus, or device.
[0148] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0149] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.
[0150] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.
[0151] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages such as Java and C++, and conventional procedural programming languages such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).
[0152] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.
[0153] Furthermore, although the steps of the method in this disclosure are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or a step may be broken down into multiple steps.
[0154] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or network device, etc.) to execute the methods according to the embodiments of this disclosure.
[0155] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the appended claims.
Claims
1. A method for indicating an uplink shared channel, characterized in that, Applied to terminal devices, including: The device receives downlink control information (DCI) sent by a network device. The DCI supports scheduling multiple physical resource units (PRUs). At least one of the PRUs supports scheduling multiple physical uplink shared channels (PUSCHs). The DCI supports an uplink shared channel UL-SCH indicator, which includes a 1-bit bit. Based on the UL-SCH indicator, the UL-SCH may be sent or not sent to one of the PUSCHs in the DCI scheduling, or to a specified PUSCH among the multiple PUSCHs in the DCI scheduling.
2. The method for indicating an uplink shared channel according to claim 1, characterized in that, If the DCI schedules multiple PUSCHs in at least one of the physical resource units, the UL-SCH indicator is 0 bits. Otherwise, the UL-SCH indicator is 1 bit.
3. The method for indicating an uplink shared channel according to claim 1, characterized in that, If the DCI schedules the maximum number of PUSCHs that can be scheduled in all the physical resource units that support scheduling, the UL-SCH indicator is 0 bits. Otherwise, the UL-SCH indicator is 1 bit.
4. The method for indicating an uplink shared channel according to claim 3, characterized in that, The designated PUSCH is the earliest PUSCH scheduled by the DCI in the first physical resource unit or the earliest PUSCH that satisfies the Channel State Information (CSI) processing time requirement. The first physical resource unit is the physical resource unit with the smallest unit index among the physical resource units scheduled by the DCI.
5. The method for indicating an uplink shared channel according to claim 3, characterized in that, The designated PUSCH is the earliest PUSCH among all PUSCHs scheduled by the DCI, or the earliest PUSCH that meets the CSI processing time requirement. If the earliest PUSCH includes multiple PUSCHs, then the earliest PUSCH on the physical resource unit with the smallest unit index among the multiple earliest PUSCHs is taken as the designated PUSCH.
6. The method for indicating an uplink shared channel according to claim 1, characterized in that, If the DCI schedules multiple PUSCHs in each of the scheduled physical resource units, the UL-SCH indicator is 0 bits. If the physical resource unit scheduled by the DCI includes a second physical resource unit, and a single PUSCH is scheduled in the second physical resource unit, the UL-SCH indicator is 1 bit.
7. The method for indicating an uplink shared channel according to claim 6, characterized in that, The specified PUSCH is the PUSCH scheduled in the second physical resource unit with the smallest unit index.
8. The method for indicating an uplink shared channel according to claim 1, characterized in that, The UL-SCH indicator in the DCI is 1 bit.
9. The method for indicating an uplink shared channel according to claim 8, characterized in that, The designated PUSCH is the earliest PUSCH scheduled by the DCI in the first physical resource unit or the earliest PUSCH that satisfies the Channel State Information (CSI) processing time requirement. The first physical resource unit is the physical resource unit with the smallest unit index among the physical resource units scheduled by the DCI.
10. The method for indicating an uplink shared channel according to claim 8, characterized in that, The designated PUSCH is the earliest PUSCH among all PUSCHs scheduled by the DCI, or the earliest PUSCH that meets the CSI processing time requirement. If the earliest PUSCH includes multiple PUSCHs, then the earliest PUSCH on the physical resource unit with the smallest unit index among the multiple earliest PUSCHs is taken as the designated PUSCH.
11. The method for indicating an uplink shared channel according to claim 8, characterized in that, If the physical resource unit scheduled by the DCI includes a second physical resource unit, a single PUSCH is scheduled in the second physical resource unit, and the designated PUSCH is the PUSCH scheduled in the second physical resource unit with the smallest unit index. If the physical resource unit scheduled by the DCI does not include the second physical resource unit, the designated PUSCH is the earliest PUSCH scheduled by the DCI in the first physical resource unit or the earliest PUSCH that meets the CSI processing time requirement, and the first physical resource unit is the physical resource unit with the smallest unit index among the physical resource units scheduled by the DCI.
12. The method for indicating an uplink shared channel according to claim 8, characterized in that, If the physical resource unit scheduled by the DCI includes a second physical resource unit, a single PUSCH is scheduled in the second physical resource unit, and the designated PUSCH is the PUSCH scheduled in the second physical resource unit with the smallest unit index. If the physical resource unit scheduled by the DCI does not include the second physical resource unit, the designated PUSCH is the earliest PUSCH among all the PUSCHs scheduled by the DCI, or the earliest PUSCH that meets the CSI processing time requirement. If the earliest PUSCH includes multiple PUSCHs, then the earliest PUSCH on the physical resource unit with the smallest unit index among the physical resource units where the multiple earliest PUSCHs are located is taken as the designated PUSCH.
13. The method for indicating an uplink shared channel according to claim 8, characterized in that, If the physical resource unit scheduled by the DCI includes a second physical resource unit, a single PUSCH is scheduled in the second physical resource unit, and the designated PUSCH is the PUSCH scheduled in the second physical resource unit with the smallest unit index. If the physical resource unit scheduled by the DCI does not include the second physical resource unit, the indication value of the UL-SCH indicator is invalid.
14. The method for indicating an uplink shared channel according to claim 8, characterized in that, If the DCI schedules a single PUSCH in the first physical resource unit of the scheduled physical resource unit, the specified PUSCH is the PUSCH scheduled in the first physical resource unit, and the first physical resource unit is the physical resource unit with the smallest unit index among the physical resource units scheduled by the DCI. If the DCI schedules multiple PUSCHs in the first physical resource unit, the indication value of the UL-SCH indicator is invalid.
15. The method for indicating an uplink shared channel according to claim 1, characterized in that, The DCI supports fields including CSI requests, and the fields of the CSI requests are applicable to the specified PUSCH.
16. The method for indicating an uplink shared channel according to claim 1, characterized in that, The physical resource unit includes cells and / or carriers.
17. A method for indicating an uplink shared channel, characterized in that, Applied to network devices, including: A DCI is sent to a terminal device. The DCI supports scheduling multiple physical resource units, and at least one of the multiple physical resource units supports scheduling multiple PUSCHs. The DCI supports a 1-bit UL-SCH indicator, which enables the terminal device to send or not send UL-SCH based on the UL-SCH indicator for one of the PUSCHs scheduled by the DCI, or to send or not send UL-SCH for a specified PUSCH among the multiple PUSCHs scheduled by the DCI.
18. An apparatus for indicating an uplink shared channel, characterized in that, Applied to terminal devices, including: The receiving module is used to receive downlink control information (DCI) sent by the network device. The DCI supports scheduling multiple physical resource units (PRPs). At least one of the PRPs supports scheduling multiple physical uplink shared channels (PUSCHs). The DCI supports an uplink shared channel (UL-SCH) indicator including a 1-bit bit. The first transmitting module is configured to transmit or not transmit UL-SCH based on the UL-SCH indicator for one of the PUSCHs scheduled in the DCI, or to transmit or not transmit UL-SCH for a specified PUSCH among a plurality of PUSCHs scheduled in the DCI.
19. An apparatus for indicating an uplink shared channel, characterized in that, Applied to network devices, including: The second sending module is used to send a DCI to the terminal device. The DCI supports scheduling multiple physical resource units, and at least one of the multiple physical resource units supports scheduling multiple PUSCHs. The DCI supports a 1-bit UL-SCH indicator, so that the terminal device can send or not send UL-SCH based on the UL-SCH indicator for one of the PUSCHs scheduled by the DCI, or send or not send UL-SCH for a specified PUSCH among the multiple PUSCHs scheduled by the DCI.
20. A terminal device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the method of indicating an uplink shared channel as described in any one of claims 1 to 16 by executing the executable instructions.
21. A network device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to perform the method of indicating an uplink shared channel as described in claim 17 by executing the executable instructions.
22. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method for indicating an uplink shared channel as described in any one of claims 1 to 17.
23. A computer program product having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method for indicating an uplink shared channel as described in any one of claims 1 to 17.