Method and apparatus for processing pdcch repetition transmission, and user equipment and network-side device

Abstract

The present application belongs to the technical field of communications. Disclosed are a method and apparatus for processing PDCCH repetition transmission, and a user equipment and a network-side device. The method for processing PDCCH repetition transmission in the embodiments of the present application comprises: a user equipment acquiring configuration information of common PDCCH repetition transmission; and the user equipment receiving the common PDCCH repetition transmission according to the configuration information, wherein a common PDCCH comprises at least one of the following: a PDCCH for SIB1, a PDCCH for OSI, a PDCCH for a message 2, a PDCCH for a message 4, a PDCCH for a message B, a paging PDCCH, and a PDCCH for scheduling the re-transmission of a message 3.

Description

Method, device, terminal and network-side equipment for processing PDCCH repeated transmission

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese Patent Application No. 202310882204.1 filed on July 18, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a method, apparatus, terminal, and network-side equipment for processing repeated transmission of a physical downlink control channel (PDCCH). Background Art

[0004] In terrestrial network scenarios, since the base station transmission power is much greater than the terminal transmission power, the link quality of the downlink channel is usually higher than the link quality of the uplink channel. However, in some application scenarios, for example, in non-terrestrial communication networks, such as satellite communications, the downlink transmission power depends on the number of beams supported simultaneously by the satellite. As the number of beams increases, the transmission power corresponding to each beam will decrease. For example, in high-frequency conditions, the base station transmission power will be close to the mobile phone transmission power. At this time, the quality of the downlink channel is not necessarily higher than that of the uplink channel. In addition, the terminal (User Equipment, UE) uses the common physical downlink control channel (Common Physical downlink control channel, Common PDCCH) to send scheduling information for some public messages before the Radio Resource Control (RRC) connection is established. If the reception performance of the Common PDCCH is affected by the downlink channel quality, the public messages scheduled by the Common PDCCH will not be received, and the network coverage performance will be affected.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a method, apparatus, terminal, and network-side equipment for processing repeated PDCCH transmissions, which can solve the problem of poor network coverage caused by poor downlink channel quality.

[0007] In a first aspect, a method for processing repeated transmission of a physical downlink control channel (PDCCH) is provided, including:

[0008] The terminal obtains the configuration information of the common PDCCH repeated transmission;

[0009] The terminal receives repeated transmission of a common PDCCH according to the configuration information;

[0010] The public PDCCH includes at least one of the following:

[0011] System Information Block (SIB) 1 PDCCH, Other System Information (OSI) PDCCH, Message 2 PDCCH, Message 4 PDCCH, Message B PDCCH, Paging PDCCH, and PDCCH for scheduling message 3 retransmission.

[0012] In a second aspect, a method for processing repeated transmission of a physical downlink control channel (PDCCH) is provided, comprising:

[0013] The network side device sends the configuration information of common PDCCH repeated transmission to the terminal;

[0014] The network side device performs common PDCCH repeated transmission according to the configuration information;

[0015] The public PDCCH includes at least one of the following:

[0016] System information block SIB1 PDCCH, OSI PDCCH, message 2 PDCCH, message 4 PDCCH, message BPDCCH, paging PDCCH, and PDCCH scheduling message 3 retransmission.

[0017] In a third aspect, a device for processing repeated transmission of a physical downlink control channel (PDCCH) is provided, comprising:

[0018] An acquisition module, configured to acquire configuration information of repeated transmission of a common PDCCH;

[0019] A receiving module, configured to receive repeated transmissions of a common PDCCH according to the configuration information;

[0020] The public PDCCH includes at least one of the following:

[0021] System information block SIB1 PDCCH, OSI PDCCH, message 2 PDCCH, message 4 PDCCH, message BPDCCH, paging PDCCH, and PDCCH scheduling message 3 retransmission.

[0022] In a fourth aspect, a device for processing repeated transmission of a physical downlink control channel (PDCCH) is provided, comprising:

[0023] A sending module, configured to send configuration information of common PDCCH repeated transmission to the terminal;

[0024] An execution module, configured to execute common PDCCH repeated transmission according to the configuration information;

[0025] The public PDCCH includes at least one of the following:

[0026] System information block SIB1 PDCCH, OSI PDCCH, message 2 PDCCH, message 4 PDCCH, message BPDCCH, paging PDCCH, and PDCCH scheduling message 3 retransmission.

[0027] In a fifth aspect, a terminal is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the processing method for repeated transmission of PDCCH on the terminal side as provided in an embodiment of the present application are implemented.

[0028] In the sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to obtain configuration information of repeated transmission of a common PDCCH; and receive repeated transmission of a common PDCCH according to the configuration information; wherein the common PDCCH includes at least one of the following: system information block SIB1 PDCCH, OSIPDCCH, message 2 PDCCH, message 4 PDCCH, message B PDCCH, paging PDCCH, and PDCCH for scheduling retransmission of message 3.

[0029] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the processing method for repeated transmission of PDCCH on the network side as provided in the embodiment of the present application are implemented.

[0030] In the eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used to send configuration information of repeated transmission of a common PDCCH to a terminal; an execution module is used to perform repeated transmission of the common PDCCH according to the configuration information; wherein the common PDCCH includes at least one of the following: system information block SIB1PDCCH, OSIPDCCH, message 2PDCCH, message 4PDCCH, message B PDCCH, paging PDCCH, and PDCCH for scheduling retransmission of message 3.

[0031] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method for processing repeated transmission of PDCCH on the terminal side as provided in the embodiment of the present application are implemented, or the steps of the method for processing repeated transmission of PDCCH on the network side as provided in the embodiment of the present application are implemented.

[0032] In the tenth aspect, a wireless communication system is provided, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the processing method for repeated transmission of PDCCH on the terminal side as provided in the embodiment of the present application, and the network side device can be used to execute the steps of the processing method for repeated transmission of PDCCH on the network side as provided in the embodiment of the present application.

[0033] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run a program or instruction to implement a processing method for repeated transmission of PDCCH on the terminal side as provided in an embodiment of the present application, or to implement a processing method for repeated transmission of PDCCH on the network side as provided in an embodiment of the present application.

[0034] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the method for processing repeated transmission of PDCCH on the terminal side as provided in the embodiment of the present application, or the program / program product is executed by at least one processor to implement the steps of the method for processing repeated transmission of PDCCH on the network side as provided in the embodiment of the present application.

[0035] In an embodiment of the present application, a terminal obtains configuration information for repeated transmission of a common PDCCH; the terminal receives repeated transmissions of the common PDCCH based on the configuration information; wherein the common PDCCH includes at least one of the following: SIB1 PDCCH, OSI PDCCH, Message 2 PDCCH, Message 4 PDCCH, Message B PDCCH, Paging PDCCH, and PDCCH scheduling Message 3 retransmission. This enables the terminal to receive repeated transmissions of the common PDCCH, thereby improving network coverage. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0037] FIG2 is a flowchart of a method for processing repeated PDCCH transmissions provided in an embodiment of the present application;

[0038] FIG3 is a flowchart of another method for processing repeated PDCCH transmissions provided in an embodiment of the present application;

[0039] FIG4 is a structural diagram of a device for processing repeated PDCCH transmissions provided in an embodiment of the present application;

[0040] FIG5 is a structural diagram of another apparatus for processing repeated PDCCH transmissions provided in an embodiment of the present application;

[0041] FIG6 is a structural diagram of a communication device provided in an embodiment of the present application;

[0042] FIG7 is a structural diagram of a terminal provided in an embodiment of the present application;

[0043] FIG8 is a structural diagram of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0044] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0045] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0046] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0047] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0048] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home device (a home appliance with wireless communication capabilities, such as a refrigerator, a television, a washing machine, or furniture), a game console, a personal computer (PC), a teller machine, or a self-service machine, or other terminal-side device. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0049] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0050] In some embodiments, the random access procedure may be a contention-based random access procedure or a non-contention-based random access procedure. The random access procedure may be a four-step random access procedure (also called a Type-1 random access procedure) or a two-step random access procedure (also called a Type-2 random access procedure).

[0051] In the contention-based four-step random access channel (RACH) process, the terminal first sends Message 1 (Msg1) to the network, containing a preamble. After the network detects the preamble, it sends Message 2 (Msg2) / Random Access Response (RAR), which contains the preamble number detected by the network and the uplink radio resources allocated to the terminal for sending Message 3 (Msg3). After receiving Msg2, the terminal confirms that at least one of the preamble numbers carried in Msg2 matches the number of the preamble it sent. Then, based on the resources indicated by the RAR, it sends Msg3 containing contention resolution information. After receiving Msg3, the network sends Message 4 (Msg4) containing contention resolution information. Upon receiving Msg4, the terminal confirms that the resolution information matches the contention resolution information it sent in Msg3, completing the four-step random access process.

[0052] The network includes uplink grant (UL grant) information in the RAR to indicate the scheduling information of the Msg3 physical uplink shared channel (PUSCH), and includes information such as the random access preamble ID (RACH preamble ID, RAPID), temporary cell-radio network temporary identifier (TC-RNTI), and timing advance (TA). If the network does not receive the Msg3 PUSCH, it can schedule the retransmission of the Msg3 PUSCH in the physical downlink control channel (PDCCH) scrambled by the TC-RNTI.

[0053] For the contention-based random access process, different terminals randomly select preambles for transmission. In this way, different terminals may select the same preamble to send on the same time-frequency radio resources (such as random access opportunity (RACH Occasion, RO) resources). This situation can be understood as a terminal preamble conflict. In this case, different terminals will receive the same RAR. At this time, different terminals will transmit Msg3PUSCH according to the scheduling information in the RAR UL grant. In some related technologies, since repeated transmission of Msg3 PUSCH is not supported, the network can only decode the PUSCH (including contention resolution information) sent by one terminal on one Msg3 PUSCH scheduling resource. Therefore, the network will include the contention resolution information received in Msg3 in Msg4. If the contention resolution information in Msg4 received by the terminal matches the contention resolution information sent by the terminal in Msg3 PUSCH, the terminal considers that the contention resolution is successful. If they do not match, the contention resolution is considered unsuccessful.

[0054] If the contention resolution is unsuccessful, the terminal reselects RACH transmission resources, performs physical random access channel (PRACH) transmission, and makes the next random access attempt.

[0055] In some embodiments, the first step in the two-step random access process (2-step RACH) is that the terminal sends message A (MsgA) to the network side. After receiving MsgA, the network side sends message B (MsgB) to the terminal. If the terminal does not receive MsgB within a certain period of time, the terminal will increment the counter that counts the number of times MsgA is sent and resend MsgA. If the counter that counts the number of times MsgA is sent reaches a certain threshold, the terminal will switch from the two-step random access process to the four-step random access process. MsgA includes the MsgA preamble part and the MsgAPUSCH part. The preamble part is sent on the RO used for the two-step random access process, and the PUSCH part is sent on the MsgAPUSCH resources associated with the sending of the MsgA preamble and the RO. MsgAPUSCH resources are a set of PUSCH resources configured relative to each PRACH slot, including time-frequency resources and DMRS resources.

[0056] In some embodiments, a CORESET is a collection of time and frequency domain resources for control information. CORESET#0 is a special CORESET that is typically used to schedule the transmission of the PDCCH of System Information Block (SIB) 1. The configuration information of CORESET#0 and the configuration information of the monitoring opportunity of the Type0-PDCCH Common Search Space (CSS) are carried by the associated Cell Defining Synchronization Signal Block (CD-SSB). The main function of CORESET#0 is to define the time and frequency resources of the Type0-PDCCH CSS and the size of the monitoring opportunity of the Type0-PDCCH CSS.

[0057] In some embodiments, CORESET#0 and Synchronization Signal Block (SSB) have the following multiplexing mode:

[0058] Multiplexing Mode 1: This is a multiplexing mode in which SSB and CORESET#0 appear at different times (no overlap in the time domain), and the SSB transmission bandwidth overlaps with the initially activated downlink bandwidth part (Bandwidth Part, BWP) of CORESET#0 (overlap in the frequency domain). This mode can be used for carrier frequencies less than 6 GHz and greater than 6 GHz (and less than 52.6 GHz).

[0059] Multiplexing Mode 2: Multiplexing mode in which SSB and CORESET#0 appear at different times (no overlap in time domain), and the transmission bandwidth of SSB does not overlap with the initial activation downlink BWP of CORESET#0 (no overlap in frequency domain); SSB is located at the top or bottom of CORESET#0. This is only used when the carrier frequency is greater than 6 GHz. SSB is located at the top of CORESET#0, with an interval of 12+k SSB subcarriers. SSB is located at the bottom of CORESET#0. If k SSB Equal to 0, interval 12 subcarriers; if k SSB Not equal to 0, interval 24-k SSB subcarriers.

[0060] Multiplexing mode 3: The multiplexing mode in which SSB and CORESET#0 appear at the same time (overlap in the time domain), and the transmission bandwidth of SSB does not overlap with the initial activation downlink BWP of CORESET#0 (no overlap in the frequency domain); SSB is located at the top or bottom of CORESET#0. It is only used when the carrier frequency is greater than 6 GHz. SSB is located at the top of CORESET#0, with an interval of k SSB subcarriers. SSB is located at the bottom of CORESET#0. If k SSB Equal to 0, interval 0 subcarrier; if k SSB Not equal to 0, interval 12-k SSB subcarriers.

[0061] In some embodiments, there are two types of search space (SS) sets: a common search space (CSS) set monitored by a group of terminals in a cell, and a user-specific search space (USS) set monitored by a single terminal. The SS set further configures the PDCCH candidates that the terminal needs to monitor. Search spaces can be of the following types:

[0062] 1. Type 0 - PDCCH common search space set (CSS set): This search space set is used to monitor SIB1 system messages;

[0063] 2. Type 0A-PDCCH CSS set: This search space set is used to monitor system messages other than SIB1;

[0064] 3. Type 1 - PDCCH CSS set: This search space set is used to monitor: the downlink PDCCH corresponding to Msg2 / Msg4 in the traditional four-step random access process; and the downlink PDCCH corresponding to MsgB in the two-step random access process;

[0065] 4. Type 2 - PDCCH CSS set: This search space set is used to monitor paging messages;

[0066] 5. Type 3 - PDCCH CSS set: This search space set is used to monitor uplink power control PDCCH, downlink pre-emption PDCCH, slot format indication PDCCH, and PDCCH related to downlink data transmission;

[0067] 6. USS: This search space set is used to monitor PDCCH related to downlink data transmission.

[0068] In some embodiments, during the random access process, the reception of the scheduling information of the Msg2 / MsgB / Msg4 physical downlink shared channel (PDSCH) needs to be within a certain window, and the size of the window is configured by the network.

[0069] For Msg2, the window starts at the first symbol of the Control Resource Set (CORESET) in the Type 1 PDCCH Common Search Space (Type 1-PDCCH CSS) set after the PRACH is transmitted. For MsgB, the window starts at the first symbol of the CORESET in the Type 1-PDCCH CSS set after the PUSCH (MsgAPUSCH) portion of the Msg is transmitted.

[0070] For Msg4, the window is actually controlled by the random access contention resolution timer (ra-ContentionResolutionTimer), which starts or restarts after sending Msg3 (if Msg3 repeated transmission is supported, it is after sending the last transmission of Msg3).

[0071] In the following, in combination with the accompanying drawings, a method, apparatus, terminal and network-side equipment for processing repeated transmission of a PDCCH provided in an embodiment of the present application are described in detail through some embodiments and application scenarios.

[0072] Please refer to FIG. 2 , which is a flowchart of a method for processing repeated PDCCH transmission provided by an embodiment of the present application. As shown in FIG. 2 , the method includes the following steps:

[0073] Step 201: Acquire configuration information for repeated transmission of a common PDCCH;

[0074] Step 202: The terminal receives repeated transmissions of the common PDCCH according to the configuration information.

[0075] The public PDCCH includes at least one of the following:

[0076] System Information Block (SIB) 1 physical downlink control channel (PDCCH), other system information (OSI) PDCCH, message 2 (Msg2) PDCCH, message 4 (Msg4) PDCCH, message B (MsgB) PDCCH, paging PDCCH, and PDCCH for scheduling retransmission of message 3 (Msg3).

[0077] Among them, SIB1 PDCCH refers to the PDCCH scheduling SIB1, OSIPDCCH refers to the PDCCH scheduling OSI, Msg2 PDCCH refers to the PDCCH scheduling Msg2, Msg4 PDCCH refers to the PDCCH scheduling Msg4, MsgB PDCCH refers to the PDCCH scheduling MsgB, and paging PDCCH refers to the PDCCH scheduling paging or the PDCCH used for paging.

[0078] The common PDCCH may refer to one or more PDCCHs transmitted on a common PDCCH resource. The common PDCCH resource may refer to a CORESET resource supporting CSS, which may be CORESET#0 or another CORESET. The CSS may include at least one of the following:

[0079] Type0 CSS collection, Type0A CSS collection, Type1 CSS collection, Type2 CSS collection.

[0080] For example, the common PDCCH may be a PDCCH transmitted on CORESET#0, or may be a PDCCH transmitted on CORESET resources associated with a Type0 / 0A / 1 / 2 PDCCH CSS set.

[0081] In addition, the common PDCCH transmitted on the CORESET resources associated with the CSS is also called a broadcast PDCCH.

[0082] In addition, the above-mentioned common PDCCH may be a common PDCCH in a non-terrestrial network (NTN) scenario, or may be a common PDCCH in a terrestrial network (TN) scenario.

[0083] In some implementations, the common PDCCH may also be a PDCCH channel before the terminal enters the RRC connected state.

[0084] In the embodiment of the present application, the common PDCCH repeated transmission may also be referred to as common PDCCH repetition (common PDCCH repetition), or each transmission in the common PDCCH repeated transmission is referred to as a PDCCH repetition (PDCCH repetition).

[0085] The configuration information of the common PDCCH repetition transmission may be information such as the function, number, and pattern of the common PDCCH repetition transmission, or the configuration information of the common PDCCH repetition transmission may be timeline information of the common PDCCH repetition transmission.

[0086] In the embodiment of the present application, the above steps enable the terminal to receive repeated transmissions of the common PDCCH, thereby improving network coverage. Furthermore, since the common PDCCH includes the SIB1 PDCCH, OSIP PDCCH, Message 2 PDCCH, Message 4 PDCCH, Message B PDCCH, Paging PDCCH, and PDCCH scheduling Message 3 retransmissions, this also enables the terminal to better receive messages during the random access process, thereby improving terminal random access performance.

[0087] As an optional implementation manner, the configuration information includes at least one of the following parameters:

[0088] The function of repeated transmission of the common PDCCH;

[0089] The number of repetitions of the common PDCCH retransmission;

[0090] The index of the common PDCCH repeated transmission;

[0091] Resource information of repeated transmission of the common PDCCH;

[0092] Activation information of the common PDCCH repeated transmission, where the activation information indicates activation or deactivation of the common PDCCH repeated transmission;

[0093] The repetition mode of the common PDCCH repeated transmission.

[0094] Among them, the function of the above-mentioned public PDCCH repeated transmission can indicate whether the network side supports public PDCCH repeated transmission, or whether the network side device supports the terminal requesting public PDCCH repeated transmission; the function of the above-mentioned public PDCCH repeated transmission can indicate whether the terminal supports public PDCCH repeated transmission, or whether the terminal supports requesting public PDCCH repeated transmission to the network side device.

[0095] The index of the above-mentioned common PDCCH repetition transmission may indicate the number of the common PDCCH repetition transmission, such as the nth transmission, where n is greater than or equal to 1 and less than or equal to the number of repetitions of the common PDCCH repetition transmission.

[0096] The resource information for repeated transmission of the common PDCCH may include at least one of the following:

[0097] A pattern of repeated transmission of the common PDCCH, wherein the pattern is used to indicate a resource position occupied by repeated transmission of the common PDCCH;

[0098] Instruction information for instructing the common PDCCH to be repeatedly transmitted based on available time slots;

[0099] Indication information used to instruct the common PDCCH to be repeatedly transmitted based on a physical slot.

[0100] The pattern of the above-mentioned common PDCCH repetition transmission may represent a control channel element (CCE) position or a PDCCH candidate (PDCCH candidate) position. For example, for the case where PDCCH repetition transmission between CORESETs is supported, the above-mentioned bitmap may represent that the occupied CCE positions or PDCCH candidate positions of different PDCCH repetitions (i.e., different transmissions) in different CORESETs are the same or in a varying pattern, or, for the case where PDCCH repetition transmission within a CORESET is supported, the above-mentioned bitmap may represent that the occupied CCE positions or PDCCH candidate positions of different PDCCH repetitions (i.e., different transmissions) in the same CORESET are the same or in a varying pattern.

[0101] The indication information for instructing the common PDCCH to be repeatedly transmitted based on the available time slots may indicate whether the common PDCCH is repeatedly transmitted based on the available time slots.

[0102] The indication information for instructing the common PDCCH to be repeatedly transmitted based on the physical time slot may indicate whether the common PDCCH is repeatedly transmitted based on the physical time slot.

[0103] The repetition mode of the common PDCCH retransmission may include at least one of the following:

[0104] Based on intra-slot repetition;

[0105] Based on inter-slot repetition.

[0106] The repeated transmission within the above-mentioned time slot can be that all transmissions of the common PDCCH repeated transmission are completed within one time slot. For example: combined with the method of adding a new column in Table 1 described below, the first symbol index (First symbol index) is used to indicate the starting symbol, and the number of symbols (Number of Symbols) indicates the number of symbols occupied by each transmission. And a transmission cannot be transmitted across slots. For example, First symbol index = 0, Number of Symbols = 3, then PDCCH repetition index 0 is on symbol 0 / 1 / 2; PDCCH repetition index 1 is on symbol 3 / 4 / 5; PDCCH repetition index 2 is on symbol 6 / 7 / 8; PDCCH repetition index 3 is on symbol 9 / 10 / 11; since the remaining two symbols are less than the Number of Symbols number 3, there is no PDCCH repetition index 4.

[0107] The repeated transmissions between time slots can be performed in such a way that each transmission of the common PDCCH repeated transmission is completed within one time slot. For example, in combination with the newly added columns in Table 1 described below, each time slot uses the same first symbol index and number of symbols. The number of repetitions determines the number of consecutive slots used for repeated transmissions.

[0108] In the above implementation manner, the above configuration information can enable the terminal to better receive repeated transmissions of the common PDCCH of the network side device, thereby further improving the reliability of PDCCH reception.

[0109] As an optional implementation manner, the terminal obtains configuration information of repeated transmission of the common PDCCH, including:

[0110] The terminal determines, based on the indication information, configuration information for repeated transmission of the common PDCCH, where the indication information includes at least one of the following:

[0111] SSB, Master Indication Block (MIB), Physical broadcast channel (PBCH), SIB, Radio Network Temporary Identifier (RNTI), CORESET configuration table, CSS listening opportunity table, downlink channel reception window, downlink channel transmission period, CORESET resources, search space, PDCCH MO, Physical Random Access Channel (PRACH) resources, SIB1 PDCCH, Msg2, MsgB, Msg2 PDCCH, MsgB PDCCH, PDCCH scheduling Msg3 retransmission, Radio Resource Control RRC signaling, Medium Access Control Control Element (MAC CE), random access response, downlink control information (DCI), Msg3.

[0112] The above-mentioned indication information is indication information received by the terminal from the network side device.

[0113] In the above implementation, the above configuration information can be indicated by at least one of the above items, which does not require the introduction of additional messages, thereby saving transmission overhead.

[0114] In some implementations, the above-mentioned configuration information is configuration information explicitly or implicitly indicated by the indication information.

[0115] For example, the above configuration information is implicitly or explicitly indicated through SSB, or implicitly or explicitly indicated through MIB.

[0116] In some implementations, the configuration information is implicitly indicated by some bits in existing fields in the MIB, for example, by using a specific k SSB The value of (subcarrier offset value between subcarrier 0 of SSB and subcarrier 0 in common resource block) is used to implicitly indicate the above configuration information, such as defining k SSB The values ​​or groups of correspond to different numbers of repetitions, such as k SSB When the value is 0 to 1, it means that the common PDCCH repeated transmission is not supported, such as k SSB When the value of is 2 to 3, it indicates that the common PDCCH repeated transmission is supported, and the number of repetitions of the common PDCCH repeated transmission is 2. SSBWhen the value of is 4 to 5, it indicates that common PDCCH repeated transmission is supported, and the number of repetitions of common PDCCH repeated transmission is 4, etc. Alternatively, the above configuration information is explicitly carried in the MIB information; explicitly carried in the MIB information, for example, by using spare bits in the MIB.

[0117] The above configuration information is either implicitly or explicitly indicated through PBCH, or indicated through SIB, where the SIB includes SIB1 or other system information (OSI), for example, one or more bits of signaling are used in the SIB to indicate that the above configuration information is explicitly carried, or the configuration information is carried in PDCCH common configuration (PDCCH-configCommon) signaling.

[0118] Alternatively, it is indicated through a specific PRACH resource. For example, when the network configures a PRACH resource that allows the terminal to request common PDCCH repetition or configures a PRACH resource that allows the terminal to report the ability to receive PDCCH repetition, it indicates that the network supports the common PDCCH repetition function.

