WO2025011474A1 - Downlink repeated transmission method and apparatus, and related apparatus - Google Patents

Abstract

The present application belongs to the technical field of communications. Disclosed are a downlink repeated transmission method and apparatus, and a related apparatus. The downlink repeated transmission method in the embodiments of the present application comprises: a terminal receiving indication information from a network-side device, wherein the indication information is used for indicating a repeat count type, which is used when public PDSCH repeated transmission is performed; according to the repeat count type, the terminal determining a time-domain resource corresponding to the public PDSCH repeated transmission; and the terminal performing the public PDSCH repeated transmission on the time-domain resource.

Description

Downlink repeated transmission method, device and related devices

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on July 10, 2023, with application number 202310840063.7 and application name “Downlink repeated transmission method, device, terminal and readable storage medium”, the entire contents of which are incorporated by reference in this application.

Technical Field

The present application belongs to the field of communication technology, and specifically relates to a downlink repeated transmission method, device and related devices.

Background Art

Currently, in the process of wireless communication, a terminal can send an uplink channel for carrying a random access request message (such as messages Msg 1, Msg A, etc.) to a network side device, so that the network side device can send a downlink channel for carrying a random access response message (such as Msg 2, Msg B, Msg 4, etc.) to the terminal according to the random access request message, so that the terminal can perform a random access process according to the random access response message to establish a wireless connection with the network side device, and then the terminal can communicate with other terminals through the wireless connection.

However, due to the poor channel quality of the downlink channel, the terminal may not receive the above-mentioned random access response message. At this time, the terminal will re-send the uplink channel used to carry the random access request message to the network side device to re-execute the random access process. Therefore, the terminal may take a long time to establish a wireless connection with the network side device, which will cause a large delay in terminal communication.

Summary of the invention

The embodiments of the present application provide a downlink repeated transmission method, device and related devices, which can solve the problem of large delay in terminal communication.

In a first aspect, a downlink repeated transmission method is provided, which is executed by a terminal, and the method includes: the terminal receives indication information from a network side device; the indication information is used to indicate the repetition count type used when performing repeated transmission of a common physical downlink shared channel (PDSCH); the terminal determines the time domain resources corresponding to the repeated transmission of the common PDSCH according to the repetition count type; and the terminal performs repeated transmission of the common PDSCH on the time domain resources.

In a second aspect, a downlink repeated transmission device is provided, and the downlink repeated transmission device includes: a receiving module, a determining module and a transmitting module. Among them, the receiving module is used to receive indication information from a network side device; the indication information is used to indicate the repetition count type used when performing public PDSCH repeated transmission. The determining module is used to determine the time domain resources corresponding to the public PDSCH repeated transmission according to the repetition count type. The transmitting module is used to perform public PDSCH repeated transmission on the time domain resources determined by the determining module.

In a third aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

In a fourth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive indication information from a network side device; the indication information is used to indicate the repetition count type used when performing repeated transmission of a public PDSCH; the processor is used to determine the time domain resources corresponding to the repeated transmission of the public PDSCH according to the repetition count type; and the communication interface is also used to perform repeated transmission of the public PDSCH on the time domain resources.

In a fifth 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 described in the first aspect are implemented.

In a sixth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the method described in the first aspect.

In a seventh aspect, a computer program/program product is provided, wherein the computer program/program product 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 described in the first aspect.

In an eighth aspect, a downlink repetition transmission device is provided, comprising: the downlink repetition transmission device being configured to execute the steps of the method described in the first aspect.

In the embodiment of the present application, the terminal can receive a message from the network side device indicating that the common PDSCH is being repeatedly transmitted. The terminal can determine the time domain resources corresponding to the repeated transmission of the public PDSCH according to the repetition count type indicated by the network-side device when performing repeated transmission of the public PDSCH, and perform repeated transmission of the public PDSCH on the time domain resources, that is, the terminal can transmit the public PDSCH multiple times on the time domain resources. Therefore, the situation where the terminal does not receive the public PDSCH due to poor channel quality of the downlink channel can be reduced, so as to reduce the situation where the terminal does not receive the random access response message, thereby reducing the time it takes for the terminal to establish a wireless connection with the network-side device, and thus, the communication delay of the terminal can be reduced.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a block diagram of a wireless communication system provided in an embodiment of the present application;

FIG2 is a schematic diagram of a flow chart of a downlink repeated transmission method according to an embodiment of the present application;

FIG3 is a second flow chart of a downlink repeated transmission method provided in an embodiment of the present application;

FIG4 is a third flow chart of a downlink repeated transmission method provided in an embodiment of the present application;

FIG5 is a fourth flow chart of a downlink repeated transmission method provided in an embodiment of the present application;

FIG6 is a schematic diagram of the structure of a downlink repeated transmission device provided in an embodiment of the present application;

7 is a schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application;

FIG8 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application.

DETAILED DESCRIPTION

The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

The terms involved in the embodiments of the present application are explained below.

1. Random access process, Msg 2, Msg B and Msg 4

Currently, 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).

Among them, in the contention-based four-step random access process (4-step Random Access Channel, 4-step RACH), the terminal can first send Msg 1 to the network side device, and the Msg 1 includes the preamble preamble, so that after the network side device detects the preamble, it can send Msg 2/Random Access Response (RAR) message to the terminal, and the Msg 2 includes the number of the preamble detected by the network side device, and the uplink wireless resources allocated to the terminal to send Msg 3; so that after receiving Msg 2, the terminal can confirm that the preamble carried in Msg 2 Whether there is a number in the preamble number that is consistent with the number of the preamble sent by the terminal, and if it is determined that there is a number that is consistent with the number of the preamble sent by the terminal, Msg3 containing contention resolution information can be sent according to the uplink wireless resource; after receiving Msg 3, the network side device can send Msg 4 containing contention resolution information to the terminal; then, after receiving Msg 4, the terminal can determine whether the contention resolution information is consistent with the contention resolution information sent by the terminal in Msg 3, and if it is determined that the contention resolution information is consistent with the contention resolution information sent by the terminal in Msg 3, a wireless connection can be established with the network side device, thereby completing the four-step random access process.

The network side device can include the uplink grant (UL grant) information in Msg 2/RAR to indicate the scheduling information of Msg 3 physical uplink shared channel (PUSCH), and include the random access process preamble ID (RAPID), the temporary identity of the wireless network (TC-RNTI), the timing advance command (TA), etc. If the network side device does not receive Msg 3 PUSCH, it can schedule the retransmission of Msg 3 PUSCH in the physical downlink control channel (PDCCH) scrambled by TC-RNTI.

For the competitive 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 wireless resources. This situation can be understood as a terminal preamble conflict. In this case, different terminals will receive the same Msg 2/RAR. At this time, different terminals will transmit Msg 3 according to the scheduling information in the RAR uplink grant (UpLink grant, UL grant). None Regardless of whether Msg 3 PUSCH is scheduled for repeated transmission, the network side device can only decode one PUSCH (including contention resolution information) sent by the terminal on the same Msg 3 PUSCH scheduling resource, so the network side device will include the contention resolution information received in Msg 3 in Msg 4. If the contention resolution information in Msg 4 received by the terminal matches the contention resolution information sent by the terminal in Msg 3 PUSCH, the terminal considers that the contention resolution is successful. If they do not match, the contention resolution is considered unsuccessful.

