CN118891842A

CN118891842A - Repeated transmission method, terminal equipment and network equipment

Info

Publication number: CN118891842A
Application number: CN202280093965.2A
Authority: CN
Inventors: 马腾; 张世昌; 赵振山
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2022-08-09
Filing date: 2022-08-09
Publication date: 2024-11-01
Also published as: WO2024031395A1

Abstract

The application relates to a repeated transmission method, terminal equipment and network equipment. The repeated transmission method may include: and the terminal equipment executes subsequent repeated transmission related processing according to the first repeated transmission times of the downlink data and the transmission condition of the downlink data. According to the embodiment of the application, the subsequent repeated transmission related processing can be reasonably executed according to the first repeated transmission times of the downlink data and the transmission condition of the downlink data, so that transmission resources are saved.

Description

Repeated transmission method, terminal equipment and network equipment

Technical Field

The present application relates to the field of communications, and more particularly, to a retransmission method, a terminal device, and a network device.

Background

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

Disclosure of Invention

The embodiment of the application provides a repeated transmission method, terminal equipment and network equipment.

The embodiment of the application provides a repeated transmission method, which comprises the following steps: and the terminal equipment executes subsequent repeated transmission related processing according to the first repeated transmission times of the downlink data and the transmission condition of the downlink data.

The embodiment of the application provides a repeated transmission method, which comprises the following steps: and the network equipment executes subsequent repeated transmission related processing according to the first repeated transmission times of the downlink data and the feedback condition of the downlink data.

The embodiment of the application provides a terminal device, which comprises: and the processing unit is used for executing subsequent repeated transmission related processing according to the first repeated transmission times of the downlink data and the transmission condition of the downlink data.

An embodiment of the present application provides a network device, including: and the processing unit is used for executing subsequent repeated transmission related processing according to the first repeated transmission times of the downlink data and the feedback condition of the downlink data.

The embodiment of the application provides terminal equipment, which comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory so as to enable the terminal equipment to execute the repeated transmission method.

The embodiment of the application provides a network device which comprises a processor and a memory. The memory is used for storing a computer program, and the processor is used for calling and running the computer program stored in the memory so as to enable the network equipment to execute the repeated transmission method.

The embodiment of the application provides a chip for realizing the repeated transmission method.

Specifically, the chip includes: and a processor for calling and running the computer program from the memory, so that the device mounted with the chip executes the repetitive transmission method described above.

An embodiment of the present application provides a computer-readable storage medium storing a computer program which, when executed by a device, causes the device to perform the above-described repetitive transmission method.

An embodiment of the present application provides a computer program product including computer program instructions for causing a computer to execute the above-described retransmission method.

The embodiment of the application provides a computer program which, when run on a computer, causes the computer to execute the repeated transmission method.

According to the embodiment of the application, the subsequent repeated transmission related processing can be reasonably executed according to the first repeated transmission times of the downlink data and the transmission condition of the downlink data, so that transmission resources are saved.

Drawings

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

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

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

Fig. 4a to 4c are schematic diagrams of an NR MBS scheduling scheme according to an embodiment of the present application.

Fig. 5 is a schematic flow chart of a retransmission method according to an embodiment of the present application.

Fig. 6 is a schematic flow chart of a retransmission method according to another embodiment of the present application.

Fig. 7 is a schematic flow chart of a retransmission method according to another embodiment of the present application.

Fig. 8 is a schematic flow chart of a retransmission method according to an embodiment of the present application.

Fig. 9 is a schematic flow chart of a retransmission method according to another embodiment of the present application.

Fig. 10 is a schematic flow chart of a retransmission method according to another embodiment of the present application.

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

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

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

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

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

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

Fig. 17 is a schematic diagram of transmitting TB1 to a group of UEs via PTM according to an embodiment of the application.

Fig. 18 is a schematic diagram of TB retransmission in SPS according to an embodiment of the present application.

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

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

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

