Method, device and terminal for indicating public PDSCH (Physical Downlink Shared Channel) repeated transmission

Abstract

The invention discloses an indication method and device for public PDSCH repeated transmission and a terminal, and belongs to the technical field of communication, and the method comprises the steps that the terminal determines the number of repeated transmission times of first downlink transmission based on first indication information; wherein the first indication information is used for indicating at least one repeated transmission frequency, and the first downlink transmission is public PDSCH repeated transmission.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a method, device and terminal for indicating repeated transmission of a public PDSCH. Background Art

[0002] 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 that of the uplink channel. However, in some application scenarios, such as high frequency, the base station transmission power will be close to the mobile phone transmission power, and the link quality of the downlink channel may not necessarily be higher than that of the uplink channel.

[0003] In non-terrestrial communication network scenarios, firstly, such as satellite communications, the downlink transmission power depends on the number of beams supported by the satellite at the same time. As the number of beams increases, the transmission power corresponding to each beam will decrease. Secondly, when the frequency band used for non-terrestrial communications overlaps with the terrestrial communication frequency band used in the covered land area, in order to reduce interference to the terrestrial network, the downlink transmission power of non-terrestrial communications needs to be reduced to a certain extent to meet the power flux density (PFD) requirements. In both cases, the downlink transmission power will be reduced, which may cause the quality of the downlink channel to decrease.

[0004] Therefore, in both the above-mentioned terrestrial network scenario and the non-terrestrial communication network scenario, the degradation of the channel quality of the downlink channel leads to insufficient network coverage. In order to improve the overall coverage of the network, some downlink channels can be enhanced. For example, the base station can enhance the downlink channel by repeatedly transmitting the downlink channel to obtain coverage gain. However, currently, for the public physical downlink shared channel (PDSCH), for example, the downlink channel used to carry the random access response does not support repeated transmission, so that the transmission of the downlink channel cannot meet the link budget requirements in the link budget.

[0005] Therefore, how to enhance the public PDSCH to improve the coverage capability of the network is an urgent problem to be solved. Summary of the invention

[0006] The embodiments of the present application provide a method, device and terminal for indicating repeated transmission of a common PDSCH, which can solve the problem of how to enhance the common PDSCH to improve the coverage capability of the network.

[0007] In a first aspect, a method for indicating repeated transmission of a common PDSCH is provided, the method comprising: a terminal determines the number of repeated transmissions of a first downlink transmission based on first indication information; wherein the first indication information is used to indicate at least one number of repeated transmissions, and the first downlink transmission is a common PDSCH repeated transmission.

[0008] In a second aspect, a device for indicating repeated transmission of a common PDSCH is provided, and the device for indicating repeated transmission of a common PDSCH comprises: a determination module. The determination module is used to determine the number of repeated transmissions of a first downlink transmission based on first indication information; wherein the first indication information is used to indicate at least one number of repeated transmissions, and the first downlink transmission is a common PDSCH repeated transmission.

[0009] 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.

[0010] In a fourth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is used to determine the number of repeated transmissions of a first downlink transmission based on first indication information; wherein the first indication information is used to indicate at least one number of repeated transmissions, and the first downlink transmission is a common PDSCH repeated transmission.

[0011] 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.

[0012] 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 method described in the first aspect.

[0013] 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 computer program / program product is executed by at least one processor to implement the steps of the method for indicating repeated transmission of a common PDSCH as described in the first aspect.

[0014] In an embodiment of the present application, the terminal can determine the number of repeated transmissions of the public PDSCH based on at least one repeated transmission number indicated by the first indication information, that is, support the repeated transmission of the public PDSCH through the indication of the repeated transmission number by the first indication information, so that the transmission of the downlink channel meets the link budget requirements in the link budget, improves the reliability of the public PDSCH transmission, and thus improves the coverage capability of the network. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application;

[0016] Figure 2This is one of the flow charts of a method for indicating repeated transmission of a common PDSCH provided in an embodiment of the present application;

[0017] Figure 3 This is a second flowchart of a method for indicating repeated transmission of a common PDSCH provided in an embodiment of the present application;

[0018] Figure 4 This is a flowchart of a method for indicating repeated transmission of a common PDSCH provided in an embodiment of the present application;

[0019] Figure 5 It is a structural schematic diagram of a common PDSCH repeated transmission indication device provided in an embodiment of the present application;

[0020] Figure 6 It is a schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application;

[0021] Figure 7 It is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] 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.

[0023] The terms "first", "second", etc. of the present 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 one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0024] The terms "at least one (item)", "at least one of" and the like in this application refer to any one, any two or a combination of more than two of the objects included therein. For example, at least one (item) of a, b, and c can be represented by: "a", "b", "c", "a and b", "a and c", "b and c" and "a, b and c", where a, b, and c can be single or multiple. Similarly, "at least two (items)" refers to two or more, and its meaning is similar to that of "at least one (item)".

[0025] 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.

[0026] 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.

[0027] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. 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 (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), an aircraft (flight vehicle), a vehicle user equipment (VUE), a shipborne equipment, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home equipment with wireless communication function, such as a refrigerator, a television, a washing machine 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 referred to as 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 may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a new radio Node B (NR Node B), an access point, a relay station (RBS), a serving base station (SBS), a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home Node B (HNB), a home evolved Node B (home evolved Node B), a transmission reception point (TRP) or other appropriate terms in the 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 taken as an example for introduction, and the specific type of the base station is not limited.

[0028] The following is an explanation of some concepts and / or terms involved in a method, device and terminal for indicating repeated transmission of a common PDSCH provided in an embodiment of the present application.

[0029] 1. Random access process and Msg2 / MsgB / Msg4

[0030] 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).

[0031] In the contention-based four-step random access process, the terminal first sends Msg1 to the network, including a preamble; after the network detects the preamble, it will send a Msg2 / RAR (random access response) message, including the number of the preamble detected by the network and the uplink wireless resources allocated to the terminal to send Msg3; after receiving Msg2, the terminal confirms that at least one of the numbers of the preamble carried in Msg2 is consistent with the number of the preamble sent by itself, and then sends Msg3 containing contention resolution information according to the resources indicated by the random access response (RAR); after receiving Msg3, the network will send Msg4 containing contention resolution information; after receiving Msg4, the terminal confirms that the resolution information is consistent with that sent by itself in Msg3, and the four-step random access is completed.

[0032] The network includes uplink grant (UL grant) information in the RAR to indicate the Msg3 PUSCH scheduling information, and includes information such as the Random Access Channel Preamble ID (RAPID), Temporary Cell Radio Network Temporary Identity (RNTI, TC-RNTI) and Timing Advance (TA). If the network does not receive the Msg3 Physical Uplink Shared Channel (PUSCH), it can schedule the retransmission of the Msg3 PUSCH in the TC-RNTI-scrambled Physical Downlink Control Channel (PDCCH).

[0033] For the contention random access process, different terminals randomly select preambles for transmission, so different terminals may select the same preamble to send on the same time-frequency radio resources (random access opportunity (RACH Occasion, RO) resources), which can be understood as a preamble conflict of the terminal. In this case, different terminals will receive the same RAR, and at this time, different terminals will transmit Msg3 PUSCH according to the scheduling information in the RAR UL grant. Regardless of whether Msg3 PUSCH is scheduled for repeated transmission (Msg3 repeated transmission was introduced in NR Rel-17), the network can only decode the PUSCH (including contention resolution information) sent by one terminal on the same Msg3 PUSCH scheduling resource, so 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.

[0034] If the contention resolution is unsuccessful, the terminal reselects RACH transmission resources, performs PRACH transmission, and makes the next random access attempt.

[0035] In NR Rel-16, the two-step random access process 2-step RACH was introduced. The first step is that the terminal sends MsgA to the network side. After receiving MsgA, the network side sends a MsgB message to the terminal. If the terminal does not receive MsgB within a certain period of time, the terminal will accumulate 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 2-step random access process to the 4-step random access process. The MsgB received by the terminal may be a success random access response (success RAR), at which point the 2-step RACH ends. It may also be a fallback random access response (fallback RAR), at which point the terminal will fall back to the 4-step RACH process. MsgA includes MsgA preamble and MsgA PUSCH. The preamble is sent on the RO for 2-step RACH, and the PUSCH is sent on the MsgA PUSCH resources associated with the MsgA preamble and RO. MsgA PUSCH resources are a set of PUSCH resources configured relative to each Physical Random Access Channel (PRACH) time slot, including time-frequency resources and demodulation reference signal (DMRS) resources.

[0036] 2. Determination of Msg2 / MsgB / Msg4 PDSCH transmission resources

[0037] Msg2 PDSCH is a downlink transmission scheduled by downlink control information (DCI) scrambled by random access (RA)-RNTI CRC;

[0038] MsgB PDSCH is a DCI-scheduled downlink transmission using MsgB-RNTI scrambled cyclic redundancy check (CRC).

[0039] Msg4 PDSCH is a downlink transmission scheduled by DCI with TC-RNTI scrambled CRC.

[0040] (1) Time Domain Resource Allocation (TDRA):

[0041] Table 1

[0042]

[0043] Among them, the meaning of the above Table 1 indicates: for Msg2 / MsgB / Msg4 PDSCH, if PDSCH-TimeDomainAllocationList (time domain allocation table) is configured in the high-level parameter PDSCH-ConfigCommon, its time domain resource allocation is given by PDSCH-Time Domain Allocation List; otherwise, it is given by the default (Default) A, and the default A is the following for the normal cyclic prefix (Normal Cyclic Prefix, NCP) and extended cyclic prefix (ExtendedCP, ECP) ​​cases, PDSCH TDRA default table A (which may be called TDRA table A) is given, which are the following Tables 2 and 3 respectively.

