Coverage enhancement method for physical downlink channel, and controller and communication device

Abstract

Disclosed in the present application are a coverage enhancement method for a physical downlink channel, and a controller and a communication device. The method comprises: receiving first signaling (S110); and determining transmission configuration parameters for at least one target physical downlink channel, wherein the transmission configuration parameters include an enable state of repeated transmission and / or the number of times of repeated transmission (S120).

Description

Methods, controllers and communication equipment for enhancing coverage of downlink physical channels

[0001] Cross-reference to related applications

[0002] This application is based on and claims priority to Chinese Patent Application No. 202510378822.1, filed on March 27, 2025, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of network communication technology, and in particular to a method, controller and communication device for enhancing coverage of downlink physical channels. Background Technology

[0004] Future communication systems need to be applicable to more scenarios, including those requiring deep coverage. For example, 5G and 6G wireless communication systems need to support non-terrestrial networks and maritime communications. In these scenarios, due to the large distance between users and network nodes, path loss during signal transmission is much greater than in traditional terrestrial communication networks. Therefore, it is necessary to consider enhancing the coverage capability of the downlink physical channel to ensure that users can successfully receive downlink signals.

[0005] However, the current traditional terrestrial network coverage enhancement for downlink physical channels is only applicable to user terminals in the connected state, and not to user terminals in the idle state or initial access state. In this case, the signaling that the user terminal can receive is very limited. Therefore, it is necessary to propose new coverage enhancement methods for non-terrestrial networks, marine communications and other scenarios. Summary of the Invention

[0006] The following is an overview of the subject matter described in detail herein. This overview is not intended to limit the scope of the claims.

[0007] This application provides a method, controller, and communication device for enhancing downlink physical channel coverage, which can be applied to scenarios such as non-terrestrial networks and marine communications to enhance downlink physical channel coverage.

[0008] In a first aspect, embodiments of this application provide a method for enhancing coverage of a downlink physical channel, applied to a first node. The method includes: receiving a first signaling; determining transmission configuration parameters for at least one target downlink physical channel, the transmission configuration parameters including an enable state for repeated transmission and / or the number of repeated transmissions.

[0009] Secondly, embodiments of this application provide a controller, including at least one processor and a memory for communicatively connecting to the at least one processor; the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the coverage enhancement method as described above.

[0010] Thirdly, embodiments of this application provide a communication device, including the controller as described above.

[0011] The downlink physical channel coverage enhancement method, controller, and communication device provided in this application embodiment, wherein the first node determines the transmission configuration parameters of at least one target downlink physical channel through the first signaling, is applicable to scenarios such as non-terrestrial networks and marine communications for downlink physical channel coverage enhancement.

[0012] Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures particularly pointed out in the description, claims and drawings. Attached Figure Description

[0013] The accompanying drawings are used to provide a further understanding of the technical solutions of this application and form part of the specification. They are used together with the examples of this application to explain the technical solutions of this application and do not constitute a limitation on the technical solutions of this application.

[0014] Figure 1 is an overall flowchart of a downlink physical channel coverage enhancement method provided in an embodiment of this application;

[0015] Figure 2 is a flowchart illustrating the transmission configuration parameters of multiple target downlink physical channels through different indication information, according to an embodiment of this application.

[0016] Figure 3 is a flowchart illustrating the transmission configuration parameters of multiple target downlink physical channels jointly indicated by an indication information according to an embodiment of this application;

[0017] Figure 4 is a flowchart of determining the transmission configuration parameters of the second target downlink physical channel according to an embodiment of this application;

[0018] Figure 5 is a flowchart illustrating the determination of the number of retransmissions of the second target downlink physical channel according to an embodiment of this application;

[0019] Figure 6 is a flowchart illustrating optional first and / or second values ​​for network-side indication according to an embodiment of this application;

[0020] Figure 7 is a flowchart of determining the enable of repeated transmission based on the number of repeated transmissions according to an embodiment of this application;

[0021] Figure 8 is a flowchart illustrating the determination of the number of repeated transmissions based on the enable of repeated transmissions according to an embodiment of this application;

[0022] Figure 9 is a flowchart of a PDCCH detection using two blind detection methods provided in an embodiment of this application;

[0023] Figure 10 is a schematic diagram of the structural connection of a controller provided in an embodiment of this application. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. Furthermore, the features, operations, or characteristics described in the specification can be combined in any suitable manner to form various implementations. Simultaneously, the steps or actions described in the method description can be rearranged or adjusted in a manner readily apparent to those skilled in the art. Therefore, the various orders in the specification and drawings are merely for the clear description of a particular embodiment and do not imply a mandatory order, unless otherwise stated that a particular order must be followed.

[0025] In the description of this application, "several" means one or more, "more than" means two or more, "greater than," "less than," and "exceeding" are understood to exclude the stated number, while "above," "below," and "within" are understood to include the stated number. The use of "first" and "second" in the description is merely for distinguishing technical features and should not be construed as indicating or implying relative importance, or implicitly indicating the number of indicated technical features, or implicitly indicating the order of the indicated technical features.

[0026] The serial numbers assigned to components in this document, such as "first" and "second," are used only to distinguish the described objects and have no sequential or technical meaning. The terms "connection" and "linkage" used in this application, unless otherwise specified, include both direct and indirect connections (linkages).

[0027] Future communication systems need to be applicable to more scenarios, including deep coverage scenarios. For example, 5G and 6G wireless communication systems need to support non-terrestrial networks (NTN) and marine communications. In these scenarios, due to the long distance between user terminals and network nodes, the path loss during signal transmission is much greater than in traditional terrestrial communication networks. Therefore, it is necessary to consider enhancing the coverage capability of downlink physical channels to ensure that user terminals can successfully receive downlink signals. Downlink physical channels include PDCCH (Physical Downlink Control Channel) and PDSCH (Physical Downlink Shared Channel), while in NB-IoT (Narrow Band Internet of Things), downlink physical channels include NPDCCH (Narrowband Physical Downlink Control Channel) and NPDSCH (Narrowband Physical Downlink Shared Channel).

[0028] Currently, traditional terrestrial networks have enhanced the downlink physical channel to some extent, but this is mainly applicable to user terminals in the connected state and not to scenarios such as idle state or initial access. In the aforementioned non-terrestrial network and marine communication scenarios, it is difficult for user terminals to achieve reliable coverage enhancement before entering the connected state.

[0029] Furthermore, when enhancing downlink coverage, time-domain repetition is typically used. However, prolonged data repetition can block control signaling transmission. To address this, NB-IoT has introduced downlink intervals, which force terminal data repetition, allowing user terminals to receive NPDCCH data during NPDSCH repetition. However, currently, the downlink interval is determined based on absolute system frame and subframe numbers, without considering whether the system frame or subframe within the downlink interval is used for downlink transmission, potentially rendering the downlink interval ineffective.

[0030] It should be noted that the embodiments of this application are applied to a wireless communication system, which includes a terminal and network-side equipment. The terminal is a terminal device or UE (User Equipment), such as a mobile phone, tablet, computer, smart wearable device, or vehicle-mounted device. The network-side equipment can be a base station or core network, etc., and is not specifically limited here.

[0031] The aforementioned repetitive transmissions include PDCCH repetitive transmissions and PDSCH repetitive transmissions. PDCCH repetitive transmission can be defined as follows: multiple PDCCHs transmit the same DCI (downlink control information) using the same AL (aggregation level), and the encoded bits carried in these multiple PDCCHs are also identical. In this application, "PDCCH repetition" is also referred to as "PDCCH repetition" or "PDCCH retransmission," and "PDCCH used for repetitive DCI transmission" can also be referred to as "PDCCH retransmission." This will not be repeated below.

[0032] More specifically, if a network node configures two search spaces (SSs) for a user and sets the same `searchSpaceLinkingId` in both SSs, then the two SSs can be considered associated. The network node can then transmit duplicate PDCCHs between the associated SSs. The user terminal improves PDCCH detection performance by detecting these duplicate PDCCHs. However, the above-mentioned SS association configuration can only be performed after the user enters the connected state. Furthermore, the following SSs do not support association with other SSs: `SS set 0,searchSpaceSIB1,searchSpaceOtherSystemInformation,pagingSearchSpace,ra-SearchSpace,searchSpaceMCCH,searchSpaceMTCH,peiSearchSpace, and sdt-SearchSpace`. Therefore, PDCCH repetition based on associated SSs is not applicable to common PDCCH CSSs such as Type0-PDCCH CSS, Type0A-PDCCH CSS, Type0B-PDCCH CSS, Type1-PDCCH CSS, Type1A-PDCCH CSS, Type2-PDCCH CSS, and Type2A-PDCCH CSS. In other words, it cannot be used for SIB (System information block) scheduling, scheduling during initial access, paging scheduling, or SDT (Small Data Transmission) scheduling. Currently, PDCCH repetition only supports repetitive transmission within a time slot. In the two associated SSs, the detection timing and PDCCH candidates need to have a one-to-one mapping relationship. For the two associated PDCCH candidates, the UE can report whether to perform two or three blind detections, or whether to count them as two or three PDCCH candidates.

[0033] PDSCH retransmission appears in the current protocol to improve PDSCH coverage performance. However, PDSCH retransmission configuration can only be performed after the UE enters the connected state. Therefore, PDSCH retransmission is not applicable to public PDSCH or PDSCH configured before receiving UE-specific PDSCH, such as the PDSCH corresponding to SIB, Msg2, MsgB, Msg4, paging PDSCH, etc.

[0034] Based on this, this application provides a method, controller, and communication device for enhancing the coverage of the downlink physical channel, considering how to enhance the coverage performance of the downlink common transmission channel before the user terminal enters the connected state.

[0035] The following describes the downlink physical channel coverage enhancement method, controller, and communication device of this application through specific embodiments.

[0036] Referring to Figure 1, the downlink physical channel coverage enhancement method is applied to the first node. The coverage enhancement method includes, but is not limited to, the following steps:

[0037] Step S110: Receive the first signaling;

[0038] Step S120: Determine the transmission configuration parameters of at least one target downlink physical channel, including the enable state of repeated transmission and / or the number of repeated transmissions.

[0039] The first node receives a first signaling instruction from the network side. This first node can be a user communication device such as a user terminal (UE), and the network side can be a network device such as a base station. The first instruction specifies coverage enhancement parameters for one or more target downlink physical channels, i.e., it instructs the repeated transmission of one or more target downlink physical channels, enabling the UE to detect the target downlink physical channels and achieve coverage enhancement. These transmission configuration parameters correspond to the coverage enhancement parameters for the target downlink physical channels. Based on the first signaling instruction, the UE can determine the enabled state of the target downlink physical channel and / or the number of repeated transmissions.

[0040] In existing technologies, when a user terminal accesses a network, it typically goes through the following process:

[0041] 1.1 The user terminal searches for the SSB (Synchronization Signal and PBCH block) and demodulates the PBCH (Physical Broadcast Channel) to obtain the MIB (Master Information Block) information. The MIB contains the relevant configurations of the SIB1 PDCCH, namely searchSpaceZero and controlResourceSetZero.

[0042] 1.2 Based on the information indicated by the MIB, detect the Type 0-PDCCH and the scheduled SIB1. SIB1 contains basic system messages, as well as configurations for other common channels, such as Type 0A-PDCCH CSS, Type 1-PDCCH CSS, etc.

[0043] 1.3 After obtaining the necessary system information (such as SIB1 and SIB19), the random access procedure is initiated. The random access procedure may include the user sending Msg1 (random access preamble), receiving Msg2 (random access response RAR message), sending Msg3 (containing user identification code, etc.), and receiving Msg4 (contention resolution message). Alternatively, the random access procedure may include the user sending MsgA (Msg1PRACH and MsgA PUSCH, corresponding to the random access preamble and a message containing the user identification code), and receiving MsgB (MsgB PDCCH and MsgB PDSCH, corresponding to control information and a random access response message (possibly containing contention resolution or fallback information)). The Type 1-PDCCH CSS is used to detect the PDCCH during this process.

[0044] 1.4 After the random access procedure is completed, the network node can configure dedicated resources for the user, such as the USS and dedicated PDSCH configuration. The USS can then be used to schedule user-dedicated data and transmit it according to the dedicated PDSCH configuration.

[0045] As previously mentioned, neither the common PDCCH nor the common PDSCH supports repeated transmissions before the UE enters the connected state or receives UE-specific configuration. Furthermore, during initial access, especially when detecting the PDSCH corresponding to Type 0-PDCCH CSS and SIB1, the signaling the UE can receive is very limited. Therefore, when enhancing the common PDCCH and common PDSCH, a combined configuration / indication can be considered to save signaling. For example, a single signaling instruction can be used to indicate / configure the enabling / activation / number of repeated transmissions of the common PDCCH and common PDSCH.