Detailed Description

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

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio Service (GENERAL PACKET Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, long term evolution advanced (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, non-terrestrial communication network (Non-TERRESTRIAL NETWORKS, NTN) system, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (WIRELESS FIDELITY, WIFI), fifth Generation communication (5 th-Generation, 5G) system, or other communication system, etc.

Generally, the number of connections supported by the conventional Communication system is limited and easy to implement, however, with the development of Communication technology, the mobile Communication system will support not only conventional Communication but also, for example, device-to-Device (D2D) Communication, machine-to-machine (Machine to Machine, M2M) Communication, machine type Communication (MACHINE TYPE Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) Communication, or internet of vehicles (Vehicle to everything, V2X) Communication, etc., and the embodiments of the present application can also be applied to these Communication systems.

In one implementation, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a stand-alone (Standalone, SA) networking scenario.

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

Embodiments of the present application are described in connection with a network device and a terminal device, where the terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, a User Equipment, or the like.

The terminal device may be a Station (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA) device, a handheld device with wireless communication functionality, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a next generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In the embodiment of the application, the terminal equipment can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).

In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned (SELF DRIVING), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (SMART GRID), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (SMART CITY), or a wireless terminal device in smart home (smart home), or the like.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In the embodiment of the present application, the network device may be a device for communicating with a mobile device, where the network device may be an Access Point (AP) in a WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or an Access Point, or a vehicle device, a wearable device, and a network device (gNB) in an NR network, or a network device in a PLMN network of future evolution, or a network device in an NTN network, etc.

By way of example, and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth Orbit (medium earth Orbit, MEO) satellite, a geosynchronous Orbit (geostationary earth Orbit, GEO) satellite, a high elliptical Orbit (HIGH ELLIPTICAL Orbit, HEO) satellite, or the like. Alternatively, the network device may be a base station disposed on land, in a water area, or the like.

In the embodiment of the present application, a network device may provide services for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a small cell (SMALL CELL), where the small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

Fig. 1 schematically illustrates a communication system 100. The communication system comprises one network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include a plurality of network devices 110, and each network device 110 may include other numbers of terminal devices 120 within a coverage area of the network device 110, which is not limited by the embodiment of the present application.

In one embodiment, the communication system 100 may further include other network entities such as Mobility management entity (Mobility MANAGEMENT ENTITY, MME), access and Mobility management function (ACCESS AND Mobility Management Function, AMF), which is not limited by the embodiment of the present application.

The network device may further include an access network device and a core network device. I.e. the wireless communication system further comprises a plurality of core networks for communicating with the access network devices. The access network device may be a long-term evolution (LTE) system, a next-generation (NR) system, or an evolved base station (evolutional node B, which may be simply an eNB or e-NodeB) macro base station, a micro base station (also referred to as a "small base station"), a pico base station, an Access Point (AP), a transmission point (transmission point, TP), a new generation base station (new generation Node B, gNodeB), or the like in an licensed assisted access long-term evolution (LAA-LTE) system.

It should be understood that a device having a communication function in a network/system according to an embodiment of the present application may be referred to as a communication device. Taking the communication system shown in fig. 1 as an example, the communication device may include a network device and a terminal device with a communication function, where the network device and the terminal device may be specific devices in the embodiments of the present application, and are not described herein again; the communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

It should be understood that the "indication" mentioned in the embodiments of the present application may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, etc.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description describes related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as alternatives, which all belong to the protection scope of the embodiments of the present application.

Currently, with the pursuit of speed, delay, high speed mobility, energy efficiency and diversity and complexity of future life services, the third generation partnership project (3 ^rd Generation Partnership Project,3 GPP) international standards organization starts to develop 5G for this purpose. The main application scenario of 5G is: mobile ultra-wideband (enhanced Mobile Broadband, eMBB), low latency high reliability Communications (Ultra Reliability and Low Latency Communication, URLLC), large scale machine class Communications (MASSIVE MACHINE TYPE Communications, mMTC).

EMBB still aims at obtaining multimedia content, services and data by users, and the demand of which is growing very rapidly. On the other hand, eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., where the capability and demand are also quite different, so detailed analysis must be performed in conjunction with a specific deployment scenario. Typical applications of URLLC include: industrial automation, electric power automation, remote medical operation (surgery), traffic safety guarantee and the like. Typical features of mMTC include: high connection density, small data volume, delay insensitive traffic, low cost and long service life of the module, etc.

For the purposes of reducing air interface signaling and quickly restoring wireless connections and quickly restoring data traffic in a 5G network environment, a new radio resource control (Radio Resource Control, RRC) state, i.e., rrc_inactive state, is defined. This state is different from the rrc_idle and rrc_active states.

Rrc_idle: mobility is cell selection reselection based on User Equipment (UE), paging is initiated by a Core Network (CN), and paging areas are configured by the CN. The base station side does not have a UE Access Stratum (AS) context. There is no RRC connection.

Rrc_connected: there is an RRC connection and the base station and UE have a UE AS context. The network side knows that the location of the UE is cell specific. Mobility is network-side controlled mobility. Unicast data may be transmitted between the UE and the base station.

Rrc_inactive: mobility is a UE-based cell selection reselection, there is a connection between CN-New Radio technology (NR), the UE AS context is present on a certain base station, paging is triggered by the Radio access network (Radio Access Network, RAN), the RAN-based paging area is managed by the RAN, the network side knows that the UE location is based on the RAN paging area level.

In 5G, the maximum channel bandwidth may be 400MHZ (bandwidth carrier), which is large compared to the maximum 20M bandwidth of long term evolution (Long Term Evolution, LTE). If the UE remains operating on a broadband carrier (wideband carrier), the power consumption of the UE is significant. It is suggested that the RF bandwidth of the UE may be adjusted according to the actual throughput of the UE. The motivation for introducing a BandWidth Part (BWP) for this is to optimize the power consumption of the UE. For example, the UE may be configured with a smaller bandwidth (fig. 2 a) if the UE rate is low, and a larger bandwidth (fig. 2 b) if the UE rate requirement is high. If the UE supports high rates or operates in carrier aggregation (Carrier Aggregation, CA) mode, multiple BWP may be configured (fig. 2 c). Another purpose of BWP is to trigger coexistence of multiple basic parameter sets (numerology) in one cell.

The UE in the current idle state or inactive state resides on an initial BWP. This BWP is visible to either the idle state or the inactive state UE. Within this BWP a master information block (Master Information Block, MIB), remaining minimum system information (REMAINING MINIMUM SYSTEM INFORMATION, RMSI), open system interconnection (Open Systems Interconnection, OSI), paging (paging) etc. information may be obtained.

Common frequency domain resources (common frequency resource, CFR) of NR multimedia broadcast multicast service (Multimedia Broadcast Multicast Services, MBMS)/multicast broadcast service (multi broadcast service, MBS).

CFR is a design concept introduced during the NR MBS discussion in order to distinguish from BWP. CFR is a continuous set of frequency domain resources located on a carrier for receiving MBS services. From the perspective of a single UE, one CFR is a continuous set of frequency domain resources for receiving downlink MBS service data. From a system perspective, the CFR is used to transmit MBS service data, a group of UEs in a CONNECTED state (rrc_connected) receive multicast/multicast of MBS in the CFR, and UEs in a non-CONNECTED state (rrc_idle/rrc_inactive) receive broadcast of MBS on the CFR.

MBMS and single cell point-to-multipoint (SINGLE CELL Point To Multiploint, SC-PTM) system in LTE

Multimedia Broadcast Multicast Service (MBMS) is a service introduced in Release 6 (R6) of 3 GPP. The multimedia broadcast multicast service is a technology for transmitting data from one data source to a plurality of user equipments through a shared network resource, and can effectively utilize the network resource while providing a multimedia service, thereby realizing broadcasting and multicasting of the multimedia service at a higher rate (256 kbps).

Due to the low MBMS spectrum efficiency in 3gpp R6, it is not sufficient to effectively carry and support the operation of the mobile tv type service. In the long term evolution standard (Long Term Evolution, LTE) project of radio access networks, 3GPP has therefore explicitly proposed to enhance the support capability for downlink high-speed multimedia broadcast multicast service services and to determine the design requirements for the physical layer and air interface.

EMBMS is R9 introduced to LTE networks. eMBMS proposes the concept of a single frequency network (Single Frequency Network, SFN), i.e. to transmit data simultaneously in all cells using a unified frequency, but to guarantee synchronization between cells. The method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the frequency spectrum efficiency can be correspondingly and greatly improved. And implements broadcast and multicast of services based on an internet protocol (Internet Protocol, IP) multicast protocol.

In LTE/long term evolution high order (Long Term Evolution Advanced, LTE-a), MBMS has only a broadcast bearer mode and no multicast bearer mode.

The reception of the MBMS service is applicable to the UE in the rrc_connected or rrc_idle state.

As shown in FIG. 3, SC-PTM was introduced into R13. The SC-PTM is based on the MBMS network architecture, and a Multi-cell/multicast coordination entity (Multi-cell/multicast Coordination Entity, MCE) decides whether to use the SC-PTM transmission scheme or the multimedia broadcast multicast service single frequency network (Multimedia Broadcast multicast SERVICE SINGLE Frequency Network, MBSFN) transmission scheme.

A new logical channel single-cell multicast control channel (SINGLE CELL Multicast Control Channel, SC-MCCH) (logical channel identity (logical CHANNEL IDENTIFY, LCID) =11001) and single-cell multicast transport channel (SINGLE CELL Multicast Transport Channel, SC-MTCH) (lcid=11001) are introduced, mapped onto DL-SCH transport channel, physical downlink shared channel (Physical Downlink SHARED CHANNEL, PDSCH) physical channel. The SC-MCCH and SC-MTCH do not support hybrid automatic repeat reQuest (Hybrid Automatic Repeat-reQuest, HARQ) operations.

A new system information block (System Information Block, SIB) type is introduced, SIB20 transmits configuration information of SC-MCCH, and one cell has only one SC-MCCH. The configuration information includes: modification period, repetition period, and radio frame and subframe configuration information of the SC-MCCH.

Radio frame scheduled by SC-MCCH: SFN mod MCCH-repetition period (Repetition Period) =mcch-Offset (Offset).

The subframes for SC-MCCH scheduling are indicated by SC-MCCH-subframes.

The SC-MCCH transmits only one message SC-PTMConfiguration (configuration) for configuring configuration information of the SC-PTM. A new radio network temporary identity (Radio Network Temporary Identifier, RNTI) is introduced, a single cell RNTI (SINGLE CELL RNTI, SC-RNTI) (which may be a fixed value FFFC) to identify scheduling information of the SC-MCCH on the physical downlink control channel (Physical Downlink Control Channel, PDCCH).

A new RNTI is introduced, and a single cell Notification RNTI (SINGLE CELL Notification RNTI, SC-N-RNTI) (a value FFFB may be fixed) is used to identify the PDCCH for the change Notification of the SC-MCCH. The change notification is indicated by one bit of 8 bits (bits) in the downlink control information (Downlink Control Information, DCI) 1C. The modification period boundary is defined as SFN mod m=0, where m is the modification period configured in SIB20, e.g., sc-mcch-ModificationPeriod; mod represents a modulo operation.

In NR, the radio link control (Radio Link Control, RLC) acknowledged mode (Acknowledgement Mode, AM) mode is with Automatic Repeat-reQuest (ARQ) feedback mechanism. The receiving end sends RLC status report to feed back whether the receiving status of the RLC packet is Acknowledged (ACK) or unacknowledged (NACK). The transmitting end may repeatedly transmit RLC packets of a Secondary Node (SN) number of the feedback NACK.

Downstream BWP configuration

The downstream BWP is configured by BWP-Downlink (bandwidth part downstream) parameters. As shown in the following first-stage autonomous system number (Autonomous System Number, ASN) 1 code, the Id of the current BWP is included in the parameter in BWP-Id (bandwidth part identification) field, and BWP-Common (bandwidth part Common) is used to configure the Common parameters of the downstream BWP. As shown in the following second-segment asn.1 coding, GENERICPARAMETERS (general parameter) in BWP-DownlinkCommon (bandwidth part downlink common) is used to configure the frequency domain starting point of the downlink BWP and the number of included physical resource blocks (Physical Resource Block, PRB). For one terminal-specific unicast BWP, the BWP-scheduled (bandwidth part specific) parameter in BWP-Downlink will configure the Downlink reception parameter on the Downlink BWP. As shown in the following third asn.1 coding, it includes at least PDCCH-Config (PDCCH configuration), PDSCH-Config (PDSCH configuration), and SPS-Config (SPS configuration). As shown in the second asn.1 code, PDCCH-Config is used to indicate the PDCCH transmission scheme on the downlink BWP, PDSCH-Config is used to indicate the PDSCH transmission scheme on the downlink BWP, and SPS-Config is used to indicate the SPS configuration on the downlink BWP.

First segment asn.1 encoding:

Second segment asn.1 coding:

Third segment asn.1 coding:

...,

Propagation mode of NR MBS

For MBS service, the base station schedules transmission in the following manners:

(1) Broadcast (Broadcast)

The MBS service is sent in a broadcast mode, and is suitable for the terminal in an RRC_IDLE/RRC_INACTIVE state and the terminal in an RRC_CONNECTED state. That is, through the MBS service transmitted by broadcasting, the terminal is in any link state as long as it can receive the same within the coverage area.

(2) Multicast/Multicast (Multicast)

And the base station sends the same MBS service to a group of terminals by a one-to-many PTM sending mode.

(3) Unicast (Unicast)

And the base station sends the same MBS service to each terminal by a one-to-one PTP sending mode.

NR MBS group scheduling mode

In NR MBS, one-to-many multicast transmission needs to be supported, in which a base station needs to schedule a common PDSCH by transmitting a common downlink control channel, where the common PDCCH and the common PDSCH are transmitted in a common frequency domain range (CFR, common Frequency Resource). Currently, there are the following alternative CFR configurations:

First kind: the CFR is configured as an MBS-specific BWP, which is associated with a terminal-specific unicast BWP, and the subcarrier spacing and cyclic prefix configured on the CFR are the same as those on the terminal-specific unicast BWP.

Second kind: the CFR is configured as a plurality of PRBs that are contiguous in the terminal-specific unicast BWP range.

The first approach has the advantage that the CFR can follow the relevant BWP signaling configuration, which is advantageous for reducing the standard workload. But since CFR is defined as BWP, if a terminal is required to receive unicast in dedicated unicast BWP and receive multicast in CFR at the same time, it means that the terminal needs to receive downlink transmission on two BWP at the same time. However, the terminal has only the capability to receive downstream on one BWP at a given moment. In addition, even if the terminals receive unicast and multicast at different times, BWP switching delay is introduced because the terminals are located at different BWPs. The second method can avoid the problem of BWP handover, but in this method, since the CFR is a plurality of consecutive PRBs, the existing BWP-based signaling configuration cannot be used, and the resource range of the CFR, the configuration mode of uplink and downlink transmission parameters, and the like need to be redesigned, which has a large impact on the standard.

In addition, since the common PDCCH scheduling the common PDSCH needs to be simultaneously transmitted to a plurality of receiving terminals, in order to ensure that the number of bits of the common DCI carried in the common PDCCH determined by the plurality of terminals is the same, the terminals cannot determine the number of bits of the common DCI according to the configuration of the respective dedicated unicast BWP. In addition, since the PRB number of CFR may be different from the initial BWP or CORESET (ControlResourceSet ) #0 (COntrol REsource SET 0) currently configured by the terminal, the terminal cannot determine the bit number of the common DCI through the initial BWP or CORESET #0. Therefore, it is inevitable that the number of bits of the common DCI may be different from the number of bits of DCI received by the terminal in the relevant USS or CSS. Then, in order to reduce the implementation complexity of the terminal, the terminal can only receive DCI with 4 different bit numbers at most in one Cell, wherein the bit number of DCI scrambled by Cell-specific RNTI (Cell RNTI, C-RNTI) is not more than 3.

NR MBS group scheduling mode

As shown in fig. 4a, 4b and 4c, there may be three ways of scheduling transmission MBS services, in which PTM1 and Point-to-Point (PTP) are already supported. The group shared PDCCH/PDSCH refers to PDCCH/PDSCH transmitted by a base station on a set of time-frequency resources, which can be received by multiple UEs of the same group. The PTM scheduling manner mentioned in the present scheme may refer to PTM1.

PTM 1: for multiple UEs of the same group in a connected state, a group shared PDSCH is scheduled using a group shared PDCCH, wherein a cyclic redundancy check (Cyclic Redundancy Check, CRC) of the group shared PDCCH is scrambled using a group shared RNTI, and the group shared PDSCH is scrambled using the same group shared RNTI.

PTM 2: for multiple UEs of the same group in a connected state, a group shared PDSCH is scheduled for each UE using a UE-specific PDCCH, wherein the CRC of the UE-specific PDCCH is scrambled using a UE-specific RNTI (i.e., C-RNTI), and the group shared PDSCH is scrambled using a group shared RNTI.

PTP: for connected UEs, a UE-specific PDCCH is used to schedule a UE-specific PDSCH for each UE, wherein the CRC of the UE-specific PDCCH is scrambled with a UE-specific RNTI (i.e., C-RNTI) and the UE-specific PDSCH is scrambled with a UE-specific RNTI (i.e., C-RNTI).

Transmission mode of NR MBS group dispatch

The retransmission mechanism of MBS business based on HARQ-ACK feedback in the connection state can support the following modes:

mode one: primary pass PTM1+ retransmission PTM1

Mode two: primary PTM1+retransmission PTP

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

HPID (HARQ process ID: 0-15) sharing the system between multicast/multicast and unicast, how HPID is specifically allocated is determined by the base station implementation. If HPID #1 is first allocated to the transmission use of a Transport Block (TB) 1 of the MBS service, when both the initial transmission and the potential retransmission of TB1 are finished, the base station will continue to allocate HPID #1 to the transmission use of TB2, where TB2 is used for unicast transmission of UE 3. When the initial transmission and the potential retransmission of the TB2 are finished, the base station will continue to allocate HPID #1 to the transmission of the TB3 for use, and the TB3 is used for the transmission of the MBS service.

HPID and new data identification (New Data Indicator, NDI) method for determining initial transmission and retransmission

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

The ndi=1 corresponding to HPID #1 received immediately before can be compared, and the currently received TB can be determined as the initial transmission of a new TB. The UE empties the data information of the last TB stored in the buffer, and then stores the initial transmission of the newly received TB and the potentially received retransmission in the buffer for soft combining.

The currently received TB may be determined to be retransmitted at this time by comparing ndi=0 corresponding to HPID #1 received previously.

In the related art, the network side determines the TB retransmission times of an MBS service through configuration. Once the configuration determines that, for example, one TB is repeated 4 times, the number of repeated transmissions of all TBs corresponding to this service is 4 times for a long period of time before the signaling update. In addition, each TB is configured only once at the end of the repeated transmission to feed back the uplink feedback resource.

In the related art, the repeated transmission of the TB is as described above. Once the configuration determines the number of repetitions of the TB, it cannot be changed for a short period of time. When the channel condition is very good, when all UEs receive one TB, the other TBs can be correctly decoded once or twice, and the remaining TB repeated transmission is obviously redundant, and occupies a large amount of downlink transmission resources, so that waste is caused. In addition, for each TB feedback, feedback is performed for one TB at the end of the repeated transmission. If the number of repeated transmissions of one TB is 8, the UE needs to feed back for the TB after the 8 transmissions are completed. If the UE decodes successfully the first time, the waiting time is very long, resulting in a long delay. In the related art, multiple repeated transmission of one TB is required to be received by the UE, and the UE is required to decode continuously when receiving multiple times, which is not only electricity-consuming but also unfavorable for effective utilization of resources.

Fig. 5 is a schematic flow chart diagram of a retransmission method 500 according to an embodiment of the present application. The method may alternatively be applied to the system shown in fig. 1, but is not limited thereto. The method includes at least some of the following.

S510, the terminal equipment executes subsequent repeated transmission related processing according to the first repeated transmission times of the downlink data and the transmission condition of the downlink data.

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

In the embodiment of the present application, the terminal device may execute subsequent repeated transmission related processing of the TB according to the first repeated transmission number of the TB and the transmission condition of the TB. The terminal device may perform subsequent repeated transmission related processing of the PDSCH according to the first number of repeated transmissions of the PDSCH and the transmission condition of the PDSCH.

In the embodiment of the present application, the subsequent repeated transmission related processing performed by the terminal device, for example, the UE, may include various types, and mainly may include some operations related to repeated transmission of the TB and/or the PDSCH performed by the UE after receiving the current TB and/or PDSCH. For example, stop receiving the retransmission, continue receiving the retransmission, perform uplink feedback, and the like.

In one embodiment, a subsequent repeated transmission related process is performed, comprising: it is determined whether to receive the repeated transmission of the downlink data.

In the embodiment of the present application, the UE may determine whether to continue to receive the downlink data repeatedly transmitted by the network device according to one or more of whether to receive the downlink data, the current number of times of the received downlink data, the first number of repeated transmissions N (i.e., the total number of times), and the decoding condition after the received downlink data.

In one embodiment, determining whether to receive the repeated transmission of the downstream data includes:

Mode 1: and the terminal equipment does not receive the downlink data which are repeatedly transmitted under the condition that the received at least one time of the downlink data is successfully decoded.

For example, if the current number of transmissions of TB1 is 2 nd, the first number of repeated transmissions N is 6 th, and the UE successfully decodes the current TB1, the UE may not receive the repeated transmissions of TB1 from 3rd to 6 th of the network device. Of course, the network side may not repeatedly transmit the TB1 from the 3rd time to the 6 th time after knowing that the UE successfully decodes the TB1 from the 2 nd time.

Mode 2: and the terminal equipment continuously receives the downlink data which is repeatedly transmitted under the condition that the received downlink data is failed to be decoded, until the current transmission times reach the first repeated transmission times or the received downlink data is successfully decoded.

For another example, if the current transmission number of TB2 is 2 nd and the first retransmission number N is 6, but the UE fails to decode this TB2, the UE continues to receive the 3 rd retransmission of TB 2. If the received 3 rd time TB2 decoding is successful, the network device may not receive the 4 th to 6 th time TB2 retransmission. If the received 3 rd to 6 th TB2 fails decoding, the repeated transmission of the received TB2 is stopped.

Mode 3: and the terminal equipment continuously receives the downlink data which are repeatedly transmitted under the condition of not receiving the downlink data until the current transmission times reach the first repeated transmission times or the received downlink data are successfully decoded.

For another example, if the current number of transmissions of TB3 is 3 rd, the first number of retransmission N is 6, but the UE does not receive the 3 rd number of retransmission of TB3, the UE continues to receive the 4 th number of retransmission of TB 3. If the received 4 th TB3 is successfully decoded, the network device may not receive the 5 th to 6 th TB3 repeated transmissions. If the received 4 th to 6 th TB3 fails decoding, the repeated transmission of the received TB2 is stopped.

In one embodiment, as shown in fig. 6, the method 600 includes: s610, the terminal equipment receives first indication information, wherein the first indication information comprises the first repeated transmission times and/or first repeated intervals.

In the embodiment of the present application, the steps of the method 600 and the method 500 described above may be implemented separately or combined.

In the embodiment of the application, the UE may receive the first indication information from the network device, for example, the base station, where the indication information may be configured dynamically or semi-statically. The first retransmission times may be the total times of the network device for retransmitting the downlink data, or the total times of the terminal device for receiving the retransmission of the downlink data. The total number of repeated transmission of the downlink data by the network device and the total number of repeated transmission of the downlink data received by the terminal device can be the same or different. The first repetition interval may represent an interval of repeated transmission of the downlink data, and the first repetition interval may be a slot or a symbol.

In one embodiment, the first indication information is in at least one of: radio Resource Control (RRC) signaling; downlink Control Information (DCI).

In the embodiment of the application, the RRC signaling is a high-level configuration information. The network device may first send the first indication information to the terminal device through the higher layer configuration information. The DCI is a dynamic indication mode, and the network device can send the PDCCH to the terminal device, wherein the DCI is carried in the PDCCH, and the first indication information is carried in the DCI. The terminal device may perform subsequent repeated transmission related processing by using the first indication information including the first repeated transmission number and/or the first repeated interval.

In the embodiment of the present application, the feedback mode of the terminal device may be an acknowledgement/non-acknowledgement (ACK/NACK) feedback mode or a non-acknowledgement only (NACK-only) feedback mode. The feedback mode may also be referred to as a feedback mode. In the ACK/NACK feedback mode, the terminal device may feed back acknowledgement information to the network device, or may feed back non-acknowledgement information to the network device. In this case, the uplink feedback information transmitted by the terminal device may be Acknowledgement (ACK) information or non-acknowledgement (NACK) information. In the NACK-only feedback mode, if the state is an acknowledgement state, the terminal device does not feed back information, and only in the non-acknowledgement state, the terminal device feeds back the non-acknowledgement information to the network device.

In one embodiment, performing subsequent repeated transmission related processing further includes:

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

In one embodiment, 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 once every 1 TB or PDSCH is received. For another example, the terminal device may send 1 PUCCH carrying uplink feedback information to the network device after receiving 2 TBs or PDSCH each time.

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

Under the condition that at least one downlink data in the n times of received downlink data is successfully decoded, the terminal equipment sends the uplink feedback information comprising the confirmation information; and/or

Under the condition that m times of downlink data in the n times of received downlink data fails to be decoded, the terminal equipment sends the uplink feedback information comprising non-acknowledgement information; wherein m is greater than or equal to 1 and m is less than or equal to n.

In the embodiment of the application, the terminal equipment feeds back once every time when receiving n times of downlink data. m may represent a threshold of decoding failure times, and the decoding failure times are greater than the threshold, and the terminal device may feed back non-acknowledgement information.

For example, in the ACK/NACK feedback mode, the terminal device feeds back 1 uplink feedback information every time it receives 3 TBs or PDSCH. If the 3 times of received TBs or PDSCH are each successfully decoded, or 1 or 2 times of decoding are successful, the terminal device may transmit PUCCH including ACK information to the network device. If the 3 times received TB or PDSCH each fails decoding or the number of decoding failures is greater than a certain threshold, for example, 2 times, the terminal device transmits PUCCH including NACK information.

For another example, in the NACK-only feedback mode, the terminal device feeds back 1 uplink feedback information every time it receives 3 TBs or PDSCH. If the 3 times of received TBs or PDSCH are decoded successfully or 1 or 2 times of decoding are successful, the terminal device does not transmit PUCCH. If the 3 times received TB or PDSCH each fails decoding or the number of decoding failures is greater than a certain threshold, for example, 2 times, the terminal device transmits PUCCH including NACK information.

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

In the embodiment of the present application, s may represent the number of times the terminal device receives the downlink data. For example, the first retransmission number N is equal to 4, the terminal device receives the 1 st TB, and if the TB is successfully decoded, the 2 nd to 4 th TB retransmission is not received. For another example, the first retransmission number N is equal to 5, and if the terminal device does not receive the 1 st PDSCH, the terminal device continues to receive the 2 nd PDSCH retransmission. If the 2 nd PDSCH decoding is successful, the terminal device no longer receives the 3 rd, 4 th and 5 th PDSCH repeated transmissions. For another example, the first retransmission number N is equal to 5, and the terminal device receives the 1 st, 2 nd and 3 rd PDSCH, and the terminal device no longer receives the 4 th and 5 th PDSCH retransmission if the 2 nd PDSCH is successfully decoded.

In one embodiment, as shown in fig. 7, the method 700 includes: s710, the terminal equipment receives second indication information, wherein the second indication information comprises second repeated transmission times and/or second repeated intervals, the second repeated transmission times are determined according to the feedback condition of the downlink data and the first repeated transmission times, and the second repeated transmission times are different from the first repeated transmission times.

In an embodiment of the present application, the steps of the method 700 and the methods 500 and/or 600 described above may be performed separately or in combination. 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 device may determine whether to receive the downlink data that is repeatedly transmitted according to the first number of repeated transmissions of the downlink data and the transmission condition of the downlink data, and determine whether to receive the downlink data that is repeatedly transmitted according to the second number of repeated transmissions of the downlink data and the transmission condition of the downlink data for the next TB and/or PDSCH. For another example, for the current TB and/or PDSCH, the terminal device receives all the downlink data according to the first number of repeated transmissions, and for the next TB and/or PDSCH, determines whether to receive the repeated downlink data according to the second number of repeated transmissions of the downlink data and the transmission condition of the downlink data.

In the embodiment of the present application, if the current transmission frequency of the downlink data received and successfully decoded by the terminal device is smaller than the first retransmission frequency N, the network device may appropriately reduce the first retransmission frequency N to obtain the second retransmission frequency N'. If the terminal device N times cannot receive and successfully decode the downlink data, the network device may appropriately increase the first retransmission number N to obtain a second retransmission number N'.

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

In the embodiment of the present application, the second repeated transmission times may be configured in a dynamic indication manner. For example, the terminal device receives a PDCCH from the network device, where 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 the embodiment of the application, in related service scenarios such as multicast, multicast and the like, the network device may send the same downlink data to a plurality of terminal devices at a time. There may be some terminals that are able to receive and successfully decode the downstream data and some other terminals that are not receiving or not successfully decoding the downstream data. In addition, the feedback modes of the terminal equipment further comprise the ACK/NACK feedback mode and the NACK-only feedback mode. Thus, there may be a plurality of specific feedback situations of the terminal device. Based on different feedback conditions of the terminal device, the network device may need to adjust the manner in which the number of retransmissions is repeated.

In one embodiment, the feedback condition of the downlink data satisfies at least one of the following, and the first repetition number is adjusted to the second repetition number by the network device:

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

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

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

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

wherein M is less than or equal to a 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 a 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 a second threshold;

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

In the embodiment of the present application, for a specific example of the network device adjusting the number of repeated transmissions, reference may be made to the following description about the embodiment of the network device.

Fig. 8 is a schematic flow chart diagram of a retransmission method 800 according to an embodiment of the present application. The method may alternatively be applied to the system shown in fig. 1, but is not limited thereto. The method includes at least some of the following.

And S810, the network equipment executes subsequent repeated transmission related processing according to the first repeated transmission times of the downlink data and the feedback condition of the downlink data.

In one embodiment, a subsequent repeated transmission related process is performed, comprising: it is determined whether the downlink data is repeatedly transmitted.

In one embodiment, determining whether to repeat the transmission of the downstream data includes at least one of:

the network equipment does not repeatedly transmit the downlink data under the condition that the received at least one uplink feedback information aiming at the downlink data comprises the confirmation information;

the network equipment does not repeatedly transmit the downlink data under the condition that the network equipment does not receive the uplink feedback information aiming at the downlink data;

And the network equipment repeatedly transmits the downlink data under the condition that the uplink feedback information aiming at the downlink data comprises non-acknowledgement information until the uplink feedback information aiming at the downlink data comprises acknowledgement information or the current transmission times reach the first repeated transmission times.

In one embodiment, as shown in fig. 9, the method 900 includes: s910, the network device sends first indication information, wherein the first indication information comprises the first repeated transmission times and/or a first repeated interval.

In the embodiment of the present application, the steps of the method 900 and the method 800 described above may be implemented separately or may be combined.

In one embodiment, the first indication information is in at least one of: RRC signaling; DCI (DCI).

In one embodiment, the method further comprises: after the network equipment sends the downlink data for n times, the network equipment receives uplink feedback information once; wherein N is greater than or equal to 1, and N is less than or equal to the first number of repeated transmissions N, where N is greater than or equal to 1.

In one embodiment, after sending n times of downlink data, the network device receives one time of uplink feedback information, including:

under the condition that at least one downlink data in the n times of transmitted downlink data is successfully decoded, the network equipment receives the uplink feedback information comprising the confirmation information; and/or

Under the condition that m times of downlink data in the n times of transmitted downlink data are failed to be decoded, the network equipment receives the uplink feedback information comprising non-acknowledgement information; wherein m is greater than or equal to 1 and less than or equal to n.

In one embodiment, a subsequent repeated transmission related process is performed, comprising:

the network device adjusts the first repeated transmission times according to the feedback condition of the downlink data.

In one embodiment, the network device adjusts the first retransmission number according to the feedback condition of the downlink data, including:

The network device adjusts the first retransmission times to second retransmission times according to the feedback condition of the downlink data, wherein the second retransmission times are different from the first retransmission times.

In one embodiment, the feedback condition of the downlink data satisfies at least one of the following:

the uplink feedback information of the M target terminal devices comprises confirmation information;

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

The uplink feedback information of the P target terminal devices comprises non-acknowledgement information;

p target terminal devices do 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 the point-to-multipoint PTM, and M is greater than or equal to a 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 a second threshold;

For example, the network device sends TB1 to Y terminal devices, where the first number of repeated transmissions of TB1 is N, and in the ACK/NACK feedback mode, the network device adjusts the first number of repeated transmissions to the second number of repeated transmissions when receiving that the uplink feedback information of M target terminal devices includes ACK information, M is greater than a first threshold of the set number of successful transmission devices, and M is less than N. In this case, the second number of retransmissions may be smaller than the first number of retransmissions. Specifically, for example, the first retransmission number 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 fed back ACK information terminal devices 30 is greater than the second threshold, the network device adjusts the first number of repeated transmissions to be 4. Assuming that the second threshold is 70%, the ratio of the number m=30 to y=40 of the fed back terminal devices of the ACK information is 75% greater than the second threshold, and the network device adjusts the first number of repeated transmissions to the second number of repeated transmissions to be 4.

For another example, the network device sends TB1 to Y terminal devices, where the first number of repeated transmissions of TB1 is N, and in the NACK-only feedback mode, the network device adjusts the first number of repeated transmissions to the second number of repeated transmissions when no uplink feedback information of M target terminal devices is received by the network device. Specifically, for example, the first retransmission number is 8, the network device sends TB1 to 40 terminal devices, and ACK information fed back by 30 terminal devices is not received. Assuming that the first threshold is 25 and the number of terminal devices 30 without feedback information is greater than the second threshold, the network device adjusts the first number of repeated transmissions to a second number of repeated transmissions of 4. Assuming that the second threshold is 70%, the ratio of the number of terminal devices m=30 and y=40 without feedback information is 75% greater than the second threshold, and the network device adjusts the first retransmission number to the second retransmission number of 4.

For another example, the network device sends TB1 to Y terminal devices, where the first number of repeated transmissions of TB1 is N, and in the ACK/NACK feedback mode or the NACK-only feedback mode, the network device adjusts the first number of repeated transmissions to the second number of repeated transmissions when receiving uplink feedback information including NACK information of P target terminal devices. Specifically, for example, the first retransmission number is 8, the network device sends TB1 to 40 terminal devices, receives ACK information fed back by 30 terminal devices, and adjusts the first retransmission number to the second retransmission number to be 4 if the first threshold is 25.

For another example, the network device sends TB1 to Y terminal devices, where the first number of repeated transmissions of TB1 is N, and in the NACK-only feedback mode, the network device adjusts the first number of repeated transmissions to the second number of repeated transmissions when no uplink feedback information of P target terminal devices is received. Specifically, for example, the first retransmission number is 8, the network device sends TB1 to 40 terminal devices, and does not receive ACK information fed back by 30 terminal devices, and if the first threshold is 25, the network device adjusts the first retransmission number to be 4.

The adjusted second retransmission times may be used for retransmission of TB2 or TB3 after the current TB 1.

In one embodiment, as shown in fig. 10, the method 1000 further comprises: 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 the embodiment of the present application, the steps of the method 1000 and the methods 800 and/or 900 described above may be implemented separately or may be combined.

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

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

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

Specific examples of the method 800, 900, 1000 performed by the network device in this embodiment may be referred to the relevant descriptions of the network device, such as the base station, in the methods 500, 600, 700, and are not repeated herein for brevity.

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

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

In one embodiment, the processing unit is configured to perform subsequent repeated transmission related processing, including: it is determined whether to receive the repeated transmission of the downlink data.

In one embodiment, as shown in fig. 12, the terminal device 1200 may include the processing unit 1110 described above, where the terminal device 1200 further includes a first receiving unit 1210, and the processing unit 1110 is configured to determine whether to receive the downlink data that is repeatedly transmitted, and includes:

In the case that the received at least one time of decoding of the downlink data is successful, the first receiving unit 1210 is instructed to no longer receive the downlink data transmitted repeatedly;

Under the condition that the received downlink data decoding fails, the first receiving unit 1210 is instructed to continue receiving the downlink data that is repeatedly transmitted until the current transmission number reaches the first retransmission number or the received downlink data decoding is successful;

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

In one embodiment, as shown in fig. 12, the terminal device 1200 further includes: the second receiving unit 1220 is configured to receive first indication information, where the first indication information includes the first retransmission number and/or the first repetition interval.

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

radio Resource Control (RRC) signaling;

downlink Control Information (DCI).

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

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

Under the condition that at least one downlink data in the n times of received downlink data is successfully decoded, the sending unit 1240 is instructed to send the uplink feedback information including acknowledgement information; and/or

In case that m times of downlink data among the n times of received downlink data fails to be decoded, instructing the transmitting unit 1240 to transmit the uplink feedback information including non-acknowledgement information; wherein 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 further configured to instruct the first receiving unit 1210 not to receive the downlink data that is repeatedly transmitted if at least one downlink data decoding in the received s downlink data is successful, where s is greater than or equal to 1 and s is less than the first retransmission number N.

In one embodiment, as shown in fig. 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 retransmission number and/or a second retransmission interval, and the second retransmission number is determined according to the feedback condition of the downlink data and the first retransmission number, and the second retransmission number is different from the first retransmission number.

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

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

p target terminal devices do not feed back uplink feedback information;

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

The terminal device 1100, 1200 according to the embodiment of the present application can implement the corresponding functions of the terminal device in the foregoing embodiments of the methods 500, 600, 700. The flow, function, implementation and beneficial effects corresponding to each module (sub-module, unit or component, etc.) in the terminal device 1100, 1200 can be referred to the corresponding description in the above method embodiments, and will not be repeated here. It should be noted that, the functions described in the respective modules (sub-modules, units, or components, etc.) in the terminal devices 1100, 1200 of the application embodiments may be implemented by different modules (sub-modules, units, or components, etc.), or may be implemented by the same module (sub-module, unit, component, etc.).

Fig. 13 is a schematic block diagram of a network device 1300 in accordance with an embodiment of the present application. The network device 1300 may include:

And a processing unit 1310, configured to execute subsequent repeated transmission related processing according to the first repeated transmission times of the downlink data and the feedback situation of the downlink data.

In one embodiment, the processing unit 1310 is configured to perform subsequent repeated transmission related processing, including: it is determined whether the downlink data is repeatedly transmitted.

In one embodiment, as shown in fig. 14, the network device 1400 further includes a first sending unit 1410, and the processing unit 1310 is further configured to determine whether to repeatedly transmit the downlink data, including at least one of the following:

Under the condition that the received at least one uplink feedback information for the downlink data includes acknowledgement information, the first sending unit 1410 is instructed not to repeatedly transmit the downlink data;

in the case that the uplink feedback information for the downlink data is not received, the first transmitting unit 1410 is instructed not to repeatedly transmit the downlink data;

And under the condition that the uplink feedback information for the downlink data includes non-acknowledgement information, the first sending unit 1410 is instructed to repeatedly transmit the downlink data until the uplink feedback information for the downlink data is received and the acknowledgement information is included or the current transmission frequency reaches the first repeated transmission frequency.

In one embodiment, as shown in fig. 14, the network device 1400 further includes: the second sending unit 1420 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.

In one embodiment, as shown in fig. 14, the network device 1400 further includes: a receiving unit 1430 for receiving primary uplink feedback information after n times of downlink data are transmitted; wherein N is greater than or equal to 1, and N is less than or equal to the first number of repeated transmissions N, where N is greater than or equal to 1.

In one embodiment, the receiving unit 1430 is configured to:

Receiving the uplink feedback information including acknowledgement information under the condition that at least one downlink data in the n times of transmitted downlink data is successfully decoded; and/or

Receiving the uplink feedback information including non-acknowledgement information under the condition that m times of downlink data in the n times of transmitted downlink data fails to be decoded; wherein m is greater than or equal to 1 and less than or equal to n.

In one embodiment, the processing unit 1310 is further configured to perform subsequent repeated transmission related processing, including: and adjusting the first repeated transmission times according to the feedback condition of the downlink data.

In an embodiment, the processing unit 1310 is further configured to adjust the first retransmission number according to the feedback condition of the downlink data, including: and according to the feedback condition of the downlink data, adjusting the first repeated transmission times to second repeated transmission times, wherein the second repeated transmission times are different from the first repeated transmission times.

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

p target terminal devices do not feed back uplink feedback information;

In one embodiment, as shown in fig. 14, the network device 1400 further includes: the third transmitting unit 1440 is configured to transmit second indication information, where the second indication information includes the second number of repeated transmissions and/or the second repetition interval.

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

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

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

The network devices 1300, 1400 of the embodiments of the present application can implement the corresponding functions of the network devices in the foregoing embodiments of the methods 800, 900, 1000. The flow, function, implementation manner and beneficial effect corresponding to each module (sub-module, unit or assembly, etc.) in the network device 1300, 1400 can be referred to the corresponding description in the above method embodiments, and will not be repeated here. It should be noted that, the functions described in the respective modules (sub-modules, units, or components, etc.) in the network devices 1300, 1400 of the application embodiments may be implemented by different modules (sub-modules, units, or components, etc.), or may be implemented by the same module (sub-module, unit, component, etc.).

The repeated transmission method provided by the embodiment of the application can be a method for repeatedly sending the TB in the broadcast multicast service. The method mainly comprises the following steps:

(1) The repetition number and transmission interval of one TB are configured according to semi-static state.

(2) And according to the repetition number and the transmission interval of the PDCCH indicated one TB, and according to the HARQ-ACK feedback condition of the previous TB, adjusting parameters such as the repetition number and the transmission interval of the next TB, and dynamically indicating the repeated transmission information of the current scheduled TB through the PDCCH.

(3) For repeated transmission of a TB, if there are multiple uplink feedbacks, the base station decides whether the remaining repeated transmission of the TB is to be sent continuously or not according to the current feedback information.

(4) In Semi-persistent scheduling (Semi-PERSISTENT SCHEDULING, SPS, or referred to as Semi-persistent scheduling), the number of retransmissions, the interval, and the time-frequency resource location of one TB per period are determined by 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 successful; if the UE does not receive a certain transmission of a TB, the UE continues to receive the subsequent repeated transmission of the TB.

Example 1: TB, semi-static configuration feedback times

(1) According to the indication information of the configuration of the high-level configuration parameters, one PDSCH/TB is repeatedly transmitted for N times, N PDSCH transmission intervals are G, wherein N is a positive integer more than or equal to 1, and G is an integer more than or equal to 0.

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

(A) ACK/NACK feedback mode: in the receiving of the receiving UE for less than or equal to N times, if at least one time of decoding the PDSCH is successful, feeding back the ACK to the base station through an uplink resource Physical Uplink Control Channel (PUCCH) or a Physical Uplink Shared Channel (PUSCH); and if the receiving UE does not successfully decode the PDSCH once in N times or less of receiving, feeding back NACK to the base station through the uplink resource PUCCH or the PUSCH. Or (b)

(B) NACK-only feedback mode: in the receiving process of the receiving UE for less than or equal to N times, if at least one time of decoding the PDSCH is successful, no information is fed back to the base station through an uplink resource PUCCH or PUSCH; and if the receiving UE does not successfully decode the PDSCH once in N times or less of receiving, feeding back NACK to the base station through the uplink resource PUCCH or the PUSCH.

(3) If N repeated transmissions of PDSCH correspond to multiple uplink feedback resources, the base station may decide whether to continue to transmit the remaining PDSCH repetitions according to feedback conditions of a group of UEs (e.g., Y UEs).

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

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

Example 1-1

(1) As shown in fig. 15, one TB is repeatedly transmitted 4 times, and at this time, one uplink feedback resource PUCCH is configured, and the UE successfully decodes the PDSCH at least once in 4 (or less than 4) times of reception, and feeds back ACK to the base station through the uplink resource. In 4 (or less than 4) receptions of the UE, the UE feeds back NACK to the base station through uplink resources without successful PDSCH decoding.

(2) As shown in fig. 16, one TB is repeatedly transmitted 4 times, and two uplink feedback resources PUCCH are configured at this time, and there is one PUCCH resource after the first two repeated transmissions and one PUCCH resource after the second two repeated transmissions.

Angle of one UE: if the UE has at least one decoding success among the first 2 received PDSCHs and feeds back an ACK on the first PUCCH, the UE may not receive the last two PDSCHs.

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

(a) ACK/NACK feedback: for the transmission of the PDSCH in the first two times, if the feedback of all receiving UE is ACK, the base station does not transmit the PDSCH in the last two times; for the transmission of the PDSCH in the first two times, if K (K is more than or equal to 1) UE feeds back NACK, the base station continues to transmit the PDSCH in the last two times.

(B) NACK-only feedback: for the transmission of the PDSCH in the first two times, all the UE does not feed back any information to the base station (namely, the decoding is successful), and the base station does not transmit the PDSCH in the last two times; for the transmission of the PDSCH in the first two times, if K (K is more than or equal to 1) UE feeds back NACK, the base station continues to transmit the PDSCH in the last two times.

One special case state of example 1: each PDSCH is followed by one PUCCH resource for the UE to transmit feedback information.

Example 2: TB (terminal block) dynamically indicates feedback times

(1) According to the indication information of the PDCCH/DCI, indicating that the repeated transmission times of one PDSCH/TB are N times, and N PDSCH transmission intervals are G, wherein N is a positive integer more than or equal to 1, and G is an integer more than or equal to 0.

(2) According to the feedback situation after the previous TB is transmitted, if all UEs or more than X% of UEs have fed back ACK (ACK/NACK feedback mode) or no feedback information (NACK-only feedback mode), the repetition number may be changed from N to N 'at the time of transmitting the next TB, and updated N' information may be indicated in the PDCCH. Wherein, X% may be a ratio of the number of UEs fed back with ACK (ACK/NACK feedback mode) or without feedback information (NACK-only feedback mode) to the total number of UEs (in PTM scenario).

Example 2-1

(1) As shown in fig. 17, when the base station transmits TB1 to a group of Y (Y positive integer) UEs through PTM, the PDCCH indicates the repetition number of 4 times.

(2) The group of UEs feeds back on the PUCCH resource if M UEs out of the Y UEs feed back ACK (ACK/NACK feedback mode), or if M UEs out of the Y UEs do not feed back (NACK-only feedback mode). When the base station transmits the TB2, the repeated transmission times of the TB2 are dynamically adjusted, and the repeated times are indicated through the PDCCH.

For example, if the base station transmits TB1 to 100 UEs via PTM and repeats 4 times and 90 UEs feed back ACK on PUCCH, the base station repeats transmission only 2 times when transmitting TB 2.

(3) The description can also be replaced with: and determining the adjustment repetition times according to the number of the UE feeding back NACK. If M UE in Y UE feeds back NACK (ACK/NACK and NACK-only feedback mode are all possible), the base station dynamically adjusts the repeated transmission times of TB2 and indicates the repeated times through PDCCH when the TB2 is transmitted.

For example, if the base station transmits TB1 to 100 UEs 4 times and 10 UEs feedback NACK, the base station may transmit TB2 only 2 times repeatedly when transmitting TB2.

Example 3: TB retransmission in SPS

(1) According to the high-level configuration information, in semi-persistent scheduling, the number of repeated transmission times of one PDSCH/TB in each period is N, the repeated interval is G, and N and G are positive integers. And after the repetition is performed for N times, PUCCH resources are correspondingly reserved for the UE to report feedback information.

(2) When the UE receives a TB in one period, it may decide whether to continue to receive the next repetition of the TB according to each reception.

(3) As shown in fig. 18, when receiving TB1, the UE receives the first transmission of TB1 first, and if decoding is successful, the UE does not receive the remaining two transmissions of TB 1. The UE feeds back ACK (ACK/NACK feedback mode) or this without feedback (NACK-only feedback mode) on PUCCH resources.

(4) As shown in fig. 18, when receiving TB2, if the first reception decoding of TB2 fails, the UE continues to receive the second transmission of TB 2; if decoding still fails, the third transmission continues to be received until all duplicate transmissions of TB2 in the current period are received and decoded. The UE decides information fed back in the PUCCH according to the three times of decoding of the TB 2; and if none of the decoding is successful, feeding back NACK.

(5) As in fig. 18, when receiving TB3, the ue does not receive the first transmission of TB3 for some reason, and then receives TB3 at the second transmission location of TB3; if decoding fails, the reception of TB3 in the third transmission position is continued. The UE decides feedback information on the PUCCH according to the fact that the TB3 is received for the second time and whether decoding is correct or not; if none of the decoding is correct, a NACK is fed back.

The embodiment of the application provides a method for repeatedly sending a TB in a broadcast multicast service. And configuring a plurality of uplink feedback resources for repeated transmission of one TB, and adjusting the residual repeated transmission of the TB by the base station according to the feedback information. In addition, the base station can dynamically adjust the repeated transmission times of the next TB according to the feedback condition of the previous TB. The UE may also decide whether to continue to receive the remaining duplicate transmissions of the current TB according to the reception/decoding situation of this TB. This scheme also designs the behavior of UE reception for repeated transmissions of semi-persistent scheduling SPS. The design of the embodiment of the application can adjust the parameter information such as the number of repeated transmission, interval and the like in real time, flexibly changes by using the feedback information, greatly improves the utilization efficiency of resources, and can ensure the reliability of transmission without generating redundant transmission.

Fig. 19 is a schematic structural diagram of a communication device 1900 according to an embodiment of the present application. The communications device 1900 includes a processor 1910, and the processor 1910 may call and execute a computer program from memory to cause the communications device 1900 to implement the methods of embodiments of the present application.

In one implementation, the communications device 1900 may also include a memory 1920. Wherein the processor 1910 may invoke and execute a computer program from the memory 1920 to cause the communication device 1900 to implement the method in the embodiments of the present application.

Wherein the memory 1920 may be a separate device from the processor 1910 or may be integrated within the processor 1910.

In one embodiment, the communication device 1900 may further include a transceiver 1930, and the processor 1910 may control the transceiver 1930 to communicate with other devices, in particular, to transmit information or data to other devices, or to receive information or data transmitted by other devices.

Among other things, transceiver 1930 may include a transmitter and a receiver. The transceiver 1930 may further include antennas, the number of which may be one or more.

In an implementation manner, the communication device 1900 may be a network device of an embodiment of the present application, and the communication device 1900 may implement corresponding flows implemented by the network device in each method of the embodiment of the present application, which are not described herein for brevity.

In an implementation manner, the communication device 1900 may be a terminal device of an embodiment of the present application, and the communication device 1900 may implement corresponding flows implemented by the terminal device in each method of the embodiment of the present application, which are not described herein for brevity.

Fig. 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, from which the processor 2010 may call and run computer programs to implement the methods of embodiments of the present application.

In one embodiment, chip 2000 may also include memory 2020. Wherein the processor 2010 may invoke and run a computer program from the memory 2020 to implement the method performed by the terminal device or the network device in embodiments of the present application.

Wherein the memory 2020 may be a separate device from the processor 2010 or may be integrated in the processor 2010.

In one embodiment, the chip 2000 may also include an input interface 2030. Processor 2010 may control input interface 2030 to communicate with other devices or chips, and in particular, may obtain information or data sent by the other devices or chips.

In one embodiment, the chip 2000 may also include an output interface 2040. Processor 2010 may control the output interface 2040 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.

In an implementation manner, the chip may be applied to the network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

In an implementation manner, the chip may be applied to a terminal device in an embodiment of the present application, and the chip may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

The chips applied to the network device and the terminal device may be the same chip or different chips.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The processors mentioned above may be general purpose processors, digital Signal Processors (DSP), off-the-shelf programmable gate arrays (field programmable GATE ARRAY, FPGA), application SPECIFIC INTEGRATED Circuits (ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor.

The memory mentioned above may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an erasable programmable ROM (erasable PROM), an electrically erasable programmable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM).

It should be appreciated that the above memory is exemplary and not limiting, and for example, the memory in the embodiments of the present application may be static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (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), direct Rambus RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Fig. 21 is a schematic block diagram of a communication system 2100 in accordance with an embodiment of the present application. The communication system 2100 includes a terminal device 2110 and a network device 2120.

Terminal device 2110, configured to execute subsequent repeated transmission related processing according to the first repeated transmission number of the downlink data and the transmission situation of the downlink data;

the network device 2120 is configured to perform subsequent repeated transmission related processing according to the first repeated transmission number of the downlink data and the feedback condition of the downlink data.

Wherein the terminal device 2110 may be used to implement the corresponding functionality implemented by the terminal device in the method described above, and the network device 2120 may be used to implement the corresponding functionality implemented by the network device in the method described above. For brevity, the description is omitted here.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, 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 loaded and executed on a computer, produces a flow or function in accordance with embodiments of the application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (Solid STATE DISK, SSD)), etc.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily appreciate variations or alternatives within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