[0044] Table 2: Default PDSCH time domain resource allocation A for normal CP

[0045]

[0046] Table 3: Default PDSCH time domain resource allocation A for extended CP

[0047]

[0048] Among them, it can be seen from the information in Table 2 and Table 3 above that a set of K0, S and L can be determined by row index (row index, scheduled DCI indication), DMRS-TypeA-Position, and PDSCH mapping type. Among them, K0 represents the time slot offset between the scheduled DCI and the corresponding PDSCH, S represents the starting symbol of the time domain resource of the corresponding PDSCH transmission, and L represents the number of symbols occupied by the time domain resource of the corresponding PDSCH transmission.

[0049] (2) Frequency Domain Resource Allocation

[0050] The NR protocol defines two frequency domain resource allocation methods for the PDSCH channel: type 0 and type 1. When the terminal assumes that the scheduling information is carried by DCI format 1_0 / 4_0 / 4_1, the frequency domain resource allocation method of type 1 is used.

[0051] For PDSCH scheduled by PDCCH on any type of common search space, regardless of which bandwidth part (Bandwidth Part, BWP) is the active BWP, the resource block (RB) numbering starts from the lowest RB index on the bandwidth of the control resource set (Control Resource Set, CORESET) of the received DCI; otherwise, the RB numbering starts from the lowest RB index of the determined downlink BWP.

[0052] Downlink frequency domain resource type 1: The resource block assignment information indicates to the terminal a set of interleaved or non-interleaved virtual resource blocks (VRBs) continuously allocated on the initial bandwidth. For DCI format 1_0 decoded on any type of common search space, if the cell is configured with CORESET 0, the initial bandwidth is the bandwidth of CORESET 0; if the cell is not configured with CORESET 0, the initial bandwidth is the bandwidth corresponding to the initial downlink BWP.

[0053] The indication field of downlink frequency domain resource type 1 is mainly composed of a resource indication value (RIV), corresponding to a starting VRB index RBstart and the number of consecutively allocated RBs LRBs. The RIV is determined by the following formula:

[0054] If then

[0055]

[0056] else

[0057]

[0058] Where L RBs ≥1 and no more than

[0059] 3. Determination of Msg2 / MsgB / Msg4 PDSCH transmission parameters

[0060] (1) Physical Resource Block (PRB) Binding

[0061] The terminal assumes the precoding granularity P′ in the frequency domain BWP,i is a continuous RB, and P′ BWP,iCan be equal to a value in {2,4,wideband}.

[0062] If P′ BWP,i If it is determined as "wideband", the terminal does not expect to be scheduled for PDSCH transmission on non-contiguous PRBs, and the terminal can assume that resources under the same transmission configuration indication (Transmission Configuration Indication, TCL) state or the same quasi-co-location (Quasi-Co-Location, QCL) assumption use the same precoding.

[0063] P′ BWP,i If it is determined to be a value in {2,4}, then BWP i is P′ BWP,i The coding resource block groups (PRG) are divided into consecutive PRBs, and the actual number of consecutive PRBs in each PRG can be one or more.

[0064] Similarly, the terminal can assume that the same precoding is used on any consecutive PRBs in the same PRG;

[0065] Furthermore, the size of the first PRG is The size of the final PRG is:

[0066] if

[0067] if P′ BWP,i .

[0068] If the terminal is scheduled to transmit PDSCH via DCI format 1_0 / 4_0, the terminal assumes P′ BWP,i is 2PRBs.

[0069] (2) Modulation order:

[0070] For the PDSCH (msg2 PDSCH) scheduled by DCI using RA-RNTI scrambling, the terminal does not expect its modulation order Qm>2.

[0071] For MsgB / Msg4 PDSCH, the protocol does not make special provisions for its modulation order. The conventional process is used to determine the modulation and coding scheme (MCS) level and thus the modulation order through relevant parameter indication.

[0072] (3) Determination of PDSCH Transport Block Size (TBS):

[0073] The TBS calculation process is as follows:

[0074] Step 1: Calculate the number of resource elements (RE) available in a time slot;

[0075] 1) Calculate the number of REs available in a PRB: in Indicates that one PRB in the frequency domain contains 12 subcarriers; is the number of PDSCH symbols scheduled in this time slot; The number of REs used for DMRS in one PRB in the frequency domain and in a symbol scheduled in the time domain; It is configured by the xOverhead field in the high-level parameter PUSCH-ServingCellConfig, taking into account the Channel State Information-Reference Signal (CSI-RS), CORESET overhead, etc. The default value is 0, and the configurable value is {6,12,18}. For RA-RNTI or MsgB-RNTI scrambled DCI-scheduled PDSCH (msg2 / msgB PDSCH) transmission, Set to 0.