[0046] Among them, the aforementioned common PDCCH and common PDSCH are both types of target downlink physical channels, and the target downlink physical channel may also include synchronization signal block (SSB).

[0047] The public PDCCH includes at least one of the PDCCH public search space CSS and / or at least one of the PDCCHs that use cell-level PDCCH parameters (PDCCH-ConfigCommon);

[0048] The common PDSCH includes at least one PDSCH before the UE obtains the proprietary PDSCH configuration (e.g., PDSCH-Config) and / or at least one PDSCH using cell-level PDSCH parameters (PDSCH-ConfigCommon).

[0049] A public PDCCH may include at least one of the following:

[0050] Type0-PDCCH CSS

[0051] Type0A-PDCCH CSS

[0052] Type0B-PDCCH CSS

[0053] Type 1-PDCCH CSS

[0054] Type1A-PDCCH CSS

[0055] Type2-PDCCH CSS

[0056] Type2A-PDCCH CSS

[0057] Type3-PDCCH CSS

[0058] SS0 (searchSpaceZero)

[0059] The PDCCH corresponding to the SS configured in searchSpaceSIB1

[0060] The PDCCH corresponding to the SS configured in searchSpaceOtherSystemInformation

[0061] The PDCCH corresponding to the SS configured in pagingSearchSpace

[0062] The PDCCH corresponding to SS configured in ra-SearchSpace

[0063] The searchSpaceMCCH configuration corresponds to the PDCCH of the SS.

[0064] The searchSpaceMTCH configuration corresponds to the PDCCH of the SS.

[0065] The searchSpaceMulticastMCCH configuration corresponds to the PDCCH of the SS.

[0066] The searchSpaceMulticastMTCH configuration corresponds to the PDCCH of the SS.

[0067] peiSearchSpace's configured SS corresponding to PDCCH

[0068] The PDCCH corresponding to SS configured in sdt-SearchSpace

[0069] A public PDSCH may include at least one of the following:

[0070] SIB1 PDSCH

[0071] SIBx PDSCH(x>1)

[0072] Msg2 PDSCH

[0073] Msg4 PDSCH

[0074] MsgB PDSCH

[0075] paging PDSCH

[0076] PDSCH scheduled by public PDCCH

[0077] PDSCH corresponding to SI-RNTI or PDSCH of DCI scheduling for SI-RNTI scrambled CRC

[0078] PDSCH corresponding to RA-RNTI or PDSCH of DCI scheduling for RA-RNTI scrambled CRC

[0079] PDSCH corresponding to TC-RNTI or PDSCH of DCI scheduling with TC-RNTI scrambled CRC

[0080] The PDSCH corresponding to MsgB-RNTI or the DCI scheduling PDSCH of MsgB-RNTI scrambled CRC

[0081] PDSCH corresponding to P-RNTI or P-RNTI scrambled CRC DCI scheduling PDSCH

[0082] PDSCH corresponding to PEI-RNTI or PDSCH of DCI scheduling for PEI-RNTI scrambled CRC

[0083] PDSCH corresponding to MCCH-RNTI or PDSCH of DCI scheduling with MCCH-RNTI scrambled CRC

[0084] PDSCH corresponding to G-RNTI or PDSCH of DCI scheduling for G-RNTI scrambled CRC

[0085] Obtain the proprietary configuration for the PDSCH corresponding to C-RNTI / CS-RNTI.

[0086] Obtain the PDSCH of the DCI schedule with the proprietary configuration previously scrambled CRC by C-RNTI / CS-RNTI.

[0087] The aforementioned first signaling includes at least one of the following: Master Information Block (MIB), System Information Block (SIB), Physical Broadcast Channel (PBCH), Radio Resource Control (RRC) signaling, Media Access Control Unit (MAC CE), MAC header, MAC subheader, and Downlink Control Information (DCI) signaling.

[0088] In other words, the first signaling (which can notify configuration, signaling, or indicate implementation) may include at least one of the following: MIB, PBCH, SIB1, SIBx (x>=1), RRC signaling, MAC CE, MAC header, MAC subheader, DCI signaling, etc. Specific indication methods may include:

[0089] Define a new / dedicated bit field to indicate,

[0090] Multiplexing / reinterpreting existing bit fields to indicate

[0091] Multiplexing / reinterpreting one or more states / code points of an existing bit field to indicate,

[0092] Introduce new information elements (IEs) to indicate (e.g., enumerate multiple candidate values, indicate one from multiple candidate values, or indicate a specific value).

[0093] Introduce a new MAC CE and use MAC CE for indication.

[0094] A new MAC subheader is introduced, indicated by LCID code points.

[0095] Use relevant information about the scrambling code to indicate (such as RNTI, code sequence, root of the generator code, seed of the generator code, etc.).

[0096] When indicating via DCI, such as introducing a new / dedicated bit field or reusing an existing bit field, corresponding enable / activation signaling may be introduced, for example via MIB / PBCH / SIB / RRC / MAC CE.

[0097] Alternatively, when the network side configures multiple parameters via higher-layer signaling (e.g., SIB1, SIBx, RRC), DCI may be used to further indicate one of the parameters. The DCI will only include new / dedicated bit fields, or reuse / reinterpret existing bit fields, when multiple parameters are enabled / activated / configured by the network side. When indicated via MAC CE or MAC header / subheader, for example, by introducing new / dedicated bit fields or reusing existing bit fields, corresponding enable / activation signaling may be introduced, such as via MIB / PBCH / SIB / RRC.

[0098] Alternatively, when the network side configures multiple parameters via higher-layer signaling (e.g., SIB1, SIBx, RRC), it may use MAC CE or MAC header / subheader to further indicate one of the parameters. New / dedicated bit fields will only be included in the MAC CE or MAC header / subheader when multiple parameters are enabled / activated / configured by the network side, or when existing bit fields are reused / reinterpreted.

[0099] For enable / activation indications, a corresponding information element (IE) may be introduced. When the network side configures / indicates this information element, it indicates enable / activation; when it is not configured / indicated, it indicates disable / de-enable / de-activation. Alternatively, for enable / activation indications, a new bit field or multiplexing / reinterpreting idle / reserved bits in existing signaling may be introduced, such as MIB / PBCH / SIB1 / SIBx. When the bit indicates "1", it indicates enable / activation; when it indicates "0", it indicates disable / de-enable / de-activation; and vice versa.

[0100] In some embodiments, the indication content of the first signaling may vary depending on the specific circumstances and may include at least one of the following:

[0101] The transmission configuration parameters of the first target downlink physical channel and the second target downlink physical channel are indicated by different indication information in the first signaling;

[0102] The transmission configuration parameters of the first target downlink physical channel and the second target downlink physical channel are jointly indicated by the same indication information in the first signaling;

[0103] The transmission configuration parameters of the second target downlink physical channel are determined by the transmission configuration parameters of the first target downlink physical channel.

[0104] In the first scenario described above, the first signaling includes first indication information and second indication information; the transmission configuration parameters of the first target downlink physical channel and the second target downlink physical channel are indicated by different indication information in the first signaling, as shown in Figure 2, and may specifically include:

[0105] Step S210: Indicate the transmission configuration parameters of the first target downlink physical channel through the first indication information;

[0106] Step S220: Indicate the transmission configuration parameters of the second target downlink physical channel through the second indication information;

[0107] In the second scenario, the first signaling includes indication information for indicating transmission configuration parameters; the same indication information in the first signaling jointly indicates the transmission configuration parameters of the first target downlink physical channel and the second target downlink physical channel, as shown in Figure 3, and may specifically include:

[0108] Step S230: The indication information in the first signaling indicates the enabled state of repeated transmission of the first target downlink physical channel and the second target downlink physical channel;

[0109] Alternatively, in step S240, the indication information in the first signaling indicates the number of times the first target downlink physical channel and the second target downlink physical channel are repeatedly transmitted.

[0110] The following examples illustrate the above method of indicating the transmission of configuration parameters:

[0111] For cases where the same instruction information in the first signaling is used in conjunction with the instruction:

[0112] Example 1: Using the same signaling / indication, instruct the PDCCH CSS and SIB1 PDSCH (whether) to use repeated transmissions. This signaling / indication may be achieved by multiplexing idle bits in the MIB or reserved bits in the PBCH.

[0113] Example 2: Use the same signaling / indication to indicate whether Type0-PDCCH CSS and SIB1 PDSCH (are) used for repeated transmission. This signaling / indication may be achieved by multiplexing idle bits in the MIB or reserved bits in the PBCH.

[0114] Example 3: Using the same signaling / indication, indicate whether the Type0-PDCCH CSS and SIB1 PDSCH (as indicated in the MIB) use repeated transmission. This signaling / indication may be achieved by multiplexing idle bits in the MIB or reserved bits in the PBCH.

[0115] Example 4: Use the same signaling / indication to indicate whether SIB1 PDSCH and Msg4 PDSCH or MsgB PDSCH (whether) use repeated transmissions. This signaling / indication may be achieved by multiplexing idle bits in the MIB, reserved bits in the PBCH, or scheduling the PDCCH of SIB1.

[0116] Example 5: Using the same signaling / indication, instruct Type1-PDCCH CSS and Msg4 PDSCH or MsgB PDSCH (whether) to use repeated transmission. This signaling / indication may be achieved by multiplexing idle bits in the MIB, reserved bits in the PBCH, information elements in SIB1, or dedicated RRC signaling.

[0117] Example 6: Use the same signaling / indication to indicate whether PDCCH CSS, SIB1 PDSCH, and Msg4 PDSCH or MsgB PDSCH (are) used for repeated transmission. This signaling / indication may be achieved by multiplexing idle bits in the MIB or reserved bits in the PBCH.

[0118] Example 7: Use the same signaling / indication to indicate whether Type0-PDCCH CSS, SIB1 PDSCH, and Msg4 PDSCH or MsgB PDSCH (whether) use repeated transmission. This signaling / indication may be achieved by multiplexing idle bits in the MIB or reserved bits in the PBCH.

[0119] Example 8: Using the same signaling / indication, instruct whether the Type0-PDCCH CSS, SIB1 PDSCH, and Msg4 PDSCH or MsgB PDSCH indicated in the MIB (are) used for repeated transmission. This signaling / indication may be achieved by multiplexing idle bits in the MIB or reserved bits in the PBCH.

[0120] Referring to Figure 4, the case where the transmission configuration parameters of the second target downlink physical channel are determined by the transmission configuration parameters of the first target downlink physical channel includes at least one of the following:

[0121] Step S310: The indication information in the first signaling indicates the enable state of repeated transmission of the first target downlink physical channel, and the enable state of repeated transmission of the second target downlink physical channel is determined according to the enable state of repeated transmission of the first target downlink physical channel.

[0122] That is, whether the first target downlink physical channel (first common PDCCH or first common PDSCH) applies coverage enhancement or retransmission may be determined by whether the second target downlink physical channel (second common PDCCH or second common PDSCH) applies coverage enhancement or retransmission. The network side may configure / instruct whether the second common PDCCH or second common PDSCH applies / enables / activates retransmission. The number of retransmissions of the first common PDCCH or first common PDSCH may be configured / instructed by the network side, and its value may be different from that of the second common PDCCH or second common PDSCH.

[0123] Step S320: The indication information in the first signaling indicates the number of times the first target downlink physical channel is repeatedly transmitted, and the number of times the second target downlink physical channel is repeatedly transmitted is determined based on the number of times the first target downlink physical channel is repeatedly transmitted.

[0124] That is, the number of retransmissions of the first public PDCCH or the first public PDSCH may be determined by the number of retransmissions of the second public PDCCH or the second public PDSCH.

[0125] Step S330: The indication information in the first signaling indicates the enable state of repeated transmission of the first target downlink physical channel, and the number of repeated transmissions of the second target downlink physical channel is determined according to the enable state of repeated transmission of the first target downlink physical channel.

[0126] That is, the number of retransmissions of the first public PDCCH or the first public PDSCH may be determined by whether the second public PDCCH or the second public PDSCH applies / enables / activates coverage enhancement or retransmission. For example, when the second public PDCCH or the second public PDSCH applies / enables / activates coverage enhancement or retransmission, the number of retransmissions of the first public PDCCH or the first public PDSCH is the first number of retransmissions; when the second public PDCCH or the second public PDSCH does not apply / deactivate / deactivate coverage enhancement or retransmission, the number of retransmissions of the first public PDCCH or the first public PDSCH is the second number of retransmissions.

[0127] Step S340: The indication information in the first signaling indicates the number of times the first target downlink physical channel is repeatedly transmitted, and the enable state of the second target downlink physical channel is determined according to the number of times the first target downlink physical channel is repeatedly transmitted.

