CN110719632B

Movatterモバイル変換

Info

Publication number: CN110719632B
Application number: CN201810766144.6A
Authority: CN
Inventors: 杨宇; 孙鹏
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2018-07-12
Filing date: 2018-07-12
Publication date: 2021-08-24
Anticipated expiration: 2038-07-12
Also published as: CN110719632A

Abstract

Translated fromChinese

本发明提供了一种准共址确定方法、调度方法、终端及网络设备，涉及通信技术领域。该准共址确定方法，应用于终端或网络设备，包括：在物理下行控制信道PDCCH和所调度的目标物理下行共享信道PDSCH在不同的载波和/或不同的带宽部分BWP时，根据准共址QCL的确定规则，确定目标PDSCH的QCL信息。上述方案，可以使得终端与网络设备对PDSCH QCL信息理解一致，从而提高了数据的准确传输。

The invention provides a quasi-co-location determination method, a scheduling method, a terminal and a network device, and relates to the technical field of communications. The quasi-co-location determination method, applied to a terminal or a network device, includes: when the physical downlink control channel PDCCH and the scheduled target physical downlink shared channel PDSCH are on different carriers and/or different bandwidth parts BWP, according to the quasi-co-location The QCL determination rule determines the QCL information of the target PDSCH. The above solution can make the terminal and the network device have consistent understanding of PDSCH QCL information, thereby improving the accurate transmission of data.

Description

Quasi co-location determining method, scheduling method, terminal and network equipment

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a quasi-co-location determining method, a scheduling method, a terminal, and a network device.

Background

In the prior art, a network side configures a correspondence between a TCI (Transmission Configuration Indication) state and an RS (Reference Signal) for a UE (User Equipment) through an RRC (Radio Resource Control) signaling.

When TCI is used for QCL (Quasi-co-location) indication of PDCCH (Physical Downlink Control Channel), the network configures K TCI states for each CORESET (Control resource set), when K >1, 1 TCI state is indicated by MAC (Media Access Control) CE (Control elements), and when K is 1, no additional MAC CE signaling is required. When listening to the CORESET (control resource set), the UE uses the same QCL, i.e. the same TCI state, for all search spaces within the CORESET. RS resources (e.g., periodic-State Information Reference Symbol (CSI-RS) resources, semi-persistent CSI-RS resources, SSBs, etc.) and UE-specific PDCCH DMRS (Demodulation Reference signal) ports in the RS set corresponding to the TCI State are spatial QCLs. The UE can know which receiving beam is used to receive the PDCCH according to the TCI status.

When TCI is used for QCL indication of PDSCH (Physical Downlink Shared Channel), the network activates 2^NAnd then informing the TCI state through an N-bit TCI field (region) of the DCI, wherein RS resources in an RS set corresponding to the TCI state and a DMRS port of the PDSCH to be scheduled are QCL. The UE can know which receiving beam is used to receive the PDSCH according to the TCI status.

The prior art is a method for determining PDSCH QCL information when scheduling on the same carrier (PDCCH and PDSCH are on the same carrier). When receiving DCI (Downlink Control Information) and a time Offset of the PDSCH is less than a preset Threshold (Threshold-Scheduled-Offset), the UE determines the PDSCH QCL Information based on PDCCH QCL Information on CORESET (lowest CORESET-ID) having a minimum ID for serving cell activation BWP.

However, for the case of cross-Carrier (cross Carrier) scheduling, that is, when the time Offset for receiving DCI and PDSCH is smaller than a preset Threshold (Threshold-Scheduled-Offset), when the PDCCH and PDSCH are on different carriers (or referred to as on different CCs (Component carriers), cell cells), if the Carrier where the Scheduled PDSCH is located is not configured with CORESET by the network, or the Carrier where the Scheduled PDSCH is located is configured with CORESET but does not configure TCI state information for CORESET, the UE cannot know how to determine PDSCH QCL information.

Disclosure of Invention

The embodiment of the invention provides a quasi co-location determining method, a scheduling method, a terminal and network equipment, and aims to solve the problems that when cross-carrier scheduling is carried out, UE (user equipment) cannot determine PDSCH (physical Downlink shared channel) QCL (QCL) information, so that the terminal and a base station cannot understand the PDSCH QCL information in a inconsistent manner, and accurate data transmission cannot be guaranteed.

In order to solve the technical problem, the invention adopts the following scheme:

in a first aspect, an embodiment of the present invention provides a quasi-co-location determining method, applied to a terminal or a network device, including:

and when the physical downlink control channel PDCCH and the scheduled target physical downlink shared channel PDSCH are in different carriers and/or different bandwidth parts BWP, determining QCL information of the target PDSCH according to a determination rule of the quasi-co-location QCL.

In a second aspect, an embodiment of the present invention provides a method for scheduling a physical downlink shared channel, which is applied to a network device, and includes:

when a Physical Downlink Control Channel (PDCCH) and a scheduled target Physical Downlink Shared Channel (PDSCH) are on different carriers and/or different bandwidth parts (BWP), acquiring a scheduling rule of the target PDSCH;

determining quasi co-location QCL information of the target PDSCH according to the scheduling rule;

and transmitting the target PDSCH according to the QCL information.

In a third aspect, an embodiment of the present invention provides a method for scheduling a physical downlink shared channel, where the method is applied to a terminal and includes:

when a Physical Downlink Control Channel (PDCCH) and a scheduled target Physical Downlink Shared Channel (PDSCH) are on different carriers and/or different bandwidth parts (BWPs), and when the time offset between the receiving time of the DCI and the receiving time of the target PDSCH is smaller than a preset threshold value, determining QCL information of the target PDSCH based on QCL information indicated by TCI state information configured by network equipment for a first control resource set in the carrier and/or the BWP where the target PDSCH is located;

and receiving the target PDSCH according to the QCL information.

In a fourth aspect, an embodiment of the present invention provides a quasi-co-location determining apparatus, where the quasi-co-location determining apparatus is a terminal or a network device, and includes:

a first determining module, configured to determine QCL information of the target PDSCH according to a determination rule of the quasi-co-located QCL when the PDCCH and the scheduled PDSCH are on different carriers and/or different bandwidth portions BWP.

In a fifth aspect, an embodiment of the present invention provides a quasi-co-location determining apparatus, where the quasi-co-location determining apparatus is a terminal or a network device, and includes: a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the quasi co-location determination method described above.

In a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium, where the computer-readable storage medium stores thereon a computer program, and the computer program, when executed by a processor, implements the steps of the quasi co-location determination method described above

In a seventh aspect, an embodiment of the present invention provides a network device, including:

an obtaining module, configured to obtain a scheduling rule of a target PDSCH when a PDCCH and the scheduled PDSCH are on different carriers and/or different bandwidth portions BWP;

a second determining module, configured to determine quasi-co-located QCL information of the target PDSCH according to the scheduling rule;

and the sending module is used for sending the target PDSCH according to the QCL information.

In an eighth aspect, an embodiment of the present invention provides a network device, including: the scheduling method comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the computer program realizes the steps of the scheduling method for the physical downlink shared channel when being executed by the processor.

In a ninth aspect, an embodiment of the present invention provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and the computer program, when executed by a processor, implements the steps of the scheduling method for a physical downlink shared channel described above.

In a tenth aspect, an embodiment of the present invention provides a terminal, including:

a third determining module, configured to determine, when a physical downlink control channel PDCCH and a scheduled target physical downlink shared channel PDSCH are on different carriers and/or different bandwidth portions BWP and a time offset between a receiving time of a DCI and a receiving time of the target PDSCH is smaller than a preset threshold, QCL information of the target PDSCH based on QCL information indicated by TCI state information configured by a network device for a first control resource set in the carrier and/or BWP where the target PDSCH is located;

a receiving module, configured to receive the target PDSCH according to the QCL information.

In an eleventh aspect, an embodiment of the present invention provides a terminal, including: the scheduling method comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the computer program realizes the steps of the scheduling method for the physical downlink shared channel when being executed by the processor.

In a twelfth aspect, an embodiment of the present invention provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and the computer program, when executed by a processor, implements the steps of the scheduling method for a physical downlink shared channel described above.

The invention has the advantages that the QCL information of the target PDSCH is determined according to the QCL determination rule when the PDCCH and the scheduled PDSCH are in different carriers and/or different BWPs, so that the terminal and the network equipment can understand the QCL information of the PDSCH consistently, and the accurate transmission of data is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.

FIG. 1 is a block diagram of a network system suitable for use in embodiments of the present invention;

fig. 2 is a schematic flowchart of a quasi-co-location determination method according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating a scheduling method of a physical downlink shared channel applied to a network device according to an embodiment of the present invention;

fig. 4 is a flowchart illustrating a scheduling method of a physical downlink shared channel applied to a terminal according to an embodiment of the present invention;

FIG. 5 is a block diagram of a quasi-co-location determining apparatus according to an embodiment of the present invention;

FIG. 6 is a block diagram of a network device according to an embodiment of the invention;

FIG. 7 is a block diagram of a network device according to an embodiment of the present invention;

fig. 8 is a block diagram of a terminal according to an embodiment of the present invention;

fig. 9 is a block diagram of a terminal according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged under appropriate circumstances such that embodiments of the application described herein may be implemented, for example, in a sequence other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Furthermore, the use of "and/or" in the specification and claims means that at least one of the connected objects, such as a and/or B, means that three cases, a alone, B alone, and both a and B, exist.

In the embodiments of the present invention, words such as "exemplary" or "for example" are used to mean serving as examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "e.g.," an embodiment of the present invention is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

Embodiments of the present invention are described below with reference to the accompanying drawings. The quasi co-location determining method, the scheduling method, the terminal and the network equipment provided by the embodiment of the invention can be applied to a wireless communication system. The wireless communication system may be a system adopting a 5th Generation (5G) mobile communication technology (hereinafter, referred to as a 5G system), and those skilled in the art will appreciate that the 5G NR system is only an example and is not a limitation.

Referring to fig. 1, fig. 1 is a structural diagram of a network system to which an embodiment of the present invention is applicable, and as shown in fig. 1, the network system includes aUser terminal 11 and abase station 12, where theUser terminal 11 may be a User Equipment (UE), for example: the terminal side Device may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer), a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), or a Wearable Device (Wearable Device), and it should be noted that the specific type of theuser terminal 11 is not limited in the embodiments of the present invention. Thebase station 12 may be a base station of 5G and later releases (e.g., a gNB, a 5G NR NB), or a base station in other communication systems, or referred to as a node B, and it should be noted that, in the embodiment of the present invention, only the 5G base station is taken as an example, but the specific type of thebase station 12 is not limited.

