WO2024031307A1

WO2024031307A1 - Hybrid automatic repeat request (harq) feedback method and apparatus, and device and medium

Info

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

Abstract

The present application relates to the field of wireless communications. Disclosed are a hybrid automatic repeat request (HARQ) feedback method and apparatus, and a device and a medium. The method is applied to a terminal, and comprises: according to a negative-acknowledgement-only (NACK-only) feedback mode, reporting, to an access network device, reception feedback of a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) of a multicast and broadcast service (MBS). The method can perform HARQ feedback of an SPS PDSCH of an MBS service by using a NACK-only feedback mode.

Description

Hybrid automatic repeat request HARQ feedback method, device, equipment and medium

Technical field

The present application relates to the field of wireless communications, and in particular to a hybrid automatic repeat request HARQ feedback method, device, equipment and medium.

Background technique

Multimedia Broadcast Multicast Service (MBMS) is a service introduced in Release 6 of 3GPP (3rd Generation Partnership Project). Multimedia broadcast multicast service is a technology that transmits data from one data source to multiple user devices by sharing network resources. While providing multimedia services, it can effectively utilize network resources and achieve higher-speed multimedia service broadcast and multicast. . Due to the demand for broadcast and multicast services, the fifth generation mobile communication technology (5th-Generation, 5G) also introduces MBMS services, which are called Multicast and Broadcast Services (MBS) in 5G.

In related technology, the NR (New Radio, New Air Interface) MBS service supports the ACK (affirmative response)/NACK (negative response) feedback mode of HARQ (Hybrid Automatic Repeat reQuest, hybrid automatic repeat request) feedback.

Contents of the invention

The embodiments of this application provide a hybrid automatic repeat request HARQ feedback method, device, equipment and medium, which can use the NACK-only (negative response only) feedback mode to perform SPS (Semi-Persistent Scheduling, semi-persistent scheduling of MBS services) ) HARQ feedback of PDSCH (Physical Downlink Shared Channel, physical downlink shared channel). The technical solutions are as follows:

According to one aspect of the present application, a hybrid automatic repeat request HARQ feedback method is provided and applied to a terminal. The method includes:

The reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS is reported to the access network device according to the NACK-only feedback mode.

According to one aspect of the present application, a hybrid automatic repeat request HARQ feedback method is provided, which is applied to access network equipment. The method includes:

Receive feedback from the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS sent by the terminal according to the NACK-only feedback mode.

According to one aspect of the present application, a hybrid automatic repeat request HARQ feedback device is provided, and the device includes:

The first sending module is configured to report the reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS to the access network device according to the NACK-only feedback mode.

The second receiving module is configured to receive reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS sent by the terminal according to the NACK-only feedback mode.

According to one aspect of the present application, a terminal is provided, which terminal includes: a processor and a transceiver connected to the processor; wherein,

The transceiver is configured to report the reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS to the access network device according to the NACK-only feedback mode.

According to one aspect of the present application, a network device is provided. The network device includes: a processor and a transceiver connected to the processor; wherein,

The transceiver is configured to receive reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS sent by the terminal according to the NACK-only feedback mode.

According to one aspect of the present application, a terminal is provided. The terminal includes: a processor and a memory. The memory stores at least one instruction, at least a program, a code set or an instruction set. The at least one instruction, the The at least one program, the code set or the instruction set are loaded and executed by the processor to implement the hybrid automatic repeat request HARQ feedback method as described in the above aspect.

According to one aspect of the present application, a network device is provided. The network device includes: a processor and a memory. The memory stores at least one instruction, at least a program, a code set or an instruction set. The at least one instruction The at least one program, the code set or the instruction set are loaded and executed by the processor to implement the hybrid automatic repeat request HARQ feedback method as described in the above aspect.

According to one aspect of the present application, a computer-readable storage medium is provided. The readable storage medium stores executable instructions, and the executable instructions are loaded and executed by a processor to enable the communication device to implement the above aspects. The hybrid automatic repeat request HARQ feedback method described above.

According to one aspect of an embodiment of the present application, a chip is provided. The chip includes programmable logic circuits and/or program instructions. When the chip is run on a communication device, it is used to enable the communication device to implement the above aspect. Hybrid automatic repeat request HARQ feedback method.

According to one aspect of the present application, a computer program product is provided. When the computer program product is run on a processor of a communication device, the computer program product causes the communication device to perform the hybrid automatic repeat request HARQ feedback method described in the above aspect.

The technical solutions provided by the embodiments of this application at least include the following beneficial effects:

The terminal feeds back the reception status of MBS's SPS PDSCH to the access network device according to the NACK-only feedback mode. If it successfully receives the MBS's SPS PDSCH, it will not send feedback information to the access network device. If it fails to receive the MBS's SPS PDSCH, it will The access network device sends feedback information (NACK) indicating reception failure. For MBS services, which are sent to a large number of terminal groups, compared with the ACK/NACK feedback mode, the NACK-only feedback mode can reduce the size of feedback information, reduce the occupation of uplink feedback resources, and improve resource utilization. Rate.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings without exerting creative efforts.

Figure 1 is a schematic diagram of a communication system provided by an exemplary embodiment of the present application;

Figure 2 is a schematic channel diagram provided by an exemplary embodiment of the present application;

Figure 3 is a schematic diagram of MBS transmission provided by an exemplary embodiment of the present application;

Figure 4 is a flow chart of a HARQ feedback method provided by an exemplary embodiment of the present application;

Figure 5 is a schematic diagram of a HARQ feedback method provided by an exemplary embodiment of the present application;

Figure 6 is a flow chart of a HARQ feedback method provided by an exemplary embodiment of the present application;

Figure 7 is a flow chart of a HARQ feedback method provided by an exemplary embodiment of the present application;

Figure 8 is a schematic diagram of a HARQ feedback method provided by an exemplary embodiment of the present application;

Figure 9 is a schematic diagram of a HARQ feedback method provided by an exemplary embodiment of the present application;

Figure 10 is a flow chart of a HARQ feedback method provided by an exemplary embodiment of the present application;

Figure 11 is a schematic diagram of a HARQ feedback method provided by an exemplary embodiment of the present application;

Figure 12 is a schematic diagram of a HARQ feedback method provided by an exemplary embodiment of the present application;

Figure 13 is a schematic diagram of a HARQ feedback method provided by an exemplary embodiment of the present application;

Figure 14 is a schematic diagram of a HARQ feedback method provided by an exemplary embodiment of the present application;

Figure 15 is a structural block diagram of a HARQ feedback device provided by an exemplary embodiment of the present application;

Figure 16 is a structural block diagram of a HARQ feedback device provided by an exemplary embodiment of the present application;

Figure 17 is a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

The network architecture and business scenarios described in the embodiments of this application are to more clearly explain the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided by the embodiments of this application. Those of ordinary skill in the art will know that with the network architecture evolution and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

Please refer to Figure 1, which shows a schematic diagram of a network architecture 100 provided by an embodiment of the present application. The network architecture 100 may include: a terminal 10, an access network device 20 and a core network device 30.

The terminal 10 may refer to user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, user agent or user device. Optionally, the terminal 10 may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, or a Personal Digital Assistant (PDA). , handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminals in the fifth generation mobile communication system (5th Generation System, 5GS) or public land in future evolutions Terminals in a mobile communication network (Public Land Mobile Network, PLMN), etc. are not limited in the embodiments of the present application. For convenience of description, the devices mentioned above are collectively called terminals. The number of terminals 10 is usually multiple, and one or more terminals 10 may be distributed in the cell managed by each access network device 20 .

The access network device 20 is a device deployed in the access network to provide wireless communication functions for the terminal 10 . The access network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems using different wireless access technologies, the names of devices with access network device functions may be different. For example, in 5G NR systems, they are called gNodeB or gNB. As communication technology evolves, the name "access network equipment" may change. For convenience of description, in the embodiment of the present application, the above-mentioned devices that provide wireless communication functions for the terminal 10 are collectively referred to as access network equipment. Optionally, through the access network device 20, a communication relationship can be established between the terminal 10 and the core network device 30. For example, in a Long Term Evolution (LTE) system, the access network device 20 may be an Evolved Universal Terrestrial Radio Access Network (EUTRAN) or one or more eNodeBs in EUTRAN; In the 5G NR system, the access network device 20 may be a radio access network (Radio Access Network, RAN) or one or more gNBs in the RAN. In the embodiment of this application, the network device refers to the access network device 20, such as a base station, unless otherwise specified.

The core network device 30 is a device deployed in the core network. The core network device 30 mainly functions to provide user connections, manage users, and carry services, and serves as an interface for the bearer network to provide to external networks. For example, the core network equipment in the 5G NR system can include Access and Mobility Management Function (AMF) network elements, User Plane Function (UPF) network elements and Session Management Function (Session Management Function, SMF) network element, etc.