[0128] In other words, whether the first public PDCCH or the first public PDSCH applies / enables / activates coverage enhancement or repeats transmission may be determined by the number of repeats of the second public PDCCH or the second public PDSCH. For example, if the number of repeats of the second public PDCCH or the second public PDSCH is the first repetition number, then the first public PDCCH or the first public PDSCH applies / enables / activates coverage enhancement or repeats transmission; if the number of repeats of the second public PDCCH or the second public PDSCH is the second repetition number, then the first public PDCCH or the first public PDSCH does not apply / de-enable / de-activate coverage enhancement or repeats transmission.

[0129] In step S310, the enable state for repeated transmission of the second target downlink physical channel is determined. The number of repeated transmissions of the second target downlink physical channel can also be indicated / configured by the network side, specifically including:

[0130] The system receives a second signaling message and determines the number of times the second target downlink physical channel is repeatedly transmitted based on the indication information in the second signaling message. The indication information in the second signaling message is used to indicate the number of repetitions, or to indicate the number of times the second target downlink physical channel is repeatedly transmitted based on the number of times the first target downlink physical channel is repeatedly transmitted, or to indicate a scaling factor of the number of times the second target downlink physical channel is repeatedly transmitted relative to the number of times the first target downlink physical channel is repeatedly transmitted.

[0131] Regarding the case of step S310 above, several examples are provided below for illustration:

[0132] Example 9: When PDCCH CSS applies repeated transmissions, SIB1 PDSCH also applies repeated transmissions. The network side may configure / indicate whether PDCCH CSS applies repeated transmissions, or whether repeated transmissions are enabled / activated. The network side may configure / indicate the number of repetitions for SIB1 PDSCH. The number of repetitions for SIB1 PDSCH may differ from that of PDCCH CSS.

[0133] Example 10: When duplicate transmission is applied to the Type0-PDCCH CSS, duplicate transmission is also applied to the SIB1 PDSCH. The network side may configure / instruct whether duplicate transmission is applied to the Type0-PDCCH CSS, or whether duplicate transmission is enabled / activated.

[0134] Example 11: When duplicate transmission is applied to the Type0-PDCCH CSS indicated in the MIB, duplicate transmission is also applied to the SIB1 PDSCH. The network side may configure / indicate whether duplicate transmission is applied to the Type0-PDCCH CSS indicated in the MIB, or whether duplicate transmission is enabled / activated.

[0135] Example 12: When SIB1 PDSCH applies repeated transmissions, Msg4 PDSCH also applies repeated transmissions. The network side may configure / indicate whether SIB1 PDSCH applies repeated transmissions, or whether repeated transmissions are enabled / activated. The network side may configure / indicate the number of repetitions for Msg4 PDSCH. The number of repetitions for Msg4 PDSCH may differ from that for SIB1 PDSCH.

[0136] Example 13: When duplicate transmission is applied to Type1-PDCCH CSS, duplicate transmission is also applied to Msg4 PDSCH or MsgB PDSCH. The network side may configure / instruct whether duplicate transmission is applied to Type1-PDCCH CSS, or whether duplicate transmission is enabled / activated.

[0137] Example 14: When PDCCH CSS applies repeated transmissions, SIB1 PDSCH and Msg4 PDSCH or MsgB PDSCH also apply repeated transmissions. The network side may configure / indicate whether PDCCH CSS applies repeated transmissions, or whether repeated transmissions are enabled / activated. The network side may configure / indicate the number of repetitions for SIB1 PDSCH or Msg4 PDSCH. The number of repetitions for SIB1 PDSCH or Msg4 PDSCH may differ from that for PDCCH CSS.

[0138] Example 15: When duplicate transmission is applied to Type0-PDCCH CSS, duplicate transmission is also applied to SIB1 PDSCH and Msg4 PDSCH or MsgB PDSCH. The network side may configure / instruct whether duplicate transmission is applied to Type0-PDCCH CSS, or whether duplicate transmission is enabled / activated.

[0139] Regarding the cases in steps S320 and S310 above where the number of repeated transmissions of the second target downlink physical channel is indicated / configured through the indication information in the second signaling, referring to Figure 5, the number of repeated transmissions can be determined in the following ways:

[0140] Step S410: Increase the number of times the first target downlink physical channel is repeatedly transmitted by a first value to obtain the number of times the second target downlink physical channel is repeatedly transmitted by a first value, where the first value is a non-zero integer.

[0141] Alternatively, in step S420, the number of times the first target downlink physical channel is repeatedly transmitted is multiplied by the second value to obtain the number of times the second target downlink physical channel is repeatedly transmitted, where the second value is not equal to 1.

[0142] Alternatively, in step S430, the number of repeated transmissions of the first target downlink physical channel is increased by a first value and then multiplied by a second value to obtain the number of repeated transmissions of the second target downlink physical channel.

[0143] Alternatively, in step S440, the number of times the first target downlink physical channel is repeatedly transmitted is multiplied by the second value and then added to the first value to obtain the number of times the second target downlink physical channel is repeatedly transmitted.

[0144] The first and / or second values ​​are specified by the protocol or configured by the network side.

[0145] Referring to Figure 6, configuring the first and / or second values ​​on the network side may include the following steps:

[0146] Step S510: Receive multiple optional first values ​​and / or multiple second values ​​configured by the network side;

[0147] Step S520: Determine which of the following first and / or second values ​​to use based on the indication information in the DCI or MAC CE sent by the network side.

[0148] The following example illustrates how the first and / or second values ​​affect the number of repeated transmissions:

[0149] The number of repeated transmissions of the first public PDCCH or the first public PDSCH is equal to the number of repeated transmissions of the second public PDCCH or the second public PDSCH.

[0150] The number of retransmissions of the first common PDCCH or the first common PDSCH (e.g., N1) is the number of retransmissions of the second common PDCCH or the second common PDSCH (e.g., N2) plus an offset value (e.g., M). For example, N1 = N2 + M. Where M may be a positive number, a negative number, or zero.

[0151] The number of retransmissions of the first public PDCCH or the first public PDSCH (e.g., N1) is the number of retransmissions of the second public PDCCH or the second public PDSCH (e.g., N2) multiplied by a first scaling factor (e.g., K). For example, N1 = K * N2. Where K may be greater than 1, less than 1, or equal to 1.

[0152] The number of retransmissions of the first public PDCCH or the first public PDSCH (e.g., N1) is the number of retransmissions of the second public PDCCH or the second public PDSCH (e.g., N2) multiplied by a first scaling factor (e.g., K), and then an offset value (e.g., M). For example, N1 = K * N2 + M.

[0153] The aforementioned offset value M or scaling factor K may be predefined by the protocol or configured on the network side. If the network side configures multiple offset values ​​or scaling factors via higher-layer signaling (e.g., SIB1, SIBx, RRC), the network side may further indicate the offset value or scaling factor used via DCI / MAC CE. The network side may configure / indicate the number of retransmissions of the second public PDCCH or second public PDSCH. Whether the first public PDCCH or first public PDSCH (whether) applies / enables / activates retransmissions may be configured / indicated by the network side, and whether its retransmissions are applied / enabled / activated may differ from that of the second public PDCCH or second public PDSCH. The second public PDCCH or second public PDSCH may be received before the first public PDCCH or first public PDSCH. Specifically, the first public PDCCH or first public PDSCH and the second public PDCCH or second public PDSCH may refer to Examples 9 to 15. For example, in Example 9, the first public PDCCH or the first public PDSCH refers to SIB1 PDSCH, and the second public PDCCH or the second public PDSCH refers to PDCCH CSS.

[0154] For step S340 above, the network side may configure / indicate the number of retransmissions of the second public PDCCH or the second public PDSCH. The number of retransmissions of the first public PDCCH or the first public PDSCH may be configured by the network side, and its number of retransmissions may be different from that of the second public PDCCH or the second public PDSCH. The second public PDCCH or the second public PDSCH may be received before the first public PDCCH or the first public PDSCH. Specifically, the first public PDCCH or the first public PDSCH and the second public PDCCH or the second public PDSCH may refer to Examples 9 to 15. For example, for Example 9, the first public PDCCH or the first public PDSCH refers to SIB1 PDSCH, and the second public PDCCH or the second public PDSCH refers to PDCCH CSS. The first retransmission count may be greater than the second retransmission count. For example, referring to FIG7, step S340 may include the following steps:

[0155] Step S610: If the number of repeated transmissions of the first target downlink physical channel is the third time, determine that the second target downlink physical channel is enabled for repeated transmission.

[0156] And / or, in step S620, if the number of repeated transmissions of the first target downlink physical channel is the fourth time, determine that the second target downlink physical channel is not enabled for repeated transmission.

[0157] The following examples illustrate the situation in step S340:

[0158] Example 16: When the PDCCH CSS repeat transmission count is 2, the SIB1 PDSCH applies / enables / activates repeat transmission; when the PDCCH CSS repeat transmission count is 1, the SIB1 PDSCH does not apply / deactivate / deactivate repeat transmission. Alternatively, when the PDCCH CSS repeat transmission count is 4, the SIB1 PDSCH applies / enables / activates repeat transmission; when the PDCCH CSS repeat transmission count is 2, the SIB1 PDSCH does not apply / deactivate / deactivate repeat transmission.

[0159] Example 17: When the SIB1 PDSCH repeat transmission count is 2, Msg4 PDSCH or MsgB PDSCH applies / enables / activates repeat transmission; when the SIB1 PDSCH repeat transmission count is 1, Msg4 PDSCH or MsgB PDSCH does not apply / de-enable / de-activate repeat transmission. Alternatively, when the SIB1 PDSCH repeat transmission count is 4, Msg4 PDSCH or MsgB PDSCH applies / enables / activates repeat transmission; when the SIB1 PDSCH repeat transmission count is 2, Msg4 PDSCH or MsgB PDSCH does not apply / de-enable / de-activate repeat transmission.

[0160] For step S330 above, the network side may configure / instruct whether the second public PDCCH or second public PDSCH applies / enables / activates coverage enhancement or retransmission. Whether the first public PDCCH or first public PDSCH applies / enables / activates coverage enhancement or retransmission may be configured by the network side, and its application / enablement / activation of coverage enhancement or retransmission may differ from that of the second public PDCCH or second public PDSCH. The second public PDCCH or second public PDSCH may be received before the first public PDCCH or first public PDSCH. Specifically, the first public PDCCH or first public PDSCH and the second public PDCCH or second public PDSCH may refer to Examples 9 to 15. For example, for Example 9, the first public PDCCH or first public PDSCH refers to SIB1 PDSCH, and the second public PDCCH or second public PDSCH refers to PDCCH CSS. The first retransmission count may be greater than the second retransmission count.

[0161] For example, referring to Figure 8, step S330 may include the following steps:

[0162] Step S710: If the first target downlink physical channel enables repeated transmission, determine the number of repeated transmissions of the second target downlink physical channel as the number of the first transmission.

[0163] And / or, in step S720, if the first target downlink physical channel does not enable repeated transmission, determine the number of repeated transmissions of the second target downlink physical channel as the second number.

[0164] The following examples illustrate the situation in step S330:

[0165] Example 18: When PDCCH CSS is applied / enabled / activated for repeated transmission, the SIB1 PDSCH repeated transmission count is 2; when PDCCH CSS is not applied / disabled / deactivated for repeated transmission, the SIB1 PDSCH repeated transmission count is 1. Alternatively, when PDCCH CSS is applied / enabled / activated for repeated transmission, the SIB1 PDSCH repeated transmission count is 4; when PDCCH CSS is not applied / disabled / deactivated for repeated transmission, the SIB1 PDSCH repeated transmission count is 2.

[0166] Example 19: When SIB1 PDSCH applies / enables / activates repeat transmission, the Msg4 PDSCH or MsgB PDSCH repeats 2 times; when SIB1 PDSCH does not apply / deactivate / deactivate repeat transmission, the Msg4 PDSCH or MsgB PDSCH repeats 1 time. Alternatively, when SIB1 PDSCH applies / enables / activates repeat transmission, the Msg4 PDSCH or MsgB PDSCH repeats 4 times; when SIB1 PDSCH does not apply / deactivate / deactivate repeat transmission, the Msg4 PDSCH or MsgB PDSCH repeats 2 times.

[0167] It is understandable that the above-mentioned indication methods may be used in combination. For example, whether the first public PDCCH or the first public PDSCH applies coverage enhancement or repeated transmission is determined by whether the second public PDCCH or the second public PDSCH applies coverage enhancement or repeated transmission, and the number of repeated transmissions of the first public PDCCH or the first public PDSCH may be determined by the number of repeated transmissions of the second public PDCCH or the second public PDSCH.

