WO2024031395A1

WO2024031395A1 - Repeated transmission methods, terminal devices, and network devices

Info

Publication number: WO2024031395A1
Application number: PCT/CN2022/111286
Authority: WO
Inventors: 马腾; 张世昌; 赵振山
Original assignee: Oppo广东移动通信有限公司
Priority date: 2022-08-09
Filing date: 2022-08-09
Publication date: 2024-02-15

Abstract

The present application relates to repeated transmission methods, terminal devices, and network devices. A repeated transmission method may comprise: according to a first number of repeated transmissions of downlink data and a transmission situation of the downlink data, a terminal device executes subsequent repeated-transmission related processing. In the embodiments of the present application, the subsequent repeated-transmission related processing can be reasonably executed according to the first number of repeated transmissions of the downlink data and the transmission situation of the downlink data, thus saving transmission resources.

Description

Repeated transmission methods, terminal equipment and network equipment

Technical field

The present application relates to the field of communications, and more specifically, to a repeated transmission method, terminal equipment and network equipment.

Background technique

In some communication services such as Multimedia Broadcast Multicast Services (MBMS), Multicast Broadcast Service (MBS), etc., repeated transmission may be required. Usually, if the number of repeated transmissions of an MBS service is determined, repeated transmissions are performed according to the number of repeated transmissions for a long period of time before the signaling is updated, which may easily cause a waste of transmission resources.

Contents of the invention

Embodiments of the present application provide a repeated transmission method, terminal equipment, and network equipment.

Embodiments of the present application provide a repeated transmission method, which includes: a terminal device performing subsequent repeated transmission related processing according to the first number of repeated transmissions of downlink data and the transmission status of the downlink data.

Embodiments of the present application provide a repeated transmission method, which includes: the network device performs subsequent repeated transmission related processing according to the first number of repeated transmissions of downlink data and the feedback status of the downlink data.

Embodiments of the present application provide a terminal device, including: a processing unit configured to perform subsequent repeated transmission related processing according to the first number of repeated transmissions of downlink data and the transmission status of the downlink data.

An embodiment of the present application provides a network device, including: a processing unit configured to perform subsequent repeated transmission related processing based on the first number of repeated transmissions of downlink data and the feedback status of the downlink data.

An embodiment of the present application provides a terminal device, including a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer program stored in the memory, so that the terminal device performs the above-mentioned repeated transmission method.

An embodiment of the present application provides a network device, including a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory, so that the network device performs the above-mentioned repeated transmission method.

An embodiment of the present application provides a chip for implementing the above repeated transmission method.

Specifically, the chip includes: a processor for calling and running a computer program from the memory, so that the device installed with the chip performs the above-mentioned repeated transmission method.

Embodiments of the present application provide a computer-readable storage medium for storing a computer program. When the computer program is run by a device, it causes the device to perform the above repeated transmission method.

An embodiment of the present application provides a computer program product, including computer program instructions, which cause a computer to execute the above repeated transmission method.

An embodiment of the present application provides a computer program that, when run on a computer, causes the computer to perform the above repeated transmission method.

In the embodiment of the present application, according to the first number of repeated transmissions of downlink data and the transmission situation of the downlink data, subsequent repeated transmission related processing can be reasonably performed and transmission resources can be saved.

Description of drawings

Figure 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

Figures 2a to 2c are schematic diagrams of examples of BWP.

Figure 3 is a schematic diagram of SC-PTM according to an embodiment of the present application.

Figures 4a to 4c are schematic diagrams of NR MBS scheduling methods according to embodiments of the present application.

Figure 5 is a schematic flow chart of a repeated transmission method according to an embodiment of the present application.

Figure 6 is a schematic flow chart of a repeated transmission method according to another embodiment of the present application.

Figure 7 is a schematic flow chart of a repeated transmission method according to another embodiment of the present application.

Figure 8 is a schematic flow chart of a repeated transmission method according to an embodiment of the present application.

Figure 9 is a schematic flow chart of a repeated transmission method according to another embodiment of the present application.

Figure 10 is a schematic flow chart of a repeated transmission method according to another embodiment of the present application.

Figure 11 is a schematic block diagram of a terminal device according to an embodiment of the present application.

Figure 12 is a schematic block diagram of a terminal device according to another embodiment of the present application.

Figure 13 is a schematic block diagram of a network device according to an embodiment of the present application.

Figure 14 is a schematic block diagram of a network device according to another embodiment of the present application.

Figure 15 is a schematic diagram of configuring an uplink feedback resource PUCCH according to an embodiment of the present application.

Figure 16 is a schematic diagram of configuring two uplink feedback resources PUCCH according to an embodiment of the present application.

Figure 17 is a schematic diagram of sending TB1 to a group of UEs through PTM according to an embodiment of the present application.

Figure 18 is a schematic diagram of TB repeated transmission in SPS according to an embodiment of the present application.

Figure 19 is a schematic block diagram of a communication device according to an embodiment of the present application.

Figure 20 is a schematic block diagram of a chip according to an embodiment of the present application.

Figure 21 is a schematic block diagram of a communication system according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (Code Division Multiple Access, CDMA) system, broadband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced long term evolution (LTE-A) system , New Radio (NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), wireless fidelity (Wireless Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, Device to Device, D2D) communication, Machine to Machine (M2M) communication, Machine Type Communication (MTC), Vehicle to Vehicle (V2V) communication, or Vehicle to everything (V2X) communication, etc. , the embodiments of the present application can also be applied to these communication systems.

In an implementation manner, the communication system in the embodiment of the present application can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA)Network scene.

In one implementation, the communication system in the embodiment of the present application can be applied to unlicensed spectrum, where the unlicensed spectrum can also be considered as shared spectrum; or, the communication system in the embodiment of the present application can also be applied to licensed spectrum , among which, licensed spectrum can also be considered as non-shared spectrum.

The embodiments of this application describe various embodiments in combination with network equipment and terminal equipment. The terminal equipment may also be called user equipment (User Equipment, UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.

The terminal device can be a station (ST) in the WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, or a personal digital processing unit. (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, next-generation communication systems such as terminal devices in NR networks, or in the future Terminal equipment in the evolved Public Land Mobile Network (PLMN) network, etc.

In the embodiment of this application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons and satellites). superior).

In the embodiment of this application, the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, or an augmented reality (Augmented Reality, AR) terminal. Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, or wireless terminal equipment in smart home, etc.

As an example and not a limitation, in this embodiment of the present application, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones. Use, such as various types of smart bracelets, smart jewelry, etc. for physical sign monitoring.

In the embodiment of this application, the network device may be a device used to communicate with mobile devices. The network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA. , or it can be a base station (NodeB, NB) in WCDMA, or an evolutionary base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and an NR network network equipment (gNB) or network equipment in the future evolved PLMN network or network equipment in the NTN network, etc.

As an example and not a limitation, in the embodiment of the present application, the network device may have mobile characteristics, for example, the network device may be a mobile device. Optionally, the network device can be a satellite or balloon station. For example, the satellite can be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite ) satellite, etc. Optionally, the network device may also be a base station installed on land, water, etc.

In this embodiment of the present application, network equipment can provide services for a cell, and terminal equipment communicates with the network equipment through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell. The cell can be a network equipment ( For example, the cell corresponding to the base station), the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell). The small cell here can include: urban cell (Metro cell), micro cell (Micro cell), pico cell ( Pico cell), femto cell (Femto cell), etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-rate data transmission services.

Figure 1 illustrates a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one implementation, the communication system 100 may include multiple network devices 110 , and the coverage of each network device 110 may include other numbers of terminal devices 120 , which is not limited in this embodiment of the present application.

In one implementation, the communication system 100 may also include other network entities such as Mobility Management Entity (MME), Access and Mobility Management Function (AMF), etc. This application implements This example does not limit this.

Among them, network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks used to communicate with access network equipment. The access network equipment can be a long-term evolution (long-term evolution, LTE) system, a next-generation (mobile communication system) (next radio, NR) system or authorized auxiliary access long-term evolution (LAA- Evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also known as "small base station"), pico base station, access point (access point, AP), Transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc.

It should be understood that in the embodiments of this application, devices with communication functions in the network/system may be called communication devices. Taking the communication system shown in Figure 1 as an example, the communication equipment may include network equipment and terminal equipment with communication functions. The network equipment and terminal equipment may be specific equipment in the embodiments of the present application, which will not be described again here; the communication equipment also It may include other devices in the communication system, such as network controllers, mobility management entities and other network entities, which are not limited in the embodiments of this application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is just an association relationship that describes related objects, indicating that three relationships can exist. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and they exist alone. B these three situations. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship.

It should be understood that the "instruction" mentioned in the embodiments of this application may be a direct instruction, an indirect instruction, or an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B. relation.

In the description of the embodiments of this application, the term "correspondence" can mean that there is a direct correspondence or indirect correspondence between the two, it can also mean that there is an associated relationship between the two, or it can mean indicating and being instructed, configuration and being. Configuration and other relationships.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be optionally combined with the technical solutions of the embodiments of the present application, and they all belong to the embodiments of the present application. protected range.

Currently, with people's pursuit of speed, delay, high-speed mobility, energy efficiency, and the diversity and complexity of services in future life, the ^3rd Generation Partnership Project (3GPP) international standards organization has begun Research and develop 5G. The main application scenarios of 5G are: enhanced mobile ultra-broadband (eMBB), low-latency and high-reliability communication (Ultra Reliability and Low Latency Communication, URLLC), and massive machine type communications (Massive Machine Type Communications, mMTC).

eMBB still aims at users to obtain multimedia content, services and data, and its demand is growing rapidly. On the other hand, since eMBB may be deployed in different scenarios, such as indoors, urban areas, rural areas, etc., its capabilities and requirements are also quite different, so it cannot be generalized and must be analyzed in detail based on specific deployment scenarios. Typical applications of URLLC include: industrial automation, power automation, telemedicine operations (surgery), traffic safety and security, etc. Typical features of mMTC include: high connection density, small data volume, delay-insensitive services, low cost and long service life of the module.