[0119] In some implementations, the indication information includes the PBCH, and the terminal determines, based on the indication information, the configuration information for repeated transmission of the common PDCCH, including:

[0120] Determine at least some parameters in the configuration information for repeated transmission of the public PDCCH based on at least one of the demodulation reference signal (DMRS) sequence of the PBCH, the DMRS pattern of the PBCH, the DMRS time domain resources of the PBCH, the DMRS frequency domain resources of the PBCH, the scrambling sequence of the PBCH, and the load (PBCH payload) of the PBCH.

[0121] By using at least one of the following items in the PBCH, it is possible to indicate the configuration information without introducing additional overhead, thereby saving signaling overhead.

[0122] For example, the generation of the DMRS sequence is related to the configuration information of the Common PDCCH repetition. For example, the parameters used for initializing the DMRS sequence include the number of repetitions of the Common PDCCH repetition.

[0123] For another example, the generation of the scrambling sequence is related to the configuration information of the Common PDCCH repetition. For example, the parameters used for initializing the scrambling sequence include the number of repetitions of the Common PDCCH repetition.

[0124] Another example is to explicitly carry it in the PBCH payload, for example, to explicitly indicate the number of repetitions of Common PDCCH repetition in the layer 1 payload (L1 payload) of the PBCH.

[0125] In some implementations, the downlink channel receiving window may include a window corresponding to at least one of the following:

[0126] Random access response window (RAR window);

[0127] Contention resolution timer;

[0128] Message B response window (MsgB-response window).

[0129] The downlink channel transmission period may include:

[0130] The association period between SSB and random access opportunity (RACH occasion, RO);

[0131] SSB cycle;

[0132] SIB1 period;

[0133] The period of the search space.

[0134] In some embodiments, the RNTI includes: a first RNTI defined for repeated transmission of the common PDCCH, and the first RNTI is used to scramble the DCI related to the common PDCCH.

[0135] The RNTI defined for the repeated transmission of the common PDCCH may be understood as a newly defined RNTI for the repeated transmission of the common PDCCH.

[0136] The generation method of the first RNTI may include: generating based on the second RNTI and the offset. For example, the generation method of the first RNTI may include at least one of the following:

[0137] Based on Random Access Radio Network Temporary Identifier (RA-RNTI) and offset generation;

[0138] Based on the System Information Radio Network Temporary Identifier (SI-RNTI) and offset generation;

[0139] Generated based on a temporary cell radio network temporary identifier (TC-RNTI) and an offset;

[0140] Based on the Paging Radio Network Temporary Identifier (P-RNTI) and offset generation;

[0141] Based on Message B Radio Network Temporary Identifier (MsgB-RNTI) and offset generation;

[0142] The offset is associated with configuration information of repeated transmission of the common PDCCH.

[0143] The association between the offset and the configuration information of the common PDCCH repetition transmission can be understood as the offset being used to indicate the configuration information of the common PDCCH repetition transmission, such as different values / value ranges of the offset corresponding to different Common PDCCH repetition functions / numbers.

[0144] In the above implementation, the indication of the above repetition information is implemented through the above RNTI and offset, so there is no need to introduce additional messages, thereby saving transmission overhead.

[0145] Optionally, the CORESET configuration table includes a first CORESET configuration table, the first CORESET configuration table is a CORESET resource configuration table for a type 0 PDCCH search space set, and different resource configurations in the first CORESET configuration table correspond to respective configuration parameters of common PDCCH repeated transmission; or, the CORESET configuration table includes a second CORESET configuration table, the second CORESET configuration table is a CORESET resource configuration table defined for the common PDCCH repeated transmission, and different indexes in the second CORESET configuration table correspond to respective configuration parameters of common PDCCH repeated transmission; wherein the configuration parameters of the common PDCCH repeated transmission are at least part of the parameters included in the configuration information of the common PDCCH repeated transmission;

[0146] or,

[0147] The monitoring timing table of the CSS includes a monitoring timing table of a first CSS, which is a PDCCH monitoring timing table for a type 0 PDCCH search space set, and the parameters of different PDCCH monitoring timings in the monitoring timing table of the first CSS correspond to the configuration parameters of the respective public PDCCH repeated transmissions; or, the monitoring timing table of the CSS includes a monitoring timing table of a second CSS, which is a monitoring timing table of the CSS defined for the public PDCCH repeated transmissions, and different indexes in the monitoring timing table of the second CSS correspond to the configuration parameters of the respective public PDCCH repeated transmissions; wherein, the configuration parameters of the PDCCH repeated transmissions are at least part of the parameters contained in the configuration information of the public PDCCH repeated transmissions.

[0148] The above configuration parameters may include at least one of the following:

[0149] The function of repeated transmission of the common PDCCH;

[0150] The number of repetitions of the common PDCCH retransmission;

[0151] The index of the common PDCCH repeated transmission;

[0152] Resource information of repeated transmission of the common PDCCH;

[0153] Activation information for repeated transmission of the common PDCCH;

[0154] The repetition mode of the common PDCCH repeated transmission.

[0155] In some implementations, the first CORESET configuration table may be a CORESET resource configuration table for a type 0 PDCCH search space set defined in the protocol, for example, as shown in Table 1 below:

[0156] Table 1:

[0157] Among them, the SS / PBCH block and CORESET multiplexing mode, RB number, symbol number and offset in the above Table 1 are resource configurations, and the number of repetitions is the configuration parameter of PDCCH repeated transmission. Table 1 can represent the relationship between these resource configurations and the configuration parameters of PDCCH repeated transmission.

[0158] Among them, the last column in the above Table 1 is a newly added column. The above Table 1 can indicate the resource block and time slot symbol set of CORESET for type 0 PDCCH search space set, which can be specifically applied to the scenario where the subcarrier spacing (SCS) corresponding to SSB and PDCCH is 15kHz and the minimum channel bandwidth is 5MHz or 10MHz.

[0159] The first CORESET configuration table may be added with a new column for indicating part or all of the configuration information, such as by adding a column to the first CORESET configuration table indicated by the 4-bit Most Significant Bit (MSB) in the SIB1 PDCCH configuration (PDCCH-configSIB1) to indicate whether the common PDCCH is repeatedly transmitted, the number of repetitions, the repetition index or the pattern of repeated transmission.

[0160] The above Table 1 is an example of configuration parameters as the number of repetitions.

[0161] In the above implementation, the configuration parameters of the PDCCH repeated transmission can be indicated by the resource configuration in the first CORESET configuration table, thereby saving configuration overhead.

[0162] The second CORESET configuration table may be a CORESET resource configuration table defined for the repeated transmission of the common PDCCH. For example, the second CORESET configuration table is a CORESET resource configuration table newly defined for the repeated transmission of the common PDCCH.

[0163] In some implementations, the second CORESET configuration table is a CORESET resource configuration table determined based on a condition defined in a protocol and a condition defined for the common PDCCH repeated transmission.

[0164] The conditions defined in the above protocol may be the conditions corresponding to the above first CORESET configuration table, such as the SCS corresponding to the SSB and PDCCH are both 15 kHz, and the minimum channel bandwidth is 5 MHz or 10 MHz.

[0165] The conditions defined for the repeated transmission of the common PDCCH may be newly defined conditions for the repeated transmission of the common PDCCH, for example, including at least one of the following:

[0166] Specific k SSB The value of, specific system frame number, and spare bits in the MIB.

[0167] In the above implementation, the index in the second CORESET configuration table is used to indicate the configuration parameters of the PDCCH repeated transmission, which can more flexibly indicate the above configuration parameters.

[0168] In some embodiments, the monitoring timing table of the first CSS is a PDCCH monitoring timing table for a type 0 PDCCH search space set defined in the protocol. It can be understood that the monitoring timing table of the first CSS is a PDCCH monitoring timing table for a type 0 PDCCH search space set defined in the protocol, for example, as shown in Table 2 below:

[0169] Table 2:

[0170] Among them, O (the index of the first OFDM symbol in the search space), the number of search space sets in each time slot, M (the number of search spaces in each time slot) and the first symbol index in the above Table 2 are resource configurations, and the number of repetitions is the configuration parameter for PDCCH repeated transmission. Table 2 can represent the relationship between these resource configurations and the configuration parameters for PDCCH repeated transmission.

[0171] The last column in Table 2 is a newly added column. Table 2 can be applied to the scenario of SSB / PBCH and CORESET repetition pattern 1 in frequency range (FR) 1. Table 2 is illustrated by indicating the number of repetitions.

[0172] The above-mentioned first CSS monitoring timing table is added with a new column for indicating part or all of the configuration information, such as adding a column to the first CSS monitoring timing table indicated by the 4-bit least significant bit (LSB) in PDCCH-configSIB1 to indicate whether the public PDCCH is repeatedly transmitted, the number of repetitions, the repetition index or the pattern of repeated transmission, etc.

[0173] In the above implementation, the configuration parameters of PDCCH repeated transmission can be indicated by using the parameters of the PDCCH monitoring timing in the monitoring timing table of the first CSS, thereby saving configuration overhead.

[0174] The above-mentioned second CSS monitoring timing table may be a CSS monitoring timing table defined for repeated transmission of the common PDCCH, for example, the second CSS monitoring timing table may be a CSS monitoring timing table newly defined for repeated transmission of the common PDCCH.

[0175] In some implementations, the second CSS monitoring timing table is a CSS monitoring timing table determined based on conditions defined in a protocol and conditions defined for repeated transmission of the common PDCCH.

[0176] The conditions defined in the protocol may be conditions corresponding to the monitoring timing table of the first CSS, such as SSB / PBCH and CORESET repeating pattern 1, and being in FR1.

[0177] The conditions defined for the repeated transmission of the common PDCCH may be newly defined conditions for the repeated transmission of the common PDCCH, for example, including at least one of the following:

[0178] Specific k SSB The value of, specific system frame number, and spare bits in the MIB.

[0179] In the above implementation, the configuration parameters of PDCCH repeated transmission are indicated by the index in the monitoring opportunity table of the second CSS, which can more flexibly indicate the above configuration information.

[0180] Optionally, the number of resources existing in the downlink channel receiving window is associated with some or all parameters in the configuration information, and the number of resources includes at least one of the following: the number of CORESETs, the number of search spaces, and the number of PDCCH MOs;

[0181] or,

[0182] The transmission resource for repeated transmission of the common PDCCH is located within the downlink channel receiving window;

[0183] or,

[0184] The number of resources existing in the downlink channel transmission period is associated with part or all of the configuration information, and the number of resources includes at least one of the following: the number of CORESETs, the number of search spaces, and the number of PDCCH MOs;

[0185] or,

[0186] The transmission resource for repeated transmission of the common PDCCH is located within the downlink channel transmission period.

[0187] The number of CORESETs, the number of search spaces, and the number of PDCCH MOs may be used to indicate the number of repetitions of the common PDCCH, and the number of CORESETs, the number of search spaces, and the number of PDCCH MOs may be the same as or a multiple of the number of repetitions of the common PDCCH. Alternatively, the number of CORESETs, the number of search spaces, and the number of PDCCH MOs may be functions for indicating repeated transmission of the common PDCCH, such as a specific number of CORESETs, the number of search spaces, and the number of PDCCH MOs indicating support for repeated transmission of the common PDCCH.

[0188] In the above implementation, the configuration information is indicated by the number of CORESETs, the number of search spaces, and the number of PDCCH MOs, which can save configuration overhead.

[0189] The transmission resources of the above-mentioned repeated public PDCCH transmission are located within the downlink channel reception window, which may indicate that the actual transmission resources / pattern of the repeated public PDCCH transmission are within the downlink channel reception window, such as discarding PDCCH transmissions that are not within the downlink channel reception window.

[0190] The transmission resources of the above-mentioned repeated public PDCCH transmission are located within the downlink channel transmission period, which may mean that the actual transmission resources / pattern of the repeated public PDCCH transmission are within the downlink channel transmission period, such as discarding PDCCH transmissions that are not within the downlink channel transmission period.

[0191] In the above implementation, the actual transmission resource for repeated PDCCH transmission can be accurately determined through the above downlink channel reception window or downlink channel transmission period, so as to further improve the reliability of public PDCCH reception.

[0192] Optionally, the downlink channel receiving window includes at least one of the following:

[0193] A window configured for repeated transmission of the common PDCCH, a reception window of a downlink channel defined in a protocol, and a window determined based on downlink channel transmission parameters;

[0194] or,

[0195] The downlink channel receiving period includes at least one of the following:

[0196] The period configured for repeated transmission of the common PDCCH, the reception period of the downlink channel defined in the protocol, and the period determined based on the downlink channel transmission parameters.

[0197] The window configured by the network side for repeated transmission of the common PDCCH may be understood as a new window configured by the network, such as the window start time, offset, window size, window end time or window period configured by the network side.

[0198] The period configured by the network side for repeated transmission of the common PDCCH may be understood as a new period configured by the network, such as the period start time, offset, period size, and period end time configured by the network side.

[0199] The above-mentioned window determined based on the downlink channel transmission parameters can be a window determined based on the existing downlink channel transmission parameters, for example: the window is determined based on the SSB period and the relationship between SSB and CORESET0, such as the starting time of the above-mentioned downlink channel receiving window is the position of the first CORESET#0 after the SSB transmission, and the size of the window is the SSB period; or the starting time of the downlink channel receiving window is the position of the first CORESET#0 after the SSB transmission, and the end time of the window is the position of the last CORESET#0 before the next SSB is sent.

[0200] The period determined based on the downlink channel transmission parameters may be a period determined based on existing downlink channel transmission parameters, for example, the period is determined based on the SSB period and the relationship between the SSB and CORESET0.

[0201] The receiving window of the downlink channel defined in the above protocol may include a window corresponding to at least one of the following:

[0202] Random access response window (RAR window);

[0203] Contention resolution timer;

[0204] Message B response window (MsgB-response window).

[0205] The receiving period of the downlink channel defined in the above protocol may include:

[0206] The association period between SSB and random access opportunity (RACH occasion, RO);

[0207] SSB cycle;

[0208] SIB1 period;

[0209] The period of the search space.

[0210] In the above implementation, the downlink channel receiving window or downlink channel receiving period may be determined in a variety of ways to support more flexible repeated transmission of the common PDCCH.

[0211] As an optional implementation manner, the common PDCCH repeated transmission satisfies at least one of the following:

[0212] The time domain resources of the repeated transmission of the public PDCCH in CORESET#0 do not overlap with the time domain resources of the associated SSB; or, the time domain resources of the repeated transmission of the public PDCCH in CORESET#0 overlap with the time domain resources of the associated SSB;

[0213] The common PDCCH is repeatedly transmitted the same number of times in multiple SSB periods;

[0214] The common PDCCH is repeatedly transmitted the same number of times in multiple first periods, where the first period is a period in which the SSB is associated with the RO;

[0215] The common PDCCH repeated transmission is located within the downlink channel receiving window;

[0216] The common PDCCH repetitive transmission is in a downlink channel transmission period.

[0217] Among them, the time domain resources of the public PDCCH repeated transmission within CORESET#0 do not overlap with the time domain resources of the associated SSB. This means that when the SSB and CORESET#0 are in multiplexing mode 1 or 2, the SSB and the CORESET#0 resources where the public PDCCH is repeatedly transmitted cannot overlap in the time domain, that is, the time domain resources of the public PDCCH repeated transmission must avoid the symbol position where the corresponding SSB is located.

[0218] The overlap of the time domain resources of the above-mentioned common PDCCH repeated transmission within CORESET#0 and the time domain resources of the associated SSB can be that when the SSB and CORESET#0 are in multiplexing mode 3, the CORESET#0 resources where the SSB and the common PDCCH repeated transmission are located must be at the same time in the time domain.

[0219] The above-mentioned repeated transmission of the common PDCCH is the same number of times in multiple SSB cycles, which can be that the number of transmissions of the common PDCCH in each SSB cycle in these multiple SSB cycles is the same, such as once or multiple times in each SSB cycle, so as to facilitate the terminal to monitor the common PDCCH in multiple SSB cycles.

[0220] The above-mentioned repeated transmission of the public PDCCH is the same number of times in multiple first periods, which can be that the number of transmissions of the public PDCCH in each first period in these multiple first periods is the same, such as once or multiple times in each first period, so as to facilitate the terminal to monitor the public PDCCH in multiple first periods.

[0221] In this way, the time domain resources for repeated transmission of the common PDCCH can be flexibly determined according to the multiplexing mode of SSB and CORESET#0, so as to improve the reception reliability of the common PDCCH.

[0222] In addition, in the above embodiment, since the number of repetitions of the common PDCCH repeated transmission is an integer multiple of one SSB period of the SSB, the number of repetitions of the PDCCH repeated transmission can be determined by the SSB period, thereby saving configuration overhead; and the number of repetitions of the common PDCCH repeated transmission is an integer multiple of the period associated with the SSB and the RO, thereby determining the number of repetitions of the PDCCH repeated transmission by the period associated with the SSB and the RO, thereby saving configuration overhead;

[0223] In addition, in the above implementation, since the common PDCCH repetition transmission is located within the downlink channel receiving window, or the common PDCCH repetition transmission is located within the downlink channel transmission period, the transmission resources of the common PDCCH repetition transmission can be determined by the downlink channel receiving window or the downlink channel receiving period to save configuration overhead.

[0224] As an optional implementation manner, the common PDCCH repeated transmission includes at least one of the following:

[0225] Repeated transmission of the common PDCCH in the time domain;

[0226] Repeated transmission of the common PDCCH in the frequency domain;

[0227] The common PDCCH is repeatedly transmitted in the spatial domain.

[0228] In some implementations, the repeated transmission of the common PDCCH in the time domain includes at least one of the following:

[0229] Repeated transmission of the common PDCCH on different PDCCH MOs in the same search space of the same CORESET;

[0230] Repeated transmission of the common PDCCH between different search spaces of the same CORESET;

[0231] Repeated transmission of the common PDCCH between different search spaces of different CORESETs;

[0232] The common PDCCH is repeatedly transmitted in the same search space of different CORESETs.

[0233] The repeated transmission of the common PDCCH on different PDCCH MOs in the same search space of the same CORESET may be repeated transmission of the common PDCCH on different PDCCH MOs in the same search space of the same CORESET.

[0234] The repeated transmission of the common PDCCH between different search spaces of the same CORESET may be repeated transmission of the common PDCCH between different search spaces of the same CORESET.

[0235] The repeated transmission of the common PDCCH in the same search space of different CORESETs may be that the search space used for the repeated transmission of the common PDCCH in different CORESETs is the same.

[0236] In some implementations, the repeated transmission of the common PDCCH in the frequency domain includes at least one of the following:

[0237] Repeated transmission of the common PDCCH on the same PDCCH MO of the same CORESET;

[0238] The common PDCCH is repeatedly transmitted on the same PDCCH MO of different CORESETs.

[0239] The same PDCCH MO mentioned above may be located in the same search space or in different search spaces.

[0240] The repeated transmission of the common PDCCH on the same PDCCH MO of different CORESETs can be understood as different transmissions (or different repetitions) of the common PDCCH being copied multiple times on the CORESET resources at one moment.

[0241] In the above implementation, repeated transmission can be achieved in the time domain, frequency domain or spatial domain, further improving the transmission performance of the common PDCCH.

[0242] As an optional implementation, the method further includes:

[0243] In a case where resources for repeated transmission of the common PDCCH conflict with resources for initial transmission of other common PDCCHs, the terminal abandons reception of the repeated transmission of the common PDCCH.

[0244] The terminal giving up receiving the repeated transmission of the common PDCCH may be the terminal giving up monitoring or detecting the repeated transmission of the common PDCCH.

[0245] The conflict between the resources of the repeated transmission of the above-mentioned public PDCCH and the resources of the first transmission of other public PDCCHs may be that the resources of the repeated transmission of the above-mentioned public PDCCH overlap with the resources of the first transmission of other public PDCCHs. The resources of the repeated transmission of the above-mentioned public PDCCH may be the resources of a certain transmission of the public PDCCH. For example, if the resources of the nth transmission of the public PDCCH conflict with the resources of the first transmission of other public PDCCHs, the nth transmission is discarded.

[0246] In addition, when the terminal abandons the repeated transmission of the common PDCCH, the discarded transmission is counted in the total number of repeated transmissions of the common PDCCH, or the discarded transmission is not counted in the total number of repeated transmissions of the common PDCCH, that is, in the case of discarding the above-mentioned repeated transmission, the number of repetitions of the common PDCCH is +1 or not +1, which is specifically determined by the protocol agreement or network side configuration, or according to the service or transmission resources.

[0247] In this implementation, since the resources for repeated transmission of the public PDCCH conflict with the resources for the first transmission of other public PDCCHs, the terminal abandons the repeated transmission of the public PDCCH, which can prioritize the first transmission of the public PDCCH to improve the transmission performance of the public PDCCH.

[0248] As an optional implementation, when the common PDCCH includes multiple PDCCHs: repetition information of the multiple PDCCHs is independently determined; or repetition information of some or all of the multiple PDCCHs is uniformly determined. The repetition information may be configuration information for repeated transmission of the common PDCCH or timeline information for repeated transmission of the common PDCCH.

[0249] The repetition information of the above-mentioned multiple PDCCHs is independently determined, and it can be an indication that there will be corresponding repetition information for each public PDCCH repetition transmission. In this way, the repetition information of each public PDCCH repetition transmission is independently indicated, which can improve the flexibility of public PDCCH transmission to meet the needs of more terminals, services or scenarios.

[0250] For example, there are indications of repeated information of SIB1 PDCCH repeated transmission, indications of repeated information of OSIPDCCH repeated transmission, indications of repeated information of Msg2 / 4 / B PDCCH repeated transmission, indications of repeated information of Paging PDCCH repeated transmission, and indications of repeated information of PDCCH repeated transmission for scheduling Msg3 retransmission, etc.

[0251] The repetition information of some or all of the above-mentioned multiple PDCCHs is uniformly determined. Some or all of the multiple PDCCHs may correspond to only one type of repetition information. In this way, the repetition information repeatedly transmitted by different Common PDCCHs is uniformly indicated, which can save transmission overhead.

[0252] For example, only the repetition information of repeated transmission of common PDCCH needs to be indicated once, and the repetition information of repeated transmission of multiple common PDCCH channels (such as SIB1 PDCCH, OSIPDCCH, Msg2 / 4 / B PDCCH, Paging PDCCH, and PDCCH scheduling Msg3 retransmission) is indicated.

[0253] As an optional implementation manner, the terminal performs PDCCH repeated transmission according to the configuration information of the PDCCH repeated transmission, including:

[0254] The terminal performs PDCCH retransmission according to the configuration information of the PDCCH retransmission and the timeline information of the common PDCCH retransmission, where the timeline information of the common PDCCH retransmission includes at least one of the following:

[0255] The timing relationship between the repeated transmission of the common PDCCH and the PDSCH scheduled by the common PDCCH;

[0256] The time relationship between the common PDCCH repetitive transmission and the RAR receiving window;

[0257] The time relationship between the common PDCCH retransmission and the contention resolution timer;

[0258] The time relationship between the common PDCCH repeated transmission and the MsgB response window.

[0259] The timing relationship between the repeated transmission of the common PDCCH and the PDSCH scheduled by the common PDCCH may be a time domain interval relationship or an offset relationship between the repeated transmission of the common PDCCH and the PDSCH scheduled by the common PDCCH.

[0260] Optionally, the timing relationship between the repeated transmission of the common PDCCH and the PDSCH scheduled by the common PDCCH includes the following:

[0261] The time slot offset of the PDSCH scheduled by the common PDCCH is an offset relative to the time slot of the first transmission of the repeated transmission of the common PDCCH;

[0262] The time slot offset of the PDSCH scheduled by the common PDCCH is the time slot offset relative to the time slot of the last transmission of the repeated transmission of the common PDCCH;

[0263] The time slot offset of the PDSCH scheduled by the public PDCCH is the time slot offset relative to the time slot of the nth transmission of the repeated transmission of the public PDCCH, where the value of n is configured on the network side or agreed upon by the protocol;

[0264] The time slot offset of the PDSCH scheduled by the common PDCCH is an offset relative to a target time point of a receiving window associated with repeated transmission of the common PDCCH.

[0265] The value of n may be determined by protocol agreement, network configuration or in advance.

[0266] When the time slot offset is 0 (e.g., time slot offset K0=0), it means that the PDSCH and a certain transmission of the PDCCH that schedules the PDSCH are transmitted in the same time slot. In this case, the relationship between the starting symbol of the PDSCH and the Common PDCCH includes one or more of the following:

[0267] The starting symbol of the PDSCH and the starting symbol of the Common PDCCH are separated by N symbols, where N>=0;

[0268] The starting symbol of the PDSCH and the last symbol of the Common PDCCH are separated by N symbols, where N>=0.

[0269] The receiving window associated with the repeated transmission of the common PDCCH may be a time window for receiving the common PDCCH, such as a RAR receiving window or a MsgB response window.

[0270] The target time point may be agreed upon by the protocol or configured on the network side. For example, the target time point may be the first time slot where the receiving window is located.

[0271] In some implementations, the first transmission of the common PDCCH includes one of the following:

[0272] The public PDCCH is repeatedly transmitted for the first time on the physical time slot;

[0273] The common PDCCH is repeatedly transmitted for the first time in an available time slot;

[0274] The public PDCCH is repeatedly transmitted for the first time within the RAR receiving window;

[0275] The first transmission of the common PDCCH repeated transmission within the MsgB response window;

[0276] The first valid transmission of the common PDCCH repeated transmission.

[0277] In some embodiments, the last transmission of the common PDCCH repeated transmission includes one of the following:

[0278] The common PDCCH is repeatedly transmitted for the last time on the physical time slot;

[0279] The common PDCCH is repeatedly transmitted in the last transmission in the available time slot;

[0280] The last transmission of the common PDCCH repetition within the RAR receiving window;

[0281] The common PDCCH repeats the last transmission within the MsgB response window;

[0282] The last valid transmission of the common PDCCH repeated transmission;

[0283] In some embodiments, the nth transmission of the common PDCCH repeated transmission includes one of the following:

[0284] The common PDCCH is repeatedly transmitted for the nth time on the physical time slot;

[0285] The common PDCCH is repeatedly transmitted for the nth time in the available time slot;

[0286] The common PDCCH is repeatedly transmitted for the nth time within the RAR receiving window;

[0287] The common PDCCH is repeatedly transmitted for the nth time within the MsgB response window;

[0288] The nth valid transmission of the common PDCCH repeated transmission.

[0289] In the above implementation, a variety of timing relationships between repeated transmissions of the common PDCCH and the PDSCH scheduled by the common PDCCH can be supported, thereby supporting more flexible reception of the common PDCCH and PDSCH, thereby improving downlink transmission performance of the terminal.

[0290] Optionally, the time relationship between the common PDCCH repetitive transmission and the RAR receiving window includes the following:

[0291] The public PDCCH repeated transmission allows crossing the RAR receiving window, and the public PDCCH repeated transmission does not allow crossing the RAR receiving window;

[0292] or,

[0293] The time relationship between the common PDCCH retransmission and the contention resolution timer includes the following:

[0294] The common PDCCH repeated transmission is allowed to cross the contention resolution timer, and the common PDCCH repeated transmission is not allowed to cross the contention resolution timer;

[0295] or,

[0296] The time relationship between the common PDCCH retransmission and the MsgB response window includes the following:

[0297] The common PDCCH repetitive transmission is allowed to cross the MsgB response window, and the common PDCCH repetitive transmission is not allowed to cross the MsgB response window.

[0298] The above-mentioned repeated transmission of the common PDCCH is allowed to cross the RAR receiving window. As long as the first transmission of the common PDCCH is within the RAR receiving window, the remaining transmissions may not be within the RAR receiving window, which can further improve the reception reliability of the common PDCCH.

[0299] The above-mentioned common PDCCH repeated transmission is not allowed to cross the RAR receiving window, which may include at least one of the following:

[0300] For the common PDCCH transmission resources that are not within the RAR receive window, it is determined that these transmission resources are not used for repeated transmission of the common PDCCH; wherein, if resources for more than or equal to N repeated PDCCH transmissions cannot be found within the RAR receive window, the PDCCH repeated transmission is not performed, where N is the number of repeated PDCCH transmissions configured by the network;

[0301] The terminal does not limit the public PDCCH beyond the RAR reception window;

[0302] The terminal only monitors the common PDCCH within the RAR receiving window and discards the transmission of the common PDCCH beyond the RAR receiving window.

[0303] In the above implementation, since repeated transmission of the common PDCCH is not allowed to cross the RAR receiving window, the terminal only needs to monitor the common PDCCH in the RAR receiving window, thereby saving power consumption of the terminal.

[0304] For the description of whether to allow the cross-contention resolution timer or the MsgB response window, refer to the corresponding description of the RAR receiving window, which will not be repeated here, and the same beneficial effects can be achieved.

[0305] Optionally, the RAR receiving window includes: a RAR receiving window that can be used for repeated transmission of the public PDCCH; or a RAR receiving window obtained by adding an offset to a RAR receiving window that cannot be used for repeated transmission of the public PDCCH;

[0306] or,

[0307] The message B response window includes:

[0308] A message B response window that can be used for repeated transmission of a common PDCCH; or a message B response window obtained by adding an offset to a message B response window that cannot be used for repeated transmission of the common PDCCH;

[0309] or,

[0310] The contention resolution timer includes:

[0311] A contention resolution timer defined for common PDCCH repetitive transmission; or a contention resolution timer obtained by adding an offset to a contention resolution timer defined for common PDCCH repetitive transmission.

[0312] The above offset may be configured by the network or predetermined.

[0313] The RAR receive window that can be used for the common PDCCH retransmission can be a newly defined RAR receive window for the common PDCCH retransmission, for example, referred to as a RAR-repetition receive window. This RAR-repetition receive window can replace the RAR window, or take effect after the RAR receive window times out, or the duration of the RAR-repetition receive window can be related to repetition information (e.g., the number of repetitions) of the common PDCCH retransmission. For example, the length of the RAR-repetition receive window is the configured RAR receive window multiplied by the number of common PDCCH repetitions.

[0314] The RAR receiving window obtained by adding an offset to the RAR receiving window that is not available for the repeated transmission of the public PDCCH may be an extension of the RAR receiving window that is not available for the repeated transmission of the public PDCCH. The above-mentioned offset may be defined by network configuration or protocol agreement or determined by repetition information of the repeated transmission of the public PDCCH, and its unit may be symbol, time slot, millisecond, etc.

[0315] The total duration of the RAR receive window obtained by adding an offset to the RAR receive window that is not available for repeated public PDCCH transmission, or the duration of the RAR receive window that is available for repeated public PDCCH transmission, cannot exceed the M duration. If the duration exceeds the M duration, it is considered to be the M duration. Specifically, the M duration can be 10 ms or other network-predefined value.

[0316] In the above embodiment, the RAR receiving window defined for repeated public PDCCH transmission is used to better match the RAR receiving window with the public PDCCH, which helps the terminal better monitor the public PDCCH. The RAR receiving window obtained by adding an offset to the RAR receiving window that is not used for repeated public PDCCH transmission can use the existing RAR receiving window, thereby reducing complexity.

[0317] The MsgB response window that can be defined for repeated common PDCCH transmissions can be a newly defined window for repeated common PDCCH transmissions. This window can replace the MsgB response window defined in the protocol, or take effect after the MsgB response window times out. Alternatively, the duration of this window can be related to repetition information (e.g., the number of repetitions) for repeated common PDCCH transmissions. For example, the window length can be the configured RAR receive window multiplied by the number of repeated common PDCCH transmissions.

[0318] The MsgB response window obtained by adding an offset to the MsgB response window that is not available for the repeated transmission of the common PDCCH may be an extension of the MsgB response window that is not available for the repeated transmission of the common PDCCH. The above-mentioned offset may be defined by network configuration or protocol agreement or determined by repetition information of the repeated transmission of the common PDCCH, and its unit may be symbol, time slot, millisecond, etc.

[0319] The total duration of the MsgB response window obtained by adding the offset to the MsgB response window that is not available for repeated public PDCCH transmission, or the duration of the MsgB response window that can be used for repeated public PDCCH transmission, cannot exceed the M duration. If the duration exceeds the M duration, it is considered to be the M duration. Specifically, the M duration can be 10 ms or other network-predefined values.

[0320] In the above embodiment, the MsgB response window defined for repeated transmission of the common PDCCH is used to better match the MsgB response window with the common PDCCH, which helps the terminal better monitor the common PDCCH. The MsgB response window obtained by adding an offset to the MsgB response window that is not used for repeated transmission of the common PDCCH can use the existing MsgB response window, thereby reducing complexity.

[0321] The contention resolution timer that can be used for the common PDCCH retransmission definition can be a newly defined contention resolution timer for the common PDCCH retransmission. This timer can be used to replace the contention resolution timer defined in the protocol, or the timer can take effect after the contention resolution timer expires, or the length of the timer can be related to repetition information (e.g., the number of repetitions) of the common PDCCH retransmission. For example, the length of the timer is the configured RAR receive window multiplied by the number of common PDCCH repetitions.

[0322] The contention resolution timer obtained by adding an offset to the contention resolution timer that is not applicable for the repeated transmission of the common PDCCH may be an extension of the contention resolution timer that is not applicable for the repeated transmission of the common PDCCH. The offset may be defined by a network configuration or protocol agreement or determined by repetition information of the repeated transmission of the common PDCCH, and its unit may be a symbol, a time slot, a millisecond, etc.

[0323] The total duration of the contention resolution timer obtained by adding the offset to the contention resolution timer that is not available for the common PDCCH repeated transmission, or the duration of the contention resolution timer that can be used for the common PDCCH repeated transmission, cannot exceed the M duration. If the duration exceeds the M duration, it is considered to be the M duration. Specifically, the M duration can be 10 ms or other network-predefined values.

[0324] In the above embodiment, the contention resolution timer defined for repeated transmission of the common PDCCH is used to better match the contention resolution timer with the common PDCCH, which helps the terminal better monitor the common PDCCH. Furthermore, the contention resolution timer obtained by adding an offset to the contention resolution timer that is not used for repeated transmission of the common PDCCH can use the existing contention resolution timer, thereby reducing complexity.

[0325] Optionally, the starting time of the RAR receiving window includes:

[0326] The first symbol of the CORESET that earliest meets the target condition in the first resource;

[0327] The first resource includes:

[0328] A resource located after the last symbol occupied by the PRACH and separated from the last symbol occupied by the PRACH by at least one symbol; or

[0329] The resource located after the last symbol occupied by the PRACH and separated from the last symbol occupied by the PRACH by a distance greater than or equal to the target time, where the target time is equal to: at least one symbol + T TA +k mac, T TA Indicates the duration of timing advance, k mac Indicates the scheduling offset supported by the non-terrestrial network (NTN) for enhancing the timing relationship between MAC and CE.

[0330] The target condition may be a condition defined by a protocol or configured on the network side. For example, the CORESET that meets the target condition may be the CORESET where a certain transmission of the common PDCCH occurs.

[0331] In some embodiments, the CORESET that meets the target conditions includes:

[0332] The CORESET where the i-th transmission of the repeated transmission of the public PDCCH is located, the value of i is equal to or greater than 1, and is less than or equal to the number of repetitions of the public PDCCH.

[0333] i may be defined by the protocol or configured on the network side, such as the i-th transmission is the first transmission of the common PDCCH.

[0334] The above-mentioned PRACH may be the PRACH corresponding to the above-mentioned common PDCCH.

[0335] In the above embodiment, the first symbol of the CORESET that earliest meets the target condition in the above first resource can be used as the RAR receiving window, so that the terminal can better monitor the public PDCCH in the RAR receiving window. In addition, since the first resource includes resources that are located after the last symbol occupied by PRACH and are spaced at least one symbol from the last symbol occupied by the PRACH, this allows at least one symbol to be spaced between the PRACH and the public PDCCH, so that the terminal can better monitor the public PDCCH. The above first resource is located after the last symbol of the physical uplink shared channel PUSCH opportunity corresponding to the PRACH, and the interval with the last symbol of the physical uplink shared channel PUSCH opportunity corresponding to the PRACH is greater than or equal to the target time, so that the interval between the PRACH and the public PDCCH can be at least one symbol + T TA +k mac , so that the terminal can better monitor the common PDCCH.

[0336] Optionally, the start time of the contention resolution timer includes: the first time after the transmission of Msg3 is completed, or the interval between the start time of the contention resolution timer and the transmission end time of Msg3 is equal to or greater than the round trip time (RTT);

[0337] The first moment includes at least one of the following:

[0338] The first symbol of the next time slot after the Msg3 transmission is completed;

[0339] The first symbol of the earliest CORESET after the Msg3 transmission is completed;

[0340] The first symbol of the CORESET that earliest meets the target condition in the second resource;

[0341] The second resource includes:

[0342] After the Msg3 transmission is completed, the resources are separated from the Msg3 transmission by at least one symbol.

[0343] In the case of repeated transmission of message 3, the above-mentioned Msg3 transmission completion indicates that all transmissions of the repeated Msg3 transmissions are completed.

[0344] Among them, the CORESET of the above target conditions can be found in the corresponding description of the above implementation method, which will not be repeated here.

[0345] In some implementations, in an NTN scenario, the interval between the start time of the contention resolution timer and the end time of transmission of Msg3 is equal to or greater than the RTT.

[0346] In the above embodiment, by including the start time of the contention resolution timer at the first time after the transmission of Msg3, the terminal can monitor the common PDCCH only after the transmission of Msg3 during the contention resolution timer, thereby enabling the terminal to better monitor the common PDCCH. By ensuring that the interval between the start time of the contention resolution timer and the end time of Msg3 transmission is equal to or greater than the RTT, the interval between Msg3 and the common PDCCH can be the RTT, thereby enabling the terminal to better monitor the common PDCCH.

[0347] Optionally, the starting time of the MsgB response window includes at least one of the following:

[0348] The first symbol of the CORESET where the first transmission of the common PDCCH repeated transmission is located;

[0349] The first symbol of the CORESET where the last transmission of the common PDCCH repetition occurs;

[0350] The first symbol of the CORESET where the i-th transmission of the common PDCCH is repeated, where the value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH;

[0351] The first symbol of the earliest CORESET in the third resource;

[0352] The first symbol of the CORESET that earliest meets the target condition in the third resource;

[0353] The third resource includes:

[0354] A resource located after the last symbol of a physical uplink shared channel (PUSCH) opportunity corresponding to a PRACH and spaced at least one symbol from the last symbol of a PUSCH opportunity corresponding to the PRACH; or

[0355] The resource is located after the last symbol of the PUSCH opportunity corresponding to the PRACH and the interval between the last symbol of the PUSCH opportunity corresponding to the PRACH is greater than or equal to the target time, and the target time is equal to: at least one symbol + T TA +k mac , T TA Indicates the duration of timing advance, k mac Indicates the scheduling offset supported by the non-terrestrial network (NTN) for enhancing the timing relationship between the media access control element (MAC) and the CE.

[0356] Among them, the CORESET and T of the above target conditions TA +k mac Please refer to the corresponding description of the above implementation mode, which will not be repeated here.

[0357] The above-mentioned PRACH may be the PRACH corresponding to the above-mentioned common PDCCH.

[0358] In the above implementation, the starting time of the MsgB response window can be flexibly configured to meet the needs of more terminals, services or scenarios.

[0359] As an optional implementation, it also includes:

[0360] When any of the following conditions is met, the common PDCCH repeated transmission is deactivated:

[0361] The terminal sends message 3;

[0362] The terminal receives a successful RAR;

[0363] RAR receiving window ends;

[0364] The maximum allowed RAR window ends;

[0365] The contention resolution timer times out;

[0366] Message 4: Message 4 was decoded successfully.

[0367] Message B is decoded successfully;

[0368] Deactivate the network-side configuration.

[0369] For example, after sending Msg3, the terminal deactivates the common PDCCH repeated transmission;

[0370] After receiving a successful RAR, the terminal deactivates the common PDCCH repetitive transmission;

[0371] Deactivate the common PDCCH repeated transmission after the RAR receives the window;

[0372] Deactivate the common PDCCH repeated transmission after the maximum allowed RAR window;

[0373] Deactivating the common PDCCH repeated transmission after the contention resolution timer expires;

[0374] After successful decoding of message 4 Msg4, the common PDCCH retransmission is deactivated;

[0375] After MsgB decoding is successful, the common PDCCH retransmission is deactivated;

[0376] The network side configures deactivation of the common PDCCH repeated transmission.

[0377] The above-mentioned terminal deactivates after sending Msg3, deactivates after receiving a successful RAR, deactivates after the RAR receiving window, deactivates after the maximum allowed RAR window, deactivates after the contention resolution timer expires, deactivates after successful decoding of message 4Msg4, and deactivates after successful decoding of MsgB. The deactivation can be after the terminal sends Msg3, after the terminal receives a successful RAR, after the RAR receiving window, after the maximum allowed RAR window, after the contention resolution timer expires, after successful decoding of Msg4, after successful decoding of MsgB, immediately or after an interval of at least one time domain resource to deactivate the common PDCCH repeated transmission, and the time domain resource can be a symbol or a time slot.

[0378] The network configuration includes at least one of the following:

[0379] Configured via RRC messages;

[0380] Configured through MAC CE messages;

[0381] Through RAR configuration, for example, RAR in four-step RACH, or fallback RAR or success RAR in two-step RACH, for example, RAR is used to indicate whether subsequent Msg4 PDCCH repetition is supported;

[0382] Through DCI configuration, for example: through the PDCCH indication of scheduling SIB1, whether the subsequent RAR PDCCH, Msg4 PDCCH, and paging PDCCH support repeated transmission.

[0383] In this implementation, it is possible to flexibly deactivate the common PDCCH repeated transmission in the above-mentioned multiple situations, thereby improving the transmission flexibility of the common PDCCH.

[0384] As an optional implementation manner, when the i-th transmission of the common PDCCH repeated transmission and the PDSCH scheduled by the common PDCCH are transmitted in the same time slot, the starting symbol of the PDSCH scheduled by the common PDCCH and the common PDCCH repeated transmission relationship include at least one of the following:

[0385] There is an interval of N symbols between the starting symbol of the PDSCH scheduled by the common PDCCH and the starting symbol of the i-th transmission of the repeated transmission of the common PDCCH;

[0386] There is an interval of N symbols between the starting symbol of the PDSCH scheduled by the common PDCCH and the i-th transmission symbol of the repeated transmission of the common PDCCH;

[0387] The value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH, and N is greater than or equal to 0.

[0388] The above N is a protocol agreement or a network configuration.

[0389] In this implementation, the transmission resources for repeated transmission of the common PDCCH can be determined based on the starting symbol of the PDSCH of the common PDCCH, which can avoid introducing additional signaling and save transmission overhead.

[0390] In the embodiment of the present application, the above-mentioned common PDCCH may be all or part of the common PDCCHs supported by the terminal, and the above-mentioned method for determining the repetition information may be applicable to all or part of the common PDCCHs supported by the terminal.

[0391] In this embodiment of the present application, a terminal obtains configuration information for repeated transmission of a common PDCCH; the terminal receives repeated transmissions of the common PDCCH based on the configuration information; wherein the common PDCCH includes at least one of the following: SIB1 PDCCH, OSIP PDCCH, Message 2 PDCCH, Message 4 PDCCH, Message B PDCCH, Paging PDCCH, and PDCCH scheduling Message 3 retransmission. This enables the terminal to receive repeated transmissions of the common PDCCH, thereby improving network coverage performance.

[0392] For example, before the terminal establishes an RRC connection, the network device uses the public PDCCH to send scheduling information for some public messages (such as RMSI / OSI / Paging / Msg2 / MsgB / Msg4). In some scenarios, such as the NTN scenario, the PDCCH used to schedule Msg2 is repeatedly transmitted, so that the terminal can better receive the PDCCH and receive Msg2, thereby improving the random access success rate.

[0393] Please refer to FIG3 , which is a flowchart of another method for processing repeated PDCCH transmissions provided by an embodiment of the present application. As shown in FIG3 , the method includes the following steps:

[0394] Step 301: The network side device sends configuration information of repeated transmission of the common PDCCH to the terminal;

[0395] Step 302: The network-side device performs repeated transmission of the common PDCCH according to the configuration information;

[0396] The public PDCCH includes at least one of the following:

[0397] System information block SIB1 PDCCH, OSI PDCCH, message 2 PDCCH, message 4 PDCCH, message BPDCCH, paging PDCCH, and PDCCH scheduling message 3 retransmission.

[0398] Optionally, the configuration information includes at least one of the following parameters:

[0399] The function of repeated transmission of the common PDCCH;

[0400] The number of repetitions of the common PDCCH retransmission;

[0401] The index of the common PDCCH repeated transmission;

[0402] Resource information of repeated transmission of the common PDCCH;

[0403] Activation information of the common PDCCH repeated transmission, where the activation information indicates activation or deactivation of the common PDCCH repeated transmission;

[0404] The repetition mode of the common PDCCH repeated transmission.

[0405] Optionally, the resource information for repeated transmission of the common PDCCH includes at least one of the following:

[0406] A pattern of repeated transmission of the common PDCCH, wherein the pattern is used to indicate a resource position occupied by repeated transmission of the common PDCCH;

[0407] Instruction information for instructing the common PDCCH to be repeatedly transmitted based on available time slots;

[0408] Indication information used to instruct the common PDCCH to be repeatedly transmitted based on the physical time slot.

[0409] Optionally, the repetition mode of the common PDCCH repeated transmission includes at least one of the following:

[0410] Based on repeated transmission within a time slot;

[0411] Based on repeated transmission between time slots.

[0412] Optionally, the network side device sends configuration information for repeated transmission of a common PDCCH to the terminal, including:

[0413] The network side device sends indication information to the terminal, where the indication information is used to determine configuration information for repeated transmission of the common PDCCH, and the indication information includes at least one of the following:

[0414] Synchronization signal block SSB, master information block MIB, physical broadcast channel PBCH, system information block SIB, radio network temporary identifier RNTI, control resource set CORESET configuration table, common search space CSS monitoring opportunity table, downlink channel receiving window, downlink channel transmission period, CORESET resources, search space, physical downlink control channel PDCCH monitoring opportunity MO, physical random access channel PRACH resources, SIB1 PDCCH, message 2, message B, message 2 PDCCH, message B PDCCH, PDCCH scheduling message 3 retransmission, radio resource control RRC signaling, media access control control element MAC CE, random access response, downlink control information DCI, message 3.

[0415] Optionally, at least one of the following items in the PBCH is used to indicate part or all of the configuration information:

[0416] The demodulation reference signal DMRS of the PBCH, the scrambling sequence of the PBCH, and the payload of the PBCH;

[0417] The DMRS includes at least one of the following: a DMRS sequence, a DMRS pattern, a DMRS time domain resource, and a DMRS frequency domain resource.

[0418] Optionally, the RNTI includes: a first RNTI defined for repeated transmission of the common PDCCH, and the first RNTI is used to scramble downlink control information DCI related to the common PDCCH;

[0419] The first RNTI is generated in at least one of the following ways:

[0420] Based on random access radio network temporary identifier RA-RNTI and offset generation;

[0421] Generate based on system information radio network temporary identifier SI-RNTI and offset;

[0422] Generated based on temporary cell radio network temporary identifier TC-RNTI and offset;

[0423] Generated based on a paging radio network temporary identifier P-RNTI and an offset;

[0424] Generating based on message B Radio Network Temporary Identifier message B-RNTI and offset;

[0425] The offset is associated with configuration information of repeated transmission of the common PDCCH.

[0426] Optionally, the CORESET configuration table includes a first CORESET configuration table, the first CORESET configuration table is a CORESET resource configuration table for a type 0 PDCCH search space set, and different resource configurations in the first CORESET configuration table correspond to respective configuration parameters of common PDCCH repeated transmission; or, the CORESET configuration table includes a second CORESET configuration table, the second CORESET configuration table is a CORESET resource configuration table defined for the common PDCCH repeated transmission, and different indexes in the second CORESET configuration table correspond to respective configuration parameters of common PDCCH repeated transmission; wherein the configuration parameters of the common PDCCH repeated transmission are at least part of the parameters included in the configuration information of the common PDCCH repeated transmission;

[0427] or,

[0428] The monitoring timing table of the CSS includes a monitoring timing table of a first CSS, which is a PDCCH monitoring timing table for a type 0 PDCCH search space set, and the parameters of different PDCCH monitoring timings in the monitoring timing table of the first CSS correspond to the configuration parameters of the respective common PDCCH repeated transmissions; or, the monitoring timing table of the CSS includes a monitoring timing table of a second CSS, which is a monitoring timing table of the CSS defined for the common PDCCH repeated transmissions, and different indexes in the monitoring timing table of the second CSS correspond to the configuration parameters of the respective common PDCCH repeated transmissions; wherein, the configuration parameters of the common PDCCH repeated transmissions are at least part of the parameters contained in the configuration information of the common PDCCH repeated transmissions.

[0429] Optionally, the number of resources existing in the downlink channel receiving window is associated with some or all parameters in the configuration information, and the number of resources includes at least one of the following: the number of CORESETs, the number of search spaces, and the number of PDCCH MOs;

[0430] or,

[0431] The transmission resource for repeated transmission of the common PDCCH is located within the downlink channel receiving window;

[0432] or,

[0433] The number of resources existing in the downlink channel transmission period is associated with part or all of the configuration information, and the number of resources includes at least one of the following: the number of CORESETs, the number of search spaces, and the number of PDCCH MOs;

[0434] or,

[0435] The transmission resource for repeated transmission of the common PDCCH is located within the downlink channel transmission period.

[0436] Optionally, the downlink channel receiving window includes at least one of the following:

[0437] A window configured for repeated transmission of the common PDCCH, a reception window of a downlink channel defined in a protocol, and a window determined based on downlink channel transmission parameters;

[0438] or,

[0439] The downlink channel receiving period includes at least one of the following:

[0440] The period configured for repeated transmission of the common PDCCH, the reception period of the downlink channel defined in the protocol, and the period determined based on the downlink channel transmission parameters.