In one example, the access network device 20 and the core network device 30 communicate with each other through some air interface technology, such as the NG interface in the 5G NR system. The access network device 20 and the terminal 10 communicate with each other through some air interface technology, such as the Uu interface.

Please refer to Figure 2, which shows a schematic diagram of a network architecture provided by another embodiment of the present application. The network architecture may include: terminal 10, access network equipment 20 and core network equipment 30.

Among them, the core network equipment 30 includes NSSF (Network Slice Selection Function), AUSF (Authentication Server Function), UDM (Unified Data Management, unified data management), AMF (Access and Mobility Management Function) , access and mobility management function), SMF (Session Management Function, session management function), PCF (Policy Control Function, policy control function), UPF (User Plane Function, user plane function), SF (Sensing Function, perception control Function).

The UE connects to the access layer with the AN (Access Network) through the Uu interface, and exchanges access layer messages and wireless data transmission. The UE connects to the non-access layer (None Access Stratum, NAS) with the AMF through the N1 interface. Exchange NAS messages. AMF is the mobility management function in the core network, and SMF is the session management function in the core network. In addition to mobility management of the UE, the AMF is also responsible for forwarding session management related messages between the UE and the SMF. PCF is the policy management function in the core network and is responsible for formulating policies related to UE mobility management, session management, and charging. PCF transmits data with external application functions (Application Function, AF) through the N5 interface. UPF is the user plane function in the core network. It transmits data with the external data network (Data Network, DN) through the N6 interface and transmits data with the AN through the N3 interface.

The "5G NR system" in the embodiments of this application may also be called a 5G system or an NR system, but those skilled in the art can understand its meaning. The technical solutions described in the embodiments of this application can be applied to the LTE system, the 5G NR system, the subsequent evolution system of the 5G NR system, and the Narrow Band Internet of Things (NB). -IoT) system and other communication systems, this application does not limit this.

Below, the technologies involved in the embodiments of this application are introduced:

Currently, with people's pursuit of speed, delay, high-speed mobility, energy efficiency, and the diversity and complexity of services in future life, the 3GPP international standards organization has begun to develop 5G. The main application scenarios of 5G are: enhanced Mobile Broadband (eMBB), ultra-reliable low-latency communications (URLLC), massive machine type of communication (mMTC) .

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

RRC status

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

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

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

RRC_INACTIVE: Mobility is UE-based cell selection/reselection, there is a connection between CN and NR, UE AS context exists on a base station, paging is triggered by RAN, RAN-based paging area is managed by RAN, network side Knowing the location of the UE is based on the paging area level of the RAN.

In 5G, the maximum channel bandwidth can be 400MHZ, which is very large compared to the maximum bandwidth of 20M in LTE. If the UE keeps working on a wideband carrier, the power consumption of the UE is relatively large. Therefore, it is recommended that the RF (Radio Frequency, electromagnetic frequency) bandwidth of the UE can be adjusted according to the actual throughput of the UE. To this end, BWP (BandWidth Part, bandwidth part) is introduced, and BWP is used to optimize the power consumption of the UE. For example, if the UE's rate is very low, a smaller bandwidth is configured for the UE. If the UE's rate requirements are very high, a larger bandwidth is configured for the UE. If the UE supports high rates or the UE works in CA (Capacity Allocation, carrier aggregation) mode, multiple BWPs can be configured for the UE. Another purpose of BWP is to trigger the coexistence of multiple basic parameter sets (numerology) in a cell.

The UE in the current RRC_IDLE state or RRC_INACTIVE state resides on the initial (initial) BWP. This BWP is visible to the UE in the RRC_IDLE state or RRC_INACTIVE state. The UE can obtain the MIB (Master Information Block) on this BWP. , RMSI (Remaining Minimum System Information, remaining minimum system information) and other information.

CFR (Common Frequency Resource, public frequency domain resource) of NR MBMS/MBS

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

MBMS and SC-PTM (Single Cell-Point-to-Multipoint, but cell point-to-multipoint) systems in LTE

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

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

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

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

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

In Release 13, SC-PTM is introduced. SC-PTM is based on the MBMS network architecture. MCE (Multi-cell/multicast Coordination Entity, multi-cell/multicast coordination entity) decides to use SC-PTM transmission method or MBSFN (Multimedia Broadcast multicast service Single Frequency Network, in single frequency network Multimedia broadcast multicast service) transmission method.

As shown in Figure 2, new logical channels SC-MCCH (Single Cell Multicast Control Channel, single cell multicast control channel) and SC-MTCH (Single Cell Multicast Transport Channel, single cell multicast transmission channel) are introduced and mapped to DL -SCH (Downlink Shared Channel, downlink shared channel) transmission channel, PDSCH physical channel. SC-MCCH and SC-MTCH do not support HARQ operation.

Introducing a new SIB (System Information Block) type, SIB20 to transmit SC-MCCH configuration information. There is only one SC-MCCH in a cell. The SC-MCCH configuration information includes: SC-MCCH modification period, repetition period, and radio frame and subframe configuration information.

SC-MCCH scheduled radio frame: SFN mod mcch-RepetitionPeriod (single frequency network mode multicast control channel repetition period) = mcch-Offset (multicast control channel offset).

The subframe scheduled by SC-MCCH is indicated by sc-mcch-Subframe (single cell multicast control channel subframe).

SC-MCCH only transmits one message SCPTMConfiguration (single cell point-to-multiple configuration), which is used to configure SC-PTM configuration information. Introduce new RNTI (Radio Network Temporary Identifier, wireless network temporary identifier), SC-RNTI (Single Cell RNTI, single cell RNTI) (fixed value FFFC) to identify SC-MCCH scheduling information on PDCCH.

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

In NR, RLC (Radio Link Control) AM (Acknowledged Mode) has an ARQ (Automatic Repeat-reQuest) feedback mechanism. The receiving end sends an RLC status report to feedback that the reception status of the RLC packet is ACK (acknowledgement/confirmation) or NACK (negative acknowledgement/denial). The sender can repeatedly transmit the RLC packet of SN (Sequence Number, sequence number) that returns NACK.

Downstream BWP configuration

The downlink BWP is configured through the BWP-Downlink parameter, as shown in the first ASN.1 encoding below. This parameter includes the bwp-Id field to identify the ID of the current BWP. bwp-Common is used to configure the public parameters of the downlink BWP, as shown below. As shown in the second section of ASN.1 encoding, the genericParameters in BWP-DownlinkCommon are used to configure the frequency domain starting point and the number of PRBs included in the downlink BWP. For a terminal-specific unicast BWP, the bwp-Dedicated parameter in BWP-Downlink will configure the downlink reception parameters on the downlink BWP, as shown in the ASN.1 encoding in the third paragraph below, including at least pdcch-Config, pdsch-Config, and sps-Config, as shown in the second ASN.1 encoding, pdcch-Config is used to indicate the PDCCH transmission method on the downlink BWP, pdsch-Config is used to indicate the PDSCH transmission method on the downlink BWP, sps-Config is used to Indicates the SPS configuration on this downstream BWP.

The first ASN.1 encoding:

The second ASN.1 encoding:

The third paragraph of ASN.1 encoding:

How NR MBS is spread

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

1)Broadcast

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

2)Multicast/Multicast

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

3) Unicast (Unicast)

Sending MBS services to each terminal in unicast mode is suitable for terminals in the RRC_CONNECTED state. The base station sends the same MBS service to each terminal in a one-to-one (Point-To-Point, PTP) transmission mode.

NR MBS group scheduling method

In NR MBS, one-to-many multicast transmission needs to be supported. In this transmission method, the base station needs to schedule the public PDSCH by sending a public downlink control channel. The public PDCCH (Physical Downlink Control Channel) and The public PDSCH is sent within a common frequency domain range (Common Frequency Resource, CFR).

Currently, there are two alternative CFR configuration methods:

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

Second type: CFR is configured as multiple consecutive PRBs (Physical Resource Block, physical resource block) within the range of terminal-specific unicast BWP.

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

In addition, since the public PDCCH that schedules the public PDSCH needs to be sent to multiple receiving terminals at the same time, in order to ensure that the number of bits of the public DCI carried in the public PDCCH determined by the multiple terminals is the same, the terminals cannot configure their own dedicated unicast BWPs. Determine the number of public DCI bits. In addition, since the number of PRBs in the CFR may be different from the initial BWP or CORESET#0 (COntrol REsource SET 0, control resource set 0) currently configured by the terminal, the terminal cannot pass the initial BWP or CORESET#0. Determine the number of bits for the common DCI. Therefore, inevitably, the number of public DCI bits may be different from the number of DCI bits received by the terminal in the existing USS or CSS. Then, in order to reduce the implementation complexity of the terminal, currently the terminal can only receive up to 4 DCI bits with different numbers in a cell, among which the number of DCI bits scrambled by C-RNTI does not exceed 3 types.

