A Quasi-Co-Location QCL Indication Method and a Communication Device
By establishing a quasi-co-address relationship in the new air interface system and flexibly configuring the QCL relationship between TRS and SSB, the problem of time-frequency deviation estimation performance and power consumption of non-connected terminal devices is solved, and efficient time-frequency synchronization and low-power terminal device operation is achieved.
Patent Information
- Application Number
- CN202110903827.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-08-06
- Publication Date
- 2025-07-11
- Estimated Expiration
- 2041-08-06
AI Technical Summary
In the new air interface system, when the terminal equipment in the non-connected state performs time-frequency deviation estimation, there are problems such as high power consumption and large system resource overhead, which is difficult to meet the requirements of time-frequency deviation estimation performance and low power consumption at the same time.
By establishing a quasi-co-address (QCL) relationship between terminal devices and network devices, flexibly configure or change the QCL relationship between TRS and SSB, including QCL-TypeA, QCL-TypeC, QCL-TypeD and other types, different associations between TRS and SSB are realized so that terminal devices can perform precise time synchronization in non-connected states, reduce dependence on SSB and reduce power consumption.
It improves the time-frequency deviation estimation performance of terminal equipment, reduces the power consumption of terminal equipment in non-connected state, and at the same time adapts to the air interface overhead of network equipment system, and optimizes system resource utilization.
Smart Images