[0076] Calculate the total number of REs available for PDSCH transmission: N RE =min(156,N' RE )·n PRB , where n PRB is the total number of PRBs allocated to the terminal.

[0077] Step 2: Calculate the number of intermediate information bits: N info =N RE ·R·Q m ·υ (where the corresponding modulation order Q is determined by the MCS level m , target bit rate R, υ is the number of transmission layers).

[0078] When N info When ≤3824, use Step 3;

[0079] Otherwise, go to Step 4.

[0080] Step 3: When N info ≤3824,

[0081] Quantize the number of intermediate information bits in

[0082] Find the value not less than N' in Table 4 below info The most recent TBS.

[0083] Table 4: TBS for N info ≤3824

[0084] Index TBS Index TBS Index TBS Index TBS 1 24 31 336 61 1288 91 3624 2 32 32 352 62 1320 92 3752 3 40 33 368 63 1352 93 3824 4 48 34 384 64 1416 5 56 35 408 65 1480 6 64 36 432 66 1544 7 72 37 456 67 1608 8 80 38 480 68 1672 9 88 39 504 69 1736 10 96 40 528 70 1800 11 104 41 552 71 1864 12 112 42 576 72 1928 13 120 43 608 73 2024 14 128 44 640 74 2088 15 136 45 672 75 2152 16 144 46 704 76 2216 17 152 47 736 77 2280 18 160 48 768 78 2408 19 168 49 808 79 2472 20 176 50 848 80 2536 21 184 51 888 81 2600 22 192 52 928 82 2664 23 208 53 984 83 2728 24 224 54 1032 84 2792 25 240 55 1064 85 2856 26 256 56 1128 86 2976 27 272 57 1160 87 3104 28 288 58 1192 88 3240 29 304 59 1224 89 3368 30 320 60 1256 90 3496

[0085] Step 4: When N info >3824 hours,

[0086] Quantifying the middle number in,

[0087] If the target bit rate R≤1 / 4,

[0088] in

[0089] Otherwise (R>1 / 4),

[0090] If N' info >8424, in

[0091] otherwise,

[0092] For the PDSCH (msg4 PDSCH) scheduled using TC-RNTI scrambled DCI format 1_0, the TBS determination process is consistent with the above TBS determination process.

[0093] For PDSCH (msg2 / msgBPDSCH) scheduled with RA-RNTI and MsgB-RNTI scrambled DCI format 1_0, the TBS determination process is basically the same as the above TBS determination process, except that the following modifications are made in Step 2: Introducing the scaling factor S, the calculation of the number of intermediate information bits can be scaled: N info =S·N RE ·R·Q m ·υ, where the supported factors are indicated by the transport block (TB) scaling field in the DCI, and the corresponding relationship is shown in Table 5 below. N of paging RNTI (P-RNTI), RA-RNTI and MsgB-RNTI info Scaling factor.

[0094] Table 5

[0095] TB scaling field Scaling factor S 00 1 01 0.5 10 0.25 11

[0096] The following, in combination with the accompanying drawings, describes in detail the method for indicating repeated transmission of the common PDSCH provided in the embodiments of the present application through some embodiments and their application scenarios.

[0097] The embodiments of the present application can be applied to non-terrestrial network (NTN) or terrestrial network (TN) scenarios to enhance Msg2 / MsgB / Msg4 PDSCH, and can be applied to all downlink channels before the terminal enters the connected state, such as paging PDSCH.

[0098] An embodiment of the present application provides a method for indicating repeated transmission of a public PDSCH. The terminal can determine the number of repeated transmissions of the public PDSCH based on at least one number of repeated transmissions indicated by first indication information. That is, the repeated transmission of the public PDSCH is supported by indicating the number of repeated transmissions through the first indication information, so that the transmission of the downlink channel meets the link budget requirements in the link budget, thereby improving the reliability of the public PDSCH transmission and thus improving the coverage capability of the network.

[0099] The execution subject of the method for indicating the repeated transmission of a common PDSCH provided in some embodiments of the present application may be a terminal, or a functional module or entity in the terminal, or a device for indicating the repeated transmission of a common PDSCH. The following takes the method for indicating the repeated transmission of a common PDSCH performed by a terminal as an example to illustrate the technical solutions provided in some embodiments of the present application.

[0100] The embodiment of the present application provides a method for indicating repeated transmission of a common PDSCH. Figure 2 FIG. 1 is a flow chart showing a method for indicating repeated transmission of a common PDSCH provided in an embodiment of the present application. Figure 2 As shown, the method for indicating repeated transmission of a common PDSCH provided in an embodiment of the present application may include the following steps 201 and 202.

[0101] Step 201: The terminal obtains first indication information.

[0102] Optionally, in an embodiment of the present application, the above-mentioned first indication information can be configured semi-statically, or dynamically indicated, or specified by a protocol.

[0103] Step 202: The terminal determines the number of repeated transmissions of the first downlink transmission based on the first indication information.

[0104] In an embodiment of the present application, the first indication information is used to indicate at least one number of repeated transmissions, and the first downlink transmission is a common PDSCH repeated transmission.

[0105] It should be noted that the common PDSCH repetition transmission described in this application may include one or more PDSCH repetition transmissions that the terminal needs to receive before entering the connected state, such as one or more PDSCH repetition transmissions in Msg2 PDSCH, MsgB PDSCH and Msg4 PDSCH. Common PDSCH repetition transmission can also be called common PDSCH repetition transmission, that is, this application supports repetitive transmission of common PDSCH.

[0106] The MsgB PDSCH described in the present application includes a success random access response (success RAR) and also includes a fallback random access response (fallback RAR).

[0107] The RAR described in the present application may refer to a RAR message in Msg2 in a four-step random access channel (4-step RACH), or may refer to a success RAR or fallback RAR in a two-step random access channel (2-step RACH).

[0108] The Msg2 / MsgB / Msg4 PDSCH repetition described in the present application may refer to any one or more of the three channels supporting repeated transmission, which may also be referred to as Msg2 / MsgB / Msg4 PDSCH repetition, or simply Msg2 / MsgB / Msg4 repetition.

[0109] It can be understood that the first indication information indicates a number of repeated transmissions or a set of repeated transmissions. Optionally, the first indication information may directly indicate a number of repeated transmissions; or, the first indication information indicates a number of repeated transmissions in an existing set of repeated transmissions, which is pre-indicated by other indication information or agreed upon by a protocol.

[0110] Optionally, in an embodiment of the present application, when the first indication information indicates a number of repeated transmissions, the first indication information is configured semi-statically or dynamically.

[0111] Optionally, in an embodiment of the present application, when the above-mentioned first indication information indicates a number of repeated transmissions, the number of repeated transmissions is the number of repeated transmissions of the above-mentioned first downlink transmission.

[0112] Optionally, in an embodiment of the present application, when the first indication information indicates a set of repeated transmission times, the first indication information is specified through a semi-static configuration or protocol, and the set of repeated transmission times includes at least two repeated transmission times.

[0113] Optionally, in an embodiment of the present application, when the first indication information indicates a set of repeated transmission times, the repeated transmission times of the first downlink transmission are determined by second indication information, and the second indication information is used to indicate a repeated transmission number in the set of repeated transmission times, and the repeated transmission number is the repeated transmission number of the first downlink transmission.

[0114] It can be understood that when the above-mentioned first indication information indicates a set of repeated transmission times, whether the set of repeated transmission times is semi-statically configured or stipulated by the protocol, the second indication information can further indicate a repeated transmission number in the repeated transmission number set in the first indication information, and the repeated transmission number is the repeated transmission number of the above-mentioned first downlink transmission.

[0115] Optionally, in an embodiment of the present application, the second indication information is configured semi-statically or dynamically.

[0116] In one embodiment, when the above-mentioned set of repeated transmission times is configured semi-statically, the above-mentioned second indication information can be dynamically indicated.

[0117] In another manner, when the above-mentioned set of repeated transmission times is specified by a protocol, the above-mentioned second indication information can be configured semi-statically.

[0118] It should be noted that in the embodiment of the present application, the semi-static configuration or dynamic indication is configured or issued by the network side device. For example, the above-mentioned first indication information is semi-statically configured or dynamically indicated by the network side device, and the above-mentioned second indication information is semi-statically configured or dynamically indicated by the network side device.

[0119] Optionally, in an embodiment of the present application, the scheduling DCI corresponding to the above-mentioned common PDSCH repeated transmission includes third indication information, and the third indication information is used to enable or disable the number of repeated transmissions configured semi-statically or dynamically indicated.

[0120] That is, after a repetition number is semi-statically configured or dynamically indicated, the repetition number can be used or not through the scheduling DCI corresponding to the common PDSCH repetition transmission. If used, the common PDSCH repetition transmission is performed; if not used, the common PDSCH repetition transmission is not performed.

[0121] It should be noted that the scheduling DCI corresponding to the repeated transmission of the common PDSCH described in the embodiment of the present application can be understood as: DCI for scheduling repeated transmission of the common PDSCH, for example, for Msg2 PDSCH, its corresponding DCI refers to the DCI for scheduling Msg2PDSCH.

[0122] Optionally, in an embodiment of the present application, the semi-static indication may be indicated by a system message (System Information, SI) or a radio resource control (Radio Resource Control, RRC) message. The system message includes at least one of a master information block (Master Information Block, MIB) and a system information block (System Information Block, SIB).

[0123] It should be noted that the semi-static indication described in the embodiment of the present application is applicable to both the first indication information and the second indication information, that is, at least one of the first indication information and the second indication information is indicated through a system message or an RRC message.

[0124] Optionally, in the embodiment of the present application, the specific manner in which the above-mentioned semi-static indication is indicated by an RRC message includes any one of the following:

[0125] (1) Introduce a new RRC parameter in PDSCH-ConfigCommon to indicate the number of repetitions of common PDSCH retransmissions;

[0126] (2) When indicating the time domain resource allocation, the parameter PDSCH-TimeDomainAllocationList in PDSCH-ConfigCommon adds an indication of the number of repetition transmissions of the common PDSCH repetition transmissions.

[0127] Optionally, in an embodiment of the present application, the above-mentioned dynamic indication is indicated by repeated transmission of a common PDSCH; or, the above-mentioned dynamic indication is indicated by a scheduling DCI corresponding to repeated transmission of a common PDSCH.

[0128] It should be noted that the dynamic indication described in the embodiments of the present application is applicable to both the first indication information and the second indication information, that is, at least one of the first indication information and the second indication information is indicated by repeated transmission of the common PDSCH, or by the scheduling DCI corresponding to the repeated transmission of the common PDSCH.

[0129] Optionally, in an embodiment of the present application, the above-mentioned dynamic indication is indicated by a scrambling sequence of repeated transmission of a common PDSCH.

[0130] Optionally, in an embodiment of the present application, when the above-mentioned dynamic indication is indicated by an scrambling sequence of a common PDSCH repeated transmission, the above-mentioned common PDSCH repeated transmission is scrambled by a first identifier, which corresponds to a repetition factor or an index in a set of repeated transmission times to determine the above-mentioned repeated transmission times.

[0131] It can be understood that the common PDSCH repeated transmission is scrambled by different identifiers (ID), and different IDs can correspond to different repetition factors (repetition factors) or indices in the set of repeated transmission times to determine the above-mentioned number of repeated transmissions, that is, the number of repeated transmissions of the above-mentioned first downlink transmission.

[0132] Optionally, in an embodiment of the present application, when the above-mentioned dynamic indication is indicated by an scrambling sequence of a common PDSCH repeated transmission, the sequence of the DMRS of the above-mentioned common PDSCH repeated transmission or an identifier of the initial value of the generated sequence corresponds to a repetition factor or an index in a set of repeated transmission times to determine the above-mentioned repeated transmission times.

[0133] It can be understood that by using different sequences of DMRS of the repeatedly transmitted public PDSCH or IDs of the generated sequence initial values, different sequences or different IDs can correspond to different repetition factors or indexes in the set of repeated transmission times to determine the above-mentioned number of repeated transmissions, that is, the number of repeated transmissions of the above-mentioned first downlink transmission.

[0134] Optionally, in the embodiment of the present application, the above dynamic indication is indicated by any of the following items:

[0135] Indicated by scrambling the RNTI of the scheduling DCI;

[0136] Indicated by the DMRS sequence of the PDCCH where the DCI is scheduled;

[0137] Indicated by a field in the scheduling DCI.

[0138] Optionally, in an embodiment of the present application, when the above-mentioned dynamic indication is indicated by the RNTI of the encrypted scheduling DCI, the above-mentioned scheduling DCI is encrypted by a first RNTI, and the first RNTI corresponds to a repetition factor or an index in a set of repeated transmission times to determine the above-mentioned repeated transmission times.

[0139] It can be understood that different RNTIs are used to scramble the DCI for scheduling repeated transmission of the public PDSCH. Different RNTIs can correspond to different repetition factors or indices in a set of repeated transmission times to determine the above-mentioned number of repeated transmissions, that is, the number of repeated transmissions of the above-mentioned first downlink transmission.

[0140] Optionally, in the embodiment of the present application, the scheduling DCI scrambled by the first RNTI includes any of the following:

[0141] The first DCI format with CRC scrambled by TC-RNTI (DCI format 1_0 with CRC scrambled by TC-RNTI);

[0142] The first DCI format with CRC scrambled by RA-RNTI (DCI format 1_0 with CRC scrambled by RA-RNTI);

[0143] The first DCI format with CRC scrambled by MsgB-RNTI (DCI format 1_0 with CRC scrambled by MsgB-RNTI).

[0144] Optionally, in an embodiment of the present application, when the above-mentioned dynamic indication is indicated through a field in the scheduling DCI, the above-mentioned scheduling DCI indicates a repetition factor or an index in a set of repeated transmission times through a first indication field to determine the above-mentioned repeated transmission times, and the first indication field is an existing field in the scheduling DCI or a newly added indication field.

[0145] Exemplarily, a field in the scheduling DCI is further used to indicate the selection of one of the repetition transmission times in the above-mentioned repetition transmission times set, which is the repetition transmission times of the above-mentioned first downlink transmission. Alternatively, a certain option of the PDSCH-TimeDomainAllocationList is indicated by scheduling the TDRAfield in the DCI, and the repetitionfactor under the option is used as the repetition transmission times of the above-mentioned first downlink transmission. In some embodiments, a PDSCH TDRAtable (also called TDRA list) that supports common PDSCH repetition transmission is specially configured through a system message. For example, for each option of the configured TDRAlist, a repetition factor is defined.

[0146] It can be understood that by adding a new indication field in the DCI for scheduling the repeated transmission of the common PDSCH, which is used to indicate different repetition factors or indices in the set of repeated transmission times, the above-mentioned number of repeated transmissions, that is, the number of repeated transmissions of the above-mentioned first downlink transmission, is determined. Alternatively, by redefining the first field (the existing field) in the DCI for scheduling the repeated transmission of the common PDSCH, which is used to correspond to different repetition factors or indices in the set of repeated transmission times, the above-mentioned number of repeated transmissions, that is, the number of repeated transmissions of the above-mentioned first downlink transmission, is determined.

[0147] Optionally, in the embodiment of the present application, when the first indication field is an existing field in the scheduling DCI:

[0148] (1) For the scheduling DCI corresponding to the downlink data channel used to carry Msg2 or MsgB, the first indication field includes at least one of the following: a modulation and coding scheme field, a TB scaling field, and a reserved bits field;

[0149] (2) For the scheduling DCI corresponding to the downlink data channel used to carry Msg4, the above-mentioned first indication field includes at least one of the following: a modulation and coding mode field, a new data indicator field, a redundancy version field, a downlink assignment index field, an indication of the timing between the downlink data channel and the hybrid automatic repeat request (Hybrid Automatic Repeat reQuest, HARQ) (PDSCH-to-HARQ_feedback timing indicator) field, and a reserved bit field.

[0150] It should be noted that the first indication field here includes at least one of the following meanings: it can be indicated by partial bits or all bits of one of these fields, or partial bits or all bits of different fields can be jointly indicated.

[0151] Optionally, in an embodiment of the present application, when the first indication information is specified by a protocol: the first indication information directly indicates a set of repeated transmission times specified by the protocol; or, the first indication information is the repeated transmission times indication information in the PDSCH time domain resource allocation table, and the repeated transmission times indication information is used to indicate the set of repeated transmission times. In this way, the repeated transmission times set is specified by the protocol without adding additional signaling overhead.

[0152] Optionally, in an embodiment of the present application, the set of repeated transmission times indicated by the above-mentioned repeated transmission time indication information is indicated by modifying the default PDSCH time domain resource allocation table.

[0153] It should be noted that the above default PDSCH time domain resource allocation table can refer to Table 2 and Table 3 in the above embodiment.

[0154] Optionally, in the embodiment of the present application, the above-mentioned modification method of modifying the default PDSCH time domain resource allocation table may include at least one of the following:

[0155] (1) Add an information column to indicate the number of repeated transmissions;

[0156] (2) Extending the table, that is, adding some row indexes below the default PDSCH time domain resource allocation table, then one or more bits need to be added to indicate the new row index;

[0157] (3) Delete some row indexes and increase the number of repeated transmissions supported by the remaining row indexes.

[0158] Optionally, in an embodiment of the present application, the set of repeated transmission times indicated by the above-mentioned repeated transmission time indication information is indicated by defining a newly added PDSCH time domain resource allocation table supporting repeated transmission.

[0159] It should be noted that whether to use the default PDSCH time domain resource allocation table or the newly added PDSCH time domain resource allocation table supporting repeated transmission can be determined by RRC parameters or whether the terminal supports common PDSCH repeated transmission.

[0160] An embodiment of the present application provides a method for indicating repeated transmission of a public PDSCH. The terminal can determine the number of repeated transmissions of the public PDSCH based on at least one number of repeated transmissions indicated by first indication information. That is, the repeated transmission of the public PDSCH is supported by indicating the number of repeated transmissions through the first indication information, so that the transmission of the downlink channel meets the link budget requirements in the link budget, thereby improving the reliability of the public PDSCH transmission and thus improving the coverage capability of the network.

[0161] Optionally, in the embodiment of the present application, combined with Figure 2 ,like Figure 3 As shown, after the above step 202, the method for indicating repeated transmission of a common PDSCH provided in an embodiment of the present application further includes the following step 301.

[0162] Step 301: The terminal determines whether repeated transmission is enabled for the first downlink transmission based on fourth indication information.

[0163] Optionally, in an embodiment of the present application, the fourth indication information is the first indication information or other indication information, and the other indication information is used to indicate enabling or disabling repeated transmission of the first downlink transmission.

[0164] The terminal determines whether repeated transmission is enabled for the first downlink transmission based on the first indication information in the following manner: when the first indication information configures the number of repeated transmissions of the first downlink transmission, the terminal considers that the network enables repeated transmission of the first downlink transmission.

[0165] It can be understood that this is an implicit indication method, that is, as long as the number of repeated transmissions is configured, the terminal considers that the repeated transmission of the first downlink transmission is enabled. For example, when SIB1 configures the candidate number of repeated transmissions for common PDSCH repeated transmissions, the terminal considers that the network has enabled common PDSCH repeated transmissions.

[0166] The terminal determines whether the first downlink transmission enables repeated transmission based on other indication information, where the other indication information is any one of the following:

[0167] An indication information semi-statically configured on the network side to indicate enabling or disabling repeated transmission of the first downlink transmission;

[0168] An indication message dynamically indicated by the network side to indicate whether to enable or disable repeated transmission of the first downlink transmission.

[0169] It can be understood that the indication information here is an explicit indication method, for example, the network configures CommonPDSCHRepetition-r18 in SIB1 to indicate whether common PDSCH repetition transmission is enabled or disabled.

[0170] For dynamic indication of enabling or disabling repeated transmission of the first downlink transmission, for example, when the network configures a number of repeated transmissions in the SIB, the enabling / disabling of common PDSCH repeated transmission can be indicated through dynamic indication in the DCI, or different RNTI-scrambled DCI, or through different scrambling code sequences.

[0171] Optionally, in the embodiment of the present application, the fourth indication information is configured semi-statically, or dynamically, or by protocol. It should be noted that for the semi-static configuration, dynamic indication, protocol, etc., please refer to the description in the above embodiment, which will not be repeated here.

[0172] The embodiment of the present application also provides a method for indicating repeated transmission of a common PDSCH. Figure 4FIG. 1 is a flow chart showing a method for indicating repeated transmission of a common PDSCH provided in an embodiment of the present application. Figure 4 As shown, the method for indicating repeated transmission of a common PDSCH provided in an embodiment of the present application may include the following steps 401 and 402.

[0173] Step 401: The terminal obtains fourth indication information.

[0174] Optionally, in an embodiment of the present application, the fourth indication information may be semi-statically configured, dynamically indicated, or specified by a protocol.

[0175] Step 402: The terminal determines whether repeated transmission is enabled for the first downlink transmission based on the fourth indication information.

[0176] Optionally, in an embodiment of the present application, the fourth indication information is the first indication information or other indication information, and the other indication information is used to indicate enabling or disabling repeated transmission of the first downlink transmission.

[0177] The terminal determines whether repeated transmission is enabled for the first downlink transmission based on the first indication information in the following manner: when the first indication information configures the number of repeated transmissions of the first downlink transmission, the terminal considers that the network enables repeated transmission of the first downlink transmission.

[0178] It can be understood that this is an implicit indication method, that is, as long as the number of repeated transmissions is configured, the terminal considers that the repeated transmission of the first downlink transmission is enabled. For example, when SIB1 configures the candidate number of repeated transmissions for common PDSCH repeated transmissions, the terminal considers that the network has enabled common PDSCH repeated transmissions.

[0179] It should be noted that, for the description of the first indication information here, reference can be made to the description in the above embodiment, which will not be repeated here.

[0180] The terminal determines whether the first downlink transmission enables repeated transmission based on other indication information, where the other indication information is any one of the following:

[0181] An indication information semi-statically configured on the network side to indicate enabling or disabling repeated transmission of the first downlink transmission;

[0182] An indication message dynamically indicated by the network side to indicate whether to enable or disable repeated transmission of the first downlink transmission.

[0183] It can be understood that the indication information here is an explicit indication method, for example, the network configures CommonPDSCHRepetition-r18 in SIB1 to indicate whether common PDSCH repetition transmission is enabled or disabled.

[0184] For dynamic indication of enabling or disabling repeated transmission of the first downlink transmission, for example, when the network configures a number of repeated transmissions in the SIB, the enabling / disabling of common PDSCH repeated transmission can be indicated through dynamic indication in the DCI, or different RNTI-scrambled DCI, or through different scrambling code sequences.

[0185] Optionally, in the embodiment of the present application, when the fourth indication information is configured semi-statically, the semi-static indication may be indicated by a system message (SI) or an RRC message, wherein the system message includes at least one of MIB and SIB.

[0186] Optionally, in the embodiment of the present application, the specific manner in which the above-mentioned semi-static indication is indicated by an RRC message includes any one of the following:

[0187] (1) Introduce a new RRC parameter in PDSCH-ConfigCommon, which is specifically used to indicate whether to enable or disable repeated transmission of the first downlink transmission;

[0188] (2) The parameter PDSCH-TimeDomainAllocationList (PDSCH time domain allocation list) in PDSCH-ConfigCommon enables or disables the indication of repeated transmission of the first downlink transmission when indicating the time domain resource allocation.

[0189] Optionally, in an embodiment of the present application, when the fourth indication information is dynamically indicated, the dynamic indication is indicated by repeated transmission of a common PDSCH; or, the dynamic indication is indicated by a scheduling DCI corresponding to repeated transmission of a common PDSCH.

[0190] Optionally, in an embodiment of the present application, the above-mentioned dynamic indication is indicated by a scrambling sequence of repeated transmission of a common PDSCH.

[0191] Optionally, in an embodiment of the present application, when the above-mentioned dynamic indication is indicated by a scrambling sequence of a common PDSCH repeated transmission, the above-mentioned common PDSCH repeated transmission is scrambled by a first identifier, and the first identifier corresponds to enabling or disabling repeated transmission.

[0192] Optionally, in an embodiment of the present application, when the above-mentioned dynamic indication is indicated by an scrambling sequence of a common PDSCH repeated transmission, the sequence of the DMRS of the above-mentioned common PDSCH repeated transmission or an identifier of an initial value of a generated sequence corresponds to enabling or disabling repeated transmission.

[0193] Optionally, in the embodiment of the present application, the above dynamic indication is indicated by any of the following items:

[0194] Indicated by scrambling the RNTI of the scheduling DCI;

[0195] Indicated by the DMRS sequence of the PDCCH where the DCI is scheduled;

[0196] Indicated by a field in the scheduling DCI.

[0197] Optionally, in an embodiment of the present application, when the above-mentioned dynamic indication is indicated by scrambling the RNTI of the scheduled DCI, the above-mentioned scheduled DCI is scrambled by a first RNTI, and the first RNTI corresponds to enabling or disabling repeated transmission.

[0198] Optionally, in the embodiment of the present application, the scheduling DCI scrambled by the first RNTI includes any of the following:

[0199] The first DCI format with CRC scrambled by TC-RNTI (DCI format 1_0 with CRC scrambled by TC-RNTI);

[0200] The first DCI format with CRC scrambled by RA-RNTI (DCI format 1_0 with CRC scrambled by RA-RNTI);

[0201] The first DCI format with CRC scrambled by MsgB-RNTI (DCI format 1_0 with CRC scrambled by MsgB-RNTI).

[0202] Optionally, in an embodiment of the present application, when the above-mentioned dynamic indication is indicated through a field in the scheduling DCI, the above-mentioned scheduling DCI indicates enabling or disabling repeated transmission through a first indication field, and the first indication field is an existing field in the scheduling DCI or a newly added indication field.

[0203] Optionally, in the embodiment of the present application, when the first indication field is an existing field in the scheduling DCI:

[0204] (1) For the scheduling DCI corresponding to the downlink data channel used to carry Msg2 or MsgB, the first indication field includes at least one of the following: a modulation and coding scheme field, a TB scaling field, and a reserved bits field;

[0205] (2) For the scheduling DCI corresponding to the downlink data channel used to carry Msg4, the above-mentioned first indication field includes at least one of the following: a modulation and coding mode field, a new data indicator field, a redundancy version field, a downlink assignment index field, an indication of the timing between the downlink data channel and HARQ (PDSCH-to-HARQ_feedback timing indicator) field, and a reserved bit field.

[0206] It should be noted that the first indication field here includes at least one of the following meanings: it can be indicated by partial bits or all bits of one of these fields, or partial bits or all bits of different fields can be jointly indicated.

[0207] Optionally, in an embodiment of the present application, when the first indication information is specified by a protocol, the first indication information is indication information for enabling or disabling repeated transmission in a PDSCH time domain resource allocation table. In this way, repeated transmission of the first downlink transmission is enabled or disabled by the protocol specification without adding additional signaling overhead.

[0208] Optionally, in an embodiment of the present application, the above-mentioned indication information for enabling or disabling repeated transmission is indicated by modifying the default PDSCH time domain resource allocation table.

[0209] Optionally, in the embodiment of the present application, the above-mentioned modification method of modifying the default PDSCH time domain resource allocation table may include at least one of the following:

[0210] (1) Add an information column to indicate whether to enable or disable repeated transmission of the first downlink transmission;

[0211] (2) Extending the table, that is, adding some row indexes below the default PDSCH time domain resource allocation table, then one or more bits need to be added to indicate the new row index;

[0212] (3) Delete some row indexes, and add an indication of enabling or disabling repeated transmission of the first downlink transmission to the remaining row indexes.

[0213] Optionally, in an embodiment of the present application, the above-mentioned indication information for enabling or disabling repeated transmission is indicated by defining a newly added PDSCH time domain resource allocation table that supports repeated transmission.

[0214] An embodiment of the present application provides a method for indicating repeated transmission of a common PDSCH. The terminal can enable or disable repeated transmission of a first downlink transmission based on the indication of fourth indication information, thereby improving the flexibility and reliability of repeated transmission of the common PDSCH.

[0215] The following describes the relevant schemes and examples involved in the method for indicating repeated transmission of the common PDSCH in the embodiments of the present application through specific implementation methods (implementation methods one to three).

[0216] Implementation method 1: semi-static configuration of the number of repeated transmissions

[0217] To support repeated transmission of the common PDSCH, the number of repeated transmissions can be semi-statically configured with one or more repeated transmission times, as follows:

[0218] (1) Configure a repeat transmission count value:

[0219] In some embodiments, a repetition transmission count value is configured through a system message (SI), that is, the repetition transmission count of the common PDSCH repetition transmission. The SI here can be MIB or SIB.

[0220] In some embodiments, a repetition number value is configured through an RRC message, that is, the repetition number of common PDSCH repetition transmissions. For example, a new RRC parameter is introduced in PDSCH-ConfigCommon, which is specifically used to indicate the repetition number; or the parameter pdsch-TimeDomainAllocationList in PDSCH-ConfigCommon adds an indication of the repetition number when indicating time domain resource allocation.

[0221] Furthermore, an enable / disable indication may be added to the corresponding scheduling DCI to enable or disable the number of repeated transmissions configured semi-statically. That is, a number of repeated transmissions is configured semi-statically, but the number of repeated transmissions may be used or not used through the corresponding scheduling DCI. If it is not used, the repeated transmission of the common PDSCH is not performed.

[0222] It should be noted that the above corresponding scheduling DCI: for example, for Msg2 PDSCH, the corresponding DCI refers to the DCI for scheduling Msg2 PDSCH.

[0223] To configure multiple retransmission count values:

[0224] In some embodiments, multiple repetition transmission times are configured through SI, that is, a repetition transmission times set, and further instructions are required to select one from the repetition transmission times set to determine the final repetition transmission times. The SI here can be MIB or SIB, such as SIB1.

[0225] In some embodiments, multiple repetition number values, i.e., a repetition number set, are configured through an RRC message, and further instructions are required to select a repetition number value from the repetition number set to determine the repetition number of common PDSCH repetition transmissions. For example, a new RRC parameter is introduced in PDSCH-ConfigCommon, which is specifically used to indicate the repetition number set; or the parameter pdsch-TimeDomainAllocationList in PDSCH-ConfigCommon adds an indication of the repetition number set.

[0226] The further indication here may be a dynamic indication, which may be indicated by a domain in the DCI, by the RNTI of the scrambled DCI, by the DMRS sequence of the PDCCH where the DCI is scheduled, or by the scrambling sequence of the repeated transmission of the common PDSCH.

[0227] For example, a field in the scheduled DCI further indicates that a certain repetition transmission number value in the repetition transmission number set is selected, that is, the repetition transmission number of the common PDSCH repetition transmission.

[0228] For another example, a certain entry of PDSCH-TimeDomainAllocationList is indicated through the TDRA field in the DCI, and the repetition factor under the entry is used as the number of repeated transmissions of the common PDSCH repeated transmissions.

[0229] In some embodiments, a PDSCH TDRA table (also called TDRA list) supporting repeated transmission of a common PDSCH is specially configured through SI. For example, for each entry of the configured TDRA list, a repetition factor is defined.

[0230] Implementation method 2: The protocol specifies the number of repeated transmissions

[0231] In order not to increase the additional signaling overhead, the number of repetitions of the common PDSCH repetition can be indicated by modifying the Default PDSCH time domain resource allocation A or the newly added PDSCH time domain resource allocation table that supports repetition, or the default set of repetition times specified by the protocol, in the following cases:

[0232] For the existing Default PDSCH time domain resource allocation A, please refer to the introduction of Table 2 and Table 3 in the above embodiment.

[0233] In some embodiments, the number of repeated transmissions is indicated by modifying the Default PDSCH time domain resource allocation table (such as TDRA table A).

[0234] Specifically, the modification method may include at least one of the following:

[0235] Method 1: Add an information column to indicate the number of repetitions.

[0236] Method 2: Expand the table, that is, add some row indexes below the default table, then you need to add 1 bit or more bits to indicate the new row index;

[0237] Method 3: Delete some row indexes and increase the number of repeated transmissions supported by the remaining row indexes.

[0238] As shown in Table 6, for normal CP, an information column (such as the Repetitionnumber column in Table 6 below) is added to indicate the number of repeated transmissions.

[0239] Table 6: Method 1 (for normal CP)

[0240]

[0241] As shown in Table 7, for normal CP, the table is extended to add some row indexes (such as Row index 17 to 32 in Table 7 below) to indicate the number of repeated transmissions.

[0242] Table 7: Mode 2 (for normal CP)

[0243]

[0244] As shown in Table 8, for normal CP, by deleting the contents of some row indexes (such as Rowindex2, 4, 6, 9-11, 13 in Table 8 below), and increasing the number of repeated transmissions supported by the retained row indexes. It should be noted that in Table 8, the deletion of the row index is indicated by a strikethrough, and the increase in the number of repeated transmissions supported by the corresponding row index is indicated by a bold font.

[0245] Table 8: Mode 3 (for normal CP)

[0246]

[0247] It should be noted that for the description of K0, S and L in the above table, please refer to the introduction in Table 2 and Table 3 in the above embodiment, which will not be repeated here. The above table is only an example and does not represent the only modification method; for extended CP, similar modification is performed.

[0248] In some embodiments, a newly added PDSCH time domain resource allocation table supporting repetition can be defined to indicate the repetition number, and whether to use the default table (such as TDRA table A) or this newly added table can be determined by RRC parameters or whether the terminal supports common PDSCH repeated transmission.

[0249] As shown in Table 9, this is an example of a newly added PDSCH time domain resource allocation table that supports repetition.

[0250] Table 9

[0251]

[0252] It should be noted that the above table is only an example and does not represent the only modification method; for extendedCP, a similar method is added.

[0253] In some embodiments, multiple candidate values ​​of the number of repetition transmissions, i.e., a set of repetition transmissions, can be determined in a manner specified by the protocol, and further instructions are required to select one repetition transmission number value from the set of repetition transmissions to determine the number of repetition transmissions for the common PDSCH repetition transmissions.

[0254] For example, the multiple candidate values ​​of the number of repeated transmissions here may be at least one of {1, 2, 4, 8, 16, 32}, and the set of the number of repeated transmissions is any subset of the set {1, 2, 4, 8, 16, 32}.

[0255] The further indication here may be a dynamic indication, which may be indicated by a domain in the DCI, by the RNTI of the scrambled DCI, by the DMRS sequence of the PDCCH where the DCI is scheduled, or by the scrambling sequence of the repeated transmission of the common PDSCH.

[0256] For example, a field in the scheduled DCI further indicates that a certain repetition transmission number value in the repetition transmission number set is selected, that is, the repetition transmission number of the common PDSCH repetition transmission.

[0257] Implementation method 3: Dynamically indicating the number of repeated transmissions

[0258] To support repeated transmission of the common PDSCH, the number of repeated transmissions can be dynamically indicated in the following cases:

[0259] Based on the description of the above embodiments, the dynamic indication can be a direct indication of the number of repeated transmissions, such as repetitionfactor, or it can be based on the set of repeated transmission numbers to further indicate the number of repeated transmissions selected in the set, such as an index in the set of repeated transmission numbers, which can be used to indicate the number of repeated transmissions selected in the set.

[0260] In some embodiments, the PDSCH of the common PDSCH repetition transmission may be scrambled by different identifiers (IDs), and different IDs may correspond to different repetition factors or indices in a set of repetition transmission times.

[0261] In some embodiments, different sequences of PDSCH DMRS or IDs of generating sequence initial values ​​for repeated transmission of the common PDSCH may be used, and different sequences or different IDs may correspond to different repetition factors or indexes in a set of repeated transmission times.

[0262] In some embodiments, the DCI for scheduling repeated transmission of the common PDSCH may be scrambled by different RNTIs, and different RNTIs may correspond to different repetition factors or indices in a set of repeated transmission times.

[0263] In some embodiments, a new indication field may be added to the DCI for scheduling repeated transmission of the common PDSCH to indicate the indexes in different repetition factors or repeated transmission number sets.

[0264] In some embodiments, the first field (existing field) in the DCI for scheduling repeated transmission of the common PDSCH may be reinterpreted to correspond to different repetition factors or indices in a set of repeated transmission times.

[0265] For Msg2 / MsgB PDSCH, the first field includes but is not limited to at least one of the following:

[0266] Modulation and coding scheme domain;

[0267] TB scaling domain;

[0268] Reserved bits field.

[0269] For Msg4 PDSCH, the first field includes but is not limited to at least one of the following:

[0270] Modulation and coding scheme domain;

[0271] New data indicator field;

[0272] Redundancy version (RV) domain;

[0273] Downlink assignment index field;

[0274] PDSCH-to-HARQ_feedback timing indicator field;

[0275] Reserved bits field.

[0276] It should be noted that the meaning of not limited to at least one of the following items here is: the indication may be that part of the bits or all of the bits of one of the domains are used for indication, or part of the bits or all of the bits of different domains are used for joint indication.

[0277] In some embodiments, some bits in the Modulation and coding scheme domain (MCS domain for short) are used to indicate the number of repeated transmissions. For example, the highest 2 bits are used to indicate the number of repeated transmissions, and the number of repeated transmissions set is indicated as {1, 2, 4, 8} through RRC parameters or system messages or pre-configured methods. The specific corresponding relationship is not limited to the following Table 10:

[0278] Table 10

[0279]

[0280] If the set of repeated transmission times is indicated as {2,4} by RRC parameters or system messages or pre-configuration, only some bits in the MCS field may be used to indicate the repeated transmission times. The specific corresponding relationship is not limited to the following Table 11:

[0281] Table 11

[0282]

[0283] In some embodiments, the TB scaling field is used to indicate the number of repetitions. The number of repetitions set here may be indicated by an RRC parameter or a system message or a preconfigured manner (eg, preconfigured as {1, 2, 4, 8}).

[0284] For example, when the set of repeated transmission times is {1, 2, 4, 8}, the corresponding relationship between TB scaling and repetition factor may be, but is not limited to, the following Table 12:

[0285] Table 12

[0286]

[0287] For another example, the number of repeated transmissions can be a function of the scaling factor. For example, the number of repeated transmissions is the inverse of the scaling factor S, and no repetition is performed when S is not defined. The existing scaling factor only supports the following three numbers, so the number of repetitions can only support {1, 2, 4}, as shown in Table 13 below:

[0288] Table 13

[0289] TB scaling field Scaling factor S 00 1 01 0.5 10 0.25 11

[0290] Or the number of repeated transmissions is 2*(1 / S), and no repetition is performed when S is not defined. In this way, the number of no repetitions can be {1, 2, 4, 8}, corresponding to S = {not defined, 1, 0.5, 0.25} respectively.

[0291] Through the above methods, a larger number of repeated transmissions can be configured when TB scaling is relatively small, that is, when coverage is relatively poor, while also saving signaling overhead.

[0292] In some embodiments, the Redundancy version field is used to indicate the number of repeated transmissions. For example, when the redundancy version sequence is configured as {0,0,0,0}, it means that the redundancy version sequence corresponding to the msg4 PDSCH repetition is {0,0,0,0}, that is, RV0 is always used. The number of repeated transmissions set is indicated as {1,2,4,8} through RRC parameters or system messages or pre-configuration. The specific correspondence relationship can be but is not limited to the following Table 14:

[0293] Table 14

[0294]

[0295] In some embodiments, some bits of the Redundancy version field and the New data indicator field are used to jointly indicate the number of repeated transmissions. For example, when the redundancy version sequence is configured as {0,3,0,3}, it means that the redundancy version sequence corresponding to msg4 PDSCHrepetition is {0,3,0,3}, and the RV can be determined only by the lowest bit of the Redundancy version field. In addition, the corresponding HARQ process ID is configured as disabled feedback. The set of repeated transmission times is indicated as {1,2,4,8} through RRC parameters, system messages, or pre-configuration. The specific corresponding relationship is not limited to the following Table 15:

[0296] Table 15

[0297]

[0298] It should be noted that there is no Redundancyversion field in the DCI format 1_0 for scheduling Msg2 PDSCH and MsgB PDSCH, but to support Msg2 / MsgB PDSCH repetition, its RV needs to be determined. For example, the RV sequence can be specified as {0,0,0,0} or {0,3,0,3} or {0,2,3,1} through system messages or RRC messages or protocols. A new field can be added in the scheduling DCI to indicate the RV_ID or specify the default RV_ID = 0, and then the RV of a repetition is determined according to the following Table 16.

[0299] Table 16: RV used when repeat transmission is enabled

[0300]

[0301] In some embodiments, the Downlink assignment index field is used to indicate the number of repeated transmissions, and the number of repeated transmissions set is indicated by an RRC parameter or a system message or a preconfigured manner (for example, predefined as {1, 2, 4, 8}), and the specific corresponding relationship is not limited to the following Table 17:

[0302] Table 17

[0303]

[0304] In some embodiments, the PDSCH-to-HARQ_feedback timing indicator field is used to partially indicate the number of repeated transmissions, and the number of repeated transmissions set is indicated by an RRC parameter or a system message or a preconfigured manner (for example, predefined as {2, 4}), and the specific corresponding relationship is not limited to the following Table 18:

[0305] Table 18

[0306]

[0307] In some embodiments, when the Reserved bits field is not 0 bits, some bits of the Reserved bits field are used to indicate the number of repeated transmissions, and the number of repeated transmissions set is indicated by RRC parameters or system messages or pre-configured methods (for example, pre-defined as {1, 2, 4, 8}). The specific correspondence relationship can be, but is not limited to, the following Table 19, for example, the lowest 2 bits of Reservedbits are used to indicate the number of repeated transmissions.

[0308] Table 19

[0309]

[0310] In some embodiments, for the above embodiments, the indication of the number of repetitions may be used when the network configuration enables common PDSCH repetition transmissions.

[0311] Each of the above-mentioned method embodiments, or various possible implementation methods in each method embodiment can be executed separately, or any two or more of them can be executed in combination with each other. The specific implementation method can be determined according to actual usage requirements, and the embodiments of the present application do not limit this.

[0312] The method for indicating the repeated transmission of a common PDSCH provided in the embodiment of the present application can be performed by a device for indicating repeated transmission of a common PDSCH. In the embodiment of the present application, the device for indicating repeated transmission of a common PDSCH is used as an example to illustrate the method for indicating repeated transmission of a common PDSCH, to illustrate the device for indicating repeated transmission of a common PDSCH provided in the embodiment of the present application.

[0313] Figure 5 A possible structural diagram of a common PDSCH repetition transmission indication device involved in an embodiment of the present application is shown. Figure 5 As shown, the indication device 40 for repeated transmission of the common PDSCH may include: a determination module 41.

[0314] The determination module 41 is used to determine the number of repeated transmissions of the first downlink transmission based on the first indication information; wherein the first indication information is used to indicate at least one number of repeated transmissions, and the first downlink transmission is a common PDSCH repeated transmission.

[0315] An embodiment of the present application provides an indication device for repeated transmission of a public PDSCH. The indication device for repeated transmission of a public PDSCH can determine the number of repeated transmissions of the public PDSCH based on at least one number of repeated transmissions indicated by first indication information, that is, the repeated transmission of the public PDSCH is supported by indicating the number of repeated transmissions through the first indication information, so that the transmission of the downlink channel meets the link budget requirements in the link budget, thereby improving the reliability of the public PDSCH transmission and thus improving the coverage capability of the network.

[0316] In a possible implementation manner, when the first indication information indicates a number of repeated transmissions, the first indication information is configured semi-statically or dynamically indicated;

[0317] or,

[0318] In the case where the first indication information indicates a set of repetition transmission times, the first indication information is specified through a semi-static configuration or a protocol, and the set of repetition transmission times includes at least two repetition transmission times.

[0319] In a possible implementation manner, when the first indication information indicates a number of repeated transmissions, the number of repeated transmissions is the number of repeated transmissions of the first downlink transmission;

[0320] or,

[0321] In the case where the first indication information indicates a set of repeated transmission times, the repeated transmission times of the first downlink transmission are determined by the second indication information, and the second indication information is used to indicate a repeated transmission number in the set of repeated transmission times, the one repeated transmission number being the repeated transmission number of the first downlink transmission, and the second indication information is configured semi-statically or dynamically indicated.

[0322] In a possible implementation manner, the scheduling DCI corresponding to the above-mentioned common PDSCH repeated transmission includes third indication information, and the third indication information is used to enable or disable the number of repeated transmissions configured semi-statically or dynamically indicated.

[0323] In a possible implementation manner, the dynamic indication is indicated by repeated transmission of a common PDSCH; or, the dynamic indication is indicated by a scheduling DCI corresponding to repeated transmission of a common PDSCH.

[0324] In a possible implementation, the dynamic indication is indicated by a scrambling sequence of repeated transmission of a common PDSCH;

[0325] or,

[0326] The above dynamic indication is indicated by any of the following:

[0327] Indicated by scrambling the RNTI of the scheduling DCI;

[0328] Indicated by the DMRS sequence of the PDCCH where the DCI is scheduled;

[0329] Indicated by a field in the scheduling DCI.

[0330] In a possible implementation, the dynamic indication is indicated by a scrambling sequence of repeated transmission of a common PDSCH;

[0331] The above-mentioned common PDSCH repetition transmission is scrambled by a first identifier, and the first identifier corresponds to a repetition factor or an index in a set of repetition transmission times to determine the above-mentioned one repetition transmission number; or,

[0332] The sequence of the DMRS for repeated transmission of the common PDSCH or the identifier for generating the initial value of the sequence corresponds to a repetition factor or an index in a set of repeated transmission times to determine the repeated transmission times.

[0333] In a possible implementation, the dynamic indication is indicated by scrambling the RNTI of the scheduling DCI; the scheduling DCI is scrambled by a first RNTI, and the first RNTI corresponds to a repetition factor or an index in a set of repeated transmission times to determine the repeated transmission times.

[0334] In a possible implementation manner, the scheduling DCI scrambled by the first RNTI includes any of the following:

[0335] A first DCI format scrambled by CRC through TC-RNTI;

[0336] A first DCI format scrambled by CRC through RA-RNTI;

[0337] The first DCI format is CRC-scrambled by MsgB-RNTI.

[0338] In a possible implementation, the above-mentioned dynamic indication is indicated through a field in the scheduling DCI; the above-mentioned scheduling DCI indicates a repetition factor or an index in a set of repeated transmission times through a first indication field to determine a repeated transmission number, and the first indication field is an existing field in the scheduling DCI or a newly added indication field.

[0339] In a possible implementation manner, the first indication field is an existing field in the scheduling DCI;

[0340] For the scheduling DCI corresponding to the downlink data channel used to carry Msg2 or MsgB, the first indication field includes at least one of the following: a modulation and coding mode field, a TB scaling field, and a reserved bit field;

[0341] For the scheduling DCI corresponding to the downlink data channel used to carry Msg4, the above-mentioned first indication field includes at least one of the following: a modulation and coding mode field, a new data indication field, a redundant version field, a downlink allocation index field, an indication field of the timing between the downlink data channel and HARQ, and a reserved bit field.

[0342] In a possible implementation manner, the first indication information is specified by a protocol;

[0343] The first indication information directly indicates a set of repeated transmission times specified by the protocol; or,

[0344] The first indication information is the repetition transmission number indication information in the PDSCH time domain resource allocation table, and the repetition transmission number indication information is used to indicate a repetition transmission number set.

[0345] In a possible implementation, the set of repeated transmission times indicated by the repeated transmission times indication information is indicated by modifying a default PDSCH time domain resource allocation table;

[0346] or,

[0347] The set of repeated transmission times indicated by the repeated transmission times indication information is indicated by defining a newly added PDSCH time domain resource allocation table supporting repeated transmission.

[0348] In a possible implementation, the determination module 41 is further configured to determine whether repeated transmission is enabled for the first downlink transmission based on fourth indication information.

[0349] The public PDSCH repeated transmission indication device provided in the embodiment of the present application can implement each process implemented by the terminal in the above method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0350] The indication device for repeated transmission of the common PDSCH in the embodiment of the present application may be a terminal, such as a terminal with an operating system, or a component in the terminal, such as an integrated circuit or a chip. 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.