Three ways of NR MBS group scheduling

As shown in Figure 3, there are three ways to schedule and transmit MBS services. Group sharing PDCCH/PDSCH means that the PDCCH/PDSCH sent by the base station on a set of time-frequency resources can be received by multiple UEs in the same group. The PTM scheduling methods mentioned in this application all refer to PTM1.

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

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

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

NR MBS group scheduling transmission method

According to the current discussion conclusion, the retransmission mechanism of MBS service based on HARQ-ACK feedback in the connected state supports the following methods:

·Method 1: Initial transmission of PTM1 + retransmission of PTM1;

·Method 2: Initial transmission of PTM1 + retransmission of PTP.

NR MBS group scheduling transmission method

NR MBS services (dynamic scheduling and semi-persistent scheduling (SPS)) support two HARQ-ACK feedback modes:

·Feedback mode one: ACK/NACK feedback mode. If the UE receives the PDSCH and decodes it correctly, it feeds back ACK through the uplink resource PUCCH; if the UE does not receive the PDSCH or fails to decode it, it feeds back NACK through the uplink resource PUCCH.

·Feedback mode two: NACK-only feedback mode. The UE receives the PDSCH and decodes it correctly without feeding back any information; the UE does not receive the PDSCH or fails to decode it, that is, it feeds back a NACK through the uplink resource PUCCH.

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

The HPID of the system (HPID: 0~15) is shared between multicast/multicast and unicast. The specific allocation of HPID is determined by the base station implementation. For example, if HPID#1 is first assigned to the transmission of a TB (Transport Block) 1 of the MBS service, when the initial transmission and potential retransmission of TB1 are completed, the base station will continue to assign HPID#1 to TB2. Transmission use, at this time TB2 is used for unicast transmission of UE3. When the initial transmission and potential retransmission of TB2 are completed, the base station will continue to allocate HPID#1 to the transmission of TB3. At this time, TB3 is used for the transmission of MBS services.

HPID and NDI (New Data Indicator, new data indicator) determine the method of initial transmission and retransmission

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

·Comparing the NDI=1 corresponding to the previously received HPID#1, it can be determined that the currently received TB is the initial transmission of a new TB; the UE will clear the data information of the previous TB stored in the cache, and then Initial transmissions of newly received TBs and potentially received retransmissions are cached.

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

codebook

The codebook is a sequence of bits constructed using ACK/NACK feedback from multiple PDSCH receptions for a configured time window.

3GPP defines two types of HARQ codebooks:

Type1 codebook is a fixed size codebook provided by gNB through RRC signaling (semi-static);

Type2 codebooks are codebooks that have dynamic sizes and change based on resource allocation.

Type 1 Codebook (Type 1 codebook, semi-static codebook)

The total size of the Type 1 codebook is the sum of the number of PDSCH transmissions within a given time window. For a specific time window, this sum is related to:

1. Multiple PDSCH transmissions in a single time slot;

2. Transmit multiple PDSCHs across time slots

3. Multiple PDSCHs transmitted across carriers

4. Multiple transport blocks TB for a specific PDSCH

5. Multiple CBGs in one TB;

The specific time window will be defined by the DCI used to allocate PDSCH resources.

Type1 codebooks have limitations, and the size of the semi-static codebook is fixed. Regardless of the actual PDSCH resource allocation, the UE must send the specified number of bits in the HARQ codebook. For example, there are 3 PDSCH allocations in a single slot, and this configuration applies to all 3 carriers. Allocation 1(S, L)={2,4}, Allocation 2(S, L)={6,4}, Allocation 3(S, L)={10,4}, so the total codebook size=3* 176 = 528 bits.

If the PDSCH UE receives not 3 but 2 PDSCH allocations, then the UE will still send 528 bits. To overcome this limitation, 3GPP defined Type 2 codebooks with dynamic sizes.

Type 2 Codebook (Type 2 codebook, dynamic codebook)

Type2 codebooks eliminate inefficiencies caused by unused transmission occasions, but another difficulty with Type2 codebooks is maintaining correct calculations between the actual transmission and feedback.

In the semi-static codebook, the UE does not have PDSCH transmission in the vacant codebook entries, that is, the codebook entries and PDSCH are mapped one-to-one.

In dynamic codebooks, the codebook size is determined by the actual transmission conditions. 3GPP introduced a counter: "Downlink Assignment Indicator (DAI)". DAI helps avoid problems caused by missed transfers. This counter has two formats: DCI 1_0 and DCI1_1.

DAI is a 2-bit field, and its range is 1 to 4, which means that DAI can detect up to 3 missed transfers. The gNB will provide the DAI value and if the UE detects any missing value of DAI, the UE will assume a missing transmission and it will be mapped into a blank codebook. The counter value will be reset on every fourth transfer.

Please refer to Figure 4, which shows a flow chart of a HARQ feedback method provided by an embodiment of the present application. This method can be applied to the terminal of the system architecture shown in Figure 1. The method includes the following steps.

Step 210: Report the SPSPDSCH reception feedback of the MBS to the access network device according to the NACK-only feedback mode.

Exemplarily, the terminal is configured to report the reception feedback of the SPS PDSCH of the MBS using the NACK-only (negative acknowledgment only) feedback mode.

The access network equipment sends MBS service data through PDSCH. The terminal receives the PDSCH sent by the access network device, and the PDSCH carries MBS service data. The transmission resources of the PDSCH are configured through SPS (semi-persistent scheduling). That is, the SPS PDSCH of MBS means: PDSCH is used to transmit MBS, and the PDSCH adopts the SPS scheduling method.

For example, the access network device may transmit the MBS in any one of broadcast, multicast, and unicast modes.

For example, the access network device broadcasts PDSCH. Terminals in the non-connected state (RRC idle state/RRC inactive state) and terminals in the connected state (RRC connected state) can receive the PDSCH broadcast by the access network device and read from it. MBS business data.

For another example, the access network device sends the PDSCH to a first group of terminals. The first group of terminals includes at least two terminals, including terminals that perform embodiments of the present application. The first group of terminals respectively receive the PDSCH and read the MBS service data therefrom. Wherein, the first group of terminals is in RRC connected state.

For another example, the access network device sends the PDSCH to the first terminal, and the first terminal is the terminal that performs the embodiment of the present application. The first terminal receives the PDSCH sent by the access network device and reads the MBS service data therefrom. Wherein, the first terminal is in RRC connected state.

For example, the terminal needs to feedback the reception status of the PDSCH to the access network device, that is, perform HARQ feedback of the PDSCH to inform the access network device whether the terminal successfully receives the PDSCH. If the terminal fails to receive the PDSCH successfully, the access network device can initiate retransmission of the PDSCH based on the HARQ feedback.

The access network equipment configures the terminal to report the SPS PDSCH of the MBS in NACK-only feedback mode. That is, if the terminal successfully receives the PDSCH, it does not need to report reception feedback to the access network device. If the terminal fails to receive the PDSCH, it reports reception failure feedback to the access network device.

The reception feedback can also be replaced with HARQ feedback, HARQ feedback information, feedback information, reception feedback information, ACK/NACK information, NACK information and other nouns with similar meanings.

The reception feedback includes the reception feedback information of the SPS PDSCH of the MBS received by the terminal. For example, a 1 in the receiving feedback indicates ACK, that is, the SPS PDSCH of the MBS is received; a 0 in the receiving feedback indicates a NACK, that is, the SPS PDSCH of the MBS is not received.

The SPS PDSCH of each MBS corresponds to an uplink feedback resource PUCCH (Physical Uplink Control Channel, physical uplink control channel). The SPS PDSCHs of multiple MBSs may correspond to the same uplink feedback resource PUCCH, and the terminal feeds back the feedback information corresponding to the SPS PDSCHs of multiple MBSs on the uplink feedback resource PUCCH. That is, the received feedback includes multiple feedback information, each feedback information Indicates the reception status of SPS PDSCH of an MBS.

For example, multiple pieces of feedback information are fed back by forming a codebook, that is, the received feedback is a codebook generated based on the multiple pieces of feedback information.

For example, as shown in Figure 5, PDSCH1 of MBS SPS#1 corresponds to the uplink feedback resource PUCCH1, and PDSCH2 of MBS SPS#2 corresponds to the uplink feedback resource PUCCH1; if PDSCH1 is successfully received but PDSCH2 fails to be received, then in PUCCH1 the corresponding PDSCH1 and PDSCH2 The codebook generated by the two feedback messages can be 10. PDSCH3 of MBS SPS#1 corresponds to the uplink feedback resource PUCCH2, and PDSCH4 of MBS SPS#2 corresponds to the uplink feedback resource PUCCH2; if PDSCH3 reception fails and PDSCH4 reception fails, the codebook generated by the two feedback information corresponding to PDSCH3 and PDSCH4 in PUCCH2 Can be 00.

