Method and apparatus for determining a beam

Abstract

The present disclosure provides a method and device for determining a beam, which can be applied in mobile communication technology. The method comprises: when a plurality of PDSCHs or PUSCHs are scheduled by one DCI, determining the transmission beams corresponding to the plurality of PDSCHs or PUSCHs, wherein the plurality of PDSCHs or PUSCHs transmit different TBs. Thus, the terminal device can determine the receiving beams corresponding to the PDSCHs scheduled by one DCI, or determine the transmitting beams corresponding to the PUSCHs scheduled by one DCI, so that the terminal device can communicate with the network device based on the determined beams.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a method and apparatus for determining a beam. Background Technology

[0002] In the 52.6-71 GHz range, a single DCI (downlink control information) can schedule multiple PDSCH (physical downlink shared channel) / PUSCH (physical uplink shared channel) channels to reduce the overhead of blind detection of PDCCH (physical downlink control channel). Determining the corresponding transmission beam for each PDSCH / PUSCH is crucial. Summary of the Invention

[0003] The first aspect of this disclosure provides a beam determination method, which is executed by a terminal device. The method includes: when a downlink control information (DCI) schedules multiple physical downlink shared channels (PDSCHs) or physical uplink shared channels (PUSCHs), determining the transmission beams corresponding to the multiple PDSCHs or PUSCHs, wherein the multiple PDSCHs or PUSCHs transmit different transport blocks (TBs).

[0004] In this technical solution, when a DCI schedules multiple PDSCHs or PUSCHs, the transmission beams corresponding to the multiple PDSCHs or PUSCHs are determined, wherein the multiple PDSCHs or PUSCHs transmit different TBs. Therefore, the terminal device can determine the receive beams corresponding to each PDSCH scheduled by a DCI, or determine the transmit beams corresponding to each PUSCH scheduled by a DCI, thereby enabling communication with network devices based on the determined beams.

[0005] In one possible implementation, determining the transmission beam corresponding to the plurality of PDSCHs or PUSCHs includes: determining a first PDSCH or a first PUSCH among the plurality of PDSCHs or PUSCHs, wherein the scheduling offset of the first PDSCH or the first PUSCH is less than a predefined quasi-co-location time length (timeDurationForQCL); and determining the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0006] In one possible implementation, determining the default transmission beam corresponding to the first PDSCH or the first PUSCH includes: when the DCI is a single DCI in a single TRP scenario, obtaining the time slot of the reference PDCCH before the first PDSCH or the first PUSCH; obtaining the beam corresponding to the CORESET with the minimum control resource set CORESET ID detected in the time slot of the reference PDCCH, and using it as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0007] In one possible implementation, determining the default transmission beam corresponding to the first PDSCH or the first PUSCH includes: when the DCI is a multi-DCI in a multi-TRP scenario based on multiple DCIs, obtaining the time slot of a reference PDCCH preceding the first PDSCH or the first PUSCH; obtaining the beam corresponding to the CORESET with the smallest CORESET ID among multiple CORESETs with the same control resource pool index CORESET PoolIndex detected in the time slot of the reference PDCCH, and using it as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0008] In one possible implementation, determining the default transmission beam corresponding to the first PDSCH or the first PUSCH includes: when the DCI is a single DCI in a multi-TRP scenario based on a single DCI, determining whether the terminal device has configured an enable flag EnableTwoDefaultTCIStates, the enable flag being used to indicate that the terminal device is allowed to use two default TCI states; if the terminal device has configured EnableTwoDefaultTCIStates, obtaining the beam with the smallest code point association containing the two TCI states in the code point corresponding to the TCI field, and using it as the default transmission beam corresponding to the first PDSCH or the first PUSCH; if the terminal device has not configured EnableTwoDefaultTCIStates, obtaining the beam corresponding to the CORESET with the smallest CORESET ID in the time slot of the reference PDCCH, and using it as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0009] In one possible implementation, the reference PDCCH is the most recently detected PDCCH preceding the first PDSCH or the first PUSCH.

[0010] In one possible implementation, the method further includes: determining a second PDSCH or a second PUSCH among the plurality of PDSCHs or PUSCHs, wherein the scheduling offset of the second PDSCH or the second PUSCH is greater than or equal to the TimeDurationForQCL; and determining the transmission beam corresponding to the second PDSCH or the second PUSCH.

[0011] In one possible implementation, the transmission beam corresponding to the second PDSCH or the second PUSCH is determined according to any of the following methods:

[0012] Method 1: If the DCI has a Transmission Indication Configuration TCI field, the beam indicated by the TCI field is used as the transmission beam corresponding to the second PDSCH or the second PUSCH.

[0013] Method 2: If the TCI domain is not present in the DCI, the beam of the physical lower layer control channel PDCCH that schedules the second PDSCH or the second PUSCH is used as the transmission beam corresponding to the second PDSCH or the second PUSCH.

[0014] Method 3: If the TCI field is not present in the DCI, the default transmission beam of the second PDSCH or the second PUSCH is determined in the same manner as the first PDSCH or the first PUSCH.

[0015] In one possible implementation, the method further includes: obtaining the number of the second PDSCH or the second PUSCH, or the proportion of the second PDSCH or the second PUSCH among multiple PDSCHs or PUSCHs; when the number of the second PDSCH or the second PUSCH is greater than or equal to a number threshold, or the proportion of the second PDSCH or the second PUSCH among multiple PDSCHs or PUSCHs is greater than or equal to a proportion threshold, determining the transmission beam corresponding to the second PDSCH or the second PUSCH using method one or method two; when the number of the second PDSCH or the second PUSCH is less than the number threshold, or the proportion of the second PDSCH or the second PUSCH among multiple PDSCHs or PUSCHs is less than the proportion threshold, determining the transmission beam corresponding to the second PDSCH or the second PUSCH using method three.

[0016] A second aspect of this disclosure provides a beamforming device that performs some or all of the functions of the terminal device described in the first aspect. For example, the beamforming device may perform some or all of the functions described in the embodiments of this disclosure, or it may perform the functions of any one embodiment of this disclosure individually. These functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0017] A third aspect of this disclosure provides a beam determination apparatus, the apparatus including a processor that, when the processor invokes a computer program in memory, executes the method described in the first aspect.

[0018] The fourth aspect of this disclosure provides another beam determination apparatus, which includes a processor and a memory, wherein the memory stores a computer program that, when executed by the processor, performs the method described in the first aspect.

[0019] The fifth aspect of this disclosure provides another beam determination apparatus, which includes a processor and an interface circuit for receiving code instructions and transmitting them to the processor, which executes the code instructions to cause the apparatus to perform the method described in the first aspect above.

[0020] A sixth aspect of this disclosure provides a communication system that includes the beam determining device described in the second aspect, or the beam determining device described in the third aspect, or the beam determining device described in the fourth aspect, or the beam determining device described in the fifth aspect.

[0021] A seventh aspect of this disclosure provides a computer-readable storage medium for storing instructions for use by the aforementioned terminal device, which, when executed, cause the terminal device to perform the method described in the first aspect.

[0022] An eighth aspect of this disclosure provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0023] A ninth aspect of this disclosure provides a chip system including at least one processor and an interface for supporting a network device in implementing the functions involved in the first aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the network device. The chip system may be composed of chips or may include chips and other discrete devices.

[0024] A tenth aspect of this disclosure provides a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above. Attached Figure Description

[0025] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.

[0026] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this disclosure;

[0027] Figure 2 This is a schematic diagram of a scheduling offset with PDSCH that is less than timeDurationForQCL;

[0028] Figure 3 This is a schematic flowchart of a beam determination method provided in an embodiment of this disclosure;

[0029] Figure 4 This is a schematic flowchart of another beam determination method provided in an embodiment of this disclosure;

[0030] Figure 5 This is a flowchart illustrating another beam determination method provided in this embodiment of the disclosure;

[0031] Figure 6 This is a flowchart illustrating another beam determination method provided in this embodiment of the disclosure;

[0032] Figure 7 This is a flowchart illustrating another beam determination method provided in this embodiment of the disclosure;