[0351] Alternatively, if Figure 6 As shown, an embodiment of the present application also provides a communication device 5000, including a processor 5001 and a memory 5002, and the memory 5002 stores programs or instructions that can be executed on the processor 5001. For example, when the communication device 5000 is a terminal, the program or instructions are executed by the processor 5001 to implement the various steps of the above-mentioned terminal side method embodiment, and can achieve the same technical effect. To avoid repetition, they are not repeated here.

[0352] The embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the processor is used to determine the number of repeated transmissions of a first downlink transmission based on first indication information; wherein the first indication information is used to indicate at least one number of repeated transmissions, and the first downlink transmission is a common PDSCH repeated transmission. The 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.

[0353] Specifically, Figure 7 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0354] The terminal 7000 includes but is not limited to: a radio frequency unit 7001, a network module 7002, an audio output unit 7003, an input unit 7004, a sensor 7005, a display unit 7006, a user input unit 7007, an interface unit 7008, a memory 7009 and at least some of the components of a processor 7010.

[0355] Those skilled in the art will appreciate that the terminal 7000 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 7010 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 7 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0356] It should be understood that in the embodiment of the present application, the input unit 7004 may include a graphics processing unit (GPU) 70041 and a microphone 70042, and the graphics processor 70041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 7006 may include a display panel 70061, and the display panel 70061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 7007 includes a touch panel 70071 and at least one of other input devices 70072. The touch panel 70071 is also called a touch screen. The touch panel 70071 may include two parts: a touch detection device and a touch controller. Other input devices 70072 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 a joystick, which will not be repeated here.

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