Figure CN115706611B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technologies, and in particular, to a quasi-co-location (QCL) indication method and a communication device. Background Art
[0002] In a new radio (NR) system, a terminal device in the connected state can obtain a tracking reference signal (TRS) through dedicated radio resource control (RRC) signaling from a network device, and the TRS is used for the terminal device to perform fine time-frequency synchronization. A terminal device in the idle state or the inactive state cannot receive the TRS through RRC signaling and can only perform preliminary time-frequency offset synchronization, automatic gain control (AGC) estimation, and signal-to-interference ratio (SIR) estimation through a synchronization signal block (SSB). However, since the transmission period of the SSB and the discontinuous reception (DRX) period do not always match, there may be a large time deviation in the paging occasion (PO) in the paging frame of the DRX period during the transmission time of the SSB. Therefore, the terminal device needs to maintain a light sleep state to keep the parameters unchanged until the PO arrives, resulting in an increase in the power consumption of the terminal device. Moreover, since the transmission bandwidth of the SSB is smaller than that of the TRS, the time-frequency offset estimation performance of a terminal device in the idle state or the inactive state is poor, and the power consumption performance of using multiple SSBs for time-frequency estimation is poor. However, configuring a dedicated TRS for a terminal device in the idle state or the inactive state to improve the time-frequency offset estimation performance of the terminal device and reduce the power consumption will introduce a huge system resource overhead.
[0003] It can be seen that how to flexibly meet the requirement of low system resource overhead while ensuring the time-frequency offset estimation performance and low power consumption of a terminal device in the non-connected state is an urgent problem to be solved. Summary of the Invention
[0004] Embodiments of this application provide a quasi-co-location (QCL) indication method and a communication device. Through such a QCL indication method, when the relationship between the TRS and the SSB is QCL-TypeA, a terminal device in the non-connected state can perform precise time synchronization through the TRS, and when the relationship between the TRS and the SSB is QCL-TypeC, a terminal device in the non-connected state can perform relatively precise time synchronization through the TRS to save system power consumption.
[0005] In a first aspect, an embodiment of the present application provides a QCL indication method. In this method: a terminal device receives TRS configuration information from a network device, where the TRS configuration information is used to configure the TRS received by the terminal device in a non-connected state, and the TRS configuration information includes first indication information; wherein, the first indication information is used to indicate a first QCL relationship between the TRS and an SSB; or, the first indication information is used to indicate a second QCL relationship between a demodulation reference signal DMRS of a physical downlink control channel PDCCH and the TRS.
[0006] Based on the method described in the first aspect, the relationship between the SSB and the TRS can be flexibly configured or changed, so as to improve the time-frequency offset estimation performance of the terminal device while flexibly meeting the requirements of the network device system air interface overhead.
[0007] In a possible implementation, the first QCL relationship is QCL-TypeA or QCL-TypeC.
[0008] In a possible implementation, the first QCL relationship is QCL-TypeA and QCL-TypeD, or the first QCL relationship is QCL-TypeC and QCL-TypeD.
[0009] In a possible implementation, the terminal device receives second indication information from the network device, where the second indication information is used to indicate that the first QCL relationship changes to a third QCL relationship, and the first QCL relationship is different from the third QCL relationship; wherein, the third QCL relationship is QCL-TypeA or QCL-TypeC. By implementing this possible implementation, the network device can flexibly change the relationship between the SSB and the TRS according to the current system network air interface overhead condition, so as to improve the time-frequency offset estimation performance of the terminal device while taking into account the requirements of the network device system air interface overhead.
[0010] In a possible implementation, the terminal device receives second indication information from the network device, where the second indication information is used to indicate that the first QCL relationship changes to a third QCL relationship, and the first QCL relationship is different from the third QCL relationship; wherein, the third QCL relationship is QCL-TypeA and QCL-TypeD, or the third QCL relationship is QCL-TypeC and QCL-TypeD. By implementing this possible implementation, the network device can flexibly change the relationship between the SSB and the TRS according to the current system network air interface overhead condition, so as to improve the time-frequency offset estimation performance of the terminal device while taking into account the requirements of the network device system air interface overhead.
[0011] In a possible implementation, the second indication information is one of the following: system message, paging indication, or physical layer message.
[0012] In a possible implementation, the second QCL relationship is QCL-TypeA or QCL-TypeC.
[0013] In a possible implementation, the second QCL relationship is QCL-TypeA and QCL-TypeD, or the second QCL relationship is QCL-TypeC and QCL-TypeD.
[0014] In a possible implementation, the TRS configuration information is a system message or radio resource control (RRC) signaling.
[0015] In a second aspect, an embodiment of the present application provides a QCL indication method. In this method: a network device sends TRS configuration information to a terminal device, where the TRS configuration information is used to configure the TRS received by the terminal device in a non-connected state, and the TRS configuration information includes first indication information; wherein, the first indication information is used to indicate a first QCL relationship between the TRS and an SSB; or, the first indication information is used to indicate a second QCL relationship between a demodulation reference signal (DMRS) of a physical downlink control channel (PDCCH) and the TRS.
[0016] Based on the method described in the second aspect, the network device can flexibly configure or change the relationship between the SSB and the TRS, so as to improve the time-frequency offset estimation performance of the terminal device while flexibly meeting the requirements of the system air interface overhead of the network device.
[0017] In a possible implementation, the first QCL relationship is QCL-TypeA or QCL-TypeC.
[0018] In a possible implementation, the first QCL relationship is QCL-TypeA and QCL-TypeD, or the first QCL relationship is QCL-TypeC and QCL-TypeD.
[0019] In a possible implementation, the network device sends second indication information to the terminal device, where the second indication information is used to indicate that the first QCL relationship changes to a third QCL relationship, and the first QCL relationship is different from the third QCL relationship; wherein, the third QCL relationship is QCL-TypeA or QCL-TypeC.
[0020] In a possible implementation, the network device sends second indication information to the terminal device, where the second indication information is used to indicate that the first QCL relationship is changed to a third QCL relationship, and the first QCL relationship is different from the third QCL relationship; wherein, the third QCL relationship is QCL-TypeA and QCL-TypeD, or the third QCL relationship is QCL-TypeC and QCL-TypeD.
[0021] In a possible implementation, the second indication information is one of the following: system message, paging indication or physical layer message.
[0022] In a possible implementation, the second QCL relationship is QCL-TypeA or QCL-TypeC.
[0023] In a possible implementation, the second QCL relationship is QCL-TypeA and QCL-TypeD, or the second QCL relationship is QCL-TypeC and QCL-TypeD.
[0024] In a possible implementation, the TRS configuration information is a system message or radio resource control (RRC) signaling.
[0025] In a third aspect, an embodiment of the present application provides a communication device, which includes a transmission module and a processing module, where the processing module is used to process data, and the transmission module is used to receive TRS configuration information from a network device, and the TRS configuration information is used to configure the TRS received by the terminal device in the non-connected state, and the TRS configuration information includes first indication information; wherein, the first indication information is used to indicate a first QCL relationship between the TRS and the SSB; or the first indication information is used to indicate a second QCL relationship between the demodulation reference signal (DMRS) of the physical downlink control channel (PDCCH) and the TRS.
[0026] For the beneficial effects based on the third aspect, reference may be made to the method and beneficial effects described in the first aspect above, and repeated parts will not be elaborated.
[0027] In a possible implementation, the first QCL relationship is QCL-TypeA or QCL-TypeC.
[0028] In a possible implementation, the first QCL relationship is QCL-TypeA and QCL-TypeD, or the first QCL relationship is QCL-TypeC and QCL-TypeD.
[0029] In a possible implementation, the transmission module is further configured to receive second indication information from a network device, where the second indication information is used to indicate that the first QCL relationship is changed to a third QCL relationship, and the first QCL relationship is different from the third QCL relationship; wherein, the third QCL relationship is QCL-TypeA or QCL-TypeC.
[0030] In a possible implementation, the transmission module is further configured to receive second indication information from a network device, where the second indication information is used to indicate that the first QCL relationship is changed to a third QCL relationship, and the first QCL relationship is different from the third QCL relationship; wherein, the third QCL relationship is QCL-TypeA and QCL-TypeD, or the third QCL relationship is QCL-TypeC and QCL-TypeD.
[0031] In a possible implementation, the second indication information is one of the following: a system message, a paging indication, or a physical layer message.
[0032] In a possible implementation, the second QCL relationship is QCL-TypeA or QCL-TypeC.
[0033] In a possible implementation, the second QCL relationship is QCL-TypeA and QCL-TypeD, or the second QCL relationship is QCL-TypeC and QCL-TypeD.
[0034] In a possible implementation, the TRS configuration information is a system message or radio resource control (RRC) signaling.
[0035] In a fourth aspect, an embodiment of the present application provides a communication device, which includes a transmission module and a processing module. The processing module is configured to process data, and the transmission module is configured to send TRS configuration information to a terminal device. The TRS configuration information is used to configure the TRS received by the terminal device in a non-connected state. The TRS configuration information includes first indication information; wherein, the first indication information is used to indicate a first QCL relationship between the TRS and the SSB; or the first indication information is used to indicate a second QCL relationship between the demodulation reference signal (DMRS) of the physical downlink control channel (PDCCH) and the TRS. For the beneficial effects based on this fourth aspect, reference may be made to the method and beneficial effects described in the first aspect above, and repeated parts will not be elaborated.
[0036] In a possible implementation, the first QCL relationship is QCL-TypeA or QCL-TypeC.
[0037] In a possible implementation, the first QCL relationship is QCL-TypeA and QCL-TypeD, or the first QCL relationship is QCL-TypeC and QCL-TypeD.
[0038] In a possible implementation, the transmission module is further configured to send second indication information to the terminal device, where the second indication information is used to indicate that the first QCL relationship changes to a third QCL relationship, and the first QCL relationship is different from the third QCL relationship; where the third QCL relationship is QCL-TypeA or QCL-TypeC.
[0039] In a possible implementation, the transmission module is further configured to send second indication information to the terminal device, where the second indication information is used to indicate that the first QCL relationship changes to a third QCL relationship, and the first QCL relationship is different from the third QCL relationship; where the third QCL relationship is QCL-TypeA and QCL-TypeD, or the third QCL relationship is QCL-TypeC and QCL-TypeD.
[0040] In a possible implementation, the second indication information is one of the following: system message, paging indication, or physical layer message.
[0041] In a possible implementation, the second QCL relationship is QCL-TypeA or QCL-TypeC.
[0042] In a possible implementation, the second QCL relationship is QCL-TypeA and QCL-TypeD, or the second QCL relationship is QCL-TypeC and QCL-TypeD.
[0043] In a possible implementation, the TRS configuration information is a system message or radio resource control (RRC) signaling.
[0044] In a fifth aspect, the present application provides a communication device, which may be a device in a terminal device or a device that can be used in matching with the terminal device. Among them, the communication device may also be a chip system. The communication device can execute the method described in the first aspect. The functions of the communication device can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions. The unit may be software and / or hardware. The operations and beneficial effects performed by the communication device can refer to the method and beneficial effects described in the first aspect above, and repeated parts will not be elaborated.
[0045] In a sixth aspect, the present application provides a communication device, which may be a device in a network device or a device that can be used in combination with a network device. Among them, the communication device may also be a chip system. The communication device can execute the method described in the second aspect. The functions of the communication device can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units corresponding to the above functions. The unit can be software and / or hardware. For the operations and beneficial effects executed by the communication device, reference can be made to the method and beneficial effects described in the second aspect above, and repeated parts will not be elaborated.
[0046] In a seventh aspect, the present application provides a communication device, which may be the terminal device in the above method embodiments or a chip disposed in the terminal device. The communication device includes a communication interface and a processor. Optionally, it further includes a memory. Among them, the memory is used to store computer programs or instructions. The processor is coupled to the memory and the communication interface. When the processor executes the computer programs or instructions, the communication device executes the method executed by the terminal device in the above method embodiments.
[0047] In an eighth aspect, the present application provides a communication device, which may be the network device in the above method embodiments or a chip disposed in the network device. The communication device includes a communication interface and a processor. Optionally, it further includes a memory. Among them, the memory is used to store computer programs or instructions. The processor is coupled to the memory and the communication interface. When the processor executes the computer programs or instructions, the communication device executes the method executed by the network device in the above method embodiments.
[0048] In a ninth aspect, the present application provides a computer-readable storage medium, which is used to store computer-executable instructions. When the computer-executable instructions are executed, the method executed by the terminal device in the method described in the first aspect is implemented.
[0049] In a tenth aspect, the present application provides a computer-readable storage medium, which is used to store computer-executable instructions. When the computer-executable instructions are executed, the method executed by the network device in the method described in the second aspect is implemented.
[0050] In an eleventh aspect, the present application provides a computer program product including a computer program. When the computer program is executed, the method executed by the terminal device in the method described in the first aspect is implemented.
[0051] In a twelfth aspect, the present application provides a computer program product including a computer program. When the computer program is executed, the method executed by the network device in the method described in the second aspect is implemented.
[0052] In a thirteenth aspect, the present application provides a communication system, which includes the communication device described in the third aspect above and the communication device described in the fourth aspect above. Description of the Drawings
[0053] Figure 1 It is a schematic diagram of a system architecture provided by the present application;
[0054] Figure 2 It is a schematic diagram of a time-domain multiplexing pattern provided by the present application;
[0055] Figure 3 It is a schematic flow diagram of another time-domain multiplexing pattern provided by the present application;
[0056] Figure 4 It is a schematic diagram of the content carried by symbols corresponding to SSB provided by the present application;
[0057] Figure 5 It is a schematic diagram of a TCI-state provided by the present application;
[0058] Figure 6 It is a schematic diagram of a high-layer signaling QCL-info provided by the present application;
[0059] Figure 7 It is a schematic diagram of a MO period provided by the present application;
[0060] Figure 8 It is a schematic diagram of the corresponding relationship between PO and MO provided by the present application;
[0061] Figure 9 It is a schematic diagram of transmitting CSI-RS resources within a time slot provided by the present application;
[0062] Figure 10 It is a schematic diagram of an NZP-CSI-RS-ResourceSet configuration signaling provided by the present application;
[0063] Figure 11 It is a schematic diagram of a channel QCL relationship provided by the present application;
[0064] Figure 12 It is a schematic flow diagram of a QCL indication method provided by the present application;
[0065] Figure 13 It is a schematic diagram of another channel QCL relationship provided by the present application;
[0066] Figure 14 It is a schematic diagram of yet another channel QCL relationship provided by the present application;
[0067] Figure 15Schematic structural diagram of a communication device provided by this application;
[0068] Figure 16 Schematic structural diagram of another communication device provided by this application. Specific embodiments
[0069] The following further describes the specific embodiments of this application in detail with reference to the accompanying drawings.
[0070] The terms "first", "second", etc. in the description, claims, and drawings of this application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but optionally further includes steps or units not listed, or optionally further includes other steps or units inherent to these processes, methods, products, or devices.
[0071] Referring to "embodiments" herein means that the specific features, structures, or characteristics described in connection with the embodiments can be included in at least one embodiment of this application. The phrase does not necessarily refer to the same embodiment at every occurrence in the specification, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that the embodiments described herein can be combined with other embodiments.
[0072] In this application, "at least one (item)" means one or more, "a plurality" means two or more, "at least two (items)" means two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist. For example, "A and / or B" can mean: only A exists, only B exists, and both A and B exist simultaneously. Among them, A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one (one) of the following" or similar expressions refer to any combination of these items, including any combination of single item (one) or plural items (ones). For example, at least one (one) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.
[0073] To better understand the embodiments of this application, the following first introduces the system architecture involved in the embodiments of this application:
[0074] The method provided by the embodiments of this application can be applied to various communication systems. For example, it can be a machine-to-machine (M2M) communication system, an Internet of Things (IoT) system, a narrow band Internet of Things (NB-IoT) system, a Long Term Evolution (LTE) system, or a 5th-generation (5G) communication system. It can also be an LTE and 5G hybrid architecture, a 5G New Radio (NR) system, and new communication systems emerging in the future development of communication, etc.
[0075] Please refer to Figure 1 , Figure 1 which is a schematic diagram of a system architecture 10 provided by the embodiments of this application. As Figure 1 shown, the system architecture 10 includes a network device 101 and a terminal device 102, where the network device 101 and the terminal device 102 are communicatively connected. It should be noted that Figure 1 the numbers of the network device 101 and the terminal device 102 shown are only illustrative and should not be regarded as a limitation on the application scenarios of this application. The terminal device and the network device involved in this application will be introduced in detail below.
[0076] I. Terminal Device
[0077] The terminal device involved in the embodiments of the present application is an entity on the user side for receiving or transmitting signals. The terminal device can be a device that provides voice and / or data connectivity to users. For example, it can be a handheld device, a vehicle-mounted device, etc. with wireless connection capabilities. The terminal device can also be other processing devices connected to a wireless modem. The terminal device can communicate with a radio access network (RAN). The terminal device can also be referred to as a wireless terminal device, a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, an access point, a remote terminal, an access terminal, a user terminal, a user agent, a user device, or a user equipment (UE), etc. The terminal device can be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device. For example, it can be a portable, pocket-sized, handheld, computer-integrated, or vehicle-mounted mobile device that exchanges voice and / or data with a wireless access network. For example, the terminal device can also be a personal communication service (PCS) phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), etc. Common terminal devices include, for example: cars, drones, robotic arms, mobile phones, tablet computers, laptop computers, palmtop computers, mobile internet devices (MIDs), wearable devices, such as smart watches, smart bracelets, pedometers, etc., but the embodiments of the present application are not limited thereto.
[0078] II. Network Device
[0079] The network device (or access network device) involved in the embodiments of the present application is an entity on the network side for transmitting or receiving signals, which can be used to mutually convert the received air frames and Internet Protocol (IP) packets, and act as a router between the terminal device and the rest of the access network. The rest of the access network may include an IP network, etc. The access network device can also coordinate the attribute management of the air interface. For example, the access network device can be an evolved Node B (eNB or e-NodeB) in LTE, can also be a new radio controller (NR controller), can also be an ng-eNB, can also be a gNode B (gNB) in the 5G system, can also be a centralized unit, can also be a new radio base station, can also be a remote radio unit, can also be a micro base station, can also be a relay, can also be a distributed unit, can also be a transmission reception point (TRP) or a transmission point (TP), or any other radio access device, but the embodiments of the present application are not limited thereto.
[0080] To facilitate the understanding of the content of this solution, some terms in the embodiments of the present application are further explained below to facilitate the understanding of those skilled in the art.
[0081] 1. Idle state
[0082] The idle state refers to the state of the terminal device when it has completed cell residence but has not performed the random access process. The terminal device usually enters the idle state after power-on or after the release of radio resource control (RRC).
[0083] 2. Connected state
[0084] The connected state refers to the state of the terminal device when it has completed the random access process but has not performed RRC release. The terminal device can perform data transmission with the network device in the connected state. When the terminal device is in the idle state, after the terminal device completes the random access process, the state of the terminal device migrates to the connected state. When the terminal device is in the connected state, after completing the RRC release, the state of the terminal device migrates to the idle state.
[0085] 3. Inactive state
[0086] The inactive state is a state between the connected state and the idle state. For a terminal device in the inactive state, the user plane bearer on the air interface has been suspended, while the user plane bearer and the control plane bearer between the radio access network (RAN) and the core network (CN) are still maintained. When the terminal device initiates a call or a service request, it is necessary to activate the user plane bearer on the air interface and reuse the existing user plane bearer and control plane bearer between the RAN and the CN.
[0087] 4. Paging
[0088] Paging, also known as the paging message, is used for the network to trigger the terminal device to establish an RRC connection, or to notify the terminal device of system information update, and to send earthquake and tsunami alerts, etc. The content of the paging message is sent to the terminal device through the physical downlink shared channel (PDSCH), and the PDSCH is scheduled by the physical downlink control channel (PDCCH) scrambled by the paging radio network temporary identifier (P-RNTI).
[0089] The process for the terminal device to obtain the paging message is as follows: The terminal device in the non-connected state (including the idle state or the inactive state) wakes up periodically. After the terminal device wakes up, it monitors the PDCCH scrambled by the P-RNTI, and analyzes the DCI in the PDCCH to determine the location (such as the time-frequency location) information of the PDSCH. The terminal device receives the PDSCH according to the location information of the PDSCH, and the terminal device obtains the paging message in the PDSCH. The terminal device determines whether the paging message includes its own terminal device identifier. If so, the terminal device performs corresponding operations (for example, establishing an RRC connection; or returning from the inactive state to the idle state, etc.).
[0090] 5. Paging Frame (PF) and Paging Occasion (PO)
[0091] The specific time for the UE to receive paging is defined by the paging frame (PF) and the paging occasion (PO).
[0092] 5.1 Paging Frame (PF)
[0093] PF represents the radio frame for sending paging. That is, UEs in the IDLE and inactive states will only receive paging attempts in the PF. In the NR system, the length of a radio frame is 10 ms (milliseconds). A UE can determine whether a radio frame is a PF according to formula (1). When the SFN of the radio frame satisfies formula (1), the radio frame is considered a PF.
[0094] (SFN + PF_offset) mod T = (T div N) * (UE_ID mod N) (1)
[0095] Wherein, SFN is the system frame number of the current radio frame; PF_offset is the frame offset of the PF; T is the discontinuous reception (DRX) period, which is a time unit. It can be understood that a UE can have one attempt to receive paging within a time T. In the NR system, the DRX period can be 1280 ms, 2560 ms, etc.; N is the number of PFs included in each DRX period; UE_ID is the UE identifier, which can be the Fifth Generation System Architecture Evolution Temporary Mobile Station Identifier (5G-S-TMSI) mod 1024 or full I-RNTI.
[0096] 5.2 Paging occasion (PO)
[0097] PO represents the occasion for attempting to receive paging within a PF. For each PF, there can be multiple corresponding POs. NR uses the parameter Ns to represent the number of POs corresponding to a PF, and Ns can be any one of the values 1, 2, and 4. Each PO has an index number i_s, which is determined by formula (2):
[0098] i_s = floor(UE_ID / N) mod Ns (2)
[0099] It should be noted that the gNB does not send paging messages to the UE on every PO. The UE will detect Paging DCI on the PO to determine whether the gNB has sent paging.
[0100] 6. Beam
[0101] A beam is a spatial communication resource. A network device or a terminal device can shape a transmit beam in an analog, digital, or hybrid manner through an antenna array. Different beams are generally considered as resources in different spaces. Therefore, the same information can be transmitted through different beams to cover multiple different spatial regions, or different information can also be transmitted to maximize spatial resources. Beams can be classified into the transmit beams and receive beams of network devices, and the transmit beams and receive beams of terminal devices.
[0102] The synchronization signal block (SSB) in the NR network, also known as the synchronization signal / physical broadcast channel (SS / PBCH) block, is generally transmitted using the above-mentioned multiple beams. There is a transmission period for SSB. In the low frequency (or called Frequency Range 1 (FR1)), it is generally 20 ms. Within each SSB period, the gNB can transmit SSBs of multiple different beams in a time-division manner within a short time length. This short time length is called the SS burst. In the NR system, according to different working frequency bands, SSBs of different beams are multiplexed according to different time-domain patterns. When the subcarrier spacing of the SSB is 15 kHz, the SSB time location CaseA in the time-domain multiplexing pattern is as Figure 2 shown. For 15 kHz, the length of its SS burst is 2 ms, that is, the SSB can be transmitted within a time slot with a length of 1 ms. At most 4 SSBs in different directions can be transmitted within this SS burst (SSB0, SSB1, SSB2, and SSB3 in the above figure are the symbol positions where SSBs can be transmitted). It should be noted that the gNB does not necessarily need to transmit all 4 SSBs in different directions. The gNB can configure the actual number of SSBs to be transmitted and the symbol positions used for transmitting SSBs through system messages. For example, the gNB can only transmit SSB0 and SSB1, or only transmit SSB1 and SSB3.
[0103] When the subcarrier spacing of the SSB is 30 kHz, the time-domain multiplexing pattern it supports is as follows: SSB time location CaseB and CaseC. As Figure 3 shown, when the subcarrier spacing is 30 kHz, the length of an SS burst is 2 ms, including 4 time slots with a length of 0.5 ms. The gNB can transmit at most 8 SSBs in different directions within the SS burst, similar to 15 kHz. In Figure 3Among them, each color represents the SSB of a beam direction, which occupies 4 OFDM symbols in the time domain. The gNB can choose to transmit the SSB of 1, 2, 4, or 8 beams. The content carried in the 4 symbols of the SSB is as Figure 4 shown. The SSB bandwidth is 20 RBs, which contains 240 subcarriers. The first symbol is the PSS (Primary Synchronization Signal), which includes 127 subcarriers, that is, the PSS sequence length is 127, and the PSS only occupies the middle part of the SSB, and no other data or control information is transmitted on both sides. The second and fourth symbols are the Physical Broadcasting Channel (PBCH), which mainly carries system information. The third symbol carries both the PBCH and the Secondary Synchronization Signal (SSS) at the same time. The SSS sequence length is the same as that of the PSS, which is 127, and both occupy 127 REs in the middle of the SSB. The two of the SSS use 48 REs to send the PBCH respectively, and there are 8 and 9 REs intervals between the SSS and the PBCH.
[0104] When the UE powers on and camps on a cell or switches to a cell, it can measure multiple SSBs within an SSB period of the cell, determine the beam with the best reception quality, and use the beam quality of the measured SSB as a reference when performing beam selection in subsequent cell access and uplink / downlink data transmission.
[0105] 7. Quasi co-location (QCL)
[0106] QCL means that certain channel characteristics on two antenna ports are the same. When the UE receives a channel or signal sent by the gNB (assumed to be channel A), it needs to perform channel estimation on this channel A. Assuming that channel A and channel B are QCL, then certain channel characteristics of channel A and channel B are the same. If the UE has received channel B before receiving channel A, then the UE can directly use these channel characteristic parameters of channel B for channel estimation of channel A, thereby simplifying the channel estimation process and improving the channel estimation speed. The channel B estimated by the UE in advance can be called the QCL source (QCL source or source channel), and channel A depends on the QCL information of channel B, so it can be called the QCL target (QCL target or target channel). It should be noted that the channels referred to in the present invention can either refer to the physical layer channels defined in the communication system, such as PDCCH, PDSCH, PBCH, etc., or can refer to signals, signaling, or data transmitted in the physical communication channel, such as CSI-RS, SSB, DMRS of PDCCH, DMRS of PDSCH, etc., or other similar channels or signals, and the present invention does not make any constraints;
[0107] The channel characteristic parameters indicated by QCL can include the following contents:
[0108] a) Two parameters for providing Doppler estimation of the channel: Doppler Shift, which is used to characterize the frequency offset of the main path of the channel; Doppler Spread.
[0109] b) Two parameters for providing fine time synchronization of the channel: Average delay, which is used to characterize the delay of the main path of the channel; Delay spread.
[0110] c) A parameter for characterizing that two channels can be received using the same receiving beam: Spatial Rx parameter.
[0111] d) NR defines that there are 4 types of QCL relationship types between two channels, denoted as QCL-TypeA, TypeB, TypeC, TypeD. These 4 Types are specifically:
[0112] QCL-TypeA: Doppler Shift, Doppler Spread, Average delay, Delay spread;
[0113] QCL-TypeB: Doppler Shift, Doppler Spread;
[0114] QCL-TypeC: Average delay, Doppler Shift;
[0115] QCL-TypeD: Spatial Rx parameter;
[0116] Among them, QCL-TypeA includes both Doppler Shift, Doppler Spread, Average delay, and Delay spread, and is a QCL relationship with the strongest constraints. QCL-TypeA includes QCL-TypeB and QCL-TypeC. When two channels are of QCL-TypeA, these two channels are also of QCL-TypeB and QCL-TypeC; QCL-TypeA indicates that the QCL source channel can provide fine time-frequency synchronization for the QCL target channel.
[0117] QCL-TypeB only includes Doppler-related channel parameters and is therefore used to provide Doppler estimation from one channel to another.
[0118] QCL-TypeC only includes Average delay and Doppler Shift, and can only provide the Doppler shift and time delay of the main path of the channel. However, since it does not include Doppler Spread and Delay spread, it cannot provide the Doppler frequency offset and time delay of all paths in the channel. Therefore, when channel B and channel A are of QCL-TypeC, the QCL channel characteristics of channel B can only provide coarse time-frequency synchronization for channel A.
[0119] QCL-TypeD indicates that two channels can be received using the same receive beam and is mainly used for beam selection and beam indication in Frequency Range 2 (FR2).
[0120] In the NR system, the target channel is configured with a high-layer signaling - transmission configuration indicator (TCI-state) to indicate the source channel (or QCL source) of the target channel, and to indicate the corresponding QCL type between the target channel and the source channel (or QCL source). Specifically, the schematic diagram of TCI-state can be seen in Figure 5As shown, a TCI-state contains the following information: The tci-StateId field represents the identification ID of the current TCI-state; both the qcl-Type1 field and the qcl-Type2 field contain a high-layer signaling QCL-info, indicating that two QCL types can be configured for each channel. Among them, qcl-Type1 is a mandatory configuration and can be configured as QCL-TypeA, QCL-TypeB, or QCL-TypeC; qcl-Type2 is an optional configuration and can only be configured as QCL-TypeD, which is used in the FR2 high-frequency scenario to indicate whether two channels can receive using the same beam. Specifically, for the schematic diagram of the high-layer signaling QCL-info, please refer to Figure 6 as shown, where the cell field represents in which cell the QCL source channel or signal is located, the bwp-Id field is used to indicate the bandwidth part (BWP) where the QCL source channel or signal is located, the reference signal represents whether the QCL source channel or signal is a channel state indicator reference signal (CSI-RS) or an SSB, and the qcl-Type indicates the specific QCL-Type.
[0121] 8. Mapping relationship between SSB and PE, PO
[0122] For each PO in a PE, there are S monitoring occasions (MO) for paging PDCCH. MO represents the transmission time of the paging PDCCH. Specifically, MO generally appears periodically. Therefore, it can be represented by the occurrence period (in time slot units), the time offset in each period, and the time length (in symbol units). MO configures the period, time offset, and time length through the search space set of the PDCCH, as Figure 7 shown. The MO period defined by this search space set is 2 slots, and the time offset in the period is 1 slot (i.e., MO only appears on odd time slot numbers, for example Figure 5 as shown, the MO appears at the time slot numbers of slot1 and slot3). In each time slot, MO occupies two symbols, and these two symbols are the first two symbols of a time slot (such as Figure 5 the first two symbols of slot1 and the first two symbols of slot3 in ). The UE can know whether there is a paging PDCCH transmission by monitoring these symbols.
[0123] The number of MOs included in a PO is the same as the number of SSBs configured in the cell, and each SSB corresponds to one MO in the PO. That is, for each SSB and the corresponding MO in the PO, the paging PDCCH DMRS (demodulation reference signal) transmitted is QCL-TypeA and QCL-TypeD (QCL-TypeD is only used in the FR2 scenario). That is, the beam of the Paging PDCCH transmitted in this MO is the same as the corresponding SSB, and the UE can receive and measure the SSB to provide fine time-frequency synchronization for the corresponding paging PDCCH. Since the content of the Paging PDCCH transmitted on different MOs is the same. Therefore, the UE can select the MO with the best reception performance to receive the Paging PDCCH according to the beam measurement result of the SSB, and can directly use some channel estimation parameters of the SSB according to the QCL relationship when receiving the Paging PDCCH.
[0124] As Figure 8 shown, the cell is configured with 2 SSBs (such as Figure 8 SSB1 and SSB2 in Figure 8 ) and 4 POs (i.e., Figure 8 PO1 - PO4 in Figure 8 ). Therefore, there are two MOs in each PO that can transmit paging PDCCH, and SSB1 and SSB2 correspond to MO1 and MO2 in each PO respectively.
[0125] If the UE detects a paging PDCCH on the MO of a PO and this paging PDCCH schedules paging PDSCH data, then the DMRS of the paging PDCCH on this MO and the DMRS of the paging PDSCH it schedules are also QCL-TypeA and QCL-TypeD (QCL-TypeD is only used in the FR2 scenario).
[0126] 9. UE Wake-up Partial Workflow
[0127] Before the UE in the non-connected state (including the IDLE state and the inactive state) wakes up and attempts to receive Paging, to ensure the reception performance, it is necessary to first adjust some parameters of the receiver. The adjustment mainly includes the following steps:
[0128] 9.1 Time Frequency Tracking
[0129] Time-frequency tracking is also called time-frequency synchronization. Its main purpose is that due to the limitation of manufacturing cost, the frequency crystal used by UE is not very accurate. This will cause the time and working frequency of the UE to deviate from the clock and frequency of the network after it is powered on for a period of time. Therefore, the base station needs to send a specific reference signal for the UE to estimate the timing deviation, frequency domain deviation, delay spread and Doppler spread between itself and the base station, and compensate for its own time-frequency deviation. In the IDLE state, the UE generally performs preliminary time-frequency tracking by receiving SSB.
[0130] Due to the different capabilities of each UE and the different signal-to-noise ratios of each UE's location, the number of SS Bursts required for time-frequency tracking by each UE will be different. Generally, the UE needs to use one to three SS Bursts for time-frequency tracking. For UEs with strong capabilities or UEs with good channel conditions in the center of the cell, only one SS burst needs to be received to correct the time-frequency offset, so that the residual time-frequency offset will not affect the UE's reception of paging PDCCH and PDSCH. For UEs with poor capabilities or UEs with poor channel conditions at the edge of the cell, it is generally necessary to receive three SS bursts to correct the time-frequency offset, so that the residual frequency offset will not affect the UE's reception of paging PDCCH and PDSCH.
[0131] 9.2 Automatic gain control (AGC)
[0132] The main purpose is to adjust the signal input and output power of the baseband and RF circuits according to the power of the received signal; in the IDLE state, the UE generally also performs AGC estimation by receiving SSB.
[0133] 9.3 Beam Measurement
[0134] Since SSB sends multiple beams, the UE needs to measure each SSB and select the paging PDCCH and PDSCH corresponding to the last SSB with the best reception quality to receive. The reference signals of SSB and the corresponding paging PDCCH and PDSCH have the relationship of QCL-TypeA and QCL-TypeD.
[0135] It should be noted that, in addition to the above operations, the UE may also need to perform operations such as SIR estimation and mobility measurement.
[0136] 10. Tracking Reference Signal (TRS)
[0137] 3GPP defines a channel state information reference signal for tracking (CSI-RS for tracking), also known as tracking RS (TRS), for the UE to perform fine time-frequency offset estimation.
[0138] The TRS of NR is a specialized CSI-RS, which is configured through a non-zero power channel state information reference signal resource set (NZP CSI-RS Resource set). Each CSI-RS Resource Set contains two or four CSI-RS resources. Each CSI-RS resource represents a resource element transmitted on a symbol with a certain frequency-domain density and bandwidth. The symbol positions of each CSI-RS resource transmitted are different, but their transmission bandwidths, densities, and frequency-domain positions are the same. As Figure 9 shown, in the low frequency (e.g., within the FR1 frequency band range), each CSI-RS ResourceSet contains four CSI-RS resources, and these four CSI-RS resources are transmitted with a 3-symbol interval in the middle of each of the two adjacent Slots (such as Figure 9 the slot1 and slot2 corresponding to the FR1 frequency band shown); in the high frequency (e.g., within the FR2 frequency band range), each CSI-RSResource Set contains two CSI-RS resources, and these two CSI-RS resources are transmitted with a 3-symbol interval in a slot (such as Figure 9 the slot1 corresponding to the FR2 frequency band shown). It can be seen that the symbol positions of each CSI-RS resource transmitted in the slot are different, but their transmission bandwidths, densities, and frequency-domain positions are the same.
[0139] There are two ways to transmit the TRS. One is periodic transmission: each CSI-RS Resource set (occupying two or four symbols) represents a TRS burst in a transmission cycle, and there is only one burst in a cycle. The other is aperiodic transmission, and the aperiodic TRS must be triggered by an uplink scheduling DCI for transmission.
[0140] According to the foregoing Figure 6 The NZP-CSI-RS-ResourceSet configuration signaling corresponding to the TRS resource set indicated by the referenceSignal (reference signal) field in Figure 10As shown, when it is used for TRS, the trs-info indication therein is configured to be true, and the nzp-CSI-RS-Resources is configured to be 2 or 4.
[0141] In addition to time-frequency tracking, TRS can also be used by the UE for functions such as AGC (Automatic Gain Control) and SIR estimation (Signal to Interference Ratio).
[0142] It should be noted that TRS is mainly used for fine time-frequency synchronization in the connected state. The gNB configures multiple TRS resource sets for the UE, and each TRS resource set has a QCL-typeC relationship with an SSB, that is, the UE can first perform coarse time-frequency synchronization based on the SSB, and then receive the TRS using the channel parameters provided by the coarse time-frequency synchronization to obtain the TRS channel information. The PDCCH and PDSCH received by the UE in the connected state are both QCL-TypeA to the TRS, so the TRS can provide fine time-frequency synchronization information for the PDCCH and PDSCH.
[0143] Generally in the NR system, such as Figure 11As shown, the terminal device enters the cell of the service of the network device (or it can be understood that the terminal device camps in this cell), obtains the SSB sent by the network device, and performs rough time-frequency synchronization based on this SSB; further, the terminal device completes the random access process and enters the connected state, and performs channel estimation on the TRS according to the QCL-TypeC relationship between the TRS (referred to as connected TRS in the present invention) and the SSB and the channel information of this SSB, and receives this connected TRS. Further, since there is a QCL-TypeA relationship between the connected TRS and the DMRS of the PDSCH (or the DMRS of the PDCCH), the terminal device performs precise time-frequency synchronization based on this connected TRS, and receives the data transmitted by the network device in the PDSCH (or receives the data transmitted by the network device in the PDCCH). For a terminal device in the disconnected state, due to the lack of TRS resource configuration, it can only perform preliminary time offset synchronization, AGC estimation, and SIR estimation through the SSB. Since the transmission bandwidth of the SSB is smaller than that of the TRS, the performance of the disconnected terminal device for time-frequency offset estimation through the SSB is worse than that of the connected terminal device for time-frequency offset estimation through the TRS. Therefore, the UE needs to receive SSBs in multiple periods, and the UE startup time is longer and the power consumption is higher. In order to save the power consumption of the UE in the disconnected state, it is desired that the terminal device in the disconnected state can also receive the TRS and perform time-frequency offset estimation based on this TRS, thereby reducing the number of SSBs that the UE needs to receive, or enabling the UE to quickly complete time-frequency offset estimation without receiving the SSB, so as to reduce the startup time of the UE in the disconnected state and save the power consumption of the UE.
[0144] However, configuring dedicated TRS resources for the terminal device in the disconnected state will introduce a huge system resource overhead, which will increase the system load when the system resources are tense. However, if the terminal device performs time-frequency offset estimation through the SSB, it will result in higher power consumption. It can be seen that how to improve the time-frequency offset estimation performance of the terminal device in the disconnected state while meeting the low-power requirements of the system is an urgent problem to be solved.
[0145] In this application, the QCL relationship between the TRS and the SSB is configurable and can be changed. By indicating the QCL relationship between the TR and the SSB, the resource location for transmitting this TRS can be flexibly indicated (whether to configure dedicated TRS resources additionally or reuse the resources of the connected TRS), which can improve the time-frequency offset estimation performance of the terminal device and meet the low-power requirements of the system.
[0146] The following further introduces the quasi-co-location QCL indication method and communication device provided by this application in conjunction with the accompanying drawings:
[0147] Please refer to Figure 12 , Figure 12It is a schematic flowchart of a QCL indication method provided by an embodiment of the present application. As Figure 12 shown, the execution subject of this QCL indication method can be a terminal device or a chip in the terminal device, or the execution subject can be a network device or a chip in the network device. Figure 12 Taking the terminal device and the network device as the execution subjects as an example for illustration. Among them:
[0148] 1201. The terminal device receives TRS configuration information from the network device. This TRS configuration information is used to configure the TRS received by the terminal device in the non-connected state. The TRS configuration information includes first indication information. Among them, the first indication information is used to indicate the first QCL relationship between the TRS and the SSB; or, the relationship between the TRS and the SSB is a QCL-TypeC relationship, and the first indication information is used to indicate the second QCL relationship between the demodulation reference signals (DMRS) of the PDCCH and the TRS. It should be understood that it can also be understood that the first indication information is used to indicate the second QCL relationship between the DMRS of the PDSCH and the TRS.
[0149] In other words, the network device sends TRS configuration information to the terminal device, and the TRS configuration information includes first indication information. In a possible implementation, the TRS configuration information includes a system message or a radio resource control (RRC) signaling, that is, the network device can send the TRS configuration information to the terminal device through a system message or a high-layer signaling. For example, in one example, when the terminal device is in the non-connected state, the network device cannot send the TRS configuration information to the terminal device through the RRC control signaling. The network device can add the TRS configuration information to a system message (such as a system information block (SIB)) in a broadcast form and send it to the terminal device through the system message. In another example, when the terminal device is in the connected state, the network device sends the TRS configuration information to the terminal device through a high-layer signaling (such as an RRC signaling), and the TRS configuration information is used to indicate how the terminal device receives the TRS in the non-connected state.
[0150] In a possible implementation, the TRS configuration information further includes TRS resource set configuration information (for example, all or part of the configuration information in the foregoing NZP-CSI-RS-Resource Set configuration information). The TRS resource set configuration information is used to configure a TRS resource set, and the TRS resource set is used for a network device to send a TRS or for a terminal device to receive a TRS. For example, the TRS resource set includes one or more of the following items: the transmission period of the network device to send a TRS, the period offset, the transmission frequency or bandwidth, the TRS transmission pattern in each time slot (the symbol position, bandwidth, density, and frequency domain position of the TRS in the time slot), etc. It should be noted that the TRS received by a non-connected state terminal device in this application is also referred to as an auxiliary TRS.
[0151] It should be stated that this application does not specifically limit whether the TRS configuration information includes both TRS resource set configuration information and the first indication information at the same time. It can be understood that in another possible implementation, after receiving the TRS resource set configuration information, the terminal device can further receive the TRS configuration information including the first indication information. Or, in yet another possible implementation, the terminal device can receive the TRS resource set configuration information and the first indication information sent by the network device respectively through different system messages or high-layer signaling. For example, in one example, the terminal device can receive the TRS resource set configuration information sent by the network device through a first system message (or a first RRC signaling), and receive the first indication information sent by the network device through a second system message (or a second RRC signaling); or, in another example, the terminal device can also receive the TRS resource set configuration information sent by the network device through an RRC signaling, and receive the first indication information sent by the network device through a system message; or, in yet another example, the terminal device receives the TRS resource set configuration information sent by the network device through a system message, and receives the first indication information sent by the network device through an RRC signaling.
[0152] Next, based on the content indicated by the foregoing first indication information, two cases will be described.
[0153] Case 1: The first indication information is used to indicate a first QCL relationship between the TRS and the synchronization signal block SSB.
[0154] Among them, in a possible implementation (for example, when the terminal device is in FR1), the first QCL relationship is QCL-TypeA or QCL-TypeC. In this possible implementation, Figure 5 in the shown TCI-state, the mandatory configuration field qcl-Type1 can be configured as QCL-TypeA or QCL-TypeC, and the optional qcl-Type2 field is not configured.
[0155] In another possible implementation (for example, when the terminal device is in FR2), the first QCL relationship is QCL-TypeA and QCL-TypeD, or the first QCL relationship is QCL-TypeC and QCL-TypeD. In this possible implementation, Figure 5 In the TCI-state shown, the mandatory configuration field qcl-Type1 can be configured as QCL-TypeA or QCL-TypeC; the optional qcl-Type2 field is configured as QCL-TypeD.
[0156] It should be noted that in this case, the auxiliary TRS received by the non-connected terminal device can be the transmission resource multiplexing the connected-state TRS, or the transmission resource of the auxiliary TRS configured additionally (except for the connected-state TRS transmission resource) by the network device. When the auxiliary TRS is the transmission resource multiplexing the connected-state TRS, there is no need for the network device to specifically configure TRS resources for the non-connected terminal device additionally, thus not increasing the system air interface resource overhead. At this time, the channel corresponding to the auxiliary TRS and the channel of the SSB are in a QCL-TypeC relationship. When the auxiliary TRS is transmitted through the transmission resource of the auxiliary TRS configured additionally by the network device, the network needs to configure resources for specifically transmitting the auxiliary TRS for the non-connected terminal device additionally, resulting in a certain resource overhead. At this time, the channel between the auxiliary TRS and the SSB is in a QCL-TypeA relationship.
[0157] It can be understood that when the QCL relationship between the auxiliary TRS and the SSB is QCL-TypeC, the auxiliary TRS received by the non-connected terminal device is transmitted by multiplexing the transmission resource of the connected-state TRS; when the QCL relationship between the TRS and the SSB is QCL-TypeA, the auxiliary TRS received by the non-connected terminal device can be transmitted through other transmission resources except for the transmission resource of the connected-state TRS, for example, transmitted through the dedicated transmission resource configured additionally by the network device for the auxiliary TRS. It can be seen that the network device can indicate the type of the QCL relationship between the TRS received by the non-connected terminal device and the SSB, and then indicate the transmission resource of the TRS received when the terminal device is in the non-connected state.
[0158] For this case, please refer to Figure 13 shown in Figure 13 is the schematic diagram of the channel QCL relationship in this case. Among them, Figure 13 13a is the schematic diagram of the QCL relationship when the non-connected terminal device multiplexes the connected-state TRS transmission resource to receive the auxiliary TRS, and the QCL relationship between the auxiliary TRS and the SSB is QCL-TypeC; or, Figure 1313a is a schematic diagram of the QCL relationship of the channel when a non-connected terminal device multiplexes a connected TRS transmission resource to receive an auxiliary TRS, and the channel between the auxiliary TRS and the SSB is QCL-TypeC and QCL-TypeD.
[0159] The following is a schematic explanation of the case where the auxiliary TRS and SSB are connected to QCL-Type C. The same logic can be used when the auxiliary TRS and SSB are connected to QCL-Type C and QCL-Type D.
[0160] In one case (for example, when the terminal device is in FR1), Figure 13 In 13a, the terminal device receives the auxiliary TRS through the connected TRS transmission resource, and the QCL relationship between the auxiliary TRS and the SSB is a QCL-TypeC relationship. That is, the TRS resource set configuration information in the TRS configuration information is the TRS resource set configuration information of the connected terminal device. Since there is a QCL-TypeA relationship between the SSB and the DMRS of the Paging PDCCH (and / or Paging PDSCH), at this time, the auxiliary TRS and the SSB have a QCL-TypeC relationship, it can be inferred that the QCL relationship between the auxiliary TRS and the DMRS of the Paging PDCCH (and / or Paging PDSCH) is a QCL-TypeC relationship. Furthermore, since the auxiliary TRS is generally sent before the Paging PDCCH (and / or Paging PDSCH), the terminal device can use the auxiliary TRS to assist the SSB in coarse time-frequency synchronization, reduce the number of SSBs that need to be received, and save power consumption. Through this method, the terminal device can receive the auxiliary TRS by reusing the connected TRS transmission resources. There is no need for the network device to specially configure TRS resources for the non-connected terminal device, no increase in air interface resource overhead, and the power consumption overhead will be better than using SSB alone for time and frequency synchronization.
[0161] exist Figure 13 13b is a schematic diagram of the QCL relationship when a non-connected terminal device receives an auxiliary TRS through an auxiliary TRS dedicated transmission resource, and the auxiliary TRS and SSB are QCL-Type A; or, Figure 13 13b is a schematic diagram of the QCL relationship of the channel when the auxiliary TRS and SSB are QCL-TypeA and QCL-TypeD when the non-connected terminal device receives the auxiliary TRS through the auxiliary TRS dedicated transmission resource.
[0162] The following uses the schematic diagram of the QCL relationship when the auxiliary TRS and the SSB are of QCL-TypeA for illustrative explanation. The schematic diagram of the QCL relationship of the channel when the auxiliary TRS and the SSB are of QCL-TypeA and QCL-TypeD can be similarly deduced.
[0163] In one case (for example, when the terminal device is in FR1), in Figure 13 the 13b of, the terminal device receives the TRS (or referred to as the auxiliary TRS) through the auxiliary TRS transmission resources configured by the network device. That is, the terminal device receives the TRS configuration information from the network device through system messages or high-layer signaling. The TRS configuration information is used to configure the QCL relationship between the TRS and the SSB as a QCL-TypeA relationship. That is, when the terminal device is in the non-connected state, the terminal device receives the auxiliary TRS according to the TRS resource set configuration information in the TRS configuration information, and performs time-frequency synchronization on the DMRS of the Paging PDCCH (and / or Paging PDSCH) based on the auxiliary TRS. By such a method, since there is a QCL-TypeA relationship between the SSB and the DMRS of the Paging PDCCH (and / or Paging PDSCH), when the auxiliary TRS and the SSB are of QCL-TypeA relationship, it can be deduced that the QCL relationship between the auxiliary TRS and the DMRS of the Paging PDCCH (and / or Paging PDSCH) is a QCL-TypeA relationship. Further, the terminal device can perform channel estimation on the DMRS of the Paging PDCCH (and / or Paging PDSCH) according to the auxiliary TRS, that is, perform accurate time-frequency synchronization.
[0164] In a possible implementation in this case, the terminal device receives second indication information from the network device. The second indication information is used to indicate that the first QCL relationship is changed to a third QCL relationship, and the third QCL relationship is different from the first QCL relationship.
[0165] In a possible implementation, the third QCL relationship is QCL-TypeA or QCL-TypeC. In other words, in this case (for example, when the terminal device is in FR1), if the first QCL relationship is QCL-TypeA, then the third QCL relationship is QCL-TypeC; if the first QCL relationship is QCL-TypeC, then the third QCL relationship is QCL-TypeA. In another possible implementation, the third QCL relationship is QCL-TypeA and QCL-TypeD, or the third QCL relationship is QCL-TypeC and QCL-TypeD. In other words, in this case (for example, when the terminal device is in FR2), if the first QCL relationship is QCL-TypeC and QCL-TypeD, then the third QCL relationship is QCL-TypeA and QCL-TypeD; if the first QCL relationship is QCL-TypeA and QCL-TypeD, then the third QCL relationship is QCL-TypeC and QCL-TypeD.
[0166] Wherein, the second indication information includes but is not limited to one of the following forms: system message, paging indication (including paging PDCCH indication or paging PDSCH indication), physical layer message (such as paging early indication (PEI)) or other RRC signaling. In other words, the network device sends the second indication information to the terminal device to indicate the change in the relationship between the SSB and the TRS.
[0167] In a scenario, when the relationship between the SSB and the TRS is QCL-TypeA, the terminal device has the best performance in time-frequency offset estimation, the shortest UE time-frequency offset estimation time, and the lowest power consumption overhead, but the system air interface overhead is relatively large; when the relationship between the SSB and the TRS is QCL-TypeC, the terminal device has relatively poor performance in time-frequency offset estimation, but the power consumption overhead of this time-frequency offset estimation is lower than the power consumption overhead of the terminal device performing time-frequency offset estimation only based on the SSB, that is, the system air interface power consumption overhead is relatively small at this time. Therefore, the network device can flexibly change the relationship between the SSB and the TRS according to the current system network air interface overhead situation, taking into account the needs of the system air interface overhead of the network device while reducing the overhead of the terminal device.
[0168] For example, in an example of a possible scenario (e.g., when the terminal device is in the FR1 scenario), the first QCL relationship is the QCL-TypeA relationship. When the network device detects that the system air interface overhead is large and it is necessary to save the system air interface overhead at a certain moment, the network device may send second indication information to the terminal device. The second indication information is used to indicate that the relationship between the SSB and the TRS is changed from the QCL-TypeA relationship (i.e., the first QCL relationship) to the QCL-TypeC relationship (i.e., the third QCL relationship) to save the system air interface overhead. In another example of this scenario, the first QCL relationship is the QCL-TypeC relationship. When the network device detects that the system air interface overhead is very small and there is no need to save the system air interface overhead at a certain moment, the network device may send second indication information to the terminal device. The second indication information is used to indicate that the relationship between the SSB and the TRS is changed from the QCL-TypeC relationship (i.e., the first QCL relationship) to the QCL-TypeA relationship (i.e., the third QCL relationship) to improve the time-frequency synchronization performance of the terminal device.
[0169] For another example, in an example of another possible scenario (e.g., when the terminal device is in the FR2 scenario), the first QCL relationship is the QCL-TypeA relationship and the QCL-TypeD relationship. When the network device detects that the system air interface overhead is large and it is necessary to save the system air interface overhead at a certain moment, the network device may send second indication information to the terminal device. The second indication information is used to indicate that the relationship between the SSB and the TRS is changed from the QCL-TypeA relationship and the QCL-TypeD relationship (i.e., the first QCL relationship) to the QCL-TypeC relationship and the QCL-TypeD relationship (i.e., the third QCL relationship) to save the system air interface overhead. In another example of this scenario, the first QCL relationship is the QCL-TypeC relationship and the QCL-TypeD relationship. When the network device detects that the system air interface overhead is very small and there is no need to save the system air interface overhead at a certain moment, the network device may send second indication information to the terminal device. The second indication information is used to indicate that the relationship between the SSB and the TRS is changed from the QCL-TypeC relationship and the QCL-TypeD relationship (i.e., the first QCL relationship) to the QCL-TypeA relationship and the QCL-TypeD relationship (i.e., the third QCL relationship) to improve the time-frequency synchronization performance of the terminal device.
[0170] Case 2: The first indication information is used to indicate the second QCL relationship between the DMRS of the PDCCH (or called Paging PDCCH) and the TRS. It can also be understood that the first indication information is used to indicate the second QCL relationship between the DMRS of the PDSCH (or called Paging PDSCH) and the TRS. In this case, the relationship between the TRS and the SSB is the QCL-TypeC relationship.
[0171] In a possible implementation, the second QCL relationship is QCL-TypeA or QCL-TypeC. In this case (for example, when the terminal device is in FR1), the second QCL relationship is QCL-TypeA or QCL-TypeC (it can also be understood that the second QCL relationship is not QCL-TypeA);
[0172] In another possible implementation, the second QCL relationship is QCL-TypeA and QCL-TypeD, or the second QCL relationship is QCL-TypeC and QCL-TypeD. In this case (for example, when the terminal device is in FR2), the second QCL relationship is QCL-TypeA and QCL-TypeD, or the second QCL relationship is QCL-TypeC and QCL-TypeD (it can also be understood that the second QCL relationship is not QCL-TypeA and QCL-TypeD).
[0173] In other words, in this case, the terminal device can receive the TRS configuration information sent by the network device through system messages or high-layer signaling. The TRS configuration information includes first indication information, which is used to indicate the QCL relationship between the DMRS of Paging PDCCH (and / or Paging PDSCH) and the TRS.
[0174] Specifically, please refer to Figure 14 as shown Figure 14 This is the schematic diagram of the channel QCL relationship in this case. Among them, Figure 14 14a in is the schematic diagram of the QCL relationship where the first indication information indicates that the QCL relationship between the DMRS of Paging PDCCH (and / or Paging PDSCH) and the TRS is a QCL-TypeA relationship; or, Figure 14 14a in is the schematic diagram of the QCL relationship where the first indication information indicates that the QCL relationship between the DMRS of Paging PDCCH (and / or Paging PDSCH) and the TRS is a QCL-TypeA and QCL-TypeD relationship.
[0175] The following is a schematic explanation using the schematic diagram of the QCL relationship where the QCL relationship between the DMRS of Paging PDCCH (and / or Paging PDSCH) and the TRS is a QCL-TypeA relationship. When the schematic diagram of the QCL relationship where the QCL relationship between the DMRS of Paging PDCCH (and / or Paging PDSCH) and the TRS is a QCL-TypeA and QCL-TypeD relationship can be deduced by the same reasoning.
[0176] In one case (for example, when the terminal device is in FR1), in Figure 14 14a, the first indication information is used to indicate that the QCL relationship between the DMRS of the Paging PDCCH (and / or Paging PDSCH) and the TRS is a QCL-TypeA relationship. For example, the first indication information is the information indicated by adding a QCLTypeA-Paging field in the TRS configuration information. When the QCLTypeA-Paging field is configured to True, the first indication information indicates that the QCL relationship between the DMRS of the Paging PDCCH (and / or Paging PDSCH) and the TRS is a QCL-TypeA relationship. In this case, when the terminal device is in the non-connected state, the terminal device can receive the auxiliary TRS according to the TRS resource set configuration information in the TRS configuration information, and perform time-frequency synchronization on the DMRS of the Paging PDCCH (and / or Paging PDSCH) based on the auxiliary TRS. By such a method, since the QCL relationship between the auxiliary TRS and the DMRS of the Paging PDCCH (and / or Paging PDSCH) is a QCL-TypeA relationship, the terminal device can perform channel estimation on the DMRS of the Paging PDCCH (and / or Paging PDSCH) according to the auxiliary TRS, that is, perform accurate time-frequency synchronization.
[0177] Figure 14 14b is a schematic diagram of the QCL relationship where the first indication information indicates that the QCL relationship between the DMRS of the Paging PDCCH (and / or Paging PDSCH) and the TRS is a QCL-TypeC relationship (that is, it can be understood as not a QCL-TypeA relationship); or, Figure 14 14b is a schematic diagram of the QCL relationship where the first indication information indicates that the QCL relationship between the DMRS of the Paging PDCCH (and / or Paging PDSCH) and the TRS is a QCL-TypeC and QCL-TypeD relationship (that is, it can be understood as not a QCL-TypeA and QCL-TypeD relationship).
[0178] The following is a schematic explanation taking the QCL relationship between the DMRS of the Paging PDCCH (and / or Paging PDSCH) and the TRS as a QCL-TypeC relationship. When the QCL relationship between the DMRS of the Paging PDCCH (and / or Paging PDSCH) and the TRS is a QCL-TypeC and QCL-TypeD relationship, it can be deduced by analogy.
[0179] In one case (for example, when the terminal device is in FR1), inFigure 14 In 14b, the first indication information is used to indicate that the QCL relationship between the DMRS of the Paging PDCCH (and / or Paging PDSCH) and the TRS is not a QCL-TypeA relationship (which can be understood as a QCL-TypeC relationship). For example, the first indication information is the information indicated by adding a QCLTypeA-Paging field in the TRS configuration information. When the QCLTypeA-Paging field is configured to False, the TRS configuration information indicates that the QCL relationship between the DMRS of the Paging PDCCH (and / or Paging PDSCH) and the TRS is not a QCL-TypeA relationship. In this case, when the terminal device is in the non-connected state, the terminal device can receive the auxiliary TRS according to the TRS resource set configuration information in the TRS configuration information (which is the same as the resource set configuration information of the TRS in the transmission connected state at this time), and perform time-frequency synchronization on the DMRS of the Paging PDCCH (and / or Paging PDSCH) based on the auxiliary TRS. By such a method, since the auxiliary TRS is received by multiplexing the transmission resources of the connected state TRS, the QCL relationship between the auxiliary TRS and the DMRS of the Paging PDCCH (and / or Paging PDSCH) is not a QCL-TypeA relationship (which can be understood as a QCL-TypeC relationship), that is, the terminal device uses the auxiliary TRS to achieve relatively fast coarse time-frequency synchronization; and since the auxiliary TRS at this time is transmitted by multiplexing the TRS transmission resources of the connected state TRS, the network device does not need to specifically configure a resource set for transmitting the auxiliary TRS for the non-connected state terminal device, without increasing the air interface resource overhead, and the power consumption of time-frequency synchronization through the TRS is lower than the case of time-frequency synchronization only based on the SSB.
[0180] It should be noted that for Scenario 2, since the QCL relationship between the SSB and the TRS is not directly indicated in the TRS configuration information, it is not necessary to modify the aforementioned TCI-state configuration information. In Scenario 1, since the QCL relationship between the SSB and the TRS is directly indicated in the TRS configuration information, it is necessary to modify the TCI-state configuration information in the TRS configuration information.
[0181] It can be seen that through this method, the relationship between the SSB and the TRS can be flexibly configured or changed, reducing the power consumption overhead of the terminal device and flexibly adapting to the requirements of the network device system for air interface overhead.
[0182] Please refer to Figure 15 , Figure 15 which shows a schematic structural diagram of a communication device 1500 according to an embodiment of the present application. Figure 15The communication device shown can be used to implement part or all of the functions of the terminal device in the embodiment corresponding to the above QCL indication method, or Figure 15 The communication device shown can be used to implement part or all of the functions of the network device in the embodiment corresponding to the above QCL indication method.
[0183] In one embodiment, Figure 15 The communication device shown can be used to implement the above Figure 12 Part or all of the functions of the terminal device in the described method embodiment. The device can be a terminal device, or a device in a terminal device, or a device that can be used in conjunction with a terminal device. The communication transposition can also be a chip system. Figure 15 The communication device shown may include a transmission module 1501. The communication device may also include a processing module 1502, which is used to perform data processing.
[0184] Transmission module 1501 is used to receive TRS configuration information from a network device, wherein the TRS configuration information is used to configure the TRS received by the terminal device when in a non-connected state, and the TRS configuration information includes first indication information; wherein the first indication information is used to indicate a first QCL relationship between the TRS and the SSB; or, the first indication information is used to indicate a second QCL relationship between the demodulation reference signal DMRS of the physical downlink control channel PDCCH and the TRS.
[0185] In a possible implementation, the first QCL relationship is QCL-TypeA or QCL-TypeC.
[0186] In a possible implementation, the first QCL relationship is QCL-TypeA and QCL-TypeD, or the first QCL relationship is QCL-TypeC and QCL-TypeD.
[0187] In one possible implementation, the transmission module 1501 is also used to receive second indication information from a network device, where the second indication information is used to indicate that the first QCL relationship is changed to a third QCL relationship, and the first QCL relationship is different from the third QCL relationship; wherein the third QCL relationship is QCL-TypeA or QCL-TypeC.
[0188] In one possible implementation, the transmission module 1501 is also used to receive second indication information from a network device, where the second indication information is used to indicate that the first QCL relationship is changed to a third QCL relationship, and the first QCL relationship is different from the third QCL relationship; wherein the third QCL relationship is QCL-TypeA and QCL-TypeD, or the third QCL relationship is QCL-TypeC and QCL-TypeD.
[0189] In a possible implementation, the second indication information is one of the following: system message, paging indication, or physical layer message.
[0190] In a possible implementation, the second QCL relationship is QCL-TypeA or QCL-TypeC.
[0191] In a possible implementation, the second QCL relationship is QCL-TypeA and QCL-TypeD, or the second QCL relationship is QCL-TypeC and QCL-TypeD.
[0192] In a possible implementation, the TRS configuration information is a system message or radio resource control (RRC) signaling.
[0193] For a more detailed description of the above-mentioned transmission module 1501 and processing module 1502, reference may be made to the relevant descriptions in the above method embodiments, which will not be elaborated here.
[0194] In another embodiment, Figure 15 the shown communication device can be used to implement some or all of the functions of the network device in the above-mentioned Figure 12 described method embodiments. The device can be a network device, a device in a network device, or a device that can be used in conjunction with a network device. Among them, the communication device can also be a chip system. Figure 15 The shown communication device may include a transmission module 1501. The communication device may also include a processing module 1502, which is used for data processing. Among them:
[0195] The transmission module 1501 is configured to send TRS configuration information to a terminal device, where the TRS configuration information is used to configure the TRS received by the terminal device in a non-connected state, and the TRS configuration information includes first indication information; where the first indication information is used to indicate the first QCL relationship between the TRS and the SSB; or the first indication information is used to indicate the second QCL relationship between the demodulation reference signal (DMRS) of the physical downlink control channel (PDCCH) and the TRS.
[0196] In a possible implementation, the first QCL relationship is QCL-TypeA or QCL-TypeC.
[0197] In a possible implementation, the first QCL relationship is QCL-TypeA and QCL-TypeD, or the first QCL relationship is QCL-TypeC and QCL-TypeD.
[0198] In a possible implementation, the transmission module 1501 is further configured to send second indication information to the terminal device, where the second indication information is used to indicate that the first QCL relationship is changed to a third QCL relationship, and the first QCL relationship is different from the third QCL relationship; wherein, the third QCL relationship is QCL-TypeA or QCL-TypeC.
[0199] In a possible implementation, the transmission module 1501 is further configured to send second indication information to the terminal device, where the second indication information is used to indicate that the first QCL relationship is changed to a third QCL relationship, and the first QCL relationship is different from the third QCL relationship; wherein, the third QCL relationship is QCL-TypeA and QCL-TypeD, or the third QCL relationship is QCL-TypeC and QCL-TypeD.
[0200] In a possible implementation, the second indication information is one of the following: a system message, a paging indication, or a physical layer message.
[0201] In a possible implementation, the second QCL relationship is QCL-TypeA or QCL-TypeC.
[0202] In a possible implementation, the second QCL relationship is QCL-TypeA and QCL-TypeD, or the second QCL relationship is QCL-TypeC and QCL-TypeD.
[0203] In a possible implementation, the TRS configuration information is a system message or radio resource control (RRC) signaling.
[0204] For a more detailed description of the above transmission module 1501 and processing module 1502, reference may be made to the relevant descriptions in the above method embodiments, which will not be elaborated herein.
[0205] Please refer to Figure 16 , Figure 16 FIG. is a schematic structural diagram of a communication device 1600 provided in the present application. The communication device 1600 includes a processor 1610 and an interface circuit 1620. The processor 1610 and the interface circuit 1620 are coupled to each other. It can be understood that the interface circuit 1620 may be a transceiver or an input / output interface. Optionally, the communication device 1600 may further include a memory 1630, which is configured to store instructions executed by the processor 1610, or input data required for the processor 1610 to run the instructions, or data generated after the processor 1610 runs the instructions.
[0206] When the communication device 1600 is used to implement the method in the foregoing method embodiments, the processor 1610 is used to execute the functions of the foregoing processing module 1502, and the interface circuit 1620 is used to execute the functions of the foregoing transmission module 1501.
[0207] When the foregoing communication device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the foregoing method embodiments. The terminal device chip receives information from other modules (such as a radio frequency module or an antenna) in the terminal device, and this information is sent by a network device to the terminal device; or, the terminal device chip sends information to other modules (such as a radio frequency module or an antenna) in the terminal device, and this information is sent by the terminal device to the network device.
[0208] When the foregoing communication device is a chip applied to a network device, the network device chip implements the functions of the network device in the foregoing method embodiments. The network device chip receives information from other modules (such as a radio frequency module or an antenna) in the network device, and this information is sent by a terminal device to the network device; or, the network device chip sends information to other modules (such as a radio frequency module or an antenna) in the network device, and this information is sent by the network device to the terminal device.
[0209] It can be understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.
[0210] The method steps in the embodiments of the present application can be implemented in a hardware manner or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory (RAM), flash memory, read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), register, hard disk, removable hard disk, CD-ROM, or any other form of storage medium well-known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC. Additionally, the ASIC can be located in an access network device or a terminal device. Of course, the processor and the storage medium can also exist as discrete components in the access network device or the terminal device.
[0211] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are executed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program or instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer-readable storage medium can be any available medium that the computer can access or a data storage device such as a server integrating one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a DVD; or it can be a semiconductor medium, such as a solid state disk (SSD).
[0212] In various embodiments of the present application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.
[0213] It should be understood that the various numerical numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The magnitudes of the serial numbers of the above processes do not mean the sequence of execution, and the execution sequence of each process should be determined according to its function and internal logic.
[0214] The embodiments of the present application further provide a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed, the methods executed by the terminal device in the above method embodiments are implemented.
[0215] The embodiments of the present application further provide a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed, the methods executed by the network device in the above method embodiments are implemented.
[0216] The embodiments of the present application further provide a computer program product, which includes a computer program. When the computer program is executed, the methods executed by the terminal device in the above method embodiments are implemented.
[0217] The embodiments of the present application further provide a computer program product, which includes a computer program. When the computer program is executed, the methods executed by the network device in the above method embodiments are implemented.
[0218] The embodiments of the present application further provide a communication system, which includes a terminal device or a network device. Among them, the terminal device is used to execute the methods executed by the terminal device in the above method embodiments. The network device is used to execute the methods executed by the network device in the above method embodiments.
[0219] It should be noted that for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described action sequence, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the present application.
[0220] The descriptions of the embodiments provided in the present application can be referred to each other. The descriptions of each embodiment have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments. For the convenience and conciseness of description, for example, the functions and steps executed by the various devices and equipment provided in the embodiments of the present application can refer to the relevant descriptions of the method embodiments of the present application. The method embodiments can also refer to, combine or quote each other among the device embodiments.
[0221] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements on some or all of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the various embodiments of the present application.
Claims
1. A method for indicating quasi-co-located QCL, characterized in that The method includes: The terminal device receives tracking reference signal (TRS) configuration information from a network device. The TRS configuration information is used to configure the TRS received by the terminal device in a non-connected state. The TRS configuration information includes first indication information. The first indication information is used to indicate a first quasi-co-location (QCL) relationship between the TRS and a synchronization signal block (SSB). The terminal device receives second indication information from the network device. The second indication information is used to indicate that the first QCL relationship is changed to a third QCL relationship, where the third QCL relationship is different from the first QCL relationship.
2. The method according to claim 1, wherein: The first QCL relationship is QCL-TypeA or QCL-TypeC.
3. The method according to claim 1, wherein: The first QCL relationship is QCL-TypeA and QCL-TypeD, or the first QCL relationship is QCL-TypeC and QCL-TypeD.
4. The method according to claim 1 or 2, characterized in that, The method further includes: The third QCL relationship is QCL-TypeA or QCL-TypeC.
5. The method according to claim 1 or 3, characterized in that, The method further includes: The third QCL relationship is QCL-TypeA and QCL-TypeD, or the third QCL relationship is QCL-TypeC and QCL-TypeD.
6. The method according to claim 1, characterized in that, The second indication information is one of the following: a system message, a paging indication, or a physical layer message.
7. The method according to claim 1, characterized in that The TRS configuration information is a system message or radio resource control (RRC) signaling.
8. A quasi-co-location QCL indication method, characterized in that, The method includes: The network device sends tracking reference signal (TRS) configuration information to a terminal device. The TRS configuration information is used to configure the TRS received by the terminal device in a non-connected state. The TRS configuration information includes first indication information. The first indication information is used to indicate a first quasi-co-location (QCL) relationship between the TRS and a synchronization signal block (SSB). The network device sends second indication information to the terminal device. The second indication information is used to indicate that the first QCL relationship is changed to a third QCL relationship, where the third QCL relationship is different from the first QCL relationship.
9. The method according to claim 8, wherein: The first QCL relationship is QCL-TypeA or QCL-TypeC.
10. The method according to claim 8, wherein: The first QCL relationship is QCL-TypeA and QCL-TypeD, or the first QCL relationship is QCL-TypeC and QCL-TypeD.
11. The method according to claim 8 or 9, characterized in that, The method further includes: The third QCL relationship is QCL-TypeA or QCL-TypeC.
12. The method according to claim 8 or 10, characterized in that, The method further includes: The third QCL relationship is QCL-TypeA and QCL-TypeD, or the third QCL relationship is QCL-TypeC and QCL-TypeD.
13. The method according to claim 8, wherein The second indication information is one of the following: a system message, a paging indication, or a physical layer message.
14. The method according to claim 8, wherein The TRS configuration information is system information or radio resource control (RRC) signaling.
15. A communication device, characterized in that, It includes a module for performing the method according to any one of claims 1-7; or, it includes a module for performing the method according to any one of claims 8-14.
16. A communication device, characterized in that, It includes a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or send signals from the processor to other communication devices outside the communication device. The processor uses logic circuits or executes code instructions to implement the method according to any one of claims 1-7 or 8-14.
17. A computer-readable storage medium, characterized in that, A computer program or instruction is stored in the storage medium. When the computer program or instruction is executed by the communication device, the method according to any one of claims 1-7 or 8-14 is implemented.
Citation Information
Patent Citations
User terminal and wireless communication method
CN112997421A
Information transmission method and device, communication equipment and storage medium
CN113170334A