If the contention resolution is unsuccessful, the terminal reselects the RACH sending resource, sends the Physical Random Access Channel (PRACH), and attempts the next random access process.

Among them, in the two-step random access process 2-step RACH, the terminal can first send Msg A to the network side device, so that the network side device can send Msg B to the terminal after receiving Msg A. If the terminal does not receive Msg B within a certain period of time, the terminal will accumulate the counter that counts the number of times Msg A is sent and resend Msg A. If the counter that counts the number of times Msg A is sent reaches a certain threshold, the terminal will switch from 2-step RACH to 4-step RACH. Here, the Msg B received by the terminal can be a success random access response success RAR, at which time the 2-step RACH ends, that is, the terminal establishes a wireless connection with the network side device. It may also be a fallback random access response fallback RAR, at which time the terminal can fall back to the 4-step RACH process. Among them, Msg A includes Msg A preamble part and Msg A PUSCH part. The preamble part is sent on the time-frequency radio resources used for 2-step RACH, and the PUSCH part is sent on the MsgA PUSCH resources associated with the sending of Msg A preamble and time-frequency radio resources. MsgA PUSCH resources are a group of PUSCH resources configured relative to each PRACH time slot, including time-frequency resources and demodulation reference signal (DMRS) resources.

2. Determination of the transmission resources of Msg 2 Physical Downlink Shared Channel (PDSCH), Msg B PDSCH, or Msg 4 PDSCH

Time Domain Resource Allocation

Currently, Msg 2 PDSCH is a downlink transmission scheduled by downlink control information (DCI) with a random access-radio network temporary identifier (RA-RNTI) scrambled with a cyclic redundancy check code (CRC); MsgB PDSCH is a downlink transmission scheduled by DCI with MsgB-RNTI scrambled with CRC; Msg4 PDSCH is a downlink transmission scheduled by DCI with TC-RNTI scrambled with CRC.

Table 1 shows the Time Domain Resource Allocation (TDRA) table. As shown in Table 1:

Table 1 TDRA table

Among them, for Msg 2/Msg B/Msg 4 PDSCH, if pdsch-TimeDomainAllocationList is configured in the high-level parameter PDSCH-ConfigCommon, the time domain resource allocation of Msg 2/Msg B/Msg 4 PDSCH is given by pdsch-TimeDomainAllocationList; otherwise, it is given by the default table Default A, which can be the PDSCH TDRA default table A for the case of normal cyclic prefix (Normal Cyclic Prefix, NCP). Table 2 The PDSCH TDRA default table A for NCP is shown in Table 2:

Table 2 PDSCH TDRA default table A for NCP

Among them, it can be seen from the information in Table 2 that a set of parameters K0, S and L can be determined by the row index (indicated by the DCI that schedules the PDSCH), dmrs-TypeA-Position, and PDSCH mapping type. Among them, K0 represents the time slot offset between the DCI that schedules the PDSCH and the PDSCH, S represents the starting symbol of the time domain resource transmitted by the PDSCH, and L represents the number of symbols occupied by the time domain resource transmitted by the PDSCH.

3. Other terms

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 under appropriate circumstances, 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 do not limit the number of objects. For example, the first object can be one or more. In addition, the terms used in this application are interchangeable under appropriate circumstances, 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 do not limit the number of objects. For example, the first object can be one or more. The "or" in the application indicates at least one of the connected objects. For example, "A or B" covers three solutions, namely, solution 1: including A but not including B; solution 2: including B but not including A; solution 3: including both A and B. The character "/" generally indicates that the objects connected before and after are in an "or" relationship.

The term "indication" in this application can be 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, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.

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 described technology can be used for the above-mentioned systems and radio technologies as well as other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terms are used in most of the following descriptions, but these technologies can also be applied to systems other than NR systems, such as ^6th Generation (6G) communication systems.

FIG1 shows a block diagram of a wireless communication system applicable to the embodiment of the present application. The wireless communication system includes a terminal 11 and a network side device 12 . Among them, the terminal 11 can 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 (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), a flight vehicle (flight vehicle), a vehicle user equipment (VUE), a shipborne equipment, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and other terminal side devices. 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 (Wireless Local Area Network, WLAN) access point (Access Point, AS) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc. Among them, the base station can be called Node B (Node B, NB), Evolved Node B (Evolved Node B, eNB), the next generation Node B (the next generation Node B, gNB), New Radio Node B (New Radio Node B, NR Node B), access point, Relay Base Station (Relay Base Station, RBS), Serving Base Station (Serving Base Station, SBS), Base Transceiver Station (Base Transceiver Station, BTS), radio base station, radio transceiver, base The base station is not limited to specific technical terms as long as the same technical effect is achieved. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

The following, in conjunction with the accompanying drawings, describes in detail the downlink repeated transmission method, device and related devices provided in the embodiments of the present application through some embodiments and their application scenarios.

The downlink repeated transmission method provided in the embodiment of the present application can be performed by a downlink repeated transmission device, or an electronic device, or a functional module or entity in an electronic device. The downlink repeated transmission method provided in the embodiment of the present application is described by taking the transmission method as an example.

Fig. 2 shows a schematic flow chart of a downlink repeated transmission method provided in an embodiment of the present application. As shown in Fig. 2, a downlink repeated transmission method provided in an embodiment of the present application may include the following steps 101 to 103.

Step 101: The terminal receives instruction information from a network side device.

In the embodiment of the present application, the above indication information is used to indicate the repetition count type adopted when performing repeated transmission of the common physical downlink shared channel PDSCH.

In some embodiments of the present application, the network side device may be a network side device in a non-terrestrial network (NTN) system or a network side device in a terrestrial network (TN) system. It can be understood that the downlink repeated transmission method provided in the embodiments of the present application may be applied to the NTN scenario or the TN scenario.

In one example, a terminal may receive a radio resource control (RRC) signaling from a network side device, wherein the RRC signaling includes indication information, wherein the indication information is included in a target bit bit in the RRC signaling.

Exemplarily, the terminal may receive a system message from a network side device, and the target bit in the system message includes the indication information. It should be noted that, in this example, the network side device assumes that all UEs are capable of repeating the common PDSCH based on the count of available time slots, or that all terminals supporting the repeat transmission of the common PDSCH are capable of repeating the common PDSCH based on the count of available time slots.

In another example, the terminal may receive a fourth DCI from the network side device, where the fourth DCI is used to schedule repeated transmission of a common PDSCH, and the fourth DCI includes indication information.

In yet another example, the terminal may receive a first PDSCH from a network side device, where the first PDSCH may be a PDSCH in a PDSCH transmitted by repeated transmission of a common PDSCH, and the first PDSCH includes indication information.

Optionally, the first PDSCH may be the first PDSCH in the PDSCHs transmitted by the repeated transmission of the common PDSCH. It can be understood that the first PDSCH may be the PDSCH transmitted by the first transmission of the repeated transmission of the common PDSCH.

In another example, the terminal may receive a first time domain resource allocation (TDRA) table from a network side device, where the TDRA table is indication information. For example, the TDRA table may be a default table Default A, which is used to indicate a common PDSCH repetition transmission counted based on available time slots. It is understood that the terminal may determine the repetition count type used when performing common PDSCH repetition transmission based on different received TDRA tables.