[0358] The memory 7009 can be used to store software programs or instructions and various data. The memory 7009 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, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 7009 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 7009 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0359] The processor 7010 may include one or more processing units; optionally, the processor 7010 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 7010.

[0360] The processor 7010 is used to determine the number of repeated transmissions of the first downlink transmission based on the first indication information; wherein the first indication information is used to indicate at least one number of repeated transmissions, and the first downlink transmission is a common PDSCH repeated transmission.

[0361] An embodiment of the present application provides a terminal, which can determine the number of repeated transmissions of a common PDSCH based on at least one repeated transmission number indicated by a first indication information, that is, support the repeated transmission of the common PDSCH through the indication of the repeated transmission number by the first indication information, so that the transmission of the downlink channel meets the link budget requirements in the link budget, improves the reliability of the common PDSCH transmission, and thus improves the coverage capability of the network.

[0362] Optionally, in an embodiment of the present application, when the first indication information indicates a number of repeated transmissions, the first indication information is configured semi-statically or dynamically;

[0363] or,

[0364] In the case where the first indication information indicates a set of repetition transmission times, the first indication information is specified through a semi-static configuration or a protocol, and the set of repetition transmission times includes at least two repetition transmission times.

[0365] Optionally, in an embodiment of the present application, when the first indication information indicates a number of repeated transmissions, the number of repeated transmissions is the number of repeated transmissions of the first downlink transmission;