In making the description of the embodiments of the present invention, some concepts used in the following description will first be explained.

Radio access technology standards such as Long Term Evolution (Long Term Evolution)/Long Term Evolution (LTE-Advanced) are constructed based on Multiple-Input Multiple-Output (MIMO-MIMO) + Orthogonal Frequency Division Multiplexing (OFDM) technology. The MIMO technology utilizes spatial freedom available in a multi-antenna system to improve peak rate and system spectrum utilization.

The dimension of the MIMO technology is continuously expanding in the process of standardization development. In LTE Rel-8, MIMO transmission of up to 4 layers can be supported. In Rel-9, an MU-MIMO (Multi-User MIMO Multi-User multiple input multiple output) technology is enhanced, and at most 4 downlink data layers can be supported in MU-MIMO Transmission of TM (Transmission Mode) -8. The transmission capability of SU-MIMO (Single-User MIMO, Single-User multiple input multiple output) is extended to a maximum of 8 data layers in Rel-10.

The industry is further pushing MIMO technology towards three-dimensionality and large-scale. Currently, 3GPP (3rd Generation Partnership Project) has completed a research Project for 3D channel modeling, and research and standardization work for eFD-MIMO and NR (New Radio) MIMO is underway. It is expected that in the future 5G (5th Generation, fifth Generation) mobile communication system, a larger-scale, more antenna-port MIMO technology will be introduced.

Massive MIMO technology uses Massive antenna array, which can greatly improve the utilization efficiency of system frequency band and support larger number of access users. Therefore, the massive MIMO technology is considered by various research organizations as one of the most potential physical layer technologies in the next generation mobile communication system.

In the massive MIMO technology, if a full Digital array is adopted, the maximized spatial resolution and the optimal MU-MIMO performance can be achieved, but such a structure requires a large number of AD (Analog-to-Digital)/DA (Digital-to-Analog) conversion devices and a large number of complete rf-baseband processing channels, which is a huge burden in terms of both equipment cost and baseband processing complexity.

In order to avoid the implementation cost and the equipment complexity, a digital-analog hybrid beamforming technology is developed, that is, on the basis of the conventional digital domain beamforming, a primary beamforming is added to a radio frequency signal near the front end of an antenna system. Analog forming enables a sending signal to be roughly matched with a channel in a simpler mode. The dimension of the equivalent channel formed after analog shaping is smaller than the actual number of antennas, so that the AD/DA conversion devices, the number of digital channels and the corresponding baseband processing complexity required thereafter can be greatly reduced. The residual interference of the analog forming part can be processed once again in the digital domain, thereby ensuring the quality of MU-MIMO transmission. Compared with full digital forming, digital-analog hybrid beam forming is a compromise scheme of performance and complexity, and has a high practical prospect in a system with a high frequency band and a large bandwidth or a large number of antennas.

In the next Generation communication system research after 4G (4th Generation), the operating frequency band supported by the system is increased to 6GHz or more, up to about 100 GHz. The high frequency band has richer idle frequency resources, and can provide higher throughput for data transmission. At present, 3GPP has completed high-frequency channel modeling work, the wavelength of a high-frequency signal is short, and compared with a low-frequency band, more antenna array elements can be arranged on a panel with the same size, and a beam with stronger directivity and narrower lobes is formed by using a beam forming technology. Therefore, the combination of a large-scale antenna and high-frequency communication is one of the trends in the future.

In NR Rel-15, the maximum channel bandwidth per carrier is 400 MHz. But considering the UE (User Equipment) capability, the maximum bandwidth supported by the UE may be less than 400MHz, and the UE may operate on multiple small BWPs (bandwidth parts). Each bandwidth part corresponds to a Numerology, bandwidth, frequency location. For FDD (Frequency Division duplex) systems or paired spectrum, the base station configures up to four downlink BWPs and up to four uplink BWPs for the UE. For TDD (Time Division duplex) systems or unpaired spectrum, the base station allocates up to four DL (DownLink)/UL (UpLink) BWP pair to the UE. The center carrier frequency of DL BWP and UL BWP in each DL/UL BWP pair is the same. In addition, each UE will have a default DL BWP, or default DL/UL BWP pair. The default DL BWP or default DL/UL BWP pair is usually a BWP with a relatively small bandwidth, and when the UE does not receive data for a long time or detects a PDCCH, the UE switches from the current active BWP to the default DL BWP or default DL/UL BWP pair through a timer, thereby achieving the power saving effect. The Active BWP handover is implemented by RRC (Radio Resource Control), DCI (Downlink Control Information), or timer, for example, DCI on a first CORESET (Control Resource set) indicates the UE to handover to a second CORESET, and the CORESET is Active BWP after the UE is handed over to the second CORESET. CORESET per BWP per cell is at most 3.