[0441] Optionally, the repeated transmission of the common PDCCH satisfies at least one of the following:

[0442] The time domain resources of the repeated transmission of the common PDCCH in CORESET#0 do not overlap with the time domain resources of the associated synchronization signal block SSB; or, the time domain resources of the repeated transmission of the common PDCCH in CORESET#0 overlap with the time domain resources of the associated SSB;

[0443] The common PDCCH is repeatedly transmitted the same number of times in multiple SSB periods;

[0444] The common PDCCH is repeatedly transmitted the same number of times in multiple first periods, where the first period is a period in which the SSB is associated with the RO;

[0445] The common PDCCH repeated transmission is located within the downlink channel receiving window;

[0446] The common PDCCH repetitive transmission is in a downlink channel transmission period.

[0447] Optionally, the repeated transmission of the common PDCCH includes repeated transmission in the time domain, and the repeated transmission of the common PDCCH in the time domain includes at least one of the following:

[0448] Repeated transmission of the common PDCCH on different PDCCH MOs in the same search space of the same CORESET;

[0449] Repeated transmission of the common PDCCH between different search spaces of the same CORESET;

[0450] Repeated transmission of the common PDCCH between different search spaces of different CORESETs;

[0451] Repeated transmission of the common PDCCH in the same search space of different CORESETs;

[0452] or,

[0453] The repeated transmission of the common PDCCH includes repeated transmission in the frequency domain, and the repeated transmission of the common PDCCH in the frequency domain includes at least one of the following:

[0454] Repeated transmission of the common PDCCH on the same PDCCH MO of the same CORESET;

[0455] The common PDCCH is repeatedly transmitted on the same PDCCH MO of different CORESETs.

[0456] Optionally, the method further includes:

[0457] In a case where resources for repeated transmission of the common PDCCH conflict with resources for initial transmission of other common PDCCHs, the terminal abandons reception of the repeated transmission of the common PDCCH.

[0458] Optionally, the network-side device performs repeated transmission of a common PDCCH according to the configuration information, including:

[0459] The network-side device performs PDCCH retransmission according to the configuration information of the PDCCH retransmission and the timeline information of the common PDCCH retransmission, where the timeline information of the common PDCCH retransmission includes at least one of the following:

[0460] The timing relationship between the repeated transmission of the common PDCCH and the physical downlink shared channel PDSCH scheduled by the common PDCCH;

[0461] The time relationship between the common PDCCH repetitive transmission and the RAR receiving window;

[0462] The time relationship between the common PDCCH retransmission and the contention resolution timer;

[0463] The time relationship between the common PDCCH repetition transmission and the message B response window.

[0464] Optionally, the timing relationship between the repeated transmission of the common PDCCH and the PDSCH scheduled by the common PDCCH includes the following:

[0465] The time slot offset of the PDSCH scheduled by the common PDCCH is an offset relative to the time slot of the first transmission of the repeated transmission of the common PDCCH;

[0466] The time slot offset of the PDSCH scheduled by the common PDCCH is the time slot offset relative to the time slot of the last transmission of the repeated transmission of the common PDCCH;

[0467] The time slot offset of the PDSCH scheduled by the public PDCCH is the time slot offset relative to the time slot of the nth transmission of the repeated transmission of the public PDCCH, where the value of n is configured on the network side or agreed upon by the protocol;

[0468] The time slot offset of the PDSCH scheduled by the common PDCCH is an offset relative to a target time point of a receiving window associated with repeated transmission of the common PDCCH.

[0469] Optionally, the first transmission of the common PDCCH includes the following:

[0470] The public PDCCH is repeatedly transmitted for the first time on the physical time slot;

[0471] The common PDCCH is repeatedly transmitted for the first time in an available time slot;

[0472] The public PDCCH is repeatedly transmitted for the first time within the RAR receiving window;

[0473] The first transmission of the common PDCCH repetition transmission within the message B response window;

[0474] The first valid transmission of the common PDCCH repeated transmission;

[0475] or,

[0476] The last transmission of the common PDCCH repeated transmission includes the following:

[0477] The common PDCCH is repeatedly transmitted for the last time on the physical timeslot;

[0478] The common PDCCH is repeatedly transmitted in the last transmission in the available time slot;

[0479] The last transmission of the common PDCCH repetition within the RAR receiving window;

[0480] The common PDCCH repeats the last transmission within the message B response window;

[0481] The last valid transmission of the common PDCCH repeated transmission;

[0482] or,

[0483] The nth transmission of the common PDCCH repeated transmission includes the following:

[0484] The common PDCCH is repeatedly transmitted for the nth time on the physical time slot;

[0485] The common PDCCH is repeatedly transmitted for the nth time in the available time slot;

[0486] The common PDCCH is repeatedly transmitted for the nth time within the RAR receiving window;

[0487] The common PDCCH is repeatedly transmitted for the nth time within the message B response window;

[0488] The nth valid transmission of the common PDCCH repeated transmission.

[0489] Optionally, the time relationship between the common PDCCH repetitive transmission and the RAR receiving window includes the following:

[0490] The public PDCCH repeated transmission allows crossing the RAR receiving window, and the public PDCCH repeated transmission does not allow crossing the RAR receiving window;

[0491] or,

[0492] The time relationship between the common PDCCH retransmission and the contention resolution timer includes the following:

[0493] The common PDCCH repeated transmission is allowed to cross the contention resolution timer, and the common PDCCH repeated transmission is not allowed to cross the contention resolution timer;

[0494] or,

[0495] The time relationship between the common PDCCH retransmission and the message B response window includes the following:

[0496] The common PDCCH repetitive transmission allows crossing the message B response window, and the common PDCCH repetitive transmission does not allow crossing the message B response window.

[0497] Optionally, the RAR receiving window includes: a RAR receiving window that can be used for repeated transmission of the public PDCCH; or a RAR receiving window obtained by adding an offset to a RAR receiving window that cannot be used for repeated transmission of the public PDCCH;

[0498] or,

[0499] The message B response window includes:

[0500] A message B response window that can be used for repeated transmission of a common PDCCH; or a message B response window obtained by adding an offset to a message B response window that cannot be used for repeated transmission of the common PDCCH;

[0501] or,

[0502] The contention resolution timer includes:

[0503] A contention resolution timer defined for common PDCCH repetitive transmission may be used; or a contention resolution timer obtained by adding an offset to a contention resolution timer that is not used for the common PDCCH repetitive transmission.

[0504] Optionally, the starting time of the RAR receiving window includes:

[0505] The first symbol of the CORESET that earliest meets the target condition in the first resource;

[0506] The first resource includes:

[0507] A resource located after the last symbol occupied by the PRACH and separated from the last symbol occupied by the PRACH by at least one symbol; or

[0508] The resource located after the last symbol occupied by the PRACH and separated from the last symbol occupied by the PRACH by a distance greater than or equal to the target time, where the target time is equal to: at least one symbol + T TA +k mac , T TA Indicates the duration of timing advance, k mac Indicates the scheduling offset supported by the non-terrestrial network (NTN) for enhancing the timing relationship of the media access control element (MAC) and the CE.

[0509] Optionally, the start time of the contention resolution timer includes: the first time after the transmission of message 3 is completed, or the interval between the start time of the contention resolution timer and the transmission end time of message 3 is equal to or greater than the round-trip time RTT;

[0510] The first moment includes at least one of the following:

[0511] The first symbol of the next time slot after the transmission of message 3 is completed;

[0512] The first symbol of the earliest CORESET after the transmission of message 3 is completed;

[0513] The first symbol of the CORESET that earliest meets the target condition in the second resource;

[0514] The second resource includes:

[0515] After the transmission of message 3 is completed, and the resources are separated from the transmission of message 3 by at least one symbol.

[0516] Optionally, the start time of the message B response window includes at least one of the following:

[0517] The first symbol of the CORESET where the first transmission of the common PDCCH repeated transmission is located;

[0518] The first symbol of the CORESET where the last transmission of the common PDCCH repetition occurs;

[0519] The first symbol of the CORESET where the i-th transmission of the common PDCCH is repeated, where the value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH;

[0520] The first symbol of the earliest CORESET in the third resource;

[0521] The first symbol of the CORESET that earliest meets the target condition in the third resource;

[0522] The third resource includes:

[0523] A resource located after the last symbol of a physical uplink shared channel PUSCH opportunity corresponding to a PRACH and spaced at least one symbol from the last symbol of the PUSCH opportunity corresponding to the PRACH; or

[0524] The resource is located after the last symbol of the PUSCH opportunity corresponding to the PRACH and the interval between the last symbol of the PUSCH opportunity corresponding to the PRACH is greater than or equal to the target time, and the target time is equal to: at least one symbol + T TA +k mac , T TA Indicates the duration of timing advance, k mac Indicates the scheduling offset supported by the non-terrestrial network (NTN) for enhancing the timing relationship between the media access control element (MAC) and the CE.

[0525] Optionally, the CORESET that meets the target conditions includes:

[0526] The CORESET where the i-th transmission of the repeated transmission of the public PDCCH is located, the value of i is equal to or greater than 1, and is less than or equal to the number of repetitions of the public PDCCH.

[0527] Optionally, also include:

[0528] When any of the following conditions is met, the common PDCCH repeated transmission is deactivated:

[0529] The terminal sends message 3;

[0530] The terminal receives a successful RAR;

[0531] RAR receiving window ends;

[0532] The maximum allowed RAR window ends;

[0533] The contention resolution timer times out;

[0534] Message 4: Message 4 was decoded successfully.

[0535] Message B is decoded successfully;

[0536] Deactivate the network-side configuration.

[0537] Optionally, when the i-th transmission of the common PDCCH repeated transmission and the PDSCH scheduled by the common PDCCH are transmitted in the same time slot, the relationship between the starting symbol of the PDSCH scheduled by the common PDCCH and the common PDCCH repeated transmission includes at least one of the following:

[0538] There is an interval of N symbols between the starting symbol of the PDSCH scheduled by the common PDCCH and the starting symbol of the i-th transmission of the repeated transmission of the common PDCCH;

[0539] There is an interval of N symbols between the starting symbol of the PDSCH scheduled by the common PDCCH and the i-th transmission symbol of the repeated transmission of the common PDCCH;

[0540] The value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH, and N is greater than or equal to 0.

[0541] It should be noted that this embodiment is an implementation of the network side device corresponding to the embodiment shown in Figure 2. Its specific implementation can refer to the relevant description of the embodiment shown in Figure 2. In order to avoid repeated description, this embodiment will not be repeated.

[0542] The following describes the method provided in the embodiments of the present application through multiple examples:

[0543] Example 1:

[0544] In this embodiment, the repetition information of the common PDCCH repetition transmission (Common PDCCH repetition) includes one or more of the following:

[0545] Common PDCCH repetition function (indicates whether repetition is supported or requested);

[0546] The number of repetitions of Common PDCCH repetition;

[0547] Common PDCCH repetition index;

[0548] Common PDCCH repetition pattern; for example: supporting PDCCH repetition between CORESETs, with different PDCCH repetitions in different CORESETs occupying the same CCE positions or PDCCH candidate positions, or varying in a certain pattern; another example: supporting PDCCH repetition within a CORESET, with different PDCCH repetitions in the same CORESET occupying the same CCE positions or PDCCH candidate positions, or varying in a certain pattern;

[0549] Whether Common PDCCH repetition is based on available slots or physical slots;

[0550] Activation or deactivation of Common PDCCH repetition;

[0551] Whether Common PDCCH repetition can exceed the RAR window;

[0552] Whether Common PDCCH repetition can exceed the contention resolution timer;

[0553] Whether Common PDCCH repetition can exceed the MsgB-response window.

[0554] In some embodiments, the repetition information of the Common PDCCH repetition is indicated in one or more of the following ways:

[0555] Implicit or explicit indication via SSB;

[0556] Implicit or explicit indication via MIB;

[0557] Implicit or explicit indication via PBCH;

[0558] Indicated by SIB information, wherein the SIB information includes SIB1 or other OSI;

[0559] Indicated by defining a new Repetition-RNTI;

[0560] Indicated by a table of modified or newly created CORESET#0 configurations;

[0561] Indicated by a modified or newly created table of Type 0-PDCCH CSS monitoring opportunities;

[0562] Determined by window / period;

[0563] Indicated by configuring specific CORESET resources, such as PDCCH transmitted through specific CORESET resources requires repetition;

[0564] Indicated by configuring a specific SearchSpace, such as when PDCCH transmitted through a specific SearchSpace resource requires repetition;

[0565] Indicated by configuring a specific PDCCH MO;

[0566] Indicated by specific PRACH resources. For example, when the network configures PRACH resources that allow the terminal to request common PDCCH repetition or configures PRACH resources that allow the terminal to report the ability to receive PDCCH repetition, it indicates that the network supports the common PDCCH repetition function.

[0567] Indicated by SIB1 PDCCH;

[0568] Indicated by Msg2 / MsgB (Msg2 / MsgB PDSCH);

[0569] Indicated by Msg2 / MsgB PDCCH;

[0570] Indicated by the PDCCH that schedules the retransmission of Msg3.

[0571] In some embodiments, the repetition information of the Common PDCCH repetition is implicitly or explicitly indicated in the MIB and includes one or more of the following:

[0572] The above repeated information is implicitly indicated by some bits in the existing fields in the MIB, for example: SSB The value of (subcarrier offset value between SSB and common resource block grid) is used to implicitly indicate the above repetition information, such as defining k SSB The values ​​or groups of correspond to different numbers of repetitions, such as k SSB When the value is 0 to 1, it means that the common PDCCH repeated transmission is not supported, such as k SSB When the value of is 2 to 3, it indicates that the common PDCCH repeated transmission is supported, and the number of repetitions of the common PDCCH repeated transmission is 2, such as k SSB When the value of is 4 to 5, it indicates that the common PDCCH repeated transmission is supported, and the number of repetitions of the common PDCCH repeated transmission is 4, etc.

[0573] Alternatively, the configuration information is explicitly carried in the MIB information; the configuration information is explicitly carried in the MIB information, for example, by utilizing reserved bits in the MIB.

[0574] In some embodiments, the repetition information of the Common PDCCH repetition is implicitly or explicitly indicated in the PBCH and includes one or more of the following:

[0575] The DMRS sequence of the PBCH is used for indication. The generation of the DMRS sequence is related to the repetition information of the Common PDCCH repetition. For example, the parameters used for initializing the DMRS sequence include the number of Common PDCCH repetitions.

[0576] The scrambling sequence of the PBCH is used for indication. The generation of the scrambling sequence is related to the repetition information of the Common PDCCH repetition. For example, the parameters used for initializing the scrambling sequence include the number of repetitions of the Common PDCCH repetition.

[0577] Explicitly carried in the PBCH payload, for example, explicitly indicating the number of Common PDCCH repetitions in the PBCH layer 1 (L1) payload.

[0578] In some embodiments, the repetition information of the Common PDCCH repetition indicated in the SIB includes one or more of the following:

[0579] The SIB carries one or more bits of signaling indicating Common PDCCH Repetition related information;

[0580] An indication of the repetition information of Common PDCCH repetition is added to the PDCCH common configuration (PDCCH-configCommon) signaling.

[0581] In some embodiments, the repetition information of the Common PDCCH repetition is indicated by defining a new repetition RNTI (Repetition-RNTI), and the Repetition-RNTI is used to scramble the related DCI. The generation of the Repetition-RNTI includes one or more of the following:

[0582] Based on RA-RNTI+offset;

[0583] Based on SI-RNTI+offset;

[0584] Based on TC-RNTI+offset;

[0585] Based on P-RNTI+offset;

[0586] Based on MSGB-RNTI+offset;

[0587] The offset is related to the repetition information of the Common PDCCH repetition. For example, different values / value ranges of the offset correspond to different functions / repetition times of the Common PDCCH repetition.

[0588] In some embodiments, the repetition information of Common PDCCH repetition is indicated by a modified or newly created table configured by CORESET#0 or a table of monitoring opportunities of Type 0-PDCCH CSS, including one or more of the following:

[0589] By adding a new column to the table of CORESET#0 configuration or the table of monitoring timing of Type 0-PDCCH CSS in the related technology indicated by PDCCH configuration (PDCCH-config) SIB1;

[0590] By adding a column to the first CORESET configuration table indicated by the 4-bit MSB in PDCCH-config SIB1 to indicate whether the common PDCCH is repeatedly transmitted, the number of repetitions, the repetition index or the repetition pattern, etc., as shown in Table 1 in the above embodiment;