[0366] or,

[0367] In the case where the first indication information indicates a set of repeated transmission times, the repeated transmission times of the first downlink transmission are determined by the second indication information, and the second indication information is used to indicate a repeated transmission number in the set of repeated transmission times, the one repeated transmission number being the repeated transmission number of the first downlink transmission, and the second indication information is configured semi-statically or dynamically indicated.

[0368] Optionally, in an embodiment of the present application, the scheduling DCI corresponding to the above-mentioned common PDSCH repeated transmission includes third indication information, and the third indication information is used to enable or disable the number of repeated transmissions configured semi-statically or dynamically indicated.

[0369] Optionally, in an embodiment of the present application, the above-mentioned dynamic indication is indicated by repeated transmission of a common PDSCH; or, the above-mentioned dynamic indication is indicated by a scheduling DCI corresponding to repeated transmission of a common PDSCH.

[0370] Optionally, in an embodiment of the present application, the above dynamic indication is indicated by a scrambling sequence repeatedly transmitted by a common PDSCH;

[0371] or,

[0372] The above dynamic indication is indicated by any of the following:

[0373] Indicated by scrambling the RNTI of the scheduling DCI;

[0374] Indicated by the DMRS sequence of the PDCCH where the DCI is scheduled;

[0375] Indicated by a field in the scheduling DCI.