The CORESET (CORESET #0) having ID of 0 is configured by PBCH (Physical Broadcast Channel) (MIB) for the UE to receive system information (system information). For broadcast PDCCH (Physical Downlink Control Channel), the UE determines which SSB (Synchronization signal block) corresponds to the (common search space) common search space. For a unicast PDSCH (Physical Downlink Shared Channel), it may be scheduled by a DCI associated with CORESET # 0.

Analog beamforming is full bandwidth transmit and each polar array element on the panel of each high frequency antenna array can only transmit analog beams in a time division multiplexed manner. The shaping weight of the analog beam is realized by adjusting parameters of equipment such as a radio frequency front end phase shifter and the like.

At present, in academic and industrial fields, a polling method is usually used to train analog beamforming vectors, that is, an array element in each polarization direction of each antenna panel sequentially sends training signals (i.e., candidate beamforming vectors) at an appointed time in a time division multiplexing manner, and a terminal feeds back a beamforming report after measurement, so that a network side can use the training signals to implement analog beamforming transmission when transmitting services next time. The contents of the beam report typically include the optimal number of transmit beam identifications and the measured received power of each transmit beam.

The UE may be configured with up to M TCI states in a higher layer parameter PDSCH-Config for decoding PDSCH according to detected DCI in PDCCH, where M depends on UE capability. Each configured TCI state includes a set of RSs (TCI-RS-SetConfig). Each TCI state contains parameters for configuring a quasi-co-location relationship between one or two downlink reference signals and a DM-RS port group of the PDSCH. The quasi co-location relationship is configured by the high level parameters qcl-Type1 of the first DL RS and qcl-Type2 of the second DL RS (if the DL RS is configured). For the case of two DL RSs, the QCL types of the two DL RSs should not be the same, whether or not they are the same reference signal. QCL-Type in the high-level parameter QCL-Info identifies a quasi co-located Type, which may take one of the following values:

'QCL-type A' { Doppler shift, Doppler spread, average delay, delay spread };

'QCL-TypeB':{Doppler shift,Doppler spread}；

'QCL-TypeC':{Doppler shift,average delay}；

QCL-TypeD' { Spatial Rx parameter (Spatial reception parameter) }.

If the time Offset (time Offset) of receiving DCI and PDSCH is less than a preset Threshold (i.e., Threshold-Scheduled-Offset, which is determined according to capability parameters reported by the UE), the UE determines PDSCH QCL information based on PDCCH QCL information on CORESET (lowest CORESET-ID) with the smallest ID for serving cell activation BWP.

If the time Offset (time Offset) of receiving the DCI and the PDSCH is equal to or greater than a preset Threshold-Scheduled-Offset, when the PDSCH is Scheduled using DCI format 1_1 and the higher layer parameter TCI-PresentInDCI is configured to be enabled, the UE assumes that the DMRS port group of the PDSCH and the RS in the RS set of the TCI status indication in the TCI field are QCL.

If the time Offset (time Offset) of receiving the DCI and the PDSCH is equal to or greater than a preset Threshold-Scheduled-Offset, when the DCI format 1_0 is used to schedule the PDSCH, or when the DCI format 1_1 is used to schedule the PDSCH, and the higher layer parameter TCI-PresentInDCI is configured as disabled, or when the DCI format 1_1 is used to schedule the PDSCH, and the higher layer parameter TCI-PresentInDCI is not configured, the UE assumes that the PDSCH QCL information is the QCL information indicated by the TCI state of the core set where the PDCCH is located.

In order to solve the problem that when cross-carrier scheduling is performed, UE cannot determine PDSCH QCL information, so that understanding of PDSCH QCL information by a terminal and a base station is inconsistent, and accurate data transmission cannot be guaranteed, embodiments of the present invention provide a quasi co-location determining method, a scheduling method, a terminal, and a network device.

Specifically, as shown in fig. 2, fig. 2 is a schematic flowchart of a quasi-co-location determining method according to an embodiment of the present invention, where the quasi-co-location determining method is applied to a terminal or a network device, and includes:

step 201, when the PDCCH and the scheduled PDSCH are on different carriers and/or different bandwidth portions BWP, determining QCL information of the target PDSCH according to the rules for determining quasi co-located QCL.

It should be noted that, instep 201, when the PDCCH and the scheduled target PDSCH are on different carriers and/or different bandwidth portions BWP, and when the network device does not configure a control resource set for the carrier and/or BWP where the target PDSCH is located, or the network device configures a control resource set for the carrier and/or BWP where the target PDSCH is located but does not configure the TCI status information for the control resource set, the step of determining the QCL information of the target PDSCH according to the determination rule of quasi co-located QCL is performed.

It should be noted that, when the PDCCH and the scheduled target PDSCH are on different carriers and/or different BWPs, that is, it indicates that cross-carrier scheduling is performed, in this case, when the network device does not configure a control resource set for the carrier and/or BWP where the target PDSCH is located, or the network device configures a control resource set for the carrier and/or BWP where the target PDSCH is located but does not configure the TCI state information for the control resource set, at this time, there is no scheme for determining the QCL information of the target PDSCH in the prior art.

Theabove step 201 will be specifically described below from different implementations.

The first method and the specific implementation process ofstep 201 are as follows:

and when the time offset between the transmission time of the DCI and the transmission time of the target PDSCH is smaller than a preset threshold value, determining the QCL information of the target PDSCH according to preset QCL information.

It should be noted that the above-mentioned DCI is carried by a PDCCH; specifically, the preset QCL information is configured by the network device or predetermined by a protocol.

Since the implementation manner ofstep 201 may be applied to both the terminal and the network device, whenstep 201 is applied to the terminal, the DCI transmission time refers to a time when the terminal receives DCI, the target PDSCH transmission time refers to a time when the terminal receives the target PDSCH, and the time offset refers to a number of symbols from a last symbol of a PDCCH to a first symbol of the PDSCH, during which time the terminal needs to complete the QCL parameter adjustment required for receiving the PDSCH according to the PDSCH QCL information in the DCI. Whenstep 201 is applied to a network device, the transmission time of DCI refers to the time when the network device transmits DCI, and the transmission time of a target PDSCH refers to the time when the network device transmits the target PDSCH.

Specifically, when preset QCL information is configured by a network device, the preset QCL information is transmitted through Radio Resource Control (RRC) signaling and/or a media access control layer control element (MAC CE); in this case, when the network device determines the QCL information, the network device only needs to obtain the preset QCL information to be sent to the terminal from the network device, and when the terminal determines the QCL information, the terminal needs to receive the preset QCL information sent by the network device through RRC signaling and/or MAC CE.

Specifically, when the preset QCL information is pre-contracted by the protocol, the terminal and the network device may directly acquire the preset QCL information in the network protocol without interaction of target information.

Specifically, the preset QCL information is QCL information belonging to a preset channel and/or a preset reference signal at a preset position; wherein the preset position comprises: a preset carrier and/or a preset BWP. For example, the preset QCL information is QCL information of a control resource set having minimum identification information at a preset position.

It should be noted that, when the time offset is smaller than the preset threshold, the terminal and the network device consider that the pre-configured or pre-agreed certain channel or reference signal and the target PDSCH are quasi co-located.

The second method and the specific implementation process ofstep 201 are as follows:

and in the cell activated by the network device for the terminal, when the network device does not configure a control resource set for the cell and/or the BWP belonging to the preset frequency band, or the network device configures the control resource set for the cell and/or the BWP belonging to the preset frequency band but does not configure the TCI state information for the control resource set, determining the QCL information of the target PDSCH according to the preset QCL information.

It should be noted that, the preset frequency band mentioned herein refers to a frequency band greater than or equal to 6GHz, such as a millimeter wave frequency band.

Specifically, the preset QCL information is configured by the network device or predetermined by a protocol.

Specifically, when preset QCL information is configured by a network device, the preset QCL information is transmitted through RRC signaling and/or MAC CE; in this case, when the network device determines the QCL information, the network device only needs to obtain the preset QCL information to be sent to the terminal from the network device, and when the terminal determines the QCL information, the terminal needs to receive the preset QCL information sent by the network device through RRC signaling and/or MAC CE.

It should be noted that, in this case, the terminal and the network device consider that the pre-configured or pre-agreed certain channel or reference signal is quasi co-located with the target PDSCH.

The third way, the specific implementation process ofstep 201 is:

and in the cells activated by the network equipment for the terminal, when at least one cell monitoring the PDCCH belongs to a preset frequency band, and when the time offset between the DCI transmission time and the target PDSCH transmission time is less than a preset threshold value, determining the QCL information of a control resource set where the first PDCCH is located as the QCL information of the target PDSCH.

Optionally, the first PDCCH is used for scheduling a target PDSCH; or

The first PDCCH is located in a preset control resource set in a cell and/or BWP of a monitored PDCCH of a preset frequency band.

Further, the preset control resource set comprises:

and in a preset cell belonging to the monitored PDCCH in a preset frequency band, a preset BWP is provided with a control resource set with preset identification information.

It should be further noted that the QCL information mentioned above at least includes: the space receives parameters (i.e., parameters contained in QCL-type).

According to the scheme, when the PDCCH and the scheduled PDSCH are on different carriers and/or different BWPs, and when the network device does not configure the control resource set for the carrier and/or BWP where the target PDSCH is located, or the network device configures the control resource set for the carrier and/or BWP where the target PDSCH is located but does not configure TCI state information for the control resource set, the QCL information of the target PDSCH is determined according to the determination rule of the QCL, so that the QCL information of the PDSCH can be understood consistently by the terminal and the network device, and accurate transmission of data is improved.

As shown in fig. 3, an embodiment of the present invention further provides a method for scheduling a physical downlink shared channel, which is applied to a network device, and includes:

step 301, acquiring a scheduling rule of a target PDSCH when a physical downlink control channel PDCCH and the scheduled target PDSCH are on different carriers and/or different bandwidth portions BWP;

step 302, determining quasi co-located QCL information of the target PDSCH according to the scheduling rule;

step 303, transmitting the target PDSCH according to the QCL information.

It should be noted that, in the case of cross-carrier scheduling, the target PDSCH is transmitted according to the scheduling rule of the target PDSCH, so as to ensure smooth transmission of the PDSCH.

Specifically, the scheduling rule includes at least one of the following ways:

a1, configuring a control resource set on a carrier and/or BWP where the scheduled target PDSCH is located, and configuring Transmission Configuration Indication (TCI) state information for the control resource set;

that is, in this case, it is not allowed that the control resource set is not configured on the carrier and/or BWP on which the scheduled PDSCH is located, and it is not allowed that the control resource set is configured on the carrier and/or BWP on which the scheduled PDSCH is located but TCI state information is not configured for the control resource set.

A2, scheduling a target PDSCH to a carrier and/or BWP configured with a control resource set and TCI state information for the control resource set;

that is, in this case, the PDSCH is not allowed to be scheduled using the PDCCH on a carrier and/or BWP on which a control resource set is not configured, and the PDSCH is not allowed to be scheduled using the PDCCH on a carrier and/or BWP on which a control resource set is configured but TCI state information is not configured for the control resource set.

The scheduling rule indicates that the network device always schedules the target PDSCH to the carrier and/or BWP configured with the control resource set and configured with the TCI state information for the control resource set when performing scheduling, so as to avoid the network device from scheduling the target PDSCH to the carrier and/or BWP not configured with the control resource set, or avoid the network device from scheduling the target PDSCH to the carrier and/or BWP configured with the control resource set but not configured with the TCI state information for the control resource set, and further, the determination of the QCL information is not affected, and the accurate transmission of the target PDSCH is ensured.

The above-mentioned configuring the control resource set on the carrier and/or BWP and configuring the TCI state information for the control resource set are all sent to the terminal by the network device through the high-level signaling.

Further, the implementation manner of step 302 is:

when the time offset between the DCI sending time and the target PDSCH sending time is smaller than a preset threshold value, determining QCL information of the target PDSCH based on QCL information indicated by TCI state information configured by the network equipment for a carrier and/or a first control resource set in BWP where the target PDSCH is located.

It should be noted that the above-mentioned DCI is carried by a PDCCH.

Specifically, the first set of control resources has minimal identifying information (i.e., lowest CORESET-ID).

In the embodiment of the invention, the network equipment directly schedules the PDSCH to the carrier and/or BWP which is configured with the control resource set and is configured with the TCI state information for the control resource set during cross-carrier scheduling, thereby not influencing the determination of the QCL information and ensuring the accurate transmission of the target PDSCH.

As shown in fig. 4, an embodiment of the present invention further provides a method for scheduling a physical downlink shared channel, which is applied to a terminal, and includes:

step 401, when a physical downlink control channel PDCCH and a scheduled target physical downlink shared channel PDSCH are on different carriers and/or different bandwidth portions BWP, and when a time offset between a receiving time of a DCI and a receiving time of the target PDSCH is smaller than a preset threshold, determining QCL information of the target PDSCH based on QCL information indicated by TCI state information configured by a network device for a first control resource set in the carrier and/or BWP where the target PDSCH is located;

step 402, receiving the target PDSCH according to the QCL information;

wherein the DCI is carried by the PDCCH.

It should be noted that, in the above embodiment, the preset Threshold refers to a Threshold-Scheduled-Offset or a time duration for QCL in a protocol, and the preset Threshold refers to a scheduling Offset Threshold corresponding to each subcarrier interval supported by the terminal and determined by the network device according to capability information reported by the terminal, and in this time, the terminal needs to complete QCL parameter adjustment, such as beam switching, required for receiving the PDSCH according to PDSCH QCL information in DCI.

As shown in fig. 5, an embodiment of the present invention further provides a quasi-co-location determining apparatus 500, where the quasi-co-location determining apparatus 500 is a terminal or a network device, and includes:

a first determiningmodule 501, configured to determine QCL information of a target PDSCH according to a determination rule of a quasi-co-located QCL when a physical downlink control channel PDCCH and the scheduled target PDSCH are on different carriers and/or different bandwidth portions BWP.

Further, the first determiningmodule 501 is specifically configured to, when the physical downlink control channel PDCCH and the scheduled target physical downlink shared channel PDSCH are on different carriers and/or different bandwidth portions BWP, and when the network device does not configure a control resource set for the carrier and/or BWP where the target PDSCH is located, or the network device configures a control resource set for the carrier and/or BWP where the target PDSCH is located but does not configure the TCI status information for the control resource set, determine the QCL information of the target PDSCH according to the determination rule of quasi co-located QCL.

Optionally, the first determiningmodule 501 is configured to:

when the time offset between the transmission time of the DCI and the transmission time of the target PDSCH is smaller than a preset threshold value, determining QCL information of the target PDSCH according to preset QCL information;

the preset QCL information is configured by network equipment or agreed in advance by a protocol;

the DCI is carried by the PDCCH.

Optionally, the first determiningmodule 501 is configured to:

in a cell activated by the network device for a terminal, when the network device does not configure a control resource set for a cell and/or BWP belonging to a preset frequency band, or the network device configures a control resource set for a cell and/or BWP belonging to the preset frequency band but does not configure TCI status information for the control resource set, determining QCL information of the target PDSCH according to preset QCL information;

and the preset QCL information is configured by the network equipment or is predetermined by a protocol.

Further, when the preset QCL information is configured by a network device, the preset QCL information is sent through radio resource control RRC signaling and/or media access control layer control element MAC CE.

Specifically, the preset QCL information is QCL information belonging to a preset channel and/or a preset reference signal at a preset position;

wherein the preset position comprises: a preset carrier and/or a preset BWP. For example, the preset QCL information is QCL information of a control resource set having minimum identification information at a preset position.

Optionally, the first determiningmodule 501 is configured to:

Specifically, the first PDCCH is used for scheduling a target PDSCH; or

The first PDCCH is located in a preset control resource set in a cell and/or BWP of the monitored PDCCH of the preset frequency band.

Specifically, the preset control resource set includes:

and in a preset cell belonging to the monitored PDCCH in the preset frequency band, a preset BWP is provided with a control resource set with preset identification information.

Specifically, the preset frequency band is a frequency band greater than or equal to 6 GHz.

Specifically, the QCL information includes at least: the space receives the parameters.

The quasi-co-location determining apparatus 500 provided in the embodiment of the present invention can implement each process implemented by the terminal or the network device in the method embodiment of fig. 2, and is not described herein again to avoid repetition. The quasico-location determining apparatus 500 of the embodiment of the present invention determines the QCL information of the target PDSCH according to the QCL determination rule when the network device does not configure the control resource set for the carrier and/or BWP where the target PDSCH is located, or the network device configures the control resource set for the carrier and/or BWP where the target PDSCH is located but does not configure the TCI status information for the control resource set when the PDCCH and the scheduled PDSCH are on different carriers and/or different BWPs, so that the terminal and the network device can understand the QCL information of the PDSCH consistently, thereby improving accurate data transmission.

An embodiment of the present invention further provides a quasi-co-location determining apparatus, where the quasi-co-location determining apparatus is a terminal or a network device, and includes: the computer program is executed by the processor to implement each process in the embodiment of the quasi co-location determining method, and the same technical effect can be achieved, and further details are not described here to avoid repetition.

An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process in the foregoing quasi-co-location determining method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

As shown in fig. 6, an embodiment of the present invention further provides anetwork device 600, including:

an obtainingmodule 601, configured to obtain a scheduling rule of a target PDSCH when a physical downlink control channel PDCCH and the scheduled target PDSCH are on different carriers and/or different bandwidth portions BWP;

a second determiningmodule 602, configured to determine quasi-co-located QCL information of the target PDSCH according to the scheduling rule;

a sendingmodule 603, configured to send the target PDSCH according to the QCL information.

Further, the scheduling rule includes at least one of:

configuring a control resource set on a carrier and/or BWP (BWP) where the scheduled target PDSCH is located, and configuring Transmission Configuration Indication (TCI) state information for the control resource set;

scheduling a target PDSCH onto a carrier and/or BWP configured with a set of control resources and for which TCI state information is configured.

Further, the second determiningmodule 602 is configured to:

when the time offset between the sending time of the DCI and the sending time of the target PDSCH is smaller than a preset threshold value, determining QCL information of the target PDSCH based on QCL information indicated by TCI state information configured by the network equipment for a carrier and/or a first control resource set in BWP where the target PDSCH is located;

wherein the DCI is carried by the PDCCH.

Specifically, the first set of control resources has minimal identifying information.

It should be noted that, this network device embodiment is a network device corresponding to the scheduling method applied to the physical downlink shared channel on the network device side, and all implementation manners of the foregoing embodiments are applicable to this network device embodiment, and can also achieve the same technical effect as this.

Fig. 7 is a structural diagram of a network device according to an embodiment of the present invention, which can implement details of the above scheduling method applied to the physical downlink shared channel on the network device side, and achieve the same effect. As shown in fig. 7, thenetwork device 700 includes: aprocessor 701, atransceiver 702, amemory 703 and a bus interface, wherein:

theprocessor 701 is configured to read the program in thememory 703 and execute the following processes:

when a Physical Downlink Control Channel (PDCCH) and a scheduled target Physical Downlink Shared Channel (PDSCH) are on different carriers and/or different bandwidth parts (BWP), acquiring a scheduling rule of the target PDSCH; determining quasi co-location QCL information of the target PDSCH according to the scheduling rule; transmitting the target PDSCH through thetransceiver 702 according to the QCL information.

In fig. 7, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented byprocessor 701, and various circuits, represented bymemory 703, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. Thetransceiver 702 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium.

Theprocessor 701 is responsible for managing the bus architecture and general processing, and thememory 703 may store data used by theprocessor 701 in performing operations.

Wherein the scheduling rule comprises at least one of the following:

Optionally, theprocessor 701 reads the program in thememory 703, and is further configured to execute:

wherein the DCI is carried by the PDCCH.

An embodiment of the present invention further provides a network device, including: the scheduling method for the physical downlink shared channel applied to the network device side includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the computer program is executed by the processor to implement each process in the above-mentioned scheduling method embodiment for the physical downlink shared channel applied to the network device side, and can achieve the same technical effect, and is not described here again to avoid repetition.

An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when executed by a processor, the computer program implements each process in the foregoing scheduling method embodiment applied to a physical downlink shared channel on a network device side, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

The network device may be a Base Transceiver Station (BTS) in Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), a Base Station (NodeB, NB) in Wideband Code Division Multiple Access (WCDMA), an evolved Node B (eNB, eNodeB) in LTE, a relay Station, an Access point, a Base Station in a future 5G network, or the like, which is not limited herein.