[0033] Figure 8 This is a flowchart illustrating another beam determination method provided in this embodiment of the disclosure;

[0034] Figure 9 This is a schematic flowchart of another beam determination method provided in an embodiment of this disclosure;

[0035] Figure 10This is another schematic diagram showing that the scheduling offset of PDSCH is less than timeDurationForQCL;

[0036] Figure 11 This is a schematic diagram of the structure of a beam determining device provided in an embodiment of this disclosure;

[0037] Figure 12 This is a schematic diagram of the structure of a beam determining device provided in an embodiment of this disclosure;

[0038] Figure 13 This is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure. Detailed Implementation

[0039] To better understand the beam determination method disclosed in this embodiment, the communication system to which this embodiment applies will be described below.

[0040] To make the objectives, technical solutions, and advantages of this disclosure clearer, the embodiments of this disclosure will be described in further detail below with reference to the accompanying drawings.

[0041] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. Unless otherwise indicated, the same numerals in different drawings denote the same or similar elements in the following description relating to the drawings. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0042] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of the present disclosure. The communication system may include, but is not limited to, a network device and a terminal device. Figure 1 The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of this disclosure. In actual applications, two or more network devices and two or more terminal devices may be included. Figure 1 The communication system shown is exemplified by a network device 101 and a terminal device 102.

[0043] It should be noted that the technical solutions of this disclosure can be applied to various communication systems. For example, Long Term Evolution (LTE) systems, 5th Generation (5G) mobile communication systems, 5G New Radio (NR) systems, or other future new mobile communication systems.

[0044] The network device 101 in this embodiment is a network-side entity used for transmitting or receiving signals. For example, the network device 101 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. This disclosure does not limit the specific technology or device form used in the network device. The network device provided in this disclosure can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure allows the protocol layer of a network device, such as a base station, to be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0045] The terminal device 102 in this disclosure is a user-side entity used to receive or transmit signals, such as a mobile phone. The terminal device can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device can be a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, etc. This disclosure does not limit the specific technology or device form used in the terminal device.

[0046] In the aforementioned communication system, within the 52.6-71 GHz range, a single DCI can schedule multiple PDSCH / PUSCHs to reduce the overhead of blind detection of the PDCCH (physical downlink control channel). Unlike traditional PDSCH aggregation / repetition, each PDSCH / PUSCH transmits a different TB (Transport Block). Furthermore, each PDSCH / PUSCH is confined to a single time slot.

[0047] For the above situation, it is necessary to specify the beam confirmation method of the PDSCH / PUSCH (that is, since the concept of multiple beams is introduced in high frequency band transmission, compared with low frequency band transmission, high frequency band transmission has not only time domain and frequency domain resource locations, but also spatial domain resource locations, in which different beam directions are used to distinguish different spatial domain resource locations).

[0048] When there is a situation where the scheduling offset of PDSCH / PUSCH is less than the QCL (Quasi co-location) time length (i.e., timeDurationForQCL), such as... Figure 2 As shown, `timeDurationForQCL` represents the minimum time overhead required for the terminal device to receive the PDCCH and use the QCL information in the DCI to receive the PDSCH. At this point, the default beam for these PDSCHs needs to be determined. That is, after the DCI is sent, there is a period of silence during which the terminal device can wait before sending service data. However, there are also situations where the configured time for sending service data falls within this silence period, for example... Figure 2 The Physical Downlink Shared Channel 1 (PDSCH1) in the data is currently undetermined as to which beam it is transmitted with.

[0049] When the scheduling offset of all PDSCH / PUSCH in a DCI is greater than or equal to timeDurationForQCL, the receive / transmit beam corresponding to each PDSCH / PUSCH can be determined according to the beam indicated by the TCI (transmission configuration indicator) field in the DCI. However, if there is no TCI field in the DCI, the receive / transmit beam corresponding to each PDSCH / PUSCH can be determined according to the beam of the PDCCH that schedules the PDSCH / PUSCH.

[0050] In related technologies, for PDSCH aggregation in Rel15: if there is a PDSCH with a scheduling offset less than timeDurationForQCL, then all PDSCHs use the default beam. That is, the beam with the smallest CORESET (control resource set) ID is used in the slot that most recently needs to detect PDCCH.

[0051] For the repetition transmission strategy of mTRP (Multi-TRP) in Rel16: If there is a PDSCH with a scheduling offset less than timeDurationForQCL, then all PDSCHs use the default beam. That is, if the terminal device is configured to enable two default TCI states (i.e., enableTwoDefaultTCIStates-r16), then from all codepoints corresponding to the TCI field, the smallest codepoint containing both TCI states is determined, and the beam associated with the smallest codepoint is used as the default beam for the PDSCH; if the terminal device is not configured to enableTwoDefaultTCIStates-r16, then the beam corresponding to the smallest CORESETID in the nearest slot that needs to detect the PDCCH is used.

[0052] However, in the existing protocol's multi-slot (multiple slot) PDSCH scheduling, when there is a PDSCH scheduling offset less than timeDurationForQCL, all PDSCHs use the beam determined by the default method. This default method of beam determination is not the optimal beam.

[0053] Because existing protocols transmit the same TB across multiple time slots in PDSCH, although not using optimal beamforming, this repetitive transmission across multiple time slots makes the overall transmission performance acceptable. However, for the newly proposed DCI scheduling of multiple PDSCH / PUSCH in the 52.6-71GHz range, each PDSCH / PUSCH transmits a different TB, thus eliminating the redundant gain. If the same default beamforming method is used for multi-time slot PDSCH as in the current protocol, there will be a significant performance penalty.

[0054] To address the aforementioned issues, this disclosure provides a method and apparatus for beam determination.

[0055] It is understood that the communication system described in the embodiments of this disclosure is for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and does not constitute a limitation on the technical solutions provided in the embodiments of this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this disclosure are also applicable to similar technical problems.

[0056] The beam determination method and apparatus provided in this disclosure will now be described in detail with reference to the accompanying drawings.

[0057] Please see Figure 3 , Figure 3 This is a schematic flowchart illustrating a beam determination method provided in an embodiment of this disclosure. The beam determination method can be performed by... Figure 1 The terminal device in the communication system shown performs the following.

[0058] like Figure 3 As shown, the method for determining this beam may include, but is not limited to, the following steps:

[0059] Step 301: When a DCI schedules multiple PDSCHs or PUSCHs, determine the transmission beams corresponding to the multiple PDSCHs or PUSCHs, wherein the multiple PDSCHs or PUSCHs transmit different TBs.

[0060] In this embodiment of the disclosure, the transmission beam may include a receive beam and a transmit beam. When a DCI schedules multiple PDSCHs, the transmission beam may be a receive beam. When a DCI schedules multiple PUSCHs, the transmission beam may be a transmit beam.

[0061] In this embodiment of the disclosure, when a DCI schedules multiple PDSCHs, the receive beam corresponding to each PDSCH can be determined, wherein each PDSCH is used to transmit a different TB. Alternatively, when a DCI schedules multiple PUSCHs, the transmit beam corresponding to each PUSCH can be determined, wherein each PUSCH is used to transmit a different TB.

[0062] The beam determination method of this disclosure determines the transmission beams corresponding to multiple PDSCHs or PUSCHs when a DCI schedules multiple PDSCHs or PUSCHs, wherein the multiple PDSCHs or PUSCHs transmit different TBs. Therefore, a terminal device can determine the receive beams corresponding to each PDSCH scheduled by a DCI, or determine the transmit beams corresponding to each PUSCH scheduled by a DCI, thereby enabling communication with network devices based on the determined beams.

[0063] Please see Figure 4, Figure 4 This is a schematic flowchart illustrating another beam determination method provided in this embodiment of the disclosure. This beam determination method can be performed by... Figure 1 The beam determination method is executed by a terminal device in the communication system shown. This beam determination method can be executed alone, or it can be executed in conjunction with any embodiment of this disclosure or any possible implementation thereof, or it can be executed in conjunction with any technical solution in the related art.

[0064] like Figure 4 As shown, the method for determining this beam may include, but is not limited to, the following steps:

[0065] Step 401: When a DCI schedules multiple PDSCHs or PUSCHs, determine the first PDSCH or first PUSCH among the multiple PDSCHs or PUSCHs, wherein the scheduling offset of the first PDSCH or first PUSCH is less than timeDurationForQCL.

[0066] In this embodiment of the disclosure, when a DCI schedules multiple PDSCHs, a first PDSCH with a scheduling offset less than a predefined timeDurationForQCL can be determined from the multiple PDSCHs, wherein the number of first PDSCHs can be at least one. Alternatively, when a DCI schedules multiple PUSCHs, a first PUSCH with a scheduling offset less than a predefined timeDurationForQCL can be determined from the multiple PUSCHs, wherein the number of first PUSCHs can be at least one.

[0067] As an example, we will illustrate this by having a DCI schedule multiple PDSCHs, such as... Figure 2 As shown, the first PDSCH can be Figure 2 The physical downlink shared channel 1, namely PDSCH1.

[0068] Step 402: Determine the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0069] The default transmission beam can include the default receive beam and the default transmission beam. When a DCI schedules multiple PDSCHs, the default transmission beam can be the default receive beam. When a DCI schedules multiple PUSCHs, the default transmission beam can be the default transmit beam.

[0070] In the embodiments of this disclosure, when a DCI schedules multiple PDSCHs, the default receive beam corresponding to each first PDSCH can be determined; or, when a DCI schedules multiple PUSCHs, the default transmit beam corresponding to each first PUSCH can be determined.

[0071] The beam determination method of this disclosure, when a DCI schedules multiple PDSCHs or PUSCHs, determines a first PDSCH or first PUSCH among the multiple PDSCHs or PUSCHs, wherein the scheduling offset of the first PDSCH or first PUSCH is less than timeDurationForQCL; and determines the default transmission beam corresponding to the first PDSCH or first PUSCH. Thus, the terminal device can determine the default transmission beam corresponding to the first PDSCH or first PUSCH whose scheduling offset is less than timeDurationForQCL.

[0072] It should be noted that the above-mentioned possible implementations can be executed individually or in combination, and this disclosure does not limit them.

[0073] Please see Figure 5 , Figure 5 This is a schematic flowchart illustrating another beam determination method provided in this embodiment of the disclosure. This beam determination method can be performed by... Figure 1 The beam determination method is executed by a terminal device in the communication system shown. This beam determination method can be executed alone, or it can be executed in conjunction with any embodiment of this disclosure or any possible implementation thereof, or it can be executed in conjunction with any technical solution in the related art.

[0074] like Figure 5 As shown, the method for determining this beam may include, but is not limited to, the following steps:

[0075] Step 501: When a DCI schedules multiple PDSCHs or PUSCHs, determine the first PDSCH or first PUSCH among the multiple PDSCHs or PUSCHs, wherein the scheduling offset of the first PDSCH or first PUSCH is less than timeDurationForQCL.

[0076] In the embodiments of this disclosure, step 501 can be implemented in any of the various embodiments of this disclosure. This disclosure does not limit this implementation and will not elaborate further.

[0077] Step 502: When the DCI is a single DCI in a single TRP scenario, obtain the time slot of the reference PDCCH before the first PDSCH or the first PUSCH.

[0078] In this embodiment of the disclosure, when multiple PDSCHs are scheduled in a single DCI, in response to the aforementioned DCI being a single TRP scenario, the time slot of the reference PDCCH preceding the first PDSCH can be obtained. The reference PDCCH can be the most recently detected PDCCH preceding the first PDSCH.

[0079] Similarly, when a DCI schedules multiple PUSCHs, in the case of a single DCI in a single TRP scenario, the time slot of the reference PDCCH preceding the first PUSCH can be obtained. The reference PDCCH can be the most recently detected PDCCH preceding the first PUSCH.

[0080] Step 503: Obtain the beam corresponding to the CORESET with the smallest CORESET ID detected in the time slot of the reference PDCCH, and use it as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0081] In this embodiment of the disclosure, when multiple PDSCHs are scheduled in a DCI, the beam corresponding to the CORESET with the smallest CORESET ID detected in the time slot of the reference PDCCH can be obtained and used as the default receive beam corresponding to the first PDSCH. The reference PDCCH is the most recently detected PDCCH preceding the first PDSCH.

[0082] Similarly, when scheduling multiple PUSCHs in a single DCI, the beam corresponding to the CORESET with the smallest CORESET ID detected in the time slot of the reference PDCCH can be obtained and used as the default transmission beam for the first PUSCH. The reference PDCCH is the most recent PDCCH that needs to be detected before the first PUSCH.

[0083] The beam determination method of this disclosure, when a DCI schedules multiple PDSCHs or PUSCHs, determines a first PDSCH or first PUSCH among the multiple PDSCHs or PUSCHs, wherein the scheduling offset of the first PDSCH or first PUSCH is less than timeDurationForQCL; when the DCI is a single DCI in a single TRP scenario, it obtains the time slot of a reference PDCCH preceding the first PDSCH or first PUSCH; it obtains the beam corresponding to the CORESET with the smallest CORESET ID detected in the time slot of the reference PDCCH, and uses it as the default transmission beam corresponding to the first PDSCH or first PUSCH. Thus, the terminal device can determine the default transmission beam corresponding to the first PDSCH or first PUSCH whose scheduling offset is less than timeDurationForQCL.

[0084] It should be noted that the above-mentioned possible implementations can be executed individually or in combination, and this disclosure does not limit them.

[0085] Please see Figure 6 , Figure 6 This is a schematic flowchart illustrating another beam determination method provided in this embodiment of the disclosure. This beam determination method can be performed by... Figure 1 The beam determination method is executed by a terminal device in the communication system shown. This beam determination method can be executed alone, or it can be executed in conjunction with any embodiment of this disclosure or any possible implementation thereof, or it can be executed in conjunction with any technical solution in the related art.

[0086] like Figure 6 As shown, the method for determining this beam may include, but is not limited to, the following steps:

[0087] Step 601: When a DCI schedules multiple PDSCHs or PUSCHs, determine the first PDSCH or first PUSCH among the multiple PDSCHs or PUSCHs, wherein the scheduling offset of the first PDSCH or first PUSCH is less than timeDurationForQCL.

[0088] In the embodiments of this disclosure, step 601 can be implemented in any of the various embodiments of this disclosure. This disclosure does not limit this implementation and will not elaborate further.

[0089] Step 602: When the DCI is a multi-DCI in a multi-TRP scenario based on multiple DCI, obtain the time slot of the reference PDCCH before the first PDSCH or the first PUSCH.

[0090] In this embodiment of the disclosure, when a DCI schedules multiple PDSCHs, in response to the DCI being one of the multiple DCIs in a multi-DCI based mTRP scenario, the time slot of a reference PDCCH preceding the first PDSCH can be obtained. The reference PDCCH can be the most recently detected PDCCH preceding the first PDSCH.

[0091] Similarly, when multiple PUSCHs are scheduled in a single DCI, in response to the aforementioned DCI being a multi-DCI based mTRP scenario, the time slot of the reference PDCCH preceding the first PUSCH can be obtained. The reference PDCCH can be the most recently detected PDCCH preceding the first PUSCH.

[0092] Step 603: Obtain the beam corresponding to the CORESET with the smallest CORESET ID among multiple CORESETs with the same control resource set pool index CORESET PoolIndex detected in the time slot of the reference PDCCH, and use it as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0093] In this embodiment of the disclosure, when multiple PDSCHs are scheduled in a DCI, the beam corresponding to the CORESET with the smallest CORESET ID among multiple CORESETs with the same CORESET PoolIndex detected in the time slot of the reference PDCCH can be obtained and used as the default receive beam corresponding to the first PDSCH. The reference PDCCH is the most recently detected PDCCH preceding the first PDSCH.

[0094] Similarly, when scheduling multiple PUSCHs in a single DCI, the beam corresponding to the CORESET with the smallest CORESET ID among multiple CORESETs with the same CORESET PoolIndex detected in the time slot of the reference PDCCH can be obtained and used as the default transmission beam for the first PUSCH. The reference PDCCH is the most recent PDCCH that needs to be detected before the first PUSCH.