[0168] Whether to perform repeated transmission of Msg4 PDSCH may be determined based on the UE's capability reporting. The UE may report the capability / request for repeated transmission of Msg4 PDSCH via Msg3. When the network side enables / activates repeated transmission of Msg4 PDSCH, or configures the number of Msg4 PDSCH repetitions, repeated transmission of Msg4 PDSCH will only occur when the UE reports the capability / request for repeated transmission of Msg4 PDSCH. Otherwise, the UE will not perform repeated transmission of Msg4 PDSCH or will not apply the configuration / instruction for repeated transmission of Msg4 PDSCH.

[0169] Example 20: Configure the number of repetitions for Msg4 PDSCH on the network side, for example, via SIB1 / SIBx. However, if SIB1 PDSCH is not retransmitted, then Msg4 PDSCH will not be retransmitted. If SIB1 PDSCH is retransmitted, then Msg4 PDSCH will be retransmitted, and the number of repetitions depends on the network side configuration.

[0170] Example 21: The network side configures the number of repetitions for Msg4 PDSCH, for example, via SIB1 / SIBx. However, if the UE does not report the capability / request for Msg4 PDSCH repetition, then Msg4 PDSCH will not be repetitive. If the UE reports the capability / request for Msg4 PDSCH repetition, then Msg4 PDSCH will be repetitive, and the number of repetitions will be determined according to the network side configuration.

[0171] Example 22: The network side configures the number of repetitions for Msg4 PDSCH, for example, via SIB1 / SIBx. However, if SIB1 PDSCH is not retransmitted or the UE does not report the ability / request for Msg4 PDSCH retransmission, then Msg4 PDSCH will not be retransmitted. If SIB1 PDSCH is retransmitted and the UE reports the ability / request for Msg4 PDSCH retransmission, then Msg4 PDSCH will be retransmitted, and the number of repetitions is determined by the network side configuration.

[0172] Furthermore, for common PDCCH repetition, different indications may be used for different types of common PDCCHs or those with different signaling configurations. For example, before the UE acquires SIB1, it can only acquire the configuration of Type0-PDCCH CSS based on SS0 configured in pdcch-ConfigSIB1 in the MIB. At this time, the UE can only acquire the corresponding configuration of Type0-PDCCH CSS through the MIB or PBCH. Therefore, consider using bits in the MIB or PBCH to indicate whether Type0-PDCCH CSS is enabled / activated / applies repeated transmissions or the number of repeated transmissions. After the UE acquires SIB1, it can configure Type0 PDCCH CSS through SIB1 or dedicated RRC signaling (e.g., searchSpaceSIB1 or searchSpaceZero in PDCCH-ConfigCommon). At this time, consider using information elements of SIB1 or dedicated RRC signaling to indicate whether Type0-PDCCH CSS is enabled / activated / applies repeated transmissions or the number of repeated transmissions. In addition, for Type0A / Type1 / Type2-PDCCH CSS, it can be configured after SIB1. Therefore, it is also possible to use SIB1 information elements or dedicated RRC signaling to indicate whether Type0-PDCCH CSS enables / activates / applies repeat transmissions or the number of repeat transmissions.

[0173] In summary, the following methods for indicating coverage enhancement can be considered: using a first signaling / indication to indicate whether the first public PDCCH is enabled / activated / applies repeated transmissions or the number of repeated transmissions; and using a second signaling / indication to indicate whether the second public PDCCH is enabled / activated / applies repeated transmissions or the number of repeated transmissions.

[0174] The first signaling / indication may refer to the MIB and / or PBCH. For example, it may be indicated in the following ways: an idle bit in the MIB, a reserved bit in the PBCH, a state / code point in an existing bit field in the MIB, a state / code point in an existing bit field in the PBCH, etc.

[0175] The first public PDCCH may refer to at least one of the following:

[0176] Retrieve the Type0 / Type0A / Type0B / Type1 / Type1A / Type2 / Type2A / Type3-PDCCH CSS from SIB1, the Type0 / Type0A / Type0B / Type1 / Type1A / Type2 / Type2A / Type3-PDCCH CSS from SS0, and the Type0 / Type0A / Type0B / Type1 / Type1A / Type2 / Type2A / Type3-PDCCH CSS from SS0 configured in pdcch-ConfigSIB1 within the MIB.

[0177] For example:

[0178] Get Type0-PDCCH CSS prior to SIB1

[0179] Get PDCCH CSS prior to SIB1

[0180] (Configured in pdcch-ConfigSIB1 in the MIB) Type 0 PDCCH CSS on SS0

[0181] (Configured in pdcch-ConfigSIB1 in the MIB) Type 0 PDCCH CSS and Type 0A PDCCH CSS on SS0

[0182] (Configured in pdcch-ConfigSIB1 in MIB) PDCCH CSS other than Type 3 PDCCH CSS on SS0

[0183] (Configured in pdcch-ConfigSIB1 within the MIB) PDCCH CSS on SS0

[0184] The second signaling / indication may be SIB1, SIBx (x>1), dedicated RRC signaling, MAC CE, or DCI. For example, indication can be given through information elements in SIB1 / SIBx.

[0185] The second public PDCCH may refer to at least one of the following:

[0186] Retrieve the Type0 / Type0A / Type0B / Type1 / Type1A / Type2 / Type2A / Type3-PDCCH CSS after SIB1, the Type0 PDCCH CSS configured in searchSpaceSIB1 in PDCCH-ConfigCommon, the Type0 / Type0A / Type0B / Type1 / Type1A / Type2 / Type2A / Type3-PDCCH CSS configured in PDCCH-ConfigCommon, the Type0 / Type0A / Type0B / Type1 / Type1A / Type2 / Type2A / Type3-PDCCH CSS on SS other than SS0, and the Type0 / Type0A / Type0B / Type1 / Type1A / Type2 / Type2A / Type3-PDCCH CSS configured in pdcch-ConfigSIB1 in MIB on SS other than SS0.

[0187] For example:

[0188] Get Type0-PDCCH CSS after SIB1

[0189] Get PDCCH CSS after SIB1

[0190] (Besides SS0) (Configured in searchSpaceSIB1 in PDCCH-ConfigCommon) Type0-PDCCH CSS

[0191] (Besides SS0) Type0-PDCCH CSS and Type0A-PDCCH CSS configured in PDCCH-ConfigCommon

[0192] (Besides SS0) PDCCH CSS other than those configured in PDCCH-ConfigCommon Type3-PDCCH CSS

[0193] (Except for SS0) PDCCH CSS (configured in PDCCH-ConfigCommon)

[0194] More specifically, for repeated common PDCCHs, the enhancements in the following examples can be considered:

[0195] Example 23: The MIB / PBCH is used to indicate whether the Type 0 PDCCH CSS is enabled / activated / applied with repeat transmissions or repeat transmission counts; the SIB1 / SIBx or dedicated RRC signaling is used to indicate whether other types of PDCCH CSS are enabled / activated / applied with repeat transmissions or repeat transmission counts. Other types of PDCCH CSS may include PDCCH CSSs other than Type 0 and Type 3.

[0196] Example 24: The MIB / PBCH is used to indicate whether the public PDCCH on SS0 is enabled / activated / applies duplicate transmissions or the number of duplicate transmissions; the SIB1 / SIBx or dedicated RRC signaling is used to indicate whether the public PDCCH on other SSs is enabled / activated / applies duplicate transmissions or the number of duplicate transmissions. The public PDCCH may not contain Type 3-PDCCH CSS.

[0197] Example 25: The MIB / PBCH is used to indicate whether the Type0-PDCCH CSS configured in pdcch-ConfigSIB1 on SS0 is enabled / activated / applied with repeat transmissions or repeat transmission counts; the SIB1 / SIBx or dedicated RRC signaling is used to indicate whether the Type0-PDCCH CSS or other types of PDCCH CSS configured in searchSpaceSIB1 is enabled / activated / applied with repeat transmissions or repeat transmission counts. Other types of PDCCH CSS may include PDCCH CSSs other than Type0 and Type3.

[0198] Example 26: The MIB / PBCH is used to instruct the UE whether to enable / activate / apply repeated transmissions or the number of repeated transmissions for Type 0-PDCCH CSS prior to SIB1; the SIB1 / SIBx or dedicated RRC signaling is used to instruct the UE whether to enable / activate / apply repeated transmissions or the number of repeated transmissions for Type 0-PDCCH CSS or other types of PDCCH CSS after SIB1. Other types of PDCCH CSS may include PDCCH CSSs other than Type 0 and Type 3.

[0199] Example 27: The MIB / PBCH is used to indicate whether the Type 0-PDCCH CSS on the initial BWP is enabled / activated / applied with repeat transmissions or repeat transmission counts; the SIB1 / SIBx or dedicated RRC signaling is used to indicate whether the Type 0-PDCCH CSS or other types of PDCCH CSS on other BWPs are enabled / activated / applied with repeat transmissions or repeat transmission counts. Other types of PDCCH CSS may include PDCCH CSSs other than Type 0 and Type 3.

[0200] In some embodiments, the downlink physical channel coverage enhancement method further includes: detecting the target downlink physical channel.

[0201] The current protocol already supports repeated PDCCH transmission within a time slot. The mechanism is as described above: the network node configures two Service Controllers (SSs) with the same association ID (searchSpaceLinkingId) for the user. Then, the network node can transmit repeated PDCCHs between the two associated SSs. The detection timing or PDCCH candidate for repeated transmission between the two associated SSs is a one-to-one mapping and must occur within the same time slot; therefore, it is also referred to as repeated PDCCH transmission within a time slot.

[0202] For repeated PDCCH transmissions within the aforementioned time slots, depending on the UE's reporting capabilities, the two associated PDCCH candidates may be counted as two PDCCH candidates or three PDCCH candidates (i.e., performing two or three blind detections). This is mainly because repeated PDCCH transmissions within time slots primarily target multi-TRP transmission scenarios, where two TRPs may each correspond to one SS and transmit one PDCCH transmission respectively. In response, the UE may exhibit the following detection behaviors:

[0203] Two blind detections: detecting the first PDCCH candidate and detecting the second PDCCH candidate;

[0204] Three-stage blind detection: Detect the first PDCCH candidate, detect the second PDCCH candidate, merge the two PDCCH candidates and perform detection.

[0205] However, the repeated transmission of the common PDCCH considered in this application is mainly to compensate for the large path loss in NTN scenarios, primarily targeting single-transmitter-receiver-receiver (STR) scenarios. In this case, it is generally not the case that the UE can only receive the second PDCCH candidate but cannot receive the first PDCCH candidate. At this time, the UE does not need to detect the second PDCCH candidate separately. Alternatively, to reduce the number of blind detections, the UE may only need to merge the detection of two PDCCH candidates, without needing to detect each PDCCH candidate separately. In addition, during the repeated transmission of the common PDCCH, the UE may be in an idle or inactive state, making it difficult to report capabilities.

[0206] Therefore, for repeated transmissions of the common PDCCH within a time slot, a (fixed) detection behavior may be defined in the protocol. This detection behavior may differ from the detection behavior for repeated transmissions of the common PDCCH within a time slot in the USS or Type 3-PDCCH CSS (in legacy protocols). Alternatively, the UE's reporting capabilities may not affect the detection behavior for repeated transmissions of the common PDCCH. The detection behavior for repeated transmissions of the common PDCCH within a time slot includes:

[0207] One-time blind detection: merge the associated PDCCH candidates and perform detection. Alternatively, treat the associated PDCCH candidates in the associated SS as a single PDCCH candidate.

[0208] Two blind detections: Detect the first PDCCH candidate, merge the associated PDCCH candidates and detect them again. Alternatively, treat the associated PDCCH candidates in the associated SS as two PDCCH candidates.

[0209] N blind detections: Detect the first PDCCH candidate, merge the first and second PDCCH candidates and detect them, ..., merge the first to the Nth PDCCH candidates and detect them. Alternatively, in the associated SSs, the associated PDCCH candidates are considered as N PDCCH candidates. N is the number of associated SSs.

[0210] For the i-th PDCCH candidate among N PDCCH candidates, it may refer to the i-th candidate in chronological order among the associated PDCCH candidates. Alternatively, the i-th PDCCH candidate may refer to the PDCCH candidate within the i-th search space. The i-th search space may refer to the search space with the i-th index among the associated search spaces. The order of the index numbers may be ascending, descending, or arranged according to the corresponding PDCCH CSS type (e.g., the order of Type0, Type0A, Type1, Type1A, Type2).