How the terminal generates the reception feedback based on multiple pieces of feedback information will be described in detail in subsequent embodiments.

To sum up, in the method provided by this embodiment, the terminal feedbacks the reception status of the MBS's SPS PDSCH to the access network device according to the NACK-only feedback mode. If the MBS's SPS PDSCH is successfully received, no feedback is sent to the access network device. Information, if the SPS PDSCH of MBS fails to be received, feedback information (NACK) of reception failure is sent to the access network device. For MBS services, which are sent to a large number of terminal groups, compared with the ACK/NACK feedback mode, the NACK-only feedback mode can reduce the size of feedback information, reduce the occupation of uplink feedback resources, and improve resource utilization. Rate.

Please refer to Figure 6, which shows a flow chart of a hybrid automatic repeat request HARQ feedback method provided by an embodiment of the present application. This method can be applied to the access network equipment of the system architecture shown in Figure 1. The method includes the following steps.

Step 220: Receive reception feedback of the SPSPDSCH of the MBS sent by the terminal according to the NACK-only feedback mode.

The access network equipment sends configuration information to the terminal. The configuration information is used to instruct the terminal to report the SPS PDSCH reception feedback of the MBS in accordance with the NACK-only feedback mode.

It should be noted that the NACK-only feedback mode is the HARQ feedback mode configured by the access network equipment for the terminal, but the HARQ feedback mode actually adopted by the terminal may not be the NACK-only feedback mode. When the terminal actually generates reception feedback, it can follow the configuration The NACK-only feedback mode generates reception feedback, and can also automatically switch to the ACK/NACK feedback mode to generate reception feedback. That is, although the access network device instructs the terminal to perform feedback in the NACK-only feedback mode, the actual received feedback may be feedback information in the NACK-only feedback mode or feedback information in the ACK/NACK feedback mode.

For example, under certain circumstances, the terminal automatically switches the feedback mode from the NACK-only feedback mode to the ACK/NACK feedback mode to generate reception feedback. In this case, the access network equipment will read and receive feedback according to the ACK/NACK feedback mode.

Exemplarily, an exemplary embodiment is provided in which the terminal reports reception feedback after receiving the SPS PDSCH of the MBS.

Please refer to Figure 7, which shows a flow chart of a hybrid automatic repeat request HARQ feedback method provided by an embodiment of the present application. This method can be applied to terminals and access network equipment in the system architecture shown in Figure 1. The method includes the following steps.

Step 301: The access network device sends feedback configuration information to the terminal.

Optionally, the access network device sends a PDCCH to the terminal, and the PDCCH carries feedback configuration information; the terminal receives the PDCCH. For example, the PDCCH includes DCI, and the DCI includes feedback configuration information. Alternatively, the PDCCH includes an RRC message, and the RRC message includes feedback configuration information.

The feedback configuration information is used to indicate that the HARQ feedback mode of the SPS PDSCH of the MBS is the NACK-only feedback mode.

Optionally, the access network device can also send configuration information to the terminal. The configuration information is used to indicate the uplink feedback resources of the SPS PDSCH of the MBS; the terminal receives the configuration information sent by the access network device. The access network device sends a PDCCH to the terminal, and the PDCCH carries configuration information. For example, the PDCCH includes DCI, and the DCI includes configuration information. Alternatively, the PDCCH includes an RRC message, and the RRC message includes configuration information.

This configuration information can instruct the terminal to report the SPS PDSCH reception feedback of the MBS after receiving the DCI. Alternatively, the configuration information may instruct the terminal to report the reception feedback of the SPS PDSCH of the MBS after receiving the last SPS PDSCH of the MBS. Alternatively, the configuration information may indicate that the terminal reports the uplink feedback resources used by the SPS PDSCH of the MBS to receive feedback.

Optionally, the access network device can also send the scheduling information of the SPS PDSCH of the MBS to the terminal. The scheduling information is used to indicate the transmission resources of the SPS PDSCH of the MBS; the terminal receives the scheduling information sent by the access network device. The access network device sends a PDCCH to the terminal, and the PDCCH carries scheduling information. For example, the PDCCH includes DCI, and the DCI includes scheduling information.

After receiving the scheduling information, the terminal receives the SPS PDSCH of the MBS on the transmission resources indicated by the scheduling information.

Step 302: The access network device sends the SPS PDSCH of the MBS.

The access network equipment sends the SPS PDSCH of the MBS through broadcast, multicast or unicast.

Step 303: The terminal receives the SPS PDSCH of the MBS sent by the access network device.

The terminal receives the SPS PDSCH of the MBS sent by the access network equipment, and generates reception feedback based on the reception of the SPS PDSCH of the MBS.

In an optional embodiment, the received feedback only includes one bit of feedback information. For example, if the terminal receives the first PDSCH of the SPS of the MBS, the uplink feedback resource corresponding to the first PDSCH is the first PUCCH, and there is and only the uplink feedback resource corresponding to the first PDSCH is the first PUCCH, then the terminal only needs to One-bit reception feedback of the first PDSCH is sent on a PUCCH.

In another optional embodiment, the received feedback includes a codebook formed by the feedback information corresponding to the SPS PDSCH of the MBS; that is, the received feedback includes a code block composed of a series of consecutive bits.

Receiving feedback as code blocks may include the following situations;

Scenario 1: The SPS PDSCH of an MBS corresponds to multiple transport blocks (Transport Block, TB). Each transport block corresponds to one bit of feedback information. Multiple bits of feedback information are connected to obtain a code block.

Scenario 2: The SPS PDSCH of multiple MBSs correspond to the same uplink feedback resource. The SPS PDSCH of each MBS corresponds to at least one bit of feedback information. Multiple bits of feedback information are connected to obtain a code block, and the terminal transmits the code on the uplink feedback resource. block (receiving feedback).

Optionally, the codebook may be a Type1 codebook (Type 1 codebook) and/or a Type2 codebook (Type 2 codebook).

Exemplarily, the access network device will also configure codebook type information to the terminal. The codebook type information is used to indicate the codebook type used to receive feedback. The terminal generates a codebook for receiving feedback according to the codebook type indicated by the access network device. Codebook.

When generating reception feedback according to the Type1 codebook: the terminal needs to convert the feedback mode from the NACK-only feedback mode to the ACK/NACK feedback mode. That is, the terminal converts the HARQ feedback mode from the NACK-only feedback mode to the positive response/negative response ACK/NACK feedback mode; the ACK/NACK feedback mode is used to report the SPS PDSCH reception feedback of the MBS to the access network device.

When generating reception feedback according to the Type2 codebook: the terminal can provide feedback according to the NACK-only feedback mode, or can switch to the ACK/NACK feedback mode for feedback. The terminal uses the NACK-only feedback mode to report the MBS SPS PDSCH reception feedback to the access network equipment; or, converts the HARQ feedback mode from the NACK-only feedback mode to the ACK/NACK feedback mode; uses the ACK/NACK feedback mode to report to the access network device. The network equipment reports the SPS PDSCH reception feedback of MBS.

For example, when the SPS PDSCHs of multiple MBSs correspond to the same uplink feedback resource, in the reception feedback sent on the uplink feedback resources, the feedback information corresponding to the SPS PDSCHs of each MBS can be arranged in any of the following ways:

Sorting method 1: Arrange according to SPS index (SPS-index). That is, in the codebook, multiple feedback information corresponding to the SPS PDSCH of multiple MBSs are arranged according to the SPS index.

Optionally, the information may be arranged in SPS index order or in reverse order of the SPS index, which is not limited in the embodiment of the present application.

The PDSCH of MBS adopts semi-persistent scheduling (SPS). The access network equipment first configures at least one set of SPS resources for the terminal, and each set of SPS resources corresponds to an SPS index. When the access network device configures the PDSCH transmission resources of the MBS, it uses the SPS index to indicate that one of the SPS resources is used to transmit the PDSCH of the MBS. Then the SPS PDSCH of each MBS corresponds to an SPS index. When generating a codebook, the terminal sorts the feedback information according to the SPS index corresponding to the SPS PDSCH of each MBS, and then generates a codebook based on multiple feedback information.