[0095] The beam determination method of this disclosure, when a DCI schedules multiple PDSCHs or PUSCHs, determines a first PDSCH or first PUSCH among the multiple PDSCHs or PUSCHs, wherein the scheduling offset of the first PDSCH or first PUSCH is less than timeDurationForQCL; when the DCI is a multi-DCI in a multi-TRP scenario based on multiple DCIs, the time slot of the reference PDCCH preceding the first PDSCH or first PUSCH is obtained; the beam corresponding to the CORESET with the smallest CORESET ID among multiple CORESETs with the same CORESET PoolIndex detected in the time slot of the reference PDCCH is obtained and used as the default transmission beam corresponding to the first PDSCH or first PUSCH. Thus, the terminal device can determine the default transmission beam corresponding to the first PDSCH or first PUSCH whose scheduling offset is less than timeDurationForQCL.

[0096] It should be noted that the above-mentioned possible implementations can be executed individually or in combination, and this disclosure does not limit them.

[0097] Please see Figure 7 , Figure 7 This is a schematic flowchart illustrating another beam determination method provided in this embodiment of the disclosure. This beam determination method can be performed by... Figure 1 The beam determination method is executed by a terminal device in the communication system shown. This beam determination method can be executed alone, or it can be executed in conjunction with any embodiment of this disclosure or any possible implementation thereof, or it can be executed in conjunction with any technical solution in the related art.

[0098] like Figure 7 As shown, the method for determining this beam may include, but is not limited to, the following steps:

[0099] Step 701: When a DCI schedules multiple PDSCHs or PUSCHs, determine the first PDSCH or first PUSCH among the multiple PDSCHs or PUSCHs, wherein the scheduling offset of the first PDSCH or first PUSCH is less than timeDurationForQCL.

[0100] In the embodiments of this disclosure, step 701 can be implemented in any of the various embodiments of this disclosure. This disclosure does not limit this implementation and will not elaborate further.

[0101] Step 702: When the DCI is a single DCI in a multi-TRP scenario based on a single DCI, determine whether the terminal device has configured the enable flag EnableTwoDefaultTCIStates. If yes, proceed to step 703; otherwise, proceed to step 704.

[0102] The enable flag EnableTwoDefaultTCIStates indicates that the terminal device is allowed to use two default TCI states.

[0103] In this embodiment of the disclosure, when the above-mentioned DCI is a single DCI based Multi-TRP scenario, it can be determined whether the terminal device is configured with the enable flag EnableTwoDefaultTCIStates. For example, taking the terminal device as a terminal device conforming to the R16 standard as an example, the enable flag can be enableTwoDefaultTCIStates-r16, where the enable flag is used to indicate that the terminal device is allowed to use two default TCI states.

[0104] Step 703: Obtain the beam associated with the smallest code point containing two TCI states in the code point corresponding to the TCI field, and use it as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0105] In this embodiment of the disclosure, in response to the terminal device configuring EnableTwoDefaultTCIStates, the beam associated with the smallest code point containing the two TCI states in the code point corresponding to the TCI field is obtained and used as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0106] Step 704: Obtain the beam corresponding to the CORESET with the smallest CORESET ID in the time slot of the reference PDCCH, and use it as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0107] In this embodiment of the disclosure, in response to the terminal device not configuring EnableTwoDefaultTCIStates, the beam corresponding to the CORESET with the smallest CORESET ID in the time slot of the reference PDCCH is obtained and used as the default transmission beam corresponding to the first PDSCH or the first PUSCH. Specifically, when multiple PDSCHs are scheduled in one DCI, the aforementioned reference PDCCH is the most recently detected PDCCH preceding the first PDSCH; when multiple PUSCHs are scheduled in one DCI, the aforementioned reference PDCCH is the most recently detected PDCCH preceding the first PUSCH.

[0108] The beam determination method of this disclosure, when a DCI schedules multiple PDSCHs or PUSCHs, determines the first PDSCH or first PUSCH among the multiple PDSCHs or PUSCHs, wherein the scheduling offset of the first PDSCH or first PUSCH is less than timeDurationForQCL; when the DCI is a single DCI in a multi-TRP scenario based on a single DCI, it determines whether the terminal device has configured the enable flag EnableTwoDefaultTCIStates, wherein the enable flag is used to indicate that the terminal device is allowed to use two default TCI states; in response to the terminal device configuring EnableTwoDefaultTCIStates, the beam associated with the smallest code point containing the two TCI states in the code point corresponding to the TCI field is obtained and used as the default transmission beam corresponding to the first PDSCH or first PUSCH; in response to the terminal device not configuring EnableTwoDefaultTCIStates, the beam corresponding to the CORESET with the smallest CORESET ID in the time slot of the reference PDCCH is obtained and used as the default transmission beam corresponding to the first PDSCH or first PUSCH. Therefore, the terminal device can determine the default transmission beam corresponding to the first PDSCH or the first PUSCH whose scheduling offset is less than timeDurationForQCL.

[0109] It should be noted that the above-mentioned possible implementations can be executed individually or in combination, and this disclosure does not limit them.

[0110] In any embodiment of this disclosure, when a DCI schedules multiple PDSCH / PUSCH, for the first PDSCH or the first PUSCH whose scheduling offset value is less than timeDurationForQCL (e.g., Figure 2 The Physical Downlink Shared Channel 1 (PDSCH1) can be used to determine the default transmission beam corresponding to the first PDSCH or the first PUSCH in the following manner:

[0111] The following situations exist:

[0112] First, when the above-mentioned DCI is a single DCI under a single TRP scenario, the nearest PDCCH that needs to be detected before the first PDSCH or the first PUSCH can be determined. In this disclosure, the beam corresponding to the CORESET with the smallest CORESET ID detected in the time slot of the reference PDCCH is used as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0113] Second, when the above DCI is a multi-DCI based mTRP scenario, the beam corresponding to the CORESET with the smallest CORESET ID among the multiple CORESETs with the same CORESET PoolIndex detected in the time slot of the reference PDCCH can be determined and used as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0114] Third, when the above DCI is a single DCI based Multi-TRP scenario, it can be determined whether the terminal device is configured with the enable flag EnableTwoDefaultTCIStates. For example, taking a terminal device that conforms to the R16 standard as an example, the enable flag can be enableTwoDefaultTCIStates-r16, where the enable flag is used to indicate that the terminal device is allowed to use two default TCI states.

[0115] In response to the terminal device configuring EnableTwoDefaultTCIStates, the beam associated with the smallest code point containing both TCI states corresponding to the code point in the TCI field is used as the default transmission beam for the first PDSCH or the first PUSCH. The correspondence (or mapping relationship) between the two TCI states corresponding to the aforementioned code point and the first PDSCH is the same as the correspondence in existing protocols such as FDMSchemeA (Frequency Division Multiplexing Scheme A), FDMSchemeB (Frequency Division Multiplexing Scheme B), and TDMSchemeA (Time Division Multiplexing Scheme A), without considering the mapping relationship of the repetition transmission scheme.

[0116] In response to the terminal device not configuring the enable flag EnableTwoDefaultTCIStates, the beam corresponding to the CORESET with the smallest CORESET ID in the time slot of the reference PDCCH will be used as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0117] Please see Figure 8 , Figure 8 This is a schematic flowchart illustrating another beam determination method provided in this embodiment of the disclosure. This beam determination method can be performed by... Figure 1The beam determination method is executed by a terminal device in the communication system shown. This beam determination method can be executed alone, or it can be executed in conjunction with any embodiment of this disclosure or any possible implementation thereof, or it can be executed in conjunction with any technical solution in the related art.

[0118] like Figure 8 As shown, the method for determining this beam may include, but is not limited to, the following steps:

[0119] Step 801: When a DCI schedules multiple PDSCHs or PUSCHs, determine the second PDSCH or second PUSCH among the multiple PDSCHs or PUSCHs, wherein the scheduling offset of the second PDSCH or second PUSCH is greater than or equal to timeDurationForQCL.

