Channel monitoring or receiving method, device and terminal
By establishing a quasi-co-address relationship between the DMRS antenna port and the target reference signal in the terminal, the problem of poor downlink channel reliability during RACH-less handover is solved, and the handover success rate is improved.
Patent Information
- Application Number
- CN202310547636.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-15
- Publication Date
- 2024-11-19
AI Technical Summary
During the long-term evolution (LTE) random access channel (RACH-less) transmission, the reliability of downlink control and data channels is poor, resulting in a low success rate of RACH-less handover.
By establishing a quasi-co-address (QCL) relationship between the antenna port of the demodulation reference signal DMRS and the target reference signal in the terminal, the transmission characteristics of the PDCCH and the PDSCH are determined based on the relationship, thereby improving the reliability of the downlink control and data channel.
Improve the success rate of RACH-less handover, and enhance the reliability of downlink control and data channel.
Smart Images

Figure CN118984498A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of communication technology, and specifically relates to a channel monitoring or receiving method, device and terminal. Background Art
[0002] In the RACH-less transmission process of Long Term Evolution (LTE), there is no need to consider the correlation between the beam of the uplink and downlink channels and the demodulation reference signal (DMRS) antenna port and the known signal. In the New Radio (NR), RACH-less Physical Uplink Shared Channel (PUSCH) transmission must be supported. Since there is no Random Access Channel (RACH) transmission in the target cell and the corresponding reference signal selection, the reliability of the downlink control and data channels is poor, resulting in a low success rate of RACH-less switching.
[0003] Therefore, how to improve the success rate of RACH-less handover is an urgent problem to be solved. Summary of the invention
[0004] The embodiments of the present application provide a channel monitoring or receiving method, device and terminal, which can solve the problem of improving the success rate of RACH-less switching.
[0005] In a first aspect, a channel monitoring or receiving method is provided, which is performed by a terminal, and the method includes:
[0006] During the RACH-less switching of the terminal, the terminal monitors or receives the first channel based on the target reference signal; the antenna port of the demodulation reference signal DMRS of the first channel and the target reference signal are in a quasi-co-location QCL relationship;
[0007] Wherein, the first channel includes at least one of the following:
[0008] RACH-less physical downlink control channel PDCCH;
[0009] RACH-less Physical Downlink Shared Channel PDSCH.
[0010] In a second aspect, a channel monitoring or receiving device is provided, including:
[0011] A monitoring or receiving module, configured to monitor or receive a first channel based on a target reference signal during a RACH-less switching process of a terminal; an antenna port of a demodulation reference signal DMRS of the first channel and the target reference signal are in a quasi-co-location QCL relationship;
[0012] Wherein, the first channel includes at least one of the following:
[0013] RACH-less physical downlink control channel PDCCH;
[0014] RACH-less Physical Downlink Shared Channel PDSCH.
[0015] In a third aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.
[0016] In a fourth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is used to monitor a first channel based on a target reference signal during a RACH-less switching process of the terminal; the antenna port of the demodulation reference signal DMRS of the first channel and the target reference signal are in a quasi-co-site QCL relationship; wherein the first channel includes at least one of the following: a RACH-less physical downlink control channel PDCCH; a RACH-less physical downlink shared channel PDSCH, and the communication interface is used to receive the first channel based on the target reference signal during a RACH-less switching process of the terminal; the antenna port of the DMRS of the first channel and the target reference signal are in a QCL relationship; wherein the first channel includes at least one of the following: RACH-less PDCCH; RACH-less PDSCH.
[0017] In a fifth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.
[0018] In a sixth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.
[0019] In a seventh aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the channel monitoring or receiving method as described in the first aspect.
[0020] In an embodiment of the present application, a QCL relationship is established between the antenna port of the DMRS of the first channel and the target reference signal, wherein the first channel includes at least one of RACH-less PDCCH and RACH-less PDSCH; during the RACH-less switching process of the terminal, the terminal can determine the transmission characteristics of the first channel under the QCL relationship based on the target reference signal, and then the terminal monitors or receives the PDCCH and PDSCH based on the transmission characteristics, which helps to improve the reliability of the downlink control and data channels and improve the success rate of the RACH-less switching. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;
[0022] Figure 2 It is a flow chart of a channel monitoring or receiving method provided in an embodiment of the present application;
[0023] Figure 3 is a structural diagram of a channel monitoring or receiving device provided in an embodiment of the present application;
[0024] Figure 4 This is one of the hardware structure diagrams of a terminal provided in an embodiment of the present application;
[0025] Figure 5 This is the second schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application. DETAILED DESCRIPTION
[0026] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.
[0027] The terms "first", "second", etc. of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0028] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.
[0029] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6 thGeneration, 6G) communication system.
[0030] Figure 11 is a block diagram of a wireless communication system applicable to the embodiment of the present application. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and other terminal side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AP) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.
[0031] The channel monitoring or receiving method provided in the embodiment of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.
[0032] First of all, it should be noted that the channel monitoring or receiving method provided in the embodiment of the present application can be applied to non-terrestrial network (NTN) scenarios, and can also be applied to terrestrial network (TN) communication scenarios, and the present application does not limit this.
[0033] The following is an introduction to NTN:
[0034] The satellite types considered in the NTN network are mainly geosynchronous earth orbit satellites (GEO), medium earth orbit satellites (MEO), and low earth orbit satellites (LEO) according to the orbital altitude. According to whether the base station is on the satellite, it can be divided into two types of NTN networks, namely regenerative payload and transparent payload. These two aspects are the main factors that determine the delay in the NTN network. The following Table 1 describes the delay size in GEO and LEO networks.
[0035] Table 1
[0036]
[0037]
[0038] The scheduling timing relationship offset (K_offset) is introduced in the 3rd Generation Partnership Project (3GPP) to enhance the timing relationship.
[0039] In the initial access phase, a cell specific K_offset is used, and the K_offset is indicated through a system message.
[0040] After the initial access phase, the user equipment (UE) specific K_offset may be indicated and updated via a MAC Control Element (MAC CE). The MAC CE provides a differential UE specific K_offset value. A complete UE specific K_offset value is equal to the cell specific K_offset minus the differential UE specific K_offset.
[0041] After the initial access phase, if there is no indication and update of K_offset, the cell specific K_offset in the system message continues to be used for the enhancement of all the above timing relationships. The cell specific K_offset value range is 0-1023ms; the UE specific K_offset value range is 0-63ms.
[0042] The timing advance (TA) applied by NTN UE is determined by the following formula (1):
[0043] T TA =(N TA +N TA,UE-specific +N TA,common +N TA,offset )×T c (1)
[0044] Among them, N TA Indicated and updated by the TACommand field in msg2 / msgB or the TAcommand in the MAC CE; for the Physical Random Access Channel (PRACH), N TA =0;
[0045] N TA,UE-specific TA estimated and pre-compensated by the UE autonomously;
[0046] N TA,common A public TA that is controlled and instructed by the network;
[0047] N TA,offset is a fixed timing offset that depends on the frequency band and LTE / NR coexistence, and is specified by network configuration or protocol;
[0048] T c is the basic time unit, T c =1 / (Δf max ·N f ), where Δf max =480·10 3 Hz; N f =4096.
[0049] And N TA,UE-specific It is calculated by the UE based on some auxiliary information, such as the UE position and the ephemeris of the serving satellite.
[0050] NTN UE at least supports calculating and pre-compensating the Doppler frequency offset on the service link through the UE position and the ephemeris of the serving satellite.
[0051] The above N TA,commonThe relevant parameters and the ephemeris of the service satellite use the same validity duration (validityduration), which is broadcast by system messages and indicated by 4 bits. The optional values are {5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 120, 180, 240, 900 (for GEO)}, in seconds.
[0052] During a valid duration, the UE assumes that N TA,common The relevant parameters and the ephemeris of the service satellite are valid and there is no update. If within a valid duration, N TA,common If the relevant parameters and the ephemeris of the serving satellite are not available, the UE assumes that the uplink is out of sync.
[0053] The above-mentioned effective duration starts from the initial time (epoch time) of the auxiliary information (such as the ephemeris of the service satellite). When the epoch time is explicitly indicated by the system message, the epoch time is the starting time of a downlink (DL) subframe, and the DL subframe is obtained by the system frame number (SFN) and the subframe number.
[0054] When the system message does not explicitly indicate the epoch time, the epoch time can be implicitly determined by the end time of the system message window (SI window) that transmits the NTN-specific system information block (SIB); when the epoch time is indicated by dedicated signaling, the epoch time is the start time of a DL subframe, which is indicated by the SFN and subframe number.
[0055] RACH-less handover in NR:
[0056] The PUSCH during RACH-less switching in NR can be a pre-allocated grant, a configured grant Type 1, or dynamically scheduled.
[0057] In the channel monitoring or receiving method provided in the embodiment of the present application, a quasi co-location (QCL) relationship is established between the antenna port of the DMRS of the first channel and the target reference signal, wherein the first channel includes at least one of a RACH-less physical downlink control channel (PDCCH) and a RACH-less physical downlink shared channel (PDSCH); during the RACH-less switching process of the terminal, the terminal can determine the transmission characteristics of the first channel under the QCL relationship based on the target reference signal, and then the terminal monitors or receives the PDCCH and PDSCH based on the transmission characteristics, which helps to improve the reliability of the downlink control and data channels and improve the success rate of the RACH-less switching.
[0058] The channel monitoring or receiving method provided in the embodiment of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.
[0059] Figure 2 is a flow chart of a channel monitoring or receiving method provided in an embodiment of the present application, such as Figure 2 As shown, the method includes step 201; wherein:
[0060] Step 201. During the RACH-less switching process of the terminal, the terminal monitors or receives a first channel based on a target reference signal; the antenna port of the demodulation reference signal DMRS of the first channel and the target reference signal are in a quasi-co-site QCL relationship; wherein the first channel includes at least one of the following: a RACH-less physical downlink control channel PDCCH; and a RACH-less physical downlink shared channel PDSCH.
[0061] It can be understood that the RACH-less PDCCH is the PDCCH in which the terminal performs RACH-less switching, and the RACH-less PDSCH is the PDCCH in which the terminal performs RACH-less switching.
[0062] It should be noted that the embodiments of the present application can be applied to a scenario where a terminal performs RACH-less switching. The terminal includes but is not limited to the types of the terminal 11 listed above.
[0063] Since the terminal does not send RACH in the target cell and select the corresponding reference signal during the RACH-less switching process, some transmission characteristics, such as measurement information or spatial relationship or beam relationship, cannot be well mapped or inferred, resulting in poor reliability of downlink control and data channels and a low success rate of RACH-less switching.
[0064] Therefore, in order to improve the reliability of downlink control and data channels, and thus improve the success rate of RACH-less switching, in an embodiment of the present application, a QCL assumption for PDCCH and PDSCH transmission is proposed, so that the terminal can monitor or receive the first channel based on the target reference signal and QCL relationship during the RACH-less switching process.
[0065] That is to say, there is a QCL relationship between the antenna port of the DMRS of at least one of RACH-less PDCCH and RACH-less PDSCH and the target reference signal. Based on the target reference signal and the QCL relationship, the terminal can monitor or receive RACH-less PDCCH and RACH-less PDSCH.
[0066] For example, the terminal monitors or receives RACH-less PDCCH and RACH-less PDSCH based on a target reference signal having a QCL relationship with RACH-less PDCCH and RACH-less PDSCH, and then determines the corresponding transmission characteristics (such as beam or spatial reception parameters). That is, based on the transmission characteristics and QCL relationship associated with the target reference signal, the corresponding transmission characteristics of RACH-less PDCCH and RACH-less PDSCH can be inferred, thereby monitoring or receiving.
[0067] Optionally, there are multiple ways for the terminal to obtain the QCL relationship, for example, it may be predefined in the protocol, preconfigured, or indicated by a network-side device.
[0068] In an embodiment of the present application, a QCL relationship is established between the antenna port of the DMRS of the first channel and the target reference signal, wherein the first channel includes at least one of RACH-less PDCCH and RACH-less PDSCH; during the RACH-less switching process of the terminal, the terminal can determine the transmission characteristics of the first channel under the QCL relationship based on the target reference signal, and then the terminal monitors or receives the PDCCH and PDSCH based on the transmission characteristics, which helps to improve the reliability of the downlink control and data channels and improve the success rate of the RACH-less switching.
[0069] Optionally, the QCL relationship includes at least one of the following:
[0070] a) Average gain.
[0071] b) QCL relationship of type A (quasi co-location 'typeA').
[0072] Specifically, the QCL relationship of type A includes at least one of Doppler shift, Doppler spread, average delay, and delay spread.
[0073] For example, if the antenna port of the DMRS of the first channel has a QCL relationship of type A with the target reference signal, the terminal determines at least one of the Doppler shift, Doppler spread, average delay and delay spread of the target reference signal, and then applies it to the antenna port of the DMRS of the first channel for channel estimation.
[0074] c) QCL relationship of type D (quasi co-location 'typeD').
[0075] Specifically, the QCL relationship of type D includes spatial reception parameters (Spatial Rx parameter).
[0076] For example, if the antenna port of the DMRS of the first channel has a QCL relationship of type D with the target reference signal, the terminal can use the same spatial reception parameter / beam as the target reference signal to monitor or receive the signal on the DMRS antenna port of the first channel.
[0077] Optionally, the target reference signal includes at least one of the following:
[0078] 1) RACH-less PUSCH-associated synchronization signal block (SSB) or channel state information reference signal (CSI Reference Signal, CSI-RS).
[0079] Optionally, the SSB or CSI-RS associated with the RACH-less PUSCH is determined based on any one of the following methods:
[0080] Mode 1: When the RACH-less PUSCH is a pre-configured PUSCH or a configured granted PUSCH of type 1, the SSB or CSI-RS associated with the RACH-less PUSCH is determined based on a mapping relationship between PUSCH resources and SSB or CSI-RS.
[0081] That is, when the PUSCH transmission of RACH-less switching is a pre-allocated grant or a configured grant Type 1, the SSB or CSI-RS associated with the PUSCH is determined by the mapping relationship between the PUSCH resource and the SSB or CSI-RS.
[0082] Mode 2: When the RACH-less PUSCH is dynamically scheduled, the SSB or CSI-RS associated with the RACH-less PUSCH is determined based on downlink control information (DCI) used to schedule the RACH-less PUSCH.
[0083] That is, in the case where the PUSCH transmission of RACH-less switching is dynamically scheduled, the SSB or CSI-RS associated with the PUSCH is specified by the DCI that schedules the PUSCH.
[0084] 2) The target SSB or target CSI-RS in the source cell before the terminal performs RACH-less switching.
[0085] Optionally, the target SSB or target CSI-RS includes at least one of the following:
[0086] a) The SSB or CSI-RS most recently received by the terminal on the source cell.
[0087] b) SSB or CSI-RS associated with the RACH-less PUSCH scheduled by the PDCCH received by the terminal on the source cell.
[0088] c) the SSB or CSI-RS associated with the handover command received by the terminal on the source cell.
[0089] In the above implementation, by establishing an association between SSB or CSI-RS and DMRS antenna port resources of RACH-less PDCCH and RACH-less PDSCH, it helps to improve the reliability of downlink control and data channels, thereby improving the success rate of RACH-less switching.
[0090] Optionally, based on monitoring or receiving the first channel based on the target reference signal, it is also necessary to determine the transmission characteristics used for the transmission of the physical uplink control channel (PUCCH) for feedback of the RACH-less PDSCH reception status, so as to improve the beamforming gain of the uplink transmission, which helps to further improve the success rate of the RACH-less switching; wherein the transmission characteristics are, for example, beam / spatial reception parameters. Specifically, this can be achieved by the following steps:
[0091] The terminal determines the transmission characteristic of a PUCCH for transmitting RACH-less PDSCH hybrid automatic repeat request (HARQ) feedback based on the target transmission characteristic.
[0092] The target transmission characteristic includes any one of the following:
[0093] a) Uplink transmission characteristics used by RACH-less PUSCH.
[0094] For example, the uplink beam used by the RACH-less PUSCH may be used as the beam of the PUCCH.
[0095] b) The uplink transmission characteristics used by the most recent RACH-less PUSCH transmission.
[0096] For example, the uplink beam used for the most recent transmission of the RACH-less PUSCH may be used as the beam of the PUCCH.
[0097] c) Transmission characteristics indicated by network-side equipment.
[0098] For example, a certain beam is indicated as the beam of PUCCH in the handover command.
[0099] It should be noted that the target transmission characteristic is determined based on the QCL relationship.
[0100] In the above implementation, for PUCCH transmission, by establishing an association between the PUCCH transmission characteristics and the transmission characteristics used by the configuration grant (CG) and / or dynamic grant (DG) PUSCH in RACH-less, the beamforming gain of uplink transmission can be improved.
[0101] Optionally, when the RACH-less PUSCH is DG, it is necessary to make certain restrictions on the DCI format and search space used by the RACH-less PDCCH, so as to reduce the complexity of the terminal and improve the reliability of the RACH-less PDCCH, and further improve the success rate of the RACH-less switching; this can be achieved by the following steps:
[0102] The terminal determines a search space for a PDCCH for scheduling a RACH-less PUSCH based on a target search space; wherein the target search space includes any one of the following search spaces:
[0103] a) Public search space.
[0104] Optionally, the common search space includes: a Type 1 PDCCH common search space set Type1-PDCCH CSS set of the target cell, wherein the Type1-PDCCH CSS set is indicated by a high-layer parameter ra-SearchSpace.
[0105] b) Search space indicated by the network side device.
[0106] For example, the search space indicated by the network side device may be a type 1B PDCCH common search space set Type1B-PDCCH CSS set configured by the network side device. In the PDCCH-ConfigCommon parameter of the Type1B-PDCCH CSS set, rachless-SearchSpace is configured, and the DCI format corresponding to the rachless-SearchSpace is scrambled with a cell radio network temporary identifier (Cell Radio Network Temporary Identifier, C-RNTI) or a configured scheduling RNTI (Configured Scheduling RNTI, CS-RNTI). It can be specifically expressed in the following ways:
[0107] Type1B-PDCCH CSS set, rachless-SearchSpace in PDCCH-ConfigCommon for aDCI format with CRC scrambled by a C-RNTI or a CS-RNTI.
[0108] Optionally, when the network side device is not configured with rachless-SearchSpace and does not provide at least one of Type3-PDCCH CSS set, Type1A-PDCCH CSS set and user equipment-specific search space set (UE-specific searchspace set, USS set), the terminal will monitor C-RNTI or CS-RNTI in rachless-SearchSpace.
[0109] In the above implementation, by determining the search space of the PDCCH for scheduling the RACH-less PUSCH, the terminal complexity can be reduced and the reliability of the RACH-less PDCCH can be improved, thereby further improving the success rate of the RACH-less handover.
[0110] Optionally, the terminal also needs to perform the following steps:
[0111] The terminal schedules the RACH-less PUSCH using the target DCI format format;
[0112] The target DCI format includes any one of the following DCI formats:
[0113] a) DCI format 0_0; that is, fallback DCI.
[0114] b) DCI format agreed upon by the protocol or indicated by the network-side device.
[0115] Optionally, when the first channel is a PDCCH, the PDCCH transmission includes any one of the following:
[0116] a) PDCCH repetition transmission;
[0117] b) PDCCH group transmission.
[0118] In an embodiment of the present application, in NR RACH-less switching, PDCCH repetition and the association of SSB, CSI-RS to PDCCH repetition are introduced.
[0119] For example, the UE selects to receive the corresponding PDCCH repetition based on the best SSB on the target cell, or the UE receives all different PDCCH repetitions.
[0120] As a sub-embodiment of the above embodiment, the time domain resource allocation of the PUSCH scheduled by the PDCCH repetition uses the time slot where the last PDCCH repetition is located as a reference time, thereby determining the time domain resources corresponding to the PUSCH transmission.
[0121] In an embodiment of the present application, in NR RACH-less switching, PDCCH grouping and an association of a group of SSBs and CSI-RS to a PDCCH group are introduced.
[0122] The PDCCH grouping here may be a group of PDCCH monitoring occasions, or the PDCCH grouping corresponds to multiple PDCCH transmissions.
[0123] In the above implementation, by limiting the DCI format of the PDCCH that schedules the RACH-less PUSCH, the number of blind detections can be reduced, the terminal complexity can be reduced, the reliability of the RACH-less PDCCH can be improved, and the success rate of the RACH-less switching can be improved.
[0124] The channel monitoring or receiving method provided in the embodiment of the present application is further described below.
[0125] Optionally, during the NR RACH-less switching process of the terminal, the DMRS antenna port associated with receiving the PDCCH and / or PDSCH and the SSB or CSI-RS associated with the PUSCH in the NR RACH-less switching are QCL relationships in one or more of the following senses:
[0126] 1) Average gain;
[0127] 2) QCL relationship of type A;
[0128] 3) Type D QCL relationship.
[0129] In the above embodiments, the QCL relationship is applicable to one or more of the following situations:
[0130] [1] When the PUSCH transmission of RACH-less switching is a pre-allocated grant, the SSB or CSI-RS associated with the PUSCH is determined by the mapping relationship between the PUSCH resource and the SSB or CSI-RS.
[0131] [2] In the case of dynamic scheduling of PUSCH transmission with RACH-less switching, the SSB or CSI-RS associated with the PUSCH is specified by the DCI that schedules the PUSCH.
[0132] Optionally, during the NR RACH-less switching process of the terminal, the DMRS antenna port associated with the received PDCCH and / or PDSCH has a QCL relationship with a certain SSB or a certain CSI-RS in the source cell before the NR RACH-less switching in one or more of the following senses:
[0133] 1) Average gain;
[0134] 2) QCL relationship of type A;
[0135] 3) Type D QCL relationship.
[0136] A certain SSB or a certain CSI-RS in the above embodiment may be one or more of the following:
[0137] [1] The SSB or CSI-RS most recently received by the UE on the source cell;
[0138] [2] The UE receives the SSB or CSI-RS associated with the PDCCH-scheduled RACH-less PUSCH on the source cell;
[0139] [3] The UE receives the SSB or CSI-RS associated with the handover command on the source cell.
[0140] Optionally, the beam for the UE to send the PUCCH for feedback of the PDSCH reception status may be determined by one or more of the following methods:
[0141] 1) The uplink beam used for PUSCH switched by RACH-less;
[0142] 2) The uplink beam used for the most recent PUSCH transmission of the RACH-less switch;
[0143] 3) Instructed by the network, such as a handover command.
[0144] Optionally, the search space of the PDCCH for scheduling the RACH-less PUSCH is determined by one or more of the following methods:
[0145] 1) Use existing public search space;
[0146] For example, the Type1-PDCCH CSS of the target cell sets ra-SearchSpace.
[0147] 2) The network side device configures an additional search space; for example:
[0148] The network configures a Type1B-PDCCH CSS set, rachless-SearchSpace in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a C-RNTI or a CS-RNTI.
[0149] Optionally, when rachless-SearchSpace is not configured, and Type3-PDCCH CSS set, or Type1A-PDCCH CSS set, or USS set is not provided, the UE will monitor C-RNTI / CS-RNTI in rachless-SearchSpace.
[0150] Optionally, the DCI format of the PDCCH scheduling the RACH-less PUSCH is determined by one or more of the following methods:
[0151] 1) Just use DCI format 0_0, i.e. fallback DCI;
[0152] 2) Introduce a new DCI format.
[0153] In the channel monitoring or receiving method provided in the embodiment of the present application, in the NR RACH-less switching, a QCL relationship between the SSB or CSI-RS signal and the DMRS antenna port resources of the PDCCH and PDSCH is established, which helps to improve the reliability of the downlink control and data channels; in addition, for PUCCH transmission, an association is established between the PUCCH beam and the beam used by the CG and / or DGPUSCH in the RACH-less, thereby improving the beamforming gain of the uplink transmission; at the same time, when the RACH-less PUSCH is DG, certain restrictions are made on the DCI format and search space used for the corresponding PDCCH, thereby reducing the UE complexity and improving the reliability of the PDCCH, thereby improving the success rate of the RACH-less switching.
[0154] The channel monitoring or receiving method provided in the embodiment of the present application can be executed by a channel monitoring or receiving device. In the embodiment of the present application, the channel monitoring or receiving device performing the channel monitoring or receiving method is taken as an example to illustrate the channel monitoring or receiving device provided in the embodiment of the present application.
[0155] Figure 3 is a schematic diagram of the structure of a channel monitoring or receiving device provided in an embodiment of the present application, such as Figure 3 As shown, the channel monitoring or receiving device 300 includes:
[0156] The monitoring or receiving module 301 is used to monitor or receive a first channel based on a target reference signal during a RACH-less switching process of a terminal; an antenna port of a demodulation reference signal DMRS of the first channel and the target reference signal are in a quasi-co-location QCL relationship;
[0157] Wherein, the first channel includes at least one of the following:
[0158] RACH-less physical downlink control channel PDCCH;
[0159] RACH-less Physical Downlink Shared Channel PDSCH.
[0160] In the channel monitoring or receiving device provided in the embodiment of the present application, a QCL relationship is established between the antenna port of the DMRS of the first channel and the target reference signal, wherein the first channel includes at least one of RACH-less PDCCH and RACH-less PDSCH; during the RACH-less switching process of the terminal, the transmission characteristics of the first channel under the QCL relationship can be determined based on the target reference signal, and then the PDCCH and PDSCH are monitored or received based on the transmission characteristics, which helps to improve the reliability of downlink control and data channels and improve the success rate of RACH-less switching.
[0161] Optionally, the target reference signal includes at least one of the following:
[0162] RACH-less physical uplink shared channel PUSCH associated synchronization signal block SSB or channel state information reference signal CSI-RS;
[0163] The terminal performs a target SSB or a target CSI-RS in a source cell before performing a RACH-less handover.
[0164] Optionally, the SSB or CSI-RS associated with the RACH-less PUSCH is determined based on any one of the following methods:
[0165] In a case where the RACH-less PUSCH is a pre-configured PUSCH or a configured granted PUSCH of type 1, determining the SSB or CSI-RS associated with the RACH-less PUSCH based on a mapping relationship between a PUSCH resource and an SSB or a CSI-RS;
[0166] In the case where the RACH-less PUSCH is dynamically scheduled, the SSB or CSI-RS associated with the RACH-less PUSCH is determined based on downlink control information DCI used to schedule the RACH-less PUSCH.
[0167] Optionally, the target SSB or target CSI-RS includes at least one of the following:
[0168] The SSB or CSI-RS most recently received by the terminal on the source cell;
[0169] An SSB or CSI-RS associated with a RACH-less PUSCH scheduled by a PDCCH received by the terminal on a source cell;
[0170] The SSB or CSI-RS associated with the handover command received by the terminal on the source cell.
[0171] Optionally, the QCL relationship includes at least one of the following:
[0172] Average gain;
[0173] QCL relationship of type A;
[0174] Type D QCL relationship.
[0175] Optionally, the device further comprises:
[0176] A first determining module is used to determine the transmission characteristics of a physical uplink control channel PUCCH used for transmitting RACH-less PDSCH hybrid automatic repeat request HARQ feedback based on the target transmission characteristics;
[0177] The target transmission characteristic includes any one of the following:
[0178] Uplink transmission characteristics used by RACH-less PUSCH;
[0179] The uplink transmission characteristics used by the most recent RACH-less PUSCH transmission;
[0180] Transmission characteristics indicated by network-side equipment.
[0181] Optionally, the device further comprises:
[0182] A second determining module is used to determine a search space of a PDCCH for scheduling a RACH-less PUSCH based on a target search space;
[0183] The target search space includes any of the following search spaces:
[0184] Public search space;
[0185] Search space indicated by the network-side device.
[0186] Optionally, the common search space includes: a Type 1 PDCCH common search space set Type1-PDCCH CSS set of the target cell.
[0187] Optionally, the device further comprises:
[0188] A scheduling module, used for scheduling RACH-less PUSCH using a target DCI format format;
[0189] The target DCI format includes any one of the following DCI formats:
[0190] DCI format 0_0;
[0191] DCI format specified by the protocol or indicated by the network device.
[0192] Optionally, when the first channel is a PDCCH, the PDCCH transmission includes any one of the following:
[0193] PDCCH repetition transmission;
[0194] PDCCH group transmission.
[0195] The channel monitoring or receiving device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or it can be other devices other than a terminal. Exemplarily, the terminal can include but is not limited to the types of terminals 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.
[0196] The channel monitoring or receiving device provided in the embodiment of the present application can achieve Figure 2 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.
[0197] Figure 4 is one of the hardware structure diagrams of a terminal provided in an embodiment of the present application. The terminal 400 includes a processor 401 and a memory 402. The memory 402 stores a program or instruction that can be run on the processor 401. For example, when the program or instruction is executed by the processor 401, the above Figure 2 The various steps of the channel monitoring or receiving method embodiment shown can achieve the same technical effect.
[0198] The embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the following Figure 2 The steps in the channel monitoring or receiving method embodiment are shown. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 5 This is the second schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application.
[0199] The terminal 500 includes but is not limited to: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, a memory 509 and at least some of the components of a processor 510.
[0200] Those skilled in the art will appreciate that the terminal 500 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 510 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 5 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.
[0201] It should be understood that in the embodiment of the present application, the input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042, and the graphics processor 5041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 506 may include a display panel 5061, and the display panel 5061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 507 includes a touch panel 5071 and at least one of other input devices 5072. The touch panel 5071 is also called a touch screen. The touch panel 5071 may include two parts: a touch detection device and a touch controller. Other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control button, a switch button, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
[0202] In the embodiment of the present application, after receiving downlink data from the network side device, the radio frequency unit 501 can transmit the data to the processor 510 for processing; in addition, the radio frequency unit 501 can send uplink data to the network side device. Generally, the radio frequency unit 501 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
[0203] The memory 509 can be used to store software programs or instructions and various data. The memory 509 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 509 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 509 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.
[0204] The processor 510 may include one or more processing units; optionally, the processor 510 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 510.
[0205] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the above Figure 2 The relevant description of the channel monitoring or receiving method embodiment shown in the figure achieves the same or corresponding technical effect, so it will not be repeated here to avoid repetition.
[0206] The embodiment of the present application also provides a readable storage medium on which a program or instruction is stored. When the program or instruction is executed by a processor, the above Figure 2The various processes of the channel monitoring or receiving method embodiment shown can achieve the same technical effect. To avoid repetition, they will not be described here.
[0207] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.
[0208] The present application also provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the above Figure 2 The various processes of the channel monitoring or receiving method embodiment shown can achieve the same technical effect. To avoid repetition, they will not be described here.
[0209] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0210] The present application embodiment further provides a computer program / program product, wherein the computer program / program product is stored in a storage medium, and the computer program / program product is executed by at least one processor to implement the above Figure 2 The various processes of the channel monitoring or receiving method embodiment shown can achieve the same technical effect. To avoid repetition, they will not be described here.
[0211] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0212] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.
[0213] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.
Claims
1. A channel monitoring or receiving method, characterized in that: include: During the RACH-less switching of the terminal, the terminal monitors or receives the first channel based on the target reference signal; the antenna port of the demodulation reference signal DMRS of the first channel and the target reference signal are in a quasi-co-location QCL relationship; Wherein, the first channel includes at least one of the following: RACH-less physical downlink control channel PDCCH; RACH-less Physical Downlink Shared Channel PDSCH.
2. The method according to claim 1, characterized in that The target reference signal includes at least one of the following: RACH-less physical uplink shared channel PUSCH associated synchronization signal block SSB or channel state information reference signal CSI-RS; The terminal performs a target SSB or a target CSI-RS in a source cell before performing a RACH-less handover.
3. The method according to claim 2, characterized in that The SSB or CSI-RS associated with the RACH-less PUSCH is determined based on any of the following methods: In a case where the RACH-less PUSCH is a pre-configured PUSCH or a configured granted PUSCH of type 1, determining the SSB or CSI-RS associated with the RACH-less PUSCH based on a mapping relationship between a PUSCH resource and an SSB or a CSI-RS; In the case where the RACH-less PUSCH is dynamically scheduled, the SSB or CSI-RS associated with the RACH-less PUSCH is determined based on downlink control information DCI used to schedule the RACH-less PUSCH.
4. The method according to claim 2, characterized in that: The target SSB or target CSI-RS includes at least one of the following: The SSB or CSI-RS most recently received by the terminal on the source cell; An SSB or CSI-RS associated with a RACH-less PUSCH scheduled by a PDCCH received by the terminal on a source cell; The SSB or CSI-RS associated with the handover command received by the terminal on the source cell.
5. The method according to any one of claims 1 to 4, characterized in that: The QCL relationship includes at least one of the following: Average gain; QCL relationship of type A; Type D QCL relationship.
6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: The terminal determines, based on the target transmission characteristic, a transmission characteristic of a physical uplink control channel PUCCH for transmitting RACH-less PDSCH hybrid automatic repeat request HARQ feedback; The target transmission characteristic includes any one of the following: Uplink transmission characteristics used by RACH-less PUSCH; The uplink transmission characteristics used by the most recent RACH-less PUSCH transmission; Transmission characteristics indicated by network-side equipment.
7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: The terminal determines, based on the target search space, a search space of the PDCCH for scheduling the RACH-less PUSCH; The target search space includes any of the following search spaces: Public search space; Search space indicated by the network-side device.
8. The method according to claim 7, characterized in that The common search space includes: a Type 1 PDCCH common search space set Type1-PDCCH CSS set of a target cell.
9. The method according to any one of claims 1 to 8, characterized in that: The method further comprises: The terminal schedules the RACH-less PUSCH using the target DCI format format; The target DCI format includes any one of the following DCI formats: DCI format 0_0; DCI format specified by the protocol or indicated by the network device.
10. The method according to any one of claims 1 to 9, characterized in that: In the case where the first channel is a PDCCH, the PDCCH transmission includes any one of the following: PDCCH repetition transmission; PDCCH group transmission.
11. A channel monitoring or receiving device, characterized in that: include: A monitoring or receiving module, configured to monitor or receive a first channel based on a target reference signal during a RACH-less switching process of a terminal; an antenna port of a demodulation reference signal DMRS of the first channel and the target reference signal are in a quasi-co-location QCL relationship; Wherein, the first channel includes at least one of the following: RACH-less physical downlink control channel PDCCH; RACH-less Physical Downlink Shared Channel PDSCH.
12. A terminal, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the channel monitoring or receiving method according to any one of claims 1 to 10 are implemented.
13. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the channel monitoring or receiving method according to any one of claims 1 to 10 are implemented.
Citation Information
Cited By
Channel monitoring or receiving method and device and terminal
EP4716350A1