[0376] Optionally, in an embodiment of the present application, the above dynamic indication is indicated by a scrambling sequence repeatedly transmitted by a common PDSCH;

[0377] The above-mentioned common PDSCH repetition transmission is scrambled by a first identifier, and the first identifier corresponds to a repetition factor or an index in a set of repetition transmission times to determine the above-mentioned one repetition transmission number; or,

[0378] The sequence of the DMRS for repeated transmission of the common PDSCH or the identifier for generating the initial value of the sequence corresponds to a repetition factor or an index in a set of repeated transmission times to determine the repeated transmission times.

[0379] Optionally, in an embodiment of the present application, the above-mentioned dynamic indication is indicated by scrambling the RNTI of the scheduling DCI; the above-mentioned scheduling DCI is scrambled by a first RNTI, and the first RNTI corresponds to a repetition factor or an index in a set of repeated transmission times to determine the above-mentioned repeated transmission times.

[0380] Optionally, in the embodiment of the present application, the scheduling DCI scrambled by the first RNTI includes any of the following:

[0381] A first DCI format scrambled by CRC through TC-RNTI;

[0382] A first DCI format scrambled by CRC through RA-RNTI;

[0383] The first DCI format is CRC-scrambled by MsgB-RNTI.

[0384] Optionally, in an embodiment of the present application, the above-mentioned dynamic indication is indicated through a field in the scheduling DCI; the above-mentioned scheduling DCI indicates a repetition factor or an index in a set of repeated transmission times through a first indication field to determine a repeated transmission number, and the first indication field is an existing field in the scheduling DCI or a newly added indication field.