For example, as shown in Figure 8, the terminal receives the SPS PDSCH1, PDSCH2, PDSCH3 and PDSCH4 of MBS. Among them, the SPS index of PDSCH1 is SPS#1, the SPS index of PDSCH2 is SPS#2, and the SPS index of PDSCH3 is SPS#3. The SPS index of PDSCH4 is SPS#4. Four PDSCHs are instructed to perform HARQ feedback on the same uplink feedback resource PUCCH. Then the reception feedback in the PUCCH includes feedback information corresponding to the four PDSCHs, that is, the reception feedback includes a codebook composed of 4-bit feedback information; the order of the 4-bit feedback information in the codebook is arranged in accordance with the SPS index order, that is, , the first bit is the feedback information of PDSCH1 of SPS#1, the second bit is the feedback information of PDSCH2 of SPS#2, the third bit is the feedback information of PDSCH3 of SPS#3, and the fourth bit is the feedback information of PDSCH4 of SPS#4. Feedback. Each feedback message includes ACK or NACK.

Sorting method 2: Arrange according to G-CS-RNTI (Group Configured Scheduling RNTI, Group-Semi-Persistent Scheduling-Wireless Network Temporary Identifier). In the codebook, multiple feedback information corresponding to the SPS PDSCH of multiple MBSs are arranged according to G-CS-RNTI.

Optionally, the information may be arranged in G-CS-RNTI order or in reverse order of G-CS-RNTI, which is not limited in the embodiment of the present application.

Exemplarily, G-CS-RNTI is used to scramble and descramble PDSCH. The access network device scrambles PDSCH according to G-CS-RNTI and then sends the scrambled PDSCH; the terminal receives the scrambled PDSCH. , descramble it according to G-CS-RNTI to obtain PDSCH. The access network equipment configures a G-CS-RNTI for each PDSCH, that is, each PDSCH corresponds to a G-CS-RNTI.

Sorting method 3: Arrange according to PDSCH timing. That is, in the codebook, multiple feedback information corresponding to the SPS PDSCH of multiple MBSs are arranged in time sequence.

The timing may be at least one of the reception timing of the SPS PDSCH of the MBS and the transmission timing of the SPS PDSCH of the MBS.

Optionally, they can be arranged in chronological order or in reverse chronological order, which is not limited by the embodiment of the present application.

For example, as shown in Figure 9, the terminal sequentially receives the SPS PDSCH1, PDSCH3, PDSCH2 and PDSCH4 of the MBS. Four PDSCHs are instructed to perform HARQ feedback on the same uplink feedback resource PUCCH. Then the reception feedback in the PUCCH includes feedback information corresponding to the four PDSCHs, that is, the reception feedback includes a codebook composed of 4-bit feedback information; the order of the 4-bit feedback information in the codebook is arranged according to the reception timing of the PDSCH, That is, the first bit is the feedback information of PDSCH1, the second bit is the feedback information of PDSCH3, the third bit is the feedback information of PDSCH2, and the fourth bit is the feedback information of PDSCH4. Each feedback message includes ACK or NACK.

Step 304: The terminal sends the SPS PDSCH reception feedback of the MBS to the access network device.

After generating the reception feedback, the terminal sends the reception feedback of the SPS PDSCH of the MBS to the access network device on the indicated PUCCH.

To sum up, with the method provided in this embodiment, the terminal feeds back the reception status of the SPS PDSCH of the MBS to the access network device according to the NACK-only feedback mode. When the terminal needs to feed back multiple feedback information on the same uplink feedback resource, the terminal A codebook is formed based on multiple feedback information. If the codebook is a type 1 codebook, the terminal needs to convert the feedback mode from NACK-only feedback mode to ACK/NACK feedback mode. If the codebook is a type 2 codebook, the terminal can adopt the NACK-only feedback mode or the ACK/NACK feedback mode. This enables SPS PDSCH that uses NACK-only feedback mode to feed back MBS.

According to the method provided in this embodiment, when the terminal needs to feed back the SPS PDSCHs of multiple MBSs on the same uplink feedback resource, the feedback information corresponding to the SPS PDSCHs of the multiple MBSs can form a codebook in a certain order, and the terminal reports the SPS PDSCHs of multiple MBSs to the access network device. Report the codebook.

For example, the SPS PDSCH of MBS and the SPS PDSCH of unicast service may correspond to the same uplink feedback resource. An embodiment of feeding back the reception feedback of MBS and unicast service in the same uplink feedback resource is provided.

Please refer to Figure 10, which shows a flow chart of a hybrid automatic repeat request HARQ feedback method provided by an embodiment of the present application. This method can be applied to terminals and access network equipment in the system architecture shown in Figure 1. The method includes the following steps.

Step 401: The access network device sends the SPS PDSCH of the MBS and the SPS PDSCH of the unicast service.

Step 402: The terminal receives the SPS PDSCH of the MBS and the SPS PDSCH of the unicast service sent by the access network device.

The terminal receives at least one SPS PDSCH of MBS and at least one SPS PDSCH of unicast service. Among them, the SPS PDSCH of each MBS corresponds to an uplink feedback resource PUCCH, and the SPS PDSCH of each unicast service corresponds to an uplink feedback resource PUCCH.

According to the higher layer configuration information (such as configuration information in RRC) or the DCI indication information for activating SPS, the uplink feedback resource of the SPS PDSCH of the MBS and the uplink feedback resource of the SPS PDSCH of the unicast service can be the same uplink feedback resource. That is, the terminal feeds back the reception status of multiple PDSCH/TBs in one uplink feedback resource, including TBs of MBS and TBs of unicast services.

For example, as shown in Figure 11, the terminal receives PDSCH1 and PDSCH5 of MBS SPS#1; receives PDSCH2 and PDSCH6 of MBS SPS#2; receives PDSCH3 and PDSCH7 of unicast service SPS#3; receives PDSCH4 of unicast service SPS#4 , PDSCH8; among them, the uplink feedback resources corresponding to PDSCH1, PDSCH2, PDSCH3, and PDSCH4 are PUCCH1; and the uplink feedback resources corresponding to PDSCH5, PDSCH6, PDSCH7, and PDSCH8 are PUCCH2.

For example, an uplink feedback resource includes feedback information corresponding to SPS PDSCHs of N MBSs and feedback information corresponding to SPS PDSCHs of M unicast services. Among them, N≥0, M≥0. When M equals 0, the uplink feedback resource only contains the feedback information of the SPS PDSCH of the MBS; when N equals 0, the uplink feedback resource only contains the feedback information of the SPS PDSCH of the unicast service.

Among them, the SPS PDSCH of MBS is configured to adopt NACK-only feedback mode; the SPS PDSCH of unicast service is configured to adopt ACK/NACK feedback mode. Optionally, the SPS PDSCH of the unicast service can also be configured to adopt the NACK-only feedback mode. This embodiment uses the ACK/NACK feedback mode as an example.

For example, one PDSCH corresponds to at least one TB, and each TB corresponds to one bit of feedback information. The feedback information may be ACK or NACK.

In an optional embodiment, when multiple feedback information corresponding to multiple TBs need to be fed back on an uplink feedback resource, the multiple feedback information forms a codebook. When forming the codebook, the SPS of the MBS and the NACK of the PDSCH The -only feedback mode is converted to ACK/NACK feedback mode, and then the feedback information generated according to the ACK/NACK feedback mode is imported into the codebook.

Among them, the codebook can be a Type1 codebook or a Type2 codebook. Among them, when the codebook is a Type1 codebook, the feedback mode of the SPS PDSCH of the MBS must be changed from the NACK-only feedback mode to the ACK/NACK feedback mode. When the codebook is a Type2 codebook, the feedback mode of the MBS's SPS PDSCH can be the NACK-only feedback mode, or it can be converted to the ACK/NACK feedback mode.

When the SPS PDSCH of the MBS and the SPS PDSCH of the unicast service correspond to the same uplink feedback resource, and feedback information of multiple PDSCHs needs to be fed back on the same PUCCH resource, the feedback is performed by forming a codebook. The codebook includes feedback information corresponding to the SPS PDSCH of the unicast service and feedback information corresponding to the SPS PDSCH of the MBS.

The embodiments of this application provide two types of methods for generating codebooks based on feedback information corresponding to MBS and feedback information corresponding to unicast services:

Method 1: Cascade codebook generation.

The codebook includes a cascaded first sub-codebook and a second sub-codebook. The first sub-codebook is formed by the feedback information corresponding to the SPS PDSCH of the unicast service; the second sub-codebook is formed by the feedback information corresponding to the SPS PDSCH of the MBS. form.

That is, the terminal forms a first subcodebook based on the feedback information of the SPS PDSCH of the unicast service, and the first subcodebook includes at least one bit; the terminal forms a second subcodebook based on the feedback information of the SPS PDSCH of the MBS, and the second subcodebook This contains at least one bit. After forming the first sub-codebook and the second sub-codebook, the terminal cascades the first sub-codebook and the second sub-codebook to obtain a codebook, which is the reception feedback.