In another example, the terminal may receive a target mapping relationship table from a network side device, the target mapping relationship table including at least one mapping relationship, each mapping relationship being a mapping relationship between a first format and a repetition count type, the first format being a format in which the terminal sends a physical random access channel (PRACH) to the network side device, and the target mapping relationship table is the indication information. It is understandable that the terminal may use the target mapping relationship table to determine the corresponding repetition count type according to the first format in which the terminal sends the PRACH to the network side device, so as to determine the repetition count type used when performing repeated transmission of the public PDSCH.

Optionally, the above-mentioned target mapping relationship table can be predefined, or agreed upon by protocol, or indicated by system information (SI).

In some embodiments of the present application, the above-mentioned public PDSCH may include at least one PDSCH that needs to be received before the terminal enters the RRC connected state. It should be noted that the above-mentioned "PDSCH that needs to be received" can be understood as: the PDSCH received from the network side device during the process of the terminal switching from the RRC idle state or inactive state to the RRC connected state.

Exemplarily, the public PDSCH may include at least one of the following: Msg 2 PDSCH, Msg B PDSCH, Msg 4 PDSCH, and paging PDSCH. Among them, Msg B PDSCH may include at least one of a success response success RAR and a fallback response fallback RAR.

In some embodiments of the present application, the above-mentioned repetition count type may be any one of the following: a physical time slot count type and an available time slot count type. The physical time slot count type is used to indicate that in the process of calculating the number of common PDSCH repetition transmissions, the counting is based on the physical time slot; the available time slot count type is used to indicate that in the process of calculating the number of common PDSCH repetition transmissions, the counting is based on the available time slot.

The above “counting based on physical time slots” can be understood as: continuous physical time slots are used for repeated transmission of common PDSCH, and the continuous physical time slots are counted in the number of configured repeated transmissions of common PDSCH. The above “counting based on available time slots” can be understood as: only available time slots are used for repeated transmission of common PDSCH, and the available time slots are counted in the number of configured repeated transmissions of common PDSCH.

Step 102: The terminal determines the time domain resources corresponding to the repeated transmission of the common PDSCH according to the repetition count type.

In the embodiment of the present application, the time domain resources corresponding to the above-mentioned common PDSCH repeated transmission are: the time domain resources used for the common PDSCH repeated transmission.

In some embodiments of the present application, the time domain resources may include any of the following: at least one time slot, at least one symbol. The at least one symbol may specifically be an orthogonal frequency division multiplexing (OFDM) symbol.

In some embodiments of the present application, when the repetition count type is a physical time slot count type, that is, when the repetition count type indicates counting based on physical time slots, the terminal may determine at least one continuous time slot as a time domain resource corresponding to the common PDSCH repeated transmission. The first time slot of the at least one time slot is located at the position of the common PDSCH repeated transmission start transmission configured by the network side device, or after the position.

In some embodiments of the present application, in combination with FIG. 2 , as shown in FIG. 3 , the above step 102 may be specifically implemented through the following step 102a.

Step 102a: When the repetition count type indicates counting based on physical time slots, the terminal determines N consecutive time slots from the starting position as time domain resources.

In the embodiment of the present application, the above-mentioned starting position is: the position where the common PDSCH repeated transmission starts transmission configured by the network side device; N is a positive integer.

It can be understood that, in this example, the at least one time slot is N time slots, and the first time slot in the at least one time slot is located at the starting position.

In some embodiments of the present application, when the common PDSCH repetitive transmission is a repetitive transmission within a time slot, the number N of N time slots is equal to the number of time slots corresponding to the above-mentioned time domain resources.

Exemplarily, assuming that the number of times the common PDSCH is repeatedly transmitted is K, the number N of N time slots is equal to the number of time slots occupied by the time domain resources that are repeatedly used K times.

Optionally, when the repetition count type indicates that counting is based on physical time slots, if the common PDSCH repetition transmission is a repetition transmission within a time slot, the terminal can first determine the number of time slots occupied by the time domain resources used for the common PDSCH repetition transmission, and determine the time domain resources consisting of continuous time slots from the first time slot at the starting position to this number of time slots as the time domain resources corresponding to the common PDSCH.

In some embodiments of the present application, when the common PDSCH repetitive transmission is inter-time slot repetitive transmission, the number N of N time slots is equal to the number of common PDSCH repetitive transmissions.

Optionally, when the repetition count type indicates that counting is based on physical time slots, if the common PDSCH repetition transmission is a repetition transmission between time slots, the terminal can first determine the number N of common PDSCH repetition transmissions, and determine the number N as the number N of time slots occupied by the time domain resources corresponding to the common PDSCH repetition transmission, and then determine N consecutive time slots from the starting position as the time domain resources corresponding to the common PDSCH repetition transmission.

It can be seen that since the terminal can directly determine N consecutive time slots from the starting position as time domain resources when the repetition counting type indicates counting based on the physical time slot, the terminal can directly perform public PDSCH retransmission from the starting position without waiting for a long time. Therefore, the efficiency of public PDSCH retransmission can be improved.

In some embodiments of the present application, when the repetition count type is a count type based on available time slots, that is, when the repetition count type indicates counting based on available time slots, the terminal can determine symbols that meet the conditions from at least one time slot, and determine the use resources composed of the symbols that meet the conditions in the at least one time slot as the time domain resources corresponding to the repeated transmission of the common PDSCH. In each time slot, the at least one symbol can be a continuous symbol or a discontinuous symbol, and the first symbol of the at least one symbol is located at the position of the start transmission of the repeated transmission of the common PDSCH configured by the network side device, or after the position.

In some embodiments of the present application, in combination with FIG. 2 , as shown in FIG. 4 , the above step 102 can be specifically performed as follows: Step 102b is implemented.

Step 102b: When the repetition count type indicates counting based on available time slots, the terminal determines the time slot including the target symbol from the M time slots starting from the starting position as the time domain resource.

In the embodiment of the present application, the above-mentioned starting position is: the position where the common PDSCH repeated transmission starts transmission configured by the network side device; M is a positive integer.

It can be understood that, in this example, the at least one time slot is M time slots, and the first time slot of the M time slots is located at the starting position.

In some embodiments of the present application, the above-mentioned M time slots may be continuous or discontinuous time slots.

In an embodiment of the present application, the terminal can first determine M time slots starting from the starting position, and then determine whether each time slot is an available time slot based on whether the target symbol is included in multiple symbols in each time slot of the M time slots, so as to determine at least one available time slot, so that the terminal can determine the at least one available time slot as the use resource used for the repeated transmission of the common PDSCH.

It can be understood that, in this example, the target symbol in the at least one available time slot may be the symbol occupied by all repeated transmissions on the time domain resources corresponding to the common PDSCH repeated transmissions.

Optionally, the multiple symbols in each of the above M time slots are determined by S and L in TDRAtable.

In the embodiment of the present application, the target symbol satisfies at least one of the following:

The symbol format of the target symbol is a downlink symbol or a flexible symbol;

The target symbol and the symbols occupied by the synchronization signal block (SSB) do not overlap in the time domain;