A method of repeating transmissions, comprising:

And the terminal equipment executes subsequent repeated transmission related processing according to the first repeated transmission times of the downlink data and the transmission condition of the downlink data.
The method of claim 1, wherein performing subsequent repeated transmission related processing comprises:

and determining whether to receive the repeated transmission of the downlink data.
The method of claim 2, wherein determining whether to receive the downlink data for repeated transmissions comprises:

The terminal equipment does not receive the downlink data which are repeatedly transmitted under the condition that the received at least one time of downlink data are successfully decoded;

The terminal equipment continues to receive the downlink data which are repeatedly transmitted under the condition that the received downlink data are failed to be decoded, until the current transmission times reach the first repeated transmission times or the received downlink data are successfully decoded;

And under the condition that the downlink data is not received, the terminal equipment continuously receives the downlink data which is repeatedly transmitted until the current transmission times reach the first repeated transmission times or the received downlink data is successfully decoded.
A method according to any one of claims 1 to 3, wherein the method further comprises:

The terminal equipment receives first indication information, wherein the first indication information comprises the first repeated transmission times and/or a first repeated interval.
The method of claim 4, wherein the first indication information is in at least one of: 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 comprises:

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

Under the condition that at least one downlink data in the received n times of downlink data is successfully decoded, the terminal equipment sends the uplink feedback information comprising the confirmation information; and/or