[0591] Alternatively, several columns may be added to the relevant table indicated by the 4-bit LSB (search space #0 (SearchSpaceZero)) in PDCCH-configSIB1 to indicate whether to perform repeated transmission, the number of repetitions, the repetition index or the pattern of repeated transmission, as specifically shown in Table 2 in the above embodiment.

[0592] By defining a new table of CORESET#0 configuration and a table of Type 0-PDCCH CSS monitoring timing, the new table is used to determine the specific time domain resources / frequency domain resources / CORESET / SearchSpace / PDCCH MO that supports PDCCH repetition. The new table can be based on the conditions defined in the protocol (such as all or part of the conditions corresponding to Table 1) and combined with the new conditions to indicate or determine. The new condition can be a specific k SSBThe value of , or a specific system frame number, or a spare bit in the MIB. For example, for the table configured for CORESET#0, the conditions defined in the protocol may be the {SSB, PDCCH} subcarrier spacing combination and the minimum bandwidth; for the table of monitoring opportunities for Type0-PDCCH CSS, the conditions in the related art are the multiplexing pattern and frequency band of SSB and CORESET#0.

[0593] In some embodiments, the repetition information of the Common PDCCH repetition is determined based on at least a window / period, wherein the determining of the repetition information of the Common PDCCH repetition based on the window / period includes at least one of the following:

[0594] There are as many PDCCH repetitions as there are CORESETs or searchSpaces or PDCCH MOs in the above window / period;

[0595] The above window / period is used to determine the actual transmission resource / pattern of the PDCCH repetition, for example, to drop the PDCCH repetition that is not within the window / period.

[0596] The window / period may be at least one of the following:

[0597] The new window configured by the network (including the window start time / offset and / or window size and / or window end time or window period);

[0598] Reuse windows / periods defined by other protocols, such as RAR window, contention resolution timer, MsgB-response window, SSB to RO association period, SSB period, SIB1 period, SearchSpace period, etc.

[0599] A window determined based on protocol-defined parameters, for example, based on the SSB period and the relationship between SSB and CORESET0, or the starting time of the window is the position of the first CORESET#0 after the SSB transmission, and the size of the window is the SSB period, or the starting time of the window is the position of the first CORESET#0 after the SSB transmission, and the end time of the window is the position of the last CORESET#0 before the next SSB is sent.

[0600] In some embodiments, the repetition method indicated in the above embodiments includes intra-slot repetition or inter-slot repetition.

[0601] For intra-slot repetition, all public PDCCH transmissions are completed within a single time slot. In combination with the newly added columns in Table 1 in the above embodiment, the first symbol index indicates the starting symbol, and the number of symbols indicates the number of symbols occupied by each transmission. Furthermore, a single transmission cannot span multiple slots.

[0602] For example: First symbol index = 0, Number of Symbols = 3, then PDCCH repetition index 0 is on symbols 0 / 1 / 2; PDCCH repetition index 1 is on symbols 3 / 4 / 5; PDCCH repetition index 2 is on symbols 6 / 7 / 8; PDCCH repetition index 3 is on symbols 9 / 10 / 11; since the remaining two symbols are less than the Number of Symbols 3, there is no PDCCH repetition index 4.

[0603] For another example, for inter-slot repetition, each transmission is completed within one time slot. In combination with the newly added columns in Table 1 in the above embodiment, each time slot uses the same First Symbol and Number of Symbols, as indicated in the table. The repetition number determines the number of consecutive time slots used for repeated common PDCCH transmissions.

[0604] In some embodiments, the resources determined by the above-mentioned Common PDCCH repetition mechanism meet the multiplexing mode of SSB and CORESET#0.

[0605] For multiplexing mode 1 or 2 of SSB and CORESET#0, the CORESET#0 resources where SSB and PDCCH repetition are located cannot overlap in the time domain, that is, the time domain resources of PDCCH repetition must avoid the symbol position where the corresponding SSB is located.

[0606] For multiplexing mode 3 of SSB and CORESET#0, the CORESET#0 resources where SSB and PDCCH repetition are located must be at the same time in the time domain.

[0607] The above-mentioned Common PDCCH repetition generally refers to SIB1 PDCCH repetition, but does not exclude the repetition of other Common PDCCHs.

[0608] In some embodiments, the transmission of the Common PDCCH repetition needs to meet one or more of the following rules:

[0609] The number of common PDCCH repetitions must be an integer multiple of an SSB period.

[0610] The number of common PDCCH repetitions must be an integer multiple of an SSB to RO association period.

[0611] The transmission of the common PDCCH repetition must be within a certain window / period. For example, transmission that is not within the window / period is discarded.

[0612] The above-mentioned window / period can be at least one of RAR window, contention resolution timer, MsgB-response window, SSB to RO association period, SSB period, SIB1 period, SearchSpace period, etc.

[0613] In some embodiments, the Common PDCCH repetition may be a time-domain PDCCH repetition or a frequency-domain PDCCH repetition.

[0614] The time domain repetition may be at least one of the following:

[0615] Repetition on different PDCCH MOs in the same Searchspace of the same CORESET;

[0616] Repetition between different searchspaces of the same or different CORESETs;

[0617] Repetition within the same searchspace of different CORESETs.

[0618] The frequency domain repetition may be at least one of the following:

[0619] Repetition on the same PDCCH MO of the same CORESET;

[0620] Repetition on the same PDCCH MO of different CORESETs;

[0621] The same PDCCH MO may be located in the same search space or in different search spaces. For example, different transmissions are multiple copies of the CORESET resources at one moment.

[0622] In some embodiments, if the CORESET resources of a repeated transmission of a Common PDCCH conflict with the CORESET resources of a first transmission corresponding to another Common PDCCH, the transmission is abandoned, and the number of repetitions is increased by 1 or not increased by 1.

[0623] In some embodiments, the above Common PDCCH repetition indication method may not be valid for all Common PDCCHs. For example, the SIB1 PDCCH repetition transmission indication only supports explicit or implicit indication in the SSB, PBCH, or MIB, while the Msg4 PDCCH repetition transmission indication can support any of the above methods.

[0624] In some embodiments, the granularity / combination indicated by the repetition information of the Common PDCCH repetition includes one or more of the following:

[0625] Each Common PDCCH will have a corresponding repetition information indication, that is, the repetition information of each Common PDCCH repetition is independently indicated. For example, there are indications of repetition information for SIB1 PDCCH retransmission, repetition information for OSIPDCCH retransmission, repetition information for Msg2 / 4 / B PDCCH retransmission, repetition information for Paging PDCCH retransmission, and repetition information for PDCCH retransmission for scheduling Msg3 retransmission, etc.

[0626] All Common PDCCHs correspond to only one type of repetition information indication, that is, the repetition information of different Common PDCCH repetitions is uniformly indicated. For example, only the repetition information of common PDCCH repetition transmission needs to be indicated once to indicate the repetition information of repetition transmission of multiple common PDCCH channels (such as SIB1 PDCCH, OSI PDCCH, Msg2 / 4 / B PDCCH, Paging PDCCH, and PDCCH scheduling Msg3 retransmission). For example, only the repetition information of common PDCCH repetition transmission needs to be indicated once to indicate the repetition information of repetition transmission of multiple common PDCCH channels (such as SIB1 PDCCH, OSI PDCCH, Msg2 / 4 / B PDCCH, Paging PDCCH, and PDCCH scheduling Msg3 retransmission).

[0627] In some embodiments, activation / deactivation of Common PDCCH repetition transmission may include one or more of the following:

[0628] Activate / deactivate via RRC, such as system messages, configure activation / deactivation;

[0629] Activate / deactivate via MAC CE message;

[0630] Successful RAR message activation / deactivation through RAR (RAR in four-step random access, or return RAR in four-step random access); for example, RAR is used to indicate whether the subsequent Msg4 PDCCH repetition is supported;

[0631] Activate / deactivate through DCI messages; for example, through the PDCCH indication of scheduling SIB1, and whether the subsequent RAR PDCCH, Msg4 PDCCH, and paging PDCCH support repetition;

[0632] Deactivate after the terminal sends Msg3;

[0633] After receiving the successful RAR, the terminal is deactivated.

[0634] In some embodiments, the MIB or SIB information may be an NTN specific MIB / SIB or a common MIB / SIB.

[0635] Example 2:

[0636] This embodiment mainly describes the timing relationship of Common PDCCH repetition, which is as follows:

[0637] In some embodiments, the timing relationship between the Common PDCCH repetition and its scheduled PDSCH includes at least one of the following:

[0638] The slot offset of the PDSCH scheduled by Common PDCCH is relative to the slot where the first transmission of PDCCH repetition is located;

[0639] The slot offset of the PDSCH scheduled by Common PDCCH is relative to the slot where the last transmission of PDCCH repetition is located;

[0640] The slot offset of the PDSCH scheduled by the Common PDCCH is relative to the slot where the Nth transmission of the PDCCH repetition is located.

[0641] The above N may be configured by the network or predetermined.

[0642] The first transmission / last transmission / Nth transmission of the above-mentioned public PDCCH repetition includes at least one of the following:

[0643] Transmission on physical time slots;

[0644] Transmission on available time slots;

[0645] Efficient transmission within the RAR window;

[0646] Must be a valid transfer.

[0647] If the time slot offset value K0 = 0, it means that the PDSCH and a certain transmission of the PDCCH that schedules the PDSCH are transmitted in the same slot.

[0648] At this time, the relationship between the starting symbol of the PDSCH and the Common PDCCH includes one or more of the following:

[0649] The starting symbol of the PDSCH and the starting symbol of the Common PDCCH are separated by N symbols, where N>=0;

[0650] The start symbol of the PDSCH and the last symbol of the Common PDCCH are separated by N symbols, where N>=0.

[0651] The time slot offset of the PDSCH scheduled by the Common PDCCH is referenced to a certain time point of the RAR / MsgB response window. For example, the reference time slot is the first time slot of the RAR / MsgB response window.

[0652] In some embodiments, if the Common PDCCH repetition is Msg2 PDCCH repetition, the relationship between the Msg2 PDCCH repetition and the RAR window includes at least one of the following:

[0653] Msg2 PDCCH repetitions can be sent across RAR windows, for example, as long as the first repetition (first transmission) of Msg2 PDCCH is within the RAR window;

[0654] Msg2 PDCCH repetition cannot be sent across the RAR window, including one or more of the following methods:

[0655] For PDCCHs that cannot find all repetition resources within the RAR window, those PDCCH resources are not used for PDCCH repetition transmission;

[0656] The terminal does not expect Msg2 PDCCH to exceed the RAR window;

[0657] The terminal only monitors the portion of transmission within the RAR window and discards transmission beyond the RAR window.

[0658] A new RAR-repetition window is defined for Msg2 PDCCH repetition transmission. Further, the definition of the RAR-repetition window includes one or more of the following:

[0659] The above-mentioned RAR-repetition window is used to replace the RAR window;

[0660] The above RAR-repetition window takes effect after the RAR window times out;

[0661] The duration of the RAR-repetition window is related to Common PDCCH repetition information (e.g., the number of repetitions). For example, the actual RAR window length is the configured RAR window multiplied by the number of Msg2 repetitions, provided that the total length does not exceed the maximum allowed RAR window length (the maximum allowed RAR window length by the protocol is 10ms). If the product reaches or exceeds the maximum allowed RAR window length, the RAR window length becomes the maximum allowed RAR window length.

[0662] The RAR window is extended by N time based on the RAR window in the related art. The N time can be configured by the network or predefined or determined by other factors such as the number of Msg2 repetitions. The unit can be symbol, slot, millisecond, etc. For example, the N time here is an offset.

[0663] For example, if the terminal has not received Msg2 before the N time period expires, the terminal will consider that Msg2 reception has failed.

[0664] For example, PDCCH repetitions exceeding N time duration are discarded.

[0665] The starting time of the RAR window satisfies one or more of the following conditions:

[0666] At least one symbol after the last symbol of the PRACH (or at least one symbol plus T TA +k mac , see the definition in the above embodiment for the specific definition);

[0667] The first symbol of the CORESET where the i-th transmission of the Msg2 PDCCH repetition occurs. In particular, the i-th transmission may be the first transmission.

[0668] For example, define the RAR window start time as at least one symbol after the last symbol of the corresponding PRACH (or at least one symbol plus T TA +k mac , for the specific definition, refer to the definition in the above embodiment); the earliest CORESET containing the first repetition of Msg2 PDCCH after

[0669] The aforementioned extension of the RAR window by N duration based on the related art also includes that the total duration after the extension (RAR_window_length plus N duration) cannot exceed M duration. If the total duration exceeds M duration, it is considered to be M duration. Specifically, M duration can be 10ms or other network-predefined value.

[0670] In some embodiments, if the Common PDCCH repetition is Msg4 PDCCH repetition, the relationship between Msg4 PDCCH repetition and contention resolution timer includes at least one of the following:

[0671] Msg4 PDCCH repetitions can be sent across contention resolution timers, for example, as long as the first repetition (first transmission) of Msg4 PDCCH is within the contention resolution timer;

[0672] Msg4 PDCCH repetition cannot be sent across the contention resolution timer, for example, including one or more of the following methods:

[0673] If all transmission resources for Msg4 PDCCH repetition cannot be found within the contention resolution timer, the PDCCH resources outside the contention resolution timer are not used for PDCCH repetition transmission;

[0674] The terminal does not expect the Msg4 PDCCH repetition resource to exceed the contention resolution timer;

[0675] The terminal only receives the portion of transmission within the monitor contention resolution timer and discards the transmission that exceeds the contention resolution timer.

[0676] A new timer is defined for Msg4 PDCCH repetition transmission. Further, the definition of the timer includes one or more of the following:

[0677] This timer is used to replace the contention resolution timer;

[0678] This timer takes effect after the contention resolution timer expires;

[0679] The duration of this timer is related to Common PDCCH repetition-related information (e.g., the number of repetitions). For example, the actual contention resolution timer length is the configured contention resolution timer multiplied by the number of Msg4PDCCH repetitions, provided that the total length does not exceed the maximum allowed contention resolution timer length. If the product reaches or exceeds the maximum allowed contention resolution timer length, the contention resolution timer length becomes the maximum allowed contention resolution timer length.

[0680] The contention resolution timer of the Msg4 PDCCH repetition is extended by N time based on the contention resolution timer defined in the protocol. The N time can be configured by the network, predefined, or determined by other factors such as the number of Msg4 repetitions. The unit can be symbol, time slot, or millisecond. For example, the N time is one time slot offset.

[0681] In addition, if the terminal has not received Msg4 before the N time period expires, the terminal will consider that the conflict resolution has failed. For example, the terminal will discard the PDCCH repetition that exceeds the N time period.

[0682] The start time of the contention resolution timer can be at least one of the following:

[0683] The first symbol after the end of the associated Msg3 transmission (including all Msg3 repetitions if Msg3 repetitions are supported) (or for NTN, the first symbol plus the RTT between the terminal and the network-side device);

[0684] The time X after the associated Msg3 transmission (including all Msg3 repetitions, if Msg3 repetitions are supported) ends. The time X can be at least one of the following:

[0685] The first symbol of the next time slot;

[0686] The first symbol of the slot where the earliest CORESET is located;

[0687] The first symbol of the earliest CORESET that meets the target condition after at least one symbol.

[0688] The target condition is the first symbol of the CORESET containing the i-th transmission of the Msg4 PDCCH repetition. Here, i can be network-configured or pre-defined. In particular, the i-th transmission can be the first transmission. For example, if i is 1, the start time of the contention resolution timer is defined as the first symbol of the earliest CORESET containing the first Msg4 PDCCH repetition, at least one symbol after the end of the associated Msg3 transmission (including all Msg3 repetitions, if supported) (or, for NTN, the first symbol plus the UE-gNB RTT).

[0689] For another example, in the NTN scenario, the interval between the end of the associated Msg3 transmission (including all Msg3 repetitions, if supported) and the start of the contention resolution timer must be at least equal to or greater than the RTT between the terminal and the network device. If the interval is less than the RTT between the terminal and the network device, the start of the contention resolution timer is the end of the associated Msg3 transmission (including all Msg3 repetitions, if supported) plus the UE-gNB RTT.

[0690] In some embodiments, if the Common PDCCH repetition is an MsgB repetition, the relationship between the MsgB PDCCH repetition and the MsgB-response window includes at least one of the following:

[0691] MsgB PDCCH repetitions can be sent across the MsgB-response window. For example, as long as the first repetition (first transmission) of the MsgB PDCCH is within the MsgB-response window,

[0692] MsgB PDCCH repetition cannot be sent across the MsgB-response window, including one or more of the following methods:

[0693] If all transmission resources for MsgB PDCCH repetition cannot be found within the MsgB-response window, the PDCCH resources outside the MsgB-response window will not be used for PDCCH repetition transmission;

[0694] The terminal does not expect the MsgB PDCCH to exceed the MsgB-response window;

[0695] The terminal only monitors the repetitions within the MsgB-response window and discards the repetitions that exceed the MsgB-response window.

[0696] Alternatively, a new window is defined for MsgB PDCCH repetition transmission. Further, the definition of the new window includes one or more of the following:

[0697] The new window is used to replace the MsgB-response window;

[0698] The new window takes effect after the MsgB-response window times out;

[0699] The duration of the new window is related to Common PDCCH repetition-related information (e.g., the number of transmissions). For example, the actual MsgB response window length is the configured MsgB response window multiplied by the number of MsgB repetitions, provided that the total length does not exceed the maximum allowed MsgB response window length (currently 40ms). If the product reaches or exceeds the maximum allowed MsgB response window length, the MsgB response window length becomes the maximum allowed MsgB response window length.

[0700] Alternatively, the MsgB-response window of the MsgB PDCCH repetition is increased by N, based on the MsgB-response window defined in the protocol. N can be configured by the network, predefined, or determined by other factors such as the number of Msg4 repetitions, and its unit can be symbols, time slots, or milliseconds.

[0701] For example, if the terminal has not received MsgB after the N time period expires, it will fall back to retransmit MsgA.

[0702] Another example is discarding PDCCH repetitions that have lasted for more than N time periods.

[0703] The starting time of the MsgB-response window may be at least one of the following:

[0704] The first symbol of the CORESET where the first repetition of MsgB PDCCH repetition is located;

[0705] The first symbol of the CORESET where the last repetition of MsgB PDCCH repetition is located;

[0706] The first symbol of the CORESET where the i-th transmission of MsgB PDCCH repetition is located;

[0707] At least one symbol after the last symbol of the PUSCH occasion corresponding to the PRACH (or at least one symbol plus T TA +k mac , see the above embodiment for specific definition);

[0708] At least one symbol after the last symbol of the PUSCH occasion corresponding to the PRACH (or at least one symbol plus T TA +k mac , for specific definition, see the above embodiment) the first symbol of the earliest CORESET that meets the target condition;

[0709] The target condition is to meet the first symbol of the CORESET where the i-th repetition of MsgB PDCCH repetition is located. In particular, the i-th repetition can be the first or the last repetition. For example, the starting time of the MsgB-response window is defined as: at least one symbol after the last symbol of the PUSCH transmission opportunity corresponding to the PRACH (or at least one symbol plus T TA +k mac) after the earliest one containing the first symbol of the CORESET of the first repetition of MsgB PDCCH. The PRACH refers to the MsgAPRACH part, and the corresponding PUSCH refers to the MsgAPUSCH part.

[0710] In some embodiments, deactivation of Common PDCCH repetition transmission may include one or more of the following:

[0711] Deactivation occurs after the UE sends Msg3;

[0712] When the UE receives the success RAR, it is deactivated;

[0713] RAR window deactivation;

[0714] The maximum allowed RAR window is deactivated;

[0715] Deactivated by network configuration;

[0716] Deactivate after the Contention resolution timer times out;

[0717] Deactivate after Msg4 / MsgB is successfully decoded.

[0718] The embodiments of the present application can be applied to the enhancement of Common PDCCH in NTN scenarios, can also be applied to the enhancement of Common PDCCH in TN networks, and can be applied to all enhancements of Common PDCCH before the terminal enters the RRC connected state.

[0719] The embodiments of the present application solve the Common PDCCH coverage problem in certain scenarios by configuring repeated transmission of the common PDCCH, thereby ensuring the success rate of random access and improving the overall coverage of the network.

[0720] The method for processing PDCCH repeated transmission provided in the embodiment of the present application can be executed by a device for processing PDCCH repeated transmission. In the embodiment of the present application, the device for processing PDCCH repeated transmission provided in the embodiment of the present application is described by taking the method for processing PDCCH repeated transmission performed by the device for processing PDCCH repeated transmission as an example.

[0721] Please refer to FIG. 4 , which is a structural diagram of a device for processing PDCCH repeated transmission provided in an embodiment of the present application. As shown in FIG. 4 , the device 400 for processing PDCCH repeated transmission includes:

[0722] An acquisition module 401 is configured to acquire configuration information for repeated transmission of a common PDCCH;

[0723] A receiving module 402 is configured to receive repeated transmissions of a common PDCCH according to the configuration information;

[0724] The public PDCCH includes at least one of the following:

[0725] System information block SIB1 PDCCH, OSI PDCCH, message 2 PDCCH, message 4 PDCCH, message BPDCCH, paging PDCCH, and PDCCH scheduling message 3 retransmission.

[0726] Optionally, the configuration information includes at least one of the following parameters:

[0727] The function of repeated transmission of the common PDCCH;

[0728] The number of repetitions of the common PDCCH retransmission;

[0729] The index of the common PDCCH repeated transmission;

[0730] Resource information of repeated transmission of the common PDCCH;

[0731] Activation information of the common PDCCH repeated transmission, where the activation information indicates activation or deactivation of the common PDCCH repeated transmission;

[0732] The repetition mode of the common PDCCH repeated transmission.

[0733] Optionally, the resource information for repeated transmission of the common PDCCH includes at least one of the following:

[0734] A pattern of repeated transmission of the common PDCCH, wherein the pattern is used to indicate a resource position occupied by repeated transmission of the common PDCCH;

[0735] Instruction information for instructing the common PDCCH to be repeatedly transmitted based on available time slots;

[0736] Indication information used to instruct the common PDCCH to be repeatedly transmitted based on the physical time slot.

[0737] Optionally, the repetition mode of the common PDCCH repeated transmission includes at least one of the following:

[0738] Based on repeated transmission within a time slot;

[0739] Based on repeated transmission between time slots.

[0740] Optionally, the acquisition module 401 is configured to determine configuration information for repeated transmission of the common PDCCH based on indication information, where the indication information includes at least one of the following:

[0741] Synchronization signal block SSB, master information block MIB, physical broadcast channel PBCH, system information block SIB, radio network temporary identifier RNTI, control resource set CORESET configuration table, common search space CSS monitoring opportunity table, downlink channel receiving window, downlink channel transmission period, CORESET resources, search space, physical downlink control channel PDCCH monitoring opportunity MO, physical random access channel PRACH resources, SIB1 PDCCH, message 2, message B, message 2 PDCCH, message B PDCCH, PDCCH scheduling message 3 retransmission, radio resource control RRC signaling, media access control control element MAC CE, random access response, downlink control information DCI, message 3.

[0742] Optionally, the acquisition module 401 is used to determine at least part of the parameters in the configuration information of the repeated transmission of the public PDCCH based on at least one of the demodulation reference signal DMRS sequence of the PBCH, the DMRS pattern of the PBCH, the DMRS time domain resources of the PBCH, the DMRS frequency domain resources of the PBCH, the scrambling sequence of the PBCH, and the payload of the PBCH.

[0743] Optionally, the RNTI includes: a first RNTI defined for repeated transmission of the common PDCCH, and the first RNTI is used to scramble downlink control information DCI related to the common PDCCH;

[0744] The first RNTI is generated in at least one of the following ways:

[0745] Based on random access radio network temporary identifier RA-RNTI and offset generation;

[0746] Generate based on system information radio network temporary identifier SI-RNTI and offset;

[0747] Generated based on temporary cell radio network temporary identifier TC-RNTI and offset;

[0748] Generated based on a paging radio network temporary identifier P-RNTI and an offset;

[0749] Generating based on message B Radio Network Temporary Identifier message B-RNTI and offset;

[0750] The offset is associated with configuration information of repeated transmission of the common PDCCH.

[0751] Optionally, the CORESET configuration table includes a first CORESET configuration table, the first CORESET configuration table is a CORESET resource configuration table for a type 0 PDCCH search space set, and different resource configurations in the first CORESET configuration table correspond to respective configuration parameters of common PDCCH repeated transmission; or, the CORESET configuration table includes a second CORESET configuration table, the second CORESET configuration table is a CORESET resource configuration table defined for the common PDCCH repeated transmission, and different indexes in the second CORESET configuration table correspond to respective configuration parameters of common PDCCH repeated transmission; wherein the configuration parameters of the common PDCCH repeated transmission are at least part of the parameters included in the configuration information of the common PDCCH repeated transmission;

[0752] or,

[0753] The monitoring timing table of the CSS includes a monitoring timing table of a first CSS, which is a PDCCH monitoring timing table for a type 0 PDCCH search space set, and the parameters of different PDCCH monitoring timings in the monitoring timing table of the first CSS correspond to the configuration parameters of the respective common PDCCH repeated transmissions; or, the monitoring timing table of the CSS includes a monitoring timing table of a second CSS, which is a monitoring timing table of the CSS defined for the common PDCCH repeated transmissions, and different indexes in the monitoring timing table of the second CSS correspond to the configuration parameters of the respective common PDCCH repeated transmissions; wherein, the configuration parameters of the common PDCCH repeated transmissions are at least part of the parameters contained in the configuration information of the common PDCCH repeated transmissions.

[0754] Optionally, the number of resources existing in the downlink channel receiving window is associated with some or all parameters in the configuration information, and the number of resources includes at least one of the following: the number of CORESETs, the number of search spaces, and the number of PDCCH MOs;

[0755] or,

[0756] The transmission resource for repeated transmission of the common PDCCH is located within the downlink channel receiving window;

[0757] or,

[0758] The number of resources existing in the downlink channel transmission period is associated with part or all of the configuration information, and the number of resources includes at least one of the following: the number of CORESETs, the number of search spaces, and the number of PDCCH MOs;

[0759] or,

[0760] The transmission resource for repeated transmission of the common PDCCH is located within the downlink channel transmission period.

[0761] Optionally, the downlink channel receiving window includes at least one of the following:

[0762] A window configured for repeated transmission of the common PDCCH, a reception window of a downlink channel defined in a protocol, and a window determined based on downlink channel transmission parameters;

[0763] or,

[0764] The downlink channel receiving period includes at least one of the following:

[0765] The period configured for repeated transmission of the common PDCCH, the reception period of the downlink channel defined in the protocol, and the period determined based on the downlink channel transmission parameters.

[0766] Optionally, the repeated transmission of the common PDCCH satisfies at least one of the following:

[0767] The time domain resources of the repeated transmission of the common PDCCH in CORESET#0 do not overlap with the time domain resources of the associated synchronization signal block SSB; or, the time domain resources of the repeated transmission of the common PDCCH in CORESET#0 overlap with the time domain resources of the associated SSB;

[0768] The common PDCCH is repeatedly transmitted the same number of times in multiple SSB periods;

[0769] The common PDCCH is repeatedly transmitted the same number of times in multiple first periods, where the first period is a period in which the SSB is associated with the RO;

[0770] The common PDCCH repeated transmission is located within the downlink channel receiving window;

[0771] The common PDCCH repetitive transmission is in a downlink channel transmission period.

[0772] Optionally, the repeated transmission of the common PDCCH includes repeated transmission in the time domain, and the repeated transmission of the common PDCCH in the time domain includes at least one of the following:

[0773] Repeated transmission of the common PDCCH on different PDCCH MOs in the same search space of the same CORESET;

[0774] Repeated transmission of the common PDCCH between different search spaces of the same CORESET;

[0775] Repeated transmission of the common PDCCH between different search spaces of different CORESETs;

[0776] Repeated transmission of the common PDCCH in the same search space of different CORESETs;

[0777] or,

[0778] The repeated transmission of the common PDCCH includes repeated transmission in the frequency domain, and the repeated transmission of the common PDCCH in the frequency domain includes at least one of the following:

[0779] Repeated transmission of the common PDCCH on the same PDCCH MO of the same CORESET;

[0780] The common PDCCH is repeatedly transmitted on the same PDCCH MO of different CORESETs.

[0781] Optionally, the device further includes:

[0782] The abandonment module is configured to abandon the reception of the repeated transmission of the common PDCCH if the resources of the repeated transmission of the common PDCCH conflict with the resources of the first transmission of other common PDCCHs.

[0783] Optionally, the execution module 402 is configured to perform PDCCH retransmission according to the configuration information of the PDCCH retransmission and the timeline information of the common PDCCH retransmission, where the timeline information of the common PDCCH retransmission includes at least one of the following:

[0784] The timing relationship between the repeated transmission of the common PDCCH and the physical downlink shared channel PDSCH scheduled by the common PDCCH;

[0785] The time relationship between the common PDCCH repetitive transmission and the RAR receiving window;

[0786] The time relationship between the common PDCCH retransmission and the contention resolution timer;

[0787] The time relationship between the common PDCCH repetition transmission and the message B response window.

[0788] Optionally, the timing relationship between the repeated transmission of the common PDCCH and the PDSCH scheduled by the common PDCCH includes the following:

[0789] The time slot offset of the PDSCH scheduled by the common PDCCH is an offset relative to the time slot of the first transmission of the repeated transmission of the common PDCCH;

[0790] The time slot offset of the PDSCH scheduled by the common PDCCH is the time slot offset relative to the time slot of the last transmission of the repeated transmission of the common PDCCH;

[0791] The time slot offset of the PDSCH scheduled by the public PDCCH is the time slot offset relative to the time slot of the nth transmission of the repeated transmission of the public PDCCH, where the value of n is configured on the network side or agreed upon by the protocol;

[0792] The time slot offset of the PDSCH scheduled by the common PDCCH is an offset relative to a target time point of a receiving window associated with repeated transmission of the common PDCCH.

[0793] Optionally, the first transmission of the common PDCCH includes the following:

[0794] The public PDCCH is repeatedly transmitted for the first time on the physical time slot;

[0795] The common PDCCH is repeatedly transmitted for the first time in an available time slot;

[0796] The public PDCCH is repeatedly transmitted for the first time within the RAR receiving window;

[0797] The first transmission of the common PDCCH repetition transmission within the message B response window;

[0798] The first valid transmission of the common PDCCH repeated transmission;

[0799] or,

[0800] The last transmission of the common PDCCH repeated transmission includes the following:

[0801] The common PDCCH is repeatedly transmitted for the last time on the physical time slot;

[0802] The common PDCCH is repeatedly transmitted in the last transmission in the available time slot;

[0803] The last transmission of the common PDCCH repetition within the RAR receiving window;

[0804] The common PDCCH repeats the last transmission within the message B response window;

[0805] The last valid transmission of the common PDCCH repeated transmission;

[0806] or,

[0807] The nth transmission of the common PDCCH repeated transmission includes the following:

[0808] The common PDCCH is repeatedly transmitted for the nth time on the physical time slot;

[0809] The common PDCCH is repeatedly transmitted for the nth time in the available time slot;

[0810] The common PDCCH is repeatedly transmitted for the nth time within the RAR receiving window;

[0811] The common PDCCH is repeatedly transmitted for the nth time within the message B response window;

[0812] The nth valid transmission of the common PDCCH repeated transmission.

[0813] Optionally, the time relationship between the common PDCCH repetitive transmission and the RAR receiving window includes the following:

[0814] The public PDCCH repeated transmission allows crossing the RAR receiving window, and the public PDCCH repeated transmission does not allow crossing the RAR receiving window;

[0815] or,

[0816] The time relationship between the common PDCCH retransmission and the contention resolution timer includes the following:

[0817] The common PDCCH repeated transmission is allowed to cross the contention resolution timer, and the common PDCCH repeated transmission is not allowed to cross the contention resolution timer;

[0818] or,

[0819] The time relationship between the common PDCCH retransmission and the message B response window includes the following:

[0820] The common PDCCH repetitive transmission allows crossing the message B response window, and the common PDCCH repetitive transmission does not allow crossing the message B response window.

[0821] Optionally, the RAR receiving window includes: a RAR receiving window that can be used for repeated transmission of the public PDCCH; or a RAR receiving window obtained by adding an offset to a RAR receiving window that cannot be used for repeated transmission of the public PDCCH;

[0822] or,

[0823] The message B response window includes:

[0824] A message B response window that can be used for repeated transmission of a common PDCCH; or a message B response window obtained by adding an offset to a message B response window that cannot be used for repeated transmission of the common PDCCH;

[0825] or,

[0826] The contention resolution timer includes:

[0827] A contention resolution timer defined for common PDCCH repetitive transmission may be used; or a contention resolution timer obtained by adding an offset to a contention resolution timer that is not used for the common PDCCH repetitive transmission.

[0828] Optionally, the starting time of the RAR receiving window includes:

[0829] The first symbol of the CORESET that earliest meets the target condition in the first resource;

[0830] The first resource includes:

[0831] A resource located after the last symbol occupied by the PRACH and separated from the last symbol occupied by the PRACH by at least one symbol; or

[0832] The resource located after the last symbol occupied by the PRACH and separated from the last symbol occupied by the PRACH by a distance greater than or equal to the target time, where the target time is equal to: at least one symbol + T TA +k mac , T TA Indicates the duration of timing advance, k mac Indicates the scheduling offset supported by the non-terrestrial network (NTN) for enhancing the timing relationship of the media access control element (MAC) and the CE.

[0833] Optionally, the start time of the contention resolution timer includes: the first time after the transmission of message 3 is completed, or the interval between the start time of the contention resolution timer and the transmission end time of message 3 is equal to or greater than the round-trip time RTT;

[0834] The first moment includes at least one of the following:

[0835] The first symbol of the next time slot after the transmission of message 3 is completed;

[0836] The first symbol of the earliest CORESET after the transmission of message 3 is completed;

[0837] The first symbol of the CORESET that earliest meets the target condition in the second resource;

[0838] The second resource includes:

[0839] After the transmission of message 3 is completed, and the resources are separated from the transmission of message 3 by at least one symbol.

[0840] Optionally, the start time of the message B response window includes at least one of the following:

[0841] The first symbol of the CORESET where the first transmission of the common PDCCH repeated transmission is located;

[0842] The first symbol of the CORESET where the last transmission of the common PDCCH repetition occurs;

[0843] The first symbol of the CORESET where the i-th transmission of the common PDCCH is repeated, where the value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH;

[0844] The first symbol of the earliest CORESET in the third resource;

[0845] The first symbol of the CORESET that earliest meets the target condition in the third resource;

[0846] The third resource includes:

[0847] A resource located after the last symbol of a physical uplink shared channel PUSCH opportunity corresponding to a PRACH and spaced at least one symbol from the last symbol of the PUSCH opportunity corresponding to the PRACH; or

[0848] The resource is located after the last symbol of the PUSCH opportunity corresponding to the PRACH and the interval between the last symbol of the PUSCH opportunity corresponding to the PRACH is greater than or equal to the target time, and the target time is equal to: at least one symbol + T TA +k mac , T TA Indicates the duration of timing advance, k mac Indicates the scheduling offset supported by the non-terrestrial network (NTN) for enhancing the timing relationship between the media access control element (MAC) and the CE.

[0849] Optionally, the CORESET that meets the target conditions includes:

[0850] The CORESET where the i-th transmission of the repeated transmission of the public PDCCH is located, the value of i is equal to or greater than 1, and is less than or equal to the number of repetitions of the public PDCCH.

[0851] Optionally, also include:

[0852] A deactivation module is configured to deactivate the common PDCCH repeated transmission when any of the following conditions is met:

[0853] The terminal sends message 3;

[0854] The terminal receives a successful RAR;

[0855] RAR receiving window ends;

[0856] The maximum allowed RAR window ends;

[0857] The contention resolution timer times out;

[0858] Message 4: Message 4 was decoded successfully.

[0859] Message B is decoded successfully;

[0860] Deactivate the network-side configuration.

[0861] Optionally, when the i-th transmission of the common PDCCH repeated transmission and the PDSCH scheduled by the common PDCCH are transmitted in the same time slot, the relationship between the starting symbol of the PDSCH scheduled by the common PDCCH and the common PDCCH repeated transmission includes at least one of the following:

[0862] There is an interval of N symbols between the starting symbol of the PDSCH scheduled by the common PDCCH and the starting symbol of the i-th transmission of the repeated transmission of the common PDCCH;

[0863] There is an interval of N symbols between the starting symbol of the PDSCH scheduled by the common PDCCH and the i-th transmission symbol of the repeated transmission of the common PDCCH;

[0864] The value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH, and N is greater than or equal to 0.

[0865] The above-mentioned PDCCH repeated transmission processing device can improve the coverage performance of the network.

[0866] In the embodiments of the present application, the apparatus for processing repeated PDCCH transmissions may be an electronic device, such as an electronic device having an operating system, or a component in the electronic device, such as an integrated circuit or chip. For example, the electronic device may be a terminal, or may be another device other than a terminal. For example, the terminal may include, but is not limited to, the types of terminals listed in the embodiments of the present application, and the other devices may be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0867] The processing device for repeated PDCCH transmission provided in the embodiment of the present application can implement the various processes implemented in the method embodiment shown in Figure 2 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0868] Please refer to FIG5 , which is a structural diagram of a device for processing PDCCH repeated transmission provided in an embodiment of the present application. As shown in FIG5 , the device 500 for processing PDCCH repeated transmission includes:

[0869] The sending module 501 is used to send configuration information of common PDCCH repeated transmission to the terminal;

[0870] An execution module 502 is configured to execute repeated transmission of a common PDCCH according to the configuration information;

[0871] The public PDCCH includes at least one of the following:

[0872] System information block SIB1 PDCCH, OSI PDCCH, message 2 PDCCH, message 4 PDCCH, message B PDCCH, paging PDCCH, PDCCH scheduling message 3 retransmission.

[0873] Optionally, the configuration information includes at least one of the following parameters:

[0874] The function of repeated transmission of the common PDCCH;

[0875] The number of repetitions of the common PDCCH retransmission;

[0876] The index of the common PDCCH repeated transmission;

[0877] Resource information of repeated transmission of the common PDCCH;

[0878] Activation information of the common PDCCH repeated transmission, where the activation information indicates activation or deactivation of the common PDCCH repeated transmission;

[0879] The repetition mode of the common PDCCH repeated transmission.

[0880] Optionally, the resource information for repeated transmission of the common PDCCH includes at least one of the following:

[0881] A pattern of repeated transmission of the common PDCCH, wherein the pattern is used to indicate a resource position occupied by repeated transmission of the common PDCCH;

[0882] Instruction information for instructing the common PDCCH to be repeatedly transmitted based on available time slots;

[0883] Indication information used to instruct the common PDCCH to be repeatedly transmitted based on the physical time slot.

[0884] Optionally, the repetition mode of the common PDCCH repeated transmission includes at least one of the following:

[0885] Based on repeated transmission within a time slot;

[0886] Based on repeated transmission between time slots.

[0887] Optionally, the sending module 501 is configured to send indication information to the terminal, where the indication information is used to determine configuration information for repeated transmission of the common PDCCH, and the indication information includes at least one of the following:

[0888] Synchronization signal block SSB, master information block MIB, physical broadcast channel PBCH, system information block SIB, radio network temporary identifier RNTI, control resource set CORESET configuration table, common search space CSS monitoring opportunity table, downlink channel receiving window, downlink channel transmission period, CORESET resources, search space, physical downlink control channel PDCCH monitoring opportunity MO, physical random access channel PRACH resources, SIB1 PDCCH, message 2, message B, message 2 PDCCH, message B PDCCH, PDCCH scheduling message 3 retransmission, radio resource control RRC signaling, media access control control element MAC CE, random access response, downlink control information DCI, message 3.

[0889] Optionally, at least one of the following items in the PBCH is used to indicate part or all of the configuration information:

[0890] The demodulation reference signal DMRS of the PBCH, the scrambling sequence of the PBCH, and the payload of the PBCH;

[0891] The DMRS includes at least one of the following: a DMRS sequence, a DMRS pattern, a DMRS time domain resource, and a DMRS frequency domain resource.

[0892] Optionally, the RNTI includes: a first RNTI defined for repeated transmission of the common PDCCH, and the first RNTI is used to scramble downlink control information DCI related to the common PDCCH;

[0893] The first RNTI is generated in at least one of the following ways:

[0894] Based on random access radio network temporary identifier RA-RNTI and offset generation;

[0895] Generate based on system information radio network temporary identifier SI-RNTI and offset;

[0896] Generated based on temporary cell radio network temporary identifier TC-RNTI and offset;

[0897] Generated based on a paging radio network temporary identifier P-RNTI and an offset;

[0898] Generating based on message B Radio Network Temporary Identifier message B-RNTI and offset;

[0899] The offset is associated with configuration information of repeated transmission of the common PDCCH.

[0900] Optionally, the CORESET configuration table includes a first CORESET configuration table, the first CORESET configuration table is a CORESET resource configuration table for a type 0 PDCCH search space set, and different resource configurations in the first CORESET configuration table correspond to respective configuration parameters of common PDCCH repeated transmission; or, the CORESET configuration table includes a second CORESET configuration table, the second CORESET configuration table is a CORESET resource configuration table defined for the common PDCCH repeated transmission, and different indexes in the second CORESET configuration table correspond to respective configuration parameters of common PDCCH repeated transmission; wherein the configuration parameters of the common PDCCH repeated transmission are at least part of the parameters included in the configuration information of the common PDCCH repeated transmission;

[0901] or,

[0902] The monitoring timing table of the CSS includes a monitoring timing table of a first CSS, which is a PDCCH monitoring timing table for a type 0 PDCCH search space set, and the parameters of different PDCCH monitoring timings in the monitoring timing table of the first CSS correspond to the configuration parameters of the respective common PDCCH repeated transmissions; or, the monitoring timing table of the CSS includes a monitoring timing table of a second CSS, which is a monitoring timing table of the CSS defined for the common PDCCH repeated transmissions, and different indexes in the monitoring timing table of the second CSS correspond to the configuration parameters of the respective common PDCCH repeated transmissions; wherein, the configuration parameters of the common PDCCH repeated transmissions are at least part of the parameters contained in the configuration information of the common PDCCH repeated transmissions.

[0903] Optionally, the number of resources existing in the downlink channel receiving window is associated with some or all parameters in the configuration information, and the number of resources includes at least one of the following: the number of CORESETs, the number of search spaces, and the number of PDCCH MOs;

[0904] or,

[0905] The transmission resource for repeated transmission of the common PDCCH is located within the downlink channel receiving window;

[0906] or,

[0907] The number of resources existing in the downlink channel transmission period is associated with part or all of the configuration information, and the number of resources includes at least one of the following: the number of CORESETs, the number of search spaces, and the number of PDCCH MOs;

[0908] or,

[0909] The transmission resource for repeated transmission of the common PDCCH is located within the downlink channel transmission period.

[0910] Optionally, the downlink channel receiving window includes at least one of the following:

[0911] A window configured for repeated transmission of the common PDCCH, a reception window of a downlink channel defined in a protocol, and a window determined based on downlink channel transmission parameters;

[0912] or,

[0913] The downlink channel receiving period includes at least one of the following:

[0914] The period configured for repeated transmission of the common PDCCH, the reception period of the downlink channel defined in the protocol, and the period determined based on the downlink channel transmission parameters.

[0915] Optionally, the repeated transmission of the common PDCCH satisfies at least one of the following:

[0916] The time domain resources of the repeated transmission of the common PDCCH in CORESET#0 do not overlap with the time domain resources of the associated synchronization signal block SSB; or, the time domain resources of the repeated transmission of the common PDCCH in CORESET#0 overlap with the time domain resources of the associated SSB;

[0917] The common PDCCH is repeatedly transmitted the same number of times in multiple SSB periods;

[0918] The common PDCCH is repeatedly transmitted the same number of times in multiple first periods, where the first period is a period in which the SSB is associated with the RO;

[0919] The common PDCCH repeated transmission is located within the downlink channel receiving window;

[0920] The common PDCCH repetitive transmission is in a downlink channel transmission period.

[0921] Optionally, the repeated transmission of the common PDCCH includes repeated transmission in the time domain, and the repeated transmission of the common PDCCH in the time domain includes at least one of the following:

[0922] Repeated transmission of the common PDCCH on different PDCCH MOs in the same search space of the same CORESET;

[0923] Repeated transmission of the common PDCCH between different search spaces of the same CORESET;

[0924] Repeated transmission of the common PDCCH between different search spaces of different CORESETs;

[0925] Repeated transmission of the common PDCCH in the same search space of different CORESETs;

[0926] or,

[0927] The repeated transmission of the common PDCCH includes repeated transmission in the frequency domain, and the repeated transmission of the common PDCCH in the frequency domain includes at least one of the following:

[0928] Repeated transmission of the common PDCCH on the same PDCCH MO of the same CORESET;

[0929] The common PDCCH is repeatedly transmitted on the same PDCCH MO of different CORESETs.

[0930] Optionally, the device further includes:

[0931] The abandonment module is configured to abandon the repeated transmission of the common PDCCH if the resources for the repeated transmission of the common PDCCH conflict with the resources for the first transmission of other common PDCCHs.

[0932] Optionally, the execution module 502 is configured to perform PDCCH retransmission according to the configuration information of the PDCCH retransmission and the timeline information of the common PDCCH retransmission, where the timeline information of the common PDCCH retransmission includes at least one of the following:

[0933] The timing relationship between the repeated transmission of the common PDCCH and the physical downlink shared channel PDSCH scheduled by the common PDCCH;

[0934] The time relationship between the common PDCCH repetitive transmission and the RAR receiving window;

[0935] The time relationship between the common PDCCH retransmission and the contention resolution timer;

[0936] The time relationship between the common PDCCH repetition transmission and the message B response window.

[0937] Optionally, the timing relationship between the repeated transmission of the common PDCCH and the PDSCH scheduled by the common PDCCH includes the following:

[0938] The time slot offset of the PDSCH scheduled by the common PDCCH is an offset relative to the time slot of the first transmission of the repeated transmission of the common PDCCH;

[0939] The time slot offset of the PDSCH scheduled by the common PDCCH is the time slot offset relative to the time slot of the last transmission of the repeated transmission of the common PDCCH;

[0940] The time slot offset of the PDSCH scheduled by the public PDCCH is the time slot offset relative to the time slot of the nth transmission of the repeated transmission of the public PDCCH, where the value of n is configured on the network side or agreed upon by the protocol;

[0941] The time slot offset of the PDSCH scheduled by the common PDCCH is an offset relative to a target time point of a receiving window associated with repeated transmission of the common PDCCH.

[0942] Optionally, the first transmission of the common PDCCH includes the following:

[0943] The public PDCCH is repeatedly transmitted for the first time on the physical time slot;

[0944] The common PDCCH is repeatedly transmitted for the first time in an available time slot;

[0945] The public PDCCH is repeatedly transmitted for the first time within the RAR receiving window;

[0946] The first transmission of the common PDCCH repetition transmission within the message B response window;

[0947] The first valid transmission of the common PDCCH repeated transmission;

[0948] or,

[0949] The last transmission of the common PDCCH repeated transmission includes the following:

[0950] The common PDCCH is repeatedly transmitted for the last time on the physical timeslot;

[0951] The common PDCCH is repeatedly transmitted in the last transmission in the available time slot;

[0952] The last transmission of the common PDCCH repetition within the RAR receiving window;

[0953] The common PDCCH repeats the last transmission within the message B response window;

[0954] The last valid transmission of the common PDCCH repeated transmission;

[0955] or,

[0956] The nth transmission of the common PDCCH repeated transmission includes the following:

[0957] The common PDCCH is repeatedly transmitted for the nth time on the physical time slot;

[0958] The common PDCCH is repeatedly transmitted for the nth time in the available time slot;

[0959] The common PDCCH is repeatedly transmitted for the nth time within the RAR receiving window;

[0960] The common PDCCH is repeatedly transmitted for the nth time within the message B response window;

[0961] The nth valid transmission of the common PDCCH repeated transmission.

[0962] Optionally, the time relationship between the common PDCCH repetitive transmission and the RAR receiving window includes the following:

[0963] The public PDCCH repeated transmission allows crossing the RAR receiving window, and the public PDCCH repeated transmission does not allow crossing the RAR receiving window;

[0964] or,

[0965] The time relationship between the common PDCCH retransmission and the contention resolution timer includes the following:

[0966] The common PDCCH repeated transmission is allowed to cross the contention resolution timer, and the common PDCCH repeated transmission is not allowed to cross the contention resolution timer;

[0967] or,

[0968] The time relationship between the common PDCCH retransmission and the message B response window includes the following:

[0969] The common PDCCH repetitive transmission allows crossing the message B response window, and the common PDCCH repetitive transmission does not allow crossing the message B response window.

[0970] Optionally, the RAR receiving window includes: a RAR receiving window that can be used for repeated transmission of the public PDCCH; or a RAR receiving window obtained by adding an offset to a RAR receiving window that cannot be used for repeated transmission of the public PDCCH;

[0971] or,

[0972] The message B response window includes:

[0973] A message B response window that can be used for repeated transmission of a common PDCCH; or a message B response window obtained by adding an offset to a message B response window that cannot be used for repeated transmission of the common PDCCH;

[0974] or,

[0975] The contention resolution timer includes:

[0976] A contention resolution timer defined for common PDCCH repetitive transmission may be used; or a contention resolution timer obtained by adding an offset to a contention resolution timer that is not used for the common PDCCH repetitive transmission.

[0977] Optionally, the starting time of the RAR receiving window includes:

[0978] The first symbol of the CORESET that earliest meets the target condition in the first resource;

[0979] The first resource includes:

[0980] A resource located after the last symbol occupied by the PRACH and separated from the last symbol occupied by the PRACH by at least one symbol; or

[0981] The resource located after the last symbol occupied by the PRACH and separated from the last symbol occupied by the PRACH by a distance greater than or equal to the target time, where the target time is equal to: at least one symbol + T TA +k mac , T TA Indicates the duration of timing advance, k mac Indicates the scheduling offset supported by the non-terrestrial network (NTN) for enhancing the timing relationship of the media access control element (MAC) and the CE.

[0982] Optionally, the start time of the contention resolution timer includes: the first time after the transmission of message 3 is completed, or the interval between the start time of the contention resolution timer and the transmission end time of message 3 is equal to or greater than the round-trip time RTT;

[0983] The first moment includes at least one of the following:

[0984] The first symbol of the next time slot after the transmission of message 3 is completed;

[0985] The first symbol of the earliest CORESET after the transmission of message 3 is completed;

[0986] The first symbol of the CORESET that earliest meets the target condition in the second resource;

[0987] The second resource includes:

[0988] After the transmission of message 3 is completed, and the resources are separated from the transmission of message 3 by at least one symbol.

[0989] Optionally, the start time of the message B response window includes at least one of the following:

[0990] The first symbol of the CORESET where the first transmission of the common PDCCH repeated transmission is located;

[0991] The first symbol of the CORESET where the last transmission of the common PDCCH repetition occurs;

[0992] The first symbol of the CORESET where the i-th transmission of the common PDCCH is repeated, where the value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH;

[0993] The first symbol of the earliest CORESET in the third resource;

[0994] The first symbol of the CORESET that earliest meets the target condition in the third resource;

[0995] The third resource includes:

[0996] A resource located after the last symbol of a physical uplink shared channel PUSCH opportunity corresponding to a PRACH and spaced at least one symbol from the last symbol of the PUSCH opportunity corresponding to the PRACH; or

[0997] The resource is located after the last symbol of the PUSCH opportunity corresponding to the PRACH and the interval between the last symbol of the PUSCH opportunity corresponding to the PRACH is greater than or equal to the target time, and the target time is equal to: at least one symbol + T TA +k mac , T TA Indicates the duration of timing advance, k mac Indicates the scheduling offset supported by the non-terrestrial network (NTN) for enhancing the timing relationship between the media access control element (MAC) and the CE.

[0998] Optionally, the CORESET that meets the target conditions includes:

[0999] The CORESET where the i-th transmission of the repeated transmission of the public PDCCH is located, the value of i is equal to or greater than 1, and is less than or equal to the number of repetitions of the public PDCCH.

[1000] Optionally, also include:

[1001] A deactivation module is configured to deactivate the common PDCCH repeated transmission when any of the following conditions is met:

[1002] The terminal sends message 3;

[1003] The terminal receives a successful RAR;

[1004] RAR receiving window ends;

[1005] The maximum allowed RAR window ends;

[1006] The contention resolution timer times out;

[1007] Message 4: Message 4 was decoded successfully.

[1008] Message B is decoded successfully;

[1009] Deactivate the network-side configuration.

[1010] Optionally, when the i-th transmission of the common PDCCH repeated transmission and the PDSCH scheduled by the common PDCCH are transmitted in the same time slot, the relationship between the starting symbol of the PDSCH scheduled by the common PDCCH and the common PDCCH repeated transmission includes at least one of the following:

[1011] There is an interval of N symbols between the starting symbol of the PDSCH scheduled by the common PDCCH and the starting symbol of the i-th transmission of the repeated transmission of the common PDCCH;

[1012] There is a gap of N symbols between the starting symbol of the PDSCH scheduled by the common PDCCH and the i-th transmission symbol of the repeated transmission of the common PDCCH;

[1013] The value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH, and N is greater than or equal to 0.

[1014] The above-mentioned PDCCH repeated transmission processing device can improve the coverage performance of the network.

[1015] The PDCCH retransmission processing device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or a network-side device.

[1016] The processing device for repeated transmission of PDCCH provided in the embodiment of the present application can implement the various processes implemented in the method embodiment shown in Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[1017] Optionally, as shown in Figure 6, an embodiment of the present application further provides a communication device 600, including a processor 601 and a memory 602, wherein the memory 602 stores a program or instruction that can be run on the processor 601. For example, when the communication device 600 is a terminal, the program or instruction is executed by the processor 601 to implement the various steps of the embodiment of the method for processing repeated transmission of PDCCH on the terminal side, and can achieve the same technical effect. When the communication device 600 is a network side device, the program or instruction is executed by the processor 601 to implement the various steps of the embodiment of the method for processing repeated transmission of PDCCH on the network side, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[1018] An embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is used to obtain configuration information for repeated transmission of a common PDCCH; an execution module is used to receive repeated transmission of a common PDCCH according to the configuration information; wherein the common PDCCH includes at least one of the following: system information block SIB1 PDCCH, OSIPDCCH, message 2 PDCCH, message 4 PDCCH, message B PDCCH, paging PDCCH, and PDCCH for scheduling retransmission of message 3.

[1019] As shown in Figure 7, the terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709 and at least some of the components of the processor 710.

[1020] Those skilled in the art will appreciate that the terminal 700 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 710 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The communication device structure shown in FIG7 does not limit the communication device. The communication device may include more or fewer components than shown, or may combine certain components or arrange the components differently, which will not be described in detail here.

[1021] It should be understood that in an embodiment of the present application, the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042, and the graphics processor 7041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 707 includes a touch panel 7071 and at least one of other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include two parts: a touch detection device and a touch controller. Other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[1022] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 701 may transmit the data to the processor 710 for processing. Furthermore, the RF unit 701 may send uplink data to the network-side device. Typically, the RF unit 701 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[1023] The memory 709 can be used to store software programs or instructions and various data. The memory 709 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 709 may include a volatile memory or a non-volatile memory, or the memory 709 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 709 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[1024] Processor 710 may include one or more processing units. Optionally, processor 710 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 710.

[1025] The radio frequency unit 701 is configured to obtain configuration information for repeated transmission of a common PDCCH; and receive repeated transmission of the common PDCCH according to the configuration information;

[1026] The public PDCCH includes at least one of the following:

[1027] System information block SIB1 PDCCH, OSI PDCCH, message 2 PDCCH, message 4 PDCCH, message BPDCCH, paging PDCCH, and PDCCH scheduling message 3 retransmission.

[1028] Optionally, the configuration information includes at least one of the following parameters:

[1029] The function of repeated transmission of the common PDCCH;

[1030] The number of repetitions of the common PDCCH retransmission;

[1031] The index of the common PDCCH repeated transmission;

[1032] Resource information of repeated transmission of the common PDCCH;

[1033] Activation information of the common PDCCH repeated transmission, where the activation information indicates activation or deactivation of the common PDCCH repeated transmission;

[1034] The repetition mode of the common PDCCH repeated transmission.

[1035] Optionally, the resource information for repeated transmission of the common PDCCH includes at least one of the following:

[1036] A pattern of repeated transmission of the common PDCCH, wherein the pattern is used to indicate a resource position occupied by repeated transmission of the common PDCCH;

[1037] Instruction information for instructing the common PDCCH to be repeatedly transmitted based on available time slots;

[1038] Indication information used to instruct the common PDCCH to be repeatedly transmitted based on the physical time slot.

[1039] Optionally, the repetition mode of the common PDCCH repeated transmission includes at least one of the following:

[1040] Based on repeated transmission within a time slot;

[1041] Based on repeated transmission between time slots.

[1042] Optionally, the acquiring configuration information of repeated transmission of a common PDCCH includes:

[1043] Used to determine configuration information for repeated transmission of a common PDCCH based on indication information, where the indication information includes at least one of the following:

[1044] Synchronization signal block SSB, master information block MIB, physical broadcast channel PBCH, system information block SIB, radio network temporary identifier RNTI, control resource set CORESET configuration table, common search space CSS monitoring opportunity table, downlink channel receiving window, downlink channel transmission period, CORESET resources, search space, physical downlink control channel PDCCH monitoring opportunity MO, physical random access channel PRACH resources, SIB1 PDCCH, message 2, message B, message 2 PDCCH, message B PDCCH, PDCCH scheduling message 3 retransmission, radio resource control RRC signaling, media access control control element MAC CE, random access response, downlink control information DCI, message 3.

[1045] Optionally, the indication information includes the PBCH, and determining the configuration information for repeated transmission of the common PDCCH based on the indication information includes:

[1046] Determine at least some parameters in the configuration information for repeated transmission of the public PDCCH based on at least one of the demodulation reference signal DMRS sequence of the PBCH, the DMRS pattern of the PBCH, the DMRS time domain resources of the PBCH, the DMRS frequency domain resources of the PBCH, the scrambling sequence of the PBCH, and the load of the PBCH.

[1047] Optionally, the RNTI includes: a first RNTI defined for repeated transmission of the common PDCCH, and the first RNTI is used to scramble downlink control information DCI related to the common PDCCH;

[1048] The first RNTI is generated in at least one of the following ways:

[1049] Based on random access radio network temporary identifier RA-RNTI and offset generation;

[1050] Generate based on system information radio network temporary identifier SI-RNTI and offset;