[0211] In addition to intra-slot PDCCH retransmission, inter-slot PDCCH retransmission can also be considered. For example, the network side configures an SS (Security Stream). Starting from the detection time corresponding to the SS, PDCCH retransmission is performed in multiple consecutive or non-consecutive time slots. The retransmitted PDCCH candidates may have the same aggregation level, coded bits, DCI payload, and CCE index. The UE may detect the same PDCCH candidate or PDCCH candidates with the same index / number within multiple time slots where PDCCH retransmission is performed. For inter-slot PDCCH retransmission, the maximum number of detections may be calculated per time slot, per time slot group (e.g., time slots used for PDCCH retransmission), or per detection time. The detection behavior for inter-slot PDCCH retransmission includes:

[0212] One-time blind detection: Combine PDCCH candidates from multiple time slots that are transmitted repeatedly and then detect them. Alternatively, treat the PDCCH candidates from multiple time slots that are transmitted repeatedly as a single PDCCH candidate.

[0213] Two blind detections: Detect the first PDCCH candidate, then merge the PDCCH candidates from multiple repeatedly transmitted time slots and detect them together. Alternatively, treat the PDCCH candidates from multiple repeatedly transmitted time slots as two PDCCH candidates.

[0214] N blind detections: Detect the first PDCCH candidate, merge the first and second PDCCH candidates and detect them, ..., merge the first to the Nth PDCCH candidates and detect them. Alternatively, treat the PDCCH candidates in multiple repeatedly transmitted time slots as N PDCCH candidates. N is the number of times the PDCCH is repeated.

[0215] The i-th PDCCH candidate among N PDCCH candidates may refer to the PDCCH candidate in the i-th time slot occupied by repeated transmissions. Alternatively, it may refer to the i-th PDCCH candidate in chronological order among the repeated transmissions.

[0216] For ease of description, the detection of repeated PDCCH transmission within the above time slot is described as the first blind detection method, and the detection of repeated PDCCH transmission between the above time slots is described as the second blind detection method.

[0217] Inter-slot PDCCH repetition and intra-slot PDCCH repetition may be supported simultaneously. For example, inter-slot PDCCH repetition is supported for Type I public PDCCH, while intra-slot PDCCH repetition is supported for Type II public PDCCH. If Type I and Type II public PDCCH use different SS configurations, such as SSx and SSy respectively, different detection methods can be simply applied to SSx and SSy respectively. However, in existing systems, different types of public PDCCH may use the same SS configuration. For example, Type0-PDCCH CSS and Type1-PDCCH CSS can both be configured as SS0, meaning the UE will detect Type0-PDCCH CSS and Type1-PDCCH CSS in SS0. Therefore, it is possible that the UE will search for different types of public PDCCH using different PDCCH repetition methods in the same SS, requiring clarification of the UE's behavior in this situation. Specifically, detection of the target downlink physical channel includes at least one of the following:

[0218] The first type of PDCCH is detected using the first blind detection method, and the second type of PDCCH is detected using the second blind detection method.

[0219] The first blind detection method was used to detect the PDCCH corresponding to the first type of RNTI, and the second blind detection method was used to detect the PDCCH corresponding to the second type of RNTI.

[0220] In the first state of the first node, the PDCCH is detected using the first blind detection method, and in the second state of the first node, the PDCCH is detected using the second blind detection method.

[0221] The PDCCH is detected using a first blind detection method in the first search space, and a second blind detection method is detected using the second search space.

[0222] The target downlink physical channel is detected using a first blind detection method and a second blind detection method.

[0223] The first type of PDCCH includes Type0-PDCCH CSS, and the second type of PDCCH includes at least one of the following: Type0A-PDCCH CSS, Type1-PDCCH CSS, Type1A-PDCCH CSS, Type2-PDCCH CSS, and Type2A-PDCCH CSS.

[0224] Alternatively, the first type of PDCCH includes Type0-PDCCH CSS and Type0A-PDCCH CSS, and the second type of PDCCH includes at least one of the following: Type1-PDCCH CSS, Type1A-PDCCH CSS, Type2-PDCCH CSS, and Type2A-PDCCH CSS;

[0225] The first type of RNTI includes SI-RNTI, and the second type of RNTI includes at least one of the following: RA-RNTI, TC-RNTI, MsgB-RNTI, P-RNTI, C-RNTI, CS-RNTI and PEI-RNTI;

[0226] The first state includes the state before the first node acquires SIB1, and the second state includes the state after the first node acquires SIB1.

[0227] The first search space is SS0, and the second search space is the search space other than SS0.

[0228] Example 28: In SS, the UE uses different detection methods when detecting different types of PDCCH. Alternatively, the UE uses a first detection method when detecting the first type of PDCCH in SS, and a second detection method when detecting the second type of PDCCH. For example, the first type of PDCCH is Type0-PDCCH CSS, and the second type of PDCCH is at least one of Type0A-PDCCH CSS, Type1-PDCCH CSS, Type1A-PDCCH CSS, Type2-PDCCH CSS, and Type2A-PDCCH CSS. Or, for example, the first type of PDCCH is both Type0-PDCCH CSS and Type0A-PDCCH CSS, and the second type of PDCCH is at least one of Type1-PDCCH CSS, Type1A-PDCCH CSS, Type2-PDCCH CSS, and Type2A-PDCCH CSS. The first detection method is a detection method for repeated transmission of PDCCH between time slots (such as the second blind detection method mentioned above), and the second detection method is a detection method for repeated transmission of PDCCH within a time slot (such as the first blind detection method mentioned above).

[0229] Example 29: In the SS, the UE uses different detection methods when detecting PDCCHs corresponding to different RNTIs (e.g., using different RNTIs to scramble DCI CRC). Alternatively, the UE uses the first detection method when detecting a PDCCH corresponding to the first RNTI (e.g., using the first RNTI to scramble DCI CRC) in the SS; and uses the second detection method when detecting a PDCCH corresponding to the second RNTI (e.g., using the second RNTI to scramble DCI CRC). For example, the first RNTI might be SI-RNTI, and the second RNTI might be RA-RNTI / TC-RNTI / MsgB-RNTI / P-RNTI / C-RNTI / CS-RNTI / PEI-RNTI. The first detection method is for detecting repeated PDCCH transmissions between time slots (e.g., the second blind detection method described above), and the second detection method is for detecting repeated PDCCH transmissions within a time slot (e.g., the first blind detection method described above).

[0230] Example 30: In SS, the UE uses different detection methods when detecting PDCCH in different stages / states. Alternatively, the UE uses the first detection method in the first stage or first state; and the UE uses the second detection method in the second stage or second state. A stage / state may refer to the stage / state in which the UE expects to acquire a certain signaling, or the stage / state in which it has not yet acquired a certain signaling, or the stage / state in which it has not yet sent a certain signaling, or the stage / state in which it has already acquired a certain signaling, or the stage / state in which it has already sent a certain signaling. Signaling may include one of the following: MIB, PBCH, SIB1, SIB19, SIBx (x>1), PRACH, MsgA, Msg2, MsgB, Msg3, Msg4, etc. For example, the first stage or first state may refer to before the UE acquires SIB1; the second stage or second state may refer to after the UE acquires SIB1. In the first stage or first state, a detection method for repeated PDCCH transmissions between time slots (such as the second blind detection method described above) is used; in the second stage or second state, a detection method for repeated PDCCH transmissions within a time slot (such as the first blind detection method described above) is used.

[0231] Example 31: The UE uses different detection methods in different SSs. For example, in SS0, the first detection method is used; in other SSs, the second detection method is used. The first detection method is for detecting repeated PDCCH transmissions between time slots (e.g., the second blind detection method mentioned above), and the second detection method is for detecting repeated PDCCH transmissions within a time slot (e.g., the first blind detection method mentioned above).

[0232] Example 32: Referring to Figure 9, the steps for detecting the target downlink physical channel using the first blind detection method and the second blind detection method, as described above, specifically include:

[0233] Step S810: Take the union of the detection behaviors of the first blind detection method and the second blind detection method to obtain the target detection method;

[0234] Step S820: Detect PDCCH using a target blind detection method.

[0235] In the SS (Security Controller), the UE uses the first detection method and the second detection method simultaneously or sequentially to detect the PDCCH. Alternatively, when the UE detects the PDCCH in the SS, it first uses the first detection method and then uses the second detection method. The PDCCH may be any PDCCH or a common PDCCH. The first detection method is a detection method for PDCCH repetition between time slots (e.g., the detection method described above), and the second detection method is a detection method for PDCCH repetition within a time slot (e.g., the detection method described above). Alternatively, the first detection method is a detection method for PDCCH repetition within a time slot (e.g., the detection method described above), and the second detection method is a detection method for PDCCH repetition between time slots (e.g., the detection method described above). For example, if the first detection method includes {merging associated PDCCH candidates and performing detection}, and the second detection method includes {merging PDCCH candidates from multiple time slots with repetitive transmissions and performing detection}, then the UE's detection behavior may be {merging associated PDCCH candidates and performing detection, merging PDCCH candidates from multiple time slots with repetitive transmissions and performing detection}.

[0236] If the UE successfully detects the PDCCH using the first detection method, it may not continue to detect the PDCCH using the second detection method. If a detection action in the second detection method is the same as a detection action in the first detection method, the UE may skip the corresponding detection action in the second detection method. For example, if the first detection method includes {detecting the first PDCCH candidate, merging associated PDCCH candidates and performing detection}, and the second detection method includes {detecting the first PDCCH candidate, merging PDCCH candidates from multiple time slots that are being transmitted repeatedly and performing detection}, then when executing the second detection method, the UE may skip {detecting the first PDCCH candidate}. That is, the UE's detection actions are, in sequence, {detecting the first PDCCH candidate, merging associated PDCCH candidates and performing detection, merging PDCCH candidates from multiple time slots that are being transmitted repeatedly and performing detection}.

[0237] In some embodiments, the downlink physical channel coverage enhancement method further includes: in TDD mode, if the target downlink physical channel is configured to have a downlink interval, adjusting the downlink interval of the target downlink physical channel.

[0238] Time Division Duplex (TDD) is a duplexing technology commonly used in traditional terrestrial networks. In TDD, a periodic transmission mode is typically defined, allocating a portion of the periodic time domain resources as downlink transmission resources, a portion as uplink transmission resources, and a portion as guard intervals or flexible resources.

[0239] Regarding the transport modes in TDD, the following concepts may be introduced:

[0240] Periodic mode: This may also refer to transmission configuration, transmission mode, periodic configuration, etc. For example, the length or period of a transmission mode is T. Each transmission mode may contain one or more uplink times, downlink times, and guard intervals.

[0241] Uplink time: This may also refer to uplink service time, uplink activation time, uplink configuration time, uplink duration, uplink mode, etc. In TDD mode, uplink and downlink are time-divided resources, meaning that uplink transmission takes place for a portion of the time, downlink transmission takes place for a portion of the time, and additional time is used as a guard interval / protection time or flexible / special time. Uplink time refers to the time used for uplink transmission as defined by the standard protocol or configured by the network (in periodic mode). Here, time may also refer to time-domain resources. For example, uplink time may refer to uplink subframes, available uplink subframes, or NB-IoT uplink subframes, etc.

[0242] Downlink time: This may also refer to downlink service time, downlink activation time, downlink configuration time, downlink duration, downlink mode, etc. Downlink time refers to the time used for downlink transmission as defined by the standard protocol or configured by the network (in periodic mode). Time here may also refer to time-domain resources. For example, downlink time may refer to downlink subframes, available downlink subframes, or NB-IoT downlink subframes, etc.

[0243] Guard interval: This may also refer to guard time, non-service time, inactive time, flexible time, special time, offset time (between uplink and downlink times), non-uplink / downlink time, or time outside of uplink and downlink times. It may be defined by standard protocols or configured by the network. Here, time or interval may also refer to time-domain resources. For example, a guard interval may refer to a subframe not configured as a downlink or uplink subframe, or consecutive subframes between downlink and uplink subframes.

[0244] Non-uplink time: refers to time other than uplink time. It may include downlink time and protection interval.

[0245] Non-downlink time: refers to time other than downlink time. It may include uplink time and protection interval.

[0246] Overlap: This can also refer to overlapping, conflict, collision, or coincidence. It indicates that two resources partially or completely overlap.

[0247] The units or units of time mentioned above may be superframes, frames, subframes, time slots, symbols, samples, resource units, symbol groups, repetition units, etc., or absolute time such as milliseconds. When time resources used for transmission or mapping overlap with non-transmission time, it may be necessary to specify the UE's behavior. For example, if a subframe originally used for PDSCH transmission or mapping overlaps with non-downlink time, the PDSCH transmission overlapping with the non-downlink time may be delayed.

