Devices and methods for downlink coverage
By receiving and decoding two PDCCH candidates within the same slot, with the second being a repetition of the first, the method enhances PDSCH scheduling flexibility and downlink coverage in NTN, addressing the limitations of current PDSCH resource allocation.
Patent Information
- Application Number
- PCT/CN2025/094083
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
Current communication technologies in non-terrestrial networks (NTN) lack effective solutions for PDSCH resource allocation with intra-slot PDCCH repetition, which is essential for enhancing downlink coverage, especially in scenarios like satellite communication where legacy UEs face challenges in decoding PDCCH and PDSCH due to limited symbol availability.
A terminal device receives two PDCCH candidates within the same slot, with the second candidate being a repetition of the first, and decodes at least one PDSCH located between them, allowing for enhanced downlink coverage through flexible PDSCH scheduling.
This approach maximizes scheduling flexibility for PDSCH resources and ensures compatibility with legacy UEs while significantly improving downlink coverage by utilizing intra-slot PDCCH repetition.
Smart Images

Figure CN2025094083_12112026_PF_FP_ABST
Abstract
Description
DEVICES AND METHODS FOR DOWNLINK COVERAGEFIELDS
[0001] Example embodiments of the present disclosure generally relate to the field of communication techniques and in particular, to devices and methods for downlink coverage.BACKGROUND
[0002] A non-terrestrial network (NTN) refers to a network or segment of networks using radio frequency (RF) resources onboard a satellite or unmanned aircraft system (UAS) platform. The NTN could provide ubiquitous and resilient wireless service beyond the terrestrial network coverage. The 3rd Generation Partnership Project (3GPP) has started the standardization of NTN since the fifth generation (5G) communication system. NTN is expected to be fully integrated with terrestrial network (TN) in the sixth generation (6G) .SUMMARY
[0003] In general, embodiments of the present disclosure provide devices and methods for downlink coverage.
[0004] In a first aspect, there is provided a terminal device. The terminal device comprises: a processor configured to cause the terminal device to: receive, from a network device, two physical downlink control channel (PDCCH) candidates and at least one PDSCH scheduled by the two PDCCH candidates, wherein the two PDCCH candidates are located within a same slot, the second PDCCH candidate of the two PDCCH candidates is a repetition of the first PDCCH candidate of the two PDCCH candidates, and the at least one PDSCH is located between the two PDCCH candidates in time domain; and decode the at least one PDSCH based on downlink control information (DCI) in the two PDCCH candidates.
[0005] In a second aspect, there is provided a network device. The network device comprises: a processor configured to cause the network device to: encode at least one PDSCH scheduled by two PDCCH candidates located within a same slot based on DCI in the two PDCCH candidates; and transmit, to a terminal device, the two PDCCH candidates and at least one PDSCH, wherein the second PDCCH candidate of the two PDCCH candidates is a repetition of the first PDCCH candidate of the two PDCCH candidates, and the at least one PDSCH is located between the two PDCCH candidates in time domain.
[0006] In a third aspect, there is provided a communication method performed by a terminal device. The method comprises: receiving, from a network device, two PDCCH candidates and at least one PDSCH scheduled by the two PDCCH candidates, wherein the two PDCCH candidates are located within a same slot, the second PDCCH candidate of the two PDCCH candidates is a repetition of the first PDCCH candidate of the two PDCCH candidates, and the at least one PDSCH is located between the two PDCCH candidates in time domain; and decoding the at least one PDSCH based on DCI in the two PDCCH candidates.
[0007] In a fourth aspect, there is provided a communication method performed by a network device. The method comprises: encoding at least one PDSCH scheduled by two PDCCH candidates located within a same slot based on DCI in the two PDCCH candidates; and transmitting, to a terminal device, the two PDCCH candidates and at least one PDSCH, wherein the second PDCCH candidate of the two PDCCH candidates is a repetition of the first PDCCH candidate of the two PDCCH candidates, and the at least one PDSCH is located between the two PDCCH candidates in time domain.
[0008] In a fifth aspect, there is provided a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to the third, or fourth aspect.
[0009] Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Through the more detailed description of some example embodiments of the present disclosure in the accompanying drawings, the above and other objects, features and advantages of the present disclosure will become more apparent, wherein:
[0011] FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;
[0012] FIGS. 2A and 2B illustrate schematic diagrams of non-terrestrial network scenarios with different payload types in accordance with some embodiments of the present disclosure;
[0013] FIG. 3A illustrates a signaling flow of an initial access procedure with 4 step random access channel (RACH) ;
[0014] FIG. 3B illustrates a signaling flow of an initial access procedure with 2 step RACH;
[0015] FIG. 4 illustrates a signaling flow for downlink coverage in accordance with some embodiments of the present disclosure;
[0016] FIG. 5 illustrates an example schematic diagram of PDCCH repetition resource allocation in accordance with some embodiments of the present disclosure;
[0017] FIG. 6 illustrates an example schematic diagram of PDSCH repetition resource allocation in accordance with some embodiments of the present disclosure;
[0018] FIG. 7A illustrates an example schematic diagram of PDSCH time domain resource allocation A for normal cyclic prefix (CP) in accordance with some embodiments of the present disclosure;
[0019] FIG. 7B illustrates an example schematic diagram of PDSCH time domain resource allocation A for extended CP in accordance with some embodiments of the present disclosure;
[0020] FIG. 7C illustrates an example schematic diagram of PDSCH time domain resource allocation B in accordance with some embodiments of the present disclosure;
[0021] FIG. 7D illustrates an example schematic diagram of PDSCH time domain resource allocation C in accordance with some embodiments of the present disclosure;
[0022] FIGS. 8A and 8B illustrate example schematic diagrams of PDCCH repetition resource allocation in accordance with some embodiments of the present disclosure;
[0023] FIG. 9 illustrates a flowchart of a communication method implemented at a terminal device according to some example embodiments of the present disclosure;
[0024] FIG. 10 illustrates a flowchart of a communication method implemented at a network device according to some example embodiments of the present disclosure; and
[0025] FIG. 11 illustrates a simplified block diagram of an apparatus that is suitable for implementing example embodiments of the present disclosure.
[0026] Throughout the drawings, the same or similar reference numerals represent the same or similar element.DETAILED DESCRIPTION
[0027] Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.
[0028] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.
[0029] As used herein, the term ‘terminal device’ refers to any device having wireless or wired communication capabilities. Examples of the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, devices on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure / network, devices for Integrated Access and Backhaul (IAB) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV) commonly known as a drone which is an aircraft without any human pilot, devices on high speed train (HST) , or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like. The ‘terminal device’ can further has ‘multicast / broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM. The term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
[0030] The term “network device” refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate. Examples of a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , and the like.
[0031] The terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function and can be used to predict some information.
[0032] The terminal or the network device may work on several frequency ranges, e.g., FR1 (e.g., 450 MHz to 6000 MHz) , FR2 (e.g., 24.25GHz to 52.6GHz) , frequency band larger than 100 GHz as well as Tera Hertz (THz) . It can further work on licensed / unlicensed / shared spectrum. The terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario. The terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
[0033] The embodiments of the present disclosure may be performed in test equipment, e.g., signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator. In some embodiments, the terminal device may be connected with a first network device and a second network device. One of the first network device and the second network device may be a master node and the other one may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs) . In some embodiments, the first network device may be a first RAT device and the second network device may be a second RAT device. In some embodiments, the first RAT device is eNB and the second RAT device is gNB. Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device. In some embodiments, first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device. In some embodiments, information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
[0034] As used herein, the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’ The term ‘based on’ is to be read as ‘at least in part based on. ’ The term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’ The term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’ The terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
[0035] In some examples, values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
[0036] As used herein, the term “resource, ” “transmission resource, ” “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
[0037] Principles and implementations of the present disclosure will be described in detail below with reference to the figures.
[0038] FIG. 1 illustrates a schematic diagram of an example communication environment 100 in which example embodiments of the present disclosure can be implemented. The communication environment 100 involves a network device 120 and a terminal device 110. The terminal device 110 may be a UE and the network device 120 may be a base station serving the UE.
[0039] It is to be understood that the number of devices and their connections shown in FIG. 1 is only for the purpose of illustration without suggesting any limitation. The communication environment 100 may include any suitable number of devices configured to implement example embodiments of the present disclosure. Although not shown, it would be appreciated that one or more additional devices may be deployed in the communication environment 100.
[0040] In the following, for the purpose of illustration, some example embodiments are described with the terminal device 110 operating as a UE in the NTN and the network device 120 operating as a satellite or server device in the NTN. However, in some example embodiments, operations described in connection with a terminal device may be implemented at a network device or other device, and operations described in connection with a network device may be implemented at a terminal device or other devices.
[0041] A link from the network device 120 to the terminal device 110 is referred to as a downlink (DL) , while a link from the terminal device 110 to the network device 120 is referred to as an uplink (UL) . In DL, the network device 120 is a transmitting (TX) device (or a transmitter) and the terminal device 110 is a receiving (RX) device (or a receiver) . In UL, the terminal device 110 is a TX device (or a transmitter) and the network device 120 is a RX device (or a receiver) . In communication, the terminal device 110 may perform uplink transmission with the network device 120, for example PUSCH transmission. DMRS bundling may be needed for transmission occasions of the uplink transmission.
[0042] The communications in the communication environment 100 may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , New Radio (NR) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like. The embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
[0043] Satellite direct communication as a complement to terrestrial network coverage provides communication services to everyone, everywhere, at any time, bringing new values and opportunities to various market segments including IoT and smartphones.
[0044] Geostationary earth orbit (GEO) satellite has its advantage to provide global coverage for low data rate services. Using existing GEO satellites can enable rapid deployment to provide short message services (SMSs) and voice services. This feature is necessary for operators to increase their productivity and usage of GEO satellites.
[0045] There are smartphone products in the market supporting GEO satellite direct communication for SMS and low-rate voice call for emergency services. Although the market acceptance of such products has been good, they are based on proprietary solutions which are not preferred from a cost perspective and cannot provide consistent user performance.
[0046] 3GPP has been working on internet of things over NTN (IoT-NTN) since Rel-17 targeting direct communication over satellites. However, it was designed for IoT devices / services thus the current solution cannot enable voice call over GEO satellites.
[0047] In some embodiments, the communication environment 100 may be implemented in the NTN. The NTN may have different payload types. FIG. 2A and FIG. 2B illustrate schematic diagrams of NTN scenarios with different payload types. The NTN of FIG. 2A is based on a transparent payload, and the NTN of FIG. 2B is based on a regenerative payload.
[0048] In some example embodiments, a satellite or UAS platform may implement either a transparent or a regenerative (with on board processing) payload. The satellite or UAS platform may generate beams (for example, typically generate several beams) over a given service area bounded by its field of view 260. The footprints 250 of the beams are typically of an elliptic shape. The field of view of a satellite or UAS platform depends on the on-board antenna diagram and the minimum elevation angle. Table 1 shows some parameters for some example platforms. Table 1
[0049] As shown in FIG. 2A, in a transparent payload scenario, a UE 210 may communicate with the satellite 220 or UAS platform through a service link, and the satellite 220 or UAS platform may communicate with a gateway 230 having connection with a data network 240 through a feeder link. In this scenario, the satellite 220 or UAS platform may perform RF filtering, frequency conversion and amplification, therefore a waveform signal repeated by the payload may be unchanged. Based on the transparent payload, the UE 210 may have a connection with the data network 240. The round-trip time (RTT) in this case reflects the time for data to transmit from the UE 210 through the satellite 220 or UAS platform to a gNB (which is on the ground) .
[0050] As shown in FIG. 2B, in a regenerative payload scenario, the UE 210 may communicate with a satellite 220-1 or UAS platform through a service link. The satellite 220-1 or UAS platform may communicate with a satellite 220-2 or UAS platform through Inter-Switch Link (ISL) , and the satellite 220-2 or UAS platform may communicate with the gateway 230 having a connection with the data network 240 through a feeder link. If ISL is not available, the satellite 220 or UAS platform may communicate with the gateway 230 having a connection with a data network 240 through a feeder link. In this scenario, the satellite 220-1 and 220-2 (or UAS platform) may perform RF filtering, frequency conversion and amplification, demodulation / decoding, switch and / or routing, and coding / modulation which is effectively equivalent to having all or part of base station (for example, gNB) functions on the satellite or UAS platform. Based on the regenerative payload, the UE 210 may have a connection with the data network 240. The RTT in this case reflects the time for data to transmit from the UE 210 to the gNB (which is on the satellite or UAS platform) .
[0051] FIGS. 3A and 3B illustrate example initial access procedures, where FIG. 3A shows an example procedure of 4 step RACH, and FIG. 3B shows an example procedure of 2 step RACH.
[0052] In the downlink, a gNB may transmit (e.g., unicast, multicast, and / or broadcast) one or more reference signals (RSs) to a UE, e.g., primary synchronization signal (PSS) , secondary synchronization signal (SSS) , channel state information reference signal (CSI-RS) , DMRS, and / or PT-RS) . The PSS and the SSS may be transmitted by the gNB and used by the UE to synchronize the UE to the gNB. The PSS and the SSS may be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block (SSB) that includes the PSS, the SSS, and the PBCH. The gNB may periodically transmit a burst of SS / PBCH blocks.
[0053] The SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., 4 OFDM symbols) and may span one or more subcarriers in the frequency domain (e.g., 240 contiguous subcarriers) . The PSS, the SSS, and the PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, 1 OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., two symbols later) and may span 1 OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., across the next 3 OFDM symbols) and may span 240 subcarriers.
[0054] The location of the SS / PBCH block in the time and frequency domains may not be known to the UE (e.g., if the UE is searching for the cell) . To find and select the cell, the UE may monitor a carrier for the PSS. For example, the UE may monitor a frequency location within the carrier. If the PSS is not found after a certain duration (e.g., 20ms) , the UE may search for the PSS at a different frequency location within the carrier, as indicated by a synchronization raster. If the PSS is found at a location in the time and frequency domains, the UE may determine, based on a known structure of the SS / PBCH block, the locations of the SSS and the PBCH, respectively. The SS / PBCH block may be a cell-defining SS block (CD-SSB) . In an example, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on a synchronization raster. In an example, a cell selection / search and / or reselection may be based on the CD-SSB.
[0055] The PBCH may include a master information block (MIB) used to provide the UE with one or more parameters. The MIB may be used by the UE to locate remaining minimum system information (RMSI) associated with the cell. The RMSI may include a system information block type 1 (SIB1) . The SIB1 may contain information needed by the UE to access the cell. The UE may use one or more parameters of the MIB to monitor PDCCH, which may be used to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may be decoded using parameters provided in the MIB. The PBCH may indicate an absence of SIB1. Based on the PBCH indicating the absence of SIB1, the UE may be pointed to a frequency. The UE may search for an SS / PBCH block at the frequency to which the UE is pointed.
[0056] The IE SearchSpace defines how / where to search for PDCCH candidates. Each search space is associated with one ControlResourceSet. For a scheduled SCell in the case of cross carrier scheduling, except for nrofCandidates, all the optional fields are absent (regardless of their presence conditions) . For a scheduled SpCell in the case of the cross carrier scheduling, if the search space is linked to another search space in the scheduling SCell, all the optional fields of this search space in the scheduled SpCell are absent (regardless of their presence conditions) except for nrofCandidates.
[0057] In NTN, system information block type 19 (SIB19) is broadcasted with NTN specific information. SIB19 may include PDCCH and PDSCH. For example, SIB19 includes Type0A-PDCCH CSS set configured by searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI format 1_0 with CRC scrambled by a SI-RNTI. After that, a random access procedure may be performed. It should be noted that FIG. 3A and FIG. 3B are illustrated as an example. The SIB19 shown in FIG. 3A and FIG. 3B may be replaced by SIBx, which may include any SIB except SIB1, for both TN and NTN.
[0058] As shown in FIG. 3A, the 4-step RACH procedure may be summarized as follows below. Message 1 / Msg1 (also known as PRACH) indicates that the UE sends a specific preamble to the gNB via PRACH using a specific resource called RACH occasion (RO) . Message 2 / Msg2 (also known as random access response, RAR) indicates that the gNB replies with an RAR message, which includes PDCCH and PDSCH. In response to a PRACH transmission, the UE attempts to detect a DCI format 1_0 with CRC scrambled by a corresponding RA-RNTI during a window controlled by higher layers. Message 3 / Msg3 (also known as radio resource control (RRC) request) indicates that the UE responds to Msg2 over the scheduled PUSCH with an ID for contention resolution. Further, Message 4 / Msg4 (also known as RRC setup) indicates that the gNB transmits the contention resolution message with the contention-resolution ID. Msg4 includes PDCCH and PDSCH. In response to a PUSCH transmission scheduled by a RAR UL grant when a UE has not been provided a C-RNTI, the UE attempts to detect a DCI format 1_0 with CRC scrambled by a corresponding TC-RNTI scheduling a PDSCH that includes a UE contention resolution identity.
[0059] Upon reception of Msg4, the UE sends an acknowledgement (ACK) on a physical uplink control channel (PUCCH) if its contention-resolution ID is carried by Msg4. This completes the 4-step RACH.
[0060] FIG. 3B illustrates the 2-step RACH procedure which is similar to the 4-step RACH presented above. Specifically, Msg1 and Msg3 in the 4-step RACH are combined in a MsgA and sent out without waiting for feedback from the UE in between (i.e., Msg2 in the 4-step RACH) . Similarly, the gNB combines Msg2 and Msg4 in the 4-step RACH into MsgB. In response to a transmission of a PRACH and a PUSCH, or to a transmission of only a PRACH if the PRACH preamble is mapped to a valid PUSCH occasion, the UE attempts to detect a DCI format 1_0 with CRC scrambled by a corresponding MsgB-RNTI during a window controlled by higher layers. MsgB may include PDCCH and PDSCH.
[0061] The above PDSCH and PDCCH may require coverage enhancements to ensure the successful initial access. Some more aspects regarding PDCCH are described below.
[0062] The resource allocation of PDCCH needs to consider time domain and frequency domain. In frequency domain, control resource set (CORESET) is used to describe the physical resource allocation of PDCCH, and control channel element (CCE) is used to define the logical resource allocation of PDCCH. A CORESET contains multiple CCEs, a control-channel element consists of 6 resource-element groups (REGs) , and a resource-element group equals one resource block (RB) during one OFDM symbol. In time domain, search space is used to describe the resource allocation of PDCCH. The search space defines where and how the UE searches for possible DCI on the PDCCH.
[0063] In NTN, the search space of PDCCH can be divided into two types: common search space (CSS) and UE-specific search space (USS) . It is to be noted that each search space set is appointed to one CORESET. The periodicity, offset, duration of an SS may be configured in slot level, and in symbol level, the parameter “monitoringSymbolsWithinSlot” may be used to define the locations of the PDCCH candidates.
[0064] The PDCCH aggregation level (AL) is the CCE number of each PDCCH candidate, e.g., AL 16 means the PDCCH candidate is composed of 16 CCEs. The PDCCH AL gain will be limited by the data rate. The Msg2 / Msg4 / MsgB includes DCI format 1_0 scrambled by RA-RNTI / TC-RNTI / MsgB-RNTI, Type1 PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommon, configured by SIB1, BWP-DownlinkCommon, BWP-DownlinkDedicated or Type0 PDCCH CSS without configured.
[0065] The SIB1 includes the DCI format 1_0 scrambled by SI-RNTI, the CORESET0, the Type0 PDCCH CSS configured by searchSpaceZero in PDCCH-ConfigCommon, and the SIB1 is configured by MIB.
[0066] In addition, the paging may indicate a Type2-PDCCH CSS set configured by pagingSearchSpace in PDCCH-ConfigCommon for a DCI format 1_0 with CRC scrambled by a paging-RNTI (P-RNTI) .
[0067] Regarding PDCCH detection for Msg2, the UE attempts to detect a DCI format 1_0 with CRC scrambled by a corresponding RA-RNTI during a window controlled by higher layers. The window starts at the first symbol of the earliest CORESET the UE is configured to receive PDCCH for Type1-PDCCH CSS set, that is at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for Type1-PDCCH CSS set. The length of the window in number of slots, based on the SCS for Type1-PDCCH CSS set, is provided by ra-ResponseWindow. Possible values of ra-ResponseWindow are {1, 2, 4, 8, 10, 20, 40, 80} slot (s) , and the duration is less than or equal to 10ms.
[0068] Regarding PDSCH detection for Msg2, if the UE detects the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI and a transport block in a corresponding PDSCH within the window, it passes the transport block to higher layers. Then the higher layers parse the transport block for a random access preamble identity (RAPID) associated with the PRACH transmission. If the higher layers identify the RAPID in RAR message (s) of the transport block, the higher layers indicate an uplink grant to the physical layer, which is referred to as random access response (RAR) UL grant in the physical layer.
[0069] For Msg 3 or Msg 1, the higher layers can indicate to the physical layer to transmit a PRACH, if UE does not detect the DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI within the window, or UE does not correctly receive the transport block in the corresponding PDSCH within the window, or higher layers do not identify the RAPID associated with the PRACH transmission from the UE. If requested by higher layers, the UE is expected to transmit a PRACH no later than NT, 1 + 0.75 msec after the last symbol of the window, or the last symbol of the PDSCH reception, where NT, 1 is a time duration of N1 symbols corresponding to a PDSCH processing time for UE processing capability 1. μ corresponds to the smallest SCS configuration among the SCS configurations for the PDCCH carrying the DCI format 1_0, the corresponding PDSCH when additional PDSCH DM-RS is configured, and the corresponding PRACH. For μ = 0, the UE assumes N1, 0 = 14. For a PRACH transmission using 1.25 kHz or 5 kHz SCS, the UE determines N1 assuming SCS configuration μ = 0. N1 = {14, 13, 20, 24} for μ = {0, 1, 2, 3} .
[0070] In the case of two PDCCH candidates, when a PDCCH reception by a UE includes two PDCCH candidates from corresponding search space sets, the PDCCH monitoring occasion is the union of the PDCCH monitoring occasions for the two PDCCH candidates, the start of the PDCCH reception is the start of the earlier PDCCH candidate, and the end of the PDCCH reception is the end of the PDCCH candidate that ends later. This may lead to the situation where the corresponding PDSCH can only start at the end of the PDCCH monitoring occasion or the end of the PDCCH reception, particularly when using linked PDCCH SS.
[0071] Moreover, the UE does not expect any two PDCCH monitoring occasions on an active DL BWP, for the same search space set or for different search space sets, in the same CORESET to be separated by a non-zero number of symbols that is smaller than the CORESET duration. In some solutions, the typical CORESET duration is 2 symbols (1-3 symbols) . The issue is that intra-slot PDCCH repetition with two candidates will occupy at least 3 times the duration of the CORESET, ranging from 3 to 9 symbols. This leaves the remaining symbols in the same slot for legacy PDSCH scheduling restricted.
[0072] Regarding the reception of PDSCH, the UE in RRC_IDLE and RRC_INACTIVE modes shall be able to decode two PDSCHs each scheduled with SI-RNTI, P-RNTI, RA-RNTI, TC-RNTI, G-RNTI, or G-CS-RNTI, where the PDSCH scheduled with TC-RNTI for a reduced capability UE that indicates supportOfERedCap is allocated no more than 25 physical RBs (PRBs) when configured with SCS m = 0 or no more than 12 PRBs when configured with SCS m = 1, with the two PDSCHs partially or fully overlapping in time in non-overlapping PRBs.
[0073] On a frequency range 1 cell, the UE shall be able to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI and, during a process of P-RNTI triggered SI acquisition, another PDSCH scheduled with SI-RNTI that partially or fully overlap in time domain in non-overlapping PRBs, unless the PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI requires Capability 2 processing time according to clause 5.3 in which case the UE may skip decoding of the scheduled PDSCH with C-RNTI, MCS-C-RNTI, or CS-RNTI.
[0074] On a frequency range 2 cell, the UE is not expected to decode a PDSCH scheduled with C-RNTI, MCS-C-RNTI, or CS-RNTI if in the same cell, during a process of P-RNTI triggered SI acquisition, another PDSCH scheduled with SI-RNTI partially or fully overlapping in time.
[0075] Two downlink resource allocation schemes, type 0 and type 1, are supported. The UE shall assume that when the scheduling grant is received with DCI format 1_0, 4_0 or 4_1 then downlink resource allocation type 1 is used.
[0076] For a PDSCH scheduled with a DCI format 1_0 in any type of PDCCH CSS, regardless of which bandwidth part is the active bandwidth part, RB numbering starts from the lowest RB of the CORESET in which the DCI was received; otherwise, RB numbering starts from the lowest RB in the determined downlink bandwidth part. When the PDCCH reception includes two PDCCH candidates from two respective search space sets, for the purpose of determining the downlink RB set of a PDSCH when scheduled by DCI format 1_0, the CORESET with lower ID among two CORESETs associated with two PDCCH candidates is used.
[0077] In downlink resource allocation of type 1, the RB assignment information indicates to a scheduled UE a set of contiguously allocated non-interleaved or interleaved virtual RBs within the active bandwidth part of size PRBs except for the case when DCI format 1_0 is decoded in any CSS in which case the size of CORESET 0 shall be used if CORESET 0 is configured for the cell and the size of initial DL bandwidth part shall be used if CORESET 0 is not configured for the cell.
[0078] Regarding the scheduling of DCI, reserved Bits are used for PDSCH repetition indication, activation or deactivation. For example, the following information is transmitted by means of the DCI format 1_0 with CRC scrambled by P-RNTI: Reserved bits - (8 -M) bits for operation in a cell with shared spectrum channel access in frequency range 1 or for operation in a cell in frequency range 2-2; (6 -M) bits for operation in a cell without shared spectrum channel access, where the value of M is the number of bits for the field of “TRS availability indication” as defined above.
[0079] The following information is transmitted by means of the DCI format 1_0 with CRC scrambled by SI-RNTI: Reserved bits -17 bits for operation in a cell with shared spectrum channel access in frequency range 1 or for operation in a cell in frequency range 2-2; otherwise, 15 bits.
[0080] The following information is transmitted by means of the DCI format 1_0 with CRC scrambled by RA-RNTI or MsgB-RNTI: Reserved bits - (16 -A) bits for operation in a cell without shared spectrum access in frequency range 1 and frequency range 2-1, (18 -A) for operation in a cell with shared spectrum access in frequency range 1 or for operation in a cell in frequency range 2-2, where the value of A is the number of bits for the field of “LSBs of SFN” as defined above.
[0081] As can be summarized from the above, several issues need to be addressed in the NTN. On one hand, there is currently no solution for PDSCH resource allocation with the intra-slot PDCCH repetition. On the other hand, several considerations should be taken into account, such as how to do the PDSCH repetition scheduled by the PDCCH within an intra-slot repetition, how to activate or deactivate the PDSCH repetition, how to indicate resources for the repeated PDSCH, and the like.
[0082] According to some embodiments of the present disclosure, a solution is proposed for downlink coverage enhancement. In one solution, a terminal device receives two PDCCH candidates and at least one PDSCH scheduled by the two PDCCH candidates from a network device. The two PDCCH candidates are located within a same slot, the second PDCCH candidate of the two PDCCH candidates is a repetition of the first PDCCH candidate of the two PDCCH candidates, and the at least one PDSCH is located between the two PDCCH candidates in time domain. The terminal device decodes the at least one PDSCH based on DCI in the two PDCCH candidates.
[0083] In this way, the flexibility in scheduling PDSCH resource is maximized, backward compatibility for legacy UEs to decode the PDSCH is ensured, and the downlink coverage of PDSCH is enhanced using intra-slot repetition.
[0084] Reference is made to FIG. 4, which illustrates a signaling flow 400 for downlink coverage in accordance with some embodiments of the present disclosure. For the purposes of discussion, the signaling flow 400 will be discussed with reference to FIG. 1, for example, by using the terminal device 110 and the network device 120.
[0085] The network device 120 may encode 402 at least one PDSCH scheduled by two PDCCH candidates located within the same slot based on DCI in the two PDCCH candidates. For example, the two PDCCH candidates in one slot may be allocated in discontinuous symbols with a gap larger than the symbol length (represented as L) of the at least one scheduled PDSCH of the PDCCH. The at least one scheduled PDSCH may be allocated in the symbols between the two PDCCH candidates.
[0086] After the encoding, the network device 120 transmits 404 the two PDCCH candidates and the at least one PDSCH to the terminal device 110. The two PDCCH candidates include a first PDCCH and a second PDCCH. The second PDCCH candidate is a repetition of the first PDCCH candidate, and the at least one PDSCH is located between the two PDCCH candidates in time domain.
[0087] The terminal device 110 receives 406 the two PDCCH candidates and the at least one PDSCH from the network device 120. The terminal device 110 decodes 408 the at least one PDSCH based on the DCI in the two PDCCH candidates.
[0088] By this approach, the PDSCH (s) can be scheduled between two intra-slot repeated PDCCH candidates, thereby maximizing the flexibility in scheduling PDSCH resource and enhancing the downlink coverage of PDSCH.
[0089] FIG. 5 illustrates an example schematic diagram of PDCCH repetition resource allocation in accordance with some embodiments of the present disclosure. The example in FIG. 5 involves a PDCCH candidate 502, a PDCCH candidate 504, and at least one scheduled PDSCH (such as PDSCH 506, PDSCH 508, and the like) in a single slot.
[0090] In some example embodiments, a separation in time domain between the two PDCCH candidates may be not smaller than the total duration of the at least one scheduled PDSCH. For instance, each PDCCH candidate may be allocated with the same CORESET and the same time duration in the same number of symbols. The PDCCH candidate 502 and the PDCCH candidate 504 may be separated by a non-zero number of symbols that is not smaller than the total duration of the duration of the scheduled PDSCH (s) .
[0091] As an example, the terminal device 110 may not expect any two PDCCH monitoring occasions on an active DL BWP, at least for the Type0A-PDCCH CSS, Type1-PDCCH CSS and Type2-PDCCH CSS, which are not SearchSpaceZero, within the same CORESET to be separated by a non-zero number of symbols that is equal to or greater than the duration of the scheduled PDSCH (s) . As another example, the terminal device 110 may not expect any two PDCCH monitoring occasions on an active DL BWP, for PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, within the same CORESET to be separated by a non-zero number of symbols that is equal to or greater than the duration of the scheduled PDSCH (s) .
[0092] In some examples, the two PDCCH candidates may be associated with the same search space set, and the separation may be indicated by a gap in a number of symbols. Alternatively, or additionally, the separation may be indicated by respective bitmaps for the two PDCCH candidates, and a bitmap may represent symbols occupied by a respective PDCCH within the slot. For example, the PDCCH candidate 502 and the PDCCH candidate 504 may be separated by a gap in the unit of symbol or by two bitmaps of the two PDCCH candidates.
[0093] In some other examples, the two PDCCH candidates may be associated with different search space sets, and the separation may be indicated by a gap in a number of symbols. Alternatively, or additionally, the separation may be indicated by respective bitmaps for the two PDCCH candidates. A bitmap may represent symbols occupied by a respective PDCCH within the slot.
[0094] In some example embodiments, as shown in FIG. 5, the at least one PDSCH may include at least two PDSCHs (such as PDSCH 506, PDSCH 508, and the like) , and the total duration of the at least two PDSCHs may be defined as starting at the first symbol of the first PDSCH in time domain and ending at the last symbol of the last PDSCH in time domain. For example, as shown in FIG. 5, if there are two PDSCHs, i.e., the PDSCH 506 and the PDSCH 508, the total duration may start at the first symbol of the PDSCH 506 and end at the last symbol of the PDSCH 508 in time domain.
[0095] In some other example embodiments, the at least one PDSCH may include two PDSCHs with the second PDSCH in time domain being a repetition of the first PDSCH, and the total duration of the two PDSCHs may be determined based on: a time duration of a PDSCH of the two PDSCHs, and a time offset between the two PDSCHs. For example, the PDSCH 508 may be the repetition of the PDSCH 506, and the total duration may be determined based on the time duration of the PDSCH 508 and the time offset between the PDSCH 506 and the PDSCH 508. In an example, the terminal device 110 does not expect any two PDCCH monitoring occasions on an active DL BWP, at least for the Type0A-PDCCH CSS, Type1-PDCCH CSS and Type2-PDCCH CSS, which are not SearchSpaceZero, in the same CORESET, to be separated by a non-zero number of symbols that is not smaller than the duration of the scheduled PDSCH (s) . In another example, the terminal device 110 does not expect any two PDCCH monitoring occasions on an active DL BWP, for PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, in the same CORESET, to be separated by a non-zero number of symbols that is not smaller than the duration of the scheduled PDSCH (s) .
[0096] In some examples, the time offset between the two PDSCHs may be determined by a time difference between a first starting symbol of the first PDSCH and a second starting symbol for the second PDSCH. For example, the PDSCH 508 may be the repetition of the PDSCH 506, and the total duration may be L+Soffset, where L represents a symbol length of the PDSCH, and Soffset represents the time offset. Further, Soffset=S2-S1, where S2 represents the starting symbol of the PDSCH 508, and S1 represents the starting symbol of the PDSCH 506. In this case, the two PDSCHs have the same reference point S0 for the starting symbol S.
[0097] Alternatively, or additionally, the time offset between the two PDSCHs may be determined by a time difference between a first reference point for the first starting symbol and a second reference point for the second starting symbol. For example, the PDSCH 508 may be the repetition of the PDSCH 506, and the total duration may be L+Soffset, where L represents a symbol length of the PDSCH, and Soffset represents the time offset. Further, where represents the reference point for the starting symbol of the PDSCH 508, and represents the reference point for the starting symbol of the PDSCH 506. In this case, the two PDSCHs have the same value for the starting symbol S.
[0098] In some example embodiments, the at least one PDSCH may include at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and the at least two PDSCHs may be partially or fully overlapped in time domain, and non-overlapped in frequency domain. As an example, FIG. 6 illustrates an example schematic diagram of PDSCH repetition resource allocation in accordance with some embodiments of the present disclosure. The example in FIG. 6 involves the PDSCH 506 and the PDSCH 508 in a single slot. The PDSCH 508 may be the repetition of the PDSCH 506. The PDSCH 506 and the PDSCH 508 may be partially overlapped in time domain, and non-overlapped in frequency domain.
[0099] As an example, the terminal device 110 in RRC_IDLE or RRC_INACTIVE modes may be able to decode the PDSCH 506 and the PDSCH 508, which are scheduled with SI-RNTI, P-RNTI, RA-RNTI, TC-RNTI, G-RNTI, or G-CS-RNTI. The PDSCH 506 and the PDSCH 508 may partially or fully overlap in time, while using non-overlapping PRBs.
[0100] As another example, the terminal device 110 in RRC_IDLE or RRC_INACTIVE modes may be able to decode two PDSCHs: the PDSCH 506, scheduled with SI-RNTI, P-RNTI, RA-RNTI, TC-RNTI, G-RNTI, or G-CS-RNTI; and the PDSCH 508, implicitly scheduled by the higher layer as a repetition of the PDSCH 506 that may partially or fully overlap in time, while using non-overlapping PRBs.
[0101] Thus, the PDSCH (s) scheduled by the repeated PDCCH candidates may be repeated in time domain, either partially or fully overlapped, using non-overlapped PRBs, thereby providing PDSCH scheduling flexibility. FIGS. 7A to 7D illustrate example schematic diagrams of PDSCH time domain resource allocation in accordance with some embodiments of the present disclosure.
[0102] Specifically, FIG. 7A illustrates an example schematic diagram of PDSCH time domain resource allocation A for normal cyclic prefix (CP) . The entries for PDSCH time domain resource allocation in multiple blocks 702 may be schedulable according to the embodiments of the present disclosure, while the entries for PDSCH time domain resource allocation in multiple blocks 704 may be schedulable according to legacy solutions. It can be seen that the entries for PDSCH time domain resource allocation in multiple blocks 702 are multiple times greater than those in multiple blocks 704.
[0103] FIG. 7B illustrates an example schematic diagram of PDSCH time domain resource allocation A for extended CP. The entries for PDSCH time domain resource allocation in multiple blocks 702 may be schedulable according to the embodiments of the present disclosure, while the entries for PDSCH time domain resource allocation in multiple blocks 704 may be schedulable according to legacy solutions. It can be seen that the entries for the PDSCH time domain resource allocation in multiple blocks 702 are multiple times greater than those in multiple blocks 704.
[0104] FIG. 7C illustrates an example schematic diagram of PDSCH time domain resource allocation B. The entries for PDSCH time domain resource allocation in multiple blocks 702 may be schedulable according to the embodiments of the present disclosure, while the entries for PDSCH time domain resource allocation in multiple blocks 704 may be schedulable according to legacy solutions. It can be seen that the entries for PDSCH time domain resource allocation in multiple blocks 702 are multiple times greater than those in multiple blocks 704.
[0105] FIG. 7D illustrates an example schematic diagram of PDSCH time domain resource allocation C. The entries for PDSCH time domain resource allocation in multiple blocks 702 may be schedulable according to the embodiments of the present disclosure, while the entries for PDSCH time domain resource allocation in multiple blocks 704 may be schedulable according to legacy solutions. It can be seen that the entries for PDSCH time domain resource allocation in multiple blocks 702 are multiple times greater than those in multiple blocks 704.
[0106] In addition, the time domain resource for the PDSCH (s) scheduled by the repeated PDCCH candidates may be indicated by a negative value of S to determine the starting symbol of the PDSCH (s) . The negative value of S may be configured by higher layer (e.g., via the parameter startSymbolAndLength) or indicated by DCI corresponding to an index of a single time resource allocation configuration.
[0107] In some examples, the PDSCH carrying SIBx, Paging, Msg2 / Msg3 / MsgB may be intra-slot repeated between the two intra-slot PDCCH candidates scheduling the PDSCH (s) .
[0108] In some example embodiments, the at least one PDSCH may include at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and a time offset of a PDSCH after the first PDSCH with respect to the first PDSCH is larger than or equal to zero symbol. For example, the PDSCH 506 may be the first PDSCH, and the PDSCH 508 may be one of its repetitions. The time offset (i.e., Soffset) from the PDSCH 508 (i.e., repeated PDSCH) to the PDSCH 506 may be larger than or equal to 0 symbol.
[0109] Additionally, in some example embodiments, the time offset may be smaller than a time duration of the first PDSCH. For example, the PDSCH 506 may be the first PDSCH, and the PDSCH 508 may be one of its repetitions. The time offset (i.e., Soffset) from the PDSCH 508 to the PDSCH 506 may be larger than or equal to 0 symbol and smaller than the symbol length L of PDSCH. In this case, the PDSCH 508 and the PDSCH 506 partially overlap in time, thereby saving the time domain resources and ensuring they are placed within a single slot.
[0110] In some example embodiments, the at least one PDSCH may include at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and a frequency offset of a PDSCH after the first PDSCH with respect to the first PDSCH may be larger than one RB. For example, the PDSCH 506 may be the first PDSCH, and the PDSCH 508 may be one of its repetitions. In frequency domain, the frequency offset from the PDSCH 508 to the PDSCH 506 may be larger than 1 RBs.
[0111] In some example embodiments, a reference point for a starting symbol of the first PDSCH of the at least one PDSCH may be determined based on a PDCCH candidate of the two PDCCH candidates that starts earlier in time domain. For example, the PDSCH 506 may be the first PDSCH, and the PDSCH 508 may be one of its repetitions. The slot allocated for the PDSCH 506 is Ks, where where n represents the slot with the scheduling DCI, and K0 is based on the numerology of PDSCH, and μPDSCHand μPDCCH are the subcarrier spacing configurations for PDSCH and PDCCH, respectively. In an example, if the PDCCH reception includes two PDCCH candidates from the same CSS sets, the PDCCH candidate that starts earlier in time domain may be used for the purpose of determining the reference point S0 for the starting symbol of the PDSCH 506. In another example, if the PDCCH reception includes two PDCCH candidates from the same CSS sets, the starting symbol of the PDCCH monitoring occasion of the detected PDCCH candidate that starts earlier in time is the reference point S0. In a further example, if the PDCCH reception includes two PDCCH candidates from the same CSS sets, the starting symbol of the CORSET of the detected PDCCH candidate that starts earlier in time domain may be the reference point S0.
[0112] Alternatively, or additionally, the reference point S0 for the starting symbol of the first PDSCH may be determined based on a start of the slot. For example, the PDSCH 506 may be the first PDSCH, and the PDSCH 508 may be one of its repetitions. The slot allocated for the PDSCH 506 is Ks, where where n represents the slot with the scheduling DCI, and K0 is based on the numerology of PDSCH, and μPDSCHand μPDCCH are the subcarrier spacing configurations for PDSCH and PDCCH, respectively. If the PDCCH reception includes two PDCCH candidates from the same CSS sets, the starting symbol S may be relative to the start of the slot using S0=0.
[0113] In some examples, the two PDCCH candidates may be associated with the same search space set. Optionally, the two PDCCH candidates may be associated with two search space sets respectively, where the two search space sets may be of the same type and have different configurations.
[0114] In some other examples, the two PDCCH candidates may be associated with two search spaces in the same search space set respectively, where the two search spaces may have different configurations.
[0115] In addition, the scheduling of PDSCH (s) further involves signaling, such as for SIB activation / deactivation of PDCCH repetition, corresponding PDSCH repetition, DCI reserved bits to activate / deactivate PDSCH repetition, or the like.
[0116] In some example embodiments, the terminal device 110 may receive a common indication from the network device 120, and the common indication may indicate activation of both PDCCH repetition and PDSCH repetition or deactivation of both PDCCH repetition and PDSCH repetition. For example, for PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, the PDCCH repetition may be activated or deactivated by SIB1. For another example, at least for the Type0A-PDCCH CSS, Type1-PDCCH CSS and Type2-PDCCH CSS, which are not SearchSpaceZero, the PDCCH repetition may be activated or deactivated by SIB1. For the corresponding scheduled PDSCH (e.g., PDSCH of SIBx, Paging, Msg2, Msg4, MsgB) , the PDSCH repetition may be activated or deactivated together with the PDCCH by the same signaling.
[0117] In some example embodiments, the common indication may include an explicit indication indicative of activation of the PDCCH repetition or deactivation of the PDCCH repetition. For example, the explicit indication may be one or more parameters in an information element (IE) as follows:
[0118] In this case, it should be noted that an explicit indication for activation or deactivation of the PDSCH repetition, as described below, may be optional.
[0119] Optionally, the common indication may include an explicit indication indicative of activation of the PDSCH repetition or deactivation of the PDSCH repetition. For example, the explicit indication may be one or more parameters in an IE as follows:
[0120] In this case, it should be noted that an explicit indication for activation or deactivation of the PDCCH repetition, as described above, may be optional.
[0121] In some example embodiments, the terminal device 110 may receive a first indication from the network device 120. The first indication may indicate activation of PDCCH repetition or deactivation of the PDCCH repetition. Further, the terminal device 110 may receive a second indication from the network device 120. The second indication may indicate activation of PDSCH repetition or deactivation of the PDSCH repetition. For example, for PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, the PDCCH repetition may be activated or deactivated by SIB1. For another example, at least for the Type0A-PDCCH CSS, Type1-PDCCH CSS and Type2-PDCCH CSS, which are not SearchSpaceZero, the PDCCH repetition may be activated or deactivated by SIB1. For the corresponding scheduled PDSCH (e.g., PDSCH of SIBx, Paging, Msg2, Msg4, MsgB) , the PDSCH repetition may be activated or deactivated separately from the PDCCH repetition via different signaling in SIB1.
[0122] In some example embodiments, the first indication may be included in SIB1, and the second indication may be included in DCI scheduling PDSCH transmission. For example, for PDCCH CSS other than Type-0 CSS and other than Type-3 CSS for common search spaces other than SearchSpaceZero, the PDCCH repetition may be activated or deactivated by SIB1. For another example, at least for the Type0A-PDCCH CSS, Type1-PDCCH CSS and Type2-PDCCH CSS, which are not SearchSpaceZero, the PDCCH repetition may be activated or deactivated by SIB1. For the corresponding scheduled PDSCH (e.g. PDSCH of SIBx, Paging, Msg2, Msg4, MsgB) , the PDSCH repetition may be activated or deactivated by the reserved DCI bits in the scheduling PDCCH.
[0123] As an example, the first indication or the second indication may be as follows:
[0124] In addition, the following information may be transmitted by means of the DCI Format 1_0 with CRC scrambled by P-RNTI: PDSCH repetition indicator -1 bit for enabling or disabling the intra-slot PDSCH repetition. The following information may be transmitted by means of the DCI Format 1_0 with CRC scrambled by SI-RNTI: PDSCH repetition indicator -1 bit for enabling or disabling the intra-slot PDSCH repetition. The following information may be transmitted by means of the DCI Format 1_0 with CRC scrambled by RA-RNTI or MsgB-RNTI: PDSCH repetition indicator -1 bit for enabling or disabling the intra-slot PDSCH repetition.
[0125] The repeated PDSCH resource, such as time domain resource and frequency domain resource, may be indicated by time offset and frequency offset, which will be described below with reference to some example embodiments.
[0126] In some examples, the at least one PDSCH may include at least two PDSCHs, and the terminal device 110 may receive an information element from the network device 120. The information element may include a parameter set (e.g., pdsch-TimeDomainAllocationList) indicating time domain resources for these PDSCHs. For each PDSCH of these PDSCHs, the parameter set may include a parameter (e.g., TimeDomainAllocation) indicating a time domain resource for the PDSCH. A value of such a parameter (for example, the TimeDomainAllocation value) may be used to determine the row in the tables shown in FIGS. 7A and 7D.
[0127] In some other examples, the at least one PDSCH may include at least two PDSCHs, and the terminal device 110 may receive an information element from the network device 120. The information element may include at least two parameters corresponding to these PDSCHs respectively. A parameter of these parameters may indicate a time domain resource for a corresponding PDSCH.
[0128] According to the above examples, the time domain resources for the PDSCH repetition may be indicated by a separate parameter or a parameter set, e.g., using pdsch-TimeDomainAllocationList to configure the starting symbol S.
[0129] In an example, different pdsch-TimeDomainAllocationList parameters may be used to indicate the first PDSCH and the repeated PDSCH, respectively. In another example, the parameter startSymbolAndLength may be used to indicate the time domain resource for the first PDSCH, and the parameter startSymbolAndLength-repetition may be used to indicate the time domain resource for the PDSCH repetition. That is, the first PDSCH and the repeated PDSCH may correspond to the same parameter pdsch-TimeDomainAllocation, which includes the parameter startSymbolAndLength for the first PDSCH and the parameter startSymbolAndLength-repetition for the repeated PDSCH.
[0130] In some examples, the at least one PDSCH may include at least two PDSCHs, and the terminal device 110 may receive an information element from the network device 120. The information element may include a bitmap set (e.g., bitmap list) indicating frequency domain resources for the at least two PDSCHs. For each PDSCH of these PDSCHs, the bitmap set may include a bitmap indicating a frequency domain resource for the PDSCH.
[0131] In some examples, the at least one PDSCH may include at least two PDSCHs, and the terminal device 110 may receive an information element from the network device 120. The information element may include at least two bitmaps corresponding to these PDSCHs respectively, and a bitmap of these bitmaps may indicate a frequency domain resource for a corresponding PDSCH.
[0132] In some examples, the at least one PDSCH may include at least two PDSCHs, and the terminal device 110 may receive an information element from the network device 120. The information element may include a bitmap indicating frequency domain resources for the at least two PDSCHs. For each PDSCH of these PDSCHs, the bitmap may include one or more bits indicating a frequency domain resource for the PDSCH. In this way, a single bitmap can indicate the frequency domain resources for two PDSCH.
[0133] According to the above examples, the frequency domain resources for the PDSCH repetition may be indicated by a separate parameter or a parameter set, e.g., using CORESET frequency domain resource configuration bitmap frequencyDomainResources, or using the locationAndBandwidth, locationAndBandwidthMulticast to indicate different PDSCH frequency domain resources. More specifically, using the locationAndBandwidth, locationAndBandwidthMulticast to indicate different starting PRBs for the PDSCH frequency domain resource.
[0134] As an example, the information elements may be as follows:
[0135] In addition, different frequency domain resources of the CORSET may be used to indicate different PDSCH frequency domain resource.
[0136] As an example, the information elements may be as follows:
[0137] As another example, the information elements may be as follows:
[0138] As a further example, the information element may be as follows:
[0139] The parameter frequencyDomainResources refers to frequency domain resources for the CORESET. Each bit corresponds to a group of 6 RBs, with grouping starting from the first RB group in the BWP or MBS CFR where the CORESET is configured. When at least one search space is configured with freqMonitorLocation-r16, only the first bits are valid. The first (left-most / most significant) bit corresponds to the first RB group in the BWP or MBS CFR where the CORESET is configured, and so on. A bit that is set to 1 indicates that this RB group belongs to the frequency domain resource of this CORESET. Bits corresponding to a group of RBs not fully contained in the bandwidth part within which the CORESET is configured are set to zero. Thus, the bitmap can be used to realize the indication of frequency domain resource.
[0140] In some examples, the at least one PDSCH may include at least two PDSCHs, and the terminal device 110 may receive an information element from the network device 120. The information element may include an indication of a time offset between the at least two PDSCHs. In this way, the time domain resources for the PDSCH repetition may be indicated by configuring the time offset from a PDSCH repetition to the first PDSCH.
[0141] In some examples, the at least one PDSCH may include at least two PDSCHs, and DCI scheduling these PDSCHs may include an indication of a time offset (denoted by Soffset) between these PDSCHs.
[0142] In some other examples, the at least one PDSCH may include at least two PDSCHs, and DCI scheduling these PDSCHs may include an indication of a frequency offset (denoted by RBoffset) between the at least two PDSCHs.
[0143] As an example, the following information may be transmitted by means of the DCI format 1_0 with CRC scrambled by P-RNTI: a field Soffset of x bits for indicating 2x values of the time offset; and a field RBoffset with y bits for indicating 2y values of the frequency offset in RB unit. The following information may be transmitted by means of the DCI format 1_0 with CRC scrambled by SI-RNTI: a field Soffset of x bits for indicating 2x values of the time offset; and a field RBoffset with y bits for indicating 2y values of the frequency offset in RB unit. The following information may be transmitted by means of the DCI format 1_0 with CRC scrambled by RA-RNTI or MsgB-RNTI: a field Soffset of x bits for indicating 2x values of the time offset; and a field RBoffset with y bits for indicating 2y values of the frequency offset in RB unit .
[0144] In some example embodiments, the at least one PDSCH may include at least two PDSCHs, and DCI scheduling the at least two PDSCHs may include a parameter indicating a time domain resource (e.g., time domain resource assignment for the repetition) for a PDSCH after the first PDSCH of these PDSCHs in time domain.
[0145] As an example, the following information may be transmitted by means of the DCI format 1_0 with CRC scrambled by P-RNTI: the field “time domain resource assignment” for the repetition of 4 bits. The following information may be transmitted by means of the DCI format 1_0 with CRC scrambled by SI-RNTI: the field “time domain resource assignment” for the repetition of 4 bits. The following information may be transmitted by means of the DCI format 1_0 with CRC scrambled by RA-RNTI or MsgB-RNTI: the field “time domain resource assignment” for the repetition of 4 bits.
[0146] It should be noted that the various embodiments of time domain resource allocation and frequency domain resource allocation can be combined. Specifically, the above information elements may be partially combined or individually configured to indicate the time domain resources for PDSCHs and / or the frequency domain resources for the PDSCHs by means of bitmap (e.g., reserved bits in DCI) or network indication (e.g., SIB1) .
[0147] In some example embodiments, the at least one PDSCH may include at least two PDSCHs, and the terminal device 110 may determine a time offset between these PDSCHs based on a search space type for the two PDCCH candidates and first mapping (e.g., a table or rows in the table) from different PDCCH search space types to different time offset values. Alternatively, or additionally, the terminal device 110 may determine the time offset between these PDSCHs based on a type of RNTI associated with the two PDCCHs and second mapping (e.g., a table or rows in the table) from different RNTI types to different time offset values. For example, the time offset Soffset (such as in unit of symbol) may be determined by looking up a table.
[0148] In some example embodiments, the at least one PDSCH may include at least two PDSCHs, and the terminal device 110 may determine a frequency offset between these PDSCHs based on a search space type for the two PDCCH candidates and third mapping (e.g., a table or rows in the table) from different PDCCH search space types to different frequency offset values. Alternatively, or additionally, the terminal device 110 may determine the frequency offset between these PDSCHs based on a type of RNTI associated with the two PDCCHs and fourth mapping (e.g., a table or rows in the table) from different RNTI types to different frequency offset values. For example, the frequency offset (for example, RB offset, represented as RBoffset) may be determined by looking up a table.
[0149] As an example, a table mapping the time offset Soffset and the frequency offset RBoffset to different types of RNTI is shown in Table 2. or PDCCH CSS may be predefined as follows. Table 2
[0150] As another example, a table mapping the time offset Soffset and the frequency offset RBoffset to different types of PDCCH CSS is shown in Table 3. Table 3
[0151] It should be noted that the time offset Soffset and the RB offset RBoffset may be indicated by different rows in the same table or in different rows.
[0152] In view of the above, the two PDCCH candidates in a single slot may be allocated in discontinuous symbols with a gap larger than the symbol length of the scheduled PDSCH, the scheduled PDSCH may be allocated in the symbols between the two PDCCH candidates, and the intra-slot repeated PDSCHs may partially or fully overlap in time domain in non-overlapping PRBs. In some cases, the intra-slot repeated PDSCHs may be in the same frequency domain, which will be described with reference to the following embodiments. It should be noted that the embodiments described above can be applied to the following embodiments if they are not contradictory or conflicting.
[0153] In some example embodiments, the at least one PDSCH may include at least two PDSCHs that are successively located between the two PDCCH candidates. FIGS. 8A and 8B illustrate example schematic diagrams of PDCCH repetition resource allocation in accordance with some embodiments of the present disclosure. The examples in FIGS. 8A and 8B involve the PDCCH candidates 502 and 504, and the scheduled PDSCHs 506 and 508. The scheduled PDSCHs 506 and 508 are successively located between the PDCCH candidates 502 and 504.
[0154] In some example embodiments, the at least two PDSCHs may occupy the same frequency domain resource. For example, the PDSCH 506 and PDSCH 508 may be in the same frequency domain resource (e.g. PRB) .
[0155] In some example embodiments, a time duration of a PDSCH after the first PDSCH of the at least two PDSCHs may be different from a time duration of the first PDSCH. For example, the symbol length L1 of the PDSCH 506 and the symbol length L2 of the PDSCH 508 may be different, e.g., L2 ≤ L1.
[0156] In some example embodiments, DCI scheduling the at least two PDSCHs may include at least two fields corresponding to the at least two PDSCHs, and a field of the at least two fields may indicate a time domain resource for a corresponding PDSCH. In this way, the time domain resource may be scheduled by different fields of the DCI.
[0157] In some example embodiments, the at least two PDSCHs may be successively located between the two PDCCH candidates without a gap between these PDSCHs. For example, as shown in FIG. 8A, there may be no gap between the scheduled symbols of the PDSCH 506 and the PDSCH 508.
[0158] In some example embodiments, the two PDCCH candidates may satisfy that the first PDCCH candidate starts at the very first available symbol of the slot. Alternatively, or additionally, the two PDCCH candidates may satisfy that the second PDCCH candidate ends at the very last available symbol of the slot. For example, as shown in FIG. 8B, the PDCCH candidate 502 may begin at the very first available symbol of a slot, and the PDCCH candidate 504 may end at the very last available symbol of the slot.
[0159] In some example embodiments, a time domain resource for the first PDSCH of the at least two PDSCHs may be indicated by the network device 120 to the terminal device 110, and a time domain resource for a PDSCH after the first PDSCH may be determined based on remaining symbols between the first PDSCH and the second PDCCH candidate. For example, the time domain resource of the PDSCH 506 may be scheduled by a DCI or higher layer. The time domain resource of the PDSCH 508 may be implicitly scheduled by the remaining symbols between the PDSCH 506 and the PDSCH 508.
[0160] FIG. 9 illustrates a flowchart of a communication method 900 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 900 will be described from the perspective of the terminal device 110 in FIG. 1.
[0161] At block 910, the terminal device 110 receives, from a network device, two PDCCH candidates and at least one PDSCH scheduled by the two PDCCH candidates, wherein the two PDCCH candidates are located within a same slot, the second PDCCH candidate of the two PDCCH candidates is a repetition of the first PDCCH candidate of the two PDCCH candidates, and the at least one PDSCH is located between the two PDCCH candidates in time domain.
[0162] At block 920, the terminal device 110 decodes the at least one PDSCH based on DCI in the two PDCCH candidates.
[0163] In some example embodiments, a separation in time domain between the two PDCCH candidates is not smaller than a total duration of the at least one PDSCH.
[0164] In some example embodiments, the two PDCCH candidates are associated with a same search space set, and the separation is indicated by at least one of: a gap in a number of symbols, or respective bitmaps for the two PDCCH candidates, a bitmap representing symbols occupied by a respective PDCCH within the slot.
[0165] In some example embodiments, the two PDCCH candidates are associated with different search space sets, and the separation is indicated by at least one of: a gap in a number of symbols, or respective bitmaps for the two PDCCH candidates, a bitmap representing symbols occupied by a respective PDCCH within the slot.
[0166] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and the total duration of the at least two PDSCHs is defined as starting at the first symbol of the first PDSCH of the at least two PDSCHs in time domain and ending at the last symbol of the last PDSCH of the at least two PDSCHs in time domain.
[0167] In some example embodiments, the at least one PDSCH comprises two PDSCHs with the second PDSCH in time domain being a repetition of the first PDSCH, and the total duration of the two PDSCHs is determined based on: a time duration of a PDSCH of the two PDSCHs, and a time offset between the two PDSCHs.
[0168] In some example embodiments, the time offset between the two PDSCHs is determined by at least one of: a time difference between a first starting symbol of the first PDSCH and a second starting symbol for the second PDSCH, or a time difference between a first reference point for the first starting symbol and a second reference point for the second starting symbol.
[0169] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and the at least two PDSCHs are partially or fully overlapped in time domain, and non-overlapped in frequency domain.
[0170] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and a time offset of a PDSCH after the first PDSCH with respect to the first PDSCH is larger than or equal to zero symbol.
[0171] In some example embodiments, the time offset is smaller than a time duration of the first PDSCH.
[0172] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and a frequency offset of a PDSCH after the first PDSCH with respect to the first PDSCH is larger than one resource block.
[0173] In some example embodiments, a reference point for a starting symbol of the first PDSCH of the at least one PDSCH is determined based on: a PDCCH candidate of the two PDCCH candidates that starts earlier in time domain, or a start of the slot.
[0174] In some example embodiments, the two PDCCH candidates are associated with a same search space set, or the two PDCCH candidates are associated with two search space sets respectively, wherein the two search space sets are of the same type and have different configurations.
[0175] In some example embodiments, the two PDCCH candidates are associated with two search spaces in the same search space set respectively, wherein the two search spaces have different configurations.
[0176] In some example embodiments, the terminal device 110 receives, from the network device, a common indication indicative of activation of both PDCCH repetition and PDSCH repetition or deactivation of both PDCCH repetition and PDSCH repetition.
[0177] In some example embodiments, the common indication comprises: an explicit indication indicative of activation of the PDCCH repetition or deactivation of the PDCCH repetition, or an explicit indication indicative of activation of the PDSCH repetition or deactivation of the PDSCH repetition.
[0178] In some example embodiments, the terminal device 110 receives, from the network device, a first indication indicative of activation of PDCCH repetition or deactivation of the PDCCH repetition; and receives, from the network device, a second indication indicative of activation of PDSCH repetition or deactivation of the PDSCH repetition.
[0179] In some example embodiments, the first indication is comprised in system information block 1, and the second indication is comprised in downlink control information scheduling PDSCH transmission.
[0180] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and the terminal device 110 receives, from the network device, an information element comprising a parameter set indicating time domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the parameter set comprises a parameter indicating a time domain resource for the PDSCH, or receive, from the network device, an information element comprising at least two parameters corresponding to the at least two PDSCHs respectively, wherein a parameter of the at least two parameters indicates a time domain resource for a corresponding PDSCH.
[0181] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and the terminal device 110 receives, from the network device, an information element comprising a bitmap set indicating frequency domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the bitmap set comprises a bitmap indicating a frequency domain resource for the PDSCH, or receives, from the network device, an information element comprising at least two bitmaps corresponding to the at least two PDSCHs respectively, wherein a bitmap of the at least two bitmaps indicates a frequency domain resource for a corresponding PDSCH, or receives, from the network device, an information element comprising a bitmap indicating frequency domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the bitmap comprises one or more bits indicating a frequency domain resource for the PDSCH.
[0182] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and the terminal device 110 receives, from the network device, an information element comprising an indication of a time offset between the at least two PDSCHs.
[0183] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and downlink control information scheduling the at least two PDSCHs comprises at least one of: an indication of a time offset between the at least two PDSCHs, or an indication of a frequency offset between the at least two PDSCHs.
[0184] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and downlink control information scheduling the at least two PDSCHs comprises a parameter indicating a time domain resource for a PDSCH after the first PDSCH of the at least two PDSCHs in time domain.
[0185] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and the terminal device 110 determines a time offset between the at least two PDSCHs based on at least one of: a search space type for the two PDCCH candidates and first mapping from different PDCCH search space types to different time offset values, or a type of Radio Network Temporary Identifier (RNTI) associated with the two PDCCHs and second mapping from different RNTI types to different time offset values.
[0186] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and the terminal device 110 determines a frequency offset between the at least two PDSCHs based on at least one of: a search space type for the two PDCCH candidates and third mapping from different PDCCH search space types to different frequency offset values, or a type of RNTI associated with the two PDCCHs and fourth mapping from different RNTI types to different frequency offset values.
[0187] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs that are successively located between the two PDCCH candidates.
[0188] In some example embodiments, the at least two PDSCHs occupy the same frequency domain resource.
[0189] In some example embodiments, a time duration of a PDSCH after the first PDSCH of the at least two PDSCHs is different from a time duration of the first PDSCH.
[0190] In some example embodiments, downlink control information scheduling the at least two PDSCHs comprises at least two fields corresponding to the at least two PDSCHs, and a field of the at least two fields indicates a time domain resource for a corresponding PDSCH.
[0191] In some example embodiments, the at least two PDSCHs are successively located between the two PDCCH candidates without a gap between the at least two PDSCHs.
[0192] In some example embodiments, the two PDCCH candidates satisfy at least one of: that the first PDCCH candidate starts at the very first available symbol of the slot, or that the second PDCCH candidate ends at the very last available symbol of the slot.
[0193] In some example embodiments, a time domain resource for the first PDSCH of the at least two PDSCHs is indicated by the network device to the terminal device, and a time domain resource for a PDSCH after the first PDSCH is determined based on remaining symbols between the first PDSCH and the second PDCCH candidate.
[0194] FIG. 10 illustrates a flowchart of a communication method 1000 implemented at a network device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 1000 will be described from the perspective of the network device 120 in FIG. 1.
[0195] At block 1010, the network device 120 encodes at least one PDSCH scheduled by two PDCCH candidates located within a same slot based on DCI in the two PDCCH candidates.
[0196] At block 1020, the network device 120 transmits, to a terminal device, the two PDCCH candidates and at least one PDSCH, wherein the second PDCCH candidate of the two PDCCH candidates is a repetition of the first PDCCH candidate of the two PDCCH candidates, and the at least one PDSCH is located between the two PDCCH candidates in time domain.
[0197] In some example embodiments, a separation in time domain between the two PDCCH candidates is not smaller than a total duration of the at least one PDSCH.
[0198] In some example embodiments, the two PDCCH candidates are associated with a same search space set, and the separation is indicated by at least one of: a gap in a number of symbols, or respective bitmaps for the two PDCCH candidates, a bitmap representing symbols occupied by a respective PDCCH within the slot.
[0199] In some example embodiments, the two PDCCH candidates are associated with different search space sets, and the separation is indicated by at least one of: a gap in a number of symbols, or respective bitmaps for the two PDCCH candidates, a bitmap representing symbols occupied by a respective PDCCH within the slot.
[0200] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and the total duration of the at least two PDSCHs is defined as starting at the first symbol of the first PDSCH of the at least two PDSCHs in time domain and ending at the last symbol of the last PDSCH of the at least two PDSCHs in time domain.
[0201] In some example embodiments, the at least one PDSCH comprises two PDSCHs with the second PDSCH in time domain being a repetition of the first PDSCH, and the total duration of the two PDSCHs is determined based on: a time duration of a PDSCH of the two PDSCHs, and a time offset between the two PDSCHs.
[0202] In some example embodiments, the time offset between the two PDSCHs is determined by at least one of: a time difference between a first starting symbol of the first PDSCH and a second starting symbol for the second PDSCH, or a time difference between a first reference point for the first starting symbol and a second reference point for the second starting symbol.
[0203] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and the at least two PDSCHs are partially or fully overlapped in time domain, and non-overlapped in frequency domain.
[0204] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain respective repetitions respective repetitions of the first PDSCH, and a time offset of a PDSCH after the first PDSCH with respect to the first PDSCH is larger than or equal to zero symbol.
[0205] In some example embodiments, the time offset is smaller than a time duration of the first PDSCH.
[0206] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and a frequency offset of a PDSCH after the first PDSCH with respect to the first PDSCH is larger than one resource block.
[0207] In some example embodiments, a reference point for a starting symbol of the first PDSCH of the at least one PDSCH is determined based on: a PDCCH candidate of the two PDCCH candidates that starts earlier in time domain, or a start of the slot.
[0208] In some example embodiments, the two PDCCH candidates are associated with a same search space set, or the two PDCCH candidates are associated with two search space sets respectively, wherein the two search space sets are of the same type and have different configurations.
[0209] In some example embodiments, the two PDCCH candidates are associated with two search spaces in the same search space set respectively, wherein the two search spaces have different configurations.
[0210] In some example embodiments, the network device 120 transmits, to the terminal device, a common indication indicative of activation of both PDCCH repetition and PDSCH repetition or deactivation of both PDCCH repetition and PDSCH repetition.
[0211] In some example embodiments, the common indication comprises: an explicit indication indicative of activation of the PDCCH repetition or deactivation of the PDCCH repetition, or an explicit indication indicative of activation of the PDSCH repetition or deactivation of the PDSCH repetition.
[0212] In some example embodiments, the network device 120 transmits, to the terminal device, a first indication indicative of activation of PDCCH repetition or deactivation of the PDCCH repetition; and transmit, to the terminal device, a second indication indicative of activation of PDSCH repetition or deactivation of the PDSCH repetition.
[0213] In some example embodiments, the first indication is comprised in system information block 1, and the second indication is comprised in downlink control information scheduling PDSCH transmission.
[0214] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and the network device 120 transmits, to the terminal device, an information element comprising a parameter set indicating time domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the parameter set comprises a parameter indicating a time domain resource for the PDSCH, or transmit, to the terminal device, an information element comprising at least two parameters corresponding to the at least two PDSCHs respectively, wherein a parameter of the at least two parameters indicates a time domain resource for a corresponding PDSCH.
[0215] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and the network device 120 transmits, to the terminal device, an information element comprising a bitmap set indicating frequency domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the bitmap set comprises a bitmap indicating a frequency domain resource for the PDSCH, or transmits, to the terminal device, an information element comprising at least two bitmaps corresponding to the at least two PDSCHs respectively, wherein a bitmap of the at least two bitmaps indicates a frequency domain resource for a corresponding PDSCH, or transmits, to the terminal device, an information element comprising a bitmap indicating frequency domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the bitmap comprises one or more bits indicating a frequency domain resource for the PDSCH.
[0216] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and the network device 120 transmits, to the terminal device, an information element comprising an indication of a time offset between the at least two PDSCHs.
[0217] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and downlink control information scheduling the at least two PDSCHs comprises at least one of: an indication of a time offset between the at least two PDSCHs, or an indication of a frequency offset between the at least two PDSCHs.
[0218] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and downlink control information scheduling the at least two PDSCHs comprises a parameter indicating a time domain resource for a PDSCH after the first PDSCH of the at least two PDSCHs in time domain.
[0219] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and the network device 120 determines a time offset between the at least two PDSCHs based on at least one of: a search space type for the two PDCCH candidates and first mapping from different PDCCH search space types to different time offset values, or a type of RNTI associated with the two PDCCHs and second mapping from different RNTI types to different time offset values.
[0220] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs, and the network device 120 determines a frequency offset between the at least two PDSCHs based on at least one of: a search space type for the two PDCCH candidates and third mapping from different PDCCH search space types to different frequency offset values, or a type of RNTI associated with the two PDCCHs and fourth mapping from different RNTI types to different frequency offset values.
[0221] In some example embodiments, the at least one PDSCH comprises at least two PDSCHs that are successively located between the two PDCCH candidates.
[0222] In some example embodiments, the at least two PDSCHs occupy the same frequency domain resource.
[0223] In some example embodiments, a time duration of a PDSCH after the first PDSCH of the at least two PDSCHs is different from a time duration of the first PDSCH.
[0224] In some example embodiments, downlink control information scheduling the at least two PDSCHs comprises at least two fields corresponding to the at least two PDSCHs, and a field of the at least two fields indicates a time domain resource for a corresponding PDSCH.
[0225] In some example embodiments, the at least two PDSCHs are successively located between the two PDCCH candidates without a gap between the at least two PDSCHs.
[0226] In some example embodiments, the two PDCCH candidates satisfy at least one of:that the first PDCCH candidate starts at the very first available symbol of the slot, or that the second PDCCH candidate ends at the very last available symbol of the slot.
[0227] In some example embodiments, a time domain resource for the first PDSCH of the at least two PDSCHs is indicated by the network device to the terminal device, and a time domain resource for a PDSCH after the first PDSCH is determined based on remaining symbols between the first PDSCH and the second PDCCH candidate.
[0228] FIG. 11 is a simplified block diagram of a device 1100 that is suitable for implementing embodiments of the present disclosure. The device 1100 can be considered as a further example implementation of any of the devices as shown in FIG. 1. Accordingly, the device 1100 can be implemented at or as at least a part of the terminal device 110 or the network device 120.
[0229] As shown, the device 1100 includes a processor 1110, a memory 1120 coupled to the processor 1110, a suitable transceiver 1140 coupled to the processor 1110, and a communication interface coupled to the transceiver 1140. The memory 1120 stores at least a part of a program 1130. The transceiver 1140 may be for bidirectional communications or a unidirectional communication based on requirements. The transceiver 1140 may include at least one of a transmitter 1142 and a receiver 1144. The transmitter 1142 and the receiver 1144 may be functional modules or physical entities. The transceiver 1140 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones. The communication interface may represent any interface that is necessary for communication with other network elements, such as X2 / Xn interface for bidirectional communications between eNBs / gNBs, S1 / NG interface for communication between a Mobility Management Entity (MME) / Access and Mobility Management Function (AMF) / SGW / UPF and the eNB / gNB, Un interface for communication between the eNB / gNB and a relay node (RN) , or Uu interface for communication between the eNB / gNB and a terminal device.
[0230] The program 1130 is assumed to include program instructions that, when executed by the associated processor 1110, enable the device 1100 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGS. 1, 4 to 10. The embodiments herein may be implemented by computer software executable by the processor 1110 of the device 1100, or by hardware, or by a combination of software and hardware. The processor 1110 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 1110 and memory 1120 may form processing means 1150 adapted to implement various embodiments of the present disclosure.
[0231] The memory 1120 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 1120 is shown in the device 1100, there may be several physically distinct memory modules in the device 1100. The processor 1110 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1100 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0232] According to embodiments of the present disclosure, a terminal device comprising a circuitry is provided. The circuitry is configured to: receive, from a network device, two PDCCH candidates and at least one PDSCH scheduled by the two PDCCH candidates, wherein the two PDCCH candidates are located within a same slot, the second PDCCH candidate of the two PDCCH candidates is a repetition of the first PDCCH candidate of the two PDCCH candidates, and the at least one PDSCH is located between the two PDCCH candidates in time domain; and decode the at least one PDSCH based on DCI in the two PDCCH candidates. According to embodiments of the present disclosure, the circuitry may be configured to perform any method implemented by the terminal device as discussed above.
[0233] According to embodiments of the present disclosure, a network device comprising a circuitry is provided. The circuitry is configured to: encode at least one PDSCH scheduled by two PDCCH candidates located within a same slot based on DCI in the two PDCCH candidates; and transmit, to a terminal device, the two PDCCH candidates and at least one PDSCH, wherein the second PDCCH candidate of the two PDCCH candidates is a repetition of the first PDCCH candidate of the two PDCCH candidates, and the at least one PDSCH is located between the two PDCCH candidates in time domain. According to embodiments of the present disclosure, the circuitry may be configured to perform any method implemented by the network device as discussed above.
[0234] The term “circuitry” used herein may refer to hardware circuits and / or combinations of hardware circuits and software. For example, the circuitry may be a combination of analog and / or digital hardware circuits with software / firmware. As a further example, the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions. In a still further example, the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software / firmware for operation, but the software may not be present when it is not needed for operation. As used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and / or firmware.
[0235] According to embodiments of the present disclosure, a terminal apparatus is provided. The terminal apparatus comprises means for receiving, from a network device, two PDCCH candidates and at least one PDSCH scheduled by the two PDCCH candidates, wherein the two PDCCH candidates are located within a same slot, the second PDCCH candidate of the two PDCCH candidates is a repetition of the first PDCCH candidate of the two PDCCH candidates, and the at least one PDSCH is located between the two PDCCH candidates in time domain; and means for decoding the at least one PDSCH based on DCI in the two PDCCH candidates. In some embodiments, the first apparatus may comprise means for performing the respective operations of the method 900. In some example embodiments, the first apparatus may further comprise means for performing other operations in some example embodiments of the method 900. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0236] According to embodiments of the present disclosure, a network apparatus is provided. The network apparatus comprises means for encoding at least one PDSCH scheduled by two PDCCH candidates located within a same slot based on DCI in the two PDCCH candidates; and means for transmitting, to a terminal device, the two PDCCH candidates and at least one PDSCH, wherein the second PDCCH candidate of the two PDCCH candidates is a repetition of the first PDCCH candidate of the two PDCCH candidates, and the at least one PDSCH is located between the two PDCCH candidates in time domain. In some embodiments, the second apparatus may comprise means for performing the respective operations of the method 1000. In some example embodiments, the second apparatus may further comprise means for performing other operations in some example embodiments of the method 1000. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.
[0237] In summary, embodiments of the present disclosure provide the following aspects.
[0238] In an aspect, it is proposed a terminal device comprising: a processor configured to cause the terminal device to: receive, from a network device, two PDCCH candidates and at least one PDSCH scheduled by the two PDCCH candidates, wherein the two PDCCH candidates are located within a same slot, the second PDCCH candidate of the two PDCCH candidates is a repetition of the first PDCCH candidate of the two PDCCH candidates, and the at least one PDSCH is located between the two PDCCH candidates in time domain; and decode the at least one PDSCH based on DCI in the two PDCCH candidates.
[0239] In some embodiments, a separation in time domain between the two PDCCH candidates is not smaller than a total duration of the at least one PDSCH.
[0240] In some embodiments, the two PDCCH candidates are associated with a same search space set, and the separation is indicated by at least one of: a gap in a number of symbols, or respective bitmaps for the two PDCCH candidates, a bitmap representing symbols occupied by a respective PDCCH within the slot.
[0241] In some embodiments, the two PDCCH candidates are associated with different search space sets, and the separation is indicated by at least one of: a gap in a number of symbols, or respective bitmaps for the two PDCCH candidates, a bitmap representing symbols occupied by a respective PDCCH within the slot.
[0242] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and the total duration of the at least two PDSCHs is defined as starting at the first symbol of the first PDSCH of the at least two PDSCHs in time domain and ending at the last symbol of the last PDSCH of the at least two PDSCHs in time domain.
[0243] In some embodiments, the at least one PDSCH comprises two PDSCHs with the second PDSCH in time domain being a repetition of the first PDSCH, and the total duration of the two PDSCHs is determined based on: a time duration of a PDSCH of the two PDSCHs, and a time offset between the two PDSCHs.
[0244] In some embodiments, the time offset between the two PDSCHs is determined by at least one of: a time difference between a first starting symbol of the first PDSCH and a second starting symbol for the second PDSCH, or a time difference between a first reference point for the first starting symbol and a second reference point for the second starting symbol.
[0245] In some embodiments, the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and the at least two PDSCHs are partially or fully overlapped in time domain, and non-overlapped in frequency domain.
[0246] In some embodiments, the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and a time offset of a PDSCH after the first PDSCH with respect to the first PDSCH is larger than or equal to zero symbol.
[0247] In some embodiments, the time offset is smaller than a time duration of the first PDSCH.
[0248] In some embodiments, the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and a frequency offset of a PDSCH after the first PDSCH with respect to the first PDSCH is larger than one resource block.
[0249] In some embodiments, a reference point for a starting symbol of the first PDSCH of the at least one PDSCH is determined based on: a PDCCH candidate of the two PDCCH candidates that starts earlier in time domain, or a start of the slot.
[0250] In some embodiments, the two PDCCH candidates are associated with a same search space set, or the two PDCCH candidates are associated with two search space sets respectively, wherein the two search space sets are of the same type and have different configurations.
[0251] In some embodiments, the two PDCCH candidates are associated with two search spaces in the same search space set respectively, wherein the two search spaces have different configurations.
[0252] In some embodiments, the terminal device is further caused to: receive, from the network device, a common indication indicative of activation of both PDCCH repetition and PDSCH repetition or deactivation of both PDCCH repetition and PDSCH repetition.
[0253] In some embodiments, the common indication comprises: an explicit indication indicative of activation of the PDCCH repetition or deactivation of the PDCCH repetition, or an explicit indication indicative of activation of the PDSCH repetition or deactivation of the PDSCH repetition.
[0254] In some embodiments, the terminal device is further caused to: receive, from the network device, a first indication indicative of activation of PDCCH repetition or deactivation of the PDCCH repetition; and receive, from the network device, a second indication indicative of activation of PDSCH repetition or deactivation of the PDSCH repetition.
[0255] In some embodiments, the first indication is comprised in system information block 1, and the second indication is comprised in downlink control information scheduling PDSCH transmission.
[0256] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and the terminal device is further caused to: receive, from the network device, an information element comprising a parameter set indicating time domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the parameter set comprises a parameter indicating a time domain resource for the PDSCH, or receive, from the network device, an information element comprising at least two parameters corresponding to the at least two PDSCHs respectively, wherein a parameter of the at least two parameters indicates a time domain resource for a corresponding PDSCH.
[0257] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and the terminal device is further caused to: receive, from the network device, an information element comprising a bitmap set indicating frequency domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the bitmap set comprises a bitmap indicating a frequency domain resource for the PDSCH, or receive, from the network device, an information element comprising at least two bitmaps corresponding to the at least two PDSCHs respectively, wherein a bitmap of the at least two bitmaps indicates a frequency domain resource for a corresponding PDSCH, or receive, from the network device, an information element comprising a bitmap indicating frequency domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the bitmap comprises one or more bits indicating a frequency domain resource for the PDSCH.
[0258] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and the terminal device is further caused to: receive, from the network device, an information element comprising an indication of a time offset between the at least two PDSCHs.
[0259] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and downlink control information scheduling the at least two PDSCHs comprises at least one of: an indication of a time offset between the at least two PDSCHs, or an indication of a frequency offset between the at least two PDSCHs.
[0260] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and downlink control information scheduling the at least two PDSCHs comprises a parameter indicating a time domain resource for a PDSCH after the first PDSCH of the at least two PDSCHs in time domain.
[0261] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and the terminal device is further caused to: determine a time offset between the at least two PDSCHs based on at least one of: a search space type for the two PDCCH candidates and first mapping from different PDCCH search space types to different time offset values, or a type of RNTI associated with the two PDCCHs and second mapping from different RNTI types to different time offset values.
[0262] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and the terminal device is further caused to: determine a frequency offset between the at least two PDSCHs based on at least one of: a search space type for the two PDCCH candidates and third mapping from different PDCCH search space types to different frequency offset values, or a type of RNTI associated with the two PDCCHs and fourth mapping from different RNTI types to different frequency offset values.
[0263] In some embodiments, the at least one PDSCH comprises at least two PDSCHs that are successively located between the two PDCCH candidates.
[0264] In some embodiments, the at least two PDSCHs occupy the same frequency domain resource.
[0265] In some embodiments, a time duration of a PDSCH after the first PDSCH of the at least two PDSCHs is different from a time duration of the first PDSCH.
[0266] In some embodiments, downlink control information scheduling the at least two PDSCHs comprises at least two fields corresponding to the at least two PDSCHs, and a field of the at least two fields indicates a time domain resource for a corresponding PDSCH.
[0267] In some embodiments, the at least two PDSCHs are successively located between the two PDCCH candidates without a gap between the at least two PDSCHs.
[0268] In some embodiments, the two PDCCH candidates satisfy at least one of: that the first PDCCH candidate starts at the very first available symbol of the slot, or that the second PDCCH candidate ends at the very last available symbol of the slot.
[0269] In some embodiments, a time domain resource for the first PDSCH of the at least two PDSCHs is indicated by the network device to the terminal device, and a time domain resource for a PDSCH after the first PDSCH is determined based on remaining symbols between the first PDSCH and the second PDCCH candidate.
[0270] In an aspect, it is proposed a network device comprising: a processor configured to cause the network device to: encode at least one PDSCH scheduled by two PDCCH candidates located within a same slot based on DCI in the two PDCCH candidates; and transmit, to a terminal device, the two PDCCH candidates and at least one PDSCH, wherein the second PDCCH candidate of the two PDCCH candidates is a repetition of the first PDCCH candidate of the two PDCCH candidates, and the at least one PDSCH is located between the two PDCCH candidates in time domain.
[0271] In some embodiments, a separation in time domain between the two PDCCH candidates is not smaller than a total duration of the at least one PDSCH.
[0272] In some embodiments, the two PDCCH candidates are associated with a same search space set, and the separation is indicated by at least one of: a gap in a number of symbols, or respective bitmaps for the two PDCCH candidates, a bitmap representing symbols occupied by a respective PDCCH within the slot.
[0273] In some embodiments, the two PDCCH candidates are associated with different search space sets, and the separation is indicated by at least one of: a gap in a number of symbols, or respective bitmaps for the two PDCCH candidates, a bitmap representing symbols occupied by a respective PDCCH within the slot.
[0274] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and the total duration of the at least two PDSCHs is defined as starting at the first symbol of the first PDSCH of the at least two PDSCHs in time domain and ending at the last symbol of the last PDSCH of the at least two PDSCHs in time domain.
[0275] In some embodiments, the at least one PDSCH comprises two PDSCHs with the second PDSCH in time domain being a repetition of the first PDSCH, and the total duration of the two PDSCHs is determined based on: a time duration of a PDSCH of the two PDSCHs, and a time offset between the two PDSCHs.
[0276] In some embodiments, the time offset between the two PDSCHs is determined by at least one of: a time difference between a first starting symbol of the first PDSCH and a second starting symbol for the second PDSCH, or a time difference between a first reference point for the first starting symbol and a second reference point for the second starting symbol.
[0277] In some embodiments, the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and the at least two PDSCHs are partially or fully overlapped in time domain, and non-overlapped in frequency domain.
[0278] In some embodiments, the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain respective repetitions respective repetitions of the first PDSCH, and a time offset of a PDSCH after the first PDSCH with respect to the first PDSCH is larger than or equal to zero symbol.
[0279] In some embodiments, the time offset is smaller than a time duration of the first PDSCH.
[0280] In some embodiments, the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and a frequency offset of a PDSCH after the first PDSCH with respect to the first PDSCH is larger than one resource block.
[0281] In some embodiments, a reference point for a starting symbol of the first PDSCH of the at least one PDSCH is determined based on: a PDCCH candidate of the two PDCCH candidates that starts earlier in time domain, or a start of the slot.
[0282] In some embodiments, the two PDCCH candidates are associated with a same search space set, or the two PDCCH candidates are associated with two search space sets respectively, wherein the two search space sets are of the same type and have different configurations.
[0283] In some embodiments, the two PDCCH candidates are associated with two search spaces in the same search space set respectively, wherein the two search spaces have different configurations.
[0284] In some embodiments, the terminal device is further caused to: transmit, to the terminal device, a common indication indicative of activation of both PDCCH repetition and PDSCH repetition or deactivation of both PDCCH repetition and PDSCH repetition.
[0285] In some embodiments, the common indication comprises: an explicit indication indicative of activation of the PDCCH repetition or deactivation of the PDCCH repetition, or an explicit indication indicative of activation of the PDSCH repetition or deactivation of the PDSCH repetition.
[0286] In some embodiments, the network device is further caused to: transmit, to the terminal device, a first indication indicative of activation of PDCCH repetition or deactivation of the PDCCH repetition; and transmit, to the terminal device, a second indication indicative of activation of PDSCH repetition or deactivation of the PDSCH repetition.
[0287] In some embodiments, the first indication is comprised in system information block 1, and the second indication is comprised in downlink control information scheduling PDSCH transmission.
[0288] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and the network device is further caused to: transmit, to the terminal device, an information element comprising a parameter set indicating time domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the parameter set comprises a parameter indicating a time domain resource for the PDSCH, or transmit, to the terminal device, an information element comprising at least two parameters corresponding to the at least two PDSCHs respectively, wherein a parameter of the at least two parameters indicates a time domain resource for a corresponding PDSCH.
[0289] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and the network device is further caused to: transmit, to the terminal device, an information element comprising a bitmap set indicating frequency domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the bitmap set comprises a bitmap indicating a frequency domain resource for the PDSCH, or transmit, to the terminal device, an information element comprising at least two bitmaps corresponding to the at least two PDSCHs respectively, wherein a bitmap of the at least two bitmaps indicates a frequency domain resource for a corresponding PDSCH, or transmit, to the terminal device, an information element comprising a bitmap indicating frequency domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the bitmap comprises one or more bits indicating a frequency domain resource for the PDSCH.
[0290] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and the network device is further caused to: transmit, to the terminal device, an information element comprising an indication of a time offset between the at least two PDSCHs.
[0291] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and downlink control information scheduling the at least two PDSCHs comprises at least one of: an indication of a time offset between the at least two PDSCHs, or an indication of a frequency offset between the at least two PDSCHs.
[0292] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and downlink control information scheduling the at least two PDSCHs comprises a parameter indicating a time domain resource for a PDSCH after the first PDSCH of the at least two PDSCHs in time domain.
[0293] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and the network device is further caused to: determine a time offset between the at least two PDSCHs based on at least one of: a search space type for the two PDCCH candidates and first mapping from different PDCCH search space types to different time offset values, or a type of RNTI associated with the two PDCCHs and second mapping from different RNTI types to different time offset values.
[0294] In some embodiments, the at least one PDSCH comprises at least two PDSCHs, and the network device is further caused to: determine a frequency offset between the at least two PDSCHs based on at least one of: a search space type for the two PDCCH candidates and third mapping from different PDCCH search space types to different frequency offset values, or a type of RNTI associated with the two PDCCHs and fourth mapping from different RNTI types to different frequency offset values.
[0295] In some embodiments, the at least one PDSCH comprises at least two PDSCHs that are successively located between the two PDCCH candidates.
[0296] In some embodiments, the at least two PDSCHs occupy the same frequency domain resource.
[0297] In some embodiments, a time duration of a PDSCH after the first PDSCH of the at least two PDSCHs is different from a time duration of the first PDSCH.
[0298] In some embodiments, downlink control information scheduling the at least two PDSCHs comprises at least two fields corresponding to the at least two PDSCHs, and a field of the at least two fields indicates a time domain resource for a corresponding PDSCH.
[0299] In some embodiments, the at least two PDSCHs are successively located between the two PDCCH candidates without a gap between the at least two PDSCHs.
[0300] In some embodiments, the two PDCCH candidates satisfy at least one of: that the first PDCCH candidate starts at the very first available symbol of the slot, or that the second PDCCH candidate ends at the very last available symbol of the slot.
[0301] In some embodiments, a time domain resource for the first PDSCH of the at least two PDSCHs is indicated by the network device to the terminal device, and a time domain resource for a PDSCH after the first PDSCH is determined based on remaining symbols between the first PDSCH and the second PDCCH candidate.
[0302] In an aspect, a terminal device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the terminal device discussed above.
[0303] In an aspect, a network device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the network device discussed above.
[0304] In an aspect, a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the terminal device discussed above.
[0305] In an aspect, a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the network device discussed above.
[0306] In an aspect, a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the terminal device discussed above.
[0307] In an aspect, a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the network device discussed above.
[0308] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0309] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGS. 1 to 11. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0310] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0311] The above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine readable medium may be a machine readable signal medium or a machine readable storage medium. A machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0312] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.
[0313] Although the present disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims
1.A terminal device comprising:a processor configured to cause the terminal device to:receive, from a network device, two physical downlink control channel (PDCCH) candidates and at least one physical downlink shared channel (PDSCH) scheduled by the two PDCCH candidates, wherein the two PDCCH candidates are located within a same slot, the second PDCCH candidate of the two PDCCH candidates is a repetition of the first PDCCH candidate of the two PDCCH candidates, and the at least one PDSCH is located between the two PDCCH candidates in time domain; anddecode the at least one PDSCH based on downlink control information (DCI) in the two PDCCH candidates.2.The terminal device of claim 1, wherein a separation in time domain between the two PDCCH candidates is not smaller than a total duration of the at least one PDSCH.3.The terminal device of claim 2, wherein the two PDCCH candidates are associated with a same search space set, and the separation is indicated by at least one of:a gap in a number of symbols, orrespective bitmaps for the two PDCCH candidates, a bitmap representing symbols occupied by a respective PDCCH within the slot.4.The terminal device of claim 2, wherein the two PDCCH candidates are associated with different search space sets, and the separation is indicated by at least one of:a gap in a number of symbols, orrespective bitmaps for the two PDCCH candidates, a bitmap representing symbols occupied by a respective PDCCH within the slot.5.The terminal device of claim 2, wherein the at least one PDSCH comprises at least two PDSCHs, and the total duration of the at least two PDSCHs is defined as starting at the first symbol of the first PDSCH of the at least two PDSCHs in time domain and ending at the last symbol of the last PDSCH of the at least two PDSCHs in time domain.6.The terminal device of claim 2, wherein the at least one PDSCH comprises two PDSCHs with the second PDSCH in time domain being a repetition of the first PDSCH, and the total duration of the two PDSCHs is determined based on:a time duration of a PDSCH of the two PDSCHs, anda time offset between the two PDSCHs.7.The terminal device of claim 6, wherein the time offset between the two PDSCHs is determined by at least one of:a time difference between a first starting symbol of the first PDSCH and a second starting symbol for the second PDSCH, ora time difference between a first reference point for the first starting symbol and a second reference point for the second starting symbol.8.The terminal device of claim 1, wherein the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and the at least two PDSCHs are partially or fully overlapped in time domain, and non-overlapped in frequency domain.9.The terminal device of claim 1, wherein the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and a time offset of a PDSCH after the first PDSCH with respect to the first PDSCH is larger than or equal to zero symbol.10.The terminal device of claim 9, wherein the time offset is smaller than a time duration of the first PDSCH.11.The terminal device of claim 1, wherein the at least one PDSCH comprises at least two PDSCHs with one or more PDSCHs after the first PDSCH in time domain being respective repetitions of the first PDSCH, and a frequency offset of a PDSCH after the first PDSCH with respect to the first PDSCH is larger than one resource block.12.The terminal device of claim 1, wherein a reference point for a starting symbol of the first PDSCH of the at least one PDSCH is determined based on:a PDCCH candidate of the two PDCCH candidates that starts earlier in time domain, ora start of the slot.13.The terminal device of claim 12, wherein the two PDCCH candidates are associated with a same search space set, orthe two PDCCH candidates are associated with two search space sets respectively, wherein the two search space sets are of the same type and have different configurations.14.The terminal device of claim 13, wherein the two PDCCH candidates are associated with two search spaces in the same search space set respectively, wherein the two search spaces have different configurations.15.The terminal device of claim 1, wherein the terminal device is further caused to:receive, from the network device, a common indication indicative of activation of both PDCCH repetition and PDSCH repetition or deactivation of both PDCCH repetition and PDSCH repetition.16.The terminal device of claim 15, wherein the common indication comprises:an explicit indication indicative of activation of the PDCCH repetition or deactivation of the PDCCH repetition, oran explicit indication indicative of activation of the PDSCH repetition or deactivation of the PDSCH repetition.17.The terminal device of claim 1, wherein the terminal device is further caused to:receive, from the network device, a first indication indicative of activation of PDCCH repetition or deactivation of the PDCCH repetition; andreceive, from the network device, a second indication indicative of activation of PDSCH repetition or deactivation of the PDSCH repetition.18.The terminal device of claim 17, wherein the first indication is comprised in system information block 1, and the second indication is comprised in downlink control information scheduling PDSCH transmission.19.The terminal device of claim 1, wherein the at least one PDSCH comprises at least two PDSCHs, and the terminal device is further caused to:receive, from the network device, an information element comprising a parameter set indicating time domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the parameter set comprises a parameter indicating a time domain resource for the PDSCH, orreceive, from the network device, an information element comprising at least two parameters corresponding to the at least two PDSCHs respectively, wherein a parameter of the at least two parameters indicates a time domain resource for a corresponding PDSCH.20.The terminal device of claim 1, wherein the at least one PDSCH comprises at least two PDSCHs, and the terminal device is further caused to:receive, from the network device, an information element comprising a bitmap set indicating frequency domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the bitmap set comprises a bitmap indicating a frequency domain resource for the PDSCH, orreceive, from the network device, an information element comprising at least two bitmaps corresponding to the at least two PDSCHs respectively, wherein a bitmap of the at least two bitmaps indicates a frequency domain resource for a corresponding PDSCH, orreceive, from the network device, an information element comprising a bitmap indicating frequency domain resources for the at least two PDSCHs, wherein for each PDSCH of the at least two PDSCHs, the bitmap comprises one or more bits indicating a frequency domain resource for the PDSCH.21.The terminal device of claim 1, wherein the at least one PDSCH comprises at least two PDSCHs, and the terminal device is further caused to:receive, from the network device, an information element comprising an indication of a time offset between the at least two PDSCHs.22.The terminal device of claim 1, wherein the at least one PDSCH comprises at least two PDSCHs, and downlink control information scheduling the at least two PDSCHs comprises at least one of:an indication of a time offset between the at least two PDSCHs, oran indication of a frequency offset between the at least two PDSCHs.23.The terminal device of claim 1, wherein the at least one PDSCH comprises at least two PDSCHs, and downlink control information scheduling the at least two PDSCHs comprises a parameter indicating a time domain resource for a PDSCH after the first PDSCH of the at least two PDSCHs in time domain.24.The terminal device of claim 1, wherein the at least one PDSCH comprises at least two PDSCHs, and the terminal device is further caused to:determine a time offset between the at least two PDSCHs based on at least one of:a search space type for the two PDCCH candidates and first mapping from different PDCCH search space types to different time offset values, ora type of radio network temporary identifier (RNTI) associated with the two PDCCHs and second mapping from different RNTI types to different time offset values.25.The terminal device of claim 1, wherein the at least one PDSCH comprises at least two PDSCHs, and the terminal device is further caused to:determine a frequency offset between the at least two PDSCHs based on at least one of:a search space type for the two PDCCH candidates and third mapping from different PDCCH search space types to different frequency offset values, ora type of radio network temporary identifier (RNTI) associated with the two PDCCHs and fourth mapping from different RNTI types to different frequency offset values.26.The terminal device of claim 1, wherein the at least one PDSCH comprises at least two PDSCHs that are successively located between the two PDCCH candidates.27.The terminal device of claim 26, wherein the at least two PDSCHs occupy the same frequency domain resource.28.The terminal device of claim 26, wherein a time duration of a PDSCH after the first PDSCH of the at least two PDSCHs is different from a time duration of the first PDSCH.29.The terminal device of claim 26, wherein downlink control information scheduling the at least two PDSCHs comprises at least two fields corresponding to the at least two PDSCHs, and a field of the at least two fields indicates a time domain resource for a corresponding PDSCH.30.The terminal device of claim 26, wherein the at least two PDSCHs are successively located between the two PDCCH candidates without a gap between the at least two PDSCHs.31.The terminal device of claim 1, wherein the two PDCCH candidates satisfy at least one of:that the first PDCCH candidate starts at the very first available symbol of the slot, orthat the second PDCCH candidate ends at the very last available symbol of the slot.32.The terminal device of claim 26, wherein a time domain resource for the first PDSCH of the at least two PDSCHs is indicated by the network device to the terminal device, anda time domain resource for a PDSCH after the first PDSCH is determined based on remaining symbols between the first PDSCH and the second PDCCH candidate.