[0120] In embodiments of this disclosure, when a DCI schedules multiple PDSCHs, a second PDSCH with a scheduling offset greater than or equal to a predefined timeDurationForQCL can be determined from the multiple PDSCHs, wherein the number of second PDSCHs can be at least one. Alternatively, when a first DCI schedules multiple PUSCHs, a second PUSCH with a scheduling offset greater than or equal to a predefined timeDurationForQCL can be determined from the multiple PUSCHs, wherein the number of second PUSCHs can be at least one.

[0121] As an example, we will illustrate this by having a DCI schedule multiple PDSCHs, such as... Figure 2 As shown, the second PDSCH can be Figure 2 Physical downlink shared channel 2 (PDSCH2), physical downlink shared channel 3 (PDSCH3), and physical downlink shared channel 4 (PDSCH4) are included.

[0122] Step 802: Determine the transmission beam corresponding to the second PDSCH or the second PUSCH.

[0123] In the embodiments of this disclosure, when a DCI schedules multiple PDSCHs, the receiving beam corresponding to each second PDSCH can be determined; or, when a DCI schedules multiple PUSCHs, the transmitting beam corresponding to each second PUSCH can be determined.

[0124] In one possible implementation of the present disclosure, if the DCI has a TCI field, the beam indicated by the TCI field in the DCI can be used as the transmission beam corresponding to the second PDSCH or the second PUSCH.

[0125] In another possible implementation of this disclosure, when the DCI does not have a TCI field, when the DCI schedules multiple PDSCHs, the beam of the PDCCH that schedules the second PDSCH can be used as the receive beam corresponding to the second PDSCH. Similarly, when the DCI schedules multiple PUSCHs, the beam of the PDCCH that schedules the second PUSCH can be used as the transmit beam corresponding to the second PUSCH.

[0126] In another possible implementation of the embodiments of this disclosure, when there is no TCI field in the DCI, the default transmission beam of the second PDSCH or the second PUSCH can be determined in the same way as the first PDSCH or the first PUSCH. That is, the second PDSCH can use the same beam as the first PDSCH, and the second PUSCH can use the same beam as the first PUSCH.

[0127] The beam determination method of this disclosure, when a DCI schedules multiple PDSCHs or PUSCHs, determines a second PDSCH or second PUSCH among the multiple PDSCHs or PUSCHs, wherein the scheduling offset of the second PDSCH or second PUSCH is greater than or equal to Time DurationForQCL; and determines the transmission beam corresponding to the second PDSCH or second PUSCH. Thus, the terminal device can determine the default receive beam corresponding to the second PDSCH whose scheduling offset is greater than or equal to timeDurationForQCL, or determine the default transmit beam corresponding to the second PUSCH whose scheduling offset is greater than or equal to timeDurationForQCL.

[0128] It should be noted that the above-mentioned possible implementations can be executed individually or in combination, and this disclosure does not limit them.

[0129] In any embodiment of this disclosure, when a DCI schedules multiple PDSCH / PUSCH, for the second PDSCH or second PUSCH (e.g., with a scheduling offset value greater than or equal to timeDurationForQCL)... Figure 2 The physical downlink shared channels 2, 3, and 4 (i.e., PDSCH2, 3, and 4) can be used to determine the transmission beam corresponding to the second PDSCH or the second PUSCH in the following manner:

[0130] Method 1: Use the beam indicated by the TCI field in the above DCI as the transmission beam corresponding to the second PDSCH or the second PUSCH.

[0131] Method 2: If there is no TCI domain in the above DCI, then the beam of the PDCCH that schedules the second PDSCH will be used as the receiving beam corresponding to the second PDSCH, or the beam of the PDCCH that schedules the second PUSCH will be used as the transmitting beam corresponding to the second PUSCH.

[0132] Method 3: Determine the default transmission beam of the second PDSCH or second PUSCH in the same way as the first PDSCH or first PUSCH.

[0133] Please see Figure 9 , Figure 9 This is a schematic flowchart illustrating another beam determination method provided in this embodiment of the disclosure. This beam determination method can be performed by... Figure 1 The beam determination method is executed by a terminal device in the communication system shown. This beam determination method can be executed alone, or it can be executed in conjunction with any embodiment of this disclosure or any possible implementation thereof, or it can be executed in conjunction with any technical solution in the related art.

[0134] like Figure 9 As shown, the method for determining this beam may include, but is not limited to, the following steps:

[0135] Step 901: When a DCI schedules multiple PDSCHs or PUSCHs, determine the second PDSCH or second PUSCH among the multiple PDSCHs or PUSCHs, wherein the scheduling offset of the second PDSCH or second PUSCH is greater than or equal to timeDurationForQCL.

[0136] In the embodiments of this disclosure, step 901 can be implemented in any of the various embodiments of this disclosure. This disclosure does not limit this implementation and will not elaborate further.

[0137] Step 902: Obtain the number of second PDSCHs or second PUSCHs, or the proportion of second PDSCHs or second PUSCHs among multiple PDSCHs or PUSCHs.

[0138] In this embodiment of the disclosure, when a DCI schedules multiple PDSCHs, the number of second PDSCHs can be determined, or the proportion of the second PDSCHs among the multiple PDSCHs can be determined. An example is given where a DCI schedules four PDSCHs. Figure 2 As shown, the number of second PDSCHs is 3, and the proportion of second PDSCHs among multiple PDSCHs is 3 / 4 = 75%.

[0139] Similarly, when a DCI schedules multiple PUSCHs, the number of second PUSCHs can be determined, or the proportion of the second PUSCHs among the multiple PUSCHs can be determined.

[0140] Step 903: When the number of second PDSCH or second PUSCH is greater than or equal to the number threshold, or the proportion of second PDSCH or second PUSCH among multiple PDSCH or PUSCH is greater than or equal to the proportion threshold, the transmission beam corresponding to the second PDSCH or second PUSCH is determined by method one or method two.

[0141] The quantity threshold and the proportion threshold can be preset, for example, through protocol agreement, or through network device configuration and sent to the terminal device.

[0142] In this embodiment of the disclosure, when a DCI schedules multiple PDSCHs, in response to the number of second PDSCHs being greater than or equal to a number threshold, or the proportion of the second PDSCH among the multiple PDSCHs being greater than or equal to a proportion threshold, either method one or method two can be used to determine the receiving beam corresponding to the second PDSCH.

[0143] In the case where the DCI has a TCI field, the beam indicated by the TCI field in the DCI can be used as the receiving beam corresponding to the second PDSCH. Conversely, if the DCI does not have a TCI field, the beam of the PDCCH that schedules the second PDSCH can be used as the receiving beam corresponding to the second PDSCH.

[0144] Similarly, when a DCI schedules multiple PUSCHs, in response to the number of second PUSCHs being greater than or equal to a quantity threshold, or the proportion of the second PUSCH among the multiple PUSCHs being greater than or equal to a proportion threshold, the transmission beam corresponding to the second PUSCH can be determined using either method one or method two.

[0145] In other words, if the DCI has a TCI field, the beam indicated by the TCI field in the DCI can be used as the transmit beam corresponding to the second PUSCH. If the DCI does not have a TCI field, the beam of the PDCCH that schedules the second PUSCH can be used as the transmit beam corresponding to the second PUSCH.

[0146] Step 904: When the number of second PDSCH or second PUSCH is less than the number threshold, or the proportion of second PDSCH or second PUSCH among multiple PDSCH or PUSCH is less than the proportion threshold, the transmission beam corresponding to the second PDSCH or second PUSCH is determined by method three.

[0147] In this embodiment of the disclosure, when a DCI schedules multiple PDSCHs, in response to the number of second PDSCHs being less than a quantity threshold, or the proportion of the second PDSCH among the multiple PDSCHs being less than a proportion threshold, method three can be used to determine the receiving beam corresponding to the second PDSCH. That is, in the case that the DCI does not have a TCI domain, the default receiving beam of the second PDSCH can be determined in the same way as the first PDSCH.

