PDCCH configuration method, terminal equipment and storage medium
By receiving and processing the configuration information sent by the network device in the terminal device and indicating the PDCCH schemes that are related to multiple search spaces, the problem of insufficient transmission efficiency and flexibility of PDCCH in the multi-TRP environment in the prior art is solved, and the multi-TRP enhancement and system performance improvement of PDCCH is achieved.
Patent Information
- Application Number
- CN202311416592.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-03-24
- Publication Date
- 2025-03-18
- Estimated Expiration
- 2041-03-24
AI Technical Summary
The prior art has failed to effectively support the physical downlink control channel (PDCCH) multi-TRP enhancement scheme between multiple transmission points/transmitter and receive points (TRP), resulting in limited transmission efficiency and flexibility of PDCCH in a multi-TRP environment.
By receiving and processing configuration information sent by the network device in the terminal device, the configuration information indicates a plurality of search spaces that are associated with each other and correspond to a plurality of physical downlink control channels PDCCH, thereby achieving multi-TRP enhancement of the PDCCH.
It realizes the improvement of PDCCH transmission efficiency and flexibility in multi-TRP environments, and can more effectively support multi-TRP transmission scenarios and improve system coverage and performance.
Smart Images

Figure CN117377098B_ABST
Abstract
Description
[0001] This application is a divisional application of the invention patent application with application date of March 24, 2021, application number 202180081202.1, and invention name “PDCCH configuration method, terminal device and storage medium”. Technical Field
[0002] The present application relates to the field of communications, and in particular to a method, terminal device and storage medium for configuring a PDCCH. Background Art
[0003] For multi-transmission point / reception point (TRP) transmission, the New Radio (NR) Rel-16 protocol only supports the scheme of multiple TRPs simultaneously transmitting downlink data to the UE. The scheme of sending a downlink control information (DCI) from multiple TRPs to the same user equipment (UE) has not yet been introduced. Next, the multi-TRP enhancement scheme of the Physical Downlink Control Channel (PDCCH) will be studied. Currently, the 3rd Generation Partnership Project (3GPP) is discussing the details of the PDCCH multi-TRP transmission scheme. Summary of the invention
[0004] An embodiment of the present invention provides a PDCCH configuration method, terminal equipment and storage medium for realizing multi-TRP enhancement of PDCCH.
[0005] A first aspect of an embodiment of the present invention provides a method for PDCCH configuration, which may include: a first terminal device receives first configuration information sent by a first device, the first configuration information indicates N first search spaces, the physical downlink control channels PDCCH corresponding to the N first search spaces are mutually associated, and / or the N first search spaces are mutually associated, the N first search spaces correspond to PDCCH, and N is an integer greater than or equal to 2.
[0006] A second aspect of an embodiment of the present invention provides a terminal device having a function of reporting relevant UE capabilities for a solution for supporting positioning functions using multiple positioning signals in combination. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.
[0007] Another aspect of an embodiment of the present invention provides a terminal device, comprising: a memory storing executable program code; a transceiver and a processor coupled to the memory; the processor and the transceiver are used to execute the method described in the first aspect of the embodiment of the present invention.
[0008] Another aspect of an embodiment of the present invention provides a computer-readable storage medium, comprising instructions, which, when executed on a computer, enables the computer to execute the method as described in the first aspect or the second aspect of the present invention.
[0009] Another aspect of an embodiment of the present invention provides a chip, which is coupled to a memory in the terminal device, so that the chip calls program instructions stored in the memory during operation, so that the terminal device executes the method described in the first aspect or the second aspect of the present invention.
[0010] In the technical solution provided by the embodiment of the present invention, in the embodiment of the present invention, the terminal device reports to the network device through the first signaling that it supports the first terminal capability, and the first terminal capability is a positioning function based on the joint use of multiple downlink positioning signals. The solution for supporting the positioning function by the joint use of multiple positioning signals reports the relevant UE capabilities.
[0011] In the technical solution provided by the embodiment of the present invention, a first terminal device receives first configuration information sent by a first device, wherein the first configuration information indicates N first search spaces, and the physical downlink control channels PDCCH corresponding to the N first search spaces are mutually associated, and / or the N first search spaces are mutually associated, and the N first search spaces correspond to PDCCH, where N is an integer greater than or equal to 2. Used to implement multi-TRP enhancement of PDCCH. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Figure 1A A schematic diagram of multiple TRP transmissions;
[0013] Figure 1B A schematic diagram of multiple beam transmissions;
[0014] Figure 2 A system architecture diagram of a communication system used in an embodiment of the present invention;
[0015] Figure 3 A schematic diagram of an embodiment of a method for configuring a PDCCH in an embodiment of the present application;
[0016] Figure 4-1 A schematic diagram showing that the slots appearing in the PDCCH occasion corresponding to the N first search spaces in the embodiment of the present application appear in a cross form;
[0017] Figure 4-2It is a schematic diagram that the slots appearing in the PDCCH occasion corresponding to the N first search spaces in the embodiment of the present application do not appear in a cross form;
[0018] Figure 4-3 A schematic diagram showing that the slots appearing in the PDCCH occasion corresponding to the N first search spaces in the embodiment of the present application may appear in a cross form;
[0019] Figure 5 This is a schematic diagram of an embodiment of a terminal device in an embodiment of the present application;
[0020] Figure 6 This is another schematic diagram of a terminal device in an embodiment of the present application. DETAILED DESCRIPTION
[0021] The technical solutions in the embodiments of the present invention will be described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.
[0022] The following is a brief description of the terms involved in the embodiments of the present application, as shown below:
[0023] 1. Multi-beam system
[0024] The design goals of the New Radio (NR) / 5G system include large bandwidth communications in high frequency bands (e.g., bands above 6 GHz). When the operating frequency becomes higher, the path loss during transmission will increase, thus affecting the coverage capability of the high frequency system. In order to effectively ensure the coverage of the high frequency band NR system, an effective technical solution is to use multiple beams (e.g., analog beams, hybrid beams) based on massive antenna arrays (Massive MIMO) to improve coverage.
[0025] In the existing 2 / 3 / 4G typical system, a cell (sector) uses a wider beam to cover the entire cell. Therefore, at every moment, the user equipment (UE) within the cell coverage has the opportunity to obtain the transmission resources allocated by the system.
[0026] The NR / 5G Multi-beam system uses different beams to cover the entire cell, that is, each beam covers a smaller area, and multiple beams cover the entire cell through sweeping at different times. Currently, different beams are identified by the different signals they carry.
[0027] (1) Different synchronization signal blocks (Synchronization signal / PBCH block, SS block) are transmitted on different beams. UE can distinguish different beams through different SS blocks. SS block can also be expressed as SSB, SS / PBCH block.
[0028] (2) Different channel state information reference signals (CSI-RS) are transmitted on different beams, and the UE identifies different beams through CSI-RS signals / CSI-RS resources.
[0029] Therefore, the following discussion is based on the visible signal to implicitly indicate the beam carrying the signal transmission / reception.
[0030] In a multi-beam system, the Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH) can be transmitted through different downlink transmit beams.
[0031] For systems below 6G, there is generally no analog beam on the UE side, so an omnidirectional antenna (or a nearly omnidirectional antenna) is used to receive signals sent by different downlink transmit beams of the base station.
[0032] For millimeter wave systems, there may be analog beams on the UE side, and the corresponding downlink receive beam needs to be used to receive the signal sent by the corresponding downlink transmit beam. At this time, corresponding beam indication information is required to assist the UE in determining the transmit beam related information on the network side, or the corresponding receive beam related information on the UE side.
[0033] In the NR protocol, the beam indication information does not directly indicate the beam itself, but is indicated through the quasi co-location (QCL) between signals (for example, through the 'QCL-TypeD' type). On the UE side, the determination of receiving the corresponding channel / signal is also based on the QCL quasi-co-location assumption. The QCL quasi-co-location assumption is indicated by the transmission configuration indication (TCI) state (TCI-state), that is, the network configures and / or indicates the TCI state through relevant signaling (such as Radio Resource Control (RRC), and / or Media Access Control Control Element (MAC CE), and / or downlink control information (DCI).
[0034] 2. Multiple transmission points / transmission / reception points (TRP) / panel / beam transmission
[0035] Multi-TRP transmission means that multiple TRPs can communicate with a terminal at the same time on the same carrier. In the NR system, multiple TRP transmissions, or multiple panels or multiple beams transmitting to a terminal at the same time, can adopt the same scheme, so they are often not distinguished in the description (for example, collectively referred to as multi-TRP transmission, or written as multiple TRP / panel / beam transmission).
[0036] In NR / 5G Rel-16, the solution of multiple TRPs or multiple antenna panels or multiple beams transmitting downlink data to UE at the same time supports the following two types of solutions:
[0037] Alt1: single-PDCCH based scheme. The UE detects only one NR-PDCCH, and the DCI detected on this control channel PDCCH indicates relevant indication information of data transmitted simultaneously on multiple TRPs / panels / beams (from the protocol level, it is not possible to see multiple TRPs / panels / beams, but only that one transmission requires multiple TCI-states, that is, multiple TRP / panel / beam transmissions are implicitly supported through multiple TCI-states).
[0038] Alt2: multiple-PDCCH based scheme. The UE receives different NR-PDCCHs from different TRPs / panels / beams, and the DCI detected on each control channel PDCCH indicates relevant indication information of a corresponding data transmission (from the protocol level, it is not possible to see multiple TRPs / panels / beams, but only that the control resource set (CORESET) corresponding to the DCI of the scheduling data may be associated with different CORESET resource pool numbers, that is, corresponding to different CORESET pool indexes, that is, multiple TRP / panel / beam transmissions are implicitly supported through multiple different CORESET pool indexes).
[0039] like Figure 1A As shown in FIG. 1 , it is a schematic diagram of multiple TRP transmission. Figure 1B FIG. 1 is a schematic diagram of multiple beam transmission.
[0040] For the first solution (Alt1), the UE only needs to detect one NR-PDCCH, so the control channel detection complexity may be lower than the second solution. The first solution requires fast information exchange between different panels / TRPs / beams.
[0041] For the second solution (Alt2), the UE needs to detect multiple NR-PDCCHs on the same carrier at the same time. The complexity may increase, but the flexibility and robustness may be improved.
[0042] The possible application scenarios of the second solution (Alt2) include at least the following:
[0043] S1-1: Multiple TRPs belong to the same cell, and the connection (backhaul) between TRPs is ideal (i.e., fast and dynamic information exchange is possible);
[0044] S1-2: Multiple TRPs belong to the same cell, and the connection (backhaul) between TRPs is non-ideal (i.e., TRPs cannot exchange information quickly and can only exchange data relatively slowly);
[0045] S1-3: Multiple TRPs belong to different cells, and the connection (backhaul) between TRPs is ideal;
[0046] S1-4: Multiple TRPs belong to different cells, and the connection (backhaul) between TRPs is not ideal.
[0047] S2-1, S2-2, S2-3, S2-4: Replace the TRP in the above with beam, and you can get four multi-beam application scenarios. The first solution is generally considered to be only applicable to ideal backhaul scenarios (i.e., S1-1, S1-3).
[0048] It should be noted that: in the above description, for the multi-TRP system, Rel-16 only standardizes the downlink data transmission (PDSCH) scheme. For the multi-TRP system, the transmission schemes discussed above are all for the case of the same carrier. For example, for the multiple-PDCCH based scheme, the terminal detects multiple DCIs on the same carrier (the existing protocol supports 2), where each DCI can schedule the corresponding PDSCH, and multiple PDSCHs are also on the same carrier.
[0049] This solution proposes an enhanced solution for PDCCH transmission for multi-TRP systems.
[0050] 3. Existing NR control channel solutions (R15, R16)
[0051] The network side indicates the transmission of PDCCH by configuring the control resource set (CORESET) and the search space (Search Space). It can be understood that the search space (Search Space) can also be called search space set. The control resource set includes multiple physical resource blocks in the frequency domain and 1 to 3 OFDM symbols in the time domain. The time domain resources occupied by CORESET are semi-statically configured by high-level parameters. The search space is a set of candidate PDCCHs (PDCCHcandidate) at one or more aggregation levels. The aggregation level of the PDCCH actually sent by the base station is determined by the base station. Since there is no relevant signaling to inform the UE, the UE needs to blindly detect the PDCCH at different aggregation levels, where the PDCCH to be blindly detected is called a candidate PDCCH. The UE will decode the candidate PDCCH in the search space. If the cyclic redundancy check (CRC) check passes, it is considered that the content of the decoded PDCCH is valid for the UE, and the information obtained by decoding is used for subsequent operations.
[0052] In NR, in each downlink bandwidth part (Bandwidth Part, BWP) of each serving cell, the network side can configure up to 10 search space sets for the user. The search space set is configured with time domain configuration information to indicate the time domain position of the user to detect the PDCCH. At the same time, the network side configures the set-associated CORESETID for each search space set. Through the CORESET ID, the user can obtain the physical resources of the search space set in the frequency domain. Each search space set has a uniquely associated CORESET ID. Different search space sets can be associated with the same CORESET ID. The UE determines the time and frequency domain position of the PDCCH candidate based on the time domain given by the search space set, the frequency domain of the associated CORESET ID, and other parameters in the search space set.
[0053] When configuring a CORESET, the network configures one or more TCI states for each CORESET. The TCIstate is used to indicate the relevant parameters required by the user for demodulation detection of the PDCCH candidate in the Search Space associated with the CORESET. When the network configures multiple TCI states for a CORESET, the network will activate a TCI state for the CORESET through MAC CE signaling to assist the UE in demodulating the PDCCH.
[0054] In addition, the network also configures an identifier (higher layer index) for each CORESET to indicate whether it is a high-level configuration of the same CORESET pool (i.e., CORESET pool index, the corresponding name in RRC is coresetPoolIndex). The value range is 0 and 1. In implementation, a CORESET pool can correspond to one TRP. For example, for CORESETs configured with the same higher layer index, the user believes that this is data from the same TRP. Note that the protocol can only see whether different CORESET pool indexes are associated, but the physical entity of the TRP cannot be seen.
[0055] 4. QCL quasi-co-location indication / assumption for downlink transmission
[0056] When receiving signals, the terminal can improve the reception performance by using the characteristics of the transmission environment corresponding to the data transmission to improve the reception algorithm. For example, the statistical characteristics of the channel can be used to optimize the design and parameters of the channel estimator. In the NR system, these characteristics corresponding to the data transmission are represented by the QCL state (QCL-Info).
[0057] If the downlink transmission comes from different TRP / panel / beam, the characteristics of the transmission environment corresponding to the data transmission may also change. Therefore, in the NR system, when the network side transmits the downlink control channel or data channel, it will indicate the corresponding QCL status information to the terminal through the TCI status.
[0058] 1. A TCI state can include the following configurations:
[0059] 1) TCI state ID, used to identify a TCI state;
[0060] 2) QCL information 1
[0061] 3) QCL information 2 (optional)
[0062] 2. Among them, a QCL information contains the following information:
[0063] 1) QCL type configuration, which can be one of QCL type-A, QCL-typeB, QCL-typeC or QCL-typeD;
[0064] 2) QCL reference signal configuration, including the cell ID where the reference signal is located, BWP ID and the identifier of the reference signal (which can be a CSI-RS resource ID or SSB index);
[0065] Among them, if QCL information 1 and QCL information 2 are both configured, the QCL type of at least one QCL information must be one of typeA, typeB, typeC, and the QCL type of the other QCL information (if configured) must be QCL type D.
[0066] Among them, the definitions of different QCL type configurations are as follows:
[0067] 'QCL-TypeA':{Doppler shift,Doppler spread,average delay,delay spread}
[0068] 'QCL-TypeB':{Doppler shift,Doppler spread}
[0069] 'QCL-TypeC':{Doppler shift,average delay}
[0070] 'QCL-TypeD':{Spatial Rx parameter}
[0071] The relevant configuration in the existing 38.331 is as follows:
[0072]
[0073] In the description of this article, QCL-TypeA, QCL-TypeB, QCL-TypeC, QCL-TypeD are often abbreviated as typeA, typeB, typeC, typeD.
[0074] In the NR system, the network side can indicate the corresponding TCI status for the downlink signal or downlink channel.
[0075] If the network side configures the QCL reference signal of the target downlink channel or the target downlink signal as a reference SSB or a reference CSI-RS resource through the TCI state, and the QCL type is configured as typeA, typeB or typeC, the terminal can assume that the large-scale parameters of the target downlink signal and the reference SSB or reference CSI-RS resource are the same, and the large-scale parameters are determined by the QCL type configuration.
[0076] Similarly, if the network side configures the QCL reference signal of the target downlink channel or downlink signal as a reference SSB or reference CSI-RS resource through the TCI state, and the QCL type is configured as typeD, the terminal can use the same spatial reception parameter (i.e., Spatial Rx parameter) as that for receiving the reference SSB or reference CSI-RS resource to receive the target downlink signal. Typically, the target downlink channel (or downlink signal) and its reference SSB or reference CSI-RS resource are sent by the same TRP, the same panel, or the same beam on the network side. If the transmission TRP, transmission panel, or transmission beam of two downlink signals or downlink channels are different, different TCI states are usually configured.
[0077] For the downlink control channel, the TCI status of the corresponding CORESET can be indicated by RRC signaling or RRC signaling + MAC signaling.
[0078] However, as mentioned above, for multi-TRP transmission, the NR Rel-16 protocol only supports the scheme of multiple TRPs simultaneously transmitting data to the UE, that is, it only supports the corresponding PDSCH multi-TRP enhancement scheme. Therefore, in Rel-17, the multi-TRP enhancement scheme of PDCCH will be studied. At present, 3GPP has had relevant discussions, but there is still a lack of complete detailed solutions. This application will provide a detailed implementation plan for specific details.
[0079] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobilecommunication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-based access to unlicensed spectrum, LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.
[0080] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device to device (Device to Device, D2D) communication, machine to machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), vehicle to vehicle (V2V) communication, or vehicle to everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.
[0081] Optionally, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario.
[0082] Optionally, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.
[0083] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
[0084] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.
[0085] In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.).
[0086] In the embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.
[0087] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.
[0088] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (EvolutionalNode B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network, or a network device in an NTN network, etc.
[0089] As an example but not limitation, in an embodiment of the present application, the network device may have a mobile characteristic, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.
[0090] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
[0091] like Figure 2 As shown, it is a system architecture diagram of a communication system applied in an embodiment of the present invention. The communication system may include a network device, which may be a device that communicates with a terminal device (or referred to as a communication terminal or terminal). The network device can provide communication coverage for a specific geographical area and can communicate with terminal devices located in the coverage area. Figure 2 An exemplary embodiment shows a network device and two terminal devices. Optionally, the communication system may include multiple network devices and each network device may include other number of terminal devices within its coverage area, which is not limited in the present embodiment. Optionally, the communication system may also include other network entities such as a network controller and a mobility management entity, which is not limited in the present embodiment.
[0092] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment may be an evolutionary base station (evolutional node B, referred to as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), micro-micro base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB) in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.
[0093] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 2 Taking the communication system shown as an example, the communication equipment may include network equipment and terminal equipment with communication functions. The network equipment and terminal equipment may be specific equipment described in the embodiments of the present invention, which will not be repeated here; the communication equipment may also include other equipment in the communication system, such as network controllers, mobile management entities and other network entities, which are not limited to the embodiments of the present application.
[0094] The technical solution of the present application is further described below by way of embodiments.
[0095] like Figure 3 As shown, it is a schematic diagram of an embodiment of a method for configuring a PDCCH in an embodiment of the present application, which may include:
[0096] 301. A first terminal device receives first configuration information sent by a first device, wherein the first configuration information indicates N first search spaces (Search space), and the corresponding physical downlink control channels PDCCH (or PDCCH candidates) in the N first search spaces are mutually associated, and / or the N first search spaces are mutually associated, and the N first search spaces correspond to PDCCH.
[0097] Wherein, N is an integer greater than or equal to 2, and can also be written as N≥2.
[0098] 1. Description of the first device:
[0099] Optionally, the first device may be a network device, that is, the corresponding network device communicates with the first terminal device. The first configuration information may be used for information transmission between the first terminal device and the network device, or may be used for information transmission between the first terminal device and other terminal devices.
[0100] Optionally, the first device is a second terminal device. The first configuration information may be determined by the second terminal device, or the second terminal device may receive configuration information sent from a network device and then send it to the first terminal device. That is, communication between terminals is supported, such as device-to-device (D2D), vehicle to X (V2X), sidelink communication, etc.
[0101] Optionally, the value of N is 2. Compared with N being greater than 2, the solution is simpler to implement and has lower complexity, and most of the gains of the multi-TRP transmission solution can be obtained.
[0102] It is understandable that if the N first search spaces are referred to as one group, then the first configuration information can configure multiple groups. For example, there are J groups, each group contains multiple first search spaces, and the PDCCH candidates corresponding to the multiple first search spaces in each group are associated with each other. The number of first search spaces contained in each group can be the same or different. The following description is based on one of the groups.
[0103] 2. Description of the first configuration information:
[0104] Optionally, each first search space corresponds to a first CORESET.
[0105] a. Optionally, the N first search spaces correspond to the same first CORESET, which can save CORESET configuration. Compared with b, it is not necessary to configure N CORESETs, but only one.
[0106] b. Optionally, the N first search spaces correspond to M different first CORESETs, where M≤N. Different CORESETs can come from different TRPs, making network implementation simpler. It should be noted that the solutions starting from c are all based on b (cannot be used with a).
[0107] Optionally, M=N is a preferred solution. Compared with the solution where M is greater than N, M=N is a one-to-one solution where N first search spaces correspond to M different first CORESETs, and the implementation method is the simplest.
[0108] c. Optionally, the activated transmission configuration indication states (TCI-States) corresponding to the M first CORESETs are configured with the same quasi-co-located QCL type. For example, the activated TCI-States corresponding to the M first CORESETs are all configured with QCL-TypeA, or are all configured with QCL-TypeA and QCL-TypeD, or are all configured with QCL-TypeD.
[0109] d. Optionally, the number of symbols corresponding to the M first CORESETs is the same, that is, they occupy the same number of orthogonal frequency division multiplexing (OFDM) symbols. The number of symbols corresponding to different CORESETs is the same, and the terminal device can use the same time domain filter structure to achieve reception, thereby reducing the implementation complexity of the terminal device. Otherwise, the terminal device needs to use different time domain filters to receive different CORESETs.
[0110] Optionally, the RRC parameter duration (duration) has the same value. It should be noted that the duration in CORESET and the duration in Search space are two different parameters.
[0111] e. Optionally, the M first CORESETs correspond to the same number of physical resource blocks (PRBs), that is, they occupy the same number of PRBs. Different CORESETs correspond to the same number of PRBs, and the terminal device can use a similar frequency domain filter structure to implement reception, thereby reducing the implementation complexity of the terminal device.
[0112] Optionally, the number of bits whose values are 1 in the RRC parameter frequency domain resources (frequencyDomainResources) is the same.
[0113] f. Optionally, the PRB positions corresponding to two first CORESETs in the M first CORESETs differ from each other by an offset. For example, one first CORESET occupies PRB n, n+1, and another first CORESET occupies PRB n+K, n+1+K. The number of PRBs corresponding to different CORESETs is the same, and the terminal device can use the same frequency domain filter structure to implement reception, thereby reducing the implementation complexity of the terminal device.
[0114] g. Optionally, the interleaving modes corresponding to the M first CORESETs are the same, or the interleaving part parameters corresponding to the M first CORESETs are the same. By adopting the same interleaving mode, the terminal device can use a similar deinterleaver to receive the PDCCH, thereby reducing the implementation complexity of the terminal device.
[0115] i. Optionally, none of the M first CORESETs adopts interleaving. If none of the M first CORESETs adopts interleaving, the terminal device can use the same receiver to receive the PDCCH, thereby reducing the implementation complexity of the terminal device.
[0116] Optionally, the M first CORESETs are all configured with RRC parameter non-interleaved.
[0117] ii. Optionally, the values of the RRC parameter interleaved configurations corresponding to the M first CORESETs are the same. Different first CORESETs use the same interleaving method, and the terminal device can use the same deinterleaver to receive the PDCCH, thereby reducing the implementation complexity of the terminal device.
[0118] iii. Optionally, the resource-element group (REG) bundle size (BundleSize) corresponding to the M first CORESETs is the same. Different first CORESETs use the same REG bundle size for interleaving, and the terminal device can use a similar deinterleaver to receive the PDCCH, thereby reducing the implementation complexity of the terminal device.
[0119] Optionally, the RRC parameter resource unit group set size (reg-BundleSize) configuration values corresponding to the M first CORESETs are the same.
[0120] iv. Optionally, the interleaver sizes corresponding to the M first CORESETs are the same. Different first CORESETs use interleavers of the same size for interleaving, and the terminal device can use a similar deinterleaver to receive the PDCCH, thereby reducing the implementation complexity of the terminal device.
[0121] Optionally, the values of RRC parameter interleaver size (interleaverSize) configurations corresponding to the M first CORESETs are the same.
[0122] v. Optionally, the interleaver offsets corresponding to the M first CORESETs are the same. Different first CORESETs use the same interleaver offset to perform interleaving, and the terminal device can use a similar deinterleaver to receive the PDCCH, thereby reducing the implementation complexity of the terminal device.
[0123] Optionally, the values of the RRC parameter shift indication (shiftIndex) configurations corresponding to the M first CORESETs are the same.
[0124] h. Optionally, the precoding granularity corresponding to the M first CORESETs is the same. Different first CORESETs use the same precoding granularity, and the terminal device can use a receiver with the same structure to receive the PDCCH, thereby reducing the implementation complexity of the terminal device.
[0125] Optionally, the values of the RRC parameter precoding granularity (precoderGranularity) configured for the M first CORESETs are the same
[0126] i. Optionally, neither the identifier of the RRC parameter CORESET pool corresponding to the M first CORESETs nor the index (coresetPoolIndex) of the CORESET pool is configured. Avoiding mixed use of multiple solutions can effectively reduce the complexity of signaling configuration and the implementation complexity of network devices and terminal devices.
[0127] It should be noted that the above-mentioned solution ci is implemented on the basis of solution b.
[0128] j. On the basis of any of the above (except i), optionally, the values corresponding to the RRC parameter coresetPoolIndex corresponding to the M first CORESETs are the same. A hybrid solution can support the joint use of multiple solutions, thereby providing greater freedom for network optimization. At the same time, the relevant parameters are restricted, thereby limiting the freedom to a certain extent, and achieving a good balance between freedom and complexity.
[0129] k. On any of the above bases (except i), optionally, the values corresponding to the RRC parameter coresetPoolIndex corresponding to the M first CORESETs are different. A hybrid solution can support the joint use of multiple solutions, thereby providing greater freedom for network optimization. Different coresetPoolIndex can correspond to different TRPs in actual network implementation.
[0130] 3. Description of the number of bits of the TCI indication field in the DCI corresponding to the N first search spaces:
[0131] Optionally, the N first search spaces correspond to the same number of bits in the TCI indication field in the DCI, that is, the same number of bits in the "Transmission Configuration Indication (TCI)" indication field. Keeping the associated multiple DCI related fields the same avoids wasting valid bits in a certain DCI.
[0132] a. The number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined according to the TCI indication field corresponding to the first search space with the smallest or largest first search space identifier (searchSpaceId).
[0133] The number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined according to the tci indication field corresponding to the first search space with the smallest or largest index in the first search space (the first search space with the smallest or largest identifier (searchSpaceId) in the first search space is recorded as the second search space). The first CORESET corresponding to different first search spaces can freely configure the information of the corresponding tci indication field, thereby maintaining the maximum freedom of network configuration, at the cost of introducing new rules, such as here determined according to the second search space.
[0134] i. Optionally, the number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined according to the tci-PresentInDCI field in the RRC parameters of the first CORESET corresponding to the second search space, including whether tci-PresentInDCI is configured as "enabled" or tci-PresentInDCI is not configured.
[0135] ii. Optionally, the number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined according to the tci-PresentDCI-1-2 field in the RRC parameters of the first CORESET corresponding to the second search space, including whether tci-PresentDCI-1-2 is configured as "enabled" or tci-PresentDCI-1-2 is not configured.
[0136] b. The number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined according to the tci indication field corresponding to the first search space at the front or the last position (the first search space at the front or the last position in the corresponding configuration or activation signaling is recorded as the third search space). The first CORESET corresponding to different first search spaces can freely configure the information of the corresponding tci indication field, thereby maintaining the maximum freedom of network configuration, at the cost of introducing new rules, such as here determined according to the third search space.
[0137] i. Optionally, the number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined according to the tci-PresentInDCI field in the RRC parameters of the first CORESET corresponding to the third search space, including that tci-PresentInDCI is configured as "enabled" or that tci-PresentInDCI is not configured.
[0138] ii. Optionally, the number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined according to the tci-PresentDCI-1-2 field in the RRC parameters of the first CORESET corresponding to the third search space, including whether tci-PresentDCI-1-2 is configured as "enabled" or tci-PresentDCI-1-2 is not configured.
[0139] c. Optionally, the tci-PresentInDCI in the RRC parameters corresponding to the M first CORESETs are configured with the same value, or are not configured. This is achieved through existing RRC parameter configuration, without the need to introduce additional rules for indication, thereby reducing the implementation complexity of the entire solution.
[0140] d. Optionally, the tci-PresentDCI-1-2 in the RRC parameters corresponding to the M first CORESETs are configured with the same value, or none of them are configured. This is achieved through the existing RRC parameter configuration, without the need to introduce additional rules to indicate, thereby reducing the implementation complexity of the entire solution.
[0141] e. The number of bits of the TCI indication field in the DCI corresponding to the M first CORESETs is determined according to the RRC parameter configuration in the first CORESET with the smallest or largest identifier (controlResourceSetId) in the first CORESET (the first CORESET with the smallest or largest identifier in the first CORESET is recorded as the second CORESET). Different CORESETs can be configured with different numbers of bits in the tci indication field, so that the DCI corresponding to the non-associated Search space can have a greater degree of freedom, avoiding all Search spaces corresponding to these CORESETs (including unassociated search spaces) using the same number of bits in the tci indication field, thereby maintaining maximum flexibility in network configuration.
[0142] i. Optionally, the number of bits of the TCI indication field in the DCI corresponding to the M first CORESETs is determined according to the tci-PresentInDCI field in the RRC parameters of the second CORESET, including that tci-PresentInDCI is configured as "enabled" or that tci-PresentInDCI is not configured.
[0143] ii. Optionally, the number of bits of the TCI indication field in the DCI corresponding to the M first CORESETs is determined according to the tci-PresentDCI-1-2 field in the RRC parameters of the second CORESET, including that tci-PresentDCI-1-2 is configured as "enabled" or that tci-PresentDCI-1-2 is not configured.
[0144] 4. Description of the number of PDCCH occasions corresponding to the N first search spaces in the same time slot:
[0145] Optionally, the N first search spaces correspond to the same number of PDCCH occasions (PDCCH occasions may also be referred to as PDCCH monitoring occasions) in the same time slot. This can reduce the complexity of network configuration and the complexity of terminal device implementation.
[0146] 5. Description of the corresponding values in the configuration values of the monitoring symbols in the RRC parameter time slots corresponding to the N first search spaces:
[0147] Optionally, the number of bits corresponding to the value of 1 in the configuration value of the monitoring symbols within the RRC parameter time slot (monitoringSymbolsWithinSlot) corresponding to the N first search spaces is the same. Limiting the relevant configuration of the associated search space can reduce the complexity of network configuration and the complexity of terminal device implementation.
[0148] Optionally, the bit positions corresponding to the value of 1 in the configuration value of the RRC parameter monitoringSymbolsWithinSlot corresponding to the N first search spaces are crossed, for example, appearing alternately. For example: Consider the case of two first search spaces, one first search space corresponds to "1" configured at positions #1 and #8, and the other first search space corresponds to "1" configured at positions #4 and #11. This configuration meets this requirement. If one first search space corresponds to "1" configured at positions #1 and #4, and the other first search space corresponds to "1" configured at positions #8 and #11, this configuration does not meet this requirement. For example, if a first search space needs to monitor PDCCH on two non-contiguous symbols in a slot, then the other N-1 first search spaces associated with it also need to monitor PDCCH on at least one symbol between the two symbols. Limiting the relevant configuration of the associated search space can reduce the complexity of network configuration and the complexity of terminal device implementation.
[0149] 6. Description of the span corresponding to one PDCCH monitoring occasion in one slot of the N first search spaces:
[0150] Optionally, the N first search spaces have the same span (the number of consecutive symbols, refer to the R16 version of protocols TS 38.213, TS 38.331, and TS 38.306) corresponding to a PDCCH monitoring occasion in a slot, wherein the relevant configuration of the PDCCH monitoring occasion corresponding to the associated search space is restricted, thereby reducing the complexity of network configuration and the complexity of terminal device implementation.
[0151] 7. The second device indicates, through RRC signaling, a description of the N first search spaces:
[0152] Optionally, the second device indicates through RRC signaling that the N first search spaces are associated.
[0153] a. Optionally, the same group identifier (groupid) is configured in the RRC parameters corresponding to the N first search spaces. By configuring the corresponding group id, a smaller RRC signaling overhead can be used to indicate the corresponding associated search space, thereby reducing the signaling overhead. See RRC Example 1 below.
[0154] i: optional. Group id can take different values. Search spaces with the same group id value are associated. For example, search spaces a and b correspond to group id x1, and search spaces c and d correspond to group id x2 (x1 and x2 are different). Search spaces a and b are associated with each other, and search spaces c and d are associated with each other.
[0155] ii: optional, group id value is 0, 1, …, K.
[0156] For example: K can be 0, 1, 2, 3, or 4.
[0157] iii: optional, group id value is 1, …, K.
[0158] For example: K can be 1, 2, 3, 4, or 5.
[0159] b. Optionally, at least one of the N first search spaces indicates other associated first search spaces. Advantage: Only part of the N associated first search spaces needs to be configured, so that a smaller RRC signaling overhead can be used to indicate the corresponding associated search space, thereby reducing the signaling overhead. See RRC Example 2 below.
[0160] c. Optionally, the second device configures multiple search space lists (search spacelist) through PDCCH-Config, and the search spaces at corresponding positions of different search space lists are related. Avoid modifying the existing searchspace configuration message and make the most of the existing signaling design, thereby reducing the workload of signaling design. See RRC Example 3 below. The solutions corresponding to the above three examples are parallel, that is, they belong to different options.
[0161] For example: list 1 contains 3 search spaces and list 2 contains 1 search space, then the first search space in list 1 is associated with the 1 search space in list 2; for another example: list 1 contains 3 search spaces and list 2 contains 2 search spaces, then the first search space in list 1 is associated with the first search space in list 2, and the second search space in list 1 is associated with the second search space in list 2.
[0162] 8. The second device indicates, through MAC CE signaling, a description of the N first search spaces:
[0163] Optionally, the second device indicates, through media access control control unit MAC CE signaling, that the N first search spaces are associated.
[0164] a. Optionally, the MAC CE indicates N first search spaces, and the N search spaces are associated. Each MAC CE indicates a group of associated search spaces, and signaling is simple to implement.
[0165] b. Optionally, the MAC CE indicates K first search spaces, where every N adjacent first search spaces are associated. For example, the MAC CE indicates 4 first search spaces, assuming N=2, where the first and second first search spaces are associated; the third and fourth first search spaces are associated; one MAC CE can indicate multiple groups of associated search spaces, which can save signaling overhead and improve system efficiency.
[0166] c. Optionally, the MAC CE indicates K first search spaces and the corresponding groups, and the first search spaces belonging to the same group are associated. The group is not necessarily explicitly visible, and can be represented by an identifier or number (not searchSpaceId, but another new identifier or number). One MAC CE can indicate multiple groups of associated search spaces, which can save signaling overhead and improve system efficiency.
[0167] Optionally, N may be a predefined default value or a value configured by the network device.
[0168] Optionally, the K first search spaces are indicated by indicating identifiers corresponding to the first search spaces. When the number of search spaces indicated by the MAC CE is small, the number of MAC signaling bits can be saved.
[0169] Optionally, the K first search spaces are indicated by a bitmap. When the number of search spaces indicated by the MAC CE is large, the number of MAC signaling bits can be saved.
[0170] 9. Description of the periods and time offsets corresponding to the N first search spaces:
[0171] Optionally, the N first search spaces correspond to the same period but different time offsets.
[0172] a. Optionally, the time offsets of the N first search spaces result in adjacent time slots, or the time offsets of the N first search spaces result in no downlink slots between corresponding slots, or the time offsets of the N first search spaces result in no flexible slots between corresponding slots. Now the associated PDDCH is in an adjacent downlink slot, which can reduce the PDCCH reception delay.
[0173] b. Optionally, the N first search spaces are associated with each other in the nth PDCCH occasion in the same period. Limiting the fixed association relationship can reduce the complexity of network configuration and the complexity of terminal implementation.
[0174] c. Optionally, the PDCCH occasion of the first search space X in slot n and the PDCCH occasion of the first search space Y in slot n', where slot n' is the first slot after slot n that has a PDCCH occasion corresponding to the first search space Y. Limiting the fixed association relationship can reduce the complexity of network configuration and the complexity of terminal implementation.
[0175] i. Optionally, the identifier of the first search space X (searchSpaceId) is smaller than the identifier of the first search space Y (searchSpaceId).
[0176] ii. Optionally, the identifier of the first search space X (searchSpaceId) is greater than the identifier of the first search space Y (searchSpaceId).
[0177] iii. Optionally, the identifier (controlResourceSetId) of the CORESET corresponding to the first search space X is smaller than the identifier (controlResourceSetId) of the CORESET corresponding to the first search space Y.
[0178] iv. Optionally, the identifier (controlResourceSetId) of the CORESET corresponding to the first search space X is greater than the identifier (controlResourceSetId) of the CORESET corresponding to the first search space Y.
[0179] v. Optionally, the time domain offset value corresponding to the first search space X is smaller than the time domain offset value corresponding to the first search space Y.
[0180] vi. Optionally, the time domain offset value corresponding to the first search space X is greater than the time domain offset value corresponding to the first search space Y.
[0181] vii. Optionally, each of the N first search spaces has only one PDCCH occasion in one slot. Restricting the relevant configuration of the associated search space reduces the complexity of buffering of the terminal, thereby reducing the implementation complexity of the terminal.
[0182] viii. Optionally, in the configuration value of the RRC parameter monitoringSymbolsWithinSlot corresponding to each of the N first search spaces, there is only one bit with a value of 1 (monitoringSymbolsWithinSlot is a bitmap structure (BIT STRING(SIZE(14))), which contains 14 symbols. If a bit at a certain position is set to 1, the symbol at the corresponding position in a slot is the start symbol of the PDCCH occasion). Restricting the relevant configuration of the associated search space reduces the complexity of buffering of the terminal device, thereby reducing the implementation complexity of the terminal device.
[0183] d. Optionally, the slots corresponding to the PDCCH occasions of the N first search spaces appear in an interleaved form. For example, N=2 first search spaces are associated as an example (respectively denoted as SS1 and SS2). Figure 4-1 This condition is met, such as Figure 4-2 This condition is not met, such as Figure 4-3 This condition may also be met. Restricting the configuration of the associated search space reduces the complexity of buffering of the terminal device, thereby reducing the implementation complexity of the terminal device.
[0184] e. Optionally, the PDCCH occasion X corresponding to the first search space X is associated with the PDCCH occasion Y of the first search space Y, wherein there is no other PDCCH occasion from the first search space X and the first search space Y between the PDCCH occasion X and the PDCCH occasion Y, and the PDCCH occasions corresponding to the two first search spaces. Taking N=2 as an example, the relevant configuration of the associated search space can be restricted to reduce the complexity of the buffer of the terminal device, thereby reducing the implementation complexity of the terminal device.
[0185] f. Optionally, the PDCCH occasion X corresponding to the first search space X is associated with the PDCCH occasion Y of the first search space Y, wherein the PDCCH occasion X and the PDCCH occasion Y do not contain one or more first slots, wherein one or more first slots contain the first search space X and the first search space Y, and the PDCCH occasions corresponding to the two first search spaces. Taking N=2 as an example, the relevant configuration of the associated search space can be restricted to reduce the complexity of buffering of the terminal device, thereby reducing the implementation complexity of the terminal device.
[0186] g. Optionally, the RRC parameter duration corresponding to the N first search spaces has a value of 1. Restricting the relevant configuration of the associated search space reduces the complexity of buffering of the terminal device, thereby reducing the implementation complexity of the terminal device.
[0187] 10. Description of the periods and time offsets corresponding to the N first search spaces:
[0188] Optionally, the N first search spaces have the same period and time offset, such as intra-slot PDCCH repetition, i.e., a DCI is transmitted from multiple TRPs in the same slot. The advantage is that the associated search space period and time offset are the same, which can reduce the complexity of network configuration and the complexity of terminal implementation.
[0189] a. Optionally, the RRC parameter monitoring slot periodicity and offset (monitoring Slot Periodicity And Offset) corresponding to the N first search spaces are configured with the same value.
[0190] b. Optionally, the maximum number of bits corresponding to the value of 1 in the configuration value of the RRC parameter monitoringSymbolsWithinSlot corresponding to each of the N first search spaces is 1. Limiting the relevant configuration of the associated search space can reduce the complexity of network configuration and the complexity of terminal implementation.
[0191] c. Optionally, the maximum number of bits with a value of 1 in the configuration value of the RRC parameter monitoringSymbolsWithinSlot corresponding to each of the N first search spaces is 2. Limiting the relevant configuration of the associated search space can reduce the complexity of network configuration and the complexity of terminal implementation.
[0192] 11. Description of the number of consecutive slots appearing in the N first search spaces within a cycle:
[0193] Optionally, the N first search spaces appear in the same number of consecutive slots in one cycle. The associated search spaces appear in the same number of slots, which can reduce the complexity of network configuration and the complexity of terminal implementation.
[0194] Optionally, the RRC parameter duration corresponding to the N first search spaces is configured with the same value, or the RRC parameter duration corresponding to the N first search spaces is not configured.
[0195] 12. Description of the DCI formats corresponding to the N first search spaces:
[0196] Optionally, the DCI formats (DCI formats) corresponding to the N first search spaces are the same. This can reduce the complexity of network configuration and the complexity of terminal implementation.
[0197] 13. Description of the aggregation level in the N first search spaces:
[0198] Optionally, PDCCH candidates with the same aggregation level L and equal numbers in the N first search spaces are associated with each other (for example, a PDCCH candidate with aggregation level L and numbered m in the first search space A is associated with a PDCCH candidate with aggregation level L and numbered m in the first search space B). The advantage is that the PDCCH candidates are associated through fixed rules, which can reduce signaling overhead and reduce the complexity of network and terminal implementation.
[0199] a. Optionally, the PDCCHs associated in the N first search spaces indicate the same information.
[0200] b. Optionally, the PDCCHs associated in the N first search spaces indicate the same physical downlink shared channel (PDSCH) scheduling.
[0201] i. Optionally, if the PDSCH scheduled by the first PDCCH and the first PDCCH are in the same slot, and the first PDCCH is not contained within the first three symbols of the slot, the first terminal device does not expect the PDSCH to adopt mapping type A (mapping type A) (the corresponding English expression can be: The UE is not expected to receive a PDSCH with mapping type A in a slot, if the first PDCCH scheduling the PDSCH was received in the same slot and was not contained within the first three symbols of the slot.), wherein the first PDCCH is the PDCCH with the latest ending position among the associated PDCCHs corresponding to the N first search spaces. Restrict related scheduling to reduce the complexity of terminal implementation.
[0202] ii. Optionally, if the symbol at the end of the first PDCCH is later than the starting symbol of the PDSCH scheduled by the first PDCCH, the first terminal device does not expect the PDSCH to adopt mapping type A (mapping type A) (the corresponding English expression can be: The UE is not expected to receive a PDSCH with mapping type B in aslot, if the first symbol of the first PDCCH scheduling the PDSCH was received in a later symbol than the first symbol indicated in the PDSCH time domain resource allocation.), where the first PDCCH is the PDCCH with the latest ending position among the associated PDCCHs corresponding to the N first search spaces. Restrict related scheduling to reduce the complexity of terminal implementation.
[0203] c. Optionally, the PDCCHs associated in the N first search spaces indicate the same physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) scheduling.
[0204] d. Optionally, the PDCCHs associated in the N first search spaces indicate the same channel state information CSI reporting.
[0205] e. Optionally, the PDCCHs associated in the N first search spaces indicate the same channel sounding reference signal (Sounding Reference Signal, SRS) transmission.
[0206] f. Optionally, the PDCCHs associated in the N first search spaces indicate the same physical random access channel (PRACH) transmission.
[0207] 14. Optionally, all or part of the N first search spaces are used to transmit the same DCI.
[0208] It can be understood that the same DCI can be understood as at least one of the following: indicating the same information, indicating the same PDSCH scheduling, indicating the same PUSCH scheduling, indicating the same CSI reporting, indicating the same SRS scheduling, indicating the same PDSCH scheduling, and indicating the same PRACH scheduling.
[0209] Optionally, the time-frequency resources of the same DCI when transmitted in different first search spaces do not completely overlap with each other. For example, the time domain resources of the same DCI when transmitted in two different first search spaces may have no overlap at all, or the frequency domain resources have no overlap at all, or the time-frequency resources have only partial overlap.
[0210] The bits obtained after channel coding of a DCI information are transmitted from part or all of the N first search spaces, or after channel coding of a DCI information, different redundancy revisions are transmitted from part or all of the N first search spaces. By repeatedly transmitting the same information from multiple first search spaces, the transmission reliability of the control channel is improved.
[0211] Optionally, the PDCCH transmitted in the N first search spaces.
[0212] It should be noted that, except for special instructions, the above-mentioned different implementation methods can be combined with each other to form a new solution, which is also within the scope of protection of this application and will not be described one by one here.
[0213] 302. The first terminal device receives the corresponding PDCCH according to the first configuration information.
[0214] Optionally, the PDCCH occasions corresponding to the N first search spaces are associated in the following manner (taking N=2 as an example), where the first first search space is in slot There is PDCCH occasion x, the second first search space is in slot There is a PDCCH occasion Y on the , PDCCH occasion X is associated with PDCCH Y, where the following conditions are met:
[0215]
[0216]
[0217] And the value of abs(e) is the smallest;
[0218] k s,0 ,O s,0 is the period and time domain offset of the first search space, k s,1 ,O s,1 is the period and time domain offset of the second first search space, Indicates the number of slots in a frame, n f is the frame number, Table and It represents the number of the slot in a frame, and μ represents the corresponding numerology (basic parameter set parameter).
[0219] Optional, O s,0 <O s,1 .
[0220] In the technical solution provided by the embodiment of the present invention, a first terminal device receives first configuration information sent by a first device, wherein the first configuration information indicates N first search spaces, the physical downlink control channels PDCCH corresponding to the N first search spaces are mutually associated, and / or the N first search spaces are mutually associated, and N is an integer greater than or equal to 2. Used to implement multi-TRP enhancement of PDCCH.
[0221] (1) RRC Example 1
[0222] Based on the existing RRC parameters, corresponding modifications are made, and the modified parts are marked in bold. In the example, the newly added field name is only used for example, and other names can be used. In addition, the location of the newly added field is also only used for example and can be changed. The following examples will not be repeated. In addition, in general examples, two search spaces are associated as an example, and the association of more search spaces can be obtained in a similar way.
[0223] Example 1-1: Adding a new field to the SearchSpace
[0224]
[0225]
[0226] A new optional field is added, marked with GroupID, whose value is an integer (starting from 0 or 1). If the values corresponding to GroupID in two search spaces are the same, the two search spaces are associated with each other.
[0227] Example 1-2: Adding a new field to SearchSpaceExt
[0228]
[0229]
[0230] A new optional field is added, marked with GroupID, whose value is an integer (starting from 0 or 1). If the values corresponding to GroupID in two search spaces are the same, the two search spaces are associated with each other.
[0231] (2) RRC Example 2
[0232] Example 2-1: Adding a new field to the SearchSpace
[0233]
[0234]
[0235]
[0236] A new optional field is added, labeled linkedSearchSpace, which indicates the search space (can be one or more) to which this search space is associated. Optionally, its value can be the identifier of one or more search spaces. For example, if the linkedSearchSpace of search space X corresponds to search space Y, or the searchSpaceId of search space Y, then the two search spaces X and Y are associated with each other.
[0237] Example 2-2: Adding a new field to SearchSpaceExt
[0238]
[0239]
[0240] A new optional field is added, labeled linkedSearchSpace, which indicates the search space (can be one or more) to which this search space is associated. Optionally, its value can be the identifier of one or more search spaces. For example, if the linkedSearchSpace of search space X corresponds to search space Y, or the searchSpaceId of search space Y, then the two search spaces X and Y are associated with each other.
[0241] (3) RRC Example 3
[0242] Add new fields to SearchSpaceExt
[0243]
[0244]
[0245] A new optional field is added, labeled searchSpaceListZ, which indicates one or more search spaces.
[0246] The nth search space in searchSpacesToAddModList is associated with the nth search space in searchSpaceListZ
[0247] The nth search space in searchSpacesToAddModListExt-r16 is associated with the nth search space in searchSpaceListZ.
[0248] like Figure 5 As shown, it is a schematic diagram of an embodiment of a terminal device in an embodiment of the present application, which may include:
[0249] The transceiver module 501 is used to receive first configuration information sent by a first device, where the first configuration information indicates N first search spaces, where the physical downlink control channels PDCCH corresponding to the N first search spaces are mutually associated, and / or the N first search spaces are mutually associated, where the N first search spaces correspond to PDCCH, and N is an integer greater than or equal to 2.
[0250] Optionally, each of the first search spaces corresponds to a control resource set CORESET.
[0251] Optionally, the N first search spaces correspond to M different first CORESETs, where M≤N.
[0252] Optionally, the activated transmission configuration indication state TCI-State corresponding to the M first CORESETs are configured with the same quasi-co-site QCL type.
[0253] Optionally, the number of symbols corresponding to the M first CORESETs is the same.
[0254] Optionally, physical resource block (PRB) positions corresponding to two first CORESETs among the M first CORESETs differ from each other by an offset.
[0255] Optionally, the number of physical resource blocks PRBs corresponding to the M first CORESETs is the same.
[0256] Optionally, the interleaving modes corresponding to the M first CORESETs are the same, or the interleaving part parameters corresponding to the M first CORESETs are the same.
[0257] Optionally, the values of the radio resource control RRC parameter interleaved configurations corresponding to the M first CORESETs are the same.
[0258] Optionally, the M first CORESETs do not adopt interleaving.
[0259] Optionally, the resource unit group sets corresponding to the M first CORESETs are of the same size.
[0260] Optionally, the values configured for the RRC parameter resource unit group set size reg-BundleSize corresponding to the M first CORESETs are the same.
[0261] Optionally, the interleaver sizes corresponding to the M first CORESETs have the same value.
[0262] Optionally, the values of the RRC parameter interleaver size interleaverSize configured corresponding to the M first CORESETs are the same.
[0263] Optionally, the interleaver offsets corresponding to the M first CORESETs are the same.
[0264] Optionally, the RRC parameter offset indication shiftIndex configuration values corresponding to the M first CORESETs are the same.
[0265] Optionally, the identifier coresetPoolIndex of the RRC parameter CORESET pool corresponding to the M first CORESETs is not configured; or,
[0266] The values corresponding to the RRC parameter coresetPoolIndex corresponding to the M first CORESETs are the same or different.
[0267] Optionally, the precoding granularities corresponding to the M first CORESETs are the same.
[0268] Optionally, the values of RRC parameter precoding granularity precoderGranularity configurations corresponding to the M first CORESETs are the same.
[0269] Optionally, the N first search spaces correspond to the same first CORESET.
[0270] Optionally, the first device is a network device or a second terminal device.
[0271] Optionally, the N first search spaces correspond to the same number of bits in the TCI indication field in the downlink control information DCI.
[0272] Optionally, the number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined based on the TCI indication field corresponding to the first search space with the smallest or largest identifier of the first search space.
[0273] Optionally, the number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined based on the tci-PresentInDCI field or the tci-PresentDCI-1-2 field in the RRC parameters of the first CORESET corresponding to the second search space, and the second search space is the first search space with the minimum or maximum identifier of the first search space.
[0274] Optionally, the number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined according to the TCI indication field corresponding to the first search space that is the first or last in the corresponding configuration or activation signaling.
[0275] Optionally, the number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined based on the tci-PresentInDCI field, or the tci-PresentDCI-1-2 field in the RRC parameters of the first CORESET corresponding to the third search space, and the third search space is the first search space that is the frontmost or last in the corresponding configuration or activation signaling.
[0276] Optionally, the tci-PresentInDCI or tci-PresentDCI-1-2 in the RRC parameters corresponding to the M first CORESETs are configured with the same value, or are not configured.
[0277] Optionally, the number of bits of the TCI indication field in the DCI corresponding to the M first CORESETs is determined according to the RRC parameter configuration in the first CORESET that identifies the minimum or maximum in the first CORESET.
[0278] Optionally, the number of bits of the TCI indication field in the DCI corresponding to the M first CORESETs is determined based on the tci-PresentInDCI or tci-PresentDCI-1-2 field in the RRC parameters of the second CORESET, and the second CORESET is the first CORESET with the smallest or largest identifier in the first CORESET.
[0279] Optionally, the N first search spaces correspond to the same number of PDCCH occasions in the same time slot.
[0280] Optionally, the number of bits corresponding to the value of 1 in the configuration value of the RRC parameter monitoring symbols within slots monitoringSymbolsWithinSlot corresponding to the N first search spaces is the same.
[0281] Optionally, the bit positions corresponding to the values of 1 in the configuration value of the RRC parameter monitoringSymbolsWithinSlot corresponding to the N first search spaces are crossed.
[0282] Optionally, the N first search spaces have the same number of consecutive symbols span corresponding to a PDCCH monitoring occasion in a time slot.
[0283] Optionally, the first device indicates through RRC signaling that the N first search spaces are associated.
[0284] Optionally, the same group identifier group id is configured in the RRC parameters corresponding to the N first search spaces; or,
[0285] At least one of the N first search spaces indicates other associated first search spaces; or,
[0286] The first device is configured with multiple search space lists through PDCCH Config, and search spaces at corresponding positions of different search space lists are associated.
[0287] Optionally, the first device indicates, through media access control control unit MAC CE signaling, that the N first search spaces are associated.
[0288] Optionally, the MAC CE indicates N first search spaces, and the N search spaces are associated; or,
[0289] The MAC CE indicates K first search spaces, wherein adjacent N first search spaces are associated, K≥N; or,
[0290] The MAC CE indicates K first search spaces and corresponding groups, and the first search spaces belonging to the same group are associated.
[0291] Optionally, the N first search spaces correspond to the same period but different time offsets.
[0292] Optionally, the time offsets of the N first search spaces cause the slots to be adjacent, or the time offsets of the N first search spaces cause the corresponding slots to no longer be separated by downlink slots, or the time offsets of the N first search spaces cause the corresponding slots to no longer be separated by flexible time slots; or,
[0293] The N first search spaces are associated with each other between their respective n-th PDCCH occasions PDCCH occasions in the same period.
[0294] Optionally, the PDCCH occasion of the first search space X in slot n and the PDCCH occasion of the first search space Y in slot n', wherein slot n' is the first slot after slot n that has a PDCCH occasion corresponding to the first search space Y.
[0295] Optionally, the identifier of the first search space X is smaller than the identifier of the first search space Y; or,
[0296] The identifier of the first search space X is greater than the identifier of the first search space Y; or,
[0297] The identifier of the CORESET corresponding to the first search space X is smaller than the identifier of the CORESET corresponding to the first search space Y; or,
[0298] The identifier of the CORESET corresponding to the first search space X is greater than the identifier of the CORESET corresponding to the first search space Y; or,
[0299] The time domain offset value corresponding to the first search space X is smaller than the time domain offset value corresponding to the first search space Y; or,
[0300] The time domain offset value corresponding to the first search space X is greater than the time domain offset value corresponding to the first search space Y; or,
[0301] Each of the N first search spaces has only one PDCCHoccasion in one slot; or,
[0302] There is one bit with a value of 1 in the configuration value of the RRC parameter monitoringSymbolsWithinSlot corresponding to each first search space in the N first search spaces.
[0303] Optionally, the slots where the PDCCH occasions corresponding to the N first search spaces appear are in a cross form; or,
[0304] A PDCCH occasion X corresponding to a first search space X is associated with a PDCCH occasion Y corresponding to a first search space Y, wherein there is no other PDCCH occasion from the first search space X and the first search space Y between the PDCCH occasion X and the PDCCH occasion Y; or,
[0305] A PDCCH occasion X corresponding to a first search space X is associated with a PDCCH occasion Y corresponding to a first search space Y, wherein the PDCCH occasion X and the PDCCH occasion Y do not contain one or more first slots, wherein the one or more first slots contain the PDCCH occasion corresponding to the first search space X and the first search space Y; or,
[0306] The RRC parameter duration corresponding to the N first search spaces takes a value of 1.
[0307] Optionally, the periods and time offsets corresponding to the N first search spaces are the same.
[0308] Optionally, the period and offset monitoringSlotPeriodicityAndOffset of the RRC parameter monitoring slot corresponding to the N first search spaces are configured with the same value; and / or,
[0309] The maximum number of times that the bit value corresponding to 1 in the configuration value of the RRC parameter monitoringSymbolsWithinSlot corresponding to each first search space in the N first search spaces is 1; and / or,
[0310] The maximum number of times that the bit value corresponding to 1 in the configuration value of the RRC parameter monitoringSymbolsWithinSlot corresponding to each first search space in the N first search spaces is 2.
[0311] Optionally, the number of consecutive slots appearing in the N first search spaces within a cycle is the same.
[0312] Optionally, the RRC parameter duration corresponding to the N first search spaces is configured with the same value, or the RRC parameter duration corresponding to the N first search spaces is not configured.
[0313] Optionally, the DCI formats corresponding to the N first search spaces are the same.
[0314] Optionally, PDCCH candidates with the same aggregation level L and equal numbers in the N first search spaces are associated with each other.
[0315] Optionally, the PDCCHs associated in the N first search spaces indicate the same information; and / or,
[0316] The PDCCHs associated with the N first search spaces indicate the same physical downlink shared channel PDSCH scheduling; and / or,
[0317] The PDCCHs associated with the N first search spaces indicate the same physical uplink shared channel PUSCH scheduling; and / or,
[0318] The PDCCHs associated with the N first search spaces indicate the same channel state information CSI reporting; and / or,
[0319] The PDCCHs associated with the N first search spaces indicate the same channel sounding reference signal SRS transmission; and / or,
[0320] The PDCCHs associated with the N first search spaces indicate the same physical random access channel PRACH transmission.
[0321] Optionally, all or part of the N first search spaces are used to transmit the same DCI.
[0322] Corresponding to the method of at least one embodiment applied to a terminal device, the embodiment of the present application also provides one or more terminal devices. The terminal device of the embodiment of the present application can implement any one of the implementation modes of the above method. Figure 6 As shown, it is a schematic diagram of another embodiment of a terminal device in an embodiment of the present invention. The terminal device is described by taking a mobile phone as an example, and may include: a radio frequency (RF) circuit 610, a memory 620, an input unit 630, a display unit 640, a sensor 650, an audio circuit 660, a wireless fidelity (WiFi) module 670, a processor 680, and a power supply 690. Among them, the RF circuit 610 includes a receiver 614 and a transmitter 612. Those skilled in the art can understand that Figure 6 The mobile phone structure shown in the figure does not constitute a limitation on the mobile phone, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.
[0323] Combine the following Figure 6 A detailed introduction to the various components of the mobile phone:
[0324] The RF circuit 610 can be used for receiving and sending signals during information transmission or calls. In particular, after receiving the downlink information of the base station, it is sent to the processor 680 for processing; in addition, the designed uplink data is sent to the base station. Generally, the RF circuit 610 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (LNA), a duplexer, etc. In addition, the RF circuit 610 can also communicate with the network and other devices through wireless communication. The above wireless communication can use any communication standard or protocol, including but not limited to the global system of mobile communication (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), long term evolution (LTE), email, short messaging service (SMS), etc.
[0325] The memory 620 can be used to store software programs and modules. The processor 680 executes various functional applications and data processing of the mobile phone by running the software programs and modules stored in the memory 620. The memory 620 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory 620 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.
[0326] The input unit 630 can be used to receive input digital or character information, and to generate key signal input related to the user settings and function control of the mobile phone. Specifically, the input unit 630 may include a touch panel 631 and other input devices 632. The touch panel 631, also known as a touch screen, can collect the user's touch operation on or near it (such as the user's operation on the touch panel 631 or near the touch panel 631 using any suitable object or accessory such as a finger, stylus, etc.), and drive the corresponding connection device according to a pre-set program. Optionally, the touch panel 631 may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it to the processor 680, and can receive and execute commands sent by the processor 680. In addition, the touch panel 631 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 631, the input unit 630 may also include other input devices 632. Specifically, the other input devices 632 may include but are not limited to one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, etc.
[0327] The display unit 640 can be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 640 may include a display panel 641. Optionally, the display panel 641 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc. Further, the touch panel 631 may cover the display panel 641. When the touch panel 631 detects a touch operation on or near it, it is transmitted to the processor 680 to determine the type of touch event. Subsequently, the processor 680 provides a corresponding visual output on the display panel 641 according to the type of touch event. Although in Figure 6 In the embodiment, the touch panel 631 and the display panel 641 are used as two independent components to realize the input and output functions of the mobile phone, but in some embodiments, the touch panel 631 and the display panel 641 can be integrated to realize the input and output functions of the mobile phone.
[0328] The mobile phone may also include at least one sensor 650, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 641 according to the brightness of the ambient light, and the proximity sensor may turn off the display panel 641 and / or the backlight when the mobile phone is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that identify the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that can be configured in the mobile phone, such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be repeated here.
[0329] The audio circuit 660, the speaker 661, and the microphone 662 can provide an audio interface between the user and the mobile phone. The audio circuit 660 can transmit the received audio data to the speaker 661 after converting the received audio data into an electrical signal, which is converted into a sound signal for output; on the other hand, the microphone 662 converts the collected sound signal into an electrical signal, which is received by the audio circuit 660 and converted into audio data, and then the audio data is output to the processor 680 for processing, and then sent to another mobile phone through the RF circuit 610, or the audio data is output to the memory 620 for further processing.
[0330] WiFi is a short-range wireless transmission technology. The mobile phone can help users send and receive emails, browse web pages and access streaming media through the WiFi module 670. It provides users with wireless broadband Internet access. Figure 6 A WiFi module 660 is shown, but it is understandable that it is not an essential component of the mobile phone and can be omitted as needed without changing the essence of the invention.
[0331] The processor 680 is the control center of the mobile phone. It uses various interfaces and lines to connect various parts of the entire mobile phone. By running or executing software programs and / or modules stored in the memory 620, and calling data stored in the memory 620, it executes various functions of the mobile phone and processes data, thereby monitoring the mobile phone as a whole. Optionally, the processor 680 may include one or more processing units; preferably, the processor 680 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 680.
[0332] The mobile phone also includes a power supply 690 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 680 through a power management system, so that the power management system can manage charging, discharging, power consumption management, etc. Although not shown, the mobile phone can also include a camera, a Bluetooth module, etc., which will not be described in detail here.
[0333] In an embodiment of the present invention, the RF circuit 610 is used to receive first configuration information sent by a first device, wherein the first configuration information indicates N first search spaces, and the physical downlink control channels PDCCH corresponding to the N first search spaces are mutually associated, and / or the N first search spaces are mutually associated, and the N first search spaces correspond to PDCCH, where N is an integer greater than or equal to 2.
[0334] Optionally, each of the first search spaces corresponds to a control resource set CORESET.
[0335] Optionally, the N first search spaces correspond to M different first CORESETs, where M≤N.
[0336] Optionally, the activated transmission configuration indication state TCI-State corresponding to the M first CORESETs are configured with the same quasi-co-site QCL type.
[0337] Optionally, the number of symbols corresponding to the M first CORESETs is the same.
[0338] Optionally, physical resource block (PRB) positions corresponding to two first CORESETs among the M first CORESETs differ from each other by an offset.
[0339] Optionally, the number of physical resource blocks PRBs corresponding to the M first CORESETs is the same.
[0340] Optionally, the interleaving modes corresponding to the M first CORESETs are the same, or the interleaving part parameters corresponding to the M first CORESETs are the same.
[0341] Optionally, the values of radio resource control RRC parameter interleaved configurations corresponding to the M first CORESETs are the same.
[0342] Optionally, the M first CORESETs do not adopt interleaving.
[0343] Optionally, the resource unit group sets corresponding to the M first CORESETs are of the same size.
[0344] Optionally, the values configured for the RRC parameter resource unit group set size reg-BundleSize corresponding to the M first CORESETs are the same.
[0345] Optionally, the interleaver sizes corresponding to the M first CORESETs have the same value.
[0346] Optionally, the values of the RRC parameter interleaver size interleaverSize configured corresponding to the M first CORESETs are the same.
[0347] Optionally, the interleaver offsets corresponding to the M first CORESETs are the same.
[0348] Optionally, the RRC parameter offset indication shiftIndex configuration values corresponding to the M first CORESETs are the same.
[0349] Optionally, the identifier coresetPoolIndex of the RRC parameter CORESET pool corresponding to the M first CORESETs is not configured; or,
[0350] The values corresponding to the RRC parameter coresetPoolIndex corresponding to the M first CORESETs are the same or different.
[0351] Optionally, the precoding granularities corresponding to the M first CORESETs are the same.
[0352] Optionally, the values of RRC parameter precoding granularity precoderGranularity configurations corresponding to the M first CORESETs are the same.
[0353] Optionally, the N first search spaces correspond to the same first CORESET.
[0354] Optionally, the first device is a network device or a second terminal device.
[0355] Optionally, the N first search spaces correspond to the same number of bits in the TCI indication field in the downlink control information DCI.
[0356] Optionally, the number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined based on the TCI indication field corresponding to the first search space with the smallest or largest identifier of the first search space.
[0357] Optionally, the number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined based on the tci-PresentInDCI field or the tci-PresentDCI-1-2 field in the RRC parameters of the first CORESET corresponding to the second search space, and the second search space is the first search space with the minimum or maximum identifier of the first search space.
[0358] Optionally, the number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined according to the TCI indication field corresponding to the first search space that is the first or last in the corresponding configuration or activation signaling.
[0359] Optionally, the number of bits of the TCI indication field in the DCI corresponding to the N first search spaces is determined based on the tci-PresentInDCI field, or the tci-PresentDCI-1-2 field in the RRC parameters of the first CORESET corresponding to the third search space, and the third search space is the first search space that is the frontmost or last in the corresponding configuration or activation signaling.
[0360] Optionally, the tci-PresentInDCI or tci-PresentDCI-1-2 in the RRC parameters corresponding to the M first CORESETs are configured with the same value, or are not configured.
[0361] Optionally, the number of bits of the TCI indication field in the DCI corresponding to the M first CORESETs is determined according to the RRC parameter configuration in the first CORESET that identifies the minimum or maximum in the first CORESET.
[0362] Optionally, the number of bits of the TCI indication field in the DCI corresponding to the M first CORESETs is determined based on the tci-PresentInDCI or tci-PresentDCI-1-2 field in the RRC parameters of the second CORESET, and the second CORESET is the first CORESET with the smallest or largest identifier in the first CORESET.
[0363] Optionally, the N first search spaces correspond to the same number of PDCCH occasions in the same time slot.
[0364] Optionally, the number of bits corresponding to the value of 1 in the configuration value of the RRC parameter monitoring symbols within slots monitoringSymbolsWithinSlot corresponding to the N first search spaces is the same.
[0365] Optionally, the bit positions corresponding to the values of 1 in the configuration value of the RRC parameter monitoringSymbolsWithinSlot corresponding to the N first search spaces are crossed.
[0366] Optionally, the N first search spaces have the same number of consecutive symbols span corresponding to a PDCCH monitoring occasion in a time slot.
[0367] Optionally, the first device indicates through RRC signaling that the N first search spaces are associated.
[0368] Optionally, the same group identifier group id is configured in the RRC parameters corresponding to the N first search spaces; or,
[0369] At least one of the N first search spaces indicates other associated first search spaces; or,
[0370] The first device is configured with multiple search space lists through PDCCH Config, and search spaces at corresponding positions of different search space lists are associated.
[0371] Optionally, the first device indicates, through media access control control unit MAC CE signaling, that the N first search spaces are associated.
[0372] Optionally, the MAC CE indicates N first search spaces, and the N search spaces are associated; or,
[0373] The MAC CE indicates K first search spaces, wherein adjacent N first search spaces are associated, K≥N; or,
[0374] The MAC CE indicates K first search spaces and corresponding groups, and the first search spaces belonging to the same group are associated.
[0375] Optionally, the N first search spaces correspond to the same period but different time offsets.
[0376] Optionally, the time offsets of the N first search spaces cause the slots to be adjacent, or the time offsets of the N first search spaces cause the corresponding slots to no longer be separated by downlink slots, or the time offsets of the N first search spaces cause the corresponding slots to no longer be separated by flexible time slots; or,
[0377] The N first search spaces are associated with each other between their respective n-th PDCCH occasions PDCCH occasions in the same period.
[0378] Optionally, the PDCCH occasion of the first search space X in slot n and the PDCCH occasion of the first search space Y in slot n', wherein slot n' is the first slot after slot n that has a PDCCH occasion corresponding to the first search space Y.
[0379] Optionally, the identifier of the first search space X is smaller than the identifier of the first search space Y; or,
[0380] The identifier of the first search space X is greater than the identifier of the first search space Y; or,
[0381] The identifier of the CORESET corresponding to the first search space X is smaller than the identifier of the CORESET corresponding to the first search space Y; or,
[0382] The identifier of the CORESET corresponding to the first search space X is greater than the identifier of the CORESET corresponding to the first search space Y; or,
[0383] The time domain offset value corresponding to the first search space X is smaller than the time domain offset value corresponding to the first search space Y; or,
[0384] The time domain offset value corresponding to the first search space X is greater than the time domain offset value corresponding to the first search space Y; or,
[0385] Each of the N first search spaces has only one PDCCHoccasion in one slot; or,
[0386] There is one bit with a value of 1 in the configuration value of the RRC parameter monitoringSymbolsWithinSlot corresponding to each first search space in the N first search spaces.
[0387] Optionally, the slots where the PDCCH occasions corresponding to the N first search spaces appear are in a cross form; or,
[0388] A PDCCH occasion X corresponding to a first search space X is associated with a PDCCH occasion Y corresponding to a first search space Y, wherein there is no other PDCCH occasion from the first search space X and the first search space Y between the PDCCH occasion X and the PDCCH occasion Y; or,
[0389] A PDCCH occasion X corresponding to a first search space X is associated with a PDCCH occasion Y corresponding to a first search space Y, wherein the PDCCH occasion X and the PDCCH occasion Y do not contain one or more first slots, wherein the one or more first slots contain the PDCCH occasion corresponding to the first search space X and the first search space Y; or,
[0390] The RRC parameter duration corresponding to the N first search spaces takes a value of 1.
[0391] Optionally, the periods and time offsets corresponding to the N first search spaces are the same.
[0392] Optionally, the period and offset monitoringSlotPeriodicityAndOffset of the RRC parameter monitoring slot corresponding to the N first search spaces are configured with the same value; and / or,
[0393] The maximum number of times that the bit value corresponding to 1 in the configuration value of the RRC parameter monitoringSymbolsWithinSlot corresponding to each first search space in the N first search spaces is 1; and / or,
[0394] The maximum number of times that the bit value corresponding to 1 in the configuration value of the RRC parameter monitoringSymbolsWithinSlot corresponding to each first search space in the N first search spaces is 2.
[0395] Optionally, the number of consecutive slots appearing in the N first search spaces within a cycle is the same.
[0396] Optionally, the RRC parameter duration corresponding to the N first search spaces is configured with the same value, or the RRC parameter duration corresponding to the N first search spaces is not configured.
[0397] Optionally, the DCI formats corresponding to the N first search spaces are the same.
[0398] Optionally, PDCCH candidates with the same aggregation level L and equal numbers in the N first search spaces are associated with each other.
[0399] Optionally, the PDCCHs associated in the N first search spaces indicate the same information; and / or,
[0400] The PDCCHs associated with the N first search spaces indicate the same physical downlink shared channel PDSCH scheduling; and / or,
[0401] The PDCCHs associated with the N first search spaces indicate the same physical uplink shared channel PUSCH scheduling; and / or,
[0402] The PDCCHs associated with the N first search spaces indicate the same channel state information CSI reporting; and / or,
[0403] The PDCCHs associated with the N first search spaces indicate the same channel sounding reference signal SRS transmission; and / or,
[0404] The PDCCHs associated with the N first search spaces indicate the same physical random access channel PRACH transmission.
[0405] Optionally, all or part of the N first search spaces are used to transmit the same DCI.
[0406] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present invention is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk Solid State Disk (SSD)), etc.
[0407] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
Claims
1. A method for PDCCH configuration, characterized in that: include: The first terminal device receives first configuration information sent by the network device through radio resource control RRC signaling, where the first configuration information indicates N first search spaces, the N first search spaces are associated with each other, the N first search spaces correspond to PDCCH, N is an integer greater than or equal to 2; each of the first search spaces corresponds to a control resource set CORESET; the N first search spaces correspond to M different first CORESETs, where M≤N; The identifier coresetPoolIndex of the RRC parameter CORESET pool corresponding to the M first CORESETs is not configured; or, the values corresponding to the RRC parameter coresetPoolIndex corresponding to the M first CORESETs are the same.
2. The method according to claim 1, characterized in that The M first CORESETs satisfy one or more of the following: The activated transmission configuration indication states TCI-State corresponding to the M first CORESETs are configured with the same quasi-co-location QCL type; The number of symbols corresponding to the M first CORESETs is the same; The physical resource block (PRB) positions corresponding to two first CORESETs in the M first CORESETs differ from each other by an offset; The number of physical resource blocks (PRBs) corresponding to the M first CORESETs is the same; The interleaving modes corresponding to the M first CORESETs are the same, or the interleaving part parameters corresponding to the M first CORESETs are the same; or the M first CORESETs do not use interleaving; The resource unit group sets corresponding to the M first CORESETs have the same size; The values of the interleaver sizes corresponding to the M first CORESETs are the same; The interleaver offsets corresponding to the M first CORESETs are the same; The precoding granularities corresponding to the M first CORESETs are the same.
3. The method according to claim 1, characterized in that The N first search spaces correspond to the same first CORESET.
4. The method according to any one of claims 1 to 3, characterized in that The N first search spaces satisfy one or more of the following: The N first search spaces correspond to the same number of bits in the TCI indication field in the downlink control information DCI; The N first search spaces correspond to the same number of PDCCH occasions in the same time slot; The number of bits corresponding to the value of 1 in the configuration value of the RRC parameter monitoring symbol within the time slot monitoringSymbolsWithinSlot corresponding to the N first search spaces is the same; The N first search spaces have the same span as the number of consecutive symbols corresponding to a PDCCH monitoring occasion in a time slot; The N first search spaces correspond to the same period but different time offsets; or, the N first search spaces correspond to the same period and time offset; The number of consecutive slots appearing in the N first search spaces in one cycle is the same; The DCI formats corresponding to the N first search spaces are the same; The PDCCH candidates with the same aggregation level L and the same number in the N first search spaces are associated with each other; The PDCCHs associated with the N first search spaces indicate the same information; The PDCCHs associated with the N first search spaces indicate the same physical downlink shared channel PDSCH scheduling; The PDCCHs associated with the N first search spaces indicate the same physical uplink shared channel PUSCH scheduling; The PDCCHs associated with the N first search spaces indicate the same channel state information CSI reporting; The PDCCHs associated with the N first search spaces indicate the same channel sounding reference signal SRS transmission; The PDCCHs associated with the N first search spaces indicate the same physical random access channel PRACH transmission; All or part of the N first search spaces are used to transmit the same DCI.
5. A terminal device, characterized in that: include: A memory storing executable program code; a transceiver coupled to the memory; The transceiver is configured to receive first configuration information sent by a network device through RRC signaling, wherein the first configuration information indicates N first search spaces, the N first search spaces are associated with each other, the N first search spaces correspond to PDCCH, and N is an integer greater than or equal to 2; each of the first search spaces corresponds to a control resource set CORESET; the N first search spaces correspond to M different first CORESETs, where M≤N; The identifier coresetPoolIndex of the RRC parameter CORESET pool corresponding to the M first CORESETs is not configured; or, the values corresponding to the RRC parameter coresetPoolIndex corresponding to the M first CORESETs are the same.
6. The terminal device according to claim 5, characterized in that: The M first CORESETs satisfy one or more of the following: The activated transmission configuration indication states TCI-State corresponding to the M first CORESETs are configured with the same quasi-co-location QCL type; The number of symbols corresponding to the M first CORESETs is the same; The physical resource block (PRB) positions corresponding to two first CORESETs in the M first CORESETs differ from each other by an offset; The number of physical resource blocks (PRBs) corresponding to the M first CORESETs is the same; The interleaving modes corresponding to the M first CORESETs are the same, or the interleaving part parameters corresponding to the M first CORESETs are the same; or the M first CORESETs do not use interleaving; The resource unit group sets corresponding to the M first CORESETs have the same size; The values of the interleaver sizes corresponding to the M first CORESETs are the same; The interleaver offsets corresponding to the M first CORESETs are the same; The precoding granularities corresponding to the M first CORESETs are the same.
7. The terminal device according to claim 5, characterized in that: The N first search spaces correspond to the same first CORESET.
8. The terminal device according to any one of claims 5 to 7, characterized in that: The N first search spaces satisfy one or more of the following: The N first search spaces correspond to the same number of bits in the TCI indication field in the downlink control information DCI; The N first search spaces correspond to the same number of PDCCH occasions in the same time slot; The number of bits corresponding to the value of 1 in the configuration value of the RRC parameter monitoring symbol within the time slot monitoringSymbolsWithinSlot corresponding to the N first search spaces is the same; The N first search spaces have the same span as the number of consecutive symbols corresponding to a PDCCH monitoring occasion in a time slot; The N first search spaces correspond to the same period but different time offsets; or, the N first search spaces correspond to the same period and time offset; The number of consecutive slots appearing in the N first search spaces in one cycle is the same; The DCI formats corresponding to the N first search spaces are the same; The PDCCH candidates with the same aggregation level L and the same number in the N first search spaces are associated with each other; The PDCCHs associated with the N first search spaces indicate the same information; The PDCCHs associated with the N first search spaces indicate the same physical downlink shared channel PDSCH scheduling; The PDCCHs associated with the N first search spaces indicate the same physical uplink shared channel PUSCH scheduling; The PDCCHs associated with the N first search spaces indicate the same channel state information CSI reporting; The PDCCHs associated with the N first search spaces indicate the same channel sounding reference signal SRS transmission; The PDCCHs associated with the N first search spaces indicate the same physical random access channel PRACH transmission; All or part of the N first search spaces are used to transmit the same DCI.
9. A terminal device, characterized in that: include: A transceiver module, configured to receive first configuration information sent by a network device through a radio resource control RRC signaling, wherein the first configuration information indicates N first search spaces, the N first search spaces are associated with each other, the N first search spaces correspond to a PDCCH, and N is an integer greater than or equal to 2; each of the first search spaces corresponds to a control resource set CORESET; the N first search spaces correspond to M different first CORESETs, where M≤N; The identifier coresetPoolIndex of the RRC parameter CORESET pool corresponding to the M first CORESETs is not configured; or, the values corresponding to the RRC parameter coresetPoolIndex corresponding to the M first CORESETs are the same.
10. A computer-readable storage medium comprising instructions, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1 to 4.
Citation Information
Patent Citations
Channel detection indication method, terminal and network equipment
CN110740025A
Communication processing method and device, and computer storage medium
CN111279778A
Terminal apparatus, communication method, and integrated circuit
US20200076556A1