In order to reduce air interface signaling and quickly restore wireless connections and data services in the 5G network environment, a new Radio Resource Control (RRC) state is defined, namely the RRC_INACTIVE state. This state is different from the RRC_IDLE and RRC_ACTIVE states.

RRC_IDLE: Mobility is cell selection reselection based on User Equipment (User Equipment, UE). Paging is initiated by the Core Network (Core Network, CN), and the paging area is configured by the CN. There is no UE Access Stratum (AS) context on the base station side. There is no RRC connection.

RRC_CONNECTED: There is an RRC connection, and the base station and the UE have a UE AS context. The network side knows the location of the UE at the specific cell level. Mobility is network-side controlled mobility. Unicast data can be transmitted between the UE and the base station.

RRC_INACTIVE: Mobility is UE-based cell selection reselection. There is a connection between CN and New Radio Technology (New Radio, NR). The UE AS context exists on a base station. Paging is performed by the Radio Access Network (Radio Access Network). , RAN) trigger, the RAN-based paging area is managed by the RAN, and the network side knows that the location of the UE is based on the RAN paging area level.

In 5G, the maximum channel bandwidth can be 400MHZ (bandwidth carrier), which is very large compared to the maximum 20M bandwidth of Long Term Evolution (LTE). If the UE keeps working on a wideband carrier, the power consumption of the UE is very large. Therefore, it is recommended that the RF bandwidth of the UE can be adjusted according to the actual throughput of the UE. The motivation for introducing the BandWidth Part (BWP) for this purpose is to optimize the power consumption of the UE. For example, if the UE's rate is very low, a smaller bandwidth can be configured for the UE (Figure 2a). If the UE's rate requirements are very high, a larger bandwidth can be configured for the UE (Figure 2b). If the UE supports high rates or operates in Carrier Aggregation (CA) mode, multiple BWPs can be configured (Figure 2c). Another purpose of BWP is to trigger the coexistence of multiple basic parameter sets (numerology) in a cell.

The UE currently in idle state or inactive state resides on the initial BWP. This BWP is visible to UE in idle state or inactive state. In this BWP, you can obtain information such as Master Information Block (MIB), Remaining Minimum System Information (RMSI), Open Systems Interconnection (OSI), and paging.

Common frequency resource (CFR) of NR Multimedia Broadcast Multicast Services (MBMS)/Multicast Broadcast Service (MBS).

CFR is a design concept introduced during the NR MBS discussion to distinguish it from BWP. CFR is a continuous set of frequency domain resources located on the carrier and is used to receive MBS services. From the perspective of a single UE, a CFR is a continuous set of frequency domain resources used to receive downlink MBS service data. From a system perspective, CFR is used to send MBS service data. A group of UEs in the connected state (RRC_CONNECTED) receive MBS multicast/multicast in the CFR, and UEs in the non-connected state (RRC_IDLE/RRC_INACTIVE) receive MBS multicast on the CFR. Receive MBS broadcasts.

MBMS and Single Cell Point To Multipoint (SC-PTM) system in LTE

Multimedia Broadcast Multicast Service (MBMS) is a service introduced in 3GPP Release 6 (Release 6, R6). Multimedia broadcast multicast service is a technology that transmits data from one data source to multiple user devices by sharing network resources. While providing multimedia services, it can effectively utilize network resources and achieve higher-rate (256kbps) multimedia service broadcasting. and multicast.

Due to the low spectrum efficiency of MBMS in 3GPP R6, it is not enough to effectively carry and support the operation of mobile TV-type services. Therefore, in the wireless access network long-term evolution standard (Long Term Evolution, LTE) project, 3GPP clearly proposed to enhance the support capabilities for downlink high-speed multimedia broadcast multicast service services, and determined the design requirements for the physical layer and air interface.

eMBMS was introduced to LTE networks in R9. eMBMS proposes the concept of Single Frequency Network (SFN), which uses a unified frequency to send data to all cells at the same time, but must ensure synchronization between cells. This method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the spectrum efficiency will also be greatly improved accordingly. And realize the broadcast and multicast of services based on Internet Protocol (IP) multicast protocol.

In LTE/Long Term Evolution Advanced (LTE-A), MBMS only has a broadcast bearer mode and no multicast bearer mode.

Reception of MBMS services is applicable to UEs in RRC_CONNECTED or RRC_IDLE state.

As shown in Figure 3, SC-PTM is introduced in R13. SC-PTM is based on the MBMS network architecture, and the Multi-cell/multicast Coordination Entity (MCE) decides to use the SC-PTM transmission method or the Multimedia Broadcast multicast service Single Frequency Network (Multimedia Broadcast multicast service Single Frequency Network , MBSFN) transmission method.

Introducing new logical channels Single Cell Multicast Control Channel (SC-MCCH) (logical channel identify (logical channel identify, LCID) = 11001) and Single Cell Multicast Transport Channel (Single Cell Multicast Transport Channel, SC-MTCH) (LCID=11001), mapped to the DL-SCH transmission channel, Physical Downlink Shared Channel (PDSCH) physical channel. SC-MCCH and SC-MTCH do not support Hybrid Automatic Repeat-reQuest (HARQ) operations.

A new system information block (SIB) type is introduced, SIB20 to transmit SC-MCCH configuration information. There is only one SC-MCCH in a cell. Configuration information includes: SC-MCCH modification period, repetition period, and radio frame and subframe configuration information.

SC-MCCH scheduled radio frame: SFN mod MCCH-repetition period (Repetition Period) = MCCH-Offset (offset).

The subframe scheduled by SC-MCCH is indicated by SC-MCCH-Subframe (subframe).

SC-MCCH only transmits one message SC-PTMConfiguration (configuration), which is used to configure the configuration information of SC-PTM. Introduce a new wireless network temporary identifier (Radio Network Temporary Identifier, RNTI), single cell RNTI (Single Cell RNTI, SC-RNTI) (can be fixed value FFFC) to identify SC-MCCH on the physical downlink control channel (Physical Downlink Control Channel) , scheduling information on PDCCH).

Introduce a new RNTI, Single Cell Notification RNTI (SC-N-RNTI) (can be fixed value FFFB), to identify the PDCCH for SC-MCCH change notification. Use one of the 8 bits in the Downlink Control Information (DCI) 1C to indicate the change notification. The modification period boundary is defined as SFN mod m=0, where m is the modification period configured in SIB20 such as sc-mcch-ModificationPeriod; mod represents the modulo operation.

In NR, the Radio Link Control (Radio Link Control, RLC) Acknowledgment Mode (AM) mode has an Automatic Repeat-reQuest (ARQ) feedback mechanism. The receiving end sends an RLC status report to feedback whether the reception status of the RLC packet is Acknowledgment (ACK) or No Acknowledge (NACK). The sender can repeatedly transmit the RLC packet that feeds back the NACK number of the Secondary Node (SN).

Downstream BWP configuration

The downlink BWP is configured through the BWP-Downlink (bandwidth part downlink) parameter. As shown in the first paragraph of the Autonomous System Number (ASN).1 code below, this parameter includes the bwp-Id (bandwidth part identification) field to identify the ID of the current BWP, and bwp-Common (the bandwidth part public) is used to Configure the public parameters of the downlink BWP. As shown in the second paragraph of ASN.1 encoding below, the genericParameters (general parameters) in BWP-DownlinkCommon (bandwidth part downlink common) are used to configure the frequency domain starting point of the downlink BWP and the included physical resource block (Physical Resource Block, PRB) number. For a terminal-dedicated unicast BWP, the bwp-Dedicated (bandwidth part dedicated) parameter in BWP-Downlink will configure the downlink reception parameters on the downlink BWP. As shown in the third paragraph of ASN.1 encoding below, it includes at least pdcch-Config (PDCCH configuration), pdsch-Config (PDSCH configuration), and sps-Config (SPS configuration). As shown in the second section of ASN.1 encoding, pdcch-Config is used to indicate the PDCCH transmission mode on the downlink BWP, pdsch-Config is used to indicate the PDSCH transmission mode on the downlink BWP, and sps-Config is used to indicate the PDCCH transmission mode on the downlink BWP. SPS configuration.

The first ASN.1 encoding:

The second ASN.1 encoding:

The third paragraph of ASN.1 encoding:

...,

How NR MBS is spread

For MBS services, base station scheduling and transmission methods include the following:

(1)Broadcast

Sending MBS services by broadcasting is applicable when the terminal is in the RRC_IDLE/RRC_INACTIVE (non-connected) state, and when the terminal is in the RRC_CONNECTED (connected) state. In other words, the MBS service transmitted through broadcasting can be received by the terminal no matter what link state it is in, as long as it is within the coverage area.

(2)Multicast/Multicast

Sending MBS services to a group of terminals in multicast mode is applicable when all terminals in the group are in the RRC_CONNECTED state. The base station sends the same MBS service to a group of terminals through one-to-many PTM transmission.

(3)Unicast (Unicast)

Sending MBS services to each terminal in unicast mode is suitable for terminals in the RRC_CONNECTED state. The base station sends the same MBS services to each terminal through one-to-one PTP transmission.

NR MBS group scheduling method

In NR MBS, one-to-many multicast transmission needs to be supported. In this transmission method, the base station needs to schedule the public PDSCH by sending a common downlink control channel. The public PDCCH and the public PDSCH are in a common frequency domain range (CFR , sent within Common Frequency Resource). Currently, the following alternative CFR configuration methods exist:

Type 1: The CFR is configured as an MBS-specific BWP. The MBS-specific BWP is associated with the terminal's dedicated unicast BWP, and the subcarrier spacing and cyclic prefix configured on the CFR are the same as those configured on the terminal's dedicated unicast BWP.

Second type: CFR is configured as multiple consecutive PRBs within the terminal-specific unicast BWP range.