[1051] Generated based on temporary cell radio network temporary identifier TC-RNTI and offset;

[1052] Generated based on a paging radio network temporary identifier P-RNTI and an offset;

[1053] Generating based on message B Radio Network Temporary Identifier message B-RNTI and offset;

[1054] The offset is associated with configuration information of repeated transmission of the common PDCCH.

[1055] Optionally, the CORESET configuration table includes a first CORESET configuration table, the first CORESET configuration table is a CORESET resource configuration table for a type 0 PDCCH search space set, and different resource configurations in the first CORESET configuration table correspond to respective configuration parameters of common PDCCH repeated transmission; or, the CORESET configuration table includes a second CORESET configuration table, the second CORESET configuration table is a CORESET resource configuration table defined for the common PDCCH repeated transmission, and different indexes in the second CORESET configuration table correspond to respective configuration parameters of common PDCCH repeated transmission; wherein the configuration parameters of the common PDCCH repeated transmission are at least part of the parameters included in the configuration information of the common PDCCH repeated transmission;

[1056] or,

[1057] The monitoring timing table of the CSS includes a monitoring timing table of a first CSS, which is a PDCCH monitoring timing table for a type 0 PDCCH search space set, and the parameters of different PDCCH monitoring timings in the monitoring timing table of the first CSS correspond to the configuration parameters of the respective common PDCCH repeated transmissions; or, the monitoring timing table of the CSS includes a monitoring timing table of a second CSS, which is a monitoring timing table of the CSS defined for the common PDCCH repeated transmissions, and different indexes in the monitoring timing table of the second CSS correspond to the configuration parameters of the respective common PDCCH repeated transmissions; wherein, the configuration parameters of the common PDCCH repeated transmissions are at least part of the parameters contained in the configuration information of the common PDCCH repeated transmissions.

[1058] Optionally, the number of resources existing in the downlink channel receiving window is associated with some or all parameters in the configuration information, and the number of resources includes at least one of the following: the number of CORESETs, the number of search spaces, and the number of PDCCH MOs;

[1059] or,

[1060] The transmission resource for repeated transmission of the common PDCCH is located within the downlink channel receiving window;

[1061] or,

[1062] The number of resources existing in the downlink channel transmission period is associated with part or all of the configuration information, and the number of resources includes at least one of the following: the number of CORESETs, the number of search spaces, and the number of PDCCH MOs;

[1063] or,

[1064] The transmission resource for repeated transmission of the common PDCCH is located within the downlink channel transmission period.

[1065] Optionally, the downlink channel receiving window includes at least one of the following:

[1066] A window configured for repeated transmission of the common PDCCH, a reception window of a downlink channel defined in a protocol, and a window determined based on downlink channel transmission parameters;

[1067] or,

[1068] The downlink channel receiving period includes at least one of the following:

[1069] The period configured for repeated transmission of the common PDCCH, the reception period of the downlink channel defined in the protocol, and the period determined based on the downlink channel transmission parameters.

[1070] Optionally, the repeated transmission of the common PDCCH satisfies at least one of the following:

[1071] The time domain resources of the repeated transmission of the common PDCCH in CORESET#0 do not overlap with the time domain resources of the associated synchronization signal block SSB; or, the time domain resources of the repeated transmission of the common PDCCH in CORESET#0 overlap with the time domain resources of the associated SSB;

[1072] The common PDCCH is repeatedly transmitted the same number of times in multiple SSB periods;

[1073] The common PDCCH is repeatedly transmitted the same number of times in multiple first periods, where the first period is a period in which the SSB is associated with the RO;

[1074] The common PDCCH repeated transmission is located within the downlink channel receiving window;

[1075] The common PDCCH repetitive transmission is in a downlink channel transmission period.

[1076] Optionally, the repeated transmission of the common PDCCH includes repeated transmission in the time domain, and the repeated transmission of the common PDCCH in the time domain includes at least one of the following:

[1077] Repeated transmission of the common PDCCH on different PDCCH MOs in the same search space of the same CORESET;

[1078] Repeated transmission of the common PDCCH between different search spaces of the same CORESET;

[1079] Repeated transmission of the common PDCCH between different search spaces of different CORESETs;

[1080] Repeated transmission of the common PDCCH in the same search space of different CORESETs;

[1081] or,

[1082] The repeated transmission of the common PDCCH includes repeated transmission in the frequency domain, and the repeated transmission of the common PDCCH in the frequency domain includes at least one of the following:

[1083] Repeated transmission of the common PDCCH on the same PDCCH MO of the same CORESET;

[1084] The common PDCCH is repeatedly transmitted on the same PDCCH MO of different CORESETs.

[1085] Optionally, the processor 710 is configured to abandon reception of the repeated transmission of the common PDCCH if resources of the repeated transmission of the common PDCCH conflict with resources of the first transmission of other common PDCCHs.

[1086] Optionally, the receiving repeated transmission of a common PDCCH according to the configuration information includes:

[1087] configured to receive PDCCH repetition transmission according to the configuration information of the PDCCH repetition transmission and according to the timeline information of the common PDCCH repetition transmission, where the timeline information of the common PDCCH repetition transmission includes at least one of the following:

[1088] The timing relationship between the repeated transmission of the common PDCCH and the physical downlink shared channel PDSCH scheduled by the common PDCCH;

[1089] The time relationship between the common PDCCH repetitive transmission and the RAR receiving window;

[1090] The time relationship between the common PDCCH retransmission and the contention resolution timer;

[1091] The time relationship between the common PDCCH repetition transmission and the message B response window.

[1092] Optionally, the timing relationship between the repeated transmission of the common PDCCH and the PDSCH scheduled by the common PDCCH includes the following:

[1093] The time slot offset of the PDSCH scheduled by the common PDCCH is an offset relative to the time slot of the first transmission of the repeated transmission of the common PDCCH;

[1094] The time slot offset of the PDSCH scheduled by the common PDCCH is the time slot offset relative to the time slot of the last transmission of the repeated transmission of the common PDCCH;

[1095] The time slot offset of the PDSCH scheduled by the public PDCCH is the time slot offset relative to the time slot of the nth transmission of the repeated transmission of the public PDCCH, where the value of n is configured on the network side or agreed upon by the protocol;

[1096] The time slot offset of the PDSCH scheduled by the common PDCCH is an offset relative to a target time point of a receiving window associated with repeated transmission of the common PDCCH.

[1097] Optionally, the first transmission of the common PDCCH includes the following:

[1098] The public PDCCH is repeatedly transmitted for the first time on the physical time slot;

[1099] The common PDCCH is repeatedly transmitted for the first time in an available time slot;

[1100] The public PDCCH is repeatedly transmitted for the first time within the RAR receiving window;

[1101] The first transmission of the common PDCCH repetition transmission within the message B response window;

[1102] The first valid transmission of the common PDCCH repeated transmission;

[1103] or,

[1104] The last transmission of the common PDCCH repeated transmission includes the following:

[1105] The common PDCCH is repeatedly transmitted for the last time on the physical time slot;

[1106] The common PDCCH is repeatedly transmitted in the last transmission in the available time slot;

[1107] The last transmission of the common PDCCH repetition within the RAR receiving window;

[1108] The common PDCCH repeats the last transmission within the message B response window;

[1109] The last valid transmission of the common PDCCH repeated transmission;

[1110] or,

[1111] The nth transmission of the common PDCCH repeated transmission includes the following:

[1112] The common PDCCH is repeatedly transmitted for the nth time on the physical time slot;

[1113] The common PDCCH is repeatedly transmitted for the nth time in the available time slot;

[1114] The common PDCCH is repeatedly transmitted for the nth time within the RAR receiving window;

[1115] The common PDCCH is repeatedly transmitted for the nth time within the message B response window;

[1116] The nth valid transmission of the common PDCCH repeated transmission.

[1117] Optionally, the time relationship between the common PDCCH repetitive transmission and the RAR receiving window includes the following:

[1118] The public PDCCH repeated transmission allows crossing the RAR receiving window, and the public PDCCH repeated transmission does not allow crossing the RAR receiving window;

[1119] or,

[1120] The time relationship between the common PDCCH retransmission and the contention resolution timer includes the following:

[1121] The common PDCCH repeated transmission is allowed to cross the contention resolution timer, and the common PDCCH repeated transmission is not allowed to cross the contention resolution timer;

[1122] or,

[1123] The time relationship between the common PDCCH retransmission and the message B response window includes the following:

[1124] The common PDCCH repetitive transmission allows crossing the message B response window, and the common PDCCH repetitive transmission does not allow crossing the message B response window.

[1125] Optionally, the RAR receiving window includes: a RAR receiving window that can be used for repeated transmission of the public PDCCH; or a RAR receiving window obtained by adding an offset to a RAR receiving window that cannot be used for repeated transmission of the public PDCCH;

[1126] or,

[1127] The message B response window includes:

[1128] A message B response window that can be used for repeated transmission of a common PDCCH; or a message B response window obtained by adding an offset to a message B response window that cannot be used for repeated transmission of the common PDCCH;

[1129] or,

[1130] The contention resolution timer includes:

[1131] A contention resolution timer defined for common PDCCH repetitive transmission may be used; or a contention resolution timer obtained by adding an offset to a contention resolution timer that is not used for the common PDCCH repetitive transmission.

[1132] Optionally, the starting time of the RAR receiving window includes:

[1133] The first symbol of the CORESET that earliest meets the target condition in the first resource;

[1134] The first resource includes:

[1135] A resource located after the last symbol occupied by the PRACH and separated from the last symbol occupied by the PRACH by at least one symbol; or

[1136] The resource located after the last symbol occupied by the PRACH and separated from the last symbol occupied by the PRACH by a distance greater than or equal to the target time, where the target time is equal to: at least one symbol + T TA +k mac , T TA Indicates the duration of timing advance, k mac Indicates the scheduling offset supported by the non-terrestrial network (NTN) for enhancing the timing relationship of the media access control element (MAC) and the CE.

[1137] Optionally, the start time of the contention resolution timer includes: the first time after the transmission of message 3 is completed, or the interval between the start time of the contention resolution timer and the transmission end time of message 3 is equal to or greater than the round-trip time RTT;

[1138] The first moment includes at least one of the following:

[1139] The first symbol of the next time slot after the transmission of message 3 is completed;

[1140] The first symbol of the earliest CORESET after the transmission of message 3 is completed;

[1141] The first symbol of the CORESET that earliest meets the target condition in the second resource;

[1142] The second resource includes:

[1143] After the transmission of message 3 is completed, and the resources are separated from the transmission of message 3 by at least one symbol.

[1144] Optionally, the start time of the message B response window includes at least one of the following:

[1145] The first symbol of the CORESET where the first transmission of the common PDCCH repeated transmission is located;

[1146] The first symbol of the CORESET where the last transmission of the common PDCCH repetition occurs;

[1147] The first symbol of the CORESET where the i-th transmission of the common PDCCH is repeated, where the value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH;

[1148] The first symbol of the earliest CORESET in the third resource;

[1149] The first symbol of the CORESET that earliest meets the target condition in the third resource;

[1150] The third resource includes:

[1151] A resource located after the last symbol of a physical uplink shared channel PUSCH opportunity corresponding to a PRACH and spaced at least one symbol from the last symbol of the PUSCH opportunity corresponding to the PRACH; or

[1152] The resource is located after the last symbol of the PUSCH opportunity corresponding to the PRACH and the interval between the last symbol of the PUSCH opportunity corresponding to the PRACH is greater than or equal to the target time, and the target time is equal to: at least one symbol + T TA +k mac , T TA Indicates the duration of timing advance, k mac Indicates the scheduling offset supported by the non-terrestrial network (NTN) for enhancing the timing relationship between the media access control element (MAC) and the CE.

[1153] Optionally, the CORESET that meets the target conditions includes:

[1154] The CORESET where the i-th transmission of the repeated transmission of the public PDCCH is located, the value of i is equal to or greater than 1, and is less than or equal to the number of repetitions of the public PDCCH.

[1155] Optionally, the processor 710 is configured to deactivate the common PDCCH repeated transmission when any of the following conditions is met:

[1156] The terminal sends message 3;

[1157] The terminal receives a successful RAR;

[1158] RAR receiving window ends;

[1159] The maximum allowed RAR window ends;

[1160] The contention resolution timer times out;

[1161] Message 4: Message 4 was decoded successfully.

[1162] Message B is decoded successfully;

[1163] Deactivate the network-side configuration.

[1164] Optionally, when the i-th transmission of the common PDCCH repeated transmission and the PDSCH scheduled by the common PDCCH are transmitted in the same time slot, the relationship between the starting symbol of the PDSCH scheduled by the common PDCCH and the common PDCCH repeated transmission includes at least one of the following:

[1165] There is an interval of N symbols between the starting symbol of the PDSCH scheduled by the common PDCCH and the starting symbol of the i-th transmission of the repeated transmission of the common PDCCH;

[1166] There is a gap of N symbols between the starting symbol of the PDSCH scheduled by the common PDCCH and the i-th transmission symbol of the repeated transmission of the common PDCCH;

[1167] The value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH, and N is greater than or equal to 0.

[1168] The above terminals can improve the coverage performance of the network.

[1169] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above-mentioned method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[1170] An embodiment of the present application also provides a network side device, including a processor and a communication interface, wherein the communication interface or the processor is used to send indication information to the terminal or determine the time relationship information of the repeated transmission of the common PDCCH, and the indication information is used to indicate the configuration information of the repeated transmission of the common PDCCH.

[1171] As shown in Figure 8 , network-side device 800 includes an antenna 801, a radio frequency device 802, a baseband device 803, a processor 804, and a memory 805. Antenna 801 is connected to radio frequency device 802. In the uplink direction, radio frequency device 802 receives information via antenna 801 and sends the received information to baseband device 803 for processing. In the downlink direction, baseband device 803 processes the information to be transmitted and sends it to radio frequency device 802. Radio frequency device 802 processes the received information and then sends it through antenna 801.

[1172] The method executed by the radio access network device in the above embodiment may be implemented in the baseband device 803 , which includes a baseband processor.

[1173] The baseband device 803 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 8, one of which is, for example, a baseband processor, which is connected to the memory 805 through a bus interface to call the program in the memory 805 and execute the network device operations shown in the above method embodiment.

[1174] The radio access network device may further include a network interface 806, which is, for example, a common public radio interface (CPRI).

[1175] Specifically, the network side device 800 of the embodiment of the present application also includes: instructions or programs stored in the memory 805 and can be run on the processor 804. The processor 804 calls the instructions or programs in the memory 805 to execute the methods executed by each module shown in Figure 5 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[1176] The radio frequency device 802 is used to: send configuration information of repeated transmission of the common PDCCH to the terminal;

[1177] An execution module, configured to execute common PDCCH repeated transmission according to the configuration information;

[1178] The public PDCCH includes at least one of the following:

[1179] SIB1 PDCCH, OSI PDCCH, message 2 PDCCH, message 4 PDCCH, message B PDCCH, paging PDCCH, and PDCCH scheduling message 3 retransmission.

[1180] Optionally, the configuration information includes at least one of the following parameters:

[1181] The function of repeated transmission of the common PDCCH;

[1182] The number of repetitions of the common PDCCH retransmission;

[1183] The index of the common PDCCH repeated transmission;

[1184] Resource information of repeated transmission of the common PDCCH;

[1185] Activation information of the common PDCCH repeated transmission, where the activation information indicates activation or deactivation of the common PDCCH repeated transmission;

[1186] The repetition mode of the common PDCCH repeated transmission.

[1187] Optionally, the resource information for repeated transmission of the common PDCCH includes at least one of the following:

[1188] A pattern of repeated transmission of the common PDCCH, wherein the pattern is used to indicate a resource position occupied by repeated transmission of the common PDCCH;

[1189] Instruction information for instructing the common PDCCH to be repeatedly transmitted based on available time slots;

[1190] Indication information used to instruct the common PDCCH to be repeatedly transmitted based on the physical time slot.

[1191] Optionally, the repetition mode of the common PDCCH repeated transmission includes at least one of the following:

[1192] Based on repeated transmission within a time slot;

[1193] Based on repeated transmission between time slots.

[1194] Optionally, the sending the configuration information of repeated transmission of the common PDCCH to the terminal includes:

[1195] Sending indication information to the terminal, where the indication information is used to determine configuration information for repeated transmission of a common PDCCH, where the indication information includes at least one of the following:

[1196] Synchronization signal block SSB, master information block MIB, physical broadcast channel PBCH, system information block SIB, radio network temporary identifier RNTI, control resource set CORESET configuration table, common search space CSS monitoring opportunity table, downlink channel receiving window, downlink channel transmission period, CORESET resources, search space, physical downlink control channel PDCCH monitoring opportunity MO, physical random access channel PRACH resources, SIB1 PDCCH, message 2, message B, message 2 PDCCH, message B PDCCH, PDCCH scheduling message 3 retransmission, radio resource control RRC signaling, media access control control element MAC CE, random access response, downlink control information DCI, message 3.

[1197] Optionally, at least one of the following items in the PBCH is used to indicate part or all of the configuration information:

[1198] The demodulation reference signal DMRS of the PBCH, the scrambling sequence of the PBCH, and the payload of the PBCH;

[1199] The DMRS includes at least one of the following: a DMRS sequence, a DMRS pattern, a DMRS time domain resource, and a DMRS frequency domain resource.

[1200] Optionally, the RNTI includes: a first RNTI defined for repeated transmission of the common PDCCH, and the first RNTI is used to scramble downlink control information DCI related to the common PDCCH;

[1201] The first RNTI is generated in at least one of the following ways:

[1202] Based on random access radio network temporary identifier RA-RNTI and offset generation;

[1203] Generate based on system information radio network temporary identifier SI-RNTI and offset;

[1204] Generated based on temporary cell radio network temporary identifier TC-RNTI and offset;

[1205] Generated based on a paging radio network temporary identifier P-RNTI and an offset;

[1206] Generating based on message B Radio Network Temporary Identifier message B-RNTI and offset;

[1207] The offset is associated with configuration information of repeated transmission of the common PDCCH.

[1208] Optionally, the CORESET configuration table includes a first CORESET configuration table, the first CORESET configuration table is a CORESET resource configuration table for a type 0 PDCCH search space set, and different resource configurations in the first CORESET configuration table correspond to respective configuration parameters of common PDCCH repeated transmission; or, the CORESET configuration table includes a second CORESET configuration table, the second CORESET configuration table is a CORESET resource configuration table defined for the common PDCCH repeated transmission, and different indexes in the second CORESET configuration table correspond to respective configuration parameters of common PDCCH repeated transmission; wherein the configuration parameters of the common PDCCH repeated transmission are at least part of the parameters included in the configuration information of the common PDCCH repeated transmission;

[1209] or,

[1210] The monitoring timing table of the CSS includes a monitoring timing table of a first CSS, which is a PDCCH monitoring timing table for a type 0 PDCCH search space set, and the parameters of different PDCCH monitoring timings in the monitoring timing table of the first CSS correspond to the configuration parameters of the respective common PDCCH repeated transmissions; or, the monitoring timing table of the CSS includes a monitoring timing table of a second CSS, which is a monitoring timing table of the CSS defined for the common PDCCH repeated transmissions, and different indexes in the monitoring timing table of the second CSS correspond to the configuration parameters of the respective common PDCCH repeated transmissions; wherein, the configuration parameters of the common PDCCH repeated transmissions are at least part of the parameters contained in the configuration information of the common PDCCH repeated transmissions.

[1211] Optionally, the number of resources existing in the downlink channel receiving window is associated with some or all parameters in the configuration information, and the number of resources includes at least one of the following: the number of CORESETs, the number of search spaces, and the number of PDCCH MOs;

[1212] or,

[1213] The transmission resource for repeated transmission of the common PDCCH is located within the downlink channel receiving window;

[1214] or,

[1215] The number of resources existing in the downlink channel transmission period is associated with part or all of the configuration information, and the number of resources includes at least one of the following: the number of CORESETs, the number of search spaces, and the number of PDCCH MOs;

[1216] or,

[1217] The transmission resource for repeated transmission of the common PDCCH is located within the downlink channel transmission period.

[1218] Optionally, the downlink channel receiving window includes at least one of the following:

[1219] A window configured for repeated transmission of the common PDCCH, a reception window of a downlink channel defined in a protocol, and a window determined based on downlink channel transmission parameters;

[1220] or,

[1221] The downlink channel receiving period includes at least one of the following:

[1222] The period configured for repeated transmission of the common PDCCH, the reception period of the downlink channel defined in the protocol, and the period determined based on the downlink channel transmission parameters.

[1223] Optionally, the repeated transmission of the common PDCCH satisfies at least one of the following:

[1224] The time domain resources of the repeated transmission of the common PDCCH in CORESET#0 do not overlap with the time domain resources of the associated synchronization signal block SSB; or, the time domain resources of the repeated transmission of the common PDCCH in CORESET#0 overlap with the time domain resources of the associated SSB;

[1225] The common PDCCH is repeatedly transmitted the same number of times in multiple SSB periods;

[1226] The common PDCCH is repeatedly transmitted the same number of times in multiple first periods, where the first period is a period in which the SSB is associated with the RO;

[1227] The common PDCCH repeated transmission is located within the downlink channel receiving window;

[1228] The common PDCCH repetitive transmission is in a downlink channel transmission period.

[1229] Optionally, the repeated transmission of the common PDCCH includes repeated transmission in the time domain, and the repeated transmission of the common PDCCH in the time domain includes at least one of the following:

[1230] Repeated transmission of the common PDCCH on different PDCCH MOs in the same search space of the same CORESET;

[1231] Repeated transmission of the common PDCCH between different search spaces of the same CORESET;

[1232] Repeated transmission of the common PDCCH between different search spaces of different CORESETs;

[1233] Repeated transmission of the common PDCCH in the same search space of different CORESETs;

[1234] or,

[1235] The repeated transmission of the common PDCCH includes repeated transmission in the frequency domain, and the repeated transmission of the common PDCCH in the frequency domain includes at least one of the following:

[1236] Repeated transmission of the common PDCCH on the same PDCCH MO of the same CORESET;

[1237] The common PDCCH is repeatedly transmitted on the same PDCCH MO of different CORESETs.

[1238] Optionally, the processor 804 is configured to abandon the repeated transmission of the public PDCCH if the resources for the repeated transmission of the public PDCCH conflict with the resources for the first transmission of other public PDCCHs.

[1239] Optionally, performing repeated transmission of a common PDCCH according to the configuration information includes:

[1240] Perform PDCCH retransmission according to the configuration information of the PDCCH retransmission and according to the timeline information of the common PDCCH retransmission, where the timeline information of the common PDCCH retransmission includes at least one of the following:

[1241] The timing relationship between the repeated transmission of the common PDCCH and the physical downlink shared channel PDSCH scheduled by the common PDCCH;

[1242] The time relationship between the common PDCCH repetitive transmission and the RAR receiving window;

[1243] The time relationship between the common PDCCH retransmission and the contention resolution timer;

[1244] The time relationship between the common PDCCH repetition transmission and the message B response window.

[1245] Optionally, the timing relationship between the repeated transmission of the common PDCCH and the PDSCH scheduled by the common PDCCH includes the following:

[1246] The time slot offset of the PDSCH scheduled by the common PDCCH is an offset relative to the time slot of the first transmission of the repeated transmission of the common PDCCH;

[1247] The time slot offset of the PDSCH scheduled by the common PDCCH is the time slot offset relative to the time slot of the last transmission of the repeated transmission of the common PDCCH;

[1248] The time slot offset of the PDSCH scheduled by the public PDCCH is the time slot offset relative to the time slot of the nth transmission of the repeated transmission of the public PDCCH, where the value of n is configured on the network side or agreed upon by the protocol;

[1249] The time slot offset of the PDSCH scheduled by the common PDCCH is an offset relative to a target time point of a receiving window associated with repeated transmission of the common PDCCH.

[1250] Optionally, the first transmission of the common PDCCH includes the following:

[1251] The public PDCCH is repeatedly transmitted for the first time on the physical time slot;

[1252] The common PDCCH is repeatedly transmitted for the first time in an available time slot;

[1253] The public PDCCH is repeatedly transmitted for the first time within the RAR receiving window;

[1254] The first transmission of the common PDCCH repetition transmission within the message B response window;

[1255] The first valid transmission of the common PDCCH repeated transmission;

[1256] or,

[1257] The last transmission of the common PDCCH repeated transmission includes the following:

[1258] The common PDCCH is repeatedly transmitted for the last time on the physical timeslot;

[1259] The common PDCCH is repeatedly transmitted in the last transmission in the available time slot;

[1260] The last transmission of the common PDCCH repetition within the RAR receiving window;

[1261] The common PDCCH repeats the last transmission within the message B response window;

[1262] The last valid transmission of the common PDCCH repeated transmission;

[1263] or,

[1264] The nth transmission of the common PDCCH repeated transmission includes the following:

[1265] The common PDCCH is repeatedly transmitted for the nth time on the physical time slot;

[1266] The common PDCCH is repeatedly transmitted for the nth time in the available time slot;

[1267] The common PDCCH is repeatedly transmitted for the nth time within the RAR receiving window;

[1268] The common PDCCH is repeatedly transmitted for the nth time within the message B response window;