As shown in fig. 8, an embodiment of the present invention further provides a terminal 800, including:

a third determiningmodule 801, configured to, when the PDCCH and the scheduled target PDSCH are on different carriers and/or different bandwidth portions BWP, and when a time offset between a receiving time of the DCI and a receiving time of the target PDSCH is smaller than a preset threshold, determine QCL information of the target PDSCH based on QCL information indicated by TCI state information configured by the network device for the first control resource set in the carrier and/or BWP where the target PDSCH is located;

areceiving module 802, configured to receive the target PDSCH according to the QCL information;

wherein the DCI is carried by the PDCCH.

Fig. 9 is a schematic diagram of a hardware structure of a terminal for implementing an embodiment of the present invention.

The terminal 90 includes but is not limited to:radio frequency unit 910,network module 920,audio output unit 930,input unit 940,sensor 950,display unit 960,user input unit 970,interface unit 980,memory 990,processor 911, andpower supply 912. Those skilled in the art will appreciate that the terminal configuration shown in fig. 9 is not intended to be limiting, and that the terminal may include more or fewer components than shown, or some components may be combined, or a different arrangement of components. In the embodiment of the present invention, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palm computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

Theprocessor 911 is configured to, when a physical downlink control channel PDCCH and a scheduled target physical downlink shared channel PDSCH are on different carriers and/or different bandwidth portions BWP, and when a time offset between a receiving time of a DCI and a receiving time of the target PDSCH is smaller than a preset threshold, determine QCL information of the target PDSCH based on QCL information indicated by TCI state information configured by a network device for a first control resource set in the carrier and/or BWP where the target PDSCH is located; theradio frequency unit 910 is configured to receive the target PDSCH according to the QCL information;