The advantage of the first method is that CFR can continue to use the relevant BWP signaling configuration, which helps reduce the workload of the standard. However, since CFR is defined as BWP, if the terminal is required to receive unicast in the dedicated unicast BWP and receive multicast in the CFR at the same time, it means that the terminal needs to receive downlink transmission on both BWPs at the same time. However, the terminal is only capable of receiving downlink on one BWP at a given time. In addition, even if the terminal receives unicast and multicast at different times, since they are located in different BWPs, BWP switching delay will be introduced. The second method can avoid the problem of BWP handover, but because the CFR in this method is multiple consecutive PRBs, the current BWP-based signaling configuration cannot be used, and the resource range and uplink and downlink transmission parameters of the CFR need to be redesigned. The configuration method has a greater impact on the standard.

In addition, since the public PDCCH that schedules the public PDSCH needs to be sent to multiple receiving terminals at the same time, in order to ensure that the number of public DCI bits carried in the public PDCCH determined by the multiple terminals is the same, the terminals cannot determine according to the configuration of their respective dedicated unicast BWPs. The number of bits of the public DCI. In addition, since the number of PRBs in the CFR may be different from the initial BWP or CORESET (ControlResourceSet, Control Resource Set) #0 (COntrol REsource SET 0) currently configured by the terminal, the terminal cannot determine the public DCI bits through the initial BWP or CORESET#0 number. Therefore, inevitably, the number of public DCI bits may be different from the number of DCI bits received by the terminal in the relevant USS or CSS. Then, in order to reduce the implementation complexity of the terminal, currently the terminal can only receive up to 4 DCI bits with different numbers in a cell. Among them, the number of DCI bits scrambled by the cell-specific RNTI (Cell RNTI, C-RNTI) does not exceed 3 types.

NR MBS group scheduling method

As shown in Figure 4a, Figure 4b and Figure 4c, there are three ways to schedule and transmit MBS services, among which PTM1 and Point to Point (PTP) are already supported. Group-shared PDCCH/PDSCH means that the PDCCH/PDSCH sent by the base station on a set of time-frequency resources can be received by multiple UEs in the same group. The PTM scheduling method mentioned in this solution can refer to PTM1.

PTM 1: For multiple UEs in the same group in the connected state, the group-shared PDCCH is used to schedule the group-shared PDSCH. The cyclic redundancy check (Cyclic Redundancy Check, CRC) of the group-shared PDCCH is scrambled using the group-shared RNTI, and the group-shared PDSCH is used. Use the same group to share RNTI for scrambling.

PTM 2: For multiple UEs in the same group in the connected state, use the UE-specific PDCCH scheduling group to share the PDSCH for each UE. The CRC of the UE-specific PDCCH is scrambled using the UE-specific RNTI (i.e. C-RNTI), and the group-shared PDSCH is used. Group shared RNTI scrambling.

PTP: For connected UEs, each UE uses the UE-specific PDCCH to schedule the UE-specific PDSCH. The CRC of the UE-specific PDCCH is scrambled using the UE-specific RNTI (i.e., C-RNTI). The UE-specific PDSCH uses the UE-specific RNTI (i.e., C-RNTI). RNTI) scrambling.

NR MBS group scheduling transmission method

The MBS service retransmission mechanism based on HARQ-ACK feedback in the connected state can support the following methods:

Method 1: Initial transmission of PTM1 + retransmission of PTM1

Method 2: Initial transmission of PTM1 + retransmission of PTP

NR MBS multicast and unicast use HARQ process ID (HARQ process ID, HPID)

The HPID of the system is shared between multicast/multicast and unicast (HARQ process ID: 0~15). The specific allocation of HPID is determined by the base station implementation. If HPID#1 is first allocated to the transmission of a transport block (TB) 1 of the MBS service, when the initial transmission and potential retransmission of TB1 are completed, the base station will continue to allocate HPID#1 to the transmission of TB2. , at this time TB2 is used for unicast transmission of UE3. When the initial transmission and potential retransmission of TB2 are completed, the base station will continue to allocate HPID#1 to the transmission of TB3. At this time, TB3 is used for the transmission of MBS services.

HPID and New Data Indicator (NDI) determine the method of initial transmission and retransmission

HPID and NDI jointly determine whether the currently transmitted TB is an initial transmission or a retransmission. For example, the currently received HPID#1 corresponds to NDI=0 carried in the DCI.

Comparing the NDI=1 corresponding to the previously received HPID#1, it can be determined that the currently received TB is the initial transmission of a new TB. The UE will clear the data information of the previous TB stored in the cache, and then store the initial transmission of the newly received TB and the potentially received retransmission in the cache for soft merging.

Comparing the NDI=0 corresponding to the previously received HPID#1, it can be determined that the currently received TB is a retransmission.

In the related technology, the network side determines the number of TB repeated transmissions of an MBS service through configuration. Once the configuration is determined, if a TB is repeated 4 times, the number of repeated transmissions for all TBs corresponding to this service will be 4 times for a long period of time before the signaling is updated. In addition, each TB is configured with only one opportunity to provide feedback in the uplink feedback resource at the end of the repeated transmission.

In the related art, repeated transmission of TB is as described above. Once the number of TB repetitions is configured, it cannot be changed in the short term. When the channel conditions are very good, when all UEs receive a TB, they can decode it correctly after receiving it once or twice. Repeated transmission of the remaining TB is obviously redundant and takes up a lot of downlink transmission resources, causing waste. In addition, the feedback for each TB is uniformly fed back to one TB at the end of the repeated transmission. If the number of repeated transmissions of a TB is 8, then the UE needs to complete 8 transmissions before it can provide feedback for this TB. If the UE decodes successfully the first time, the waiting time will be very long, resulting in a long delay. In related technologies, multiple repeated transmissions of one TB require the UE to receive them. Allowing the UE to receive multiple transmissions at all times will actually cause the UE to decode continuously, which not only consumes power, but also is not conducive to the effective use of resources.

Figure 5 is a schematic flow chart of a repeated transmission method 500 according to an embodiment of the present application. This method can optionally be applied to the system shown in Figure 1, but is not limited thereto. The method includes at least part of the following.

S510. The terminal device performs subsequent repeated transmission related processing according to the first number of repeated transmissions of the downlink data and the transmission status of the downlink data.

In one implementation, the downlink data is in the transport block TB and/or the physical downlink shared channel PDSCH.

In this embodiment of the present application, the terminal device may perform subsequent processing related to the repeated transmission of the TB based on the first number of repeated transmissions of the TB and the transmission status of the TB. The terminal equipment may perform subsequent processing related to the repeated transmission of the PDSCH based on the first number of repeated transmissions of the PDSCH and the transmission situation of the PDSCH.

In this embodiment of the present application, the subsequent repeated transmission related processing performed by a terminal device such as a UE may include a variety of processes, which may mainly include: after receiving the current TB and/or PDSCH, the UE performs processing related to the TB and/or the PDSCH. Repeat some operations related to transmission. For example, stop receiving repeated transmissions, continue to receive repeated transmissions, perform uplink feedback, etc.

In one implementation, performing subsequent repeated transmission related processing includes: determining whether to receive the repeatedly transmitted downlink data.

In this embodiment of the present application, the UE may determine whether downlink data is received, the current number of received downlink data, the number of first repeated transmissions N (that is, the total number of times), and the decoding situation after the received downlink data. or multiple methods to determine whether to continue to receive the downlink data repeatedly transmitted by the network device.

In one implementation, determining whether to receive the repeatedly transmitted downlink data includes:

Method 1: If the terminal device successfully decodes the downlink data received at least once, it will no longer receive the repeatedly transmitted downlink data.

For example, if the current number of transmissions of TB1 is the second time, the number of first repeated transmissions N is 6 times, and the UE successfully decodes this TB1, it may no longer receive the third to sixth transmissions of TB1 from the network device. Repeat the transfer. Of course, the network side may not repeatedly transmit the third to sixth TB1 after learning that the UE has successfully decoded the second TB1.

Method 2: When the received downlink data fails to be decoded, the terminal device continues to receive the repeatedly transmitted downlink data until the current number of transmissions reaches the first number of repeated transmissions or the received downlink data is successfully decoded.

For another example, if the current number of transmissions of TB2 is the second and the number of first repeated transmissions N is 6, but the UE fails to decode this time TB2, the UE continues to receive the third repeated transmission of TB2. If the third received TB2 is decoded successfully, the network device may no longer receive repeated transmissions of TB2 from the fourth to sixth times. If the decoding of the 3rd to 6th received TB2 fails, stop receiving repeated transmissions of TB2.

Method 3: In the case where no downlink data is received, the terminal device continues to receive the repeatedly transmitted downlink data until the current number of transmissions reaches the first number of repeated transmissions or the received downlink data is decoded successfully.

For another example, if the current number of transmissions of TB3 is the third and the first number of repeated transmissions N is 6, but the UE does not receive the third repeated transmission of TB3, the UE continues to receive the fourth repeated transmission of TB3. If the fourth received TB3 is successfully decoded, the network device may no longer receive repeated transmissions of the fifth to sixth TB3s. If the decoding of the 4th to 6th received TB3 fails, stop receiving repeated transmissions of TB2.

In one implementation, as shown in Figure 6, the method 600 includes: S610. The terminal device receives first indication information, where the first indication information includes the first number of repeated transmissions and/or the first repetition interval.

In this embodiment of the present application, the steps of the method 600 and the above-mentioned method 500 can be implemented separately or combined.

In this embodiment of the present application, the UE may receive first indication information from a network device such as a base station. The indication information may be dynamically configured or semi-statically configured. The first number of repeated transmissions may be the total number of repeated transmissions of downlink data by the network device, or the total number of repeated transmissions of the terminal device receiving downlink data. The total number of times the network device repeatedly transmits downlink data and the total number of times the terminal device receives downlink data can be the same or different. The first repetition interval may represent an interval for repeated transmission of downlink data, and the first repetition interval may be a time slot or a symbol.

In an implementation manner, the first indication information is in at least one of the following: radio resource control (RRC) signaling; downlink control information (DCI).