The target symbol does not overlap in the time domain with the symbol occupied by the control resource set CORESET where the first PDCCH for scheduling repeated transmission of the common PDSCH is located;

The target symbol and the symbol corresponding to the Sounding Reference Signal (SRS) transmission of the serving cell do not overlap in the time domain.

In some embodiments of the present application, the number of the first PDCCH is at least one; the first PDCCH satisfies at least one of the following:

The first PDCCH is at least one PDCCH among the PDCCHs transmitted by PDCCH repetition transmission;

When the number of the first PDCCHs is at least two, the at least two first PDCCHs are PDCCHs transmitted by different transmitting and receiving nodes;

The first PDCCH belongs to a CORESET of the serving cell to which the terminal has accessed;

When the number of the first PDCCHs is at least two, the at least two first PDCCHs are PDCCH candidates in different search space sets.

In an embodiment of the present application, the above-mentioned service cell is different from the service cell corresponding to the public PDSCH repeated transmission, and the service cell is not configured with PUSCH transmission or physical uplink control channel (Physical Uplink Control Channel, PUCCH) transmission.

In some embodiments of the present application, the symbols corresponding to the SRS transmission include: symbols occupied by the SRS transmission and first symbols, wherein the first symbols are symbols occupied by the uplink or downlink retuning time.

In this way, it can be seen that since the terminal can determine the available time slot from the M time slots according to whether the target symbol is included in the M time slots when the repetition counting type indicates that counting is based on the available time slots, so as to determine the available time slot as the time domain resource corresponding to the common PDSCH repeated transmission, instead of determining any time slot as the time domain resource corresponding to the common PDSCH repeated transmission. Therefore, it can avoid the situation where the terminal cannot perform the common PDSCH repeated transmission. In this way, the success rate of the terminal in performing the random access process can be improved.

Step 103: The terminal repeatedly transmits the common PDSCH on time domain resources.

It can be understood that the terminal can receive repeated transmissions of the common PDSCH on the time domain resources corresponding to the common PDSCH.

The embodiment of the present application provides a downlink repeated transmission method, whereby a terminal can receive indication information for indicating the type of repetition count used when performing repeated transmission of a common PDSCH from a network side device, and determine the time domain resource corresponding to the repeated transmission of the common PDSCH according to the repetition count type, so that the terminal can perform repeated transmission of the common PDSCH on the time domain resource. The counting type determines the time domain resources corresponding to the repeated transmission of the public PDSCH, and repeats the public PDSCH on the time domain resources, that is, the terminal can transmit the public PDSCH multiple times on the time domain resources. Therefore, it can reduce the situation where the terminal does not receive the public PDSCH due to poor channel quality of the downlink channel, so as to reduce the situation where the terminal does not receive the random access response message, thereby reducing the time for the terminal to establish a wireless connection with the network side device, so as to reduce the delay of terminal communication.

Of course, before the terminal performs repeated transmission of the common PDSCH, the terminal can first determine the transmission characteristic information corresponding to the demodulation reference signal (DMRS) port of the repeated transmission of the common PDSCH, which will be explained with an example below.

In some embodiments of the present application, in combination with FIG. 2 , as shown in FIG. 5 , before the above step 103 , the downlink repeated transmission method provided in the embodiment of the present application may further include the following step 201 .

Step 201: The terminal determines transmission characteristic information corresponding to the DMRS port for repeated transmission of a common PDSCH.

It should be noted that the execution order of the above steps 201 and 102 is not limited in the embodiment of the present application; in one example, the terminal may first execute step 201 and then execute step 102; in another example, the terminal may first execute step 102 and then execute step 201; in yet another example, the terminal may execute step 102 while executing step 201. In FIG. 5, it is illustrated that the terminal first executes step 102 and then executes step 201.

In the embodiment of the present application, the transmission characteristic information includes at least one of the following:

Average power;

Average delay;

Delay spread;

Doppler shift;

Doppler expansion;

Space receiving parameters;

The beam in which the common PDSCH is repeatedly transmitted.

In some embodiments of the present application, the transmission characteristic information corresponding to the DMRS port for repeated transmission of the common PDSCH satisfies at least one of the following:

In the case where the common PDSCH repetition transmission is Msg 2 PDSCH repetition transmission or Msg B PDSCH repetition transmission, the transmission characteristic information corresponding to the DMRS port of the common PDSCH repetition transmission is the same as the transmission characteristic information corresponding to the SSB or channel state information reference signal (CSI Reference Signal, CSI-RS) resource corresponding to the RACH resource used by the terminal;

The transmission characteristic information corresponding to the DMRS port for repeated transmission of the common PDSCH is the same as the transmission characteristic information corresponding to the DMRS port of the first PDCCH for scheduling repeated transmission of the common PDSCH;

In the case where the common PDSCH repeated transmission is a specific transmission, the transmission characteristic information corresponding to the DMRS port of the common PDSCH repeated transmission is the same as the transmission characteristic information corresponding to the SSB or CSI-RS resource corresponding to the RACH resource selected by the terminal;

In the case where the above-mentioned common PDSCH repeated transmission is a repeated transmission scheduled by the third DCI, the transmission characteristic information corresponding to the common PDSCH repeated transmission and the DMRS port of the third downlink channel are the same as the transmission characteristic information corresponding to the same SSB or CSI-RS resource.

In an embodiment of the present application, when the public PDSCH repetition transmission is Msg 2 PDSCH repetition transmission or Msg B PDSCH repetition transmission, the DMRS port of the public PDSCH repetition transmission and the SSB or CSI-RS resource corresponding to the RACH resource used by the terminal have a quasi co-location (Quasi Co-Location, QCL) relationship.

Optionally, if the RACH resource used by the terminal adopts repeated transmission, a DMRS port of each repeated transmission of the common PDSCH repeated transmission and an SSB or CSI-RS resource corresponding to each repeated transmission of the RACH resource used by the terminal have a QCL relationship.

In the embodiment of the present application, the DMRS port for repeated transmission of the above-mentioned common PDSCH has a QCL relationship with the DMRS port of the first PDCCH that schedules repeated transmission of the common PDSCH.

It should be noted that, for the description of the first PDCCH, reference may be made to the specific description in the above embodiment. The embodiments are not described in detail here.

Optionally, if the first PDCCH that schedules repeated transmission of the common PDSCH adopts repeated transmission, a DMRS port for each repeated transmission of the common PDSCH has a QCL relationship with a DMRS port for each repeated transmission of the first PDCCH that schedules repeated transmission of the common PDSCH.

In the embodiment of the present application, the above-mentioned specific transmission includes at least one of the following: transmission of PDSCH in reply to the initial transmission physical uplink shared channel PUSCH carrying Msg 3, transmission of PDSCH in reply to the retransmission PUSCH carrying Msg 3, transmission of PDSCH in reply to the PUSCH of type-2 RACH process, transmission of PDSCH in reply to the PUSCH scheduled by fallback random access response fallback RAR uplink scheduling authorization UL grant, and transmission of PDSCH in reply to the retransmission PUSCH scheduled by fallback RAR UL grant.

In the embodiment of the present application, when the common PDSCH repeated transmission is a specific transmission, a QCL relationship exists between the DMRS port of the common PDSCH repeated transmission and the SSB or CSI-RS resource corresponding to the RACH resource selected by the terminal.