[0148] This is illustrated by an example of scheduling multiple PDSCHs using a single DCI, such as... Figure 10 As shown, the second PDSCH can be Figure 10 In the physical downlink shared channel 4, i.e. PDSCH4, the number of second PDSCHs is 1, and the proportion of the second PDSCH among the multiple PDSCHs is 1 / 4 = 25%. Assuming the number threshold is 2 and the proportion threshold is 50%, then method three can be used to determine the receiving beam corresponding to the second PDSCH.

[0149] As an example, when the above DCI is a single DCI under a single TRP scenario, the nearest PDCCH that needs to be detected before the second PDSCH can be determined. In this disclosure, the beam corresponding to the CORESET with the smallest CORESET ID detected in the time slot of the reference PDCCH is used as the default receiving beam corresponding to the second PDSCH.

[0150] As another example, when the above DCI is a multi-DCI based mTRP scenario, the nearest PDCCH to be detected before the second PDSCH can be determined, that is, the beam corresponding to the CORESET with the smallest CORESET ID among multiple CORESETs with the same CORESET PoolIndex detected in the time slot of the reference PDCCH, and used as the default receiving beam corresponding to the second PDSCH.

[0151] As another example, when the aforementioned DCI is a single DCI based Multi-TRP scenario, it can be determined whether the terminal device has configured the enable flag EnableTwoDefaultTCIStates. If the terminal device has configured EnableTwoDefaultTCIStates, the beam associated with the smallest code point containing both TCI states in the TCI field is used as the default receive beam for the second PDSCH. If the terminal device has not configured the enable flag EnableTwoDefaultTCIStates, the beam corresponding to the CORESET with the smallest CORESET ID in the reference PDCCH time slot is used as the default receive beam for the second PDSCH.

[0152] Similarly, when a DCI schedules multiple PUSCHs, if the number of second PUSCHs is less than a quantity threshold, or if the proportion of the second PUSCH among the multiple PUSCHs is less than a proportion threshold, method three can be used to determine the transmission beam corresponding to the second PUSCH. That is, in the absence of a TCI domain in the DCI, the default transmission beam of the second PUSCH can be determined in the same way as the first PUSCH.

[0153] As an example, when the above DCI is a single DCI under a single TRP scenario, the nearest PDCCH that needs to be detected before the second PUSCH can be determined. In this disclosure, the beam corresponding to the CORESET with the smallest CORESET ID detected in the time slot of the reference PDCCH is denoted as the beam and is used as the default transmission beam corresponding to the second PUSCH.

[0154] As another example, when the above DCI is a multi-DCI based mTRP scenario, the nearest PDCCH to be detected before the second PUSCH can be determined. That is, the beam corresponding to the CORESET with the smallest CORESET ID among the multiple CORESETs with the same CORESET PoolIndex detected in the time slot of the reference PDCCH can be used as the default transmission beam corresponding to the second PUSCH.

[0155] As another example, when the aforementioned DCI is a single DCI based Multi-TRP scenario, it can be determined whether the terminal device has configured the enable flag EnableTwoDefaultTCIStates. If the terminal device has configured EnableTwoDefaultTCIStates, the beam associated with the smallest code point containing both TCI states in the TCI field is used as the default transmission beam for the second PUSCH. If the terminal device has not configured the enable flag EnableTwoDefaultTCIStates, the beam corresponding to the CORESET with the smallest CORESET ID in the reference PDCCH time slot is used as the default transmission beam for the second PUSCH.

[0156] In any embodiment of this disclosure, when a DCI schedules multiple PDSCH / PUSCH, it can also determine whether to use the Single QCLassumption to determine the beam corresponding to each PDSCH / PUSCH, or the Multiple QCLassumption to determine the beam corresponding to each PDSCH / PUSCH, based on the number or ratio of the second PDSCH / second PUSCH.

[0157] The Single QCL assumption refers to the second PDSCH using the same beam as the first PDSCH, or the second PUSCH using the same beam as the first PDSCH, i.e., the beam used by the second PDSCH / second PUSCH is determined by method three; the Multiple QCL assumption refers to the beam used by the second PDSCH / second PUSCH, which is determined by method one or method two.

[0158] As an example, when the number of second PDSCHs is greater than or equal to the number threshold, or when the proportion of the second PDSCH among multiple PDSCHs is greater than or equal to the proportion threshold, the Multiple QCL assumption can be used to determine the beam corresponding to the second PDSCH; otherwise, the Single QCL assumption can be used to determine the beam corresponding to the second PDSCH.

[0159] Similarly, when the number of second PUSCHs is greater than or equal to the number threshold, or when the proportion of the second PUSCH among multiple PUSCHs is greater than or equal to the proportion threshold, the Multiple QCL assumption is used to determine the beam corresponding to the second PUSCH; otherwise, the Single QCL assumption is used to determine the beam corresponding to the second PUSCH.

[0160] When using the Multiple QCL assumption, the default transmit beam or default receive beam can be determined using either Method 1 or Method 2.

[0161] When using the Single QCL assumption, the default transmit beam or default receive beam can be determined using method three.

[0162] In any embodiment of this disclosure, when the boundary value of timeDurationForQCL (i.e., the cutoff time) is within a certain slot, the PDSCH / PUSCH of that slot is classified as a PDSCH / PUSCH with a scheduling offset value less than timeDurationForQCL, that is, the PDSCH / PUSCH in that slot belongs to the first PDSCH or the first PUSCH in this disclosure.

[0163] In summary, by introducing the multiple QCL assumption to determine the default transmit or receive beam, optimal performance can be obtained for the second PDSCH with a scheduling offset value greater than or equal to timeDurationForQCL by using the indicated beam.

[0164] The beam determination method of this disclosure involves obtaining the number of second PDSCHs or second PUSCHs, or the proportion of second PDSCHs or second PUSCHs among multiple PDSCHs or PUSCHs. When the number of second PDSCHs or second PUSCHs is greater than or equal to a number threshold, or the proportion of second PDSCHs or second PUSCHs among multiple PDSCHs or PUSCHs is greater than or equal to a proportion threshold, method one or method two is used to determine the transmission beam corresponding to the second PDSCH or second PUSCH. When the number of second PDSCHs or second PUSCHs is less than a number threshold, or the proportion of second PDSCHs or second PUSCHs among multiple PDSCHs or PUSCHs is less than a proportion threshold, method three is used to determine the transmission beam corresponding to the second PDSCH or second PUSCH. Therefore, it is possible for the terminal device to determine the default transmission beam corresponding to the second PDSCH or second PUSCH whose scheduling offset is greater than or equal to timeDurationForQCL.

[0165] It should be noted that the above-mentioned possible implementations can be executed individually or in combination, and this disclosure does not limit them.

[0166] In any embodiment of this disclosure, when the scheduling offset of a DCI for scheduling multiple PDSCHs or PUSCHs is greater than timeDurationForQCL, either method one or method two can be used to determine the transmission beam corresponding to each PDSCH or PUSCH. That is, if the DCI has a TCI field, the beam indicated by the TCI field is used as the receiving beam corresponding to each PDSCH or the transmitting beam corresponding to each PUSCH; if the DCI does not have a TCI field, the beam of the PDCCH that schedules the PDSCH is used as the receiving beam corresponding to the PDSCH, or the beam of the PDCCH that schedules the PUSCH is used as the transmitting beam corresponding to the PUSCH.

[0167] The methods provided in the embodiments of this disclosure above are described from the perspective of a terminal device. To implement the functions of the methods provided in the embodiments of this disclosure above, the terminal device may include hardware structures and software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. One of the above functions may be executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules.

[0168] Please see Figure 11 This is a schematic diagram of the structure of a beam determining device 110 provided in an embodiment of this disclosure. Figure 11The beam determination device 110 shown may include a processing unit 1101. Optionally, the beam determination device 110 may also include a transceiver unit, which may include a transmitting unit and / or a receiving unit. The transmitting unit is used to implement the transmitting function, and the receiving unit is used to implement the receiving function. The transceiver unit can implement both the transmitting and / or receiving functions.

[0169] The beam-determining device 110 can be a terminal device, a device within a terminal device, or a device that can be used in conjunction with a terminal device.