In the embodiment of this application, RRC signaling is a kind of high-level configuration information. The network device may first deliver the first indication information to the terminal device through high-level configuration information. DCI is a dynamic indication method. The network device can send a PDCCH to the terminal device, the PDCCH carries DCI, and the DCI carries the first indication information. The terminal device may use the first indication information to include the first number of repeated transmissions and/or the first repetition interval to perform subsequent repeated transmission related processing.

In this embodiment of the present application, the feedback mode of the terminal device may be an acknowledgment/non-acknowledgment (ACK/NACK) feedback mode or a non-acknowledgement (NACK-only) feedback mode. Feedback mode can also be called feedback mode. In the ACK/NACK feedback mode, the terminal device can feed back confirmation information to the network device, and can also feed back non-confirmation information to the network device. In this case, the uplink feedback information sent by the terminal device may be acknowledgment (ACK) information or non-acknowledgement (NACK) information. In the NACK-only feedback mode, if it is in the confirmation state, the terminal device does not feedback information. It only feeds back non-confirmation information to the network device in the non-confirmation state.

In one implementation, performing subsequent repeated transmission related processing also includes:

After receiving n times of downlink data, the terminal device sends uplink feedback information once; where n is greater than or equal to 1, and n is less than or equal to the first number of repeated transmissions N, and N is greater than or equal to 1.

In one implementation, the uplink feedback information is in a physical uplink control channel (Physical Uplink Control Channel, PUCCH) and/or a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH).

For example, the terminal device may send a PUCCH carrying uplink feedback information to the network device every time it receives a TB or PDSCH. For another example, the terminal device can send a PUCCH carrying uplink feedback information to the network device once every time it receives TB or PDSCH twice.

In one implementation, after receiving n times of downlink data, the terminal device sends uplink feedback information once, including:

If at least one of the n times of received downlink data is decoded successfully, the terminal device sends the uplink feedback information including confirmation information; and/or

When decoding of m times of downlink data received among the n times of downlink data fails, the terminal device sends the uplink feedback information including non-confirmation information; where m is greater than or equal to 1 and m is less than or equal to n.

In this embodiment of the present application, the terminal device provides feedback every n times when it receives downlink data. m can represent the threshold of the number of decoding failures. The terminal device can feedback non-confirmation information if the number of decoding failures is greater than the threshold.

For example, in the ACK/NACK feedback mode, the terminal equipment receives 1 uplink feedback information every 3 times of TB or PDSCH feedback. If the TB or PDSCH received three times are all decoded successfully, or one or two times are decoded successfully, the terminal device can send a PUCCH including ACK information to the network device. If these three received TBs or PDSCHs all fail to be decoded or the number of decoding failures is greater than a certain threshold, such as 2 times, the terminal device sends a PUCCH including NACK information.

For another example, in the NACK-only feedback mode, the terminal equipment receives 1 uplink feedback information every 3 times of TB or PDSCH feedback. If the TB or PDSCH received three times are all decoded successfully, or one or two times are decoded successfully, the terminal device does not send the PUCCH. If these three received TBs or PDSCHs all fail to be decoded or the number of decoding failures is greater than a certain threshold, such as 2 times, the terminal device sends a PUCCH including NACK information.

In one implementation, when at least one of the s downlink data received is decoded successfully, the terminal device does not receive the repeatedly transmitted downlink data, where s is greater than or equal to 1, and s is less than The first number of repeated transmissions is N.

In this embodiment of the present application, s may represent the number of times the terminal device receives downlink data. For example, if the first number of repeated transmissions N is equal to 4, and the terminal device receives the first TB and successfully decodes the TB, it will no longer receive repeated transmissions from the second to the fourth TB. For another example, if the first number of repeated transmissions N is equal to 5 and the terminal device does not receive the first PDSCH, the terminal device continues to receive the second repeated transmission of the PDSCH. If the second PDSCH is decoded successfully, the terminal device will no longer receive the repeated transmission of the third, fourth and fifth PDSCH. For another example, if the first repeated transmission number N is equal to 5, the terminal equipment receives the 1st, 2nd and 3rd PDSCH, and the 2nd PDSCH is decoded successfully, the terminal equipment will no longer receive the 4th and 5th times. Repeated transmission of PDSCH.

In one implementation, as shown in Figure 7, the method 700 includes: S710, the terminal device receives second indication information, the second indication information includes a second number of repeated transmissions and/or a second repetition interval, wherein, The second number of repeated transmissions is determined based on the feedback situation of the downlink data and the first number of repeated transmissions, and the second number of repeated transmissions is different from the first number of repeated transmissions.

In this embodiment of the present application, the method 700 and the steps of the above-mentioned methods 500 and/or 600 can be implemented separately or combined. For example, the first indication information may indicate that the current number of repeated transmissions of the TB and/or the PDSCH is the first number of repeated transmissions. The second indication information may indicate that the number of repeated transmissions of the next TB and/or PDSCH is adjusted to the second number of repeated transmissions. For another example, for the current TB and/or PDSCH, the terminal equipment can determine whether to receive the repeatedly transmitted downlink data based on the first number of repeated transmissions of downlink data and the transmission situation of the downlink data, and determine whether to receive the repeatedly transmitted downlink data for the next TB and/or PDSCH. The second number of repeated transmissions of the downlink data and the transmission situation of the downlink data are used to determine whether to receive the repeatedly transmitted downlink data. For another example, for the current TB and/or PDSCH, the terminal equipment receives all the data according to the first number of repeated transmissions, and for the next TB and/or PDSCH, the second number of repeated transmissions of downlink data and the transmission status of the downlink data are used to determine whether Receive the repeatedly transmitted downlink data.

In this embodiment of the present application, if the current number of transmissions received and successfully decoded by the terminal device of downlink data is less than the first number of repeated transmissions N, the network device can appropriately reduce the first number of repeated transmissions N to obtain the second number of repeated transmissions N. '. If the terminal device cannot receive and successfully decode the downlink data N times, the network device can appropriately increase the first number of repeated transmissions N to obtain the second number of repeated transmissions N'.

In one implementation, the second indication information is in DCI.

In this embodiment of the present application, the second number of repeated transmissions can be configured in a dynamic indication manner. For example, the terminal device receives a PDCCH from the network device, the PDCCH carries DCI, and the DCI carries second indication information. The DCI carrying the first indication information and the DCI carrying the second indication information may be different or the same.

In this embodiment of the present application, in multicast, multicast and other related business scenarios, the network device may send the same downlink data to multiple terminal devices at one time. Some terminal devices may be able to receive and successfully decode the downlink data, while other terminal devices may not receive or successfully decode the downlink data. In addition, the feedback modes of the terminal device also include the above-mentioned ACK/NACK feedback mode and NACK-only feedback mode. Therefore, there may be multiple specific feedback situations from the terminal device. Based on different feedback conditions from the terminal device, the network device may need to adjust the number of repeated transmissions.

In one implementation, if the feedback situation of the downlink data satisfies at least one of the following, then the first number of repetitions is adjusted by the network device to the second number of repetitions:

The uplink feedback information of the M target terminal devices includes acknowledgment information (ACK/NACK feedback mode);

M target terminal devices did not feed back uplink feedback information (NACK-only feedback mode);

The uplink feedback information of P target terminal devices includes non-acknowledgement information (ACK/NACK feedback mode or NACK-only feedback mode);

P target terminal devices did not feed back uplink feedback information (NACK-only feedback mode);

Wherein, M is less than or equal to the total number Y of target terminal devices sent by the network device through point-to-multipoint (PTM), and M is greater than or equal to the first threshold; and/or, M is less than or equal to the first number of repeated transmissions N, And the ratio of M to Y is greater than or equal to the second threshold;

Wherein, P is less than or equal to Y, and P is less than or equal to the third threshold; and/or, P is less than or equal to the first number of repeated transmissions N, and the ratio of P to Y is less than or equal to the fourth threshold.

In the embodiment of the present application, for a specific example of the network device adjusting the number of repeated transmissions, please refer to the following related descriptions of the embodiments of the network device.

Figure 8 is a schematic flow chart of a repeated transmission method 800 according to an embodiment of the present application. This method can optionally be applied to the system shown in Figure 1, but is not limited thereto. The method includes at least part of the following.

S810. The network device performs subsequent repeated transmission related processing based on the first number of repeated transmissions of the downlink data and the feedback of the downlink data.

In one implementation, performing subsequent repeated transmission related processing includes: determining whether to repeatedly transmit the downlink data.

In one implementation, determining whether to repeatedly transmit the downlink data includes at least one of the following:

If the network device receives at least one uplink feedback information for the downlink data including acknowledgment information, the network device will not re-transmit the downlink data;

If the network device does not receive uplink feedback information for the downlink data, it will not re-transmit the downlink data;

When the network device receives the uplink feedback information for the downlink data that includes non-confirmation information, it repeatedly transmits the downlink data until it receives the uplink feedback information for the downlink data that includes confirmation information or the current number of transmissions reaches the th. until the number of repeated transmissions.

In one implementation, as shown in Figure 9, the method 900 includes: S910. The network device sends first indication information, where the first indication information includes the first number of repeated transmissions and/or the first repetition interval.

In this embodiment of the present application, the steps of the method 900 and the above-mentioned method 800 can be implemented separately or combined.

In an implementation manner, the first indication information is in at least one of the following: RRC signaling; DCI.

In one implementation, the method further includes: the network device receiving uplink feedback information once after sending downlink data n times; wherein n is greater than or equal to 1, and n is less than or equal to the first number of repeated transmissions N, N is greater than or equal to 1.

In one implementation, after sending downlink data n times, the network device receives uplink feedback information once, including:

If at least one of the n times of sent downlink data is decoded successfully, the network device receives the uplink feedback information including confirmation information; and/or

When decoding of m times of downlink data among the n times of sent downlink data fails, the network device receives the uplink feedback information including non-acknowledgment information; where m is greater than or equal to 1 and less than or equal to n.

