Channel monitoring or receiving method and device and terminal
By establishing a quasi-co-address relationship between the DMRS antenna port of the RACH-less channel and the target reference signal in the terminal, the problem of low RACH-less handover success rate in NR is solved, and the reliability and handover success rate of the downlink channel are improved. .
Patent Information
- Application Number
- PCT/CN2024/092777
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-15
- Filing Date
- 2024-05-13
- Publication Date
- 2024-11-21
AI Technical Summary
In the new air interface (NR), the success rate of RACH-less handover is low, mainly due to the lack of association between the downlink channel beam and the demodulation reference signal (DMRS), resulting in poor downlink control and data channel reliability.
By establishing a quasi-co-address (QCL) relationship between the DMRS antenna port of the RACH-less channel and the target reference signal in the terminal, the transmission characteristics are determined based on the target reference signal, and the monitoring and reception reliability of PDCCH and PDSCH is improved.
It improves the success rate of RACH-less handover, enhances the reliability of downlink control and data channel, and ensures the accuracy and stability of channel transmission.
Smart Images

Figure CN2024092777_21112024_PF_FP_ABST
Abstract
Description
Channel monitoring or receiving method, device and terminal
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to Chinese patent application No. 202310547636.7 filed in China on May 15, 2023, the entire contents of which are incorporated herein by reference. Technical Field
[0003] 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
[0004] In Long Term Evolution (LTE) RACH-less transmission, the correlation between the uplink and downlink beams and the Demodulation Reference Signal (DMRS) antenna port and known signals is not considered. New Radio (NR) requires support for RACH-less Physical Uplink Shared Channel (PUSCH) transmission. Because 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 for RACH-less handovers.
[0005] Therefore, how to improve the success rate of RACH-less handover is an urgent problem to be solved.
[0006] Summary of the Invention
[0007] The embodiments of the present application provide a channel monitoring or receiving method, apparatus, and terminal, which can solve the problem of how to improve the success rate of RACH-less handover.
[0008] In a first aspect, a channel monitoring or receiving method is provided, which is performed by a terminal, and the method includes:
[0009] During a RACH-less handover of a terminal, the terminal monitors or receives a first channel based on a target reference signal; 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;
[0010] The first channel includes at least one of the following:
[0011] RACH-less Physical Downlink Control Channel (PDCCH);
[0012] RACH-less Physical Downlink Shared Channel (PDSCH).
[0013] In a second aspect, a channel monitoring or receiving device is provided, comprising:
[0014] A monitoring or receiving module is configured to monitor or receive a first channel based on a target reference signal during a RACH-less handover 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-site QCL relationship;
[0015] The first channel includes at least one of the following:
[0016] RACH-less physical downlink control channel PDCCH;
[0017] RACH-less Physical Downlink Shared Channel PDSCH.
[0018] In a third aspect, a terminal is provided, which includes 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 as described in the first aspect are implemented.
[0019] In a fourth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is configured 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; and a RACH-less physical downlink shared channel PDSCH; and the communication interface is configured 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; and RACH-less PDSCH.
[0020] 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 channel monitoring or receiving method as described in the first aspect are implemented.
[0021] 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 steps of the channel monitoring or receiving method as described in the first aspect.
[0022] In a seventh aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the channel monitoring or receiving method as described in the first aspect.
[0023] 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
[0024] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;
[0025] FIG2 is a flow chart of a channel monitoring or receiving method provided in an embodiment of the present application;
[0026] FIG3 is a schematic structural diagram of a channel monitoring or receiving device provided in an embodiment of the present application;
[0027] FIG4 is a schematic diagram of a hardware structure of a terminal provided in an embodiment of the present application;
[0028] FIG5 is a second schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application. DETAILED DESCRIPTION
[0029] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.
[0030] The terms "first", "second", etc. in this 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 the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.
[0031] 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, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.
[0032] 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 example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems.
[0033] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. 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 (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), a teller machine, or a self-service machine, or 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 called 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 can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NRNode B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), 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 vocabulary. It should be noted that in the embodiment 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.
[0034] The channel monitoring or receiving method provided in the embodiments of the present application is described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.
[0035] 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.
[0036] The following is an introduction to NTN:
[0037] Satellite types considered in NTN networks primarily include geosynchronous Earth orbit (GEO), medium Earth orbit (MEO), and low Earth orbit (LEO), based on their orbital altitude. NTN networks can be categorized into two types, depending on whether the base station is on the satellite: regenerative payload and transparent payload. These two factors are the primary determinants of latency in NTN networks. Table 1 below describes the latency in GEO and LEO networks.
[0038] Table 1
[0039] The scheduling timing relationship offset (K_offset) is introduced in the 3rd Generation Partnership Project (3GPP) to enhance the timing relationship.
[0040] In the initial access phase, a cell-specific K_offset is used, and the K_offset is indicated through a system message.
[0041] 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.
[0042] After the initial access phase, if there is no indication or update of K_offset, the cell-specific K_offset in the system message continues to be used for all the above timing enhancements. The cell-specific K_offset value range is 0–1023ms; the UE-specific K_offset value range is 0–63ms.
[0043] The timing advance (TA) used by NTN UE is determined by the following formula (1): TA =(N TA +N TA,UE-specific +NTA,common +N TA,offset )×T c (1)
[0044] Among them, N TA Indicated and updated by the TA Command field in msg2 / msgB or the TA command in MAC CE; for the Physical Random Access Channel (PRACH), N TA =0;
[0045] N TA,UE-specific TA is 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 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 using the UE position and the ephemeris of the serving satellite.
[0051] The above N TA,common The relevant parameters and the ephemeris of the service satellite use the same validity duration, 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, NTA,common If the relevant parameters and the ephemeris of the serving satellite are unavailable, the UE assumes that the uplink is out of synchronization.
[0053] The above-mentioned valid duration starts from the initial time (epoch time) of the auxiliary information (such as the ephemeris of the serving 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 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 handover 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 an embodiment of the present application, a quasi-co-site 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 the RACH-less physical downlink control channel PDCCH and the 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 improves the success rate of the RACH-less switching.
[0058] The channel monitoring or receiving method provided in the embodiments of the present application is described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.
[0059] FIG2 is a flow chart of a channel monitoring or receiving method provided in an embodiment of the present application. As shown in FIG2 , the method includes step 201; wherein:
[0060] Step 201: During a RACH-less switching process of a terminal, the terminal monitors or receives a first channel based on a target reference signal; an antenna port of a 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 handover, and the RACH-less PDSCH is the PDCCH in which the terminal performs RACH-less handover.
[0062] It should be noted that the embodiment of the present application can be applied to a scenario where a terminal performs RACH-less handover. The terminal includes but is not limited to the types of terminal 11 listed above.
[0063] During RACH-less handover, the terminal does not transmit RACH in the target cell and select the corresponding reference signal. Therefore, some transmission characteristics, such as measurement information, spatial relationships, or beam relationships, cannot be accurately mapped or inferred. This results in poor reliability of downlink control and data channels and a low success rate for RACH-less handover.
[0064] Therefore, in order to improve the reliability of downlink control and data channels, and thereby 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, the antenna port of the DMRS of at least one of the RACH-less PDCCH and the RACH-less PDSCH and the target reference signal have a QCL relationship. The terminal can monitor or receive the RACH-less PDCCH and the RACH-less PDSCH based on the target reference signal and the QCL relationship.
[0066] For example, the terminal determines the corresponding transmission characteristics (such as beam or spatial reception parameters) based on the target reference signal having a QCL relationship with the RACH-less PDCCH and the RACH-less PDSCH, and monitors or receives the RACH-less PDCCH and the RACH-less PDSCH. That is, based on the transmission characteristics and QCL relationship associated with the target reference signal, the corresponding transmission characteristics of the RACH-less PDCCH and the RACH-less PDSCH can be inferred, thereby monitoring or receiving.
[0067] Optionally, there are multiple ways for the terminal to obtain the QCL relationship, such as protocol pre-definition, pre-configuration, and indication 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 type A QCL relationship includes at least one of Doppler shift, Doppler spread, average delay, and delay spread.
[0073] For example, the antenna port of the DMRS of the first channel and the target reference signal have a QCL relationship of type A. 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) Type D QCL relationship (quasi co-location 'typeD').
[0075] Specifically, the QCL relationship of type D includes spatial reception parameters (Spatial Rx parameters).
[0076] For example, if the antenna port of the DMRS of the first channel has a QCL relationship with the target reference signal of type D, the terminal can use the same spatial reception parameters / 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 type 1 configured granted PUSCH, 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 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 handover.
[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) an SSB or CSI-RS associated with a RACH-less PUSCH scheduled by a PDCCH received by the terminal on a 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 embodiment, 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 handover.
[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 Physical Uplink Control Channel (PUCCH) transmission used to feedback the RACH-less PDSCH reception status, thereby improving the beamforming gain of the uplink transmission, which helps to further improve the success rate of RACH-less handover; wherein the transmission characteristics are, for example, beam / spatial reception parameters. This can be achieved by the following steps:
[0091] The terminal determines a transmission characteristic of a PUCCH for transmitting RACH-less PDSCH Hybrid Automatic Repeat Request (HARQ) feedback based on a 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 can be used as the beam of the PUCCH.
[0095] b) The uplink transmission characteristics used in the most recent RACH-less PUSCH transmission.
[0096] For example, the uplink beam used for the most recent RACH-less PUSCH transmission 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 PUCCH beam in the handover command.
[0099] It should be noted that the target transmission characteristics are determined based on the QCL relationship.
[0100] In the above embodiment, 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 limit the DCI format and search space used by the RACH-less PDCCH to reduce terminal complexity and improve the reliability of the RACH-less PDCCH, thereby further improving the success rate of the RACH-less handover. 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 higher 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 can 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 (C-RNTI) or a 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 a DCI 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 search space set, USS set), the terminal will monitor C-RNTI or CS-RNTI in rachless-SearchSpace.
[0109] In the above embodiment, 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 a RACH-less PUSCH using a target DCI 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 and 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 PDCCH repetition uses the time slot where the last PDCCH repetition is located as a reference time to further determine the time domain resource corresponding to the PUSCH transmission.
[0121] In an embodiment of the present application, in NR RACH-less switching, PDCCH grouping and the 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 embodiment, by limiting the DCI format of the PDCCH that schedules the RACH-less PUSCH, the number of blind detections can be reduced, terminal complexity can be lowered, the reliability of the RACH-less PDCCH can be improved, and the success rate of the RACH-less handover 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 have a QCL relationship in one or more of the following senses:
[0126] 1) Average gain;
[0127] 2) Type A QCL relationship;
[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 for 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 RACH-less switched PUSCH transmission, 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 handover process of the terminal, the DMRS antenna port associated with receiving the PDCCH and / or PDSCH and a certain SSB or a certain CSI-RS in the source cell before the NR RACH-less handover have a QCL relationship in one or more of the following senses:
[0133] 1) Average gain;
[0134] 2) Type A QCL relationship;
[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 last 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 that the UE sends the PUCCH for feedback on the PDSCH reception status may be determined by one or more of the following methods:
[0141] 1) Uplink beam used for PUSCH in RACH-less switching;
[0142] 2) The uplink beam used for the most recent PUSCH transmission in RACH-less switching;
[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) Using 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 the rachless-SearchSpace is not configured and the Type3-PDCCH CSS set, or the Type1A-PDCCH CSS set, or the USS set is not provided, the UE will monitor C-RNTI / CS-RNTI in the 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) Only use DCI format 0_0, i.e. fallback DCI;
[0152] 2) Introduce a new DCI format.
[0153] In the channel monitoring or reception method provided in the embodiment of the present application, during NR RACH-less handover, a QCL relationship is established between the SSB or CSI-RS signal and the DMRS antenna port resources of the PDCCH and PDSCH, 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 DG PUSCH in the RACH-less, thereby improving the beamforming gain of uplink transmission. At the same time, when the RACH-less PUSCH is DG, certain restrictions are placed on the DCI format and search space used for the PDCCH, thereby reducing UE complexity, improving PDCCH reliability, and improving the success rate of RACH-less handover.
[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 used as an example to illustrate the channel monitoring or receiving device provided in the embodiment of the present application.
[0155] FIG3 is a schematic diagram of the structure of a channel monitoring or receiving device provided in an embodiment of the present application. As shown in FIG3 , the channel monitoring or receiving device 300 includes:
[0156] The monitoring or receiving module 301 is configured to monitor or receive a first channel based on a target reference signal during a RACH-less handover 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-located QCL relationship;
[0157] 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 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 a RACH-less PDCCH and a 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 the downlink control and data channels and improve the success rate of the 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 RACH-less handover before the target SSB or target CSI-RS in the source cell.
[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 type 1 configured granted PUSCH, determining an SSB or CSI-RS associated with the RACH-less PUSCH based on a mapping relationship between a PUSCH resource and an SSB or CSI-RS;
[0166] In a 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 configured to determine, based on a target transmission characteristic, a transmission characteristic of a physical uplink control channel PUCCH for transmitting RACH-less PDSCH hybrid automatic repeat request HARQ feedback;
[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 in the most recent RACH-less PUSCH transmission;
[0180] Transmission characteristics indicated by network-side devices.
[0181] Optionally, the device further comprises:
[0182] A second determining module is configured to determine a search space for 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 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, configured to schedule RACH-less PUSCH using a target DCI 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 embodiments 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 chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.
[0196] The channel monitoring or receiving device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 2 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
[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 programs or instructions that can be run on the processor 401. For example, when the program or instruction is executed by the processor 401, the various steps of the channel monitoring or receiving method embodiment shown in Figure 2 above are implemented, and the same technical effect can be achieved.
[0198] 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 configured to execute a program or instruction to implement the steps in the channel monitoring or receiving method embodiment shown in FIG2 . 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, FIG5 is a 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 the processor 510.
[0200] Those skilled in the art will appreciate that the terminal 500 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 510 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG5 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.
[0201] It should be understood that in an 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 volume control keys, switch keys, 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 a network-side device, the radio frequency unit 501 may transmit the data to the processor 510 for processing. Furthermore, the radio frequency unit 501 may send uplink data to the network-side device. Typically, 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, and the like.
[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, applications or instructions required for at least one function (such as a sound playback function, an image playback function, 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] Processor 510 may include one or more processing units. Optionally, processor 510 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 510.
[0205] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the channel monitoring or receiving method embodiment shown in Figure 2 above, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.
[0206] An 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 the processor, the various processes of the channel monitoring or receiving method embodiment shown in Figure 2 above are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated 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-transitory readable storage medium.
[0208] An embodiment of 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 programs or instructions to implement the various processes of the channel monitoring or receiving method embodiment shown in Figure 2 above, and can achieve the same technical effect. To avoid repetition, it will not be repeated 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] An embodiment of the present application also provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the channel monitoring or receiving method embodiment shown in Figure 2 above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0211] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising 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 a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments 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 the opposite 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 embodiments, 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, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or 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 this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.
Claims
1. A channel monitoring or receiving method, comprising: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, comprising: 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 comprising 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 storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the channel monitoring or receiving method according to any one of claims 1 to 10.
14. A terminal, configured to execute the steps of the channel monitoring or receiving method according to any one of claims 1 to 10.
15. A computer program / program product, wherein the computer program / program product is stored in a storage medium, and wherein the computer program / program product is executed by at least one processor to implement the steps of the channel monitoring or receiving method according to any one of claims 1 to 10.
16. A chip 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 steps of the channel monitoring or receiving method according to any one of claims 1 to 10.
Citation Information
Patent Citations
Channel monitoring method, terminal and network equipment
CN111278092A
Channel monitoring method, information transmission method, terminal and network device
CN111600692A
Method, device and terminal for determining quasi-co-location downlink RS (Reference Signal)
CN115968050A
Handover of a coordinated multi-point connection
US20220191748A1