[0170] The beam determination device 130 is a terminal device: a processing unit 1101, used to determine the transmission beams corresponding to multiple PDSCHs or PUSCHs when a downlink control information DCI schedules multiple physical downlink shared channels (PDSCHs) or physical uplink shared channels (PUSCHs), wherein multiple PDSCHs or PUSCHs transmit different transport blocks (TBs).

[0171] In some embodiments, the processing unit 1101 is specifically used to: determine a first PDSCH or a first PUSCH among a plurality of PDSCHs or PUSCHs, wherein the scheduling offset of the first PDSCH or the first PUSCH is less than the quasi-co-location time length timeDurationForQCL; and determine the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0172] In some embodiments, the processing unit 1101 is specifically used to: when the DCI is a single DCI in a single TRP scenario, obtain the time slot of the reference PDCCH before the first PDSCH or the first PUSCH; obtain the beam corresponding to the CORESET with the minimum control resource set CORESET ID detected in the time slot of the reference PDCCH, and use it as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0173] In some embodiments, the processing unit 1101 is specifically used to: when the DCI is a multi-DCI in a multi-TRP scenario based on multiple DCI, obtain the time slot of the reference PDCCH before the first PDSCH or the first PUSCH; obtain the beam corresponding to the CORESET with the smallest CORESET ID among multiple CORESETs with the same control resource set pool index CORESET PoolIndex detected in the time slot of the reference PDCCH, and use it as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0174] In some embodiments, the processing unit 1101 is specifically configured to: when the DCI is a single DCI in a multi-TRP scenario based on a single DCI, determine whether the terminal device has configured the enable flag EnableTwoDefaultTCIStates, the enable flag being used to indicate that the terminal device is allowed to use two default TCI states; in response to the terminal device configuring EnableTwoDefaultTCIStates, obtain the beam associated with the smallest code point containing the two TCI states in the code point corresponding to the TCI field, and use it as the default transmission beam corresponding to the first PDSCH or the first PUSCH; in response to the terminal device not configuring EnableTwoDefaultTCIStates, obtain the beam corresponding to the CORESET with the smallest CORESET ID in the time slot of the reference PDCCH, and use it as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

[0175] In some embodiments, the processing unit 1101 is specifically used to: refer to the PDCCH as the most recently detected PDCCH before the first PDSCH or the first PUSCH.

[0176] In some embodiments, the processing unit 1101 is specifically used to: determine a second PDSCH or a second PUSCH among a plurality of PDSCHs or PUSCHs, wherein the scheduling offset of the second PDSCH or the second PUSCH is greater than or equal to TimeDurationForQCL; and determine the transmission beam corresponding to the second PDSCH or the second PUSCH.

[0177] In some embodiments, the processing unit 1101 is specifically configured to: determine the transmission beam corresponding to the second PDSCH or the second PUSCH according to any of the following methods:

[0178] Method 1: When there is a Transmission Indication Configuration TCI field in the DCI, the beam indicated by the TCI field is used as the transmission beam corresponding to the second PDSCH or the second PUSCH.

[0179] Method 2: In the absence of a TCI domain in the DCI, the beam of the physical lower layer control channel PDCCH that schedules the second PDSCH or the second PUSCH is used as the transmission beam corresponding to the second PDSCH or the second PUSCH.

[0180] Method 3: In the absence of a TCI field in the DCI, determine the default transmission beam of the second PDSCH or second PUSCH in the same manner as the first PDSCH or first PUSCH.

[0181] In some embodiments, the processing unit 1101 is specifically configured to: obtain the number of second PDSCHs or second PUSCHs, or the proportion of second PDSCHs or second PUSCHs among multiple PDSCHs or PUSCHs; when the number of second PDSCHs or second PUSCHs is greater than or equal to a quantity threshold, or the proportion of second PDSCHs or second PUSCHs among multiple PDSCHs or PUSCHs is greater than or equal to a proportion threshold, determine the transmission beam corresponding to the second PDSCH or second PUSCH using method one or method two; when the number of second PDSCHs or second PUSCHs is less than a quantity threshold, or the proportion of second PDSCHs or second PUSCHs among multiple PDSCHs or PUSCHs is less than a proportion threshold, determine the transmission beam corresponding to the second PDSCH or second PUSCH using method three.

[0182] It should be noted that the aforementioned Figures 3 to 9 The explanation of the method executed on the terminal device side in any embodiment also applies to the beam determination device 130 of this embodiment, and its implementation principle is similar, so it will not be repeated here.

[0183] Please see Figure 12 , Figure 12 This is a schematic diagram of another beam determination device provided in an embodiment of this disclosure. The beam determination device 120 can be a terminal device, or it can be a chip, chip system, or processor that supports the terminal device in implementing the above method. This device can be used to implement the method described in the above method embodiments, and for details, please refer to the description in the above method embodiments.

[0184] The beamforming device 120 may include one or more processors 1201. The processor 1201 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the beamforming device (e.g., base station, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0185] Optionally, the beam-determining device 120 may further include one or more memories 1202, on which a computer program 1203 may be stored. The processor 1201 executes the computer program 1203 to cause the beam-determining device 120 to perform the method described in the above method embodiments. The computer program 1203 may be embedded in the processor 1201, in which case the processor 1201 may be implemented in hardware.

[0186] Optionally, the memory 1202 may also store data. The beam-determining device 120 and the memory 1202 can be configured separately or integrated together.

[0187] Optionally, the beamforming device 120 may further include a transceiver 1205 and an antenna 1206. The transceiver 1205, also known as a transceiver unit, transceiver, or transceiver circuit, is used to implement transceiver functions. The transceiver 1205 may include a receiver and a transmitter. The receiver, also known as a receiver circuit, is used to implement a receiving function; the transmitter, also known as a transmitter or transmitting circuit, is used to implement a transmitting function.

[0188] Optionally, the beamforming device 120 may further include one or more interface circuits 1207. The interface circuits 1207 are used to receive code instructions and transmit them to the processor 1201. The processor 1201 executes the code instructions to cause the beamforming device 120 to perform the method described in the above method embodiments.

[0189] The beam determination device 120 is a terminal device: a processor 1201, used to execute any of the method embodiments described above in this disclosure.

[0190] It should be noted that the aforementioned Figures 3 to 9 The explanation of the beam determination method in any embodiment also applies to the beam determination device 120 in this embodiment, and the implementation principle is similar, so it will not be repeated here.

[0191] In one implementation, the processor 1201 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0192] In one implementation, the beam-determining device 120 may include circuitry capable of transmitting, receiving, or communicating as described in the aforementioned method embodiments. The processor and transceiver described in this disclosure can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide-semiconductor (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal-oxide-semiconductor (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0193] The beam-determining device described in the above embodiments can be a terminal device, but the scope of the beam-determining device described in this disclosure is not limited thereto, and the structure of the beam-determining device is not subject to change. Figure 12 The limitations. The beam-determining device can be a standalone device or part of a larger device. For example, the beam-determining device could be:

[0194] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0195] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0196] (3) ASIC, such as modem;

[0197] (4) Modules that can be embedded in other devices;

[0198] (5) Receivers, terminal equipment, smart terminal equipment, cellular phones, wireless equipment, handheld devices, mobile units, vehicle-mounted equipment, network equipment, cloud equipment, artificial intelligence equipment, etc.

[0199] (6) Others, etc.

[0200] For cases where the beam-determining device can be a chip or a chip system, please refer to [reference needed]. Figure 13 The diagram shows the structure of the chip. Figure 13 The chip shown includes a processor 1301 and an interface 1302. There can be one or more processors 1301, and multiple interfaces 1302.

[0201] Regarding the case where the chip is used to implement the functions of the terminal device in the embodiments of this disclosure:

[0202] Interface 1302 is used for code instructions and their transmission to the processor;

[0203] Processor 1301 is used to run code instructions to perform tasks such as Figures 3 to 9 The method.

[0204] Optionally, the chip also includes a memory 1303, which is used to store necessary computer programs and data.

[0205] It should be noted that the aforementioned Figures 3 to 9 The explanation of the beam determination method in any embodiment also applies to the chip in this embodiment, as the implementation principle is similar and will not be repeated here.