[0248] When using repeated transmissions for coverage enhancement, a single downlink transmission may occupy multiple time slots or subframes. In NB-IoT, the number of NPDSCH repetitions can reach thousands. During NPDSCH repetition reception, the UE may be unable to detect the NPDCCH. Therefore, during long NPDSCH receptions in NB-IoT, the UE may be unable to receive new schedules or indications for an extended period. To enable the UE to receive new schedules or indications in a timely manner under such circumstances, NB-IoT introduces a downlink gap (DL gap). Specifically, the network side can configure a threshold N. gap,threshold When the number of NPDSCH retransmissions exceeds a threshold, i.e., R... max >N gap,threshold When this condition is met, the downlink interval is used. The downlink interval begins in the subframe ns of system frame nf, and the condition is met. Where N gap,period The interval period configured for the network side. The duration of the downlink interval is N. gap,duration =N gap,coeff N gap,period , where N gap,coeff The coefficients configured for the network side. NPDSCH transmissions that originally overlapped with the interval are delayed.

[0249] As can be seen, the downlink interval provides time for scheduling information transmission during long periods of repeated NPDSCH transmissions. In TDD mode, the portion of the downlink interval that overlaps with non-downlink transmission time cannot be used for receiving NPDSCH. Therefore, with the downlink interval duration remaining unchanged, the actual effective time is significantly reduced in TDD mode. Therefore, adjusting the downlink interval of the target downlink physical channel includes at least one of the following:

[0250] The interval period of the downlink interval is increased by the third value;

[0251] Increase the time coefficient of the downlink interval by using the fourth value;

[0252] The duration of the downlink interval is increased by the fifth value;

[0253] Only downlink time or NB-IoT downlink subframes are included in the duration of the downlink interval;

[0254] The threshold corresponding to the downlink interval is lowered by the sixth value;

[0255] If the start time of the downlink interval overlaps with a non-downlink time, the start time of the downlink interval will be delayed to the next downlink time, downlink subframe, downlink resource, or NB-IoT downlink subframe.

[0256] If there is a part of the downlink interval that overlaps with a non-downlink time, the overlapping part will be delayed to the next downlink time, downlink subframe, downlink resource, or NB-IoT downlink subframe;

[0257] Cancel downlink intervals in TDD mode.

[0258] Among them, the third, fourth and fifth values ​​are all greater than the ratio of the length of the periodic pattern to the length of the downlink time within the periodic pattern under TDD mode.

[0259] The sixth value is less than the ratio of the downlink time length to the length of the cycle mode in TDD mode.

[0260] Specifically, at least one of the following enhancements can be made:

[0261] 2.1 Introducing a (larger) configurable downlink interval period N gap,period At this point, in coefficient N gap,coeff Without changing the time frame, the duration of the downlink interval can also be increased. For example, suppose the TDD cycle length is X and the downlink time is Y. If in non-TDD mode, the cycle N... gap,period,old sum coefficient N gap,coeff If the requirements can be met, it means that N gap,duration =N gap,coeff N gap,period The downlink interval length provides sufficient scheduling time. In TDD mode, the configured interval period N... gap,period,new >=X / Y*N gap,period,old At N gap,coeff With the downlink interval duration N remaining unchanged gap,duration,new >=X / Y*N gap,coeff N gap,period,old =X / Y*N gap,duration,old The included downlink time can be greater than N. gap,duration,old This can meet the scheduling requirements.

[0262] In TDD mode, the downlink interval period is increased by a second scaling factor, for example, N. gap,period,TDD =K period *N gap,period Kperiod It may be predefined by the protocol, configured on the network side, or determined / derived by the UE / network side. The duration of the downlink interval is determined by the scaled interval period, for example, N. gap,duration,TDD =N gap,coeff N gap,period,TDD =K period *N gap,coeff N gap,period Assuming the TDD cycle length is X and the downlink time is Y, if K... period If the downlink interval duration is greater than or equal to X / Y, then the downlink interval duration is K. period *N gap,coeff N gap,period The included downlink time can be greater than N. gap,coeff N gap,period This can meet the scheduling requirements.

[0263] In TDD mode, the downlink interval period is increased by a second scaling factor, for example, N. gap,period,TDD =K period *N gap,period K period This may be predefined by the protocol or configured on the network side. The duration of the downlink interval is still determined based on the unscaled interval period, i.e., N. gap,duration,TDD =N gap,coeff N gap,period However, only downlink time or NB-IoT downlink subframes can be included in the duration of the downlink interval. In this case, it can be ensured that the downlink time within the downlink interval meets scheduling requirements.

[0264] In TDD mode, only downlink time or NB-IoT downlink subframes can be included in the calculation of interval period and interval duration. In this case, it can be ensured that the downlink time in the downlink interval meets the scheduling requirements.

[0265] Introducing a (larger) configurable downlink interval factor N gap,coeff If the downlink interval period remains unchanged, a longer downlink interval duration can be introduced. In this case, it can be ensured that the downlink time within the downlink interval meets the scheduling requirements.

[0266] In TDD mode, the downlink interval duration coefficient N is increased by a third scaling factor. gap,coeff For example, N gap,coeff,TDD =K coeff *N gap,coeff Where K may be a protocol predefined value or a network-side configuration. Assuming the TDD cycle length is X and the downlink time is Y, if K... coeff If the distance is greater than or equal to X / Y, then the downlink interval duration N is... gap,coeff,TDD N gap,period =K coeff *Ngap,coeff N gap,period The included downlink time can be greater than N. gap,coeff N gap,period This ensures that the scheduling requirements are met. In this case, it can be guaranteed that the downlink time within the downlink interval meets the scheduling needs.

[0267] In TDD mode, the downlink interval duration N is increased by a fourth scaling factor. gap,duration For example, N gap,duration,TDD =K duration *N gap,duration =K duration *N gap,coeff N gap,period K duration This could be predefined by the protocol or configured on the network side. Assuming the TDD cycle length is X and the downlink time is Y, if K... duration If the downlink interval duration is greater than or equal to X / Y, then the downlink interval duration is K. duration *N gap,coeff N gap,period The included downlink time can be greater than N. gap,coeff N gap,period This ensures that the scheduling requirements are met. In this case, it can be guaranteed that the downlink time within the downlink interval meets the scheduling needs.

[0268] Introducing a (smaller) downlink interval threshold N gap,threshold Since the downlink time in the periodic mode only accounts for a small portion of the total mode time, completing R... max The time for each repeated transmission will increase by a factor of X / Y, where X is the periodic pattern length and Y is the downlink time length. To ensure that the frequency of receiving downlink scheduling remains unchanged, the downlink interval threshold needs to be reduced accordingly. For example, in TDD mode, configuring N... gap,threshold,new <= Y / X*N gap,threshold,old It can meet the frequency requirements of scheduling.

[0269] In TDD mode, the downlink interval threshold is reduced by a fifth scaling factor, for example, N. gap,threshold,TDD =K threshold *N gap,threshold K threshold This could be predefined by the protocol or configured on the network side. For example, K threshold <= Y / X, where X is the periodic pattern length and Y is the downlink time length.

[0270] In TDD mode, a configurable downlink interval period is introduced, which may be an integer multiple of the transmission mode period. Alternatively, in TDD mode, the original period is scaled to be an integer multiple of the transmission mode period, such as N. gap,period =K*N TDD , where Ngap,period For the downlink interval period, N TDD The period represents the transmission mode. K is a scaling factor, which may be equal to N. gap,period / N TDD , or N gap,period / N TDD Round up, or N gap,period / N TDD Round down to the nearest integer. This ensures that the downlink interval period matches the transmission mode period.

[0271] In TDD mode, an offset is introduced for the start time of the downlink interval. For example, in the current protocol, the start frame and subframe of the downlink interval satisfy... An additional offset N can be introduced for the start time of the downlink interval. offset That is, the start frame and subframe of the downlink interval satisfy... Where, N offset This could be predefined by the protocol, configured on the network side, or determined / derived by the UE / network side. This ensures that the downlink interval period matches the transmission mode period.

[0272] In TDD mode, a configurable (smaller) downlink interval length or a downlink interval length factor N is introduced. gap,coeff This allows the downlink interval length to be shorter than the downlink time within a single cycle. Thus, within the downlink time of a single cycle, both downlink intervals and normal transmission can coexist.

[0273] In TDD mode, if the start time of a downlink interval overlaps with a non-downlink time, the start delay of the downlink interval is delayed until the next (valid / available) downlink time / downlink subframe / downlink resource / NB-IoT downlink subframe.

[0274] In TDD mode, the portion of the downlink interval that overlaps with non-downlink time is delayed to the next (valid / available) downlink time / downlink subframe / downlink resource / downlink time unit / NB-IoT downlink subframe.

[0275] In TDD mode, the definition of the downlink interval is the same as the traditional definition, or the definition of the downlink interval is not modified.

[0276] In TDD mode, downlink intervals are not used.

[0277] The phrase "in TDD mode" mentioned above may refer to "IoT-NTN TDD mode" or "NB-IoT NTN TDD mode," etc. In terrestrial TDD mode, the definition of downlink intervals may be the same as the traditional definition.

[0278] The second, third, and fourth scaling factors mentioned above may be the same or refer to the same scaling factor.

[0279] In TDD mode, a TDD pattern may only have a limited downlink time. When performing coverage enhancements, such as retransmissions, the transmission of a downlink channel may not be completed within the downlink time of a single TDD pattern. For example, suppose a TDD pattern has only D subframes of downlink time (available for PDCCH transmission), and PDCCH transmission (or search space, or PDCCH candidate) requires R > D subframes; then the PDCCH cannot be transmitted within a single TDD pattern. In implementation, the PDCCH may only be mapped to valid downlink subframes, such as downlink subframes within downlink time or NB-IoT downlink subframes. In this case, if the PDCCH overlaps with non-downlink time, it will be delayed to the next valid subframe / downlink time subframe / NB-IoT downlink subframe. This delay behavior may cause different downlink transmissions to overlap. For example, the first search space / PDCCH candidate / PDCCH, after delay, may overlap with the second search space / PDCCH candidate / PDCCH. In traditional implementations (such as NB-IoT), the UE may prioritize detecting later / new search space / PDCCH candidates / PDCCHs (e.g., the second search space / PDCCH candidate / PDCCH), or the UE may not require detection of earlier / older search space / PDCCH candidates / PDCCHs (e.g., the first search space / PDCCH candidate / PDCCH), or discard earlier / older search space / PDCCH candidates / PDCCHs (e.g., the first search space / PDCCH candidate / PDCCH). However, in TDD mode, if the period of the search space / PDCCH candidate / PDCCH is less than or equal to the TDD period, continuous overlap may occur, resulting in multiple or all search space / PDCCH candidates / PDCCHs being discarded or not required to be detected.

[0280] To address the aforementioned issues, the downlink physical channel coverage enhancement method of this application further includes at least one of the following:

[0281] If the transmissions of two target downlink physical channels overlap, or if the interval between the transmissions of two target downlink physical channels is less than a preset minimum interval, perform at least one of the following:

[0282] Configure the search space, PDCCH candidates, or PDCCH period to be greater than the first period parameter, and the first period parameter to be greater than the length of the period pattern in TDD mode;

[0283] Configure the start subframe parameter of the search space to be greater than the preset threshold parameter;

[0284] Configure the maximum number of repeated transmissions in the search space to be less than the first threshold, or configure the number of repeated transmissions of the PDCCH candidate or PDCCH to be less than the second threshold;

[0285] The overlapping portion of the downlink physical channel transmissions of the two targets is not detected or discarded;

[0286] Before completing the detection of the downlink physical channel of the first target, the downlink physical channel of the second target is not detected or is discarded;

[0287] The downlink physical channel of the second target is detected, but the downlink physical channel of the first target is either detected or discarded.

[0288] Specifically, when configuring parameters, the network side can avoid overlap by configuring a (larger) search space period.

[0289] Limit network-side parameter configurations. For example, when the number of repetitions of the search space / PDCCH candidate / PDCCH or the aggregation level R is greater than (or greater than or equal to) a threshold R. threshold At that time, or the maximum number of repetitions or aggregation level R of the search space / PDCCH candidate / PDCCH. max Greater than (or greater than or equal to) the threshold R threshold At that time, the parameters that the UE expects to be configured to meet the following conditions, or the parameters configured on the network side need to meet the following conditions (threshold R). threshold This could be a parameter configured on the network side, a parameter predetermined by the protocol, or a parameter that can be derived by the UE / network side (e.g., equal to the downlink time in a TDD mode or the downlink time available for PDCCH transmission).

[0290] Search space / PDCCH candidates / PDCCH period T is greater than (or greater than or equal to) parameter T threshold T threshold It could be a parameter configured on the network side, a parameter predefined by the protocol, or a parameter that can be derived by the UE / network side. threshold Condition T may be satisfied threshold >=K*T TDD T TDD For the TDD cycle, K is a factor. K may be equal to 1, configured on the network side, predefined by the protocol, or equal to D. SS / D TDD,D , or equal to D SS / D TDD,D Round up. D SS For the search space / PDCCH candidate / PDCCH duration, D TDD,DThe downlink time length within a TDD cycle, or the downlink time length available for PDCCH transmission within a TDD cycle.