[1269] The nth valid transmission of the common PDCCH repeated transmission.

[1270] Optionally, the time relationship between the common PDCCH repetitive transmission and the RAR receiving window includes the following:

[1271] The public PDCCH repeated transmission allows crossing the RAR receiving window, and the public PDCCH repeated transmission does not allow crossing the RAR receiving window;

[1272] or,

[1273] The time relationship between the common PDCCH retransmission and the contention resolution timer includes the following:

[1274] The common PDCCH repeated transmission is allowed to cross the contention resolution timer, and the common PDCCH repeated transmission is not allowed to cross the contention resolution timer;

[1275] or,

[1276] The time relationship between the common PDCCH retransmission and the message B response window includes the following:

[1277] The common PDCCH repetitive transmission allows crossing the message B response window, and the common PDCCH repetitive transmission does not allow crossing the message B response window.

[1278] Optionally, the RAR receiving window includes: a RAR receiving window that can be used for repeated transmission of the public PDCCH; or a RAR receiving window obtained by adding an offset to a RAR receiving window that cannot be used for repeated transmission of the public PDCCH;

[1279] or,

[1280] The message B response window includes:

[1281] A message B response window that can be used for repeated transmission of a common PDCCH; or a message B response window obtained by adding an offset to a message B response window that cannot be used for repeated transmission of the common PDCCH;

[1282] or,

[1283] The contention resolution timer includes:

[1284] A contention resolution timer defined for common PDCCH repetitive transmission may be used; or a contention resolution timer obtained by adding an offset to a contention resolution timer that is not used for the common PDCCH repetitive transmission.

[1285] Optionally, the starting time of the RAR receiving window includes:

[1286] The first symbol of the CORESET that earliest meets the target condition in the first resource;

[1287] The first resource includes:

[1288] A resource located after the last symbol occupied by the PRACH and separated from the last symbol occupied by the PRACH by at least one symbol; or

[1289] The resource located after the last symbol occupied by the PRACH and separated from the last symbol occupied by the PRACH by a distance greater than or equal to the target time, where the target time is equal to: at least one symbol + T TA +k mac , T TA Indicates the duration of timing advance, k mac Indicates the scheduling offset supported by the non-terrestrial network (NTN) for enhancing the timing relationship of the media access control element (MAC) and the CE.

[1290] Optionally, the start time of the contention resolution timer includes: the first time after the transmission of message 3 is completed, or the interval between the start time of the contention resolution timer and the transmission end time of message 3 is equal to or greater than the round-trip time RTT;

[1291] The first moment includes at least one of the following:

[1292] The first symbol of the next time slot after the transmission of message 3 is completed;

[1293] The first symbol of the earliest CORESET after the transmission of message 3 is completed;

[1294] The first symbol of the CORESET that earliest meets the target condition in the second resource;

[1295] The second resource includes:

[1296] After the transmission of message 3 is completed, and the resources are separated from the transmission of message 3 by at least one symbol.

[1297] Optionally, the start time of the message B response window includes at least one of the following:

[1298] The first symbol of the CORESET where the first transmission of the common PDCCH repeated transmission is located;

[1299] The first symbol of the CORESET where the last transmission of the common PDCCH repetition occurs;

[1300] The first symbol of the CORESET where the i-th transmission of the common PDCCH is repeated, where the value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH;

[1301] The first symbol of the earliest CORESET in the third resource;

[1302] The first symbol of the CORESET that earliest meets the target condition in the third resource;

[1303] The third resource includes:

[1304] A resource located after the last symbol of a physical uplink shared channel PUSCH opportunity corresponding to a PRACH and spaced at least one symbol from the last symbol of the PUSCH opportunity corresponding to the PRACH; or

[1305] The resource is located after the last symbol of the PUSCH opportunity corresponding to the PRACH and the interval between the last symbol of the PUSCH opportunity corresponding to the PRACH is greater than or equal to the target time, and the target time is equal to: at least one symbol + T TA +k mac , T TA Indicates the duration of timing advance, k mac Indicates the scheduling offset supported by the non-terrestrial network (NTN) for enhancing the timing relationship between the media access control element (MAC) and the CE.

[1306] Optionally, the CORESET that meets the target conditions includes:

[1307] The CORESET where the i-th transmission of the repeated transmission of the public PDCCH is located, the value of i is equal to or greater than 1, and is less than or equal to the number of repetitions of the public PDCCH.

[1308] Optionally, the processor 804 is configured to deactivate the common PDCCH repeated transmission when any of the following conditions is met:

[1309] The terminal sends message 3;

[1310] The terminal receives a successful RAR;

[1311] RAR receiving window ends;

[1312] The maximum allowed RAR window ends;

[1313] The contention resolution timer times out;

[1314] Message 4: Message 4 was decoded successfully.

[1315] Message B is decoded successfully;

[1316] Deactivate the network-side configuration.

[1317] Optionally, when the i-th transmission of the common PDCCH repeated transmission and the PDSCH scheduled by the common PDCCH are transmitted in the same time slot, the relationship between the starting symbol of the PDSCH scheduled by the common PDCCH and the common PDCCH repeated transmission includes at least one of the following:

[1318] There is an interval of N symbols between the starting symbol of the PDSCH scheduled by the common PDCCH and the starting symbol of the i-th transmission of the repeated transmission of the common PDCCH;

[1319] There is a gap of N symbols between the starting symbol of the PDSCH scheduled by the common PDCCH and the i-th transmission symbol of the repeated transmission of the common PDCCH;

[1320] The value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH, and N is greater than or equal to 0.

[1321] The above network-side equipment can improve the coverage performance of the network.

[1322] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned PDCCH repeated transmission processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[1323] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[1324] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned PDCCH repeated transmission processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[1325] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[1326] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned PDCCH repeated transmission processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[1327] An embodiment of the present application also provides a wireless communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the processing method for repeated transmission of PDCCH on the terminal side provided in the embodiment of the present application, and the network side device can be used to execute the steps of the processing method for repeated transmission of PDCCH on the network side provided in the embodiment of the present application.

[1328] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[1329] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[1330] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A method for processing repeated transmission of a physical downlink control channel PDCCH, comprising: The terminal obtains configuration information of repeated transmission of the common PDCCH; The terminal receives repeated transmission of a common PDCCH according to the configuration information; The public PDCCH includes at least one of the following: System information block SIB1 PDCCH, other system information OSI PDCCH, message 2 PDCCH, message 4 PDCCH, message B PDCCH, paging PDCCH, PDCCH for scheduling message 3 retransmission.

2. The method of claim 1, wherein: The configuration information includes at least one of the following parameters: The function of repeated transmission of the common PDCCH; The number of repetitions of the common PDCCH repeated transmission; An index of the common PDCCH repeated transmission; Resource information of repeated transmission of the common PDCCH; Activation information of the common PDCCH repeated transmission, where the activation information indicates activation or deactivation of the common PDCCH repeated transmission; The repetition mode of the common PDCCH repeated transmission.

3. The method of claim 2, wherein: The resource information of the common PDCCH repeated transmission includes at least one of the following: A pattern of repeated transmission of the common PDCCH, wherein the pattern is used to indicate a resource position occupied by repeated transmission of the common PDCCH; Indication information used to instruct the common PDCCH to be repeatedly transmitted based on available time slots; Indication information used to instruct the common PDCCH to be repeatedly transmitted based on the physical time slot.

4. The method according to any one of claims 1 to 3, wherein: The terminal obtains configuration information of repeated transmission of a common PDCCH, including: The terminal determines, based on the indication information, configuration information for repeated transmission of the common PDCCH, where the indication information includes at least one of the following: Synchronization signal block SSB, master information block MIB, physical broadcast channel PBCH, system information block SIB, radio network temporary identifier RNTI, control resource set CORESET configuration table, common search space CSS monitoring time table, downlink channel receiving window, downlink channel transmission period, CORESET resources, search space, physical downlink control channel PDCCH monitoring time MO, physical random access channel PRACH resources, SIB1 PDCCH, message 2, message B, message 2 PDCCH, message B PDCCH, PDCCH scheduling message 3 retransmission, radio resource control RRC signaling, media access control control unit MAC CE, random access response, downlink control information DCI, message 3.

5. The method of claim 4, wherein: The indication information includes the PBCH, and the terminal determines, based on the indication information, configuration information for repeated transmission of the common PDCCH, including: At least some parameters in the configuration information for repeated transmission of the common PDCCH are determined based on at least one of the demodulation reference signal DMRS sequence of the PBCH, the DMRS pattern of the PBCH, the DMRS time domain resources of the PBCH, the DMRS frequency domain resources of the PBCH, the scrambling sequence of the PBCH, and the payload of the PBCH.

6. The method according to claim 4 or 5, wherein: The RNTI includes: a first RNTI defined for repeated transmission of the common PDCCH, and the first RNTI is used to scramble downlink control information DCI related to the common PDCCH; The method for generating the first RNTI includes at least one of the following: Based on random access radio network temporary identifier RA-RNTI and offset generation; Generate based on system information radio network temporary identifier SI-RNTI and offset; Generated based on temporary cell radio network temporary identifier TC-RNTI and offset; Generated based on a paging radio network temporary identifier P-RNTI and an offset; Generating based on message B Radio Network Temporary Identifier message B-RNTI and offset; The offset is associated with configuration information of repeated transmission of the common PDCCH.

7. The method according to any one of claims 4 to 6, wherein: The CORESET configuration table includes a first CORESET configuration table, the first CORESET configuration table is a CORESET resource configuration table for a type 0 PDCCH search space set, and different resource configurations in the first CORESET configuration table correspond to respective configuration parameters of common PDCCH repeated transmission; or, the CORESET configuration table includes a second CORESET configuration table, the second CORESET configuration table is a CORESET resource configuration table defined for the common PDCCH repeated transmission, and different indexes in the second CORESET configuration table correspond to respective configuration parameters of common PDCCH repeated transmission; wherein the configuration parameters of the common PDCCH repeated transmission are at least part of the parameters included in the configuration information of the common PDCCH repeated transmission; or, The monitoring timing table of the CSS includes a monitoring timing table of a first CSS, wherein the monitoring timing table of the first CSS is a PDCCH monitoring timing table for a type 0 PDCCH search space set, and the parameters of different PDCCH monitoring timings in the monitoring timing table of the first CSS correspond to the configuration parameters of respective common PDCCH repeated transmissions; or, the monitoring timing table of the CSS includes a monitoring timing table of a second CSS, wherein the monitoring timing table of the second CSS is a monitoring timing table of the CSS defined for the common PDCCH repeated transmissions, and different indexes in the monitoring timing table of the second CSS correspond to the configuration parameters of respective common PDCCH repeated transmissions; wherein the configuration parameters of the common PDCCH repeated transmissions are at least part of the parameters contained in the configuration information of the common PDCCH repeated transmissions.

8. The method according to any one of claims 4 to 7, wherein: The number of resources existing in the downlink channel receiving window is associated with some or all of the parameters in the configuration information, and the number of resources includes at least one of the following: the number of CORESETs, the number of search spaces, and the number of PDCCH MOs; or, The transmission resource for repeated transmission of the common PDCCH is located within the downlink channel receiving window; or, The number of resources existing in the downlink channel transmission period is associated with part or all of the configuration information, and the number of resources includes at least one of the following: the number of CORESETs, the number of search spaces, and the number of PDCCH MOs; or, The transmission resource for repeated transmission of the common PDCCH is located within the downlink channel transmission period.

9. The method according to any one of claims 4 to 8, wherein: The downlink channel receiving window includes at least one of the following: A window configured for repeated transmission of the common PDCCH, a receiving window of a downlink channel defined in a protocol, and a window determined based on downlink channel transmission parameters; or, The downlink channel receiving period includes at least one of the following: The period configured for the repeated transmission of the common PDCCH, the reception period of the downlink channel defined in the protocol, and the period determined based on the downlink channel transmission parameters.

10. The method according to any one of claims 1 to 9, wherein: The common PDCCH repeated transmission satisfies at least one of the following: The time domain resources of the repeated transmission of the common PDCCH in CORESET#0 do not overlap with the time domain resources of the associated synchronization signal block SSB; or, the time domain resources of the repeated transmission of the common PDCCH in CORESET#0 overlap with the time domain resources of the associated SSB; The common PDCCH repetition transmission is transmitted the same number of times in multiple SSB periods; The common PDCCH is repeatedly transmitted the same number of times in a plurality of first periods, where the first period is a period in which the SSB is associated with a random access opportunity RO; The common PDCCH repeated transmission is located within the downlink channel receiving window; The common PDCCH repetitive transmission is in the downlink channel transmission period.

11. The method according to any one of claims 1 to 10, wherein: The repeated transmission of the common PDCCH includes repeated transmission in the time domain, and the repeated transmission of the common PDCCH in the time domain includes at least one of the following: Repeated transmission of the common PDCCH on different PDCCH MOs in the same search space of the same CORESET; Repeated transmission of the common PDCCH between different search spaces of the same CORESET; Repeated transmission of the common PDCCH between different search spaces of different CORESETs; Repeated transmission of the common PDCCH in the same search space of different CORESETs; or, The repeated transmission of the common PDCCH includes repeated transmission in the frequency domain, and the repeated transmission of the common PDCCH in the frequency domain includes at least one of the following: Repeated transmission of the common PDCCH on the same PDCCH MO of the same CORESET; The common PDCCH is repeatedly transmitted on the same PDCCH MO of different CORESETs.

12. The method according to any one of claims 1 to 11, wherein: The method further comprises: In a case where resources for repeated transmission of the common PDCCH conflict with resources for first transmission of other common PDCCHs, the terminal abandons reception of the repeated transmission of the common PDCCH.

13. The method according to any one of claims 1 to 12, wherein: The terminal receives the PDCCH repeated transmission according to the configuration information of the PDCCH repeated transmission, including: The terminal receives the PDCCH repetition transmission according to the configuration information of the PDCCH repetition transmission and the timeline information of the common PDCCH repetition transmission, where the timeline information of the common PDCCH repetition transmission includes at least one of the following: The timing relationship between the repeated transmission of the common PDCCH and the physical downlink shared channel PDSCH scheduled by the common PDCCH; The time relationship between the common PDCCH repetitive transmission and the RAR receiving window; The time relationship between the common PDCCH repetitive transmission and the contention resolution timer; The time relationship between the common PDCCH repetition transmission and the message B response window.

14. The method of claim 13, wherein: The timing relationship between the repeated transmission of the common PDCCH and the PDSCH scheduled by the common PDCCH includes the following: The time slot offset of the PDSCH scheduled by the common PDCCH is an offset relative to the time slot where the first transmission of the repeated transmission of the common PDCCH is located; The time slot offset of the PDSCH scheduled by the common PDCCH is the time slot offset relative to the time slot where the last transmission of the common PDCCH is repeated; The time slot offset of the PDSCH scheduled by the common PDCCH is the time slot offset relative to the time slot of the nth transmission of the repeated transmission of the common PDCCH, and the value of n is configured by the network side or agreed upon by the protocol; The time slot offset of the PDSCH scheduled by the common PDCCH is an offset relative to a target time point of a receiving window associated with repeated transmission of the common PDCCH.

15. The method of claim 14, wherein: The first transmission of the common PDCCH includes the following: The common PDCCH is repeatedly transmitted for the first time in the physical time slot; The common PDCCH is repeatedly transmitted for the first time in an available time slot; The common PDCCH repetitive transmission is the first transmission within the RAR receiving window; The common PDCCH repetition transmission is the first transmission within the message B response window; The first valid transmission of the common PDCCH repeated transmission; or, The last transmission of the common PDCCH repeated transmission includes the following: The last transmission of the common PDCCH repetition transmission on the physical time slot; The common PDCCH is repeatedly transmitted in the last transmission in the available time slot; The last transmission of the common PDCCH repetition transmission within the RAR receiving window; The common PDCCH repeats the last transmission within the message B response window; The last valid transmission of the common PDCCH repeated transmission; or, The nth transmission of the common PDCCH repeated transmission includes the following: The common PDCCH is repeatedly transmitted for the nth time on the physical time slot; The common PDCCH is repeatedly transmitted for the nth time in the available time slot; The common PDCCH repetition transmission is the nth transmission within the RAR receiving window; The common PDCCH repetition transmission is the nth transmission within the message B response window; The nth valid transmission of the common PDCCH repeated transmission.

16. The method according to any one of claims 13 to 15, wherein: The time relationship between the common PDCCH repetitive transmission and the RAR receiving window includes the following: The common PDCCH repeated transmission allows to cross the RAR receiving window, and the common PDCCH repeated transmission does not allow to cross the RAR receiving window; or, The time relationship between the common PDCCH repetitive transmission and the contention resolution timer includes the following: The common PDCCH repetitive transmission allows a cross-contention resolution timer, and the common PDCCH repetitive transmission does not allow a cross-contention resolution timer; or, The time relationship between the common PDCCH repetitive transmission and the message B response window includes the following: The common PDCCH repetitive transmission allows crossing the message B response window, and the common PDCCH repetitive transmission does not allow crossing the message B response window.

17. The method according to any one of claims 13 to 16, wherein: The RAR receiving window includes: a RAR receiving window that can be used for repeated transmission of the common PDCCH; or a RAR receiving window obtained by adding an offset to a RAR receiving window that cannot be used for repeated transmission of the common PDCCH; or, The message B response window includes: A message B response window that can be used for repeated transmission of a common PDCCH; or a message B response window obtained by adding an offset to a message B response window that cannot be used for repeated transmission of the common PDCCH; or, The contention resolution timer includes: A contention resolution timer that can be used for common PDCCH repetitive transmission definition; or a contention resolution timer that is obtained by adding an offset to a contention resolution timer that cannot be used for the common PDCCH repetitive transmission.

18. The method according to any one of claims 13 to 17, wherein: The starting time of the RAR receiving window includes: The first symbol of the CORESET that earliest meets the target condition in the first resource; The first resource includes: A resource located after the last symbol occupied by the PRACH and spaced at least one symbol from the last symbol occupied by the PRACH; or, The resource located after the last symbol occupied by the PRACH and whose interval with the last symbol occupied by the PRACH is greater than or equal to the target time, where the target time is equal to: at least one symbol + T TA +k mac , T TA Indicates the duration of timing advance, k mac Indicates the scheduling offset supported by the non-terrestrial network NTN for media access control element MAC CE timing relationship enhancement.

19. The method according to any one of claims 13 to 18, wherein: The starting time of the contention resolution timer includes: the first time after the transmission of message 3 is completed, or the interval between the starting time of the contention resolution timer and the transmission end time of message 3 is equal to or greater than the round trip time RTT; The first moment includes at least one of the following: The first symbol of the next time slot after the transmission of message 3 is completed; The first symbol of the earliest CORESET after the transmission of message 3 is completed; The first symbol of the CORESET that earliest meets the target condition in the second resource; The second resource includes: After the transmission of message 3 is completed, and there is a resource that is at least one symbol away from the end of the transmission of message 3.

20. The method of any one of claims 13 to 19, wherein: The starting time of the message B response window includes at least one of the following: The first symbol of the CORESET where the first transmission of the common PDCCH repeated transmission is located; The first symbol of the CORESET where the last transmission of the common PDCCH repetitive transmission is located; The first symbol of the CORESET where the i-th transmission of the common PDCCH is located, where the value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH; The first symbol of the earliest CORESET in the third resource; The first symbol of the CORESET that earliest meets the target condition in the third resource; Wherein, the third resource includes: A resource located after the last symbol of a physical uplink shared channel PUSCH opportunity corresponding to the PRACH and spaced at least one symbol from the last symbol of the PUSCH opportunity corresponding to the PRACH; or, A resource located after the last symbol of the PUSCH opportunity corresponding to the PRACH and whose interval with the last symbol of the PUSCH opportunity corresponding to the PRACH is greater than or equal to the target time, and the target time is equal to: at least one symbol + T TA +k mac , T TA Indicates the duration of timing advance, k mac Indicates the scheduling offset for media access control element MAC CE timing relationship enhancement supported by the timing non-terrestrial network NTN.

21. The method according to any one of claims 18 to 20, wherein: The CORESET that meets the target conditions includes: The CORESET where the i-th transmission of the common PDCCH is repeated is located, and the value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH.

22. The method of any one of claims 1 to 21, wherein: Also includes: When any of the following conditions is met, the common PDCCH repeated transmission is deactivated: The terminal sends message 3; The terminal receives a successful RAR; RAR receiving window ends; The maximum allowed RAR window ends; The contention resolution timer expires; Message 4 Message 4 was decoded successfully; Message B is decoded successfully; Deactivate the network-side configuration.

23. The method of any one of claims 1 to 22, wherein: In the case where the i-th transmission of the common PDCCH repeated transmission and the PDSCH scheduled by the common PDCCH are transmitted in the same time slot, the relationship between the starting symbol of the PDSCH scheduled by the common PDCCH and the common PDCCH repeated transmission includes at least one of the following: The starting symbol of the PDSCH scheduled by the common PDCCH and the starting symbol of the i-th transmission of the common PDCCH repeated transmission are separated by N symbols; The starting symbol of the PDSCH scheduled by the common PDCCH and the i-th transmission symbol of the repeated transmission of the common PDCCH are separated by N symbols; The value of i is equal to or greater than 1 and less than or equal to the number of repetitions of the common PDCCH, and N is greater than or equal to 0.

24. A method for processing repeated transmission of a physical downlink control channel PDCCH, comprising: The network side device sends the configuration information of the common PDCCH repeated transmission to the terminal; The network side device performs common PDCCH repeated transmission according to the configuration information; The public PDCCH includes at least one of the following: System information block SIB1 PDCCH, other system information OSI PDCCH, message 2 PDCCH, message 4 PDCCH, message B PDCCH, paging PDCCH, PDCCH for scheduling message 3 retransmission.

25. The method of claim 24, wherein: The configuration information includes at least one of the following parameters: The function of repeated transmission of the common PDCCH; The number of repetitions of the common PDCCH repeated transmission; An index of the common PDCCH repeated transmission; Resource information of repeated transmission of the common PDCCH; Activation information of the common PDCCH repeated transmission, where the activation information indicates activation or deactivation of the common PDCCH repeated transmission; The repetition mode of the common PDCCH repeated transmission.

26. The method of claim 24 or 25, wherein: The network side device sends configuration information of common PDCCH repeated transmission to the terminal, including: The network side device sends indication information to the terminal, and the indication information is used to determine the common PDCCH repeated transmission Configuration information of the device, wherein the indication information includes at least one of the following: Synchronization signal block SSB, master information block MIB, physical broadcast channel PBCH, system information block SIB, radio network temporary identifier RNTI, control resource set CORESET configuration table, common search space CSS monitoring time table, downlink channel receiving window, downlink channel transmission period, CORESET resources, search space, physical downlink control channel PDCCH monitoring time MO, physical random access channel PRACH resources, SIB1 PDCCH, message 2, message B, message 2 PDCCH, message B PDCCH, PDCCH scheduling message 3 retransmission, radio resource control RRC signaling, media access control control unit MAC CE, random access response, downlink control information DCI, message 3.

27. The method of any one of claims 24 to 26, wherein: The network side device performs common PDCCH repeated transmission according to the configuration information, including: The network side device performs PDCCH repetition transmission according to the configuration information of the PDCCH repetition transmission and the timeline information of the common PDCCH repetition transmission, where the timeline information of the common PDCCH repetition transmission includes at least one of the following: The timing relationship between the repeated transmission of the common PDCCH and the physical downlink shared channel PDSCH scheduled by the common PDCCH; The time relationship between the common PDCCH repetitive transmission and the RAR receiving window; The time relationship between the common PDCCH repetitive transmission and the contention resolution timer; The time relationship between the common PDCCH repetition transmission and the message B response window.

28. A device for processing repeated transmission of a physical downlink control channel PDCCH, comprising: An acquisition module, used to acquire configuration information of repeated transmission of a common PDCCH; A receiving module, configured to receive repeated transmission of a common PDCCH according to the configuration information; The public PDCCH includes at least one of the following: System information block SIB1 PDCCH, other system information OSI PDCCH, message 2 PDCCH, message 4 PDCCH, message B PDCCH, paging PDCCH, PDCCH for scheduling message 3 retransmission.

29. A processing device for repeated transmission of a physical downlink control channel PDCCH, comprising: A sending module, used for sending configuration information of common PDCCH repeated transmission to the terminal; An execution module, configured to execute common PDCCH repeated transmission according to the configuration information; The public PDCCH includes at least one of the following: System information block SIB1 PDCCH, other system information OSI PDCCH, message 2 PDCCH, message 4 PDCCH, message B PDCCH, paging PDCCH, PDCCH for scheduling message 3 retransmission.

30. A terminal comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method for processing repeated transmission of a physical downlink control channel (PDCCH) as described in any one of claims 1 to 24 are implemented.

31. A network side device, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the processing method for repeated transmission of a physical downlink control channel (PDCCH) as described in any one of claims 25 to 28 are implemented.

32. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the method for processing repeated transmission of a physical downlink control channel (PDCCH) as described in any one of claims 1 to 23, or implements the steps of the method for processing repeated transmission of a physical downlink control channel (PDCCH) as described in any one of claims 24 to 26.

Images