Method and apparatus for cross-carrier scheduling considering multiple transmit-receive points

Abstract

The present invention discloses, from the perspective of a network in a wireless communication system, a method and an apparatus for performing cross-carrier scheduling considering multiple transmission and reception points. In one embodiment, the method includes the network configuring cross-carrier scheduling for a user equipment, where the network transmits a physical downlink control channel on a first cell that schedules a second cell. The method further includes the network configuring physical downlink control channel repetition on two search spaces of the first cell for the user equipment. Additionally, the method includes the network being allowed to configure physical downlink control channel repetition on two search spaces of the second cell for the user equipment only when two search spaces of the first cell having the same search space identity as the two search spaces of the second cell have been configured to have physical downlink control channel repetition.

Description

Technical Field

[0001] The present disclosure generally relates to wireless communication networks, and more particularly, to methods and apparatuses for cross-carrier scheduling considering multi-Transmission and Reception Points (multi-TRP) in a wireless communication system. Background Art

[0002] With the rapid growth of the demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks for communicating Internet Protocol (IP) data packets. This IP data packet communication can provide IP-borne voice, multimedia, multicast, and on-demand communication services for users of mobile communication devices.

[0003] An exemplary network architecture is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput to enable the above-mentioned IP-borne voice and multimedia services. Currently, the 3GPP standard organization is discussing new next-generation (e.g., 5G) radio technologies. Therefore, changes to the current body of the 3GPP standard are currently being submitted and considered to evolve and complete the 3GPP standard. Summary of the Invention

[0004] A method and an apparatus are disclosed from the perspective of a network in a wireless communication system. In one embodiment, the method includes the network configuring cross-carrier scheduling for a User Equipment (UE), where the network transmits a Physical Downlink Control Channel (PDCCH) on a first cell scheduling a second cell. The method further includes the network configuring PDCCH repetition on two search spaces of the first cell for the UE. Additionally, the method includes the network being allowed to configure PDCCH repetition on two search spaces of the second cell for the UE only when two search spaces of the first cell having the same search space identity (ID) as the two search spaces of the second cell have been configured to have PDCCH repetition. Brief Description of the Drawings

[0005] Figure 1 A diagram showing a wireless communication system according to an exemplary embodiment.

[0006] Figure 2 A block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an exemplary embodiment.

[0007] Figure 3is a functional block diagram of a communication system according to an exemplary embodiment.

[0008] Figure 4 is according to an exemplary embodiment Figure 3 of the program code's functional block diagram.

[0009] Figure 5 is a reproduction of Table 7.3.1-1 in 3GPP TS 38.212.

[0010] Figure 6 is a reproduction of Table 10.1-2 in 3GPP TS 38.213 V16.3.0.

[0011] Figure 7 is a reproduction of Table 10.1-3 in 3GPP TS 38.213 V16.3.0.

[0012] Figure 8 is a diagram according to an exemplary embodiment.

[0013] Figure 9 is an information table according to an exemplary embodiment.

[0014] Figure 10 is a diagram according to an exemplary embodiment.

[0015] Figure 11 is a diagram according to an exemplary embodiment.

[0016] Figure 12 is a diagram according to an exemplary embodiment.

[0017] Figure 13 is a diagram according to an exemplary embodiment.

[0018] Figure 14 is a flowchart according to an exemplary embodiment.

[0019] Figure 15 is a flowchart according to an exemplary embodiment. Detailed Description

[0020] The exemplary wireless communication systems and devices described below employ a wireless communication system that supports broadcast services. Wireless communication systems have been widely deployed to provide various types of communications, such as voice, data, and the like. These systems may be based on Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Orthogonal Frequency Division Multiple Access (OFDMA), 3GPP Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A), 3GPP2 Ultra Mobile Broadband (UMB), WiMax, 3GPP New Radio (NR), or some other modulation techniques.

[0021] Specifically, the exemplary wireless communication system devices described below may be designed to support one or more standards, such as those provided by the consortium named "Third Generation Partnership Project" and referred to herein as 3GPP, including: TS 38.212 V16.2.0, "NR Multiplexing and Channel Coding (Release 16)"; TS 38.213 V16.3.0, "NR Physical Layer Procedures for Control (Release 16)"; RP-193133, "New WID: Further Enhancements for MIMO in NR", Samsung; TS 38.331 V16.2.0, "NR; Radio Resource Control (RRC) Protocol Specification (Release 16)"; the Final Report of 3GPP TSGRAN WG1 #102-e V1.0.0, (Online Meeting, August 17 - 28, 2020); Chairman's Notes RAN1 #103-e V033; Draft Report of 3GPP TSG RAN WG1 #104-e V0.3.0, (Online Meeting, January 25 - February 5, 2021); and Chairman's Notes RAN1 #104b-e V012. The standards and documents listed above are hereby expressly incorporated by reference in their entirety.

[0022] Figure 1 A multi-access wireless communication system according to an embodiment of the present invention is shown. The access network 100 (AN) includes a plurality of antenna groups, where one antenna group includes 104 and 106, another antenna group includes 108 and 110, and yet another antenna group includes 112 and 114. In Figure 1In this figure, only two antennas are shown for each antenna group, but each antenna group can utilize more or fewer antennas. The access terminal 116 communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to the access terminal 116 via the forward link 120 and receive information from the access terminal 116 via the reverse link 118. The access terminal 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to the access terminal 122 via the forward link 126 and receive information from the access terminal 122 via the reverse link 124. In an FDD system, the communication links 118, 120, 124, and 126 can use different frequencies for communication. For example, the forward link 120 can use a frequency different from the frequency used by the reverse link 118.

[0023] Each group of antennas and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, each antenna group is designed to communicate with access terminals in a sector of the area covered by the access network 100.

[0024] In the communication via the forward links 120 and 126, the transmitting antennas of the access network 100 can utilize beamforming to improve the signal-to-noise ratio of the forward links for different access terminals 116 and 122. Also, compared to an access network that transmits to all of its access terminals via a single antenna, the access network that uses beamforming to transmit to access terminals randomly dispersed throughout the entire coverage area of the access network causes less interference to the access terminals in adjacent cells.

[0025] The access network (AN) can be a fixed station or a base station for communicating with terminals and can also be referred to as an access point, Node B, base station, enhanced base station, evolved base station (eNB), or some other term. The access terminal (AT) can also be referred to as a user equipment (UE), wireless communication device, terminal, access terminal, or some other term.

[0026] Figure 2 is a simplified block diagram of an embodiment of a transmitter system 210 (also referred to as an access network) and a receiver system 250 (also referred to as an access terminal (AT) or user equipment (UE)) in a MIMO system 200. At the transmitter system 210, traffic data for multiple data streams is provided from a data source 212 to a transmit (TX) data processor 214.

[0027] In one embodiment, each data stream is transmitted via a respective transmit antenna. The TX data processor 214 formats, encodes, and interleaves the traffic data of the data streams based on a particular encoding scheme selected for each data stream to provide encoded data.

[0028] The encoded data of each data stream can be multiplexed with pilot data using OFDM techniques. Pilot data are typically known data patterns that are processed in a known manner and can be used at the receiver system to estimate the channel response. The multiplexed pilot and encoded data for the data stream are then modulated (i.e., symbol mapped) based on a particular modulation scheme selected for each data stream (e.g., BPSK, QPSK, M-PSK, or M-QAM) to provide modulated symbols. Instructions executed by the processor 230 can determine the data rate, encoding, and modulation for each data stream.

[0029] The modulated symbols of all data streams are then provided to the TX MIMO processor 220, which may further process the modulated symbols (e.g., for OFDM). The TX MIMO processor 220 then provides N T streams of modulated symbols to N T transmitters (TMTRs) 222a through 222t. In some embodiments, the TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and the antennas from which the symbols are transmitted.

[0030] Each transmitter 222 receives and processes the corresponding stream of symbols to provide one or more analog signals and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission via the MIMO channel. The N T modulated signals from transmitters 222a through 222t are then transmitted from the N T antennas 224a through 224t, respectively.

[0031] At the receiver system 250, the transmitted modulated signals are received by the N R antennas 252a through 252r, and the signals received from each antenna 252 are provided to a respective receiver (RCVR) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) the corresponding received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" stream of symbols.

[0032] The RX data processor 260 then receives and processes the N R streams of received symbols from the N R receivers 254 based on particular receiver processing techniques to provide N TA "detected" symbol stream. The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing performed by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0033] The processor 270 periodically determines which precoding matrix (discussed below) to use. The processor 270 formulates a reverse link message that includes a matrix index portion and a rank value portion.

[0034] The reverse link message can include various types of information about the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238 (which also receives the traffic data for several data streams from the data source 236), modulated by the modulator 280, conditioned by the transmitters 254a to 254r, and transmitted back to the transmitter system 210.

[0035] At the transmitter system 210, the modulated signal from the receiver system 250 is received by the antenna 224, conditioned by the receiver 222, demodulated by the demodulator 240, and processed by the RX data processor 242 to extract the reverse link message transmitted through the receiver system 250. Then, the processor 230 determines which precoding matrix to use to determine the beamforming weights and then processes the extracted message.