Under the condition that m times of downlink data in the received n times of downlink data are failed to be decoded, the terminal equipment sends the uplink feedback information comprising non-acknowledgement information; wherein 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 the terminal device does not receive the downlink data of the repeated transmission in case that at least one of the received s times of downlink data is successfully decoded, wherein s is greater than or equal to 1 and s is less than the first number of repeated transmissions N.
The method of any one of claims 1 to 8, wherein the method further comprises:

The terminal equipment receives second indication information, wherein the second indication information comprises second repeated transmission times and/or second repeated intervals, the second repeated transmission times are determined according to the feedback condition of the downlink data and the first repeated transmission times, and the second repeated transmission times are different from the first repeated transmission times.
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 comprises confirmation information;

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

The uplink feedback information of the P target terminal devices comprises non-acknowledgement information;

p target terminal devices do 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 the point-to-multipoint PTM, and M is greater than or equal to a 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 a second threshold;

wherein P is less than or equal to Y, and P is less than or equal to a third threshold; and/or, P is less than or equal to the first retransmission number N, and the ratio of P to Y is less than or equal to a fourth threshold.
The method of claim 6, 7 or 11, wherein the uplink feedback information is in a physical uplink control channel, PUCCH.
The method according to any of claims 1 to 12, wherein the downlink data is in transport blocks, TBs, and/or physical downlink shared channels, PDSCH.
A method of repeating transmissions, comprising:

and the network equipment executes subsequent repeated transmission related processing according to the first repeated transmission times of the downlink data and the feedback condition of the downlink data.
The method of claim 14, wherein performing subsequent repeated transmission related processing comprises:

And determining whether to repeatedly transmit the downlink data.
The method of claim 15, wherein determining whether to repeat transmitting the downstream data comprises at least one of:

the network equipment does not repeatedly transmit the downlink data under the condition that the received at least one uplink feedback information aiming at the downlink data comprises the confirmation information;

The network equipment does not repeatedly transmit the downlink data under the condition that the network equipment does not receive uplink feedback information aiming at the downlink data;

And the network equipment repeatedly transmits the downlink data under the condition that the uplink feedback information aiming at the downlink data comprises non-acknowledgement information until the uplink feedback information aiming at the downlink data comprises acknowledgement information or the current transmission times reach the first repeated transmission times.
The method of any of claims 14 to 16, wherein the method further comprises:

The network equipment sends first indication information, wherein the first indication information comprises the first repeated transmission times and/or a first repeated interval.
The method of claim 17, wherein the first indication information is in at least one of: RRC signaling; DCI (DCI).
The method of any of claims 14 to 18, wherein the method further comprises:

the network equipment receives primary uplink feedback information after sending n times of downlink data; wherein N is greater than or equal to 1, and N is less than or equal to the first repeated transmission times N, where N is greater than or equal to 1.
The method of claim 19, wherein the network device receives one uplink feedback information after transmitting n downlink data, comprising:

Under the condition that at least one downlink data in the n times of downlink data is successfully decoded, the network equipment receives the uplink feedback information comprising acknowledgement information; and/or

Under the condition that m times of downlink data in the n times of downlink data are transmitted and the decoding of the downlink data fails, the network equipment receives the uplink feedback information comprising non-acknowledgement information; wherein 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 comprises:

and the network equipment adjusts the first repeated transmission times according to the feedback condition of the downlink data.
The method of claim 21, wherein the network device adjusting the first retransmission number according to the feedback condition of the downlink data comprises:

And the network equipment adjusts the first repeated transmission times to second repeated transmission times according to the feedback condition of the downlink data, wherein the second repeated transmission times are different from the first repeated transmission times.
The method of claim 22, wherein the feedback condition of the downstream data satisfies at least one of:

the uplink feedback information of the M target terminal devices comprises confirmation information;

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

The uplink feedback information of the P target terminal devices comprises non-acknowledgement information;

p target terminal devices do 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 the point-to-multipoint PTM, and M is greater than or equal to a 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 a second threshold;

wherein P is less than or equal to Y, and P is less than or equal to a third threshold; and/or, P is less than or equal to the first retransmission number N, and the ratio of P to Y is less than or equal to a fourth threshold.
The method of claim 22 or 23, wherein the method further comprises:

The network device sends second indication information, wherein the second indication information comprises the second repeated transmission times and/or second repeated intervals.
The method of claim 24, wherein the second indication information is in DCI.
The method of claim 16, 19, 20 or 23, wherein the uplink feedback information is in PUCCH.
The method of any of claims 14 to 26, wherein the downlink data is in a TB and/or a PDSCH.
A terminal device, comprising:

And the processing unit is used for executing subsequent repeated transmission related processing according to the first repeated transmission times of the downlink data and the transmission condition of the downlink data.
The terminal device of claim 28, wherein the processing unit is configured to perform subsequent repeated transmission related processing, and comprises: and determining whether to receive the repeated transmission of the downlink data.
The terminal device of claim 29, wherein the terminal device further comprises a first receiving unit, the processing unit configured to determine whether to receive the downlink data of the repeated transmission, including:

Under the condition that the received at least one time of downlink data decoding is successful, the first receiving unit is instructed to not receive the downlink data which are repeatedly transmitted;

Under the condition that the received downlink data decoding fails, the first receiving unit is instructed to continuously receive the downlink data which is repeatedly transmitted until the current transmission times reach the first repeated transmission times or the received downlink data decoding is successful;

And under the condition of not receiving the downlink data, indicating the first receiving unit to continuously receive the downlink data which is repeatedly transmitted until the current transmission times reach the first repeated transmission times or the received downlink data is successfully decoded.
The terminal device of any of claims 28 to 30, wherein the terminal device further comprises:

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