Optionally, if the RACH resource selected by the terminal adopts repeated transmission, a DMRS port of each repeated transmission of the common PDSCH repeated transmission and an SSB or CSI-RS resource corresponding to each repeated transmission of the RACH resource selected by the terminal have a QCL relationship.

In the embodiment of the present application, the above-mentioned third DCI is: the RA-RNTI scrambled DCI corresponding to the CFRA triggered by the PDCCH command order on the special cell SpCell; the above-mentioned third downlink channel is PDCCH order.

In some embodiments of the present application, after the terminal determines the transmission characteristic information corresponding to the DMRS port for repeated transmission of the common PDSCH, the terminal can determine the beam for repeated transmission of the common PDSCH based on the transmission characteristic information corresponding to the DMRS port for repeated transmission of the common PDSCH, so that the terminal can select the direction of the receiving beam that matches the beam direction to perform repeated transmission of the common PDSCH.

It can be seen that since the terminal can determine the transmission characteristic information corresponding to the DMRS port of the public PDSCH repeated transmission, the terminal can accurately determine the beam of the public PDSCH repeated transmission based on the transmission characteristic information, so that the terminal can accurately select the direction of the receiving beam that matches the beam direction to improve the transmission quality of the public PDSCH repeated transmission.

Of course, when the terminal performs repeated transmission of the common PDSCH, conflicts may occur between the repeated transmission of the common PDSCH and other transmissions. Therefore, when the terminal performs repeated transmission of the common PDSCH, it can determine the transmission mode for repeated transmission of the common PDSCH according to the type of the other transmission.

In some embodiments of the present application, the above-mentioned terminal performs repeated transmission of a common PDSCH on a time domain resource to meet at least one of the following conditions:

When the first downlink channel overlaps with the common PDSCH repetition transmission, the terminal gives priority to the common PDSCH repetition transmission;

When the terminal is in an idle state or an inactive state, if the second downlink channel and the common PDSCH repeated transmission do not overlap in the frequency domain and overlap in the time domain, the terminal is allowed to transmit the second downlink channel while performing the common PDSCH repeated transmission;

When there is overlap between SSB transmission and common PDSCH repetition transmission in the frequency domain, the terminal performs common PDSCH repetition transmission on the frequency domain resources corresponding to the common PDSCH repetition transmission.

In some embodiments of the present application, the first downlink channel is a PDSCH scheduled by a first DCI, and the first DCI is scrambled by any of the following:

Cell Radio Network Temporary Identifier (C-RNTI);

Modulation Coding Scheme Cell Radio Network Temporary Identifier (MCS-C-RNTI);

Group-Radio Network Temporary Identity (G-RNTI) for multicast;

G-RNTI for broadcast;

Multicast Control Channel RNTI (MCCH-RNTI);

Group Configured Scheduling RNTI (G-CS-RNTI);

Configured Scheduled-Radio Network Temporary Identity (CS-RNTI).

In some embodiments of the present application, when a first preset condition is met, the terminal may determine that the first downlink channel overlaps with the common PDSCH repeated transmission. The first preset condition may include at least one of the following: the time domain resources corresponding to the first downlink channel overlap with the time domain resources corresponding to the common PDSCH repeated transmission, and the frequency domain resources corresponding to the first downlink channel overlap with the time domain resources corresponding to the common PDSCH repeated transmission.

It should be noted that the above-mentioned “overlap exists” can be understood as: partial overlap or full overlap.

In some embodiments of the present application, when the transmission capability of the terminal cannot support simultaneous first downlink channel transmission and common PDSCH repeated transmission, the terminal may discard the first downlink channel and perform common PDSCH repeated transmission.

In the embodiment of the present application, the above-mentioned “idle state” is: the above-mentioned RRC idle state.

In some embodiments of the present application, the second downlink channel is a PDSCH scheduled by a second DCI, and the second DCI is scrambled by any of the following:

System Information Radio Network Temporary Identity (SI-RNTI);

Paging-Radio Network Temporary Identity (P-RNTI);

Random Access-Radio Network Temporary Identifier (RA-RNTI);

Temporary Cell-Radio Network Temporary Identifier (TC-RNTI);

Message B Radio Network Temporary Identifier Msg B-RNTI.

In some embodiments of the present application, when the transmission capability of the terminal supports simultaneous repeated transmission of the common PDSCH and transmission of the second downlink channel, the terminal may transmit the second downlink channel while performing repeated transmission of the common PDSCH.

In some embodiments of the present application, when the transmission capability of the terminal cannot support simultaneous repeated transmission of the common PDSCH and transmission of the second downlink channel, the terminal may perform repeated transmission of the common PDSCH, or the terminal may perform transmission of the second downlink channel.

It can be understood that although the terminal is running while performing common PDSCH repeated transmission and transmission of the second downlink channel, the transmission capability of the terminal may not be able to support the simultaneous transmission of common PDSCH repeated transmission and transmission of the second downlink channel. Therefore, the terminal may only perform common PDSCH repeated transmission, or only perform transmission on the second downlink channel.

In an embodiment of the present application, the above-mentioned frequency domain resources do not include the frequency domain units corresponding to the time units occupied by SSB transmission.

In some embodiments of the present application, the above-mentioned frequency domain unit may specifically be a physical resource block (PRB).

In some embodiments of the present application, the above-mentioned SSB transmission is determined by the parameter ssb-positionslnBurst.

It can be seen that since the terminal needs to meet the above-mentioned conditions for repeated transmission of public PDSCH in the time domain resources, it can avoid the situation where the public PDSCH repeated transmission cannot be performed due to the conflict between the public PDSCH repeated transmission and other transmissions. Therefore, the number of public PDSCH repeated transmissions can be increased, thereby improving the reliability of receiving the public PDSCH repeated transmission, thereby improving the coverage capability.

The downlink repeated transmission method provided in the embodiment of the present application may be performed by a downlink repeated transmission device. In the embodiment of the present application, the downlink repeated transmission device performing the downlink repeated transmission method is taken as an example to illustrate the downlink repeated transmission device provided in the embodiment of the present application.

Fig. 6 shows a possible structural diagram of a downlink repeated transmission device involved in an embodiment of the present application. As shown in Fig. 6 , the downlink repeated transmission device 50 may include: a receiving module 51 , a determining module 52 and a transmitting module 53 .

The receiving module 51 is used to receive indication information from a network side device; the indication information is used to indicate the repetition count type used when performing the public PDSCH repetition transmission. The determining module 52 is used to determine the time domain resources corresponding to the public PDSCH repetition transmission according to the repetition count type. The transmission module 53 is used to perform the public PDSCH repetition transmission on the time domain resources determined by the determining module 52.

The embodiment of the present application provides a downlink repeated transmission device, because the downlink repeated transmission device can determine the public PDSCH repeated transmission according to the repetition count type used when performing the public PDSCH repeated transmission indicated by the network side device. The corresponding time domain resources are input, and the common PDSCH is repeatedly transmitted on the time domain resources, that is, the downlink repeated transmission device can transmit the common PDSCH multiple times on the time domain resources. Therefore, the situation where the downlink repeated transmission device fails to receive the common PDSCH due to the poor channel quality of the downlink channel can be reduced, so as to reduce the situation where the downlink repeated transmission device fails to receive the random access response message, thereby reducing the time for the downlink repeated transmission device to establish a wireless connection with the network side device. In this way, the communication delay of the downlink repeated transmission device can be reduced.