[0036] Go to Figure 3 , this figure shows an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. As Figure 3 shown, the communication device 300 in the wireless communication system can be used to implement Figure 1 the UEs (or ATs) 116 and 122 in Figure 1 or the base station (or AN) 100 in , and the wireless communication system is preferably an NR system. The communication device 300 can include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by the user through the input device 302 (e.g., a keyboard or keypad) and can output images and sounds through the output device 304 (e.g., a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals, deliver the received signals to the control circuit 306, and wirelessly output the signals generated by the control circuit 306. The communication device 300 in the wireless communication system can also be used to implementFigure 1 AN 100 in

[0037] Figure 4 is a simplified block diagram of the program code 312 shown in Figure 3 . In this embodiment, the program code 312 includes an application layer 400, a layer 3 part 402, and a layer 2 part 404, and is coupled to a layer 1 part 406. The layer 3 part 402 generally performs radio resource control. The layer 2 part 404 generally performs link control. The layer 1 part 406 generally performs physical connection.

[0038] 3GPP TS 38.212 Rel-16 provides some relevant texts in NR as follows:

[0039] [Table 7.3.1-1 of 3GPP TS 38.212 with the title "DCI Format" is reproduced as Figure 5

[0040] 7.3.1.2.2 Format 1_1

[0041] DCI format 1_1 is used to schedule PDSCH in a cell.

[0042] The following information is transmitted by means of DCI format 1_1 with CRC scrambled by C-RNTI or CS-RNTI or MCS-C-RNTI:

[0043] - Identifier for DCI format - 1 bit

[0044] - The value of this bit field is always set to 1, indicating the DL DCI format

[0045] - Carrier indicator - 0 or 3 bits, as defined in clause 10.1 of [5, TS 38.213].

[0046] - Bandwidth part indicator - 0, 1, or 2 bits...

[0047] - Frequency domain resource allocation - The number of bits determined by the following, where is the size of the DL bandwidth part in effect:

[0048] […]

[0049] - Time domain resource allocation - 0, 1, 2, 3, or 4 bits, as defined in clause 5.1.2.1 of [6, TS 38.214]. The bit width used for this field is determined to be bits, where if the higher layer parameter is configured, then I is the number of entries in the higher layer parameter pdsch-TimeDomainAllocationList; otherwise I is the number of entries in the default table.​

[0050] - VRB to PRB mapping - 0 or 1 bit:

[0051] […]

[0052] For transport block 1:

[0053] - Modulation and coding scheme - 5 bits, as defined in clause 5.1.3.1 of [6, TS 38.214]

[0054] - New data indicator - 1 bit

[0055] - Redundancy version - 2 bits, as defined in Table 7.3.1.1.1-2

[0056] For transport block 2 (only present when maxNrofCodeWordsScheduledByDCI equals 2):

[0057] - Modulation and coding scheme - 5 bits, as defined in clause 5.1.3.1 of [6, TS 38.214]

[0058] - New data indicator - 1 bit

[0059] - Redundancy version - 2 bits, as defined in Table 7.3.1.1.1-2

[0060] […]

[0061] - HARQ process number - 4 bits

[0062] - Downlink assignment index - number of bits as defined below

[0063] […]

[0064] - TPC command for scheduled PUCCH - 2 bits, as defined in clause 7.2.1 of [5, TS 38.213]

[0065] - PUCCH resource indicator - 3 bits, as defined in clause 9.2.3 of [5, TS 38.213]

[0066] - PDSCH to HARQ_feedback timing indicator - 0, 1, 2, or 3 bits, as defined in clause 9.2.3 of [5, TS 38.213]. The bit width used for this field is determined as bits, where I is the number of entries of the higher layer parameter dl-DataToUL-ACK.

[0067] […]

[0068] - Transmission Configuration Indicator - 0 bits if the higher layer parameter tci-PresentInDCI is not enabled; otherwise 3 bits as defined in clause 5.1.5 of [6, TS38.214].

[0069] If the "bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part

[0070] - If the higher layer parameter tci-PresentInDCI is not enabled for the CORESET used to carry PDCCH of DCI format 1_1

[0071] - The UE assumes that tci-PresentInDCI is not enabled for all CORESETs in the indicated bandwidth part;

[0072] - Otherwise,

[0073] - The UE assumes that tci-PresentInDCI is enabled for all CORESETs in the indicated bandwidth part.

[0074] 3GPP TS 38.213 Rel-16 provides the following relevant text in NR:

[0075] For each CORESET, the ControlResourceSet provides the following to the UE:

[0076] - The CORESET index p provided by controlResourceSetId, where

[0077] […]

[0078] - The initialization value of the DM-RS scrambling sequence provided by pdcch-DMRS-ScramblingID;

[0079] - The precoder granularity for several REGs in the frequency domain provided by precoderGranularity, where the UE may assume the use of the same DM-RS precoder;

[0080] - The number of consecutive symbols provided by duration;

[0081] […]

[0082] - The antenna port quasi-co-location from a set of antenna port quasi-co-locations provided by TCI-State, which indicates the quasi-co-location information of the DM-RS antenna ports for PDCCH reception in the corresponding CORESET;

[0083] […]

[0084] - An indication of the presence or absence of a Transmission Configuration Indicator (TCI) field for DCI formats other than DCI format 1_0, used for DCI format scheduling of PDSCH reception or indicating SPS PDSCH release and transmitted by PDCCH in CORESETp, via tci-PresentInDCI or tci-PresentInDCI-ForDCIFormat1_2-r16.

[0085] […]

[0086] The UE determines the PDCCH monitoring occasions on the active DL BWP based on the PDCCH monitoring periodicity within a slot, the PDCCH monitoring offset, and the PDCCH monitoring pattern. For a search space set s, the UE determines that if then in a frame with number n f the PDCCH monitoring occasions exist in the slot with number Starting from slot the UE monitors PDCCH candidates for the search space set s in T s consecutive slots and does not monitor PDCCH candidates for the search space set s in the next k s - T s consecutive slots.

[0087] The USS at the CCE aggregation level L ∈ {1, 2, 4, 8, 16} is defined by the set of PDCCH candidates for the CCE aggregation level L.

[0088] If the UE is configured with CrossCarrierSchedulingConfig for the serving cell, then the carrier indicator field value corresponds to the value indicated by CrossCarrierSchedulingConfig.

[0089] For the DL BWP in the serving cell's role where the UE monitors PDCCH candidates in the USS, if the UE is not configured with a carrier indicator field, then the UE monitors PDCCH candidates without a carrier indicator field. For the DL BWP in the serving cell's role where the UE monitors PDCCH candidates in the USS, if the UE is configured with a carrier indicator field, then the UE monitors PDCCH candidates with a carrier indicator field.

[0090] If the UE is configured to monitor PDCCH candidates with a Carrier Indicator Field corresponding to a secondary cell in another serving cell, the UE does not expect to monitor PDCCH candidates on the DL BWP in the role of the secondary cell. For the DL BWP in the role of the serving cell on which the UE monitors PDCCH candidates, the UE monitors PDCCH candidates at least for the same serving cell.

[0091] Table 10.1-2 provides the maximum number of monitored PDCCH candidates per time slot for the UE in the DL BWP with SCS configuration μ for the operation of a single serving cell.

[0092] [Table 10.1-2 of 3GPP TS 38.213 V16.3.0 entitled "Maximum number of monitored PDCCH candidates per time slot in the DL BWP with SCS configuration μ ∈ {0, 1, 2, 3} for a single serving cell is reproduced as Figure 6

[0093] Table 10.1-3 provides the maximum number of non-overlapping CCEs in the DL BWP with SCS configuration μ for which the UE is expected to monitor corresponding PDCCH candidates per time slot for the operation of a single serving cell.

[0094] The CCEs of the PDCCH candidates are non-overlapping if the CCEs correspond to

[0095] - different CORESET indices, or

[0096] - different first symbols for the reception of the respective PDCCH candidates.

[0097] [Table 10.1-3 of 3GPP TS 38.213 V16.3.0 entitled "Maximum number of non-overlapping CCEs per time slot in the DL BWP with SCS configuration μ ∈ {0, 1, 2, 3} for a single serving cell is reproduced as Figure 7

[0098] […]

[0099] For each scheduled cell in the downlink cells using the combination (X, Y), the UE does not need to monitor more than PDCCH candidates or more than non-overlapping CCEs per span on the DL BWP with SCS configuration μ of the scheduled cell.

[0100] ​​It is not expected to configure a CSS set for the UE, where the set causes the corresponding total number of monitored PDCCH candidates and non-overlapping CCEs per time slot or per span, or the number per scheduled cell, to exceed the corresponding maximum number per time slot or per span, respectively.

[0101] For cross-carrier scheduling, the number of PDCCH candidates for monitoring and the number of non-overlapping CCEs per span or per time slot are counted separately for each scheduled cell.

[0102] 3GPP RP-193133 provides some content related to the text associated with the Rel-17 further enhanced MIMO (FeMIMO) work item in NR as follows:

[0103] 4 Objectives

[0104] 4.1 Objectives of the SI or Core Part WI or Test Part WI

[0105] a. […]

[0106] 2. Enhance the support for multi-TRP deployments, for both FR1 and FR2:

[0107] a. Identify and specify features to improve the reliability and stability of channels other than PDSCH (i.e., PDCCH, PUSCH, and PUCCH) using multi-TRP and / or multi-panel, where the Rel.16 reliability features are used as a baseline

[0108] In addition, 3GPP TS 38.331 V16.2.0 states:

[0109] -CrossCarrierSchedulingConfig

[0110] The IE CrossCarrierSchedulingConfig is used to specify the configuration when using cross-carrier scheduling in a cell.

[0111] CrossCarrierSchedulingConfig information element

[0112] --ASN1START

[0113] --TAG-CROSSCARRIERSCHEDULINGCONFIG-START

[0114] CrossCarrierSchedulingConfig::=SEQUENCE{

[0115] schedulingCellInfo CHOICE{

[0116] own SEQUENCE

[0117] {-- Cross-carrier scheduling: scheduling cell

[0118] cif-Presence BOOLEAN

[0119] },

[0120] other SEQUENCE

[0121] {-- Cross-carrier scheduling: scheduled cell

[0122] schedulingCellId ServCellIndex,

[0123] cif-InSchedulingCell INTEGER(1..7)

[0124] }

[0125] },

[0126] ...,

[0128] carrierIndicatorSize-r16 SEQUENCE{

[0129] carrierIndicatorSizeDCI-1-2-r16 INTEGER(0..3),

[0130] carrierIndicatorSizeDCI-0-2-r16 INTEGER(0..3)

[0131] }

[0132] OPTIONAL,-- Cond CIF-PRESENCE

[0133] enableDefaultBeamForCCS-r16 ENUMERATED {enabled}OPTIONAL-- Need S

[0135] }

[0136] -- TAG-CROSSCARRIERSCHEDULINGCONFIG-STOP

[0137] -- ASN1STOP

[0138] ​​

[0139]

[0140] -ControlResourceSet

[0141] The IE ControlResourceSet is used to configure the time / frequency control resource set (CORESET) in which to search for downlink control information (see TS 38.213

[13] , section 10.1).

[0142] ControlResourceSet information element

[0143] --ASN1START

[0144] --TAG-CONTROLRESOURCESET-START

[0145] ControlResourceSet ::= SEQUENCE {

[0146] controlResourceSetId ControlResourceSetId,

[0147] frequencyDomainResources BIT STRING (SIZE (45)),

[0148] duration INTEGER (1..maxCoReSetDuration), cce-REG-MappingType CHOICE {

[0149] interleaved SEQUENCE {

[0150] reg-BundleSize ENUMERATED {n2, n3, n6},

[0151] interleaverSize ENUMERATED {n2, n3, n6},

[0152] shiftIndex

[0153] INTEGER (0..maxNrofPhysicalResourceBlocks - 1) OPTIONAL -- Need S

[0154] },

[0155] nonInterleaved NULL

[0156] },

[0157] precoderGranularity ENUMERATED{sameAsREG-bundle, allContiguousRBs},

[0158] tci-StatesPDCCH-ToAddList SEQUENCE(SIZE(1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, --Cond NotSIB1-initialBWP

[0159] tci-StatesPDCCH-ToReleaseList SEQUENCE(SIZE(1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, --Cond NotSIB1-initialBWP

[0160] tci-PresentInDCI ENUMERATED{enabled} OPTIONAL, --Need S

[0161] pdcch-DMRS-ScramblingID INTEGER(0..65535) OPTIONAL, --Need S

[0162] ...,

[0164] rb-Offset-r16 INTEGER(0..5) OPTIONAL, --Need S

[0165] tci-PresentDCI-1-2-r16 INTEGER(1..3) OPTIONAL, --Need S

[0166] coresetPoolIndex-r16 INTEGER(0..1) OPTIONAL, --Need S

[0167] controlResourceSetId-v1610 ControlResourceSetId-v1610 OPTIONAL --Need S

[0169] }

[0170] ​​--TAG-CONTROLRESOURCESET-STOP

[0171] --ASN1STOP

[0172]

[0173]

[0174] -PhysCellId

[0175] PhysCellId identifies the Physical Cell Identity (PCI).

[0176] PhysCellId information element

[0177] --ASN1START

[0178] --TAG-PHYSCELLID-START

[0179] PhysCellId::=INTEGER(0..1007)

[0180] --TAG-PHYSCELLID-STOP

[0181] --ASN1STOP

[0182] -ServCellIndex

[0183] The IE ServCellIndex refers to the short identity used to identify a serving cell (i.e., PCell, PSCell, or SCell). The value 0 applies to the PCell, and the previously assigned SCellIndex applies to the SCell.

[0184] ServCellIndex information element

[0185] --ASN1START

[0186] --TAG-SERVCELLINDEX-START

[0187] ServCellIndex::=INTEGER(0..maxNrofServingCells-1)

[0188] --TAG-SERVCELLINDEX-STOP

[0189] --ASN1STOP

[0190] -SearchSpace

[0191] The IE SearchSpace defines how / where to search for PDCCH candidates. Each search space is associated with a ControlResourceSet. For the scheduled cell in the case of cross-carrier scheduling, all optional fields are absent (regardless of their presence conditions), except for nrofCandidates.

[0192] SearchSpace information element

[0193] --ASN1START

[0194] --TAG-SEARCHSPACE-START

[0195] SearchSpace ::= SEQUENCE {

[0196] searchSpaceId SearchSpaceId,

[0197] controlResourceSetId ControlResourceSetId OPTIONAL, -- Cond SetupOnly

[0198] monitoringSlotPeriodicityAndOffset CHOICE {

[0199] sl1 NULL,

[0200] sl2 INTEGER(0..1),

[0201] sl4 INTEGER(0..3),

[0202] sl5 INTEGER(0..4),

[0203] sl8 INTEGER(0..7),

[0204] sl10 INTEGER(0..9),

[0205] sl16 INTEGER(0..15),

[0206] sl20 INTEGER(0..19),

[0207] sl40 INTEGER(0..39),

[0208] sl80 INTEGER(0..79),

[0209] sl160 INTEGER(0..159),

[0210] sl320 INTEGER(0..319),

[0211] sl640 INTEGER(0..639),

[0212] sl1280 INTEGER(0..1279),

[0213] sl2560 INTEGER(0..2559)

[0214] }

[0215] OPTIONAL, --Cond Setup

[0216] duration INTEGER (2..2559)OPTIONAL, --Need R

[0217] monitoringSymbolsWithinSlot BIT STRING(SIZE(14))OPTIONAL, --Cond Setup

[0218] nrofCandidates SEQUENCE{

[0219] aggregationLevel1 ENUMERATED{n0, n1, n2, n3, n4, n5, n6, n8},

[0220] aggregationLevel2 ENUMERATED{n0, n1, n2, n3, n4, n5, n6, n8},

[0221] aggregationLevel4 ENUMERATED{n0, n1, n2, n3, n4, n5, n6, n8},

[0222] aggregationLevel8 ENUMERATED{n0, n1, n2, n3, n4, n5, n6, n8},

[0223] aggregationLevel16 ENUMERATED{n0, n1, n2, n3, n4, n5, n6, n8}

[0224] }

[0225] OPTIONAL, --Cond Setup

[0226] searchSpaceType CHOICE{

[0227] common SEQUENCE{

[0228] dci-Format0-0-AndFormat1-0 SEQUENCE{ ...

[0230] }

[0231] OPTIONAL, -- Need R

[0232] dci-Format2-0 SEQUENCE{

[0233] nrofCandidates-SFI SEQUENCE{

[0234] aggregationLevel1 ENUMERATED{n1, n2}OPTIONAL, -- Need R

[0235] aggregationLevel2 ENUMERATED{n1, n2}OPTIONAL, -- Need R

[0236] aggregationLevel4 ENUMERATED{n1, n2}OPTIONAL, -- Need R

[0237] aggregationLevel8 ENUMERATED{n1, n2}OPTIONAL, -- Need R

[0238] aggregationLevel16 ENUMERATED{n1, n2}OPTIONAL -- Need R

[0239] } ...

[0241] }

[0242] OPTIONAL, -- Need R

[0243] dci-Format2-1 SEQUENCE{ ...

[0245] }

[0246] OPTIONAL, -- Need R

[0247] dci-Format2-2 SEQUENCE{ ...

[0249] }

[0250] OPTIONAL, --Need R

[0251] dci-Format2-3 SEQUENCE{

[0252] dummy1 ENUMERATED{sl1, sl2, sl4, sl5, sl8, sl10, sl16, sl20} OPTIONAL, --Cond Setup

[0253] dummy2 ENUMERATED{n1, n2}, ...

[0255] }

[0256] OPTIONAL --Need R

[0257] }

[0258] ue-Specific SEQUENCE{

[0259] dci-Formats ENUMERATED

[0260] {formats0-0-And-1-0, formats0-1-And-1-1},

[0261] ...

[0263] dci-Formats-MT-r16 ENUMERATED{formats2-5} OPTIONAL, --Need R

[0264] dci-FormatsSL-r16 ENUMERATED{formats0-0-And-1-0, formats0-1-And-1-1, formats3-0, formats3-1,

[0265] formats3-0-And-3-1}

[0266] OPTIONAL, --Need R

[0267] ​dci-FormatsExt-r16 ENUMERATED{formats0-2-And-1-2, formats0-1-And-1-1And-0-2-And-1-2}

[0268] OPTIONAL--Need R

[0270] }

[0271] }

[0272] OPTIONAL--Cond Setup2

[0273] }

[0274] SearchSpaceExt-r16::= SEQUENCE{

[0275] controlResourceSetId-r16 ControlResourceSetId-r16 OPTIONAL, --Cond SetupOnly2

[0276] searchSpaceType-r16 SEQUENCE{

[0277] common-r16 SEQUENCE{

[0278] dci-Format2-4-r16 SEQUENCE{

[0279] nrofCandidates-CI-r16 SEQUENCE{

[0280] aggregationLevel1-r16 ENUMERATED{n1, n2} OPTIONAL, --Need R

[0281] aggregationLevel2-r16 ENUMERATED{n1, n2} OPTIONAL, --Need R

[0282] aggregationLevel4-r16 ENUMERATED{n1, n2} OPTIONAL, --Need R

[0283] aggregationLevel8-r16 ENUMERATED{n1, n2} OPTIONAL, --Need R

[0284] ​aggregationLevel16-r16 ENUMERATED{n1, n2} OPTIONAL -- Need R

[0285] }, ...

[0287] }

[0288] OPTIONAL, -- Need R

[0289] dci-Format2-5-r16 SEQUENCE{

[0290] nrofCandidates-IAB-r16 SEQUENCE{

[0291] aggregationLevel1-r16 ENUMERATED{n1, n2} OPTIONAL, -- Need R

[0292] aggregationLevel2-r16 ENUMERATED{n1, n2} OPTIONAL, -- Need R

[0293] aggregationLevel4-r16 ENUMERATED{n1, n2} OPTIONAL, -- Need R

[0294] aggregationLevel8-r16 ENUMERATED{n1, n2} OPTIONAL, -- Need R

[0295] aggregationLevel16-r16 ENUMERATED{n1, n2} OPTIONAL -- Need R

[0296] }, ...

[0298] }

[0299] OPTIONAL, -- Need R

[0300] dci-Format2-6-r16 SEQUENCE{ ...

[0302] }

[0303] OPTIONAL, -- Need R ...

[0305] }

[0306] }

[0307] OPTIONAL, --Cond Setup3

[0308] searchSpaceGroupIdList-r16 SEQUENCE(SIZE(1..2)) OF INTEGER(0..1) OPTIONAL, --Need R

[0309] freqMonitorLocations-r16 BIT STRING(SIZE(5)) OPTIONAL --Need R

[0310] }

[0311] --TAG-SEARCHSPACE-STOP

[0312] --ASN1STOP

[0313]

[0314]

[0315]

[0316] -TCI-State

[0317] The IE TCI-State associates one or two DL reference signals with the corresponding quasi - colocation (QCL) types.

[0318] TCI-State information element

[0319] --ASN1START

[0320] --TAG-TCI-STATE-START

[0321] TCI-State ::= SEQUENCE{

[0322] tci-StateId TCI-StateId,

[0323] qcl-Type1 QCL-Info,

[0324] qcl-Type2 QCL-Info OPTIONAL, --Need R ...

[0326] }

[0327] QCL-Info ::= SEQUENCE {

[0328] cell ServCellIndex OPTIONAL, -- NeedR

[0329] bwp-Id BWP-Id

[0330] OPTIONAL, -- Cond CSI-RS-Indicated

[0331] referenceSignal CHOICE {

[0332] csi-rs NZP-CSI-RS-ResourceId,

[0333] ssb SSB-Index

[0334] },

[0335] qcl-Type ENUMERATED {typeA, typeB, typeC, typeD}, ...

[0337] }

[0338] -- TAG-TCI-STATE-STOP

[0339] -- ASN1STOP

[0340]

[0341]

[0342] The final report of 3GPP TSG RAN WG1 #102-e V1.0.0 states that:

[0343] Protocol

[0344] To implement PDCCH transmission with two TCI states, study the pros and cons of the following alternatives:

[0345] ● Alternative 1: One CORESET with two active TCI states

[0346] ● Alternative 2: One SS set associated with two different CORESETs

[0347] ● Alternative 3: Two SS sets associated with the corresponding CORESET

[0348] ● At least the following aspects can be considered: multiplexing schemes (TDM / FDM / SFN / combination schemes), BD / CCE limitations, overload, CCE-REG mapping, PDCCH candidate CCEs (i.e., hash functions), CORESET / SS set configurations, and other program impacts.

[0349] Protocol

[0350] For non-SFN-based mTRP PDCCH reliability enhancement, study the following options:

[0351] · Option 1 (no repetition): One coding / rate matching for PDCCH with two TCI states

[0352] · Option 2 (repetition): Coding / rate matching is based on a repetition, and the same decoded bits are repeated for another repetition. Each repetition has the same number of CCEs and decoded bits and corresponds to the same DCI payload.

[0353] ○ Study both in-slot repetition and inter-slot repetition

[0354] · Option 3 (multiple opportunities): Scheduling the same PDSCH / PUSCH / RS / TB, etc. or separate DCIs that produce the same result.

[0355] ○ Study two cases of DCI in the same slot and DCI in different slots

[0356] Protocol

[0357] For mTRP PDCCH reliability enhancement, study the following multiplexing schemes

[0358] ● TDM: Two sets of symbols of the transmitted PDCCH / two non-overlapping (in time) transmitted PDCCH repetitions / multiple-opportunity transmitted PDCCHs are associated with different TCI states

[0359] ○ Aspects related to in-slot versus inter-slot and specification impacts to be discussed

[0360] ● FDM: Two sets of the transmitted PDCCH / two non-overlapping (in frequency) transmitted PDCCH repetitions / multiple-opportunity transmitted PDCCH REG clusters / CCEs are associated with different TCI states

[0361] ● SFN: PDCCH DMRS is associated with two TCI states in all REGs / CCEs of the PDCCH

[0362] ○ Note: There is a dependency between this scheme and AI 2d (HST-SFN)

[0363] Protocol

[0364] For alternative 1 (one CORESET with two TCI states out of the two roles), study the following cases

[0365] ● Alternative 1-1: One PDCCH candidate (from the given SS set) is associated with two TCI states of the CORESET.

[0366] ● Alternative 1-2: Two sets of PDCCH candidates (from the given SS set) are respectively associated with two TCI states of the CORESET

[0367] ● Alternative 1-3: Two sets of PDCCH candidates are associated with two corresponding SS sets, where the two SS sets are associated with the CORESET and each SS set is associated with only one TCI state of the CORESET

[0368] Protocol

[0369] For alternatives 1-2 / 1-3 / 2 / 3, study the following items

[0370] ● Case 1: Two (or more) PDCCH candidates are explicitly linked together (the UE knows the link before decoding)

[0371] ● Case 2: Two (or more) PDCCH candidates are not explicitly linked together (the UE does not know the link before decoding)

[0372] Chair's Note RAN1#103-e V033 statement:

[0373] Protocol

[0374] For PDCCH reliability enhancement using the non-SFN scheme, support at least option 2 + case 1.

[0375] ● The maximum number of linked PDCCH candidates is two

[0376] Working assumption

[0377] For PDCCH reliability enhancement using the non-SFN scheme and option 2 + case 1, support alternative 3 (two SS sets associated with the corresponding CORESET).

[0378] Protocol

[0379] For PDCCH reliability enhancement using the non-SFN scheme and option 2 + case 1, count the CCEs of the two PDCCH candidates separately following the Rel.15 / 16 procedures. Further study the BD limit by considering the following cases

[0380] ● Two units are required relative to the complexity associated with re-demapping / demodulation

[0381] ● Relative to the complexity associated with decoding, the following assumptions can be further discussed:

[0382] ○ Assumption 1: The UE decodes only the combined candidates without decoding the individual PDCCH candidates

[0383] ○ Assumption 2: The UE decodes the individual PDCCH candidates

[0384] ○ Assumption 3: The UE decodes the first PDCCH candidate and the combined candidate

[0385] ○ Assumption 4: The UE decodes each PDCCH candidate individually and also decodes the combined candidate

[0386] ● Note 1: Assumptions 1-4 are for discussion purposes only and they may or may not have a normative impact.

[0387] ○ To be further studied: The relationship between UE capabilities, RRC configuration and BD limitations, and whether assumptions 1-4 are relevant for this purpose.

[0388] ● Note 2: The BD / CCE limitations here are counted based on the configuration of PDCCH monitoring capabilities (e.g., per slot or per span).

[0389] The draft report of 3GPP TSG RAN WG1#104-e V0.3.0 states:

[0390] Protocol

[0391] Confirmed working assumption:

[0392] For PDCCH reliability enhancement using non-SFN schemes and option 2+ case 1, alternative 3 (two SS sets associated with the corresponding CORESET) is supported.

[0393] Protocol

[0394] For PDCCH repetition, linking two SS sets via RRC configuration is supported:

[0395] ● To be further studied: Whether MAC-CE can be used additionally

[0396] ● When monitoring PDCCH repetition in two linked SS sets, the UE does not expect a third monitoring SS set to be linked to either of the two linked SS sets.

[0397] ● The two linked SS sets have the same SS set type (USS / CSS)

[0398] ○ The two linked SS sets have the same DCI format to be monitored.

[0399] ● For PDCCH repetitions within a time slot,

[0400] ○ The two SS sets shall have the same periodicity and offset (monitoringSlotPeriodicityAndOffset), and the same duration.

[0401] ○ For monitoring occasions spanning two SS sets linked in the same time slot:

[0402] ■ The two SS sets have the same number of monitoring occasions within the time slot, and the nth monitoring occasion of one SS set is linked to the nth monitoring occasion of the other SS set.

[0403] Protocol

[0404] When two SS sets are linked for PDCCH repetitions, they do not contain individual PDCCH candidates.

[0405] ● Note 1: For the configuration of individual PDCCH candidates, different SS sets can be configured by the network.

[0406] ● Note 2: When one of the linked PDCCH candidates uses the same CCE set as the individual PDCCH candidate and they are associated with the same DCI size, scrambling, and CORESET, the Rel.15 rules are followed and no additional BD is counted.

[0407] Protocol

[0408] For PDCCH repetitions, the two PDCCH candidates in the two SS sets are linked based on the following

[0409] ● Having the same AL and the same candidate index:

[0410] ○ The two linked SS sets are configured to have the same number of candidates for each AL.

[0411] Chair's Note RAN1#104b-e V012 states:

[0412] Protocol

[0413] When DL DCI is transmitted via PDCCH repetition, for the determination of PUCCH resources for HARQ-Ack when the corresponding PUCCH resource set has a size greater than eight, the starting CCE index and the number of CCEs in the CORESET of one of the linked PDCCH candidates are applied, and option 2 is supported.

[0414] ● Option 2: Apply the one with the lowest SS set ID.

[0415] ● To be further studied: Support for Option 2 does not imply support for PDCCH repetition based on two link search space sets within a CORESET

[0416] Protocol

[0417] For PDSCH rate matching around the scheduling DCI in the case of PDCCH repetition, the previous protocol for FR1 also applies to FR2.

[0418] Protocol

[0419] For the number of BDs corresponding to two PDCCH candidates for PDCCH repetition links, support

[0420] ● The UE reports one [or more] number as the required number of BDs for two PDCCH candidates

[0421] ○ Candidate values: 2, 3.

[0422] Protocol

[0423] If the PDSCH is scheduled by the DCI in a PDCCH candidate for a repeated link (the first PDCCH candidate associated with the first CORESET and the second PDCCH candidate associated with the second CORESET),

[0424] ● Working assumption: The UE expects the same configuration for the first and second CORESETs regarding the presence of the TCI field in the DCI.

[0425] ● If the TCI field does not exist in the DCI and the scheduling offset is equal to or greater than timeDurationForQCL (if applicable), then the PDSCH QCL assumption is based on the CORESET with the lower ID among the first and second CORESETs

[0426] ● To be further studied: Whether additional options are needed (e.g., enabling SDM / FDM / TDM PDSCH schemes in the case of no TCI field in the DCI)

[0427] One or more of the following terms may be used below:

[0428] · BS : The network central unit or network node in NR that controls one or more TRPs associated with one or more cells. The communication between the BS and the TRP is via the fronthaul. The BS may also be referred to as the central unit (CU), eNB, gNB, or NodeB.

[0429] · TRP :The transceiver point provides network coverage and communicates directly with the UE. The TRP can also be referred to as a distributed unit (DU) or a network node.

[0430] · Cell :A cell consists of one or more associated TRPs, i.e., the coverage area of a cell is composed of the coverage areas of all associated TRPs. A cell is controlled by a BS. A cell can also be referred to as a TRP group (TRPG).

[0431] In NR Rel-15, beamforming technology is adopted to overcome high-power penetration in high-frequency bands such as above 6 GHz. Therefore, both the gNB and the UE can use some transmission beams and / or reception beams to make high-throughput data in such high-frequency bands reliable. How to select appropriate transmission beams and / or reception beams plays an important role in NR Rel-15. Beam indication for various channels and reference signals and the development of NR are also well discussed and mentioned in the specification.

[0432] However, in NR Rel-15, at least from the UE's perspective, beam indication for receiving downlink (DL) transmissions only considers transmissions from a single TRP and / or using a panel within a duration (e.g., a time slot or a mini-slot). In NR Rel-16, people and companies resume considering DL transmissions from multiple TRPs and / or panels. For transmissions from multiple TRPs and / or panels, it can be implied that a single DL transmission can be performed by different beams from multiple TRPs and / or panels. It can also mean that the UE can receive multiple DL transmissions from multiple TRPs and / or panels within a duration (e.g., a time slot or a mini-slot). In NR Rel-16, multiple TRP scenarios have also been considered for enhancing Ultra-Reliable Low-Latency Communication (URLLC). Therefore, there are some Physical Downlink Shared Channel (PDSCH) repetition schemes to improve the reliability of receiving PDSCH. Some examples can be Spatial Domain Multiplexing (SDM) repetition schemes, FMD repetition schemes, mini-slot-based repetition schemes, and time-slot-based repetition schemes.

[0433] Regarding NR Rel-17, people have started to consider reliability enhancements for other channels, such as the Physical Downlink Control Channel (PDCCH), Physical Uplink Control Channel (PUCCH), and Physical Uplink Shared Channel (PUSCH). Since the PDCCH controls the scheduling information for the PDSCH and PUSCH, there is no doubt that the enhancement of the PDCCH should be emphasized first. To achieve the reliability of the PDCCH, one or more PDCCH repetitions (from different TRPs) in the time domain can be a method. In this method, once a link between a TRP and a UE is blocked and results in a failed PDCCH reception, there is another PDCCH repetition from the same or a different TRP for successful scheduling. One or more PDCCH repetitions can provide the same scheduling result for the PDSCH or PUSCH. The number of one or more PDCCH repetitions is two (considering two PDCCH repetitions as a pair / correlation / link). To achieve beam diversity or soft combination gain, the UE needs to know the link of one or more PDCCH repetitions before decoding.

[0434] RAN1 has agreed on the association / link / pairing of two PDCCH repetitions through search space configuration. For the same carrier scheduling (PDCCH and PDSCH / PUSCH on the same carrier), the network can provide the configuration for linking two search spaces. The network can provide the same periodicity, slot offset, the same number of consecutive slot durations, and / or the same number of monitoring occasions within a slot. However, for cross-carrier scheduling, how the network provides the configuration for linking two search spaces of the scheduled cell may need further study.

[0435] For example, in Figure 11 , the UE is simultaneously configured for cross-carrier / cell scheduling and PDCCH repetition for the scheduled cell. For PDCCH repetition within a slot, to reduce latency and increase reliability, SS1 and SS2 of the scheduled cell should be as Figure 11 shown. However, by introducing cross-carrier / cell scheduling, the PDCCH monitoring occasion of the SS for the scheduled slot can depend on the scheduling cell. In this example, the benefit of reducing latency may be lost because SS2 of the scheduling cell is in a different slot from SS1 of the scheduling cell.

[0436] In one embodiment, when PDCCH repetition is configured or linked on a scheduling cell or a scheduled cell, the present invention design separately impacts the scheduled cell or the scheduling cell. When a scheduling cell is associated with more than one scheduled cell (e.g., one scheduling cell has more than one scheduled cell across carriers), the present invention can provide a PDCCH repetition design. A scheduling cell can be associated with one or more transmission configuration indication (TCI) states, which are at least associated with the one scheduling cell having a first physical cell identity (PCI) and / or an associated neighboring cell (or non-serving cell) having a second PCI. The source reference signal (RS) of one TCI state among the one or more TCI states can be associated with the one scheduling cell having the first PCI or the associated neighboring cell having the second PCI.

[0437] In one embodiment, when a UE is configured with cross-carrier / cell scheduling and the scheduling cell and the scheduled cell are configured to have PDCCH repetition, a problem may occur even if a one-to-one mapping between one search space of the scheduling cell and another search space of the scheduling cell is ensured. This problem can be caused by Figure 12 shown. As Figure 12 shown, the UE is configured with SS1 - SS3 of cell 1 and SS1 - SS2 of cell 2, and is configured with cross-carrier / cell for scheduling cell 1 for the scheduling cell 2. Figure 12 shows a time slot of cell 1. The UE is configured with links of SS1 and SS3 of cell 1 and links of SS1 and SS3 of cell 2. Although the PDCCH monitoring occasions derived through SS1 and SS3 can have a one-to-one mapping, SS1 of cell 2 can be associated with SS1 of cell 1, and the second PDCCH monitoring occasion of SS1 of cell 1 can be associated with the second PDCCH monitoring occasion of SS1 of cell 2 that may not have a linked SS2. This can cause whether the UE assumes the existence of PDCCH repetition or link of SS1, SS2 of cell 2, and / or whether the UE assumes more BD attempts for a pair of PDCCH candidates (e.g., BD = 3) than decoding separately (e.g., BD = 2).

[0438] In one embodiment, the scheduling cell can refer to an SCell or a PCell. The scheduled cell can refer to a PCell or an Scell. The DSS scenario for an SCell to schedule a PCell can be an addressing scenario. For a scheduled cell scheduled by a scheduling cell across cells / carriers, the UE does not receive a PDCCH on the scheduled cell.

[0439] Any combination of the above concepts can be jointly combined or formed into a new embodiment. The following embodiments can be used to at least (but not limited to) solve the problems mentioned above.

[0440] Concept 1:

[0441] Generally speaking, this concept will limit the network for providing search space configurations of the scheduling cell and the scheduled cell (when the network provides or configures cross-carrier / cell scheduling for the UE). In one embodiment, for the link of two search spaces of the scheduled cell, the UE expects a restricted / constrained configuration (from the network) of two search spaces of the scheduling cell. The link of two search spaces of the scheduling cell may not be provided for the UE. Alternatively, the UE may be provided or the network may provide a flexible configuration of two search spaces of the scheduling cell, except for the configuration of the link from two search spaces of the scheduled cell. Another alternative is that if the link of two search spaces of the scheduled cell is provided / configured, then the UE (also) may be provided with a restricted / constrained configuration of two search spaces of the scheduling cell, and / or if the link of two search spaces of the scheduled cell is provided / configured, then the UE expects the link of two search spaces of the scheduling cell.

[0442] Alternatively, for the link of two search spaces of the scheduling cell, the UE may expect a restricted / constrained configuration (from the network) of two search spaces of the scheduling cell. For two search spaces of the scheduled cell, one alternative is that the UE may not be provided with the link of two search spaces of the scheduled cell and / or the network may provide "no link" of two search spaces of the scheduled cell. For two search spaces of the scheduled cell, another alternative is that if the link of two search spaces of the scheduled cell is provided / configured, then the UE (also) may be provided with a restricted / constrained configuration of two search spaces of the scheduled cell. If the link of two search spaces of the scheduling cell is provided / configured, then the UE may expect the link of two search spaces of the scheduled cell.

[0443] In one embodiment, for the link of two search spaces of the scheduled cell, the network may provide the same first parameter set for two search spaces of the scheduled cell and the same second parameter set for two search spaces of the scheduling cell. For the link of two search spaces of the scheduled cell, the network may provide a third parameter set for two search spaces of the scheduling cell, which has the same number of bit positions with value 1.

[0444] The first parameter set may include the number of PDCCH candidates (e.g., nrofCandidates) for one or more aggregation levels. The second parameter set may at least include monitoringSlotPeriodicityAndOffset, duration, monitoringSymbolsWithinSlot, and searchSpaceType. In one embodiment, the second parameter set may (further) include CORESET-related parameters. The CORESET-related parameters may be associated with one or two search spaces of the scheduling cell. The CORESET-related parameters may include the CORESET ID and / or the number of TCI bits in the DCI on the CORESET (e.g., tci-PresentInDCI and / or tci-PresentDCI-1-2-r16). The third parameter set may include a bitmap with one or more bit positions having a value of 1 that indicate the starting OFDM symbol (e.g., monitoringSymbolsWithinSlot) for the one or more PDCCH monitoring occasions.

[0445] In one embodiment, if the network does not link two search spaces of the scheduling cell, then the network may provide different first parameter sets for the two search spaces of the scheduling cell.

[0446] In one embodiment, for the SS of the scheduled cell, the SS of the scheduling cell having the same SSID as the SS of the scheduled cell may refer to or mean the corresponding SS.

[0447] In one embodiment, the PDCCH candidate ID may refer to the ID of the PDCCH candidate for the aggregation level in the search space (set). For example, the UE has SS1 of cell 1, and SS1 of cell 1 includes 4 PDCCH candidates with AL = 2, and the PDCCH candidates for AL = 2 of SS1 of cell 1 may be 0 to 3.

[0448] In one embodiment, for cross-carrier / cell scheduling, the scheduling cell and the scheduled cell may be different (serving) cells, and / or have different PCIs and / or be associated with different serving cell IDs (ServCellIndex).

[0449] In one embodiment, the corresponding search space of the scheduling cell for the search space of the scheduled cell may be determined by the same SSID.

[0450] In one embodiment, when the UE is configured with cross-carrier / cell scheduling, the PDCCH monitoring occasion of the search space of the scheduled cell is determined by the search space of the scheduling cell, where the search space of the scheduling cell has the same SSID as the search space of the scheduled cell.

[0451] For the two linked search spaces of cross-carrier / cell scheduling and the scheduled cell, the restricted / constrained configurations for the two corresponding search spaces (i.e., having the same set of parameters or the same values of the following parameters) may include any one or combination of the following:

[0452] ● The same number of bit positions with value 1 within monitoringSymbolsWithinSlot

[0453] ● The same slot-level monitoring periodicity

[0454] ● The same slot offset for monitoring

[0455] ● The same duration

[0456] ● The same search space type

[0457] ● The same DCI format (functionality)

[0458] ● The same searchSpaceGroupIdList

[0459] ● The same freqMonitorLocations

[0460] ● Different CORESET IDs for the two corresponding search spaces

[0461] ● The same number of tci-PresentInDCI is provided for each CORESET of the two corresponding search spaces

[0462] ● The same number of tci-PresentInDCItci-PresentDCI-1-2-r16 is provided for each CORESET of the two corresponding search spaces

[0463] The restricted / constrained configurations for the two corresponding search spaces can help the UE avoid handling isolated PDCCH monitoring occasions and / or the ambiguity regarding whether the two linked SSs of the scheduled cell are linked. For the two linked search spaces of cross-carrier / cell scheduling and the scheduled cell, the number of at least PDCCH candidates (for each aggregation level) of the search space of the scheduling cell having the same SSID as the two linked search spaces of the scheduled cell may have different values.

[0464] Put simply, regardless of whether the two link search spaces are from cell 1 or cell 2 (e.g., the scheduling cell / the scheduled cell), if the UE can perform soft combination of the PDCCH in search space 1 from the scheduled cell and the PDCCH in search space 2 from the scheduled cell, then the UE can expect to be configured with two search spaces having the same first parameter set. The UE may not perform soft combination of the PDCCH in search space 1 from the scheduling cell and the PDCCH in search space 2 from the scheduling cell.

[0465] In one embodiment, for two search spaces of a scheduling cell, the two search spaces are linked for PDCCH repetition, and one or both CORESETs may be associated with the two search spaces of the scheduling cell respectively. The one or both CORESETs may be associated with different TRPs. The one or both CORESETs may be associated with different CORESETPoolIndices. The one or both CORESETs may be associated with different TCI states / beams / spatial relations / QCL type D assumptions / spatial filters.

[0466] In one embodiment, the source RSs of different TCI states / beams / spatial relations / QCL type D assumptions / spatial filters may be associated with different cells having different PCIs. A scheduling cell may be associated with one or more TCI states, where the source RSs of the one or more TCI states may be associated with one or more cells having different PCIs.

[0467] In one embodiment, the linking / connection / association / pairing of two search spaces (sets) may refer to or may mean PDCCH repetition. The UE may be configured with the linking / connection / association / pairing of two search spaces (sets) of a cell (e.g., SS1, SS2) by receiving an SSID that points to or is associated with another SSID. The linking / connection / association / pairing of two search spaces (sets) may refer to or mean that PDCCH1 from one of the two search spaces (sets) is linked / associated / paired to PDCCH2 from the other of the two search spaces (sets).

[0468] In one embodiment, (linked / associated) PDCCH1 and PDCCH2 may have the same CCE and / or the same starting CCE. Linked SS1 and SS2 (of a cell) may refer to or imply that a PDCCH (candidate) with a PDCCH candidate ID from SS1 is linked to a PDCCH (candidate) with a PDCCH candidate ID from SS2. (Linked / associated) PDCCH1 and PDCCH2 may have the same PDCCH candidate ID. PDCCH1 and PDCCH2 may be separated in the time domain (TDM), frequency domain (FDM), or spatial domain (SDM).

[0469] In one embodiment, the CORESET for PDCCH1 may be separated from the CORESET for PDCCH2 in the time domain, frequency domain, or spatial domain. The CORESET for PDCCH1 may partially overlap with the CORESET for PDCCH2 in the time domain, frequency domain, and / or spatial domain. The PDCCH monitoring occasion for PDCCH1 may be separated from the PDCCH monitoring occasion for PDCCH2 in the time domain, frequency domain, or spatial domain. The PDCCH monitoring occasion for PDCCH1 may partially overlap with the PDCCH monitoring occasion for PDCCH2 in the time domain, frequency domain, and / or spatial domain. PDCCH1 and PDCCH2 may be a pair of PDCCH candidates. PDCCH1 may be associated with a different TRP from PDCCH2. PDCCH1 may be associated with a different CORESETPoolIndex from PDCCH2. PDCCH1 may be associated with a different CORESET from PDCCH2. PDCCH1 may be associated with a different TCI state / beam / spatial relation / QCL type D assumption / spatial filter from PDCCH2.

[0470] In one embodiment, the source RS of the TCI state / beam / spatial relation / QCL type D assumption / spatial filter associated with PDCCH1 may be different from the source RS of the TCI state / beam / spatial relation / QCL type D assumption / spatial filter associated with PDCCH2. The source RS of the TCI state / beam / spatial relation / QCL type D assumption / spatial filter associated with PDCCH1 may be associated with a different cell PCI from the source RS of the TCI state / beam / spatial relation / QCL type D assumption / spatial filter associated with PDCCH2.

[0471] In one embodiment, for a pair of PDCCH candidates (e.g., PDCCH1 and PDCCH2 paired or linked for PDCCH repetition), the UE may assume X blind decoding attempts or X BDs. For unpaired PDCCH candidates (e.g., PDCCH1 and PDCCH2 not paired or linked for PDCCH repetition), the UE may assume Y blind decoding attempts or Y BDs. X may be greater than or equal to Y. The UE may report the value of X to the network. Y may be 2. X may be 2 or 3.

[0472] In one embodiment, for a pair of PDCCH candidates including PDCCH1 and PDCCH2, PDCCH1 and PDCCH2 may schedule the same physical downlink shared channel (PDSCH). For example, in Figure 10 1 and 2 are linked search spaces, and PDCCH1 and PDCCH2 from the linked search space schedule two PDSCHs respectively.

[0473] For a pair of PDCCH candidates including PDCCH1 and PDCCH2, PDCCH1 and PDCCH2 may schedule the same physical uplink shared channel (PUSCH). PDCCH1 and PDCCH2 may indicate the same physical uplink control channel (PUCCH). PDCCH1 and PDCCH2 may indicate the same uplink scheduling and / or downlink assignment.

[0474] In one embodiment, for a pair of PDCCH candidates including PDCCH1 and PDCCH2, a reference PDCCH may be determined from PDCCH1 or PDCCH2. The one reference PDCCH may be the later PDCCH in the time domain (for determining time sequence related aspects). The one reference PDCCH may be the earlier PDCCH in the time domain (for determining the counter DAI, codebook determination). The one reference PDCCH may be the PDCCH with the lowest / highest CORESET ID or associated with the lowest / highest SSID (at least for determining the beam or QCL relationship of the scheduled PDSCH).

[0475] In one embodiment, for a pair of PDCCH candidates including PDCCH1 and PDCCH2, the UE may perform soft combining on the pair of PDCCH candidates. For unpaired PDCCH candidates, the UE may not perform soft combining on the two PDCCH candidates.

[0476] Regardless of whether the link is provided on the two search spaces of the scheduling cell or the scheduled cell or both, the UE can expect a restricted configuration for the two search spaces of the scheduling cell. The UE can expect that the second parameter set and the third parameter set are restricted. The UE can expect that the second parameter set and the third parameter set for the two search spaces of the scheduled cell are restricted.

[0477] When the SS1 and SS2 of the scheduled cell are configured or provided to the UE as being linked / If the SS1 and SS2 of the scheduled cell are configured or provided to the UE as being linked, the UE does not expect a specific SS of the scheduling cell configured / provided for the link SS1 that is different from the SS2 of the scheduling cell. When more than one scheduled cell is scheduled by the scheduling cell for the UE configuration or provision / If more than one scheduled cell is scheduled by the scheduling cell for the UE configuration or provision, for the links of the two search spaces of each scheduled cell, the UE does not expect that each link search space of each scheduled cell has the same or overlapping SSIDs with each other.

[0478] For example, the UE can be configured such that cell 1 schedules cell 1 (e.g., CIF = 0), cell 2 (e.g., CIF = 1), and cell 3 (e.g., CIF = 2). The links of the two search spaces of cell 2 and the links of the two search spaces of cell 3 can be configured or provided to the UE. In this example, the UE may not expect that (SS1, SS2) of the search space of cell 2 is linked and that (SS1, SS3) of the search space of cell 3 is linked. The UE can expect (SS1, SS2) and (SS3, SS4) (since the SSIDs from different scheduled cells do not repeat). One possible reason can be that SS1 can refer to SS1 in cell 1, and a restricted / limited configuration can be applied to SS1 and SS2 and even SS1 and SS3, which may reduce the scheduling flexibility of the network.

[0479] Alternatively, for self-carrier / cell scheduling, the UE may not expect the third search space of the cell to be from either of the two search spaces of the cell's link link search space. For cross-carrier / cell scheduling and more than one scheduled cell being scheduled by the scheduling cell, for the link of the two search spaces for each scheduled cell, the UE may receive a configuration that the search space of the scheduling cell can be implicitly linked to more than one search space of the scheduled cell. For example, the UE may be configured to be scheduled by cell 1 for cell 1 (e.g., CIF = 0), cell 2 (e.g., CIF = 1), and cell 3 (e.g., CIF = 2). The link of the two search spaces of cell 2 and the link of the two search spaces of cell 3 may be configured or provided to the UE. In this example, (SS1, SS2) of cell 2 and (SS1, SS3) of cell 3 are allowed. In other words, SS1 of cell 1 (scheduling cell) may have a restricted / constrained set of second parameters and / or third parameters for SS2 of cell 1 and SS3 of cell 1.

[0480] Figure 8 An example showing two PDCCH monitoring opportunities in the time domain and / or frequency domain and the control channel element (CCE) domain of the search space (SS) for cell 1 and cell 2 in each PDCCH monitoring opportunity in the control channel element (CCE) domain. The UE may be configured with cross-carrier / cell scheduling (e.g., the PDCCH in cell 1 may schedule the PDSCH / PUSCH in cell 2). In other words, the UE may monitor the PDCCH on cell 1, and the PDCCH from the search space of cell 2 schedules the PDSCH / PUSCH on cell 2. The same SSID of the search spaces of cell 1 and cell 2 may refer to one or more identical PDCCH monitoring opportunities based on the search space of cell 1. In this example, SSID 1 of cell 1 and cell 2 may relate to the first PDCCH monitoring opportunity, while SSID 2 of cell 1 and cell 2 may relate to the second PDCCH monitoring opportunity. Since the PDCCH monitoring opportunity for the SS of the scheduled cell (e.g., cell 2) is based on the search space configuration of the scheduling cell (e.g., cell 1), when the UE is provided with the link of search space 1 and search space 2 of cell 2, the UE may expect some restricted configurations (the same set of parameters or the same values of parameters) on the corresponding search space of cell 1. In this example, although the link of the SS is mainly for the scheduled cell (e.g., cell 2), the UE may expect the scheduled SS configuration (e.g., SS1 and SS2 of cell 1) to provide link monitoring opportunities in the time slot. As another example, (when the UE is configured with cross-cell / carrier scheduling and two linked search spaces of the scheduled cell), the UE may not expect the SS configuration of the two search spaces of the scheduling cell with the same SSID as the two linked search spaces of the scheduled cell to provide isolated PDCCH monitoring opportunities.

[0481] Figure 9 An example of a PDCCH from SS1, SS2, or cell 1, cell 2 is shown, considering two scenarios of the SS1 and SS2 links of cell 1 or the SS1 and SS2 links of cell 2. Cross-carrier / cell scheduling can be provided to the UE, where cell 1 schedules cell 2 and cell 1 schedules cell 1. The number of blind decoding (BD) times X can be greater than or equal to Y. Preferably, X is 2 or 3, and Y is 2.

[0482] In this example (Upper left entry) once the SS1 and SS2 links of cell 1 are provided to the UE, For cell 1 SS1, SS2 the UE can assume or expect (which forces) the SS1 and SS2 links of cell 1. The UE can assume X BD times for a pair of PDCCH (candidates) respectively from SS1, SS2 of cell 1. PDCCH1 / PDCCH candidate 1 can have the same number of CCEs and the same starting CCE as PDCCH2 / PDCCH candidate 2. PDCCH1 can be associated with SS1 of cell 2 and PDCCH2 with SS2 of cell 1. PDCCH1 can have the same PDCCH candidate ID as PDCCH2.

[0483] In one embodiment, the UE can perform soft combining for two PDCCHs (e.g., PDCCH1 and PDCCH2 in this example). PDCCH1 and PDCCH2 can schedule one or more identical PDSCHs. The UE can consider PDCCH1 and PDCCH2 as linked PDCCHs. PDCCH1 and PDCCH2 can have the same DCI format. SS1 of cell 2 and SS2 of cell 1 can be associated with the same DCI format, the same search space type, the same duration, and / or the same number of bit positions with value 1 in each bitmap. SS1 of cell 1 and SS2 of cell 1 can be associated with the same nrofCandidates (for each aggregation level).

[0484] In this example (Lower left entry) once the SS1 and SS2 links of cell 1 are provided to the UE, For cell 2 SS1, SS2, an alternative (Alternative 1) is that the UE can assume or expect (which forces) the SS1 and SS2 links of Cell 2. The UE can assume X BDs for a pair of PDCCHs (candidates) respectively from SS1 and SS2 of Cell 2. PDCCH1 / PDCCH candidate 1 can have the same number of CCEs and the same starting CCE as PDCCH2 / PDCCH candidate 2. PDCCH1 can be associated with SS1 of Cell 2, and PDCCH2 can be associated with SS2 of Cell 2. PDCCH1 can have the same PDCCH candidate ID as PDCCH2. The UE can perform soft combination for the two PDCCHs (e.g., PDCCH1 and PDCCH2 in this instance). PDCCH1 and PDCCH2 can schedule one or more identical PDSCHs. The UE can consider PDCCH1 and PDCCH2 as linked PDCCHs. PDCCH1 and PDCCH2 can have the same DCI format. One or more restricted configurations for SS1, SS2 of Cell 1 and / or the CORESET of Cell 1 can be applied to SS1 of Cell 2 and SS2 of Cell 2. SS1 of Cell 2 and SS2 of Cell 2 can have the same DCI format, the same search space type, the same duration, and / or the same number of bit positions with value 1 in each bitmap. SS1 of Cell 2 and SS2 of Cell 2 can be associated with the same nrofCandidates (for each aggregation level).

[0485] In this instance (Lower left entry) , once the SS1 and SS2 links of Cell 1 are provided to the UE, For cell 2 SS1, SS2, Another alternative (Alternative 2) is that the UE may not link to the independent SS1 and SS2 of cell 2. The UE may assume Y blind decodings of a pair of PDCCHs (candidates) respectively from SS1 and SS2 of cell 2. PDCCH1 / PDCCH candidate 1 may have the same number of CCEs and the same starting CCE as PDCCH2 / PDCCH candidate 2. PDCCH1 may be associated with SS1 of cell 2, and PDCCH2 may be associated with SS2 of cell 2. PDCCH1 may have the same PDCCH candidate ID as PDCCH2. The UE may not perform soft combining for the two PDCCHs (e.g., PDCCH1 and PDCCH2 in this instance). PDCCH1 and PDCCH2 may schedule different PDSCHs. The UE may regard PDCCH1 and PDCCH2 as independent PDCCHs. PDCCH1 and PDCCH2 may have the same DCI format. One or more restricted configurations for SS1 and SS2 of cell 1 and / or the CORESET of cell 1 may be applied to SS1 of cell 2 and SS2 of cell 2 (even if SS1 and SS2 of cell 2 are not linked). SS1 of cell 2 and SS2 of cell 2 may have the same DCI format, the same search space type, the same duration, and / or the same number of bit positions with value 1 in each bitmap. SS1 of cell 2 and SS2 of cell 2 may have different nrofCandidates (for each aggregation level).

[0486] In this instance (Upper right entry) , once the links to SS1 and SS2 of cell 2 are provided to the UE, For cell 1 SS1, SS2, an alternative (Alternative 1) is that the UE can assume or expect the SS1 and SS2 links of Cell 1. The UE can assume X times of BD for a pair of PDCCHs (candidates) respectively from SS1 and SS2 of Cell 1. PDCCH1 / PDCCH candidate 1 can have the same number of CCEs and the same starting CCE as PDCCH2 / PDCCH candidate 2. PDCCH1 can be associated with SS1 of Cell 1, and PDCCH2 can be associated with SS2 of Cell 1. PDCCH1 can have the same PDCCH candidate ID as PDCCH2. The UE can perform soft combination for two PDCCHs (e.g., PDCCH1 and PDCCH2 in this instance). PDCCH1 and PDCCH2 can schedule one or more identical PDSCHs. The UE can consider PDCCH1 and PDCCH2 as linked PDCCHs. PDCCH1 and PDCCH2 can have the same DCI format. The UE can expect one or more restricted configurations for SS1, SS2 of Cell 1, and / or the CORESET of Cell 1. SS1 of Cell 1 and SS2 of Cell 1 can have the same DCI format, the same search space type, the same duration, and / or the same number of bit positions with value 1 in each bitmap. SS1 of Cell 1 and SS2 of Cell 1 can be associated with the same nrofCandidates (for each aggregation level).

[0487] In this instance (Upper right entry) , once the SS1 and SS2 links of Cell 1 are provided to the UE, For cell 1 SS1, SS2, Another alternative (Alternative 2) is to provide the UE with the independent SS1 and SS2 of cell 1. The UE may assume Y BDs for a pair of PDCCHs (candidates) respectively from SS1 and SS2 of cell 2. PDCCH1 / PDCCH candidate 1 may have the same number of CCEs and the same starting CCE as PDCCH2 / PDCCH candidate 2. PDCCH1 may be associated with SS1 of cell 1, and PDCCH2 may be associated with SS2 of cell 1. PDCCH1 may have the same PDCCH candidate ID as PDCCH2. The UE may not perform soft combination for the two PDCCHs (e.g., PDCCH1 and PDCCH2 in this instance). PDCCH1 and PDCCH2 may schedule different PDSCHs. The UE may regard PDCCH1 and PDCCH2 as independent PDCCHs. PDCCH1 and PDCCH2 may have the same DCI format. One or more restricted configurations for SS1 and SS2 of cell 1 and / or the CORESET of cell 1 may be applied to SS1 of cell 2 and SS2 of cell 2 (even if SS1 and SS2 of cell 2 are not linked). SS1 of cell 2 and SS2 of cell 2 may be associated with the same DCI format, the same search space type, the same duration, and / or the same number of bit positions with value 1 in each bitmap. SS1 of cell 2 and SS2 of cell 1 may have different nrofCandidates (for each aggregation level).

[0488] In this instance (Lower right entry) , once the UE is provided with the link of SS1 and SS2 of cell 2, For cell 2 SS1, SS2, the UE may assume or expect the SS1 and SS2 links of cell 2. The UE may assume X BDs for a pair of PDCCH (candidates) respectively from SS1 and SS2 of cell 2. PDCCH1 / PDCCH candidate 1 may have the same number of CCEs and the same starting CCE as PDCCH2 / PDCCH candidate 2. PDCCH1 may be associated with SS1 of cell 2, and PDCCH2 may be associated with SS2 of cell 2. PDCCH1 may have the same PDCCH candidate ID as PDCCH2. The UE may perform soft combining for two PDCCHs (e.g., PDCCH1 and PDCCH2 in this instance). PDCCH1 and PDCCH2 may schedule one or more identical PDSCHs. The UE may consider PDCCH1 and PDCCH2 as linked PDCCHs. PDCCH1 and PDCCH2 may have the same DCI format. SS1 of cell 2 and SS2 of cell 1 may have the same DCI format, the same search space type, the same duration, and / or the same number of bit positions with value 1 in each bitmap. SS1 of cell 1 and SS2 of cell 2 may be associated with the same nrofCandidates (for each aggregation level).

[0489] In one embodiment, different alternatives shown in Figure 9 may be combined. For example, once SS1 and SS2 of cell 1 are linked, then SS1 and SS2 of cell 2 are linked (alternative 1), and once SS1 and SS2 of cell 2 are linked, then SS1 and SS2 of cell 1 may not be linked (alternative 2) (but provide one or more restricted configurations to support the linked SS1 and SS2 of cell 2). As another example, vice versa, that is, once SS1 and SS2 of cell 1 are linked, then SS1 and SS2 of cell 2 are not linked (alternative 2), and once SS1 and SS2 of cell 2 are linked, then SS1 and SS2 of cell 1 are linked (alternative 1). As another example, once SS1 and SS2 of cell 1 are linked, then SS1 and SS2 of cell 2 are linked (alternative 1), and once SS1 and SS2 of cell 2 are linked, then SS1 and SS2 of cell 1 are linked (alternative 1). In other words, at least one scheduling cell (e.g., cell 1) or the scheduled cell (e.g., cell 2) has the links of two SSs, the two SSs from the scheduling cell or from the scheduled cell, and the two SSs with the same SSID from the scheduled cell or from the scheduling cell are linked.

[0490] Concept 2:

[0491] Generally speaking, this concept is to restrict the network from simultaneously configuring cross-carrier / cell scheduling and the link / linkage / link / association / pairing of two search spaces (of the scheduling cell and / or the scheduled cell). When the UE is configured with a first cell that schedules a second cell, the UE may not expect PDCCH repetition or the link / linkage / link / association / pairing of two search spaces of the first cell or the second cell. This concept may be to restrict the network from configuring the link / linkage / link / association / pairing of two search spaces of the scheduled cell (whose PDCCH is on another scheduling cell). This concept may be to restrict the network from configuring the link / linkage / link / association / pairing of two search spaces of an SCell. In one embodiment, the network may only be allowed to configure the link / linkage / link / association / pairing of two search spaces for a PCell or a PSCell. The PCell and / or the PSCell may not be the scheduled unit whose PDCCH is on another scheduling cell (e.g., the UE-specific PDCCH that schedules the PCell and / or the PSCell is not on another cell).

[0492] Concept 3:

[0493] Generally speaking, this concept is to (explicitly) associate the first link of two search spaces of the scheduled cell with the second link of two search spaces of the scheduling cell (when the link of two search spaces of the scheduled cell is provided / configured). The UE may not expect the first link to be associated with one or more scheduled search spaces for which no link is configured / provided. The PDCCH monitoring occasion of the first link of two search spaces of the scheduled cell may be determined (respectively) based on the second link of two search spaces of the scheduling cell. The PDCCH monitoring occasion of the first link of two search spaces of the scheduled cell may not be determined based on the implicit SSID of the search space of the scheduling cell that has the same SSID as the first link of two search spaces of the scheduled cell.

[0494] Alternatively, an implicit association of the first link of two search spaces of the scheduled cell to the second link of two search spaces of the scheduling cell may be applied (when the link of two search spaces of the scheduled cell is provided / configured). The scheduling cell may have a first number of links of two search spaces of the scheduling cell, and the scheduled cell has a second number of links of two search spaces of the scheduled cell. The first number of links may be associated with the second number of links (instead of via using the same SSID). The association between the first number of links and the second number of links may be one-to-one or one-to-many. The first link among the second number of links may be associated with the first link among the first number of links. The link ID (for each link) may be configured or implicitly determined by the lowest SS ID among the two SSs of the link.

[0495] For example, the UE can be configured such that cell 1 schedules cell 1 (e.g., CIF = 0) and cell 2 (e.g., CIF = 1). The UE can be configured with three links of the SS of cell 1 as (SS1, SS4), (SS2, SS5), (SS6, SS7), and five links of the SS of cell 2 as (SS2, SS3), (SS5, SS6), (SS8, SS9), (SS4, SS7), (SS1, SS10). In this example, (SS2, SS3), (SS5, SS6), (SS8, SS9), (SS4, SS7), (SS1, SS10) can surround the three links of the SS of cell 1, such that (SS1, SS4) of cell 1 can be associated with (SS2, SS3) and (SS4, SS7) of cell 2, (SS2, SS5) can be associated with (SS5, SS6) and (SS1, SS10) of cell 2, and (SS6, SS7) can be associated with (SS8, SS9). Alternatively, the three links of the SS of cell 1 can be reordered as (SS1, SS4), (SS2, SS5), (SS6, SS7) by the lowest SSID of each link, and the five links of the SS of cell 2 can be reordered as (SS1, SS10), (SS2, SS3), (SS4, SS7), (SS5, SS6), (SS8, SS9) by the lowest SSID of each link. The first two of the three links of cell 1 can refer to or be associated with two links of cell 2. Preferably, (SS1, SS4), (SS2, SS5), (SS6, SS7) of cell 1 can designate the link IDs as 0, 1, 2, and (SS2, SS3), (SS5, SS6), (SS8, SS9), (SS4, SS7), (SS1, SS10) can designate the link IDs as 0, 1, 2, 3, 4.

[0496] In one embodiment, for two search spaces of linked cells, the two search spaces are associated with the same link ID. For cross-carrier scheduling, the same link ID of the scheduled cell and the scheduling cell is also linked. The association of the five links of the SS and the three links of the SS can be determined at least based on the adjustment of the number of link IDs of the scheduling cell, and the remaining part involves the associated links of the scheduled cell.

[0497] Concept 4:

[0498] Generally speaking, a link between two search spaces of a scheduled cell is considered a link between two search spaces of the scheduled cell (when the UE is configured with cross-carrier / cell scheduling and PDCCH repetition on the scheduled cell). In other words, when the (SS1, SS2) of the scheduled cell is configured with a link, the UE can consider or derive or determine that the (SS1, SS2) of the scheduled cell (also) is the link between the (SS1, SS2) of the scheduling cell. For the scheduling cell, the UE can expect or the network can be limited to providing or configuring a one-to-one search space in the link (e.g., PDCCH repetition or a link between two search spaces should ensure that there is no other search space linked to either of the two search spaces in the link). This concept can be that (for cross-carrier / cell scheduling) the SSID of the SS in a link of the search space of the scheduling cell or the scheduled cell completely overlaps, is exactly the same, does not overlap, and / or is completely different from the SSID of the SS in another link of the search space of any scheduling cell or scheduled cell. Regardless of whether it is from the scheduling cell or the scheduled cell, any link between two search spaces can be considered a link between two search spaces with the same SSID on the scheduling cell.

[0499] (For cross-carrier / cell scheduling), the UE may not be expected to be configured such that the SSID of the SS in a link of the search space of the scheduling cell or the scheduled cell partially overlaps (but does not completely overlap) with the SSID of the SS in another link of the search space of any scheduling cell or scheduled cell.

[0500] (For self-carrier / cell scheduling), the UE can be configured such that the SSID of the SS in a link of the search space of the third cell or the scheduled cell partially overlaps with the SSID of the SS in another link of the search space of the fourth cell. The UE can monitor the PDCCH on the third cell, and the PDCCH can schedule the third cell. The UE can monitor the PDCCH on the fourth cell, and the PDCCH can schedule the fourth cell.

[0501] When a search space with a first SSID of the scheduling cell and another search space with a second SSID of the scheduling cell are linked (for PDCCH repetition), the UE may not be expected to configure the search space with the first SSID of the scheduled cell to be linked to other search spaces of the scheduled cell except for the search space with the second SSID of the scheduled cell.

[0502] When a search space with a first SSID of a scheduled cell and another search space with a second SSID of the scheduled cell are linked (for PDCCH repetition), the UE may not expect that the search space with the first SSID of the scheduled cell is configured to be linked to other search spaces of the scheduled cell except for the search space with the second SSID of the scheduled cell.

[0503] When a search space with a first SSID of a scheduled cell and another search space with a second SSID of the scheduled cell are linked (for PDCCH repetition), the UE may not expect that any search space with the first SSID of any scheduled cell is configured to be linked to other search spaces of any scheduled cell except for the search space with the second SSID of any scheduled cell.

[0504] When a search space with a first SSID of a first scheduled cell and another search space with a second SSID of the first scheduled cell are linked (for PDCCH repetition), the UE may not expect that the search space with the first SSID of a second scheduled cell is configured to be linked to other search spaces of the second scheduled cell except for the search space with the second SSID of the second scheduled cell. The first scheduled cell and the second scheduled cell may be scheduled by the same scheduled cell (cross-carrier / cell).

[0505] In one embodiment, the UE may be configured with cross-carrier / cell scheduling. The UE may be configured with a first cell to schedule one or more cells cross-carrier / cell. The one or more cells may include a second cell. The UE may be configured with a first link of a search space (set) of the first cell. The UE may be configured with a second link of a search space (set) of the second cell. The UE may be configured with a second link of a search space (set) of one of the one or more cells. In one embodiment, the first link of the search space may include a first set of search spaces with a first SSID and a second set of search spaces with a second SSID. The second link of the search space may include a third set of search spaces with a third SSID and a fourth set of search spaces with a fourth SSID. If the first SSID is the same as the third or fourth SSID, then the UE may not expect the second SSID to be different from the fourth or third SSID, respectively. If the first SSID is different from the third or fourth SSID, then the UE may not expect the second SSID to be the same as the fourth or third SSID.

[0506] For any link to the search space of the first cell and any link to the search space of a cell among the one or more cells that includes one search space with a first SSID and other search spaces with a second SSID, the UE may not expect to be configured or receive a configuration for another link to the search space of the first cell or the cell among the one or more cells, such that the other link to the search space includes a search space with the first SSID or the second SSID and other search spaces with an SSID that is not the first SSID or the second SSID.

[0507] For any link to the search space of the first cell and any link to the search space of a cell among the one or more cells that includes one search space with a first SSID and other search spaces with a second SSID, the UE may not expect to be configured or receive a configuration for another link to the search space of the first cell or the cell among the one or more cells, such that the other link to the search space includes a search space with an SSID different from the first SSID or the second SSID and other search spaces with an SSID the same as the second SSID.

[0508] For example, as Figure 12 shown, since the SS1 of cell 1 is linked to the SS3 of cell 1, the UE does not expect the SS1 of cell 2 to be linked to other search spaces other than SS3. Since the SS1 of cell 2 is linked to the SS2 of cell 2, the UE may not expect the SS1 of cell 1 to be linked to other search spaces other than SS2. In other words, the SS1 of cell 1 may be configured to be linked to the SS2 of cell 1, but the SS1 of cell 1 may not be allowed to be configured to be linked to the SS3 of cell 1.

[0509] In one embodiment, as Figure 14 shown, the UE may be configured with cross-carrier / cell scheduling such that cell 1 schedules cells 1, 2, and 3. In this example, (SSx, SSy) of cell 1 may be configured as a link for PDCCH repetition, (SSz, SSw) of cell 2 may be configured as a link for PDCCH repetition, and (SSq, SSe) of cell 3 may be configured as a link for PDCCH repetition. In this example, due to its PDCCH repetition, SSID x may be different from SSIDy, SSIDz may be different from SSID w, and SSID q may be different from SSID e.

[0510] In one embodiment, if x is equal to z or w, then y may be respectively restricted or limited to w or z. If x is different from z or w, then y may be restricted or limited to be at least different from z or w. If x is different from q or e, then y may be restricted or limited to be at least different from q or e. In one embodiment, (x, y, z, w, q, e) may be (1, 2, 1, 2, 1, 2), (x, y, z, w, q, e) may be (1, 2, 1, 2, 3, 4), (x, y, z, w, q, e) may be (3, 4, 1, 2, 3, 4), and / or (x, y, z, w, q, e) may be (3, 1, 4, 2, 1, 3). As Figure 13 shown, if x is different from z, then the UE may expect that the SSz and SSw of cell 1 have a link or at least have a restricted / restricted configuration as shown in Concept 1.

[0511] For all of the above concepts, methods, alternatives, and embodiments:

[0512] Any of the above methods, alternatives, and embodiments may be combined or applied simultaneously. A cell may be associated with more than one PCI, for example, including a first PCI and a second PCI. The first PCI may be indicated or derived from the (primary) synchronization signal and / or (secondary) synchronization signal of the cell. The second PCI may be used for (inter-cell) mTRP operation. The first TRP and the second TRP may participate in (inter-cell) mTRP operation. The first TRP (QCL source / parameters of the signal / channel from the first TRP) may be associated with the first PCI and the second TRP (QCL source / parameters of the signal / channel from the second TRP) may be associated with the second PCI.

[0513] In one embodiment, the UE may be configured and / or served by the network in the serving cell. The UE may be configured with and / or may indicate one or more BWPs. The UE may indicate and / or activate (in operation), an in-operation DL BWP or an in-operation ULBWP. The UE may be configured and / or may indicate an initial BWP.

[0514] In one embodiment, the first SS may be associated with the first TRP in the first serving cell. The second SS may be associated with the second TRP in the second serving cell. The first serving cell may have a serving cell index, which may be the same as or different from the serving cell index of the second serving cell.

[0515] In one embodiment, the UE may be in the RRC_CONNECTED state, the RRC_INACTIVE state, or the RRC_IDLE state. The UE may be served by a first TRP or a second TRP. The first TRP may belong to or be associated with the serving cell. The second TRP may belong to or be associated with the serving cell. The first TRP and the second TRP may belong to or be associated with the same serving cell. Alternatively, the first TRP and the second TRP belong to different serving cells or are associated with them. The first TRP may schedule or transmit DL or UL transmissions to the UE. The second TRP may schedule or transmit DL or UL transmissions to the UE. The first TRP may receive UL transmissions from the UE. The second TRP may receive UL transmissions from the UE.

[0516] In one embodiment, the network may include a first network panel. The network may include a second network panel. The first network panel may be used to receive UL transmissions from the UE. The second network panel may be used to receive UL transmissions from the UE. Two different CORESETs may (respectively) belong to the first TRP and the second TRP. The one search space may be associated with a CORESET belonging to the first TRP and a CORESET belonging to the second TRP. The two different CORESETs may belong to the same TRP as the first TRP or the second TRP. For two search spaces, one of the two search spaces may be associated with the CORESET belonging to the first TRP, and the other of the two search spaces may be associated with the CORESET belonging to the second TRP.

[0517] Figure 14 It is a flowchart 1400 according to an exemplary embodiment from the perspective of the network. In step 1405, the network configures cross-carrier scheduling for a user equipment (UE), where the network transmits a physical downlink control channel (PDCCH) on a first cell that schedules a second cell. In step 1410, the network configures PDCCH repetition on the first two search spaces of the second cell for the UE, where the network should configure PDCCH repetition on the second two search spaces of the first cell for the UE, and the search space identity (ID) of the first two search spaces of the second cell is the same as the search space ID of the second two search spaces of the first cell.

[0518] In one embodiment, a first physical downlink control channel (PDCCH) candidate of one search space of the first two search spaces from a second cell may have the same PDCCH candidate identity (ID) as a second PDCCH candidate of the other search space of the first two search spaces from the second cell. The first PDCCH candidate may be associated with a transmission configuration indication (TCI) state, beam, spatial relation, quasi co-location (QCL) type D assumption, or spatial filter that is different from that of the second PDCCH candidate. There may be 2 or 3 blind decoding attempts for the first PDCCH candidate and the second PDCCH candidate.

[0519] In one embodiment, the network may not be allowed to configure the UE such that the search space ID of only one search space in the first two search spaces of the second cell is the same as the search space identity of one search space in the second two search spaces of the first cell. Additionally, the network may not be allowed to configure the UE such that there is no PDCCH duplication in the second two search spaces of the first cell.

[0520] Return reference Figure 3 and 4 , in an exemplary embodiment of the network. The network includes program code 312 stored in a memory 310. A CPU 308 may execute the program code 312 to enable the network to: (i) configure cross-carrier scheduling for a user equipment (UE), where the network transmits a physical downlink control channel (PDCCH) on a first cell that schedules a second cell, and (ii) configure PDCCH duplication on the first two search spaces of the second cell, where the network shall configure PDCCH duplication on the second two search spaces of the first cell, and the search space ID of the first two search spaces of the second cell is the same as the search space ID of the second two search spaces of the first cell. Additionally, the CPU 308 may execute the program code 312 to perform all of the above actions and steps or other actions and steps described herein.

[0521] Figure 15 is a flowchart 1500 according to an exemplary embodiment from the perspective of the network. In step 1505, the network configures cross-carrier scheduling for a user equipment (UE), where the network transmits a physical downlink control channel (PDCCH) on a first cell that schedules a second cell. In step 1510, the network configures PDCCH duplication on two search spaces of the first cell. In step 1515, the network is allowed to configure PDCCH duplication on two search spaces of the second cell only if two search spaces of the first cell having the same search space identity (ID) as the two search spaces of the second cell have been configured to have PDCCH duplication.

[0522] In one embodiment, a first Physical Downlink Control Channel (PDCCH) candidate of one of two search spaces from a second cell may have the same PDCCH candidate identity (ID) as a second PDCCH candidate of the other of the two search spaces from the second cell. The first PDCCH candidate may be associated with a Transmission Configuration Indication (TCI) state, beam, spatial relation, Quasi-Co-Location (QCL) type D assumption, or spatial filter that is different from that of the second PDCCH candidate. There may be 2 or 3 blind decoding attempts for the first PDCCH candidate and the second PDCCH candidate.

[0523] In one embodiment, the network may not be allowed to configure the UE such that the search space identity (ID) of only one of the two search spaces of the second cell is the same as the search space identity of one of the two search spaces of the first cell. Additionally, the network may not be allowed to configure the UE such that there is no PDCCH duplication for the second search space of the first cell. In one embodiment, the two search spaces of the second cell have Physical Downlink Control Channel duplication only if the two search spaces of the first cell that have the same search space identity as the two search spaces of the second cell have Physical Downlink Control Channel duplication.

[0524] In one embodiment, the network may provide the same first parameter set for configuring any two Search Spaces (SSs) of a cell when two SSs of the cell are linked for PDCCH duplication. The network may not be allowed to provide different first parameter sets for configuring any two SSs of a cell when two SSs of the cell are linked for PDCCH duplication. The first parameter set may include the number of PDCCH candidates (e.g., nrofCandidates) for one or more aggregation levels, monitoringSlotPeriodicityAndOffset, duration, monitoringSymbolsWithinSlot, and searchSpaceType.

[0525] In one embodiment, in response to configuring a link between a third search space (SS) and a fourth SS of a second cell for PDCCH repetition for a UE, the network may provide the same set of first parameters for configuring a first SS and a second SS of a first cell, where the first SS and the third SS may have the same SSID, and the second SS and the fourth SS may have the same SSID. Additionally, in response to configuring a link between a third SS and a fourth SS of a second cell for PDCCH repetition for a UE, the network may not be allowed to provide different sets of first parameters for configuring a first SS and a second SS of a first cell, where the first SS and the third SS may have the same SSID, and the second SS and the fourth SS may have the same SSID.

[0526] In one embodiment, for a first SS and a second SS of a first cell that are linked for PDCCH repetition, a first PDCCH candidate from the first SS may have the same PDCCH candidate ID as a second PDCCH candidate from the second SS, and the first PDCCH candidate and the second PDCCH candidate may schedule the same physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH). For a third SS and a fourth SS of a second cell that are linked for PDCCH repetition, a third PDCCH candidate from the third SS may have the same PDCCH candidate ID as a fourth PDCCH candidate from the fourth SS, and the third PDCCH candidate and the fourth PDCCH candidate may schedule the same PDSCH or PUSCH. The first PDCCH candidate may be associated with a different TCI state, beam, spatial relation, QCL type D assumption, or spatial filter than the second PDCCH candidate. The third PDCCH candidate may be associated with a different TCI state, beam, spatial relation, QCL type D assumption, or spatial filter than the fourth PDCCH candidate. Alternatively, the third PDCCH candidate may be associated with the same TCI state, beam, spatial relation, QCL type D assumption, or spatial filter as the first PDCCH candidate. The fourth PDCCH candidate may be associated with the same TCI state, beam, spatial relation, QCL type D assumption, or spatial filter as the second PDCCH candidate. There may be 2 or 3 blind decoding attempts for the first PDCCH candidate and the second PDCCH candidate, and / or there may be 2 or 3 blind decoding attempts for the third PDCCH candidate and the fourth PDCCH candidate.

[0527] Return reference Figure 3 and 4, in an exemplary embodiment of the network. The network includes program code 312 stored in memory 310. CPU 308 can execute the program code 312 to enable the network to: (i) configure cross-carrier scheduling for the UE, where the network transmits PDCCH on the first cell that schedules the second cell, (ii) configure PDCCH repetition on two search spaces of the first cell for the UE, and (iii) be allowed to configure PDCCH repetition on two search spaces of the second cell for the UE only when two search spaces with the same search space ID in the first cell have been configured to have PDCCH repetition. In addition, CPU 308 can execute the program code 312 to perform all of the above actions and steps or other actions and steps described herein.

[0528] In an alternative method for a network in a wireless communication system, the network configures cross-carrier scheduling for the UE, where the network transmits PDCCH on the first cell that schedules the second cell. In addition, the network configures a first search space (SS) and a second SS of the first cell for the UE. Additionally, the network configures a third SS and a fourth SS of the second cell for the UE, where the third SS has the same SSID as the first SS, and the fourth SS has the same SSID as the second SS, and where if the network configures a link between the first SS and the second SS of the first cell, the third SS is linked to the fourth SS.

[0529] In one embodiment, the network may provide the same set of first parameters for configuring any two SSs of a cell when two SSs of a cell are linked. The network may not be allowed to provide different sets of first parameters for configuring any two SSs of a cell when two SSs of a cell are linked.

[0530] In one embodiment, in response to configuring a link between the first SS and the second SS of the first cell for the UE, the network may provide the same set of first parameters for configuring the third SS and the fourth SS of the second cell. In addition, in response to configuring a link between the first SS and the second SS of the first cell for the UE, the network may not be allowed to provide different sets of first parameters for configuring the third SS and the fourth SS of the second cell. The set of first parameters may include the number of PDCCH candidates (e.g., nrofCandidates) for one or more aggregation levels, monitoringSlotPeriodicityAndOffset, duration, monitoringSymbolsWithinSlot, and searchSpaceType.

[0531] In one embodiment, a first PDCCH candidate from a first SS may have the same PDCCH candidate ID as a second PDCCH candidate from a second SS. A third PDCCH candidate from a third SS may have the same PDCCH candidate ID as a fourth PDCCH candidate from a fourth SS. The first PDCCH candidate may be associated with a different TCI state, beam, spatial relation, QCL type D assumption, or spatial filter than the second PDCCH candidate. The third PDCCH candidate may be associated with a different TCI state, beam, spatial relation, QCL type D assumption, or spatial filter than the fourth PDCCH candidate. There may be 2 or 3 blind decoding attempts for the first PDCCH candidate and the second PDCCH candidate; and / or there may be 2 or 3 blind decoding attempts for the third PDCCH candidate and the fourth PDCCH candidate.

[0532] In one embodiment, if the network does not configure a link between a first SS and a second SS of a first cell for a UE, a third SS may not be linked to a fourth SS. The network may not be permitted to configure different first parameter sets for the third SS and the fourth SS. When the first SS is linked to the second SS, the first PDCCH candidate and the second PDCCH candidate may schedule the same PDSCH or PUSCH, and / or the first PDCCH candidate may provide the same uplink scheduling or downlink assignment as the second PDCCH candidate. When the third SS is linked to the second SS, the third PDCCH candidate and the fourth PDCCH candidate may schedule the same PDSCH or PUSCH, and / or the third PDCCH candidate may provide the same uplink scheduling or downlink assignment as the fourth PDCCH candidate.

[0533] In an alternative method for a UE in a wireless communication system, the UE is configured with CrossCarrierSchedulingConfig, where the UE receives a PDCCH on a first cell that schedules a second cell. Additionally, the UE is configured with a first SS having a first SSID and a second SS having a second SSID of the second cell. Further, the UE is configured with PDCCH repetition on a link of the first SS and the second SS or the first SS and the second SS, where the number of PDCCH candidates for each aggregation level for the first SS and the second SS is the same. And, the UE is configured with a third SS having a first SSID and a fourth SS having a second SSID of the first cell, where the configuration of the third SS and the fourth SS includes at least a first parameter set, a second parameter set, and a third parameter set. The UE does not expect a configuration for the third SS and the fourth SS without a restricted configuration.

[0534] In an alternative method for a network in a wireless communication system, the network configures CrossCarrierSchedulingConfig for a UE, where the network transmits a PDCCH on a first cell that schedules a second cell. In addition, the network configures a first SS with a first SSID and a second SS with a second SSID for the second cell for the UE. Additionally, the network configures PDCCH repetition on the first SS and the second SS or on a link of the first SS and the second SS for the UE, where the number of PDCCH candidates for each aggregation level for the first SS and the second SS is the same. And the network configures a third SS with a first SSID and a fourth SS with a second SSID for the first cell for the UE, where the configuration of the third SS and the fourth SS includes at least a first parameter set, a second parameter set, and a third parameter set. The network provides or configures the third SS and the fourth SS for the UE in a restricted configuration.

[0535] In one embodiment, the restricted configuration may include at least the same value of the second parameter set, and / or the same number of bit positions with a value of 1 from the third parameter set. The restricted configuration may not include the same value of the first parameter set. The first parameter set may include the number of PDCCH candidates (e.g., nrofCandidates) for one or more aggregation levels. The second parameter set may include at least monitoringSlotPeriodicityAndOffset, duration, monitoringSymbolsWithinSlot, and searchSpaceType. The second parameter set may (further) include CORESET-related parameters. The third parameter set may include a bitmap having one or more bit positions with a value of 1 for indicating the starting OFDM symbol (e.g., monitoringSymbolsWithinSlot) of the one or more PDCCH monitoring occasions. The CORESET-related parameters may be associated with one or two search spaces of the scheduling cell. The CORESET-related parameters may include a CORESET ID and / or the number of TCI bits in the DCI on the CORESET (e.g., tci-PresentInDCI and / or tci-PresentDCI-1-2-r16).

[0536] In an alternative method for a UE in a wireless communication system, the UE is configured with CrossCarrierSchedulingConfig, where the UE receives a PDCCH on a first cell that schedules a second cell. Additionally, the UE is configured with PDCCH repetition on the second cell. In response to being configured with PDCCH repetition on the second cell, the UE is configured or expected to be configured with PDCCH repetition on the first cell.

[0537] In one embodiment, the UE may be configured with a first SS of a second cell having a first SSID and a second SS having a second SSID. The UE may be configured with a link or PDCCH repetition of the first SS and the second SS of the second cell. PDCCH repetition on the first cell may mean that a third SS of the first cell having the first SSID and a fourth SS having the second SSID are linked or configured with PDCCH repetition. PDCCH repetition on the first cell may not include an SS of the first cell whose SSID is associated with an SS of the second cell and that does not have a linked SS of the second cell. The configuration of an SS (e.g., an SS of the second cell) may include at least a first set of parameters. The configuration of an SS (e.g., an SS of the first cell) may include at least a first set of parameters, a second set of parameters, and a third set of parameters. For PDCCH repetition for the third SS and the fourth SS, the UE may receive or be expected to be configured with the following configuration: the same first set of parameters, the same second set of parameters, and a restricted / constrained third set of parameters for the third SS and the fourth SS.

[0538] In an alternative method for a UE in a wireless communication system, the UE is configured with CrossCarrierSchedulingConfig, where the UE receives a PDCCH on a first cell that schedules a second cell. The UE is configured with PDCCH repetition on the first cell. In response to being configured with PDCCH repetition on the first cell, the UE is configured or expected to be configured with PDCCH repetition on the second cell.

[0539] In one embodiment, the UE may be configured with a third SS having a first SSID and a fourth SS having a second SSID of a first cell. The UE may be configured with a link or PDCCH repetition of the third SS and the fourth SS of the first cell. PDCCH repetition on a second cell may mean that a first SS having a first SSID and a second SS having a second SSID of the second cell are linked or configured to have PDCCH repetition. PDCCH repetition on the second cell may not include an SS of the second cell whose SSID is associated with an SS of the first cell and which does not have a linked SS of the first cell. The configuration of an SS (e.g., an SS of the second cell) may include at least a first set of parameters. The configuration of an SS (e.g., an SS of the first cell) may include at least a first set of parameters, a second set of parameters, and a third set of parameters. For PDCCH repetition for the first SS and the second SS, the UE may receive or expect a configuration configured to have the same first set of parameters.

[0540] In an alternative method for a network in a wireless communication system, the network configures cross-carrier scheduling (CrossCarrierSchedulingConfig) for the UE, where the network transmits a PDCCH on a first cell scheduling a second cell. In addition, the network configures a first SS having a first SSID and a second SS having a second SSID of the second cell for the UE. The network is not allowed to configure PDCCH repetition on the first cell or the second cell for the UE.

[0541] In an alternative method for a network in a wireless communication system, the network configures multiple cells for the UE. If a cell is an SCell or is cross-carrier / cell scheduled by another cell or the cell is an sPCell cross-carrier / cell scheduled by an SCell, the network is not allowed to configure PDCCH repetition on the cell for the UE.

[0542] In an alternative method for a UE in a wireless communication system, the UE is configured with cross-carrier scheduling (CrossCarrierSchedulingConfig), where the UE receives a PDCCH on a first cell scheduling a second cell. In addition, the UE is configured with PDCCH repetition on a first SS and a second SS of the second cell or on a link of the first SS and the second SS of the second cell. Additionally, the UE is configured with PDCCH repetition on a third SS and a fourth SS of the first cell, where the SSIDs of the third SS and the fourth SS do not overlap with (any) SSIDs of the first SS and the second SS of the second cell (e.g., the two SSIDs are different), and / or the SSIDs of the third SS and the fourth SS completely overlap with the SSIDs of the first SS and the second SS of the second cell (e.g., the same SSID).

[0543] In an alternative method for a UE in a wireless communication system, the UE is configured with CrossCarrierSchedulingConfig, where the UE receives a PDCCH on a first cell that schedules a second cell. Additionally, the UE is configured with PDCCH repetition on a third SS and a fourth SS of the first cell or on a link of the third SS and the fourth SS of the first cell. Further, the UE is configured with PDCCH repetition on a first SS and a second SS of the second cell, where the SSID of the first SS and the second SS does not overlap (e.g., the two SSIDs are different) with any SSID of the third SS and the fourth SS of the first cell, and / or the SSID of the first SS and the second SS completely overlaps (e.g., the same SSID) with the SSID of the third SS and the fourth SS of the first cell.

[0544] In an alternative method for a UE in a wireless communication system, the UE is configured with CrossCarrierSchedulingConfig, where the UE receives a PDCCH on a first cell that schedules multiple cells. Additionally, the UE is configured with PDCCH repetition on a first SS and a second SS of the first cell or of one of the multiple cells. Further, the UE is configured with PDCCH repetition on a third SS and a fourth SS of the first cell or of another one of the multiple cells, where the SSID of the third SS and the fourth SS does not overlap (e.g., the two SSIDs are different) with any SSID of the first SS and the second SS, and / or the SSID of the third SS and the fourth SS completely overlaps (e.g., the same SSID) with the SSID of the first SS and the second SS.

[0545] In an alternative method for a UE in a wireless communication system, the UE is configured with CrossCarrierSchedulingConfig, where the UE receives a PDCCH on a first cell that schedules multiple cells. Additionally, the UE is configured with PDCCH repetition on a first SS and a second SS of the first cell or of one of the multiple cells. Further, the UE is configured with PDCCH repetition on a third SS and a fourth SS of the first cell or of another one of the multiple cells, where the UE does not expect the SSID of the third SS and the fourth SS to overlap (partially) with the SSID of the first SS and the second SS (e.g., only one SSID is the same).

[0546] In an alternative method for a network in a wireless communication system, the network configures cross-carrier scheduling (CrossCarrierSchedulingConfig) for a UE, where the network transmits a PDCCH on a first cell of a plurality of cells. Additionally, the network configures PDCCH repetition for the UE on a first SS and a second SS of the first cell or one of the plurality of cells. Further, the network configures PDCCH repetition for the UE on a third SS and a fourth SS of another cell of the first cell or the plurality of cells, where the SSIDs of the third SS and the fourth SS do not overlap (e.g., are different) with the (any) SSIDs of the first SS and the second SS, and / or the SSIDs of the third SS and the fourth SS completely overlap with the SSIDs of the first SS and the second SS (e.g., are the same).

[0547] In an alternative method for a network in a wireless communication system, the network configures cross-carrier scheduling (CrossCarrierSchedulingConfig) for a UE, where the network transmits a PDCCH on a first cell of a plurality of cells. Additionally, the network configures PDCCH repetition for the UE on a first SS and a second SS of the first cell or one of the plurality of cells. Further, the network configures PDCCH repetition for the UE on a third SS and a fourth SS of another cell of the first cell or the plurality of cells, where the network is not allowed to configure such that the SSIDs of the third SS and the fourth SS (partially) overlap with the SSIDs of the first SS and the second SS (e.g., only one SSID is the same).

[0548] Various aspects of the present disclosure have been described above. It should be clear that the teachings herein can be implemented in a wide variety of forms, and any specific structure, function, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art should understand that the aspects disclosed herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in different ways. For example, any number of the aspects set forth herein can be used to implement a device or practice a method. Additionally, this device can be implemented or this method can be practiced by using other structures, functionality, or structures and functionality in addition to or different from one or more of the aspects set forth herein. As examples of some of the above concepts, in some aspects, parallel channels can be established based on a pulse repetition frequency. In some aspects, parallel channels can be established based on a pulse position or offset. In some aspects, parallel channels can be established based on a time-hopping sequence. In some aspects, parallel channels can be established based on a pulse repetition frequency, a pulse position or offset, and a time-hopping sequence.

[0549] Those skilled in the art will understand that any of a variety of different technologies and techniques can be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0550] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithmic steps described in connection with the aspects disclosed herein can be implemented as electronic hardware (e.g., digital implementation, analog implementation, or a combination of both that can be designed using source decoding or some other technique), incorporated into various forms of program or design code with instructions (which for convenience may be referred to herein as "software" or "software modules"), or a combination of both. To clearly illustrate the interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functionality in different ways for each particular application, but such implementation decisions should not be construed as causing a departure from the scope of the present disclosure.

[0551] In addition, the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein can be implemented within or performed by an integrated circuit ("IC"), access terminal, or access point. The IC can include a general-purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and can execute code or instructions residing within the IC, outside the IC, or in both cases. The general-purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. The processor can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0552] It should be understood that any particular order or hierarchy of steps in any disclosed process is an example instance of a method. It should be understood that based on design preferences, the specific order or hierarchy of steps in a process can be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the steps in an example order and are not meant to be limited to the specific order or hierarchy presented.

[0553] The steps of a method or algorithm described in connection with the various aspects disclosed herein can be implemented directly in hardware, in a software module executed by a processor, or in a combination of the two. Software modules (e.g., including executable instructions and related data) and other data can reside in a data memory, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. An example storage medium can be coupled to a machine such as a computer / processor (for convenience, the machine can be referred to herein as a "processor") such that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. The example storage medium can be integral with the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user device. In an alternative, the processor and the storage medium can reside as discrete components in a user device. Further, in some aspects, any suitable computer program product can include a computer-readable medium that includes code associated with one or more of the aspects of the present disclosure. In some aspects, the computer program product can include packaging material.

[0554] Although the invention has been described in connection with various aspects, it is to be understood that the invention is capable of further modification. This application is intended to cover any variations, uses, or adaptations of the invention that generally follow the principles of the invention and include such departures from the present disclosure as come within known and customary practice within the art to which the invention pertains.

[0555] Cross - reference to related applications

[0556] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 180,870, filed Apr. 28, 2021, the entire disclosure of which is incorporated herein by reference in its entirety.

Claims

1. A method for a network in a wireless communication system, characterized in that, Comprising: The network configures cross-carrier scheduling for a user equipment, wherein the network transmits a physical downlink control channel on a first cell that schedules a second cell; And The network configures repetition of the physical downlink control channel on the first two search spaces of the second cell for the user equipment, wherein the network shall configure repetition of the physical downlink control channel on the second two search spaces of the first cell for the user equipment, and the search space identities of the first two search spaces of the second cell are the same as the search space identities of the second two search spaces of the first cell.

2. The method according to claim 1, wherein A first physical downlink control channel candidate from one search space of the first two search spaces of the second cell has the same physical downlink control channel candidate identity as a second physical downlink control channel candidate from the other search space of the first two search spaces of the second cell.

3. The method according to claim 2, wherein The first physical downlink control channel candidate is associated with a transmission configuration indication state, beam, spatial relation, quasi co-location type D assumption, or spatial filter different from those of the second physical downlink control channel candidate.

4. The method according to claim 2, characterized in that There are 2 or 3 blind decoding attempts for the first physical downlink control channel candidate and the second physical downlink control channel candidate.

5. The method according to claim 1, characterized in that, The network is not allowed to configure the user equipment such that the search space identity of only one search space of the first two search spaces of the second cell is the same as the search space identity of one search space of the second two search spaces of the first cell.

6. The method according to claim 1, wherein The network is not allowed to configure the user equipment such that there is no repetition of the physical downlink control channel in the second two search spaces of the first cell.

7. A method for a network in a wireless communication system, characterized in that, Comprising: The network configures cross-carrier scheduling for a user equipment, wherein the network transmits a physical downlink control channel on a first cell that schedules a second cell; The network configures repetition of the physical downlink control channel on two search spaces of the first cell for the user equipment; And The network is allowed to configure repetition of the physical downlink control channel on the two search spaces of the second cell for the user equipment only when the two search spaces of the first cell having the same search space identity as the two search spaces of the second cell have been configured to have repetition of the physical downlink control channel.

8. The method according to claim 7, wherein A first physical downlink control channel candidate from one search space of the two search spaces of the second cell has the same physical downlink control channel candidate identity as a second physical downlink control channel candidate from the other search space of the two search spaces of the second cell.

9. The method according to claim 8, wherein The first physical downlink control channel candidate is associated with a transmission configuration indication state, beam, spatial relation, quasi co-location type D assumption, or spatial filter different from those of the second physical downlink control channel candidate.

10. The method according to claim 8, characterized in that, There are 2 or 3 blind decoding attempts for the first physical downlink control channel candidate and the second physical downlink control channel candidate.

11. The method according to claim 7, wherein The network is not allowed to configure the user equipment such that the search space identity of only one of the two search spaces of the second cell is the same as the search space identity of one of the two search spaces of the first cell, and / or The network is not allowed to configure the user equipment such that there is no physical downlink control channel repetition for the two search spaces of the first cell.

12. The method according to claim 7, wherein Only when the two search spaces of the first cell having the same search space identity as the two search spaces of the second cell have physical downlink control channel repetition, the two search spaces of the second cell have physical downlink control channel repetition.

13. The method according to claim 7, wherein The network shall provide the same first parameter set for configuring the two search spaces of a cell when any two search spaces of a cell are linked for physical downlink control channel repetition, and / or where the network is not allowed to provide different first parameter sets for configuring the two search spaces of a cell when any two search spaces of a cell are linked for physical downlink control channel repetition.

14. The method according to claim 13, wherein The first parameter set includes the number of physical downlink control channel candidates for one or more aggregation levels, monitoringSlotPeriodicityAndOffset, duration, monitoringSymbolsWithinSlot, and searchSpaceType.

15. The method according to claim 7, wherein In response to configuring a link between a third search space and a fourth search space of the second cell for the user equipment for physical downlink control channel repetition, the network shall provide the same first parameter set for configuring a first search space and a second search space of the first cell, where the first search space and the third search space have the same search space identity and the second search space and the fourth search space have the same search space identity, and / or In response to configuring a link between a third search space and a fourth search space of the second cell for the user equipment for physical downlink control channel repetition, the network is not allowed to provide different first parameter sets for configuring the first search space and the second search space of the first cell, where the first search space and the third search space have the same search space identity and the second search space and the fourth search space have the same search space identity.

16. The method according to claim 7, wherein For the first search space and the second search space of the first cell being linked for physical downlink control channel repetition, a first physical downlink control channel candidate from the first search space has the same physical downlink control channel candidate identity as a second physical downlink control channel candidate from the second search space, and the first physical downlink control channel candidate and the second physical downlink control channel candidate schedule the same physical downlink shared channel or physical uplink shared channel, and / or The third search space and the fourth search space for the second cell are linked for physical downlink control channel repetition. The third physical downlink control channel candidate from the third search space has the same physical downlink control channel candidate identity as the fourth physical downlink control channel candidate from the fourth search space, and the third physical downlink control channel candidate and the fourth physical downlink control channel candidate schedule the same physical downlink shared channel or physical uplink shared channel.

17. The method according to claim 16, wherein The first physical downlink control channel candidate is associated with a transmission configuration indication state, beam, spatial relation, quasi co-location type D assumption, or spatial filter different from that of the second physical downlink control channel candidate, and / or The third physical downlink control channel candidate is associated with a transmission configuration indication state, beam, spatial relation, quasi co-location type D assumption, or spatial filter different from that of the fourth physical downlink control channel candidate, and / or The third physical downlink control channel candidate is associated with a transmission configuration indication state, beam, spatial relation, quasi co-location type D assumption, or spatial filter identical to that of the first physical downlink control channel candidate, and / or The fourth physical downlink control channel candidate is associated with a transmission configuration indication state, beam, spatial relation, quasi co-location type D assumption, or spatial filter identical to that of the second physical downlink control channel candidate.

18. The method according to claim 16, wherein There are 2 or 3 blind decoding attempts for the first physical downlink control channel candidate and the second physical downlink control channel candidate, and / or there are 2 or 3 blind decoding attempts for the third physical downlink control channel candidate and the fourth physical downlink control channel candidate.

19. A network in a wireless communication system, characterized in that, Comprising: A control circuit; A processor installed in the control circuit; And A memory installed in the control circuit and operatively coupled to the processor; Wherein the processor is configured to execute program code stored in the memory to: Configure cross-carrier scheduling for a user equipment, wherein the network transmits a physical downlink control channel on a first cell that schedules a second cell; and Configure physical downlink control channel repetition on the first two search spaces of the second cell for the user equipment, wherein the network should configure physical downlink control channel repetition on the second two search spaces of the first cell for the user equipment, and the search space identities of the first two search spaces of the second cell are the same as the search space identities of the second two search spaces of the first cell.

20. A network in a wireless communication system, characterized in that, Comprising: A control circuit; A processor installed in the control circuit; And A memory installed in the control circuit and operatively coupled to the processor; Wherein the processor is configured to execute program code stored in the memory to: Configure cross-carrier scheduling for a user equipment, wherein the network transmits a physical downlink control channel on a first cell that schedules a second cell; Configure physical downlink control channel repetition for the user equipment on two search spaces in the first cell; And Be allowed to configure physical downlink control channel repetition for the user equipment on the two search spaces in the second cell only when the two search spaces in the first cell having the same search space identity as the two search spaces in the second cell have been configured to have physical downlink control channel repetition.

Images