[0291] The start subframe parameter G of the search space is greater than (or greater than or equal to) the threshold G. threshold , or G*R max >=K*T TDD , or G*R max >=T threshold G threshold This could be a parameter configured on the network side, a parameter predefined by the protocol, or a parameter that can be derived from the UE / network side. threshold Condition G may be satisfied threshold R max >=K*T TDD R max T represents the maximum number of repetitions / duration / aggregation level. TDD For the TDD cycle, K is a factor. K may be equal to 1, configured on the network side, predefined by the protocol, or equal to D. SS / D TDD,D , or equal to D SS / D TDD,D Round up. D SS For the search space / PDCCH candidate / PDCCH duration, D TDD,D This represents the downlink time length within a TDD cycle, or the downlink time length available for PDCCH transmission within a TDD cycle. The start subframe parameter G represents the ratio of the period of the PDCCH candidate or the period of the search space to the maximum number of repetitions.

[0292] Limit network-side parameter configuration. For example, when the period T of the search space / PDCCH candidate / PDCCH is less than (or less than or equal to) the threshold T. threshold Time (threshold T) threshold This could be a parameter configured on the network side, a parameter predetermined by the protocol, or a parameter that can be derived by the UE / network side (e.g., equal to the period of TDD mode), or a parameter G in the search space / PDCCH candidate / PDCCH start subframe that is less than (or less than or equal to) a threshold G. threshold Time (threshold G) threshold This could be a parameter configured on the network side, a parameter predefined by the protocol, or a parameter that can be derived by the UE / network side, such as equal to the TDD mode period divided by the maximum number of repetitions R in the search space. max The UE expects the configured parameters to meet the following conditions, or the parameters configured on the network side need to meet the following conditions:

[0293] The maximum number of repetitions in the search space, R maxLess than (or less than or equal to) parameter R max,threshold R max,threshold It could be a parameter configured on the network side, a parameter predefined by the protocol, or a parameter that can be derived by the UE / network side. max,threshold Condition R may be satisfied max,threshold <=K*D TDD,D D TDD,D K is the downlink time length within a TDD cycle or the downlink time length available for PDCCH transmission within a TDD cycle, where K is a factor. K may be equal to 1, configured on the network side, or predefined by the protocol.

[0294] The number of repetitions R of PDCCH candidate / PDCCH is less than (or less than or equal to) the parameter R. threshold R threshold It could be a parameter configured on the network side, a parameter predefined by the protocol, or a parameter that can be derived by the UE / network side. threshold Condition R may be satisfied threshold <=K*D TDD,D D TDD,D K is the downlink time length within a TDD cycle or the downlink time length available for PDCCH transmission within a TDD cycle, where K is a factor. K may be equal to 1, configured on the network side, or predefined by the protocol.

[0295] Define new rules to handle overlaps between the search space / PDCCH candidates / PDCCH. For example:

[0296] The first search space / PDCCH candidate / PDCCH overlaps with the second search space / PDCCH candidate / PDCCH, wherein the start time of the second search space / PDCCH candidate / PDCCH is after the start time of the first search space / PDCCH candidate / PDCCH. The UE only (does not require / expect) detects the portion of the first search space / PDCCH candidate / PDCCH that overlaps with the second search space. Alternatively, only the portion of the first search space / PDCCH candidate / PDCCH that overlaps with the second search space is discarded.

[0297] The first search space / PDCCH candidate / PDCCH overlaps with the second search space / PDCCH candidate / PDCCH, wherein the start time of the second search space / PDCCH candidate / PDCCH is after the start time of the first search space / PDCCH candidate / PDCCH. The UE (neither requests nor expects) to detect the second search space / PDCCH candidate / PDCCH before or during the duration of the first search space / PDCCH candidate / PDCCH. Alternatively, the second search space / PDCCH candidate / PDCCH is discarded.

[0298] The first search space / PDCCH candidate / PDCCH overlaps with the second search space / PDCCH candidate / PDCCH. If the UE discards or does not detect the first search space / PDCCH candidate / PDCCH in order to detect the second search space / PDCCH candidate / PDCCH, then before completing the detection of the second search space / PDCCH candidate / PDCCH or during the duration of the second search space / PDCCH candidate / PDCCH, the UE (does not require / expect) to detect any other search space / PDCCH candidate / PDCCH.

[0299] Additionally, in some implementations, a certain guard interval may be required between different search spaces / PDCCH candidates / PDCCHs to provide sufficient processing time. For example, in NB-IoT, a minimum interval of 4ms is required between different search spaces. Therefore, the "overlap" mentioned in this application may include cases where the interval between two search spaces / PDCCH candidates / PDCCHs is less than the minimum interval. Alternatively, changing "overlap" / "overlapping occurs" to "interval less than the minimum interval" will still apply the aforementioned enhancements.

[0300] Furthermore, in high-speed mobile scenarios, such as NTN scenarios, the round-trip latency from the UE to the network can change rapidly. To maintain time synchronization, the UE needs to be able to adjust timing or frequency compensation or pre-compensation values ​​during a single transmission. However, in some implementations (e.g., NB-IoT or eMTC), the UE may not support real-time adjustment of pre-compensation values, in which case segmented pre-compensation may be performed. The segment length for segmented pre-compensation may be configured by the network side. The UE may adjust the time or frequency pre-compensation in each segment. Transmission intervals may exist between segments.

[0301] In TDD mode, the UE transmits uplink data in discontinuous uplink intervals. To address this, the following solutions can be considered:

[0302] In TDD mode, subframes that are not uplink time are also included in the segment length of the segment pre-compensation.

[0303] In TDD mode, if the start time of a segment is not an uplink time, the start time of the segment is delayed to the next (valid / available) uplink time / uplink subframe / uplink resource / NB-IoT uplink subframe.

[0304] The following solutions can be considered for the transmission interval between segments:

[0305] In TDD mode, when the non-uplink time overlaps with the transmission interval, the overlapping part is counted as part of the transmission interval.

[0306] In summary, this application proposes the following technical solutions, which can be summarized as follows:

[0307] For duplicate public PDCCH and public PDSCH transmissions, a joint indication is introduced. This means that a single indication can be used to indicate duplicate transmissions on multiple channels.

[0308] Associating the enable or repetition count for repeated transmissions on different channels;

[0309] A method for detecting intra-slot repetitive transmissions and inter-slot repetitive transmissions of a public PDCCH is proposed.

[0310] The UE's detection method for PDCCH when simultaneously supporting intra-slot repetitive transmission and inter-slot repetitive transmission;

[0311] In NB-IoT TDD, adaptive adjustment of downlink intervals.

[0312] This application also provides a controller, including at least one processor and a memory for communicatively connecting to the at least one processor; the memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to perform the coverage enhancement method of the foregoing embodiments.

[0313] Referring to Figure 10, an example is taken where the processor 1001 and memory 1002 in the controller 1000 can be connected via a bus. The memory 1002, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, the memory 1002 may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, the memory 1002 may optionally include memory remotely located relative to the processor 1001, and these remote memories can be connected to the controller 1000 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0314] Those skilled in the art will understand that the device structure shown in FIG10 does not constitute a limitation on the controller 1000, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0315] This application also provides a computer-readable storage medium storing computer-executable instructions that are executed by one or more processors, for example, by a processor 1001 in FIG10, which causes the one or more processors to perform the coverage enhancement method in the above method embodiments.

[0316] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0317] This application embodiment also provides a communication device, including the above-mentioned controller 1000. The controller 1000 is connected to OBA, OLA and OPA in a multi-band transmission system. The controller 1000 can also be connected to WSS in the multi-band transmission system.

[0318] It will be understood by those skilled in the art that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0319] The above provides a detailed description of some implementations of this application. However, this application is not limited to the above-described embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of this application. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. A method for enhancing coverage of a downlink physical channel, applied to a first node, the method comprising: Receive the first signaling; Determine the transmission configuration parameters for at least one target downlink physical channel, the transmission configuration parameters including the enable state of repeated transmission and / or the number of repeated transmissions.

2. The method according to claim 1, wherein, The target downlink physical channel includes at least one of the common physical downlink control channel (PDCCH), the common physical downlink shared channel (PDSCH), and the synchronization signal block (SSB). The public PDCCH includes at least one of the PDCCH Public Search Space (CSS) and / or at least one of the PDCCHs using cell-level PDCCH parameters; the public PDSCH includes at least one of the PDSCHs before the first node obtains the proprietary PDSCH configuration and / or at least one of the PDSCHs using cell-level PDSCH parameters.

3. The method according to claim 1, wherein, The first signaling includes at least one of the following: Master Information Block (MIB), System Information Block (SIB), Physical Broadcast Channel (PBCH), Radio Resource Control (RRC) signaling, Media Access Control Unit (MAC CE), MAC header, MAC subheader, and Downlink Control Information (DCI) signaling.

4. The method according to claim 1, wherein, The determination of transmission configuration parameters for at least one target downlink physical channel includes at least one of the following: The transmission configuration parameters of the first target downlink physical channel and the second target downlink physical channel are indicated by different indication information in the first signaling; The transmission configuration parameters of the first target downlink physical channel and the second target downlink physical channel are jointly indicated by the same indication information in the first signaling; The transmission configuration parameters of the second target downlink physical channel are determined by the transmission configuration parameters of the first target downlink physical channel.

5. The method according to claim 4, wherein, The first signaling includes first indication information and second indication information; the transmission configuration parameters of the first target downlink physical channel and the second target downlink physical channel are indicated by different indication information of the first signaling, including: The first indication information indicates the transmission configuration parameters of the first target downlink physical channel; The second indication information indicates the transmission configuration parameters of the second target downlink physical channel.

6. The method according to claim 4, wherein, The transmission configuration parameters of the first target downlink physical channel and the second target downlink physical channel are jointly indicated by the same indication information in the first signaling, including: The indication information in the first signaling indicates the enabled state of repeated transmission of the first target downlink physical channel and the second target downlink physical channel; Alternatively, the indication information in the first signaling indicates the number of times the first target downlink physical channel and the second target downlink physical channel are repeatedly transmitted.

7. The method according to claim 6, wherein, The indication information in the first signaling indicates the enabled state of repeated transmission of the first target downlink physical channel and the second target downlink physical channel, including at least one of the following: The indication information in the first signaling indicates the enabled state of repeated transmission of PDCCH CSS and SIB1PSDSCH, and the indication information in the first signaling is carried by the idle bits in the multiplexed MIB or the reserved bits in the PBCH. The indication information in the first signaling indicates the enabled state of repeated transmission of Type0-PDCCH CSS and SIB1PDSCH, and the indication information in the first signaling is carried by the idle bits in the multiplexed MIB or the reserved bits in the PBCH. The indication information in the first signaling indicates the enabled state of repeated transmission of Type 0-PDCCH CSS and SIB1PDSCH indicated in the MIB, and the indication information in the first signaling is carried by multiplexing the idle bits in the MIB or the reserved bits in the PBCH. The indication information in the first signaling indicates the enabled state of repeated transmission of SIB1 PDSCH and Msg4 PDSCH or MsgB PDSCH. The indication information in the first signaling is carried by the idle bits in the multiplexed MIB, the reserved bits in the PBCH, or the PDCCH of the scheduled SIB1. The indication information in the first signaling indicates the enabled state of repeated transmission of Type1-PDCCH CSS and Msg4PDSCH or MsgB PDSCH. The indication information in the first signaling is carried by idle bits in the multiplexed MIB, reserved bits in the PBCH, RRC signaling or information elements in SIB1. The indication information in the first signaling indicates the enabled state of repeated transmission of PDCCH CSS, SIB1PDSCH and Msg4 PDSCH or MsgB PDSCH, and the indication information in the first signaling is carried by the idle bits in the multiplexed MIB or the reserved bits in the PBCH. The indication information in the first signaling indicates the enabled state of repeated transmission of Type0-PDCCH CSS, SIB1PDSCH and Msg4 PDSCH or MsgB PDSCH, and the indication information in the first signaling is carried by the idle bits in the multiplexed MIB or the reserved bits in the PBCH. The indication information in the first signaling indicates the enabled state of repeated transmission of Type0-PDCCH CSS, SIB1PDSCH and Msg4 PDSCH or MsgB PDSCH indicated in the MIB. The indication information in the first signaling is carried by multiplexing the idle bits in the MIB or the reserved bits in the PBCH.