In one implementation, performing subsequent repeated transmission related processing includes:

The network device adjusts the first number of repeated transmissions according to the feedback of the downlink data.

In one implementation, the network device adjusts the first number of repeated transmissions according to the feedback of the downlink data, including:

The network device adjusts the first number of repeated transmissions to a second number of repeated transmissions according to the feedback of the downlink data. The second number of repeated transmissions is different from the first number of repeated transmissions.

In one implementation, the feedback situation of the downlink data satisfies at least one of the following:

The uplink feedback information of the M target terminal devices includes confirmation information;

M target terminal devices did not feed back uplink feedback information;

The uplink feedback information of P target terminal devices includes non-confirmation information;

P target terminal devices did not feed back uplink feedback information;

Wherein, M is less than or equal to the total number Y of target terminal devices sent by the network device through point-to-multipoint PTM, and M is greater than or equal to the first threshold; and/or, M is less than or equal to the first number of repeated transmissions N, and M The ratio to Y is greater than or equal to the second threshold;

For example, the network device sends TB1 to Y terminal devices, and the first number of repeated transmissions of TB1 is N. In the ACK/NACK feedback mode, the network device receives uplink feedback information including ACK information from M target terminal devices, and M is greater than If the first threshold of the number of successfully transmitted devices is set, and M is less than N, then the network device adjusts the first number of repeated transmissions to the second number of repeated transmissions. In this case, the second number of repeated transmissions may be smaller than the first number of repeated transmissions. For example, if the first number of repeated transmissions is 8, the network device sends TB1 to 40 terminal devices, and receives ACK information fed back by 30 terminal devices. Assuming that the first threshold is 25 and the number of feedback ACK information terminal devices, 30, is greater than the second threshold, the network device adjusts the first number of repeated transmissions to the second number of repeated transmissions, which is 4. Assuming that the second threshold is 70%, then the ratio of the number of feedback ACK information terminal devices M = 30 to Y = 40 is 75% greater than the second threshold, then the network device adjusts the first number of repeated transmissions to the second repeated transmissions. The number of times is 4.

For another example, the network device sends TB1 to Y terminal devices, and the number of first repeated transmissions of TB1 is N. In the NACK-only feedback mode, the network device does not receive the uplink feedback information from M target terminal devices. The first number of repeated transmissions is adjusted to the second number of repeated transmissions. For example, if the first number of repeated transmissions is 8, the network device sends TB1 to 40 terminal devices, but no ACK information is received from 30 terminal devices. Assuming that the first threshold is 25 and the number 30 of terminal devices that have not fed back information is greater than the second threshold, the network device adjusts the first number of repeated transmissions to the second number of repeated transmissions, which is 4. Assuming that the second threshold is 70%, then the ratio of the number of terminal devices M=30 to Y=40 that does not feedback information is 75% greater than the second threshold, then the network device adjusts the first number of repeated transmissions to the second number of repeated transmissions. is 4.

For another example, the network device sends TB1 to Y terminal devices, and the first number of repeated transmissions of TB1 is N. In the ACK/NACK feedback mode or NACK-only feedback mode, the network device receives NACK messages from P target terminal devices. According to the uplink feedback information of the information, the first number of repeated transmissions is adjusted to the second number of repeated transmissions. For example, if the first number of repeated transmissions is 8, the network device sends TB1 to 40 terminal devices, receives ACK information from 30 terminal devices, and the first threshold is 25, then the network device adjusts the first number of repeated transmissions to 40 terminal devices. The number of repeated transmissions is 4.

For another example, the network device sends TB1 to Y terminal devices, and the number of first repeated transmissions of TB1 is N. In the NACK-only feedback mode, the network device does not receive uplink feedback information from P target terminal devices. The first number of repeated transmissions is adjusted to the second number of repeated transmissions. For example, if the first number of repeated transmissions is 8, the network device sends TB1 to 40 terminal devices, but no ACK information is received from 30 terminal devices, and the first threshold is 25, then the network device adjusts the first number of repeated transmissions to The second number of repeated transmissions is 4.

The adjusted second number of repeated transmissions can be used for repeated transmissions of TB2 or TB3 after this time TB1.

In one implementation, as shown in Figure 10, the method 1000 further includes: S1010. The network device sends second indication information, where the second indication information includes a second number of repeated transmissions and/or a second repetition interval.

In this embodiment of the present application, the method 1000 and the steps of the above-mentioned methods 800 and/or 900 can be implemented separately or combined.

In one implementation, the second indication information is in DCI.

In one implementation, the uplink feedback information is in PUCCH and/or PUSCH.

In one embodiment, the downlink data is in TB and/or PDSCH.

For specific examples of the network

device execution methods

800, 900, and 1000 in this embodiment, please refer to the relevant descriptions of network devices such as base stations in the

above methods

500, 600, and 700. For the sake of brevity, they will not be described again here.

Figure 1100 is a schematic block diagram of a terminal device 1100 according to an embodiment of the present application. The terminal device 1100 may include:

The processing unit 1110 is configured to perform subsequent repeated transmission related processing according to the first number of repeated transmissions of downlink data and the transmission status of the downlink data.

In one implementation, the processing unit is configured to perform subsequent repeated transmission related processing, including: determining whether to receive the repeatedly transmitted downlink data.

In one implementation, as shown in Figure 12, the terminal device 1200 may include the above-mentioned processing unit 1110. The terminal device 1200 may also include a first receiving unit 1210. The processing unit 1110 is used to determine whether to receive the repeatedly transmitted Downstream data includes:

If the received downlink data is decoded successfully at least once, instruct the first receiving unit 1210 to no longer receive the repeatedly transmitted downlink data;

If the received downlink data fails to be decoded, instruct the first receiving unit 1210 to continue receiving the repeatedly transmitted downlink data until the current number of transmissions reaches the first number of repeated transmissions or the received downlink data is decoded successfully;

In the case of no received downlink data, the first receiving unit 1210 is instructed to continue receiving the repeatedly transmitted downlink data until the current number of transmissions reaches the first number of repeated transmissions or the received downlink data is successfully decoded.

In one implementation, as shown in Figure 12, the terminal device 1200 further includes: a second receiving unit 1220, configured to receive first indication information, where the first indication information includes the first number of repeated transmissions and/or First repeat interval.

In one implementation, the first indication information is in at least one of the following:

Radio Resource Control (RRC) signaling;

Downlink Control Information (DCI).

In one implementation, the terminal device further includes a sending unit 1240, and the processing unit 1110 is configured to instruct the sending unit to send uplink feedback information once after receiving n times of downlink data; where n is greater than or equal to 1, and n is less than or equal to the first number of repeated transmissions N, and N is greater than or equal to 1.

In one implementation, the processing unit 1110 is configured to instruct the sending unit to send uplink feedback information once after receiving n times of downlink data, including:

If at least one of the n times of received downlink data is successfully decoded, instruct the sending unit 1240 to send the uplink feedback information including acknowledgment information; and/or

When decoding of m times of downlink data among the n times of received downlink data fails, instruct the sending unit 1240 to send the uplink feedback information including non-acknowledgement information; where m is greater than or equal to 1 and m is less than or equal to n. .

In one embodiment, the processing unit 1110 is also configured to instruct the first receiving unit 1210 not to receive the repeatedly transmitted downlink data when at least one of the s downlink data received is successfully decoded, wherein , s is greater than or equal to 1, and s is less than the first number of repeated transmissions N.

In one implementation, as shown in Figure 12, the terminal device 1200 further includes: a third receiving unit 1230, configured to receive second indication information, where the second indication information includes a second number of repeated transmissions and/or a second The repetition interval, wherein the second number of repeated transmissions is determined based on the feedback situation of the downlink data and the first number of repeated transmissions, and the second number of repeated transmissions is different from the first number of repeated transmissions.

In one implementation, the second indication information is in DCI.

M target terminal devices did not feed back uplink feedback information;

P target terminal devices did not feed back uplink feedback information;

In one implementation, the uplink feedback information is in the physical uplink control channel PUCCH and/or the physical uplink shared channel PUSCH.

The terminal devices 1100 and 1200 in the embodiment of the present application can realize the corresponding functions of the terminal devices in the foregoing

method

500, 600 and 700 embodiments. For the corresponding processes, functions, implementation methods and beneficial effects of each module (sub-module, unit or component, etc.) in the terminal equipment 1100 and 1200, please refer to the corresponding description in the above method embodiment, and will not be described again here. It should be noted that the functions described for each module (sub-module, unit or component, etc.) in the terminal devices 1100 and 1200 of the application embodiment can be implemented by different modules (sub-module, unit or component, etc.), or can be implemented by Implemented by the same module (submodule, unit or component, etc.).

Figure 13 is a schematic block diagram of a network device 1300 according to an embodiment of the present application. The network device 1300 may include:

The processing unit 1310 is configured to perform subsequent repeated transmission related processing according to the first number of repeated transmissions of downlink data and the feedback status of the downlink data.

In one implementation, the processing unit 1310 is configured to perform subsequent repeated transmission related processing, including: determining whether to repeatedly transmit the downlink data.

In one implementation, as shown in Figure 14, the network device 1400 also includes a first sending unit 1410. The processing unit 1310 is also used to determine whether to repeatedly transmit the downlink data, including at least one of the following:

If the received at least one uplink feedback information for the downlink data includes acknowledgment information, instruct the first sending unit 1410 not to repeatedly transmit the downlink data;

If no uplink feedback information for the downlink data is received, instruct the first sending unit 1410 not to re-transmit the downlink data;

When receiving the uplink feedback information for the downlink data including non-confirmation information, instruct the first sending unit 1410 to repeatedly transmit the downlink data until the uplink feedback information for the downlink data includes acknowledgment information or the current The number of transmissions reaches the first number of repeated transmissions.

In one implementation, as shown in Figure 14, the network device 1400 further includes: a second sending unit 1420, configured to send first indication information, where the first indication information includes the first number of repeated transmissions and/or First repeat interval.