In a possible implementation, the determination module 52 is specifically configured to determine N consecutive time slots from a starting position as time domain resources when the repetition count type indicates counting based on physical time slots. The starting position is: the position of the common PDSCH repetition transmission start transmission configured by the network side device; N is a positive integer.

In one possible implementation, when the common PDSCH repetition transmission is intra-time slot repetition transmission, the number N of N time slots is equal to the number of time slots corresponding to the time domain resources; when the common PDSCH repetition transmission is inter-time slot repetition transmission, the number N of N time slots is equal to the number of times the common PDSCH is repetitively transmitted.

In a possible implementation, the determination module 52 is specifically used to determine the time slot including the target symbol in the M time slots starting from the starting position as the time domain resource when the repetition count type indicates that the counting is based on the available time slots. Wherein, the starting position is: the starting transmission position of the public PDSCH repetition transmission configured by the network side device; M is a positive integer; the target symbol satisfies at least one of the following: the symbol format of the target symbol is a downlink symbol or a flexible symbol; the target symbol does not overlap with the symbol occupied by the SSB in the time domain; the target symbol does not overlap with the symbol occupied by the CORESET where the first PDCCH scheduling the public PDSCH repetition transmission is located in the time domain; the target symbol does not overlap with the symbol corresponding to the SRS transmission of the serving cell in the time domain. Wherein, the serving cell is different from the serving cell corresponding to the public PDSCH repetition transmission, and the serving cell is not configured with PUSCH transmission or PUCCH transmission.

In one possible implementation, the number of the above-mentioned first PDCCHs is at least one; the first PDCCH satisfies at least one of the following items: the first PDCCH is at least one PDCCH among the PDCCHs transmitted by PDCCH repetition transmission; when the number of first PDCCHs is at least two, at least two first PDCCHs are PDCCHs of different transmissions; the first PDCCH belongs to a CORESET of the service cell to which the downlink repetition transmission device 50 has accessed; when the number of first PDCCHs is at least two, at least two first PDCCHs are PDCCH candidates of different search space sets.

In a possible implementation, the transmission module 53 performs repeated transmission of the common PDSCH on time domain resources to meet at least one of the following conditions: when there is overlap between the first downlink channel and the repeated transmission of the common PDSCH, the repeated transmission of the common PDSCH is given priority; when the downlink repeated transmission device 50 is in an idle state or an inactive state, if there is no overlap between the second downlink channel and the repeated transmission of the common PDSCH in the frequency domain and there is overlap in the time domain, the transmission of the second downlink channel is allowed while the repeated transmission of the common PDSCH is being performed; when there is overlap between the SSB transmission and the repeated transmission of the common PDSCH in the frequency domain, the repeated transmission of the common PDSCH is performed on the frequency domain resources corresponding to the repeated transmission of the common PDSCH. The frequency domain resources do not include the frequency domain units corresponding to the time units occupied by the SSB transmission.

In one possible implementation, the above-mentioned first downlink channel is a PDSCH scheduled by a first DCI, and the first DCI is scrambled by any of the following items: C-RNTI; MCS-C-RNTI; G-RNTI for multicast; G-RNTI for broadcast; MCCH-RNTI; G-CS-RNTI; CS-RNTI.

In one possible implementation, the second downlink channel is a PDSCH scheduled by a second DCI, and the second DCI is scrambled by any one of the following: SI-RNTI; P-RNTI; RA-RNTI; TC-RNTI; Msg B-RNTI.

In a possible implementation, the determination module 52 is further used to determine the transmission characteristic information corresponding to the DMRS port of the public PDSCH repeated transmission. The transmission characteristic information includes at least one of the following: average power; average delay; delay spread; Doppler shift; Doppler spread; spatial reception parameter; beam of the public PDSCH repeated transmission.

In a possible implementation, the transmission characteristic information corresponding to the DMRS port of the above-mentioned public PDSCH repeated transmission satisfies at least one of the following: when the public PDSCH repeated transmission is Msg 2 PDSCH repeated transmission or Msg B PDSCH repeated transmission, the transmission characteristic information corresponding to the DMRS port of the public PDSCH repeated transmission is the same as the transmission characteristic information corresponding to the SSB or CSI-RS resource corresponding to the RACH resource used by the downlink repeated transmission device 50; the transmission characteristic information corresponding to the DMRS port of the public PDSCH repeated transmission is the same as the transmission characteristic information corresponding to the DMRS port of the first PDCCH that schedules the public PDSCH repeated transmission; when the public PDSCH repeated transmission is In the case of specific transmission, the transmission characteristic information corresponding to the DMRS port of the public PDSCH repeated transmission is the same as the transmission characteristic information corresponding to the SSB or CSI-RS resource corresponding to the RACH resource selected by the downlink repeated transmission device 50; in the case where the public PDSCH repeated transmission is a repeated transmission scheduled by the third DCI, the transmission characteristic information corresponding to the public PDSCH repeated transmission and the DMRS port of the third downlink channel are both the same as the transmission characteristic information corresponding to the same SSB or CSI-RS resource. Among them, the above-mentioned specific transmission includes at least one of the following: transmission of PDSCH in reply to the initial transmission PUSCH carrying Msg 3, transmission of PDSCH in reply to the retransmission PUSCH carrying Msg 3, transmission of PDSCH in reply to the PUSCH of type-2 RACH process, transmission of PDSCH in reply to the PUSCH scheduled by fallback RAR UL grant, and transmission of PDSCH in reply to the retransmission PUSCH scheduled by fallback RAR UL grant; the above-mentioned third DCI is: RA-RNTI scrambled DCI corresponding to CFRA triggered by PDCCH order on SpCell; the above-mentioned third downlink channel is PDCCH order.

The downlink repetitive transmission device in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices other than a terminal. Exemplarily, the terminal may include but is not limited to the types of terminal 11 listed above, and other devices may be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

The downlink repeated transmission device provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 1 to 5 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

As shown in Figure 7, an embodiment of the present application also provides a communication device 60, including a processor 61 and a memory 62, and the memory 62 stores programs or instructions that can be executed on the processor 61. For example, when the communication device 60 is a terminal, the program or instruction is executed by the processor 61 to implement the various steps of the above-mentioned downlink repeated transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

The embodiment of the present application also provides a terminal, including a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps in the method embodiment shown in any one of Figures 1 to 5. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to the terminal embodiment and can achieve the same technical effect. Specifically, Figure 8 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

The terminal 100 includes but is not limited to: a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109 and at least some of the components of a processor 110.

Those skilled in the art will appreciate that the terminal 100 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 110 through a power management system, so as to implement functions such as managing charging, discharging, and power consumption management through the power management system. The terminal structure shown in FIG8 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently, which will not be described in detail here.

It should be understood that in the embodiment of the present application, the input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042, and the graphics processor 1041 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 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 107 includes a touch panel 1071 and at least one of other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 may include two parts: a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control key, a switch key, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

