Background
Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These wireless communication systems are capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (fourth generation, 4G) systems such as long term evolution (long term evolution, LTE) systems and fifth generation (5G) systems, which may be referred to as New Radio (NR) systems. These systems may employ techniques such as code division multiple access (code division multiple access, CDMA), time division multiple access (time division multiple access, TDMA), frequency division multiple access (frequency division multiple access, FDMA), orthogonal frequency division multiple access (orthogonal frequency division multiple access, OFDMA), or discrete fourier transform spread OFDM (discrete Fourier transform-spread-OFDM, DFT-S-OFDM). A wireless multiple-access communication system may include multiple base stations or network access nodes, each supporting communication for multiple communication devices, which may be otherwise referred to as User Equipment (UEs). The wireless communication network may include base stations capable of supporting communication for the UE. The UE may communicate with the base station via Downlink (DL) and Uplink (UL). DL refers to the communication link from a base station to a UE, and UL refers to the communication link from a UE to a base station.
In third generation partnership project (3rd generation partnership project,3GPP) cellular networks, broadcast and multicast services may be transmitted via a transmission service known as multimedia broadcast/multicast service (multimedia broadcast/multicast service, MBMS). A broadcast multicast service center (broadcast multicast service center, BM-SC) server is responsible for disseminating media content to a group of subscribers. When the UE moves out of network coverage, the UE may not be able to use MBMS because the uplink and downlink connections to the BM-SC server are no longer available. MBMS is a point-to-multipoint (PTM) interface specification intended to provide efficient transmission of broadcast and multicast services within a 3GPP cellular network. Examples of MBMS interface specifications include those described in the universal mobile telecommunications system (universal mobile telecommunication system, UMTS) and long term evolution (long term evolution, LTE) communication specifications. For broadcast transmissions across multiple cells, the specification defines transmissions on a single frequency network configuration. Contemplated applications include mobile television, news, radio, file transfer, emergency alerts, and the like. When passing through an MBMS broadcast service, all cells within a multimedia broadcast/multicast service single frequency network (multimedia broadcast/multicast service single frequency network, MBSFN) area transmit the same MBMS service.
Users access these services and acquire MBMS content through wireless communication devices such as cellular telephones, tablet computers, notebook computers, and other devices having wireless transceivers that communicate with base stations within the communication system. A base station provides wireless services for wireless communication devices, sometimes referred to as mobile devices or UEs within a cell. A user may access at least some multimedia services through a UE using a point-to-point (PTP) connection or PTM transmission. In 3GPP systems, PTP services can be provided using unicast techniques, and PTM transmissions can be provided using MBMS communications, transmitted over MBSFN or single cell point-to-multipoint (single cell point to multipoint, SC-PTM) communications. In a system operating in accordance with a revision of the 3GPP long term evolution (long term evolution, LTE) communication specification, MBMS is provided using eMBMS. Accordingly, a unicast service, MBSFN or SC-PTM may be used in an LTE system to provide MBMS services.
In radio access network (radio access network, RAN) conference #88-e held 29 in 6, 2020 to 3 in 7, 2020, a new work item is approved aimed at supporting a multicast/broadcast service (MBS) RAN in 5G. The purpose of this work item is to provide RAN support to enable generic MBS services over 5GS, support different MBS services such as public safety and critical tasks, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, wireless software delivery, group communication and internet of things applications. One of the main goals of the RAN work item is to study and prescribe support for basic mobility and service continuity for a 5G New Radio (NR) multicast/broadcast service (multicast/broadcast services, MBS).
One of the main objectives of the workitem description (work item description, WID) is to specify a group scheduling mechanism to allow UEs to receive broadcast/multicast services RAN1, RAN 2. The goal includes specifying the necessary enhancement functions required to achieve simultaneous operation with unicast reception. One of the main goals of WIDs is to specify the required changes to improve the reliability of broadcast/multicast services, e.g. via Uplink (UL) feedback. The reliability level should be based on the requirements of the provided application/service RAN1, RAN 2.
The focus of the current company is to reuse the same HARQ design used for synchronous multicast (PTP/PTM) and unicast (PTP) service transmission and retransmission as NR unicast. However, due to the fact in NR, both multicast (PTP/PTM) and unicast (PTP) initial transmissions may form a high data service. Thus, the size of the transport blocks generated by the configured HARQ processes for (PTM and PTM) transmission will become very large. Such a huge Transport Block (TB) is retransmitted once again in the downlink resource whenever the UE fails a cyclic redundancy check (cyclic redundancy check, CRC) check for a specific TB, which will result in lower spectrum and downlink transmission resource efficiency. One way to increase the resource efficiency is to retransmit only the portion of the transport block that the UE fails to decode. However, this principle requires dividing/splitting the transport block into smaller blocks and the gNB provides multi-bit HARQ related information on the downlink channel and the UE provides multi-bit HARQ feedback on the uplink channel, which may increase the overhead.
Accordingly, there is a need for a User Equipment (UE), a base station, and a wireless communication method that can solve the problems in the prior art, reduce the HARQ feedback overhead of the UE, reduce the complexity of the UE, improve the network efficiency, reduce the downlink control information, and/or provide good and/or reliable communication performance.
Detailed Description
The technical matters, structural features, achieved objects and effects of the embodiments of the present invention will be described in detail with reference to the accompanying drawings. In particular, the terminology used in the embodiments of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.
In RAN conference #88-e held between 29 and 3 months of year 6 and 7 in 2020, a new work item WID (RP-201308) was approved, with the goal of supporting a RAN for Multicast/broadcast services (MBS). The purpose of the WID is to provide support in the RAN for target a of SA2 study item SID (SP-190726), which is related to enabling generic MBS services on 5GS to support different MBS services, such as public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, wireless software delivery, group communication and internet of things applications. One of the main goals of WIDs includes: 1. a group scheduling mechanism is specified to allow the UE to receive broadcast/multicast services RAN1, RAN 2. The goal includes specifying the necessary enhancement functions required to achieve simultaneous operation with unicast reception. 2. The required modifications are specified to improve the reliability of the broadcast/multicast service, e.g. by UL feedback. The reliability level should be based on the requirements of the provided application/service RAN1, RAN 2.
To achieve the first objective, an agreement has been made on the RAN1 conference supporting simultaneous transmission and reception of unicast services by PTP transmission dynamic or semi-persistent scheduling on a physical downlink shared channel (physical downlink shared channel, PDSCH) and multicast/broadcast services by PTP transmission on PDSCH or by PTM dynamic or semi-persistent scheduling on one time slot through group common PDSCH transmission. In addition, the following transmission schemes are agreed to support unicast (PTP) and MBS (PTP/PTM) transmission.
PTP transmission: for rrc_connected UEs, a UE-specific PDCCH with a cyclic redundancy check (cyclic redundancy check, CRC) scrambled by a UE-specific radio network temporary identifier (e.g., C-RNTI) is used to schedule a UE-specific PDSCH scrambled using the same UE-specific RNTI.
PTM transmission scheme 1: for rrc_connected UEs in the same MBS group, a group common PDSCH scrambled by the same group common RNTI is scheduled using a group common PDCCH with a CRC scrambled by the group common RNTI. This scheme may also be referred to as a group scheduling scheme based on a group common PDCCH.
PTM transmission scheme 2: for rrc_connected UEs in the same MBS group, a UE-specific PDCCH with a CRC scrambled by a UE-specific RNTI (e.g., C-RNTI) is used to schedule a group common PDSCH scrambled with a group common RNTI. This scheme may also be referred to as a group scheduling scheme based on UE-specific PDCCH.
As regards the second objective, i.e. reliability of the multicast/broadcast service, in RAN1 it has been agreed to support acknowledgement and non-Acknowledgement (ACK) based and/or NACK only based hybrid automatic repeat request (hybrid automatic repeat request, HARQ) for semi-persistent scheduling (semi-persistently scheduled, SPS) or dynamically scheduled PTM transmission and retransmission and to support ACK/NACK SPS/dynamically scheduled PTP transmission and retransmission. However, the reliability discussion of RAN2 is still in an early stage; it is therefore not clear how HARQ or transmission and retransmission processes can be configured/designed in this way, enabling dynamic scheduling of simultaneous SPS and/or unicast (PTP) and multicast/broadcast (PTM) within a time slot. To achieve this, the configuration of the HARQ process should allow the UE to multiplex PTP and PTM transmissions of at least one MAC layer Transport Block (TB), support only one TB per slot, and allow the UE to multiplex multiple PTP and PTP TBs within one slot, each capable of supporting multiple TBs. Although some companies offer some views of SPS and HARQ process configurations for MBS during the latest RAN2 conferences [ R2-2106283, R2-2104756, R2-2105287, R2-2105834, R2-2106241, R2-2106283], it is not yet concluded that the above problems have been achieved in RAN 2.
To overcome the above problems, some embodiments of the present application provide an efficient and low-overhead HARQ transmission and retransmission method for dynamic and/or semi-persistent scheduling of simultaneous MBS (PTP/PTM) and unicast (PTP) scheduling of UEs in a slot. The exemplary method avoids downlink transmission defects by employing only partial retransmissions of the PTP or PTM portion of the transport block instead of retransmitting the entire transport block, and by utilizing a one-bit HARQ indicator in the downlink and a two-bit/two-bit reconfigurable ACK/NACK uplink feedback in the downlink. In this exemplary method, the gNB configures different/separate HARQ processes for PTP and PTM data, combines/maps/multiplexes data from the HARQ processes configured for PTP/PTM into DL allocations, and indicates HARQ control information for PTP/PTM combinations and HARQ process IDs to one or more UEs. Upon receiving the HARQ control information and DL allocation from the gNB, the UE configures a single HARQ process to receive PTP and PTM DL data within the allocation, decodes and checks the PTP and PTM data (TB) CRCs contained in the DL allocation to determine the erroneous portion (possibly the PTP portion, the PTM portion, or the PTP and PTM portions) of the DL allocation. And then, the UE configures PTP/PTMACK/NACK feedback bits and sends the feedback bits to the gNB through an uplink. Then, the gNB determines whether PTP or PTM on the gNB and the gNB need retransmission according to the received ACK/NACK feedback bit; if so, the gNB retransmits the DL allocation portion indicated by the feedback bit to the UE. Finally, the UE receives a retransmission portion of the DL assignment of the previous uplink feedback previously sent to the gNB.
Some embodiments of the present application provide a new semi-persistent scheduling mechanism for scheduling initial simultaneous transmissions/retransmissions of multicast broadcast and unicast services (MBS) over 5G point-to-point (PTP) and point-to-multipoint (PTM) systems. The main advantages of the new exemplary method compared to the prior art include:
from the UE side:
1. the new exemplary method helps reduce UE HARQ feedback overhead because only one bit of feedback is used to acknowledge/disambiguate one or more transport blocks or CBGs configured for unicast (PTP) and multicast/broadcast (PTM/PTM) data units, rather than transmitting multiple feedback bits for each TB/CBG individually within a large transport block.
The new exemplary method allows the UE to be configured with only one HARQ process to correspond to two independent HARQ processes at the gNB (for unicast PTM and PTP). This helps to reduce UE complexity.
From the network side:
the new exemplary method facilitates improving network efficiency and reducing downlink control information by reducing the size of HARQ related information transmitted on downlink scheduling assignments.
Fig. 1 illustrates that in some embodiments, one or more User Equipments (UEs) 10 and base stations (e.g., gnbs) 20 for communicating in a communication network system 30 are provided in accordance with embodiments of the present application. The communication network system 30 includes one or more UEs 10 and a base station 20. One or more UEs 10 may include a memory 12, a transceiver 13, and a processor 11 coupled to the memory 12 and the transceiver 13. The base station 20 may include a memory 22, a transceiver 23, and a processor 21 coupled to the memory 22 and the transceiver 23. The processor 11 or 21 may be configured to implement the proposed functions, processes and/or methods described in the present specification. The radio interface protocol layer may be implemented in the processor 11 or 21. The memory 12 or 22 is operatively coupled to the processor 11 or 21 and stores various information to operate the processor 11 or 21. The transceiver 13 or 23 is operatively coupled to the processor 11 or 21, and the transceiver 13 or 23 transmits and/or receives radio signals.
The processor 11 or 21 may include an Application Specific Integrated Circuit (ASIC), other chipset, logic circuit, and/or data processing device. Memory 12 or 22 may include Read Only Memory (ROM), random Access Memory (RAM), flash memory, memory cards, storage media, and/or other storage devices. The transceiver 13 or 23 may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. These modules may be stored in the memory 12 or 22 and executed by the processor 11 or 21. The memory 12 or 22 may be implemented within the processor 11 or 21 or external to the processor 11 or 21, in which case they can be communicatively coupled to the processor 11 or 21 via various means as is known in the art.
In some embodiments, transceiver 13 is configured to receive Downlink (DL) assignments, including point-to-point (PTP)/point-to-multipoint (PTM) data and PTP/PTM hybrid automatic repeat request (HARQ) information, from base station 20, the processor is configured to configure a single HARQ process to receive the DL assignments including PTP/PTM data, and the processor is configured to decode Cyclic Redundancy Check (CRC) of PTP/PTM Transport Blocks (TBs)/Code Block Groups (CBGs) within the DL assignments. This may solve the problems in the prior art, reduce UE HARQ feedback overhead, reduce UE complexity, improve network efficiency, reduce downlink control information, and/or provide good and/or reliable communication performance.
In some embodiments, processor 21 is configured to configure a hybrid automatic repeat request (HARQ) process for point-to-point (PTP)/point-to-multipoint (PTM) data to UE 10, processor 21 is configured to activate a Downlink (DL) allocation comprising PTP/PTM data and PTP/PTM HARQ information, and transceiver 23 is configured to transmit the DL allocation comprising PTP/PTM data and PTP/PTM HARQ information to the UE. This may solve the problems in the prior art, reduce UE HARQ feedback overhead, reduce UE complexity, improve network efficiency, reduce downlink control information, and/or provide good and/or reliable communication performance.
Fig. 2 illustrates a wireless communication method 200 for unicast and/or multicast/broadcast service (MBS) transmission and retransmission performed by a User Equipment (UE) according to an embodiment of the present application. In some embodiments, the method 200 includes: step 202, receiving a Downlink (DL) allocation including point-to-point (PTP)/point-to-multipoint (PTM) data and PTP/PTM hybrid automatic repeat request (HARQ) information from a base station, step 204, configuring a single HARQ process to receive the DL allocation including the PTP/PTM data, step 206, decoding a Cyclic Redundancy Check (CRC) of a PTP/PTM Transport Block (TB)/Code Block Group (CBG) within the DL allocation, step 208, configuring Acknowledgement (ACK)/non-acknowledgement (NACK) feedback code bits, transmitting a PTP/PTM uplink feedback code to the base station, step 210, receiving a DL allocation for retransmission of a previously transmitted PTP/PTM ACK/NACK uplink feedback from the base station. This may solve the problems in the prior art, reduce UE HARQ feedback overhead, reduce UE complexity, improve network efficiency, reduce downlink control information, and/or provide good and/or reliable communication performance.
Fig. 3 illustrates a wireless communication method 300 for unicast and/or multicast/broadcast service (MBS) transmissions and retransmissions performed by a base station according to an embodiment of the present application. In some embodiments, the method 300 includes: step 302, configuring a hybrid automatic repeat request (HARQ) process of point-to-point (PTP)/point-to-multipoint (PTM) data to a User Equipment (UE), step 304, activating Downlink (DL) allocation including PTP/PTM data and PTP/PTM HARQ information, step 306, and transmitting DL allocation including PTP/PTM data and PTP/PTM HARQ information to the UE; step 308, reconfigure/retransmit based on the received PTP/PTM feedback indication from the UE. This may solve the problems in the prior art, reduce UE HARQ feedback overhead, reduce UE complexity, improve network efficiency, reduce downlink control information, and/or provide good and/or reliable communication performance.
In some embodiments, the wireless communication method further comprises configuring Acknowledgement (ACK)/non-acknowledgement (NACK) feedback code bits, transmitting PTP/PTM uplink feedback codes to the base station, and receiving DL allocations from the base station for retransmissions of previous PTP/PTM ACK/NACK uplink feedback. In some embodiments, an Acknowledgement (ACK)/non-acknowledgement (NACK) feedback code bit tradeoff is configured. In some embodiments, acknowledgement (ACK)/non-acknowledgement (NACK) feedback code bits are configured to trade-off PTP/PTM ACK code bits, indicating to the gNB that the initial PTM transmission was successfully received and that the initial PTP transmission was not received or received with errors. In some embodiments, acknowledgement (ACK)/non-acknowledgement (NACK) feedback code bits are configured to trade-off PTP/PTM ACK code bits, indicating to the gNB that the initial PTP transmission was successfully received and that the initial PTM transmission was not received or received with errors. In some embodiments, an Acknowledgement (ACK)/non-acknowledgement (NACK) feedback code bit tradeoff PTP/PTM ACK code bit is configured, indicating to the gNB that both PTP and PTM initial transmissions were successfully received by the UE. In some embodiments, the configuration Acknowledgement (ACK)/non-acknowledgement (NACK) feedback code bits are compromised by PTP/PTM ACK code bits indicating to the gNB that the UE did not successfully receive PTP and PTM initial transmissions. In some embodiments, the configuration Acknowledgement (ACK)/non-acknowledgement (NACK) feedback code bits are compromised to two/two bits.
In some embodiments, the wireless communication method further comprises configuring the single HARQ process to receive a DL allocation comprising PTP/PTM data in the time slot. In some embodiments, the wireless communication method further comprises receiving a DL allocation from the base station for retransmission of previous PTP/ptm ack/NACK uplink feedback. In some embodiments, the one or more HARQ processes are configured to correspond to an upper layer Radio Access Network (RAN) protocol data unit, and the upper layer RAN protocol data unit includes PTP/PTM Medium Access Control (MAC) Service Data Unit (SDU) and/or PTP/PTM Radio Link Control (RLC) segments. In some embodiments, PTP HARQ processes correspond to unicast and/or multicast (PTP) upper layer RAN protocol data units, and/or PTM HARQ processes correspond to multicast and/or broadcast (PTM) upper layer RAN protocol data units. In some embodiments, the PTP HARQ process is configured such that retransmission of the PTP initial transmission may be made by PTP transmission only, and/or the PTM HARQ process is configured such that PTM retransmission may be made by PTP transmission or PTM transmission. In some embodiments, both PTP HARQ processes or PTM HARQ processes may be configured to correspond to dynamic scheduling or semi-persistent scheduling of PTP or PTM protocol data units on PTP/PTM HARQ downlink transmission resources.
In some embodiments, for a PTP HARQ process, one or more configured scheduling RNTIs (CS-RNTIs) or C-RNTIs may be configured to semi-permanently or dynamically activate/deactivate and schedule PTP HARQ downlink transmission resources on a UE-specific physical downlink shared channel. In some embodiments, for a PTM HARQ process, one or more group common cs_rnti (G-CS-RNTI) or G-RNTI may be configured to semi-permanently or dynamically activate/deactivate and schedule PTPM HARQ downlink transmission resources on a group of common physical downlink shared channels. In some embodiments, the initial transmission of the DL allocation, the retransmission of the DL allocation, and the underlying downlink transmission resources of the PTP or PTM HARQ process are configured by a CBG method or a TBs method. In some embodiments, for the retransmission of CBG-based PTP/PM initial transmissions and DL allocations, only one transport block is configured for the UE per slot. In some embodiments, for CBG-based PTP/PM initial transmission and retransmission of DL allocations, the base station configures different HARQ processes, including one process for PTP and another process for PTM RAN upper layer protocol data units.
In some embodiments, for retransmission of CBG-based PTP/PM initial transmissions and DL allocations, a TB is divided into only two equal parts of a TB or CBG set, each part being scrambled by a different/separate (CRC) bit associated with a specific RNTI, including CS-RNTI/C-RNTI for PTP or RNTI for a G-CS-RNTI/G-base station for PTM. In some embodiments, for a CBG-based PTP/PM initial transmission and retransmission of DL allocations, for simultaneous PTP and PTM HARQ process operation, the first half of the TB is allocated to a protocol data unit, CB or CBG generated from the PTP HARQ process, and the second half of the TB is allocated to a protocol data unit or CBG generated from the PTP HARQ process. In some embodiments, the number of CBGs allocated for PTP and PTM processes within one TB may be equal. In some embodiments, TBs generated by different PTP and PTM processes are mapped to different CBGs within one TB according to the process type of the generating TB. In some embodiments, after mapping the PTP/PTM data into two portions of TBs, a single bit PTP/PTM HARQ information indicator for each TB is generated by the UE, and the UE receives the single bit PTP/PTM HARQ information indicator for each TB from the base station to help the UE identify that a given DL allocation contains simultaneous PTP and PTM TBs so that the UE can activate and use the PTP/PTM ack/NACK configuration table. In some embodiments, the UE receives a single bit PTP/PTM HARQ information indicator from the base station and one HARQ process ID including an identification of the PTP or PTM HARQ process informing the UE about the configuration of PTP and PTM for a given TB/slot or a given specific/configured HARQ of the downlink allocation.
In some embodiments, for a CBG based PTP/PM initial transmission and retransmission of DL allocations, when a UE sends PTP/PTM ack/NACK uplink feedback to a base station indicating NACK feedback code bit 01, to indicate that the UE fails to decode the PTP portion of the DL allocation but the UE has successfully decoded the PTM portion, the UE receives a retransmission from the base station that includes only protocol data units, which retransmission is mapped into a CBG index configured for PTP of other code bits that the base station can react to. In some embodiments, for retransmission of TB-based PTP/PM initial transmission and DL allocations, multiple transport blocks are configured for each slot of the UE. In some embodiments, for TB-based PTP/PM initial transmission and retransmission of DL allocations, the base station configures different HARQ processes, including one process for PTP and another process for PTM RAN upper layer protocol data units. In some embodiments, for the retransmission of TB-based PTP/PM initial transmission and DL allocation, the time slots configured for PTP and PTM HARQ processes are divided into only two equal parts, each scrambled by a different/separate (CRC) bit associated with a specific RNTI containing CS-RNTI/C-RNTI for PTP or G-CS-RNTI/G-RNTI for PTM SPS/base station dynamic scheduling. In some embodiments, for the retransmission of TB-based PTP/PM initial transmissions and DL allocations, the time slots for PTP and PTM HARQ processes are configured by the base station in such a way: the first half of the time slot is allocated to a protocol data unit or TB generated from the PTP HARQ process and the second half of the time slot is allocated to a protocol data unit or TB generated from the PTP HARQ process. The time slot is allocated to a protocol data unit or TB generated from PTM HARQ. In some embodiments, the number of TBs allocated for PTP and PTM procedures within one slot may be equal. In some embodiments, when PTP/PTM data or TBs are mapped to two portions of a slot, the base station generates/configures a single bit PTP/PTM HARQ information indicator for each slot to provide an indication to the UE, and the UE provides code bit feedback to the base station in response, the interaction between the UE and the base station being slot-based, including multiple TBs. In some embodiments, a single bit PTP/PTM HARQ information indicator indicates to the UE that a PTP/PTM based HARQ process is configured and the first half of the TB or slot is configured for PTP, or that PTP/PTM is configured and the first half of the TB or slot is configured for PTM or that PTP/PTM is not configured.
Multicast/broadcast services (MBS) are expected to cover a wide variety of 5G applications and services including public safety, mission critical, V2X, transparent IPv4/IPv6 multicast delivery, IPTV, delivering software wirelessly to group communication and internet of things applications. As part of the 5G NR R17 standardization, a new work item WID [ RP-201308] was approved, targeting RAN support for (MBS). One of the main objectives of this work project is to study and specify a group scheduling mechanism from the perspective of RAN1 and RAN2 standardization to allow UEs to receive broadcast/multicast services. This objective includes: 1) Specifying the necessary enhancement functions required to operate MBS concurrently with unicast reception, and 2) specifying the changes required to improve the reliability of broadcast/multicast service reception. To achieve the first objective, RAN1 conferences have agreed to support both dynamic or semi-persistent scheduled unicast services with PTP transmission on a Physical Downlink Shared Channel (PDSCH) and multicast/broadcast services with dynamic or semi-persistent scheduling simultaneously transmitting and receiving PTP transmission on a PDSCH or PTM transmission on a group common PDSCH on one time slot. In addition, the following transmission schemes are agreed to support unicast (PTP) and MBS (PTP/PTM) transmission.
PTP transmission: for rrc_connected UEs, a UE-specific PDCCH and a Cyclic Redundancy Check (CRC) scrambled by a UE-specific radio network temporary identifier (e.g., C-RNTI) are used to schedule UE-specific PDSCH RNTI using the same UE-specific scrambling.
PTM transmission scheme 1: for rrc_connected UEs in the same MBS group, a group common PDCCH with a group common RNTI-scrambled CRC is used to schedule a group common PDSCH scrambled using the same group common RNTI. This scheme may also be referred to as a group scheduling scheme based on a group common PDCCH.
PTM transmission scheme 2: for rrc_connected UEs in the same MBS group, a UE-specific PDCCH with a CRC scrambled by a UE-specific RNTI (e.g., C-RNTI) is used to schedule a group common PDSCH scrambled with a group common RNTI. This scheme may also be referred to as a group scheduling scheme based on UE-specific PDCCH.
As for the second objective (i.e. reliability of the multicast/broadcast service),
in RAN1, it has been agreed to support acknowledgement and non-Acknowledgement (ACK) based and/or NACK only hybrid automatic repeat request (HARQ) for SPS/dynamically scheduled PTM transmissions and retransmissions, and PTP transmissions and retransmissions based on ACK/NACK reservations for SPS/dynamic. However, the discussion of reliability by RAN2 is still in an early stage; it is therefore not clear how HARQ or transmission and retransmission processes can be configured/designed in this way, enabling dynamic scheduling of simultaneous SPS and/or unicast (PTP) and multicast/broadcast (PTM) within a time slot. To achieve this, the configuration of the HARQ process should allow the UE to multiplex PTP and PTM transmissions of at least one MAC layer Transport Block (TB), support only one TB per slot, and allow the UE to multiplex multiple PTP and PTP TBs within one slot, each capable of supporting multiple TBs. The simplest design approach is to consider reusing the same HARQ design as NR unicast for simultaneous multicast (PTP/PTM) and unicast (PTP) service transmission and retransmission. However, due to the fact that in NR both multicast (PTP/PTM) and unicast (PTP) transmissions can be used for high data services. The size of the transport block generated by the HARQ process will be very large. Such a huge transport block is retransmitted in the downlink again and again each time the CRC check of a specific TB at the UE fails, resulting in low spectrum and downlink transmission efficiency.
To overcome this problem, efficiency is improved and delay is improved, a concept called Code Block Group (CBG) based transmission is introduced in 5G NR, in which large transmission blocks are essentially divided into smaller units called Code Blocks (CBs) and smaller units called Code Blocks (CBs). The code blocks are further divided into Code Block Groups (CBGs), each of which may be scrambled using different (CRC) bits. Fig. 4 shows an example of retransmission of a single codebook set according to an embodiment of the present application. Thus, when a particular code block fails, only the CBG, CRC bit check, of the code block fails; thus, only the CBG will be retransmitted, not the entire transport block ad shown in fig. 4.
As shown in the figure. Fig. 5 shows an example of bit sizes for CBG-based HARQ information indicators and HARQ feedback according to an embodiment of the present application. One of the main drawbacks of this exemplary procedure (i.e. CBG based retransmission) is that it adds HARQ indication and feedback overhead, as in the case of a single TB, one bit per transport block is needed for HARQ indication and ACK/NACK feedback, but now the gNB needs to send multiple bit indications (i.e. one bit per CBG) and the UE also needs to provide multi-bit ACK/NACK, as shown in fig. 5. This will increase uplink and downlink control signaling overhead.
Fig. 6 illustrates an example of a wireless communication method for unicast and/or MBS performed by a base station and one or more UEs according to an embodiment of the present application. Fig. 7 illustrates an example of a wireless communication method performed by a base station for unicast and/or MBS according to an embodiment of the present application. Fig. 8 illustrates an example of a wireless communication method performed by a user equipment for unicast and/or MBS according to an embodiment of the present application. Fig. 9 shows an example of PTP and PTM HARQ process configurations at a gNB according to embodiments of the application. Referring to fig. 6, 7, 8, and 9, in some embodiments, to overcome the above-described problems, the exemplary method provides an efficient and low-overhead HARQ transmission and retransmission method for dynamic and/or semi-persistent scheduling of simultaneous MBS (PTP/PTM) and unicast (PTP) scheduling of UEs in a slot. The exemplary method avoids downlink transmission defects by employing only partial retransmissions of the PTP or PTM portion of the transport block instead of retransmitting the entire transport block, and by utilizing a one-bit HARQ indicator in the downlink and a two-bit/two-bit reconfigurable ACK/NACK uplink feedback in the downlink. In this exemplary method, the gNB configures different/separate HARQ processes for PTP and PTM data, combines/maps/multiplexes data from the HARQ processes configured for PTP/PTM into the DL allocation, and indicates HARQ control information regarding the PTP/PTM combination and the HARQ process ID (identification of the PTP or PTM HARQ processes) for one or more UEs. Upon receiving the HARQ control information and DL assignment from the gNB, the UE configures a single HARQ process to receive PTP and PTM DL data within the assignment, decodes and checks the CRCs of the PTP and PTM data contained in the DL assignment to determine an erroneous portion (which may be a PTP portion, a PTM portion, or a PTP and PTM portion) of the DL assignment. And then, the UE configures PTP/PTMACK/NACK feedback bits and sends the feedback bits to the gNB through an uplink. Then, the gNB determines whether PTP or PTM or both require retransmission according to the received ACK/NACK feedback bit; if so, the gNB retransmits the DL allocation portion indicated by the feedback bit to the UE. Finally, the UE receives a retransmission portion of the DL assignment of the previous uplink feedback previously sent to the gNB.
In some embodiments, one or more HARQ processes/entities are configured to correspond to upper layer RAN protocol data units such as PTP/PTM MAC service data unit SDUs and/or PTP/PTM RLC segments. PTP HARQ processes correspond to unicast and/or multicast (PTP) upper layer RAN protocol data units and PTM HARQ processes correspond to multicast and/or broadcast (PTM) upper layer RAN protocol data units. The PTP HARQ process is configured such that retransmissions of PTP initial transmissions may pass through a PTP only transmission scheme, and the HARQ process is configured such that retransmissions of PTM initial transmissions may pass through a PTP or PTM transmission scheme. Both PTP or PTM HARQ processes may be configured to correspond to dynamic or semi-persistent scheduling of PTP or PTM protocol data units on PTP/PTM HARQ downlink transmission resources. For a PTP HARQ process, one or more CS-RNTI/C-RNTI may be configured to dynamically or semi-permanently activate/deactivate and schedule PTP HARQ downlink transmission resources on a UE-specific physical downlink shared channel. For a PTM HARQ process, one or more G-CS-RNTI/G-RNTI may be configured to dynamically or semi-permanently activate/deactivate and schedule PTPM HARQ downlink transmission resources on a group common physical downlink shared channel. The initial transmission and retransmission of PTP or PTM HARQ processes and the underlying downlink transmission resources are configured by a block coded group (CBG) method as described in some embodiments or by a Transport Block (TB) method as described in some embodiments.
PTP/PM initial and retransmission based on code block group:
fig. 10 shows an example of CBG-based PTP/PM initial transmission and retransmission according to an embodiment of the present application. Fig. 10 shows that in some embodiments, part a provides for the combining or multiplexing of HARQ PTP and PTM data in a TB and part b provides for providing HARQ indication information bits generated per TB. In some embodiments, the exemplary configuration assumes that only one transport block is configured for each slot of the UE. In this type of configuration, the gNB configures different HARQ processes (e.g., one process for PTP and another process for PTM RAN upper layer protocol data unit). To avoid mapping protocol data units (e.g., code blocks) generated by configured PTP and PTM HARQ processes to larger protocol transport blocks (which may reduce downlink transmission efficiency) and prevent higher control signaling overhead, the gNB may divide the Transport Block (TB) into only two equal parts or Code Block Group (CBG) regions/sets, each region/set being scrambled by different/separate (CRC) bits associated with a particular RNTI (e.g., CS-RNTI/C-RNTI for PTP) or G-CS-RNTI/G-RNTI (for PTM). Currently in NR of unicast transmission, one transport block can be divided into 2, 4, 6 or 8 CBGs. For simultaneous PTP and PTM HARQ process operation, half of the CBGs (i.e., 1, 2, 3, 4) may be allocated to protocol data units generated from the PTP HARQ process, and the other half may be allocated to protocol data units or CB sets generated from the PTM HARQ process (i.e., the number of CBGs allocated for the PTP and PTM processes within the TB may be equal, as shown in part a of fig. 10). From the figure we can note that CBs generated by different PTP and PTM processes are mapped to different CBGs within the TB according to the process type that generated them. For example, a set of transport blocks indexed CB0, CB1, and CB2 are mapped to the same region of the TB (i.e., CBG 0); while CB0, CB1 and CB2 are mapped to other CBG areas of the TB (i.e., CBG 1). In this way, the gNB knows the indices (i.e., CBG 0 and CBG 1) and HARQ process IDs that the PTP and PTM protocol data units map into within the TB. After mapping PTP and PTM data or CBs to two parts of a TB, the gNB may generate a single bit PTP/PTM HARQ information indicator for each TB (part b of fig. 10, table 1) and provide it to the UE to assist the UE in identifying that a given DL allocation contains both PTP and PTM TBs so that it can activate and use the PTP/PTM ACK/NACK configuration table (table 2) instead of the conventional unicast ACK/NACK configuration. The gNB then sends a single bit PTP/PTM HARQ information indicator along with a HARQ process ID (PTP or PTM) to the UE to inform the UE about the HARQ configuration given the particular PTP and PTM configuration and given TB/slot or downlink allocation.
From the UE side, only a single HARQ process needs to be configured to receive the configured PTP/PTM DL allocation, decode the CRCs of the PTP and PTM CGBs configured within the DL allocation, in order to send the appropriate ACK/NACK uplink feedback back to the gNB. For example, when the gNB receives feedback (e.g., indicates NACK feedback code bit [01 ]), it will be appreciated that the UE fails to decode the PTP portion of the initial DL allocation, but has successfully decoded the PTM portion; therefore, only the protocol data units mapped to CBG index configured for PTP will be retransmitted, the gNB will react as shown in table 2.
Initial transmission and retransmission based on transport blocks:
fig. 11 shows an example of TB-based PTP/PM initial transmission and retransmission according to an embodiment of the present application. Fig. 11 shows that in some embodiments, part a provides a combination or multiplexing of HARQ PTP and PTM transport block data in a slot, and part b provides HARQ indication information bits generated per slot. This exemplary configuration assumes that multiple transport blocks are configured for each slot of the UE (in NR, the UE may typically support up to 2, 4 and/or 7 different unicast transport blocks per slot). In this type of configuration, the gNB may configure different HARQ processes (e.g., one process for PTP and another process for PTM RAN upper layer protocol data unit). The time slots configured for PTP and PTM HARQ processes may then be divided into two parts, each part being scrambled by a different/separate Cyclic Redundancy Check (CRC) bit associated with a particular RNTI (e.g., CS-RNTI/C-RNTI for PTP or CS-RNTI/G-RNTI for PTM SPS/dynamic scheduling). The gNB configures the timeslots of the PTP and PTM HARQ processes as follows: the first half of the time slot is allocated to a protocol data unit or TB generated from the PTP HARQ process and the second half of the time slot is allocated to a protocol data unit generated from the PTM HARQ process (i.e. the number of TBs allocated for the PTP and PTM processes may be equal within one time slot) (as shown in part a of fig. 11). After mapping PTP and PTM data or TB sets to two parts of a slot, the gNB may generate a single bit PTP/PTM HARQ information indicator per slot, as shown in table 1 of fig. 11, provide an indication to the UE, and react/reconfigure retransmissions according to the received code bit feedback from the UE as described in some embodiments above, the only difference being that the UE and the gNB interaction will be based on the slot(s) instead of on a single TB in some embodiments described above.
Table 1: PTP/PTM HARQ indication information bit provided by NB to UE
TABLE 2 PTP/PTMEACK/NACK feedback bits provided by the network to the UE
In summary, some embodiments of the present application provide an efficient and low-overhead HARQ transmission and retransmission method for dynamic and/or semi-persistent scheduling of simultaneous MBS (PTP/PTM) and unicast (PTP) scheduling of UEs in a time slot. The exemplary method avoids downlink transmission defects by employing only partial retransmissions of the PTP or PTM portion of the transport block instead of retransmitting the entire transport block, and by utilizing one-bit HARQ indicators in the downlink and two-bit reconfigurable ACK/NACK uplink feedback in the downlink. In this exemplary method, the gNB configures different/separate HARQ processes for PTP and PTM data, combines/maps/multiplexes data from the HARQ processes configured for PTP/PTM into a DL allocation, and indicates HARQ control information for the PTP/PTM combination and the HARQ process ID to one or more UEs. Upon receiving the HARQ control information and DL allocation from the gNB, the UE configures a single HARQ process to receive PTP and PTM DL data within the allocation, decodes and checks CRCs of PTP and PTM data (TBs) contained in the DL allocation to determine an erroneous portion (possibly a PTP portion, a PTM portion, or a PTP and PTM portion) of the DL allocation. After that, the UE configures PTP/PTM ACK/NACK feedback bits, and sends the feedback bits to the gNB over the uplink. Then, the gNB determines whether PTP or PTM on the gNB and the gNB need retransmission according to the received ACK/NACK feedback bit; if so, the gNB retransmits the DL allocation portion indicated by the feedback bit to the UE. Finally, the UE receives a retransmission portion of the DL assignment of the previous uplink feedback previously sent to the gNB.
In the foregoing, some embodiments of the present application provide an efficient low overhead method for configuring HARQ process initial transmissions and retransmissions to support simultaneous scheduling of multicast/broadcast (PTP/PTM) and unicast (PTP) of UEs in a time slot: the main innovative aspects of the new exemplary method may include: 1. the new exemplary method introduces HARQ mechanisms that allow simultaneous SPS and/or dynamic scheduling supporting unicast (PTP) and multicast (PTM) within a time slot. 2. The new exemplary method introduces a new indication method to help the UE identify that a given DL assignment contains both PTP and PTM TBs so that it can activate/deactivate the use of PTP/PTM ack/NACK configurations. 3. The new exemplary approach introduces a two-bit fixed feedback design, as opposed to CGB feedback, that increases uplink signaling overhead depending on the number of CBG bits configured (i.e., from 2 bits to 4, 6, 8 bits). 4. The new exemplary method introduces the idea of configuring a single HARQ process at the UE instead of two HARQ processes at the UE to correspond to two PTP and PTM HRAQ processes at the network, which helps to reduce UE complexity.
Fig. 12 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present application. The embodiments described herein may be implemented into a system using any suitably configured hardware and/or software. Fig. 12 illustrates a system 700 that includes Radio Frequency (RF) circuitry 710, baseband circuitry 720, application circuitry 730, memory/storage 740, display 750, camera 760, sensor 770, and input/output (I/O) interface 780 coupled to one another, at least as shown. Application circuitry 730 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may comprise any combination of general-purpose processors and special-purpose processors, such as graphics processors, application processors. The processor may be coupled with the memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems running on the system.
While the present application has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the present application is not to be limited to the disclosed embodiment, but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.