wherein the DCI is carried by the PDCCH.

It should be understood that, in the embodiment of the present invention, theradio frequency unit 910 may be used for receiving and sending signals during a message sending and receiving process or a call process, and specifically, after receiving downlink data from a network device, the downlink data is processed by theprocessor 911; in addition, the uplink data is sent to the network device. In general,radio unit 910 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, theradio frequency unit 910 may also communicate with a network and other devices through a wireless communication system.

The terminal provides the user with wireless broadband internet access through thenetwork module 920, such as helping the user send and receive e-mails, browse webpages, access streaming media, and the like.

Theaudio output unit 930 may convert audio data received by theradio frequency unit 910 or thenetwork module 920 or stored in thememory 990 into an audio signal and output as sound. Also, theaudio output unit 930 may also provide audio output related to a specific function performed by the terminal 90 (e.g., a call signal reception sound, a message reception sound, etc.). Theaudio output unit 930 includes a speaker, a buzzer, a receiver, and the like.

Theinput unit 940 is used to receive an audio or video signal. Theinput Unit 940 may include a Graphics Processing Unit (GPU) 941 and amicrophone 942, and theGraphics processor 941 processes image data of still pictures or video obtained by an image capturing device, such as a camera, in a video capturing mode or an image capturing mode. The processed image frames may be displayed on thedisplay unit 960. The image frames processed by thegraphic processor 941 may be stored in the memory 990 (or other storage medium) or transmitted via theradio frequency unit 910 or thenetwork module 920. Themicrophone 942 may receive sound and may be capable of processing such sound into audio data. The processed audio data may be converted into a format output transmittable to the mobile communication network device via theradio frequency unit 910 in case of the phone call mode.