In the embodiment of the present application, after receiving downlink data from the network side device, the RF unit 101 can transmit the data to the processor 110 for processing; in addition, the RF unit 101 can send uplink data to the network side device. Generally, the RF unit 101 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

The memory 109 can be used to store software programs or instructions and various data. The memory 109 can mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area can store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.). The memory 109 may include a volatile memory or a non-volatile memory. 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 109 in the embodiments of the present application includes but is not limited to these and any other suitable types of memories.

The processor 110 may include one or more processing units; optionally, the processor 110 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 110.

The radio frequency unit 101 is used to receive indication information from a network side device; the indication information is used to indicate the repetition count type used when performing repeated transmission of a common PDSCH.

The processor 110 is configured to determine, according to a repetition count type, a time domain resource corresponding to repeated transmission of a common PDSCH.

The radio frequency unit 101 is further used to perform repeated transmission of the common PDSCH on time domain resources.

An embodiment of the present application provides a terminal. Since the terminal can determine the time domain resources corresponding to the repeated transmission of the public PDSCH according to the repetition count type used when performing repeated transmission of the public PDSCH indicated by the network side device, and perform repeated transmission of the public PDSCH on the time domain resources, that is, the terminal can transmit the public PDSCH multiple times on the time domain resources. Therefore, it can reduce the situation where the terminal does not receive the public PDSCH due to poor channel quality of the downlink channel, so as to reduce the situation where the terminal does not receive the random access response message, thereby reducing the time for the terminal to establish a wireless connection with the network side device. In this way, the delay of terminal communication can be reduced.

In some embodiments of the present application, the processor 110 is specifically configured to determine N consecutive time slots from a starting position as time domain resources when the repetition count type indicates counting based on physical time slots.

The above starting position is: the position of the common PDSCH repeated transmission starting transmission configured by the network side device; N is a positive integer.

In some embodiments of the present application, the processor 110 is specifically configured to determine, when the repetition count type indicates counting based on available time slots, a time slot including a target symbol from the M time slots starting from a starting position as a time domain resource.

Among them, the above-mentioned starting position is: the starting transmission position of the common PDSCH repeated transmission configured by the network side device; M is a positive integer; the above-mentioned target symbol satisfies at least one of the following: the symbol format of the target symbol is a downlink symbol or a flexible symbol; the target symbol and the symbol occupied by the synchronization signal block SSB do not overlap in the time domain; the target symbol and the symbol occupied by the control resource set CORESET where the first physical downlink control channel PDCCH scheduling the common PDSCH repeated transmission is located do not overlap in the time domain; the target symbol and the symbol corresponding to the sounding reference signal SRS transmission of the serving cell do not overlap in the time domain; the serving cell is different from the serving cell corresponding to the common PDSCH repeated transmission, and the serving cell is not configured with physical uplink shared channel PUSCH transmission or physical uplink control channel PUCCH transmission.

In some embodiments of the present application, the processor 110 is further configured to determine transmission characteristic information corresponding to a DMRS port for repeated transmission of a common PDSCH.

The above transmission characteristic information includes at least one of the following: average power; average delay; delay spread; Doppler frequency shift; Doppler spread; spatial reception parameters; and beam for repeated transmission of public PDSCH.

It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the downlink repeated transmission method in the method embodiment, and achieve the same or corresponding technical effect. To avoid repetition, it will not be repeated here.

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 downlink repeated transmission method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes Computer-readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disk or optical disk, etc. In some examples, the readable storage medium may be a non-transitory readable storage medium.

An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned downlink repeated transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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.

An embodiment of the present application further provides a computer program/program product, which is stored in a non-volatile storage medium. The computer program/program product is executed by at least one processor to implement the various processes of the above-mentioned downlink repeated transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

An embodiment of the present application further provides a downlink repeated transmission device, including a downlink repeated transmission device configured to execute each process of the above-mentioned downlink repeated transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including 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 one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment 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 reverse 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.

Through the description of the above implementation methods, 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 hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.

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 the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.

Claims (20)