[0385] Optionally, in the embodiment of the present application, the first indication field is an existing field in the scheduling DCI;

[0386] For the scheduling DCI corresponding to the downlink data channel used to carry Msg2 or MsgB, the first indication field includes at least one of the following: a modulation and coding mode field, a TB scaling field, and a reserved bit field;

[0387] For the scheduling DCI corresponding to the downlink data channel used to carry Msg4, the above-mentioned first indication field includes at least one of the following: a modulation and coding mode field, a new data indication field, a redundant version field, a downlink allocation index field, an indication field of the timing between the downlink data channel and HARQ, and a reserved bit field.

[0388] Optionally, in an embodiment of the present application, the first indication information is specified by a protocol;

[0389] The first indication information directly indicates a set of repeated transmission times specified by the protocol; or,

[0390] The first indication information is the repetition transmission number indication information in the PDSCH time domain resource allocation table, and the repetition transmission number indication information is used to indicate a repetition transmission number set.

[0391] Optionally, in an embodiment of the present application, the set of repeated transmission times indicated by the repeated transmission times indication information is indicated by modifying a default PDSCH time domain resource allocation table;

[0392] or,

[0393] The set of repeated transmission times indicated by the repeated transmission times indication information is indicated by defining a newly added PDSCH time domain resource allocation table supporting repeated transmission.

[0394] Optionally, in an embodiment of the present application, the processor 7010 is further used to determine whether repeated transmission is enabled for the first downlink transmission based on fourth indication information.

[0395] The terminal provided in the embodiment of the present application can implement each process implemented on the terminal side in the above method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0396] 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, the various processes of the above-mentioned public PDSCH repeated transmission indication method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0397] The processor is a processor in the communication device 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-transient readable storage medium.

[0398] 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 method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0399] 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.

[0400] The embodiments of the present application further provide a computer program / program product, which is stored in a storage medium and is executed by at least one processor to implement the various processes of the above-mentioned method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described here.

[0401] 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.

[0402] 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.

[0403] 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

1. A method for indicating repeated transmission of a common physical downlink shared channel PDSCH, characterized in that: include: The terminal determines, based on the first indication information, the number of repeated transmissions of the first downlink transmission; The first indication information is used to indicate at least one number of repeated transmissions, and the first downlink transmission is a common PDSCH repeated transmission.

2. The method according to claim 1, characterized in that In the case where the first indication information indicates a number of repeated transmissions, the first indication information is configured semi-statically or dynamically indicated; or, In the case where the first indication information indicates a set of repetition transmission times, the first indication information is specified by a semi-static configuration or a protocol, and the set of repetition transmission times includes at least two repetition transmission times.

3. The method according to claim 1 or 2, characterized in that: In the case where the first indication information indicates a number of repeated transmissions, the number of repeated transmissions is the number of repeated transmissions of the first downlink transmission; or, In the case where the first indication information indicates a set of repeated transmission times, the repeated transmission times of the first downlink transmission are determined by second indication information, the second indication information is used to indicate a repeated transmission number in the set of repeated transmission times, the one repeated transmission number being the repeated transmission number of the first downlink transmission, and the second indication information is configured semi-statically or dynamically indicated.

4. The method according to claim 2 or 3, characterized in that: The scheduling downlink control information DCI corresponding to the repeated transmission of the common PDSCH includes third indication information, and the third indication information is used to enable or disable the number of repeated transmissions configured semi-statically or dynamically indicated.

5. The method according to any one of claims 2 to 4, characterized in that The dynamic indication is indicated by the common PDSCH; or, The dynamic indication is indicated by the scheduling DCI corresponding to the repeated transmission of the common PDSCH.

6. The method according to claim 5, characterized in that The dynamic indication is indicated by a scrambling sequence of repeated transmission of the common PDSCH; or, The dynamic indication is indicated by any of the following: Indicated by scrambling the radio network temporary identifier RNTI of the scheduling DCI; Indicated by a demodulation reference channel DMRS sequence of a physical downlink control channel PDCCH where the scheduling DCI is located; It is indicated by a field in the scheduling DCI.

7. The method according to claim 6, characterized in that The dynamic indication is indicated by a scrambling sequence of repeated transmission of the common PDSCH; The common PDSCH repetition transmission is scrambled by a first identifier, wherein the first identifier corresponds to a repetition factor or an index in a set of repetition transmission times to determine the one repetition transmission number; or, The sequence of the DMRS for repeated transmission of the common PDSCH or the identifier for generating the initial value of the sequence corresponds to a repetition factor or an index in a set of repeated transmission times to determine the repeated transmission times.

8. The method according to claim 6, characterized in that The dynamic indication is indicated by scrambling the RNTI of the scheduling DCI; The scheduling DCI is scrambled by a first RNTI, where the first RNTI corresponds to a repetition factor or an index in a set of repeated transmission times to determine the repeated transmission times.

9. The method according to claim 8, characterized in that The scheduling DCI scrambled by the first RNTI includes any one of the following: A first DCI format scrambled by a cyclic redundancy check code CRC through a temporary cell TC-RNTI; A first DCI format scrambled by CRC through random access RA-RNTI; The first DCI format is CRC-scrambled by MsgB-RNTI.

10. The method according to claim 6, characterized in that The dynamic indication is indicated by a field in the scheduling DCI; The scheduling DCI indicates a repetition factor or an index in a set of repeated transmission times through a first indication field to determine the number of repeated transmissions. The first indication field is an existing field or a newly added indication field in the scheduling DCI.

11. The method according to claim 1 or 2, characterized in that: The first indication information is repeated transmission number indication information in the PDSCH time domain resource allocation table, and the repeated transmission number indication information is used to indicate a repeated transmission number set; The set of repeated transmission times indicated by the repeated transmission times indication information is indicated by modifying a default PDSCH time domain resource allocation table; or, The set of repeated transmission times indicated by the repeated transmission times indication information is indicated by defining a newly added PDSCH time domain resource allocation table supporting repeated transmission.

12. The method according to claim 1, characterized in that The method further comprises: The terminal determines whether repeated transmission is enabled for the first downlink transmission based on fourth indication information.

13. A device for indicating repeated transmission of a common physical downlink shared channel PDSCH, characterized in that: include: Identify the module; The determining module is used to determine the number of repeated transmissions of the first downlink transmission based on the first indication information; The first indication information is used to indicate at least one number of repeated transmissions, and the first downlink transmission is a common PDSCH repeated transmission.

14. A terminal, characterized in that: It includes a processor and a memory, 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 indicating repeated transmission of a common physical downlink shared channel PDSCH as described in any one of claims 1 to 12 are implemented.

Images