[0206] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this disclosure can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented in hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this disclosure.

[0207] This disclosure also provides a communication system, which includes the aforementioned... Figure 12 The embodiment refers to a beam determination device as a terminal device, or the system includes the aforementioned... Figure 13 The embodiment describes a beam determination device used as a terminal device.

[0208] This disclosure also provides a readable storage medium having instructions stored thereon that, when executed by a computer, implement the functions of any of the above method embodiments.

[0209] This disclosure also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0210] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0211] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., used in this disclosure are merely for the convenience of description and are not intended to limit the scope of the embodiments of this disclosure, nor do they indicate the order of events.

[0212] At least one of the features described in this disclosure can also be described as one or more, and multiple features can be two, three, four or more, and this disclosure does not impose any limitations. In the embodiments of this disclosure, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no sequential order or size order among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0213] It is understood that in this disclosure, "multiple" refers to two or more, and other quantifiers are similar. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. The singular forms "a," "the," and "the" are also intended to include the plural forms unless the context clearly indicates otherwise.

[0214] The word “if” as used here can be interpreted as “when”, “when”, or “in response to determination”.

[0215] The correspondences shown in the tables of this disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this disclosure is not limiting. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this disclosure may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headings of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables. The predefined terms in this disclosure can be understood as definitions, pre-defined, stored, pre-stored, pre-negotiated, pre-configured, fixed, or pre-burned.

[0216] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure. It will be clearly understood by those skilled in the art that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0217] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A method for determining a beam, characterized in that, The method is executed by a terminal device, and the method includes: When a downlink control information (DCI) schedules multiple physical downlink shared channels (PDSCH) or physical uplink shared channels (PUSCH), the transmission beams corresponding to the multiple PDSCH or PUSCH are determined, wherein the multiple PDSCH or PUSCH transmit different transport blocks (TB). Determining the transmission beams corresponding to the plurality of PDSCHs or PUSCHs includes: Determine the first PDSCH or first PUSCH among the plurality of PDSCH or PUSCH, wherein the scheduling offset of the first PDSCH or first PUSCH is less than the quasi-co-location time length timeDurationForQCL. Determine the default transmission beam corresponding to the first PDSCH or the first PUSCH; The step of determining the default transmission beam corresponding to the first PDSCH or the first PUSCH includes: When the DCI is a single DCI in a multi-TRP scenario based on a single DCI, it is determined whether the terminal device is configured with the enable flag EnableTwoDefaultTCIStates. The enable flag is used to indicate that the terminal device is allowed to use two default TCI states. In response to the terminal device configuring EnableTwoDefaultTCIStates, the beam associated with the smallest code point containing the two TCI states in the code point corresponding to the TCI field is obtained and used as the default transmission beam corresponding to the first PDSCH or the first PUSCH; wherein, the correspondence between the two TCI states corresponding to the code point and the first PDSCH is the same as the correspondence between TDMSchemeA.

2. The method as described in claim 1, characterized in that, The step of determining the default transmission beam corresponding to the first PDSCH or the first PUSCH further includes: When the DCI is a single DCI in a single transmit receiver point (TRP) scenario, the time slot of the reference PDCCH before the first PDSCH or the first PUSCH is obtained. The beam corresponding to the CORESET with the smallest control resource set CORESET ID detected in the time slot of the reference PDCCH is obtained and used as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

3. The method as described in claim 1, characterized in that, The step of determining the default transmission beam corresponding to the first PDSCH or the first PUSCH further includes: When the DCI is a multi-DCI in a multi-TRP scenario based on multiple DCI, the time slot of the reference PDCCH before the first PDSCH or the first PUSCH is obtained. The beam corresponding to the CORESET with the smallest CORESET ID among multiple CORESETs with the same control resource pool index CORESETPoolIndex detected in the time slot of the reference PDCCH is used as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

4. The method as described in claim 1, characterized in that, The step of determining the default transmission beam corresponding to the first PDSCH or the first PUSCH further includes: In response to the terminal device not configuring EnableTwoDefaultTCIStates, the beam corresponding to the CORESET with the smallest CORESET ID in the time slot of the reference PDCCH is obtained and used as the default transmission beam corresponding to the first PDSCH or the first PUSCH.

5. The method according to any one of claims 2-4, characterized in that, The reference PDCCH is the most recent PDCCH that needs to be detected before the first PDSCH or the first PUSCH.

6. The method according to any one of claims 1-5, characterized in that, Also includes: Determine the second PDSCH or second PUSCH among the plurality of PDSCH or PUSCH, wherein the scheduling offset of the second PDSCH or second PUSCH is greater than or equal to the quasi-co-location time length Time DurationForQCL; Determine the transmission beam corresponding to the second PDSCH or the second PUSCH.

7. The method as described in claim 6, characterized in that, The transmission beam corresponding to the second PDSCH or the second PUSCH is determined according to any of the following methods: Method 1: If the DCI has a Transmission Indication Configuration TCI field, the beam indicated by the TCI field is used as the transmission beam corresponding to the second PDSCH or the second PUSCH. Method 2: If the TCI domain is not present in the DCI, the beam of the physical lower layer control channel PDCCH that schedules the second PDSCH or the second PUSCH is used as the transmission beam corresponding to the second PDSCH or the second PUSCH. Method 3: If the TCI field is not present in the DCI, the default transmission beam of the second PDSCH or the second PUSCH is determined in the same manner as the first PDSCH or the first PUSCH.

8. The method as described in claim 7, characterized in that, Also includes: Obtain the number of the second PDSCH or the second PUSCH, or the proportion of the second PDSCH or the second PUSCH among multiple PDSCH or PUSCH; When the number of the second PDSCH or the second PUSCH is greater than or equal to the number threshold, or the proportion of the second PDSCH or the second PUSCH among multiple PDSCH or PUSCH is greater than or equal to the proportion threshold, the transmission beam corresponding to the second PDSCH or the second PUSCH is determined by method one or method two. When the number of the second PDSCH or the second PUSCH is less than the number threshold, or the proportion of the second PDSCH or the second PUSCH among multiple PDSCHs or PUSCHs is less than the proportion threshold, the transmission beam corresponding to the second PDSCH or the second PUSCH is determined by method three.

9. A beam-determining device, characterized in that, Applied to terminal devices, including: The processing unit is used to determine the transmission beams corresponding to the multiple physical downlink shared channels (PDSCH) or physical uplink shared channels (PUSCH) when a downlink control information (DCI) schedules multiple physical downlink shared channels (PDSCH) or physical uplink shared channels (PUSCH), wherein the multiple PDSCH or PUSCH transmit different transport blocks (TB). Determining the transmission beams corresponding to the plurality of PDSCHs or PUSCHs includes: Determine the first PDSCH or first PUSCH among the plurality of PDSCH or PUSCH, wherein the scheduling offset of the first PDSCH or first PUSCH is less than the quasi-co-location time length timeDurationForQCL. Determine the default transmission beam corresponding to the first PDSCH or the first PUSCH; The step of determining the default transmission beam corresponding to the first PDSCH or the first PUSCH includes: When the DCI is a single DCI in a multi-TRP scenario based on a single DCI, it is determined whether the terminal device is configured with the enable flag EnableTwoDefaultTCIStates. The enable flag is used to indicate that the terminal device is allowed to use two default TCI states. In response to the terminal device configuring EnableTwoDefaultTCIStates, the beam associated with the smallest code point containing the two TCI states in the code point corresponding to the TCI field is obtained and used as the default transmission beam corresponding to the first PDSCH or the first PUSCH; wherein, the correspondence between the two TCI states corresponding to the code point and the first PDSCH is the same as the correspondence between TDMSchemeA.

10. A beam-determining device, characterized in that, The device includes a processor and a memory, the memory storing a computer program that, when executed by the processor, performs the method as described in any one of claims 1 to 8.

11. A beam-determining device, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to perform the method as described in any one of claims 1 to 8.

12. A computer-readable storage medium for storing instructions that, when executed, cause the method of any one of claims 1 to 8 to be implemented.

Images