A downlink repeated transmission method, comprising: The terminal receives indication information from a network side device; the indication information is used to indicate a repetition count type used when performing repeated transmission of a common physical downlink shared channel PDSCH; The terminal determines, according to the repetition count type, a time domain resource corresponding to the repeated transmission of the common PDSCH; The terminal repeatedly transmits the common PDSCH on the time domain resources. The method according to claim 1, wherein the terminal determines, according to the repetition count type, the time domain resources corresponding to the repeated transmission of the common PDSCH, comprising: In a case where the repetition count type indicates counting based on physical time slots, the terminal determines N consecutive time slots from a starting position as the time domain resources; The starting position is: the starting position of the common PDSCH repeated transmission configured by the network side device; N is a positive integer. The method according to claim 2, wherein In the case where the common PDSCH repetitive transmission is repetitive transmission within a time slot, the number N of the time slots is equal to the number of time slots corresponding to the time domain resources; In the case where the common PDSCH repetitive transmission is inter-time slot repetitive transmission, the number N of the N time slots is equal to the number of times the common PDSCH is repetitively transmitted. The method according to claim 1, wherein the terminal determines, according to the repetition count type, the time domain resources corresponding to the repeated transmission of the common PDSCH, comprising: In a case where the repetition count type indicates counting based on available time slots, the terminal determines a time slot including a target symbol from M time slots starting from a starting position as the time domain resource; Wherein, the starting position is: the position of the common PDSCH repeated transmission starting transmission configured by the network side device; M is a positive integer; The target symbol satisfies at least one of the following: The symbol format of the target symbol is a downlink symbol or a flexible symbol; The target symbol does not overlap with the symbol occupied by the synchronization signal block SSB in the time domain; The target symbol does not overlap in the time domain with the symbol occupied by the control resource set CORESET where the first physical downlink control channel PDCCH scheduling the repeated transmission of the common PDSCH is located; The target symbol does not overlap with the symbol corresponding to the sounding reference signal SRS transmission of the serving cell in the time domain; the serving cell is different from the serving cell corresponding to the common PDSCH repeated transmission, and the serving cell is not configured with physical uplink shared channel PUSCH transmission or physical uplink control channel PUCCH transmission. The method according to claim 4, wherein the number of the first PDCCH is at least one; and the first PDCCH satisfies at least one of the following: The first PDCCH is at least one PDCCH among the PDCCHs transmitted by repeated PDCCH transmission; When the number of the first PDCCHs is at least two, at least two of the first PDCCHs are PDCCHs transmitted by different sending and receiving nodes; The first PDCCH belongs to a CORESET of a serving cell to which the terminal has accessed; When the number of the first PDCCHs is at least two, at least two of the first PDCCHs are PDCCH candidates in different search space sets. The method according to any one of claims 1 to 5, wherein the terminal performs repeated transmission of the common PDSCH on the time domain resource, satisfying at least one of the following: In a case where the first downlink channel overlaps with the repeated transmission of the common PDSCH, the terminal preferentially performs the repeated transmission of the common PDSCH; When the terminal is in an idle state or an inactive state, if the second downlink channel and the repeated transmission of the common PDSCH do not overlap in the frequency domain and overlap in the time domain, the terminal allows transmission of the second downlink channel while performing repeated transmission of the common PDSCH; In the case where SSB transmission and the common PDSCH repeated transmission overlap in the frequency domain, the terminal Repeating the common PDSCH on the frequency domain resources corresponding to the repeated transmission of the common PDSCH; Among them, the frequency domain resources do not include the frequency domain unit corresponding to the time unit occupied by the SSB transmission. The method according to claim 6, wherein the first downlink channel is a PDSCH scheduled by first downlink control information DCI, and the first DCI is scrambled by any one of the following: Cell radio network temporary identifier C-RNTI; Modulation and coding scheme - cell radio network temporary identifier MCS-C-RNTI; Group Radio Network Temporary Identifier G-RNTI for multicast; G-RNTI for broadcast; MCCH-RNTI, a radio network temporary identifier of a multicast control channel; Group configuration scheduling radio network temporary identifier G-CS-RNTI; Configure the scheduling radio network temporary identifier CS-RNTI. The method according to claim 6, wherein the second downlink channel is a PDSCH scheduled by a second DCI, and the second DCI is scrambled by any one of the following: System information radio network temporary identifier SI-RNTI; Paging Radio Network Temporary Identifier P-RNTI; Random access radio network temporary identifier RA-RNTI; Temporary cell radio network temporary identifier TC-RNTI; Message B Radio Network Temporary Identifier Msg B-RNTI. The method according to any one of claims 1 to 5, wherein the method further comprises: The terminal determines transmission characteristic information corresponding to a demodulation reference signal DMRS port for repeated transmission of the common PDSCH; The transmission characteristic information includes at least one of the following: Average power; Average delay; Delay spread; Doppler shift; Doppler expansion; Space receiving parameters; The common PDSCH is repeatedly transmitted in a beam. The method according to claim 9, wherein the transmission characteristic information corresponding to the DMRS port for repeated transmission of the common PDSCH satisfies at least one of the following: In the case where the common PDSCH repetition transmission is Msg 2 PDSCH repetition transmission or Msg B PDSCH repetition transmission, the transmission characteristic information corresponding to the DMRS port of the common PDSCH repetition transmission is the same as the transmission characteristic information corresponding to the SSB or CSI-RS resource corresponding to the random access channel RACH resource used by the terminal; The transmission characteristic information corresponding to the DMRS port for repeated transmission of the common PDSCH is the same as the transmission characteristic information corresponding to the DMRS port of the first PDCCH for scheduling repeated transmission of the common PDSCH; In the case where the common PDSCH repeated transmission is a specific transmission, the transmission characteristic information corresponding to the DMRS port of the common PDSCH repeated transmission is the same as the transmission characteristic information corresponding to the SSB or CSI-RS resource corresponding to the RACH resource selected by the terminal; In the case where the common PDSCH repeated transmission is a repeated transmission scheduled by the third DCI, the transmission characteristic information corresponding to the common PDSCH repeated transmission and the DMRS port of the third downlink channel are the same as the transmission characteristic information corresponding to the same SSB or CSI-RS resource; The specific transmission includes at least one of the following: reply to the PDSCH transmission of the initial transmission PUSCH carrying Msg 3, reply to the PDSCH transmission of the retransmission PUSCH carrying Msg 3, reply to the PDSCH transmission of the PUSCH of the type-2 RACH process, reply to the PDSCH transmission of the PUSCH scheduled by the fallback random access response fallback RAR uplink scheduling authorization UL grant, reply to the PDSCH transmission of the retransmission PUSCH scheduled by the fallback RAR UL grant. transmission; The third DCI is: the RA-RNTI scrambled DCI corresponding to the non-contention random access CFRA triggered by the PDCCH command order on the special cell SpCell; the third downlink channel is the PDCCH order. A downlink repeated transmission device, wherein the downlink repeated transmission device comprises: a receiving module, a determining module and a transmitting module; The receiving module is used to receive indication information from a network side device; the indication information is used to indicate the repetition count type used when performing repeated transmission of a common PDSCH; The determining module is used to determine the time domain resources corresponding to the repeated transmission of the common PDSCH according to the repetition count type; The transmission module is used to perform repeated transmission of the common PDSCH on the time domain resources determined by the determination module. The downlink repeated transmission device according to claim 11, wherein: The determining module is specifically configured to determine, when the repetition counting type indicates counting based on physical time slots, N time slots consecutive from a starting position as the time domain resources; The starting position is: the starting position of the common PDSCH repeated transmission configured by the network side device; N is a positive integer. The downlink repeated transmission device according to claim 12, wherein: In the case where the common PDSCH repetitive transmission is repetitive transmission within a time slot, the number N of the time slots is equal to the number of time slots corresponding to the time domain resources; In the case where the common PDSCH repetitive transmission is inter-time slot repetitive transmission, the number N of the N time slots is equal to the number of times the common PDSCH is repetitively transmitted. The downlink repeated transmission device according to claim 11, wherein: The determining module is specifically configured to determine, when the repetition counting type indicates counting based on available time slots, a time slot including a target symbol from the M time slots starting from a starting position as the time domain resource; Wherein, the starting position is: the position of the common PDSCH repeated transmission starting transmission configured by the network side device; M is a positive integer; The target symbol satisfies at least one of the following: The symbol format of the target symbol is a downlink symbol or a flexible symbol; The target symbol does not overlap with the symbol occupied by the SSB in the time domain; The target symbol does not overlap in the time domain with the symbol occupied by the CORESET where the first PDCCH scheduling the repeated transmission of the common PDSCH is located; The target symbol does not overlap with the symbol corresponding to the SRS transmission of the serving cell in the time domain; the serving cell is different from the serving cell corresponding to the common PDSCH repeated transmission, and the serving cell is not configured with PUSCH transmission or PUCCH transmission. The downlink repeated transmission device according to any one of claims 11 to 14, wherein the transmission module performs the common PDSCH repeated transmission on the time domain resource, satisfying at least one of the following: In the case where the first downlink channel overlaps with the repeated transmission of the common PDSCH, the repeated transmission of the common PDSCH is performed preferentially; When the downlink repetitive transmission device is in an idle state or an inactive state, if the second downlink channel and the common PDSCH repetitive transmission do not overlap in the frequency domain and overlap in the time domain, it is allowed to transmit the second downlink channel while performing the common PDSCH repetitive transmission; In the case where the SSB transmission and the common PDSCH repeated transmission overlap in the frequency domain, the common PDSCH repeated transmission is performed on the frequency domain resources corresponding to the common PDSCH repeated transmission; Among them, the frequency domain resources do not include the frequency domain unit corresponding to the time unit occupied by the SSB transmission. A terminal comprises 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 downlink repeated transmission method as described in any one of claims 1 to 10 are implemented. A readable storage medium, wherein the readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the downlink repeated transmission method as described in any one of claims 1 to 10 are implemented. A chip, wherein the chip comprises a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the downlink repeated transmission method as described in any one of claims 1 to 10. A computer program product, wherein the computer program product is stored in a non-volatile storage medium, and the computer program product is executed by at least one processor to implement the steps of the downlink repeated transmission method as described in any one of claims 1 to 10. A downlink repetition transmission device, wherein the downlink repetition transmission device is configured to perform the steps of the downlink repetition transmission method according to any one of claims 1 to 10.