For example, the order of the first sub-codebook and the second sub-codebook in the codebook can be arbitrary. In one case, the first sub-codebook is in front and the second sub-codebook is in the back; in another case, The second sub-codebook is in the front and the first sub-codebook is in the back.

When the first sub-codebook or the second sub-codebook includes at least two pieces of feedback information, the at least two pieces of feedback information are arranged in a certain order. The order of arrangement may refer to the description in the embodiment shown in FIG. 7 .

Taking the SPS PDSCH of MBS as an example, in the second sub-codebook, the multiple feedback information corresponding to the SPS PDSCH of multiple MBS are arranged according to the SPS index; or, in the second sub-codebook, the SPS PDSCH of multiple MBS respectively correspond to The multiple feedback information of multiple MBS are arranged according to G-CS-RNTI; or, in the second sub-codebook, the multiple feedback information corresponding to the SPS PDSCH of multiple MBS are arranged in time sequence; where the time sequence includes the reception order of the SPS PDSCH of the MBS , at least one of the sending sequences of SPS of MBS and PDSCH.

For example, as shown in Figure 12, the terminal receives PDSCH1 of MBSSPS#1, PDSCH2 of MBS SPS#2, PDSCH3 of unicast service SPS#3, and PDSCH4 of unicast service SPS#4. The four PDSCHs are instructed to perform HARQ feedback on the same uplink feedback resource PUCCH, and use the Type1 codebook. Then the terminal uses the ACK/NACK feedback mode to generate the first sub-codebook corresponding to the unicast service, and converts the NACK-only feedback mode to the ACK/NACK feedback mode to generate the second sub-codebook corresponding to the MBS. The first sub-codebook includes The feedback information corresponding to PDSCH3 and PDSCH4, and the second sub-codebook includes the feedback information of PDSCH1 and PDSCH2. Among them, the feedback information in the first sub-codebook and the second sub-codebook are sorted according to the SPS index. The first bit of the first sub-codebook is the feedback information of PDSCH3 of SPS#3, and the second bit is the feedback information of PDSCH4 of SPS#4. The first bit of the second sub-codebook is the feedback information of PDSCH1 of SPS#1, and the second bit is the feedback information of PDSCH2 of SPS#2. Each feedback message includes ACK or NACK. The first sub-codebook and the second sub-codebook are cascaded to obtain the codebook (receiving feedback).

As another example, as shown in Figure 13, the terminal receives PDSCH1 of MBS SPS#1, PDSCH2 of MBS SPS#2, PDSCH3 of unicast service SPS#3, and PDSCH4 of unicast service SPS#4. The four PDSCHs are instructed to perform HARQ feedback on the same uplink feedback resource PUCCH, and use the Type1 codebook. Then the terminal uses the ACK/NACK feedback mode to generate the first sub-codebook corresponding to the unicast service, and converts the NACK-only feedback mode to the ACK/NACK feedback mode to generate the second sub-codebook corresponding to the MBS. The first sub-codebook includes The feedback information corresponding to PDSCH3 and PDSCH4, and the second sub-codebook includes the feedback information of PDSCH1 and PDSCH2. Wherein, the feedback information in the first sub-codebook and the second sub-codebook are ordered according to the reception timing of the PDSCH. The first bit of the first sub-codebook is the feedback information of PDSCH4 of SPS#4, and the second bit is the feedback information of PDSCH3 of SPS#3. The first bit of the second sub-codebook is the feedback information of PDSCH2 of SPS#2, and the second bit is the feedback information of PDSCH1 of SPS#1. Each feedback message includes ACK or NACK. The first sub-codebook and the second sub-codebook are cascaded to obtain the codebook (receiving feedback).

For another example, the terminal is configured to use the Type2 codebook to generate unicast services and reception feedback corresponding to the SPS PDSCH of the MBS. Then the terminal uses the NACK-only feedback mode to generate the second sub-codebook corresponding to the SPS PDSCH of the MBS, and uses the ACK/NACK feedback mode to generate the first sub-codebook corresponding to the SPS PDSCH of the unicast service. The first sub-codebook is cascaded with the second sub-codebook to obtain the codebook.

Method 2: Mixed codebook generation.

In the codebook, the feedback information corresponding to the SPS PDSCH of the unicast service and the feedback information corresponding to the SPS PDSCH of the MBS are arranged according to the transmission/reception timing of the PDSCH; or, in the codebook, the feedback information corresponding to the SPS PDSCH of the unicast service and the MBS The feedback information corresponding to the SPS PDSCH is arranged according to the SPS index; among them, the sending/receiving timing of the PDSCH includes at least one of the following: the sending/receiving timing of the SPS PDSCH of the unicast service, and the sending/receiving timing of the SPS PDSCH of the MBS.

That is, the terminal sorts the feedback information corresponding to the unicast service and the feedback information corresponding to the MBS in a certain order to generate a codebook, in which the feedback information corresponding to the unicast service and the feedback information corresponding to the MBS are mixed and arranged.

Taking the PDSCH transmission/reception timing sequence as an example, as shown in Figure 14, the terminal receives PDSCH1 of MBS SPS#1, PDSCH2 of MBS SPS#2, PDSCH3 of unicast service SPS#3, and PDSCH4 of unicast service SPS#4. The four PDSCHs are instructed to perform HARQ feedback on the same uplink feedback resource PUCCH, and use the Type1 codebook. Then the terminal uses the ACK/NACK feedback mode to generate feedback information corresponding to the unicast service, and the terminal converts the NACK-only feedback mode to the ACK/NACK feedback mode to generate feedback information corresponding to the MBS. Multiple feedback information are ordered according to the reception timing of PDSCH to form a codebook. Then the first bit of the codebook is the feedback information of PDSCH1 of MBS SPS#1, the second bit is the feedback information of PDSCH3 of unicast service SPS#3, the third bit is the feedback information of PDSCH2 of MBS SPS#2, and the fourth bit is the feedback information of PDSCH2 of MBS SPS#2. The bits are the feedback information of PDSCH4 of unicast service SPS#4. Each feedback message includes ACK or NACK.

Step 403: The terminal sends reception feedback of the SPS PDSCH of the MBS and the SPS PDSCH of the unicast service to the access network device.

After generating the reception feedback, the terminal sends the reception feedback of the SPS PDSCH of the MBS and the SPS PDSCH of the unicast service to the access network device on the indicated PUCCH.

To sum up, the method provided by this embodiment provides a method of multiplexing uplink feedback resources with ACK/NACK feedback of unicast SPS service in NACK-only feedback mode for semi-persistent scheduling in broadcast multicast services. One way is that the UE retains the NACK-only feedback mode of the MBS SPS, and forms a dynamic codebook together with the ACK/NACK feedback information of the unicast SPS for feedback on the same uplink resource. Another way is that the UE converts the NACK-only feedback mode of the MBS SPS into the ACK/NACK feedback mode, and forms a codebook for feedback of the ACK/NACK feedback information in different ways. These different ways include forming subcodes. Each sub-codebook is sorted according to the timing sequence of PDSCH or the SPS index value from small to large.

The method provided by this embodiment provides a method of multiplexing uplink feedback resources with ACK/NACK feedback of unicast SPS service in the NACK-only feedback mode of semi-persistent scheduling (SPS) in NR broadcast multicast service (MBS). method. Compared with the ACK/NACK feedback mode, the NACK-only feedback mode of NR MBS is a more compromised feedback mode, but when it is applied to MBS semi-persistent scheduling, if it can only use independent uplink resources to report separately and If it cannot be multiplexed with the uplink feedback of unicast SPS, its advantages will be greatly offset. The uplink feedback method provided in this embodiment can not only combine and report multiple NACK-only feedback information bits, but also combine and report them together with the feedback information of the unicast service SPS; in addition, the upgrade and improvement of codebook generation can also be reported This greatly improves the utilization efficiency of uplink resources and reduces the complexity on the UE side.

It should be noted that the PDSCH of the SPS mentioned in this application does not include the first/first group of PDSCHs scheduled when PDCCH/DCI is used to activate the SPS, and only includes non-DCI scheduled PDSCHs in subsequent SPS.

It should be noted that the method steps in the above embodiments can be combined arbitrarily to obtain new embodiments, and this application is not limited thereto.

Figure 15 shows a structural block diagram of a hybrid automatic repeat request HARQ feedback device provided by an exemplary embodiment of the present application. The device can be implemented as a terminal, or implemented as a part of the terminal. The device includes:

The first sending module 501 is configured to report the reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS to the access network device according to the NACK-only feedback mode.

In an optional embodiment, the device further includes:

The first receiving module 502 is configured to receive feedback configuration information sent by the access network device, where the feedback configuration information indicates that the HARQ feedback mode of the SPS PDSCH of the MBS is the NACK-only feedback mode.