The terminal 90 also includes at least onesensor 950, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that adjusts the brightness of thedisplay panel 961 according to the brightness of ambient light, and a proximity sensor that turns off thedisplay panel 961 and/or a backlight when the terminal 90 moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), detect the magnitude and direction of gravity when stationary, and can be used to identify the terminal posture (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration identification related functions (such as pedometer, tapping), and the like; thesensors 950 may also include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which will not be described in detail herein.

Thedisplay unit 960 serves to display information input by a user or information provided to the user. TheDisplay unit 960 may include aDisplay panel 961, and theDisplay panel 961 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.

Theuser input unit 970 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the terminal. Specifically, theuser input unit 970 includes atouch panel 971 andother input devices 972.Touch panel 971, also referred to as a touch screen, may collect touch operations by a user on or near the touch panel 971 (e.g., operations by a user on or neartouch panel 971 using a finger, a stylus, or any other suitable object or attachment). Thetouch panel 971 may include two portions of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to theprocessor 911, and receives and executes commands sent by theprocessor 911. In addition, thetouch panel 971 may be implemented by various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to thetouch panel 971, theuser input unit 970 may includeother input devices 972. In particular,other input devices 972 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

Further, thetouch panel 971 may be overlaid on thedisplay panel 961, and when thetouch panel 971 detects a touch operation on or near thetouch panel 971, the touch operation is transmitted to theprocessor 911 to determine the type of the touch event, and then theprocessor 911 provides a corresponding visual output on thedisplay panel 961 according to the type of the touch event. Although thetouch panel 971 and thedisplay panel 961 are shown in fig. 9 as two independent components to implement the input and output functions of the terminal, in some embodiments, thetouch panel 971 and thedisplay panel 961 may be integrated to implement the input and output functions of the terminal, and is not limited herein.

Theinterface unit 980 is an interface for connecting an external device to the terminal 90. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. Theinterface unit 980 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the terminal 90 or may be used to transmit data between the terminal 90 and external devices.

Memory 990 may be used to store software programs as well as various data. Thememory 990 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, thememory 990 may comprise high-speed random access memory and may also comprise non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

Theprocessor 911 is a control center of the terminal, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the terminal and processes data by operating or executing software programs and/or modules stored in thememory 990 and calling data stored in thememory 990, thereby integrally monitoring the terminal.Processor 911 may include one or more processing units; preferably, theprocessor 911 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into theprocessor 911.

The terminal 90 may further include a power supply 912 (e.g., a battery) for supplying power to various components, and preferably, thepower supply 912 may be logically connected to theprocessor 911 via a power management system, so as to manage charging, discharging, and power consumption via the power management system.

In addition, the terminal 90 includes some functional modules that are not shown, and are not described in detail herein.

Preferably, an embodiment of the present invention further provides a terminal, including aprocessor 911, amemory 990, and a computer program stored in thememory 990 and capable of running on theprocessor 911, where the computer program, when executed by theprocessor 911, implements each process of the scheduling method embodiment for a physical downlink shared channel applied to a terminal side, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again.

The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the embodiment of the scheduling method for a physical downlink shared channel applied to a terminal side, and can achieve the same technical effect, and is not described herein again to avoid repetition. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.

While the preferred embodiments of the present invention have been described, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the following claims.