In one implementation, as shown in Figure 14, the network device 1400 further includes: a receiving unit 1430, configured to receive uplink feedback information once after sending n downlink data; where n is greater than or equal to 1, and n is less than or equal to the first number of repeated transmissions N, and N is greater than or equal to 1.

In one implementation, the receiving unit 1430 is used for:

If at least one of the n times of sent downlink data is decoded successfully, receive the uplink feedback information including confirmation information; and/or

When decoding of m times of downlink data among the n times of sent downlink data fails, the uplink feedback information including non-acknowledgment information is received; where m is greater than or equal to 1 and less than or equal to n.

In one implementation, the processing unit 1310 is also configured to perform subsequent repeated transmission related processing, including: adjusting the first number of repeated transmissions according to the feedback of the downlink data.

In one implementation, the processing unit 1310 is further configured to adjust the first number of repeated transmissions according to the feedback of the downlink data, including: adjusting the first number of repeated transmissions to the second number of times according to the feedback of the downlink data. The second number of repeated transmissions is different from the first number of repeated transmissions.

M target terminal devices did not feed back uplink feedback information;

P target terminal devices did not feed back uplink feedback information;

In one implementation, as shown in Figure 14, the network device 1400 further includes: a third sending unit 1440, configured to send second indication information, where the second indication information includes the second number of repeated transmissions and/or the second Two repetition intervals.

In one implementation, the second indication information is in DCI.

In one embodiment, the downlink data is in TB and/or PDSCH.

The network devices 1300 and 1400 in the embodiments of this application can implement the corresponding functions of the network devices in the

aforementioned method

800, 900 and 1000 embodiments. For the corresponding processes, functions, implementation methods and beneficial effects of each module (sub-module, unit or component, etc.) in the network devices 1300 and 1400, please refer to the corresponding description in the above method embodiment, and will not be described again here. It should be noted that the functions described for each module (sub-module, unit or component, etc.) in the network devices 1300 and 1400 of the application embodiment can be implemented by different modules (sub-module, unit or component, etc.), or can be implemented by Implemented by the same module (submodule, unit or component, etc.).

The repeated transmission method provided by the embodiment of the present application may be a method of repeatedly sending TBs in a broadcast multicast service. This method can mainly include the following:

(1) Configure the number of repetitions and sending interval of a TB based on semi-static configuration.

(2) Indicate the number of repetitions and transmission interval of a TB according to the PDCCH, and adjust the number of repetitions and transmission interval of the next TB according to the HARQ-ACK feedback of the previous TB, and dynamically indicate the number of times of the currently scheduled TB through the PDCCH. Repeated transmission of information.

(3) For repeated transmissions of a TB, if there are multiple uplink feedbacks, the base station determines whether to continue to send the remaining repeated transmissions of this TB or not to send them again based on the current feedback information.

(4) In Semi-Persistent Scheduling (SPS, or semi-static scheduling), the number of repeated transmissions, intervals, and time-frequency resource locations of one TB in each cycle are determined through configuration. For multiple repeated transmissions of a TB, the UE decides whether to receive the remaining retransmissions of the TB based on whether the decoding of the TB has been received successfully; if the UE does not receive a certain transmission of a TB, it will continue to receive subsequent transmissions of the TB. Repeat the transfer.

Example 1: One TB, semi-static configuration feedback times

(1) According to the instruction information of the configuration of the higher layer configuration parameters, one PDSCH/TB is sent repeatedly N times, and the N PDSCH sending interval is G, where N≥1 is a positive integer and G≥0 is an integer.

(2) According to the configuration of high-level configuration parameters or the indication information of PDCCH/DCI, uplink feedback can be performed after N times of repeated transmission of a TB.

(a) ACK/NACK feedback mode: If the receiving UE successfully decodes the PDSCH at least once in ≤N receptions, it will feed back ACK to the base station through the uplink resource physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH); If the receiving UE does not successfully decode the PDSCH in ≤N receptions, it will feed back NACK to the base station through the uplink resource PUCCH or PUSCH. or

(b) NACK-only feedback mode: The receiving UE successfully decodes the PDSCH at least once in ≤N receptions, and does not feed back any information to the base station through the uplink resource PUCCH or PUSCH; the receiving UE does not feedback any information to the base station in ≤N receptions. If the PDSCH is not decoded successfully, NACK is fed back to the base station through the uplink resource PUCCH or PUSCH.

(3) If N repeated transmissions of PDSCH correspond to multiple uplink feedback resources, the base station can decide whether to continue sending the remaining PDSCH repetitions based on the feedback of a group of UEs (for example, Y UEs).

(4) Among the above configuration parameters, the number of repeated transmissions of a TB is a positive integer N≥1, for example, the priority candidate value is {2, 4, 6, 8, 16}.

(5) Among the above configuration parameters, the PDSCH transmission interval is G. For example, when G=0, it means that the N repeated transmissions of the PDSCH are continuous transmissions, that is, the time slot in which the PDSCH is located is a continuous time slot.

Example 1-1

(1) As shown in Figure 15, a TB is sent repeatedly 4 times. At this time, an uplink feedback resource PUCCH is configured. If the UE successfully decodes the PDSCH at least once in 4 (or less than 4) receptions, it passes the uplink resource Feed back ACK to the base station. If the UE does not successfully decode the PDSCH in 4 receptions (or less than 4 times), it will feed back NACK to the base station through the uplink resources.

(2) As shown in Figure 16, a TB is sent repeatedly 4 times. At this time, two uplink feedback resources PUCCH are configured, one PUCCH resource after the first two repeated transmissions, and one PUCCH resource after the last two repeated transmissions.

A UE's perspective: If the UE successfully decodes at least one of the first two PDSCHs received and feeds back ACK on the first PUCCH, the UE does not need to receive the last two PDSCHs.

Base station and all UE angles (in the case of PTM transmission):

(a) ACK/NACK feedback: For the first two PDSCH transmissions, the feedback from all receiving UEs is ACK, then the base station will no longer send the next two PDSCHs; for the first two PDSCH transmissions, if there is K (K ≥ 1) UEs feedback NACK, then the base station continues to send the last two PDSCHs.

(b) NACK-only feedback: For the first two PDSCH transmissions, all UEs do not feedback any information to the base station (that is, the decoding is successful), then the base station will no longer send the next two PDSCHs; for the first two PDSCH transmissions, If K (K≥1) UEs feedback NACK, the base station continues to send the last two PDSCHs.

A special case of Example 1: after each PDSCH, there is a PUCCH resource for the UE to send feedback information.

Example 2: One TB, dynamically indicating the number of feedback times

(1) According to the indication information of PDCCH/DCI, it is indicated that the number of repeated transmissions of one PDSCH/TB is N times, and the transmission interval of N PDSCHs is G, where N≥1 is a positive integer and G≥0 is an integer.

(2) According to the feedback situation after the previous TB is sent, if all UEs or more than X% of UEs feedback ACK (ACK/NACK feedback mode) or no feedback information (NACK-only feedback mode), then the next TB will be sent. When , the number of repetitions can be changed from N to N', and the updated N' information can be indicated in the PDCCH. Wherein, X% may be the ratio of the number of UEs that feed back ACK (ACK/NACK feedback mode) or no feedback information (NACK-only feedback mode) to the total number of UEs (in a PTM scenario).

Example 2-1

(1) As shown in Figure 17, when the base station sends TB1 to a group of Y (Y positive integer) UEs through PTM, the PDCCH indicates that the number of repetitions is 4 times.

(2) This group of UEs perform feedback on PUCCH resources. If M UEs among Y UEs feedback ACK (ACK/NACK feedback mode), or M UEs among Y UEs do not feedback (NACK-only feedback) model). When the base station sends TB2, it dynamically adjusts the number of repeated transmissions of TB2 and indicates the number of repetitions through the PDCCH.

For example, if the base station sends TB1 to 100 UEs through PTM and repeats it 4 times, and 90 UEs feedback ACK on the PUCCH, then when the base station sends TB2, it only repeats it 2 times.

(3) It can also be described in another way: the number of repetitions is adjusted based on the number of UEs that feedback NACK. If M UEs among Y UEs feedback NACK (both ACK/NACK and NACK-only feedback modes are available), when the base station sends TB2, it dynamically adjusts the number of repeated transmissions of TB2 and indicates the number of repetitions through the PDCCH.

For example, if the base station sends TB1 to 100 UEs four times and 10 UEs respond with NACK, then when the base station sends TB2, it can only send TB2 twice.

Example 3: Repeated transmission of TB in SPS

(1) According to the high-level configuration information, in semi-persistent scheduling, the number of repeated transmissions of one PDSCH/TB in each cycle is N, the repetition interval is G, and N and G are both positive integers. After N repetitions, there are corresponding PUCCH resources for the UE to report feedback information.

(2) When the UE receives a TB within a cycle, it can decide whether to continue to receive the next repetition of this TB based on each reception.

(3) As shown in Figure 18, when receiving TB1, the UE first receives the first transmission of TB1. If the decoding is successful, the UE will no longer receive the remaining two transmissions of TB1. The UE feeds back ACK on the PUCCH resource (ACK/NACK feedback mode) or does not feed back (NACK-only feedback mode).

(4) As shown in Figure 18, when the UE receives TB2, if the first reception and decoding of TB2 fails, it will continue to receive the second transmission of TB2; if the decoding still fails, it will continue to receive the third transmission until the All repeated transmissions of TB2 during this cycle are received and decoded. The UE determines the information to be fed back on the PUCCH based on these three decodings of TB2; if no decoding is successful, NACK is fed back.

(5) As shown in Figure 18, when the UE receives TB3, it does not receive the first transmission of TB3 due to some reasons, so it receives TB3 at the second transmission position of TB3; if the decoding fails, it continues in the third transmission. Location receives TB3. The UE determines the feedback information on the PUCCH based on the last two receptions of TB3 and whether the decoding is correct; if neither is decoded correctly, NACK is fed back.