under the condition that at least one downlink data in the received n times of downlink data is successfully decoded, indicating the sending unit to send the uplink feedback information comprising the confirmation information; and/or

Under the condition that m times of downlink data in the received n times of downlink data are failed to be decoded, the sending unit is instructed to send the uplink feedback information comprising non-acknowledgement information; wherein m is greater than or equal to 1 and m is less than or equal to n.
The terminal device of any of claims 28 to 34, wherein the processing unit is further configured to instruct a first receiving unit not to receive the downlink data that is repeatedly transmitted if at least one of the received s times of downlink data is successfully decoded, where s is greater than or equal to 1 and s is less than the first number of repeated transmissions N.
The terminal device of any of claims 28-35, wherein the terminal device further comprises:

and a third receiving unit, configured to receive second indication information, where the second indication information includes a second retransmission number and/or a second retransmission interval, where the second retransmission number is determined according to a feedback condition of the downlink data and the first retransmission number, and the second retransmission number is different from the first retransmission number.
The terminal device of 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 comprises confirmation information;

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

The uplink feedback information of the P target terminal devices comprises non-acknowledgement information;

p target terminal devices do 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 the point-to-multipoint PTM, and M is greater than or equal to a 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 a second threshold;

wherein P is less than or equal to Y, and P is less than or equal to a third threshold; and/or, P is less than or equal to the first retransmission number N, and the ratio of P to Y is less than or equal to a fourth threshold.
The terminal device of 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 device of any 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, comprising:

and the processing unit is used for executing subsequent repeated transmission related processing according to the first repeated transmission times of the downlink data and the feedback condition of the downlink data.
The network device of claim 41, wherein the processing unit is configured to perform subsequent repeated transmission related processing, comprising: and determining whether to repeatedly transmit the downlink data.
The network device of claim 42, wherein the network device further comprises a first transmitting unit, the processing unit configured to determine whether to retransmit the downstream data, comprising at least one of:

Under the condition that the received at least one uplink feedback information aiming at the downlink data comprises acknowledgement information, the first sending unit is instructed not to repeatedly transmit the downlink data;

Under the condition that uplink feedback information aiming at the downlink data is not received, the first sending unit is instructed not to repeatedly transmit the downlink data;

And under the condition that the uplink feedback information aiming at the downlink data comprises non-acknowledgement information, the first sending unit is instructed to repeatedly transmit the downlink data until the acknowledgement information or the current transmission times of the uplink feedback information aiming at the downlink data are received to reach the first repeated transmission times.
The network device of any one of claims 41 to 43, wherein the network device further comprises:

the second sending unit is configured to send first indication information, where the first indication information includes the first repeat transmission times and/or the first repeat interval.
The network device of claim 44, wherein the first indication information is in at least one of: RRC signaling; DCI (DCI).
The network device of any one of claims 41 to 45, wherein the network device further comprises:

the receiving unit is used for receiving primary uplink feedback information after n times of downlink data are sent; wherein N is greater than or equal to 1, and N is less than or equal to the first repeated transmission times N, where N is greater than or equal to 1.
The network device of claim 46, wherein the receiving unit is configured to:

Receiving the uplink feedback information including acknowledgement information under the condition that at least one downlink data in the n times of transmitted downlink data is successfully decoded; and/or

Receiving the uplink feedback information including non-acknowledgement information under the condition that m times of downlink data in the n times of transmitted downlink data fails to be decoded; wherein m is greater than or equal to 1 and less than or equal to n.
The network device of any one of claims 41 to 47, wherein the processing unit is further configured to adjust the first number of retransmissions according to a feedback condition of the downlink data.
The network device of claim 48, wherein the processing unit configured to adjust the first retransmission number according to a feedback condition of the downlink data comprises: and according to the feedback condition of the downlink data, the first repeated transmission times are adjusted to second repeated transmission times, and the second repeated transmission times are different from the first repeated transmission times.
The network device of claim 49, wherein the feedback condition of the downstream data satisfies at least one of:

the uplink feedback information of the M target terminal devices comprises confirmation information;

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

The uplink feedback information of the P target terminal devices comprises non-acknowledgement information;

p target terminal devices do 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 the point-to-multipoint PTM, and M is greater than or equal to a 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 a second threshold;

wherein P is less than or equal to Y, and P is less than or equal to a third threshold; and/or, P is less than or equal to the first retransmission number N, and the ratio of P to Y is less than or equal to a fourth threshold.
The network device of claim 49 or 50, wherein the network device further comprises:

And a third sending unit, configured to send second indication information, where the second indication information includes the second number of repeated transmissions and/or a second repetition interval.
The network device of claim 51, wherein the second indication information is in DCI.
The network device of claim 43, 46, 47 or 50, wherein the uplink feedback information is in PUCCH and/or PUSCH.
A network device as claimed in any one of claims 41 to 53, wherein the downlink data is in the TB and/or PDSCH.
A terminal device, comprising: a processor for controlling the transceiver to communicate with other devices, a memory for storing a computer program, and a transceiver for calling and running the computer program stored in the memory to cause the terminal device to perform the method according to any of claims 1 to 13.
A network device, comprising: a processor for controlling the transceiver to communicate with other devices, a memory for storing a computer program, and a transceiver for invoking and running the computer program stored in the memory to cause the network device to perform the method according to any of claims 14 to 27.
A chip, comprising: a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the method of any one of claims 1 to 13 or 14 to 27.
A computer readable storage medium storing a computer program which, when executed by a device, causes the device to perform the method of any one of claims 1 to 13 or 14 to 27.
A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 13 or 14 to 27.
A computer program which causes a computer to perform the method of any one of claims 1 to 13 or 14 to 27.
A communication system, comprising:

terminal device for performing the method of any of claims 1 to 13;

Network device for performing the method of any of claims 14 to 27.