8. The method according to claim 4, wherein, The transmission configuration parameters of the second target downlink physical channel are determined by the transmission configuration parameters of the first target downlink physical channel, including at least one of the following: The indication information in the first signaling indicates the enable state of repeated transmission of the first target downlink physical channel, and the enable state of repeated transmission of the second target downlink physical channel is determined based on the enable state of repeated transmission of the first target downlink physical channel. The indication information in the first signaling indicates the number of times the first target downlink physical channel is repeatedly transmitted, and the number of times the second target downlink physical channel is repeatedly transmitted is determined based on the number of times the first target downlink physical channel is repeatedly transmitted; The indication information in the first signaling indicates the enabled state of repeated transmission of the first target downlink physical channel, and determines the number of repeated transmissions of the second target downlink physical channel based on the enabled state of repeated transmission of the first target downlink physical channel. The indication information in the first signaling indicates the number of times the first target downlink physical channel is repeatedly transmitted, and the enable state of the second target downlink physical channel is determined based on the number of times the first target downlink physical channel is repeatedly transmitted.

9. The method according to claim 8, wherein, Determining the enable state of the second target downlink physical channel repetition transmission based on the enable state of the first target downlink physical channel repetition transmission includes: The enable state of the second target downlink physical channel repeat transmission is determined based on the enable state of the first target downlink physical channel repeat transmission. The system receives a second signaling message and determines the number of times the second target downlink physical channel is repeatedly transmitted based on the indication information in the second signaling message. The indication information in the second signaling message is used to indicate the number of repetitions, or to indicate the number of times the second target downlink physical channel is repeatedly transmitted based on the number of times the first target downlink physical channel is repeatedly transmitted, or to indicate a scaling factor of the number of times the second target downlink physical channel is repeatedly transmitted relative to the number of times the first target downlink physical channel is repeatedly transmitted.

10. The method according to claim 8 or 9, wherein, Determining the enabling state of the second target downlink physical channel repetition based on the enabling state of the first target downlink physical channel repetition includes at least one of the following: If the first signaling indicates that PDCCH CSS enables repeated transmission, then SIB1PDSCH is determined to enable repeated transmission. If the first signaling indicates that Type0-PDCCH CSS enables repeated transmission, then SIB1PDSCH is determined to enable repeated transmission. If the Type0-PDCCH CSS indicated in the first signaling indication MIB enables repeated transmission, then SIB1PDSCH is determined to enable repeated transmission. If the first signaling indicates that SIB1PDSCH enables repeated transmission, then Msg4 PDSCH or MsgB PDSCH is determined to enable repeated transmission. If the first signaling indicates that Type1-PDCCH CSS enables repeated transmission, then Msg4PDSCH or MsgB PDSCH is determined to enable repeated transmission. If the first signaling indicates that PDCCH CSS enables repeated transmission, then SIB1PDSCH and Msg4 PDSCH or MsgB PDSCH are determined to enable repeated transmission. If the first signaling indicates that Type0-PDCCH CSS enables repeated transmission, then SIB1PDSCH and Msg4 PDSCH or MsgB PDSCH are determined to enable repeated transmission.

11. The method according to claim 8 or 9, wherein, Determining the number of retransmissions of the second target downlink physical channel based on the number of retransmissions of the first target downlink physical channel includes: The number of times the first target downlink physical channel is repeatedly transmitted is increased by a first value to obtain the number of times the second target downlink physical channel is repeatedly transmitted, where the first value is a non-zero integer; Alternatively, the number of times the first target downlink physical channel is repeatedly transmitted is multiplied by the second value to obtain the number of times the second target downlink physical channel is repeatedly transmitted, where the second value is not equal to 1; Alternatively, the number of times the first target downlink physical channel is repeatedly transmitted is increased by the first value and then multiplied by the second value to obtain the number of times the second target downlink physical channel is repeatedly transmitted. Alternatively, the number of times the first target downlink physical channel is repeatedly transmitted can be multiplied by the second value and then added to the first value to obtain the number of times the second target downlink physical channel is repeatedly transmitted.

12. The method according to claim 11, wherein, The first value and / or the second value are specified by the protocol or configured by the network side.

13. The method of claim 12, wherein, The method further includes: Receive a plurality of optional first values ​​and / or a plurality of second values ​​configured on the network side; The first value and / or the second value are determined based on the indication information in the DCI or MAC CE sent by the network side.

14. The method according to claim 8, wherein, Determining the number of retransmissions of the second target downlink physical channel based on the enable state of the first target downlink physical channel retransmission includes: If the first target downlink physical channel enables repeated transmission, the number of repeated transmissions of the second target downlink physical channel is determined to be the number of the first transmission. And / or, if the first target downlink physical channel does not enable repeated transmission, the number of repeated transmissions of the second target downlink physical channel is determined to be the second number.

15. The method according to claim 14, wherein, Determining the number of retransmissions of the second target downlink physical channel based on the enable state of the first target downlink physical channel retransmission includes at least one of the following: If PDCCH CSS is enabled for repeated transmission, the number of times SIB1PDSCH is repeatedly transmitted is determined to be the first number; if PDCCH CSS is not enabled for repeated transmission, the number of times SIB1 PDSCH is repeatedly transmitted is determined to be the second number. If SIB1PDSCH is enabled for repeated transmission, the number of times Msg4 PDSCH or MsgB PDSCH is repeated is determined to be the first number; if SIB1 PDSCH is not enabled for repeated transmission, the number of times Msg4 PDSCH or MsgB PDSCH is determined to be the second number.

16. The method according to claim 8, wherein, The step of determining the enable state of the second target downlink physical channel retransmission based on the number of retransmissions of the first target downlink physical channel includes: If the first target downlink physical channel is retransmitted for the third time, then the second target downlink physical channel is enabled for retransmission. And / or, if the number of retransmissions of the first target downlink physical channel is the fourth time, it is determined that the second target downlink physical channel is not enabled for retransmission.

17. The method according to claim 16, wherein, Determining the enable state of the second target downlink physical channel retransmission based on the number of retransmissions of the first target downlink physical channel includes at least one of the following: If the number of times PDCCH CSS is repeatedly transmitted is the third time, it is determined that SIB1PDSCH is enabled for repeated transmission; if the number of times PDCCH CSS is repeatedly transmitted is the fourth time, it is determined that SIB1 PDSCH is not enabled for repeated transmission. If the number of times SIB1PDSCH is repeatedly transmitted is the third time, then Msg4 PDSCH or MsgB PDSCH is determined to enable repeated transmission; if the number of times SIB1 PDSCH is repeatedly transmitted is the fourth time, then Msg4 PDSCH or MsgB PDSCH is determined to disable repeated transmission.

18. The method according to claim 1, wherein, The method further includes: The target downlink physical channel is detected.

19. The method according to claim 18, wherein, The detection of the target downlink physical channel includes at least one of the following: The first type of PDCCH is detected using the first blind detection method, and the second type of PDCCH is detected using the second blind detection method. The first blind detection method is used to detect the PDCCH corresponding to the first type of RNTI, and the second blind detection method is used to detect the PDCCH corresponding to the second type of RNTI. The PDCCH is detected using the first blind detection method in the first state of the first node, and the PDCCH is detected using the second blind detection method in the second state of the first node. The PDCCH is detected using the first blind detection method in the first search space, and the PDCCH is detected using the second blind detection method in the second search space. The target downlink physical channel is detected using the first blind detection method and the second blind detection method.

20. The method according to claim 19, wherein, The first blind detection method includes: Detect the PDCCH candidates obtained by merging and associating PDCCH candidates; Alternatively, the first PDCCH candidate can be detected, and then the PDCCH candidate obtained by merging and associating the PDCCH candidates can be detected. Alternatively, the first PDCCH candidate is detected, and then N-1 target PDCCH candidates are detected respectively, where the i-th target PDCCH candidate is obtained by merging the first PDCCH candidate to the i-th PDCCH candidate, N is the number of associated search spaces, and i is greater than 1 and i is an integer not greater than N; Alternatively, N target PDCCH candidates can be detected. The N target PDCCH candidates are obtained by taking the associated PDCCH candidates in the associated search space as N PDCCH candidates, where N is the number of associated search spaces.

21. The method according to claim 19, wherein, The second blind detection method includes: Detect the PDCCH candidates obtained from merging PDCCH candidates in multiple time slots with repeated transmissions; Alternatively, the first PDCCH candidate can be detected, and then the PDCCH candidates obtained by merging the PDCCH candidates from multiple time slots that are repeatedly transmitted can be detected. Alternatively, the first PDCCH candidate is detected, and then the M-1 target PDCCH candidates are detected respectively, wherein the j-th target PDCCH candidate is obtained by merging the first PDCCH candidate to the j-th PDCCH candidate, and M is the number of times the PDCCH is repeatedly transmitted; Alternatively, M target PDCCH candidates can be detected. The M target PDCCH candidates are obtained by taking the PDCCH candidates in multiple time slots that are repeatedly transmitted as M PDCCH candidates, where M is the number of times the PDCCH is repeatedly transmitted.

22. The method according to claim 19, wherein, The first type of PDCCH includes Type0-PDCCH CSS, and the second type of PDCCH includes at least one of the following: Type0A-PDCCH CSS, Type1-PDCCH CSS, Type1A-PDCCH CSS, Type2-PDCCH CSS, and Type2A-PDCCH CSS; Alternatively, the first type of PDCCH includes Type0-PDCCH CSS and Type0A-PDCCH CSS, and the second type of PDCCH includes at least one of the following: Type1-PDCCH CSS, Type1A-PDCCH CSS, Type2-PDCCH CSS, and Type2A-PDCCH CSS; The first type of RNTI includes SI-RNTI, and the second type of RNTI includes at least one of the following: RA-RNTI, TC-RNTI, MsgB-RNTI, P-RNTI, C-RNTI, CS-RNTI, and PEI-RNTI; The first state includes the state before the first node acquires SIB1, and the second state includes the state after the first node acquires SIB1; The first search space is SS0, and the second search space is the search space other than SS0.

23. The method according to claim 19, wherein, Both the first blind detection method and the second blind detection method include at least one detection behavior; The detection of PDCCH using the first blind detection method and the second blind detection method includes: The target detection method is obtained by taking the union of the detection behaviors of the first blind detection method and the second blind detection method. The PDCCH is detected using the target blind detection method described above.

24. The method according to claim 1, wherein, The method further includes: In TDD mode, if the target downlink physical channel is configured to have a downlink interval, the downlink interval of the target downlink physical channel is adjusted.

25. The method according to claim 24, wherein, The adjustment of the downlink interval of the target downlink physical channel includes at least one of the following: The interval period of the downlink interval is increased by a third value; The time coefficient of the downlink interval is increased by a fourth value; The duration of the downlink interval is increased by a fifth value; Only downlink time or NB-IoT downlink subframes are included in the duration of the downlink interval; The threshold corresponding to the downlink interval is lowered by the sixth value; If the start time of the downlink interval overlaps with a non-downlink time, the start time of the downlink interval will be delayed to the next downlink time, downlink subframe, downlink resource, or NB-IoT downlink subframe. If the downlink interval has a portion that overlaps with a non-downlink time, the overlapping portion will be delayed to the next downlink time, downlink subframe, downlink resource, or NB-IoT downlink subframe. Cancel the downlink interval in TDD mode.

26. The method of claim 25, wherein, The third, fourth, and fifth values ​​are all greater than the ratio of the length of the periodic pattern to the length of the downlink time within the periodic pattern under TDD mode. The sixth value is less than the ratio of the length of the downlink time within the cycle pattern to the length of the cycle pattern in TDD mode.

27. The method according to claim 24, wherein, The method further includes at least one of the following: If the transmissions of the two target downlink physical channels overlap, or if the interval between the transmissions of the two target downlink physical channels is less than a preset minimum interval, at least one of the following shall be performed: Configure the search space, PDCCH candidates, or PDCCH period to be greater than the first period parameter, where the first period parameter is greater than the length of the period pattern in the TDD mode. Configure the start subframe parameter of the search space to be greater than the preset threshold parameter; Configure the maximum number of repeated transmissions in the search space to be less than the first threshold, or configure the number of repeated transmissions of the PDCCH candidate or PDCCH to be less than the second threshold; The overlapping portion of the transmissions of the two target downlink physical channels is not detected or discarded; Before completing the detection of the downlink physical channel of the first target, the downlink physical channel of the second target is not detected or is discarded; The downlink physical channel of the second target is detected, but the downlink physical channel of the first target is either detected or discarded.

28. A controller comprising at least one processor and a memory for communicatively connecting to the at least one processor; the memory storing instructions executable by the at least one processor to enable the at least one processor to perform the coverage enhancement method as described in any one of claims 1 to 27.

29. A communication device comprising the controller as described in claim 28.

Images