The embodiment of the present application provides a method for repeatedly sending TBs in a broadcast multicast service. Multiple uplink feedback resources are configured for multiple repeated transmissions of a TB, and the base station adjusts the remaining repeated transmissions of this TB based on the feedback information. In addition, the base station can dynamically adjust the number of repeated transmissions of the next TB based on the feedback of the previous TB. The UE can also decide whether to continue to receive the remaining repeated transmissions of this TB based on the reception/decoding situation of the current TB. This solution also designs the UE receiving behavior for the repeated transmission of semi-persistent scheduling SPS. The design of the embodiment of the present application can adjust parameter information such as the number of repeated transmissions and intervals in real time, and extremely flexibly use feedback information to make changes flexibly, which greatly improves resource utilization efficiency. In addition, it can also ensure the reliability of transmission. Generate redundant transmission.

Figure 19 is a schematic structural diagram of a communication device 1900 according to an embodiment of the present application. The communication device 1900 includes a processor 1910, and the processor 1910 can call and run a computer program from the memory, so that the communication device 1900 implements the method in the embodiment of the present application.

In one implementation, communication device 1900 may also include memory 1920. The processor 1910 can call and run the computer program from the memory 1920, so that the communication device 1900 implements the method in the embodiment of the present application.

The memory 1920 may be a separate device independent of the processor 1910, or may be integrated into the processor 1910.

In one embodiment, the communication device 1900 may also include a transceiver 1930, and the processor 1910 may control the transceiver 1930 to communicate with other devices. Specifically, the communication device 1900 may send information or data to other devices, or receive information sent by other devices. information or data.

Among them, the transceiver 1930 may include a transmitter and a receiver. The transceiver 1930 may further include an antenna, and the number of antennas may be one or more.

In one implementation, the communication device 1900 may be a network device according to the embodiment of the present application, and the communication device 1900 may implement the corresponding processes implemented by the network device in the various methods of the embodiment of the present application. For the sake of brevity, the communication device 1900 will not be mentioned here. Again.

In one implementation, the communication device 1900 can be a terminal device in the embodiment of the present application, and the communication device 1900 can implement the corresponding processes implemented by the terminal device in the various methods of the embodiment of the present application. For the sake of brevity, this is not mentioned here. Again.

Figure 20 is a schematic structural diagram of a chip 2000 according to an embodiment of the present application. The chip 2000 includes a processor 2010, and the processor 2010 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

In one implementation, chip 2000 may also include memory 2020. The processor 2010 can call and run the computer program from the memory 2020 to implement the method executed by the terminal device or the network device in the embodiment of the present application.

The memory 2020 may be a separate device independent of the processor 2010 , or may be integrated into the processor 2010 .

In one implementation, the chip 2000 may also include an input interface 2030. The processor 2010 can control the input interface 2030 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.

In one implementation, the chip 2000 may also include an output interface 2040. The processor 2010 can control the output interface 2040 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.

In one implementation, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiment of the present application. For the sake of simplicity, they will not be described again. .

In one implementation, the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, details will not be repeated here. .

The chips used in network equipment and terminal equipment can be the same chip or different chips.

It should be understood that the chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.

The processor mentioned above can be a general-purpose processor, a digital signal processor (DSP), an off-the-shelf programmable gate array (FPGA), an application specific integrated circuit (ASIC), or Other programmable logic devices, transistor logic devices, discrete hardware components, etc. The above-mentioned general processor may be a microprocessor or any conventional processor.

The memory mentioned above may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM).

It should be understood that the above memory is an exemplary but not restrictive description. For example, the memory in the embodiment of the present application can also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and so on. That is, memories in embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

Figure 21 is a schematic block diagram of a communication system 2100 according to an embodiment of the present application. The communication system 2100 includes a terminal device 2110 and a network device 2120.

The terminal device 2110 is configured to perform subsequent repeated transmission related processing based on the first number of repeated transmissions of downlink data and the transmission status of the downlink data;

The network device 2120 is configured to perform subsequent repeated transmission related processing based on the first number of repeated transmissions of the downlink data and the feedback status of the downlink data.

The terminal device 2110 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 2120 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, no further details will be given here.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted over a wired connection from a website, computer, server, or data center (such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means to transmit to another website, computer, server or data center. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media. The available media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), etc.

It should be understood that in the various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes any limitation.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the present application. are covered by the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A repeated transmission method, including:

The terminal device performs subsequent repeated transmission related processing according to the first number of repeated transmissions of the downlink data and the transmission situation of the downlink data.
The method according to claim 1, wherein performing subsequent repeated transmission related processing includes:

Determine whether to receive the repeatedly transmitted downlink data.
The method according to claim 2, wherein determining whether to receive the repeatedly transmitted downlink data includes:

If the terminal device successfully decodes the downlink data received at least once, it will no longer receive the repeatedly transmitted downlink data;

When the received downlink data fails to be decoded, the terminal device continues to receive the repeatedly transmitted downlink data until the current number of transmissions reaches the first number of repeated transmissions or the received downlink data is successfully decoded;

If no downlink data is received, the terminal device continues to receive the repeatedly transmitted downlink data until the current number of transmissions reaches the first number of repeated transmissions or the received downlink data is decoded successfully.
The method according to any one of claims 1 to 3, wherein the method further comprises:

The terminal device receives first indication information, where the first indication information includes the first number of repeated transmissions and/or the first repetition interval.
The method according to claim 4, wherein the first indication information is in at least one of the following: radio resource control RRC signaling; downlink control information DCI.
The method according to any one of claims 1 to 5, wherein performing subsequent repeated transmission related processing further includes:

After receiving n times of downlink data, the terminal device sends uplink feedback information once; n is greater than or equal to 1, and n is less than or equal to the first number of repeated transmissions N, and N is greater than or equal to 1.
The method according to claim 6, wherein the terminal device sends uplink feedback information once after receiving n times of downlink data, including:

If at least one of the n times of received downlink data is decoded successfully, the terminal device sends the uplink feedback information including confirmation information; and/or

When decoding of m times of downlink data among the n times of received downlink data fails, the terminal device sends the uplink feedback information including non-confirmation information; where m is greater than or equal to 1 and m is less than or equal to n.
The method according to any one of claims 1 to 7, wherein, in the case where at least one of the s downlink data received is successfully decoded, the terminal device does not receive the repeatedly transmitted downlink data. , where s is greater than or equal to 1, and s is less than the first number of repeated transmissions N.
The method according to any one of claims 1 to 8, wherein the method further comprises:

The terminal device receives second indication information, the second indication information includes a second number of repeated transmissions and/or a second repetition interval, wherein the second number of repeated transmissions is based on the feedback situation of the downlink data and the The second number of repeated transmissions is determined by the first number of repeated transmissions, and the second number of repeated transmissions is different from the first number of repeated transmissions.
The method of claim 9, wherein the second indication information is in DCI.
The method according to claim 9 or 10, wherein the feedback situation of the downlink data satisfies at least one of the following:

The uplink feedback information of the M target terminal devices includes confirmation information;

M target terminal devices did not feed back uplink feedback information;

The uplink feedback information of P target terminal devices includes non-confirmation information;

P target terminal devices did not feed back uplink feedback information;

Wherein, M is less than or equal to the total number Y of target terminal devices sent by the network device through point-to-multipoint PTM, and M is greater than or equal to the first threshold; and/or, M is less than or equal to the first number of repeated transmissions N, and The ratio of M to Y is greater than or equal to the second threshold;

Wherein, P is less than or equal to Y, and P is less than or equal to the third threshold; and/or, P is less than or equal to the first number of repeated transmissions N, and the ratio of P to Y is less than or equal to the fourth threshold.
The method according to claim 6, 7 or 11, wherein the uplink feedback information is in a physical uplink control channel (PUCCH).
The method according to any one of claims 1 to 12, wherein the downlink data is in a transport block TB and/or a physical downlink shared channel PDSCH.
A repeated transmission method, including:

The network device performs subsequent repeated transmission related processing based on the first number of repeated transmissions of the downlink data and the feedback situation of the downlink data.
The method according to claim 14, wherein performing subsequent repeated transmission related processing includes:

Determine whether to repeatedly transmit the downlink data.
The method according to claim 15, wherein determining whether to repeatedly transmit the downlink data includes at least one of the following:

The network device does not retransmit the downlink data when at least one uplink feedback information received for the downlink data includes acknowledgment information;

If the network device does not receive uplink feedback information for the downlink data, it does not retransmit the downlink data;

When the network device receives the uplink feedback information for the downlink data that includes non-confirmation information, it repeatedly transmits the downlink data until it receives the uplink feedback information for the downlink data that includes the confirmation information or the current The number of transmissions reaches the first number of repeated transmissions.
The method according to any one of claims 14 to 16, wherein the method further comprises:

The network device sends first indication information, where the first indication information includes the first number of repeated transmissions and/or the first repetition interval.
The method according to claim 17, wherein the first indication information is in at least one of the following: RRC signaling; DCI.
The method according to any one of claims 14 to 18, wherein the method further comprises:

The network device receives uplink feedback information once after sending downlink data n times; wherein n is greater than or equal to 1, and n is less than or equal to the first number of repeated transmissions N, and N is greater than or equal to 1.
The method according to claim 19, wherein the network device receives uplink feedback information once after sending n downlink data, including:

If at least one of the n times of sent downlink data is decoded successfully, the network device receives the uplink feedback information including confirmation information; and/or

When decoding of m times of downlink data among the n times of sent downlink data fails, the network device receives the uplink feedback information including non-acknowledgment information; where m is greater than or equal to 1 and less than or equal to n.
The method according to any one of claims 14 to 20, wherein performing subsequent repeated transmission related processing includes:

The network device adjusts the first number of repeated transmissions according to the feedback of the downlink data.
The method according to claim 21, wherein the network device adjusts the first number of repeated transmissions according to the feedback of the downlink data, including:

The network device adjusts the first number of repeated transmissions to a second number of repeated transmissions according to the feedback of the downlink data, and the second number of repeated transmissions is different from the first number of repeated transmissions.
The method according to claim 22, wherein the feedback situation of the downlink data satisfies at least one of the following:

The uplink feedback information of the M target terminal devices includes confirmation information;

M target terminal devices did not feed back uplink feedback information;

The uplink feedback information of P target terminal devices includes non-confirmation information;

P target terminal devices did not feed back uplink feedback information;

Wherein, M is less than or equal to the total number Y of target terminal devices sent by the network device through point-to-multipoint PTM, and M is greater than or equal to the first threshold; and/or, M is less than or equal to the first number of repeated transmissions N, and The ratio of M to Y is greater than or equal to the second threshold;

Wherein, P is less than or equal to Y, and P is less than or equal to the third threshold; and/or, P is less than or equal to the first number of repeated transmissions N, and the ratio of P to Y is less than or equal to the fourth threshold.
The method according to claim 22 or 23, wherein the method further includes:

The network device sends second indication information, where the second indication information includes the second number of repeated transmissions and/or a second repetition interval.
The method of claim 24, wherein the second indication information is in DCI.
The method according to claim 16, 19, 20 or 23, wherein the uplink feedback information is in PUCCH.
The method according to any one of claims 14 to 26, wherein the downlink data is in TB and/or PDSCH.
A terminal device including:

A processing unit configured to perform subsequent repeated transmission related processing according to the first number of repeated transmissions of downlink data and the transmission situation of the downlink data.
The terminal device according to claim 28, wherein the processing unit is configured to perform subsequent repeated transmission related processing, including: determining whether to receive the repeatedly transmitted downlink data.
The terminal device according to claim 29, wherein the terminal device further includes a first receiving unit, and the processing unit is configured to determine whether to receive the repeatedly transmitted downlink data, including:

If the received downlink data is decoded successfully at least once, instruct the first receiving unit to no longer receive the repeatedly transmitted downlink data;

If the received downlink data fails to be decoded, the first receiving unit is instructed to continue receiving the repeatedly transmitted downlink data until the current number of transmissions reaches the first number of repeated transmissions or the received downlink data is successfully decoded. ;

In the case of no received downlink data, the first receiving unit is instructed to continue receiving the repeatedly transmitted downlink data until the current number of transmissions reaches the first number of repeated transmissions or the received downlink data is successfully decoded.
The terminal device according to any one of claims 28 to 30, wherein the terminal device further includes:

The second receiving unit is configured to receive first indication information, where the first indication information includes the first number of repeated transmissions and/or the first repetition interval.
The terminal device according to claim 31, wherein the first indication information is in at least one of the following: radio resource control RRC signaling; downlink control information DCI.
The terminal device according to any one of claims 28 to 32, wherein the terminal device further includes a sending unit, and the processing unit is configured to instruct the sending unit to send uplink data once after receiving n times of downlink data. Feedback information; wherein n is greater than or equal to 1, and n is less than or equal to the first number of repeated transmissions N, and N is greater than or equal to 1.
The terminal device according to claim 33, wherein the processing unit is configured to send uplink feedback information once after receiving n times of downlink data, including:

If at least one of the n times of received downlink data is successfully decoded, instruct the sending unit to send the uplink feedback information including acknowledgment information; and/or

When decoding of m times of downlink data among the n times of received downlink data fails, instruct the sending unit to send the uplink feedback information including non-confirmation information; where m is greater than or equal to 1 and m is less than or equal to n.
The terminal device according to any one of claims 28 to 34, wherein the processing unit is further configured to instruct the first receiving unit when at least one of the s times of received downlink data is decoded successfully. The downlink data that is repeatedly transmitted is not received, where s is greater than or equal to 1, and s is less than the first number of repeated transmissions N.
The terminal device according to any one of claims 28 to 35, wherein the terminal device further includes:

A third receiving unit, configured to receive second indication information, where the second indication information includes a second number of repeated transmissions and/or a second repetition interval, wherein the second number of repeated transmissions is based on feedback from the downlink data. The situation is determined by the first number of repeated transmissions, and the second number of repeated transmissions is different from the first number of repeated transmissions.
The terminal device according to claim 36, wherein the second indication information is in DCI.
The terminal device according to claim 36 or 37, wherein the feedback situation of the downlink data satisfies at least one of the following:

The uplink feedback information of the M target terminal devices includes confirmation information;

M target terminal devices did not feed back uplink feedback information;

The uplink feedback information of P target terminal devices includes non-confirmation information;

P target terminal devices did not feed back uplink feedback information;

Wherein, M is less than or equal to the total number Y of target terminal devices sent by the network device through point-to-multipoint PTM, and M is greater than or equal to the first threshold; and/or, M is less than or equal to the first number of repeated transmissions N, and The ratio of M to Y is greater than or equal to the second threshold;

Wherein, P is less than or equal to Y, and P is less than or equal to the third threshold; and/or, P is less than or equal to the first number of repeated transmissions N, and the ratio of P to Y is less than or equal to the fourth threshold.
The terminal device according to claim 33, 34 or 38, wherein the uplink feedback information is in a physical uplink control channel PUCCH and/or a physical uplink shared channel PUSCH.
The terminal equipment according to any one of claims 28 to 39, wherein the downlink data is in a transport block TB and/or a physical downlink shared channel PDSCH.
A network device that includes:

A processing unit configured to perform subsequent repeated transmission related processing according to the first number of repeated transmissions of downlink data and the feedback situation of the downlink data.
The network device according to claim 41, wherein the processing unit is configured to perform subsequent repeated transmission related processing, including: determining whether to repeatedly transmit the downlink data.
The network device according to claim 42, wherein the network device further includes a first sending unit, and the processing unit is used to determine whether to repeatedly transmit the downlink data, including at least one of the following:

If the received at least one uplink feedback information for the downlink data includes acknowledgment information, instruct the first sending unit not to repeatedly transmit the downlink data;

If no uplink feedback information for the downlink data is received, instruct the first sending unit not to re-transmit the downlink data;

When receiving the uplink feedback information for the downlink data including non-confirmation information, instruct the first sending unit to repeatedly transmit the downlink data until the uplink feedback information for the downlink data includes the acknowledgment. The information or the current number of transmissions reaches the first number of repeated transmissions.
The network device according to any one of claims 41 to 43, wherein the network device further includes:

The second sending unit is configured to send first indication information, where the first indication information includes the first number of repeated transmissions and/or the first repetition interval.
The network device according to claim 44, wherein the first indication information is in at least one of the following: RRC signaling; DCI.
The network device according to any one of claims 41 to 45, wherein the network device further includes:

The receiving unit is configured to receive uplink feedback information once after sending downlink data n times; wherein n is greater than or equal to 1, and n is less than or equal to the first number of repeated transmissions N, and N is greater than or equal to 1.
The network device according to claim 46, wherein the receiving unit is used for:

If at least one of the n times of sent downlink data is decoded successfully, receive the uplink feedback information including confirmation information; and/or

When decoding of m times of downlink data among the n times of sent downlink data fails, the uplink feedback information including non-acknowledgment information is received; where m is greater than or equal to 1 and less than or equal to n.
The network device according to any one of claims 41 to 47, wherein the processing unit is further configured to adjust the first number of repeated transmissions according to feedback of the downlink data.
The network device according to claim 48, wherein the processing unit is configured to adjust the first number of repeated transmissions according to the feedback situation of the downlink data, including: adjusting the first number of repeated transmissions according to the feedback situation of the downlink data. A number of repeated transmissions is adjusted to a second number of repeated transmissions, and the second number of repeated transmissions is different from the first number of repeated transmissions.
The network device according to claim 49, wherein the feedback situation of the downlink data satisfies at least one of the following:

The uplink feedback information of the M target terminal devices includes confirmation information;

M target terminal devices did not feed back uplink feedback information;

The uplink feedback information of P target terminal devices includes non-confirmation information;

P target terminal devices did not feed back uplink feedback information;

Wherein, M is less than or equal to the total number Y of target terminal devices sent by the network device through point-to-multipoint PTM, and M is greater than or equal to the first threshold; and/or, M is less than or equal to the first number of repeated transmissions N, and The ratio of M to Y is greater than or equal to the second threshold;

Wherein, P is less than or equal to Y, and P is less than or equal to the third threshold; and/or, P is less than or equal to the first number of repeated transmissions N, and the ratio of P to Y is less than or equal to the fourth threshold.
The network device according to claim 49 or 50, wherein the network device further includes:

The third sending unit is configured to send second indication information, where the second indication information includes the second number of repeated transmissions and/or the second repetition interval.
The network device according to claim 51, wherein the second indication information is in DCI.
The network device according to claim 43, 46, 47 or 50, wherein the uplink feedback information is in PUCCH and/or PUSCH.
The network device according to any one of claims 41 to 53, wherein the downlink data is in TB and/or PDSCH.
A terminal device includes: a processor, a memory and a transceiver, the processor is used to control the transceiver to communicate with other devices, the memory is used to store computer programs, the processor is used to call and run the A computer program stored in the memory to cause the terminal device to execute the method according to any one of claims 1 to 13.
A network device, including: a processor, a memory and a transceiver, the processor is used to control the transceiver to communicate with other devices, the memory is used to store computer programs, the processor is used to call and run the A computer program stored in the memory to cause the network device to perform the method according to any one of claims 14 to 27.
A chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the method according to any one of claims 1 to 13 or 14 to 27.
A computer-readable storage medium used to store a computer program, which when the computer program is run by a device, causes the device to perform the method according to any one of claims 1 to 13 or 14 to 27.
A computer program product comprising computer program instructions that cause a computer to perform the method according to any one of claims 1 to 13 or 14 to 27.
A computer program that causes a computer to perform the method according to any one of claims 1 to 13 or 14 to 27.
A communications system including:

Terminal equipment, used to perform the method according to any one of claims 1 to 13;

Network equipment, used to perform the method according to any one of claims 14 to 27.