In an optional embodiment, the reception feedback includes a codebook formed by feedback information corresponding to the SPS PDSCH of the MBS;

Wherein, the feedback information corresponding to the SPS PDSCH of the MBS includes at least one of the following: multiple feedback information corresponding to multiple transmission blocks TB of the SPS PDSCH of one MBS, multiple feedback information corresponding to the SPS PDSCH of multiple MBS. .

In an optional embodiment, the codebook includes a Type 1 codebook and/or a Type 2 codebook.

In an optional embodiment, the codebook is a type 1 codebook;

The reporting of the reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast service MBS to the access network device according to the NACK-only feedback mode includes:

Convert the HARQ feedback mode from the NACK-only feedback mode to the acknowledgment/negative acknowledgment ACK/NACK feedback mode;

The ACK/NACK feedback mode is used to report the reception feedback of the SPSPDSCH of the MBS to the access network device.

In an optional embodiment, the codebook is a type 2 codebook;

Report the reception feedback of the SPSPDSCH of the MBS to the access network device in a NACK-only feedback mode;

or,

Convert the HARQ feedback mode from the NACK-only feedback mode to the ACK/NACK feedback mode; use the ACK/NACK feedback mode to report the reception feedback of the SPSPDSCH of the MBS to the access network device.

In an optional embodiment, the feedback information corresponding to the SPS PDSCH of the MBS includes multiple feedback information corresponding to the SPS PDSCH of multiple MBSs;

In the codebook, multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged according to the SPS index;

or,

In the codebook, the multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged according to the group-semi-persistent scheduling-radio network temporary identifier G-CS-RNTI;

or,

In the codebook, multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged in time sequence;

Wherein, the timing includes at least one of the receiving sequence of the SPS PDSCH of the MBS and the sending sequence of the SPS PDSCH of the MBS.

In an optional embodiment, the codebook includes feedback information corresponding to the SPS PDSCH of the unicast service and feedback information corresponding to the SPS PDSCH of the MBS.

In an optional embodiment, the codebook includes a concatenated first sub-codebook and a second sub-codebook, and the first sub-codebook is formed by feedback information corresponding to the SPS PDSCH of the unicast service ; The second sub-codebook is formed by feedback information corresponding to the SPS PDSCH of the MBS.

In the second sub-codebook, multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged according to the SPS index;

or,

In the second sub-codebook, the multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged according to the group-semi-persistent scheduling-radio network temporary identifier G-CS-RNTI;

or,

In the second sub-codebook, multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged in time sequence;

In an optional embodiment, in the codebook, the feedback information corresponding to the SPS PDSCH of the unicast service and the feedback information corresponding to the SPS PDSCH of the MBS are arranged according to the transmission/reception timing of the PDSCH;

Or, in the codebook, the feedback information corresponding to the SPS PDSCH of the unicast service and the feedback information corresponding to the SPS PDSCH of the MBS are arranged according to the SPS index;

Wherein, the sending/receiving timing of the PDSCH includes at least one of the following: the sending/receiving timing of the SPS PDSCH of the unicast service, and the sending/receiving timing of the SPS PDSCH of the MBS.

In an optional embodiment, the SPS PDSCH of the unicast service adopts ACK/NACK feedback mode.

In an optional embodiment, the SPS PDSCH of the unicast service and the SPS PDSCH of the MBS correspond to the same uplink feedback resource, and the uplink feedback resource is used to report the reception feedback.

Figure 16 shows a structural block diagram of a hybrid automatic repeat request HARQ feedback device provided by an exemplary embodiment of the present application. The device can be implemented as a network device, or can be implemented as part of an access network device. The device includes:

The second receiving module 503 is configured to receive reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multi-broadcast service MBS sent by the terminal according to the NACK-only feedback mode.

In an optional embodiment, the device further includes:

The second sending module 504 is configured to send feedback configuration information to the terminal, where the feedback configuration information indicates that the HARQ feedback mode of the SPS PDSCH of the MBS is the NACK-only feedback mode.

In an optional embodiment, the codebook is a type 1 codebook;

In the reception feedback, the ACK/NACK feedback mode is used to feed back the SPSPDSCH of the MBS.

In an optional embodiment, the codebook is a type 2 codebook;

In the reception feedback, a NACK-only feedback mode is used to feed back the reception feedback of the SPSPDSCH of the MBS;

or,

In the reception feedback, the ACK/NACK feedback mode is used to feed back the reception feedback of the SPSPDSCH of the MBS.

or,

Figure 17 shows a schematic structural diagram of a communication device (terminal or network device) provided by an exemplary embodiment of the present application. The communication device includes: a processor 101, a receiver 102, a transmitter 103, a memory 104 and a bus 105.

The processor 101 includes one or more processing cores. The processor 101 executes various functional applications and information processing by running software programs and modules.

The receiver 102 and the transmitter 103 can be implemented as a communication component, which can be a communication chip, and the communication component can be called a transceiver.

The memory 104 is connected to the processor 101 via a bus 105 .

The memory 104 may be used to store at least one instruction, and the processor 101 is used to execute the at least one instruction to implement each step in the above method embodiment.

Additionally, memory 104 may be implemented by any type of volatile or non-volatile storage device, or combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable Read-only memory (Electrically-Erasable Programmable Read Only Memory, EEPROM), erasable programmable read-only memory (Erasable Programmable Read Only Memory, EPROM), static random access memory (Static Random Access Memory, SRAM), read-only memory (Read-Only Memory, ROM), magnetic memory, flash memory, programmable read-only memory (Programmable Read-Only Memory, PROM).

When the communication device is implemented as a terminal, the processor and transceiver in the communication device involved in the embodiment of the present application can perform the steps performed by the terminal in any of the methods shown above, which will not be described again here.

In a possible implementation, when the communication device is implemented as a terminal,

When the communication device is implemented as a network device, the processor and transceiver in the communication device involved in the embodiment of the present application can perform the steps performed by the network device (access network device) in any of the methods shown above. , which will not be described again here.

In a possible implementation, when the communication device is implemented as a network device,

In an exemplary embodiment, a computer-readable storage medium is also provided, in which at least one instruction, at least a program, a code set or an instruction set is stored, and the at least one instruction, the At least a section of the program, the code set or the instruction set is loaded and executed by the processor to implement the hybrid automatic repeat request HARQ feedback method executed by the communication device provided by each of the above method embodiments.

In an exemplary embodiment, a chip is also provided. The chip includes programmable logic circuits and/or program instructions. When the chip is run on a communication device, it is used to enable the communication device to implement the above aspects. Hybrid automatic repeat request HARQ feedback method.

In an exemplary embodiment, a computer program product is also provided, which when run on a processor of a communication device causes the communication device to perform the hybrid automatic repeat request HARQ feedback method described in the above aspect.

Those of ordinary skill in the art can understand that all or part of the steps to implement the above embodiments can be completed by hardware, or can be completed by instructing relevant hardware through a program. The program can be stored in a computer-readable storage medium. The above-mentioned The storage media mentioned can be read-only memory, magnetic disks or optical disks, etc.

The above are only optional embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the protection of the present application. within the range.

Claims

A hybrid automatic repeat request HARQ feedback method, characterized in that the method is executed by a terminal, and the method includes:

The reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS is reported to the access network device according to the NACK-only feedback mode.
The method of claim 1, further comprising:

Receive feedback configuration information sent by the access network device, where the feedback configuration information indicates that the HARQ feedback mode of the SPS PDSCH of the MBS is the NACK-only feedback mode.
The method according to claim 1 or 2, characterized in that the received feedback includes a codebook formed by feedback information corresponding to the SPS PDSCH of the MBS;

Wherein, the feedback information corresponding to the SPS PDSCH of the MBS includes at least one of the following: multiple feedback information corresponding to multiple transmission blocks TB of the SPS PDSCH of one MBS, multiple feedback information corresponding to the SPS PDSCH of multiple MBS. .
The method according to claim 3, characterized in that the codebook includes a type 1 codebook and/or a type 2 codebook.
The method according to claim 4, wherein the codebook is a type 1 codebook;

The reporting of reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS to the access network device according to the NACK-only feedback mode includes:

Convert the HARQ feedback mode from the NACK-only feedback mode to the acknowledgment/negative acknowledgment ACK/NACK feedback mode;

The ACK/NACK feedback mode is used to report the reception feedback of the SPS PDSCH of the MBS to the access network device.
The method according to claim 4, characterized in that the codebook is a type 2 codebook;

The reporting of reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS to the access network device according to the NACK-only feedback mode includes:

Using NACK-only feedback mode to report the reception feedback of the SPS PDSCH of the MBS to the access network device;

or,

Convert the HARQ feedback mode from the NACK-only feedback mode to the ACK/NACK feedback mode; use the ACK/NACK feedback mode to report the reception feedback of the SPS PDSCH of the MBS to the access network device.
The method according to any one of claims 3 to 6, characterized in that the feedback information corresponding to the SPS PDSCH of the MBS includes a plurality of feedback information corresponding to the SPS PDSCH of multiple MBSs;

In the codebook, multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged according to the SPS index;

or,

In the codebook, the multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged according to the group-semi-persistent scheduling-radio network temporary identifier G-CS-RNTI;

or,

In the codebook, multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged in time sequence;

Wherein, the timing includes at least one of the receiving sequence of the SPS PDSCH of the MBS and the sending sequence of the SPS PDSCH of the MBS.
The method according to any one of claims 3 to 6, characterized in that the codebook includes feedback information corresponding to the SPS PDSCH of the unicast service and feedback information corresponding to the SPS PDSCH of the MBS.
The method according to claim 8, characterized in that:

The codebook includes a cascaded first sub-codebook and a second sub-codebook, the first sub-codebook is formed by feedback information corresponding to the SPS PDSCH of the unicast service; the second sub-codebook is formed by Feedback information corresponding to the SPS PDSCH of the MBS is formed.
The method according to claim 9, characterized in that the feedback information corresponding to the SPS PDSCH of the MBS includes a plurality of feedback information corresponding to the SPS PDSCH of multiple MBSs;

In the second sub-codebook, multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged according to the SPS index;

or,

In the second sub-codebook, the multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged according to the group-semi-persistent scheduling-radio network temporary identifier G-CS-RNTI;

or,

In the second sub-codebook, multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged in time sequence;

Wherein, the timing includes at least one of the receiving sequence of the SPS PDSCH of the MBS and the sending sequence of the SPS PDSCH of the MBS.
The method according to claim 8, characterized in that:

In the codebook, the feedback information corresponding to the SPS PDSCH of the unicast service and the feedback information corresponding to the SPS PDSCH of the MBS are arranged according to the transmission/reception timing of the PDSCH;

Or, in the codebook, the feedback information corresponding to the SPS PDSCH of the unicast service and the feedback information corresponding to the SPS PDSCH of the MBS are arranged according to the SPS index;

Wherein, the sending/receiving timing of the PDSCH includes at least one of the following: the sending/receiving timing of the SPS PDSCH of the unicast service, and the sending/receiving timing of the SPS PDSCH of the MBS.
The method according to any one of claims 8 to 11, characterized in that the SPS PDSCH of the unicast service adopts ACK/NACK feedback mode.
The method according to any one of claims 8 to 12, characterized in that the SPS PDSCH of the unicast service and the SPS PDSCH of the MBS correspond to the same uplink feedback resource, and the uplink feedback resource is used to report the reception feedback .
A hybrid automatic repeat request HARQ feedback method, characterized in that the method is executed by an access network device, and the method includes:

Receive feedback from the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS sent by the terminal according to the NACK-only feedback mode.
The method of claim 14, further comprising:

Send feedback configuration information to the terminal, where the feedback configuration information indicates that the HARQ feedback mode of the SPS PDSCH of the MBS is the NACK-only feedback mode.
The method according to claim 14 or 15, characterized in that the received feedback includes a codebook formed by feedback information corresponding to the SPS PDSCH of the MBS;

Wherein, the feedback information corresponding to the SPS PDSCH of the MBS includes at least one of the following: multiple feedback information corresponding to multiple transmission blocks TB of the SPS PDSCH of one MBS, multiple feedback information corresponding to the SPS PDSCH of multiple MBS. .
The method according to claim 16, characterized in that the codebook includes a type 1 codebook and/or a type 2 codebook.
The method according to claim 17, characterized in that the codebook is a type 1 codebook;

The ACK/NACK feedback mode is used in the reception feedback to feed back the SPS PDSCH of the MBS.
The method according to claim 17, characterized in that the codebook is a type 2 codebook;

The NACK-only feedback mode is used in the reception feedback to feed back the reception feedback of the SPS PDSCH of the MBS;

or,

In the reception feedback, the ACK/NACK feedback mode is used to feed back the reception feedback of the SPS PDSCH of the MBS.
The method according to any one of claims 16 to 19, characterized in that the feedback information corresponding to the SPS PDSCH of the MBS includes a plurality of feedback information corresponding to the SPS PDSCH of multiple MBSs;

In the codebook, multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged according to the SPS index;

or,

In the codebook, the multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged according to the group-semi-persistent scheduling-radio network temporary identifier G-CS-RNTI;

or,

In the codebook, multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged in time sequence;

Wherein, the timing includes at least one of the receiving sequence of the SPS PDSCH of the MBS and the sending sequence of the SPS PDSCH of the MBS.
The method according to any one of claims 16 to 19, characterized in that the codebook includes feedback information corresponding to the SPS PDSCH of the unicast service and feedback information corresponding to the SPS PDSCH of the MBS.
The method according to claim 21, characterized in that:

The codebook includes a cascaded first sub-codebook and a second sub-codebook, the first sub-codebook is formed by feedback information corresponding to the SPS PDSCH of the unicast service; the second sub-codebook is formed by Feedback information corresponding to the SPS PDSCH of the MBS is formed.
The method according to claim 22, characterized in that the feedback information corresponding to the SPS PDSCH of the MBS includes a plurality of feedback information corresponding to the SPS PDSCH of multiple MBSs;

In the second sub-codebook, multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged according to the SPS index;

or,

In the second sub-codebook, the multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged according to the group-semi-persistent scheduling-radio network temporary identifier G-CS-RNTI;

or,

In the second sub-codebook, multiple feedback information corresponding to the SPS PDSCHs of the multiple MBSs are arranged in time sequence;

Wherein, the timing includes at least one of the receiving sequence of the SPS PDSCH of the MBS and the sending sequence of the SPS PDSCH of the MBS.
The method according to claim 21, characterized in that:

In the codebook, the feedback information corresponding to the SPS PDSCH of the unicast service and the feedback information corresponding to the SPS PDSCH of the MBS are arranged according to the transmission/reception timing of the PDSCH;

Or, in the codebook, the feedback information corresponding to the SPS PDSCH of the unicast service and the feedback information corresponding to the SPS PDSCH of the MBS are arranged according to the SPS index;

Wherein, the sending/receiving timing of the PDSCH includes at least one of the following: the sending/receiving timing of the SPS PDSCH of the unicast service, and the sending/receiving timing of the SPS PDSCH of the MBS.
The method according to any one of claims 21 to 24, characterized in that the SPS PDSCH of the unicast service adopts ACK/NACK feedback mode.
The method according to any one of claims 21 to 25, characterized in that the SPS PDSCH of the unicast service and the SPS PDSCH of the MBS correspond to the same uplink feedback resource, and the uplink feedback resource is used to report the reception feedback .
A hybrid automatic repeat request HARQ feedback device, characterized in that the device includes:

The first sending module is configured to report the reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS to the access network device according to the NACK-only feedback mode.
A hybrid automatic repeat request HARQ feedback device, characterized in that the device includes:

The second receiving module is configured to receive reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS sent by the terminal according to the NACK-only feedback mode.
A terminal, characterized in that the terminal includes: a processor and a transceiver connected to the processor; wherein,

The transceiver is configured to report the reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS to the access network device according to the NACK-only feedback mode.
A network device, characterized in that the network device includes: a processor and a transceiver connected to the processor; wherein,

The transceiver is configured to receive reception feedback of the semi-persistent scheduling SPS physical downlink shared channel PDSCH of the multicast broadcast service MBS sent by the terminal according to the NACK-only feedback mode.
A terminal, characterized in that the terminal includes: a processor and a memory, the memory stores at least one instruction, at least one program, a code set or an instruction set, the at least one instruction, the at least one program, The code set or instruction set is loaded and executed by the processor to implement the hybrid automatic repeat request HARQ feedback method as described in any one of claims 1 to 13.
A network device, characterized in that the network device includes: a processor and a memory, the memory stores at least one instruction, at least a program, a code set or an instruction set, the at least one instruction, the at least a The program, the code set or the instruction set are loaded and executed by the processor to implement the hybrid automatic repeat request HARQ feedback method as described in any one of claims 14 to 26.
A computer-readable storage medium, characterized in that executable instructions are stored in the readable storage medium, and the executable instructions are loaded and executed by a processor to enable the communication device to implement any one of claims 1 to 26. The hybrid automatic repeat request HARQ feedback method described above.
A chip, characterized in that the chip includes a programmable logic circuit or program, and the communication device installed with the chip is used to implement the hybrid automatic repeat request HARQ feedback method as described in any one of claims 1 to 26.