System and method for managing feedback for multicast transmissions

Abstract

A system and method for wireless communication, comprising: receiving a first transmission block (TB) from a network via unicast by a wireless communication device, and receiving indication information by the wireless communication device, wherein the indication information indicates that the first TB received via unicast is the same as a second TB transmitted by the network via multicast.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications and, more particularly, to systems and methods for managing feedback for multicast transmissions. Background Art

[0002] The first phase of standardization of the fifth generation mobile communication technology (5G) has been completed. It adopts a series of unicast features specified in the new radio (NR) releases, such as but not limited to Rel-15 and Rel-16. However, broadcast / multicast feature support has not yet been specified. Summary of the invention

[0003] The exemplary embodiments disclosed herein are intended to solve problems related to one or more problems raised in the prior art, and to provide additional features, which will become apparent when referring to the following detailed description in conjunction with the accompanying drawings. According to various embodiments, example systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example, not limitation, and it will be apparent to a person of ordinary skill in the art who reads this disclosure that various modifications may be made to the disclosed embodiments while still remaining within the scope of this disclosure.

[0004] In some arrangements, a wireless communication method includes: a wireless communication device receiving a first transport block (TB) from a network via unicast, and the wireless communication device receiving indication information from the network, the indication information indicating that the first TB received via unicast is the same as a second TB received from the network via multicast. Receiving the TB via unicast means that the received TB is carried on a PUSCH scheduled by a PDCCH, the PUSCH carrying downlink control information (DCI) with a cyclic redundancy check (CRC), the cyclic redundancy check (CRC) being scrambled by a UE-specific RNTI (e.g., C-RNTI). Receiving the TB via multicast means that the received TB is carried on a PUSCH scheduled by a PDCCH, the PUSCH carrying a DCI with a CRC scrambled by a group common RNTI (e.g., G-RNTI) defined for the multicast service.

[0005] In some arrangements, a wireless communication device includes at least one processor and a memory. The at least one processor is configured to read code from the memory and implement a wireless communication method, the wireless communication method including receiving a first TB from a network via unicast, and receiving indication information from the network, the indication information indicating that the first TB received via unicast is the same as a second TB received from the network via multicast.

[0006] In some arrangements, a computer program product includes computer-readable program medium code stored thereon, which, when executed by at least one processor, causes the at least one processor to implement a wireless communication method, the wireless communication method comprising receiving a first TB from a network via unicast, and receiving indication information from the network, the indication information indicating that the first TB received via unicast is the same as a second TB received from the network via multicast.

[0007] In some arrangements, a wireless communication method includes: a network transmits a first TB to a wireless communication device via unicast and indication information, and the network transmits a second TB to multiple wireless communication devices via multicast. The multiple wireless communication devices include a wireless communication device. The indication information indicates that the first TB transmitted via unicast is the same as the second TB transmitted by the network via multicast. Transmitting a TB via unicast means that the transmitted TB is carried on a PUSCH scheduled by a PDCCH, and the PUSCH carries a DCI with a CRC, which is scrambled by a UE-specific RNTI (e.g., C-RNTI). Transmitting a TB via multicast means that the transmitted TB is carried on a PUSCH scheduled by a PDCCH, and the PUSCH carries a DCI with a CRC, which is scrambled by a group common RNTI (e.g., G-RNTI) defined for the multicast service.

[0008] In some arrangements, a wireless communication device includes at least one processor and a memory. The at least one processor is configured to read code from the memory and implement the wireless communication method, the wireless communication method including transmitting a first TB to the wireless communication device via unicast and indication information, and transmitting a second TB to a plurality of wireless communication devices via multicast. The plurality of wireless communication devices include the wireless communication device. The indication information indicates that the first TB transmitted via unicast is the same as the second TB transmitted via multicast by the network.

[0009] In some arrangements, a computer program product includes computer readable program medium code stored thereon, which, when executed by at least one processor, causes the at least one processor to implement a wireless communication method, the wireless communication method including transmitting a first TB to a wireless communication device via unicast and indication information, and transmitting a second TB to a plurality of wireless communication devices via multicast. The plurality of wireless communication devices include the wireless communication device. The indication information indicates that the first TB transmitted via unicast is the same as the second TB transmitted via multicast by the network.

[0010] The above and other aspects and embodiments thereof are described in more detail in the drawings and the specification. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Various exemplary embodiments of the present solution will be described in detail below with reference to the accompanying drawings or drawings. The drawings are provided for illustrative purposes only and merely depict example embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered as limiting the breadth, scope, or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.

[0012] Figure 1 is a diagram illustrating a time slot structure corresponding to an example configuration of monitoring opportunities according to an embodiment of the present disclosure.

[0013] Figure 2 is a diagram illustrating a time slot structure corresponding to an example configuration of monitoring opportunities according to an embodiment of the present disclosure.

[0014] Figure 3 is a diagram illustrating a time slot structure corresponding to an example configuration of monitoring opportunities according to an embodiment of the present disclosure.

[0015] Figure 4 is a diagram illustrating a time slot structure corresponding to an example configuration of monitoring opportunities according to an embodiment of the present disclosure.

[0016] Figure 5 is a diagram illustrating a time slot structure corresponding to an example configuration of monitoring opportunities according to an embodiment of the present disclosure.

[0017] Figure 6 is a diagram illustrating a time slot structure corresponding to an example configuration of monitoring opportunities according to an embodiment of the present disclosure.

[0018] Figure 7 is a flow chart illustrating a wireless communication method for managing multicast feedback according to some embodiments of the present disclosure.

[0019] Figure 8 is a flow chart illustrating a wireless communication method for managing multicast feedback according to some embodiments of the present disclosure.

[0020] Fig. 9A is a block diagram illustrating an example base station according to some embodiments of the present disclosure; and

[0021] Fig. 9B is a block diagram illustrating an example UE according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0022] Various example embodiments of the present solution are described below with reference to the accompanying drawings to enable a person of ordinary skill in the art to make and use the present solution. As will be apparent to a person of ordinary skill in the art, after reading this disclosure, various changes or modifications may be made to the examples described herein without departing from the scope of the present solution. Therefore, the present solution is not limited to the example embodiments and applications described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein are merely example methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes may be rearranged while remaining within the scope of the present solution. Therefore, a person of ordinary skill in the art should understand that the methods and techniques disclosed herein present various steps or actions in a sample order, and unless otherwise expressly stated, the present solution is not limited to the specific order or hierarchy presented.

[0023] The applicant recognizes that broadcast and multicast can improve 5G wireless communication systems (e.g., in terms of system efficiency and user experience). In multicast mode, a network node (e.g., a base station) can use the same transmission mechanism to transmit the same information to a group of user equipment (UE) or wireless communication devices. An identification and management method is adopted for a UE group corresponding to a multicast service type. As used herein, a UE group for a multicast service type may be referred to as a "multicast UE group". In some examples, different UEs may experience various network environments (e.g., channel conditions, etc.). In some examples, in order to improve the efficiency of multicast transmission, UEs experiencing similar network environments are grouped into the same multicast UE group. In this regard, the selected transmission mechanism can be matched in a corresponding manner with the network environment of each UE in the multicast UE group. In addition, assuming that the network environment of each UE can change dynamically over time, according to the various arrangements disclosed herein, the management of the multicast UE group can also be performed in a dynamic manner.

[0024] Some embodiments of the present disclosure relate to a manner of determining a transmission mechanism in response to a network environment of UEs in a multicast UE group that is subject to a mutation (e.g., in response to a change in the network environment of the UEs in the multicast UE group). For example, a channel state information (CSI) measurement result reported by a UE may indicate that the UE requires a substantially different precoding matrix indicator (PMI) or modulation and coding scheme (MCS) compared to the PMI and MSC used for other UEs in the same multicast UE group. In this case, if the network transmits the multicast service with a relatively conservative transmission mechanism by considering the needs of the mutated UEs, the efficiency of the entire network will be reduced. On the other hand, if the network selects a transmission mechanism based on the needs of the majority of UEs in the multicast UE group (without considering the needs of the mutated UEs), the network performance experienced by the mutated UEs is difficult to guarantee, resulting in a decrease in the user experience of the mutated UEs.

[0025] The multicast service may be carried on a scheduled physical downlink shared channel (PDSCH) via a physical downlink control channel (PDCCH). The PDSCH and PDCCH are referred to as "multicast service PDSCH" and "multicast service PDCCH", respectively. The multicast service PDCCH carries a DCI format with a CRC scrambled by a corresponding radio network temporary identifier (RNTI) configured via radio resource control (RRC) signaling. Monitoring information of the multicast service PDCCH, such as but not limited to search space set configuration and control resource set (CORESET) configuration, may be referred to as multicast control information. The multicast control information may be indicated in system information, where, for example, the system information may be carried on a PDSCH scheduled by a PDCCH. The PDCCH is scrambled by a system information RNTI (SI-RNTI). Alternatively, the multicast control information may be carried on a PDSCH scheduled by a PDCCH, which is scrambled by a fixed RNTI for multicast specified in the specification or a dedicated RNTI configured via RRC signaling for this multicast service. The PDSCH and PDCCH used to carry and schedule multicast control information, respectively, may be referred to as "multicast control PDSCH" and "multicast control PDCCH", respectively. The CORESETs of the multicast service PDCCH and the multicast control PDCCH may be configured separately, or may share the same CORESET configuration. The search space sets of the multicast service PDCCH and the multicast control PDCCH may be configured separately, or may share the same search space set configuration (e.g., may be jointly configured).

[0026] In a wireless communication system, a CORESET includes one or more resource blocks (RBs) in the frequency domain and one or more orthogonal frequency division multiplexing (OFDM) symbols in the time domain. One or more PDCCH candidates are transmitted in a CORESET. The configuration parameters of a CORESET are configured by the network for a UE. Examples of the configuration parameters include, but are not limited to, an index of a set (e.g., a CORESET index), frequency domain resources, a duration of a set (e.g., a CORESET duration), and the like. One or more CORESETs may be configured for a UE so that the UE monitors a PDCCH.

[0027] In some examples, UEs receiving the same type of multicast service can be defined as a multicast UE group. For each UE in the multicast group, the base station (e.g., gNB) uses the same transmission mechanism to transmit the same information.

[0028] In a wireless communication system, the network can configure one or more search space sets for the UE. The configuration parameters of the search space set include but are not limited to the search space index, the associated CORESET index (which is associated with the search space index), the PDCCH monitoring periodicity, the PDCCH monitoring offset, the search space duration, the PDCCH monitoring mode within the time slot, the search space type, and the like. In some embodiments, there are two types of search spaces: UE-specific search space (USS) and common search space (CSS). The search space type can also indicate one or more downlink control information (DCI) formats monitored by the UE. The search space set is associated with a given CORESET (mapped to a given CORESET). The PDCCH monitoring periodicity and PDCCH monitoring offset indicate the time slots in which the UE needs to monitor the PDCCH. According to the search space set configuration and the associated CORESET configuration, the UE can monitor the PDCCH using the DCI format indicated by the search space type on the resources indicated by the CORESET and in the time slots indicated by the PDCCH monitoring periodicity and PDCCH monitoring offset.

[0029] The arrangements disclosed herein relate to the transmission of TBs in a PDSCH scheduled by a unicast PDCCH. In some examples, an indication is provided to indicate that a multicast TB is scheduled by a unicast PDCCH. Using the various indication methods disclosed herein, the UE can determine that a multicast TB has been transmitted in unicast mode and avoid NACK-only feedback for a multicast TB transmitted in multicast mode (if the multicast TB is not received in multicast mode). Therefore, unnecessary retransmissions of multicast TBs by multicast mode can be avoided, thereby improving the efficiency of the network in multicast transmission.

[0030] Figure 1 1 is a diagram illustrating a time slot structure corresponding to an example configuration 100 of PDCCH monitoring opportunities according to various embodiments. Figure 1 , configuration 100 corresponds to time slots 102a, 102b, 102c, 102d, 102e, 102f, 102g, and 102h (collectively referred to as time slots 102a-102h). The PDCCH monitoring periodicity is the periodicity with which the UE monitors the PDCCH. In configuration 100, the PDCCH monitoring periodicity is 4 time slots. That is, time slots 102a-102d are in PDCCH monitoring periodicity 106a, and time slots 102e-102h are in PDCCH monitoring periodicity 106b. The PDCCH monitoring offset in configuration 100 is 0 (e.g., no offset).

[0031] The search space duration in configuration 100 is 2 time slots. As shown, within PDCCH monitoring periodicity 106a, search space duration 104a includes time slots 102a and 102b. Within PDCCH monitoring periodicity 106b, search space duration 104b includes time slots 102e and 102f. In configuration 100, 2 PDCCH monitoring opportunities (MO) are configured in a given time slot within search duration 104a or 104b. For example, time slot 102a includes 14 OFDM symbols 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j, 110k, 110l, 110m and 110n (collectively referred to as symbols 110a-110n). Symbols 110a and 110h are configured as MO. Therefore, there are a total of 4 MOs in each PDCCH monitoring period. For example, symbols 110a and 110h in slot 102b and two additional OFDM symbols are within PDCCH monitoring periodicity 106a. Two OFDM symbols in each of slots 102e and 102f are within PDCCH monitoring periodicity 106b. In each MO, the UE monitors the PDCCH using one resource configured by the CORESET.

[0032] In some examples of wireless communication systems, there may be one or more PDCCH candidates in a search space. Each PDCCH candidate is identified by a PDCCH candidate index. A network (e.g., one or more base stations) may transmit control information to a UE or a UE group (e.g., a multicast UE group). A PDCCH may use data units such as one or more control channel elements (CCEs) to transmit control information. Each CCE is identified by a CCE index.

[0033] In some cases, in a network environment, one UE in a multicast UE group may suffer a mutation. For example, the CSI measurement result reported by the UE may indicate a PMI or MCS that is significantly different from the PMI and MSC used or required by other UEs in the same multicast UE group. This means that the signal strength of the connection between the mutation UE and the network (e.g., one or more base stations) measured by the mutation UE is significantly better or worse than the signal strength of the connection between other UEs in the group and the network. In this case, the various embodiments disclosed herein can be used to determine the transmission mechanism for multicast service transmission.

[0034] Examples of multicast transmission mechanisms include, but are not limited to, MCS, precoding matrix, etc. In some embodiments, the multicast transmission mechanism for transmitting a multicast transport block (TB) may be determined based on feedback from a majority of UEs in a multicast UE group. Examples of feedback include, but are not limited to, channel quality indicator (CQI), rank indication (RI), PMI, etc. For the remaining UEs (UEs that are not mutant UEs) in the same multicast UE group, the network may transmit the same multicast TB in a unicast manner, for example, by scheduling a PDSCH that carries the same multicast TB via a unicast PDCCH. In unicast mode, a transmission mechanism may be selected to accurately correspond to the network environment experienced by a specific UE (as reflected in the feedback information). At this point, the network performance of the UE may be guaranteed.

[0035] In some arrangements, a negative acknowledgement (NACK)-only feedback mechanism may be employed to support multicast transmission hybrid automatic repeat request (HARQ)-acknowledgement (ACK) feedback. In a NACK-only feedback mechanism, a group of UEs share the same resources for HARQ-ACK feedback, and the UEs in the group only need to provide feedback in the resource in response to determining that the UE did not correctly receive a multicast TB.

[0036] In some examples where the UE receives the same multicast TB from both unicast mode and multicast mode, the UE may not correctly receive the multicast TB via the multicast mode and send a feedback message on the NACK-only feedback resource. However, the UE may have correctly received the multicast TB via unicast. In such examples, the feedback from the UE may result in additional retransmissions of the multicast TB via the multicast mode, thereby wasting network resources.

[0037] In order to save network resources, each example indication method disclosed herein can be used to indicate that the TB carried on the PDSCH scheduled by the unicast PDCCH is the same as the multicast TB transmitted in the multicast mode. In some embodiments, the network (e.g., a base station) transmits the multicast TB in the PDSCH scheduled by the unicast PDCCH. Specifically, the network can indicate the multicast TB scheduled by the unicast PDCCH. By using the indication method disclosed herein, the UE can recognize that the received multicast TB has been transmitted in the unicast mode and avoid providing only NACK feedback for the same multicast TB transmitted in the multicast mode. In this regard, retransmission of the multicast TB through the multicast mode can be avoided, thereby improving the network efficiency of transmitting multicast services.

[0038] In some cases, the normal HARQ-ACK feedback mechanism can be used for multicast transmissions. In a normal NACK-ACK feedback mechanism, each UE is configured with one or more separate feedback resources, on which both positive feedback (e.g., ACK) and negative feedback (e.g., NACK) can be transmitted. In response to determining that the UE has correctly received the multicast TB, the UE provides positive feedback in the resource. On the other hand, in response to determining that the UE has not correctly received the multicast TB, the UE provides negative feedback in the resource.

[0039] In some examples where the same multicast TB is transmitted to a UE in both unicast mode and multicast mode, the UE may not correctly receive the multicast TB via the multicast mode and send a negative feedback message on the feedback resource. In this case, the UE may have correctly received the multicast TB via the unicast mode. In such an example, the feedback from the UE may result in additional retransmissions of the multicast TB via the multicast mode, thereby wasting network resources.

[0040] In order to save network resources, each example indication method disclosed herein can be used to indicate that the TB carried on the PDSCH scheduled by the unicast PDCCH is the same as the multicast TB transmitted in the multicast mode. In some embodiments, the network (e.g., a base station) transmits the multicast TB in the PDSCH scheduled by the unicast PDCCH. Specifically, the network can indicate the multicast TB scheduled by the unicast PDCCH. By using the indication method disclosed herein, the UE can recognize that the received multicast TB has been transmitted in unicast mode and avoid providing negative feedback for the same multicast TB transmitted in multicast mode. In this regard, retransmission of the multicast TB through the multicast mode can be avoided, thereby improving the network efficiency of transmitting multicast services. Alternatively, the network can also ignore negative feedback from the UE because the multicast TB has been transmitted through unicast instead of transmitting indication information.

[0041] In some embodiments, the first indication method may be adopted to indicate a multicast TB transmitted in unicast mode. The management of the HARQ process is independent of the unicast mode and the multicast mode. In other words, the HARQ process is managed separately for the unicast mode and the multicast mode. The HARQ process number (HPN) field in the PDCCH may be used to indicate the HPN used to schedule the TB. In one example, the HPN field occupies 4 bits, and each bit provides binary information (e.g., 0 or 1). That is, HPN 0000 to 1111 is configured for use in unicast mode. HPNs in the same range may also be configured to be used in multicast mode at the same time.

[0042] In some embodiments, the indication information may be an HPN used in a multicast PDCCH for scheduling a multicast TB, referred to as the HPN of the multicast TB. The indication information may be indicated by signaling (e.g., a medium access control (MAC) control element (CE)) carried on a PDSCH scheduled by a unicast PDCCH. The UE may recognize that a TB carried on the same PDSCH is the same as a multicast TB corresponding to the same HPN. In other words, both the TB and the indication information (e.g., the HPN for the multicast TB) are carried on the same unicast PDSCH.

[0043] By way of example, a network (e.g., one or more base stations) transmits a multicast TB to UEs in a multicast UE group via a multicast mode. The network also transmits a multicast TB to one UE (e.g., a first UE) in the multicast UE group via a unicast mode. The network sets the HPN for the multicast TB to 0000 in the multicast PDCCH that schedules the multicast TB. The network transmits a MAC CE containing the HPN (0000) for the multicast TB on a PDSCH scheduled by the unicast PDCCH. After the first UE receives the PDSCH, the UE can identify that the TB carried on the same PDSCH is a multicast TB corresponding to the HPN 0000. In a NACK-only feedback mechanism in which only a NACK needs to be provided to the base station, assuming that the multicast TB identified by the same HPN (0000) has been received via unicast, the first UE avoids providing feedback for the multicast TB transmitted in the multicast mode even if the multicast TB has not been received via multicast. Therefore, the network can determine whether to retransmit the multicast TB via the multicast mode based on feedback from one or more other UEs in the multicast UE group, where the network only sends the multicast TB to those other UEs via the multicast mode. In particular, the network can select the multicast transmission mechanism for transmitting the additional multicast TB based on feedback from the majority of UEs in the multicast UE group, without considering the first UE, which can be a mutant UE, assuming that the first UE avoids sending a negative feedback (NACK) to the network indicating that the wireless communication device failed to correctly receive the second TB via multicast.

[0044] In some embodiments, the New Data Indication (NDI) in the unicast PDCCH for scheduling a multicast TB is set to a "switched" value compared to the NDI value in the last (immediately previous) unicast PDCCH with the same HPN.

[0045] Figure 2 2 is a diagram illustrating a time slot structure 200 for a multicast and unicast downlink control channel according to various embodiments. Figure 1 and Figure 2, the time slot structure 200 is a downlink time slot structure 200, through which the UE receives data in the downlink from the network (e.g., one or more base stations). The time slot structure 200 includes time slots 202a, 202b, 202c, 202e, 202f, 202g, 202h, 202i, 202j, 202k and 202l (collectively referred to as time slots 202a-202l). The UE monitors the unicast service PDCCH MO in the time slot 202c and receives the unicast PDCCH 204a in the unicast service PDCCH MO. The UE monitors the unicast service PDCCH MO in the time slot 202j and receives the unicast PDCCH 204c in the unicast service PDCCH MO. The UE monitors the multicast service PDCCH MO in the time slot 202f and receives the multicast PDCCH 204b in the multicast service PDCCH MO.

[0046] The network uses the multicast PDCCH 204b to schedule the transmission of the multicast TB to the UE. The network sets the value of the HPN in the HPN field 216 of the multicast PDCCH 204b to, for example, 0000. For example, in the case where the UE is a mutation UE, the network uses the unicast PDCCH 204c to schedule the transmission of the same multicast TB to the UE. The network sets the value of the HPN in the HPN field 218 of the unicast PDCCH 204c to, for example, 0010.

[0047] As shown in the figure, the unicast PDCCH that the network transmits to the UE closest in time before the unicast PDCCH 204c is the unicast PDCCH 204a. The network uses the unicast PDCCH 204a to schedule the transmission of the unicast TB. The unicast PDCCH 204a is the unicast PDCCH closest to the unicast PDCCH 204c with the same HPN (e.g., 0010). The network sets the HPN in the HPN field 212 of the unicast PDCCH 204c to 0010. The network sets the NDI in the NDI field 214 of the unicast PDCCH 204a to 0. In addition, the network sets the NDI in the NDI field 220 of the unicast PDCCH 204c to 1, that is, the switching value is 0. The NDI of the unicast PDCCH 204c is different from the NDI of the unicast PDCCH 204a. The NDI in the unicast PDCCH 204c being 1 (switched value being 0) indicates to the UE that the TB scheduled using the unicast PDCCH 204c is new data, so that the UE does not combine the unicast TB scheduled using the unicast PDCCH 204a with the TB scheduled using the unicast PDCCH 204c (actually a multicast TB), even if the HPNs of the unicast PDCCH 204a and the unicast PDCCH 204c are the same (e.g., 0010). In other words, the unicast PDCCH 204c includes an indication (NDI) that the unicast PDCCH 204c carries new data separate from the data carried by the unicast PDCCH 204a, so that the data from the unicast PDCCH 204a and 204c cannot be combined.

[0048] Alternatively or additionally, the indication information (e.g., HPN for the multicast TB) may be carried in a unicast PDCCH that schedules a unicast PDSCH carrying the multicast TB. A field for indicating the HPN for the multicast TB may be defined in the unicast PDCCH. In response to receiving a unicast PDCCH having the same field value as the HPN value (0010) in the multicast PDCCH (e.g., HPN (0010) for the multicast TB), the UE determines that the TB carried on the PDSCH scheduled by the unicast PDCCH is the same as the multicast TB carried on the PDSCH scheduled by the multicast PDCCH.

[0049] In some embodiments, a second indication method may be adopted to indicate a multicast TB transmitted in unicast mode. The management of the HARQ process is independent of the unicast mode and the multicast mode. In other words, the HARQ process is managed separately for the unicast mode and the multicast mode. The HPN field in the PDCCH may be used to indicate the HPN of the scheduled TB. In the second indication method, the value range of the HPN used for the multicast mode is a subset of the value range of the HPN used for the unicast mode. In other words, the HPN values ​​that can be used for the multicast mode are the same or equivalent to the corresponding HPN values ​​(some but not all) that can be used for the unicast mode. The value range of the HPN field that can be used for the multicast mode and the unicast mode can be configured by RRC signaling or defined in the specification.

[0050] In one example, the HPN field of the multicast mode and the HPN field of the unicast mode each occupy 4 bits. The HPN value range of 0000 to 1111 is configured for use in unicast mode. The HPN value range of 0000 to 0111 is configured for use in multicast mode. In this regard, each of the HPN value ranges 0000 to 0111 used in the multicast PDCCH is equivalent to one of the HPN value ranges 0000 to 1111 used in the unicast PDCCCH to identify the multicast TB. That is, 0000 in the multicast PDCCH is equivalent to 0000 in the unicast PDCCH, 0001 in the multicast PDCCH is equivalent to 0001 in the unicast PDCCH, ..., and 0111 in the multicast PDCCH is equivalent to 0111 in the PDCCH in unicast.

[0051] In another example, the bit width of the HPN field in multicast mode is smaller than the bit width of the HPN field in unicast mode. For example, the HPN field in multicast mode occupies 3 bits, and the HPN field in unicast mode occupies 4 bits. The HPN value range of 0000 to 1111 is configured for use in unicast mode. The HPN value range of 000 to 111 is configured for use in multicast mode. In this regard, each of the HPN value ranges 000 to 111 used in the multicast PDCCH is equivalent to a corresponding one of the HPN value ranges 0000 to 1111 used in the unicast PDCCCH to identify the multicast TB. That is, 000 in the multicast PDCCH is equivalent to 0000 in the unicast PDCCH, 001 in the multicast PDCCH is equivalent to 0001 in the unicast PDCCH, ..., and 111 in the multicast PDCCH is equivalent to 0111 in the unicast PDCCH.

[0052] In some embodiments, the indication information may be an HPN used for scheduling a multicast TB in a multicast PDCCH, referred to as an HPN for a multicast TB. The indication information (e.g., an HPN for a multicast TB) may be indicated by an HPN field in a unicast PDCCH that schedules a unicast PDSCH carrying the multicast TB. An HPN field may be defined in a unicast PDCCH to indicate the HPN of a multicast TB. The UE may recognize that a TB carried on the PDSCH (scheduled by a unicast PDCCH) is the same as a multicast TB scheduled by a multicast PDCCH with the same HPN. For example, a unicast PDCCH with HPN 0000 schedules the same multicast TB as a multicast TB scheduled by a multicast PDCCH with HPN 000 or 0000.

[0053] In some embodiments, assuming that the value range of HPN for multicast mode is a subset of the value range of HPN for unicast mode (the value range of HPN for unicast mode is larger than the value range of HPN for multicast mode), some but not all (e.g., the first part) of the value range of HPN for unicast mode can be configured for scheduling unicast PDSCH carrying multicast TB, while other values ​​(e.g., the second part of the value range of HPN for unicast mode) can be configured for scheduling unicast PDSCH carrying unicast TB. As an example, HPN values ​​0000 to 0111 in a unicast PDCCH can be used to schedule a PDSCH carrying a multicast TB, and HPN values ​​1000 to 1111 in a unicast PDCCH can be used to schedule a PDSCH carrying a unicast TB.

[0054] Figure 3 3 is a diagram illustrating a time slot structure 300 for a multicast and unicast downlink control channel according to various embodiments. Figure 1 and Figure 3 , the time slot structure 300 is a downlink time slot structure 300, through which the UE receives data in the downlink from the network (e.g., one or more base stations). The time slot structure 300 includes time slots 302a, 302b, 302c, 302e, 302f, 302g, 302h, 302i, 302j, 302k and 302l (collectively referred to as time slots 302a-302l). The UE monitors the multicast service PDCCH MO in the time slot 302f and receives the multicast PDCCH 304a in the multicast service PDCCH MO. The UE monitors the unicast service PDCCH MO in the time slot 302j and receives the unicast PDCCH 304b in the unicast service PDCCH MO.

[0055] The network uses the multicast PDCCH 304a to schedule the transmission of the multicast TB to the UE. The network sets the value of the HPN in the HPN field 312 of the multicast PDCCH 304a to, for example, 010 or 0010. For example, in the case where the UE is a mutation UE, the network uses the unicast PDCCH 304b to schedule the transmission of the same multicast TB to the UE. The network sets the value of the HPN in the HPN field 313 of the unicast PDCCH 304b to, for example, 0010.

[0056] In response to receiving a unicast PDCCH 304b having an HPN value (0010) that is the same as or equivalent to the HPN value (010 or 0010) in the multicast PDCCH 304a, the UE determines that the TB carried on the PDSCH scheduled by the unicast PDCCH 304b is the same as the multicast TB carried on the PDSCH scheduled by the multicast PDCCH 304a.

[0057] In some embodiments, the third indication method can be used to indicate a multicast TB transmitted in unicast mode. The HPN field in the PDCCH can be used to indicate the HPN of the scheduled TB. In the third indication method, the value range of the HPN for the multicast mode is different from the value range of the HPN for the unicast mode.

[0058] In one example, the HPN field for multicast mode and the HPN field for unicast mode each occupy 4 bits. The HPN value range 0000-0111 is configured for use in unicast mode. The HPN value range 1000-1111 is configured for use in multicast mode. In other words, the HPN value that can be used to schedule a multicast TB is different from any HPN value that can be used to schedule a multicast TB and does not overlap with any HPN value that can be used to schedule a multicast TB.

[0059] In some embodiments, the indication information may be an HPN used in a multicast PDCCH for scheduling a multicast TB, referred to as an HPN for a multicast TB. The indication information (e.g., an HPN for a multicast TB) may be indicated by an HPN field in a unicast PDCCH that schedules a unicast PDSCH carrying the multicast TB. An HPN field may be defined in a unicast PDCCH to indicate the HPN of a multicast TB. The UE may determine that a TB carried on a PDSCH (scheduled by a unicast PDCCH) is the same as a multicast TB scheduled by a multicast PDCCH with the same HPN. For example, a unicast PDCCH with HPN 0000 schedules the same multicast TB as a multicast TB scheduled by a multicast PDCCH with HPN 0000.

[0060] In some examples, the value range of HPN configured for unicast PDCCH (e.g., 0000 to 0111) is only used to schedule PDSCH carrying unicast TBs. On the other hand, assuming that the HPN field for unicast is 4 bits, at least a portion of the remaining values ​​of HPN in the unicast PDCCH, such as the value range of HPN 1000 to 1111 (referred to as the remaining value range of HPN that is not configured to carry unicast TBs) can be configured to schedule multicast TBs. In this regard, each of the HPN value ranges 1000 to 1111 used in the multicast PDCCH is equivalent to one of the HPN value ranges 1000 to 1111 used in the unicast PDCCCH to identify the multicast TB. That is, 1000 of the multicast PDCCH is equivalent to 1000 of the unicast PDCCH, 1001 of the multicast PDCCH is equivalent to 1001 of the unicast PDCCH, ..., 1111 of the multicast PDCCH is equivalent to 1111 of the unicast PDCCH. The HPN field range for multicast TB and unicast TB scheduling can be configured through RRC signaling or defined in the specification.

[0061] Figure 4 4 is a diagram illustrating a time slot structure 400 for a multicast and unicast downlink control channel according to various embodiments. Figure 1 and Figure 4 , time slot structure 400 is a downlink time slot structure 400, through which the UE receives data in the downlink from the network (e.g., one or more base stations). Time slot structure 400 includes time slots 402a, 402b, 402c, 402e, 402f, 402g, 402h, 402i, 402j, 402k and 402l (collectively referred to as time slots 402a-402l). The UE monitors the multicast service PDCCH MO in time slot 402f and receives the multicast PDCCH 404a in the multicast service PDCCH MO. The UE monitors the unicast service PDCCH MO in time slot 402j and receives the unicast PDCCH 404b in the unicast service PDCCH MO.

[0062] The network uses the multicast PDCCH 404a to schedule the transmission of the multicast TB to the UE. The network sets the value of the HPN in the HPN field 412 of the multicast PDCCH 404a to, for example, 1010. For example, in the case where the UE is a mutant UE, the network uses the unicast PDCCH 404b to schedule the transmission of the same multicast TB to the UE. The network sets the value of the HPN in the HPN field 414 of the unicast PDCCH 404b to 1010. Figure 4 In the example shown, the HPN value range of the multicast downlink control channel configured to be used for scheduling the PDSCH carrying the unicast TB is 0000-0111.

[0063] In response to receiving a unicast PDCCH 404b having an HPN value (1010) within the remaining value range of 1000 to 1111, which HPN value is the same as or equivalent to the HPN value (1010) in the multicast PDCCH 404a, the UE determines that the TB carried on the PDSCH scheduled by the unicast PDCCH 404b is the same as the multicast TB carried on the PDSCH scheduled by the multicast PDCCH 404a.

[0064] In some embodiments, the fourth indication method can be used to indicate a multicast TB transmitted in unicast mode. The management of the HARQ process is independent of the unicast mode and the multicast mode. In other words, the HARQ process is managed separately for the unicast mode and the multicast mode. The HPN field in the PDCCH can be used to indicate the HPN used to schedule the TB. In one example, the HPN field occupies 4 bits, and each bit provides binary information (e.g., 0 or 1). That is, HPN 0000~1111 is configured for use in unicast mode. The same range of HPNs can also be configured for multicast mode at the same time.

[0065] In some embodiments, in addition to the HPN field (e.g., 4 bits), the unicast PDCCH may also include a multicast indication field (e.g., 1 bit) indicating whether the unicast PDCCH schedules a unicast TB or a multicast TB. For example, a multicast indication field of a first value (e.g., 0) indicates that the unicast PDCCH schedules a unicast TB (e.g., the HPN field is used for a unicast TB). A multicast indication field of a second value (e.g., 1) indicates that the unicast PDCCH schedules a multicast TB (e.g., the HPN field is used for a multicast TB). In this regard, in an example where the multicast indication field indicates that the unicast PDCCH schedules a multicast TB, the HPN field in the unicast PDCCH also identifies the multicast TB that the unicast PDCCH is used for scheduling. The TB scheduled by the unicast PDCCH is the same as the multicast TB scheduled by the multicast PDCCH with the same HPN.

[0066] Figure 5 is a diagram illustrating a time slot structure 500 for a multicast and unicast downlink control channel according to various embodiments. Figure 1 and Figure 5, time slot structure 500 is a downlink time slot structure 500, through which the UE receives data in the downlink from the network (e.g., one or more base stations). The time slot structure 500 includes time slots 502a, 502b, 502c, 502e, 502f, 502g, 502h, 502i, 502j, 502k and 502l (collectively referred to as time slots 502a-502l). The UE monitors the multicast service PDCCH MO in time slot 502f and receives the multicast PDCCH 504a in the multicast service PDCCH MO. The UE monitors the unicast service PDCCH MO in time slot 502j and receives the unicast PDCCH 504b in the unicast service PDCCH MO.

[0067] The network uses the multicast PDCCH 504a to schedule the transmission of the multicast TB to the UE. The network sets the value of the HPN in the HPN field 512 of the multicast PDCCH 504a to, for example, 1010. For example, in the case where the UE is a mutant UE, the network uses the unicast PDCCH 504b to schedule the transmission of the same multicast TB to the UE. The network sets the value of the HPN (in the HPN field 514) in the unicast PDCCH 504b to 1010, and sets the multicast indication field (MIF) 516 in the unicast PDCCH 504 to a second value (e.g., 1).

[0068] In response to receiving a unicast PDCCH 504b whose multicast indication field 516 is a second value, assuming that the HPN values ​​of the multicast PDCCH 504a and the unicast PDCCH 504b are the same (e.g., 1010), the UE determines that the TB carried on the PDSCH scheduled by the unicast PDCCH 504b is the same multicast TB (rather than a unicast TB) as the multicast TB carried on the PDSCH scheduled by the multicast PDCCH 504a.

[0069] As described in the first, second, third and fourth indication methods herein, indication information (indicating that a multicast TB is carried on a unicast PDSCH) is carried on a unicast PDCCH that schedules a unicast PDSCH. Figure 6 6 is a diagram illustrating a time slot structure 600 for a multicast and unicast downlink control channel according to various embodiments. Figure 1-6, the time slot structure 600 includes time slots 602a, 602b, 602c, 602e, 602f, 602g, 602h, 602i, 602j, 602k and 602l (collectively referred to as time slots 602a-602l). The UE monitors the multicast service PDCCH MO in time slot 602a and receives the multicast PDCCH 604a in the multicast service PDCCH MO. The network uses the multicast PDCCH 604a to schedule the multicast PDSCH 604b carrying the multicast TB. As shown in the figure, when the multicast PDCCH 604a ends, the multicast PDSCH 604b starts. In some examples, the UE fails to receive the multicast PDSCH 604b.

[0070] The feedback resource 608 corresponds to the multicast PDSCH 604b. That is, the UE may transmit feedback to the network on the feedback resource 608. Specifically, in the NACK-only feedback mechanism, in response to the UE determining that the multicast PDSCH 604b scheduled by the multicast PDCCH 604a is not correctly received, the UE transmits NACK-only feedback to the network on the feedback resource 608 to inform the network that the UE did not receive the multicast PDSCH 604b.

[0071] The UE monitors the unicast service PDCCH MO in time slot 602f and receives the unicast PDCCH 606a in the unicast service PDCCH MO. The network uses the unicast PDCCH 606a to schedule the unicast PDSCH 606b carrying the multicast TB. As shown, when the unicast PDCCH 606a ends, the unicast PDSCH 606b starts. As described above, the unicast PDCCH 606a or the unicast PDSCH 606b can include indication information to notify the UE that the unicast PDSCH 606b is carrying the same multicast TB as the multicast TB carried by the multicast PDSCH 604b.

[0072] In an example where the unicast PDCCH 606a carries indication information to inform the UE that the unicast PDSCH 606b is carrying the same multicast TB as the multicast TB carried by the multicast PDSCH 604b, the time interval 612 is defined as the time interval between the end point of the control resource set (CORESET) of the unicast PDCCH 606a used for multicast TB scheduling (e.g., for scheduling multicast TBs) and the start point of the feedback resource 608 (e.g., only NACK feedback resources) corresponding to the multicast TB in multicast mode (e.g., carried in the multicast PDSCH 604b). The value of the threshold length defining the time interval 612 is N symbols. The value of N can be defined in the specification or configured through RRC signaling according to the subcarrier spacing (SCS). For example, for SCS=15kHz, N=5 symbols, for SCS=30kHz, N=5.5 symbols, ..., and so on. In some examples, the SCS used to determine the value of the number N may be the SCS of the unicast PDCCH 606a or the SCS of the feedback resource 608. In some examples, the number N may be defined based on the smaller of the SCS of the unicast PDCCH 606a and the SCS of the feedback resource 608. In some examples, the UE expects that the time interval 612 between the end point of the CORESET of the unicast PDCCH 606a for multicast TB scheduling and the start point of the NACK-only feedback resource 608 corresponding to the multicast TB in the multicast mode is greater than a threshold (e.g., N symbols).

[0073] In an example where the unicast PDSCH 606b carries indication information to inform the UE that the unicast PDSCH 606b is carrying the same multicast TB as the multicast TB carried by the multicast PDSCH 604b, the time interval 610 is defined as the time interval between the end point of the unicast PDSCH 606b (carrying the multicast TB scheduling, e.g., indication information) scheduled by the unicast PDCCH 606a and the start point of the feedback resource 608 (e.g., only NACK feedback resource) corresponding to the multicast TB in the multicast mode. The value of the threshold length defining the time interval 610 is M symbols. The value of M can be defined in the specification or configured by RRC signaling according to the SCS. For example, for SCS=15kHz, N=2 symbols, for SCS=30kHz, N=3 symbols, ..., and so on. In some examples, the SCS used to determine the value of the number M can be the SCS of the unicast PDSCH 606b or the SCS of the feedback resource 608. In some examples, the number M can be defined based on the smaller of the SCS of the unicast PDSCH 606b and the SCS of the feedback resources 608. In some examples, the UE expects that the time interval 610 between the end point of the unicast PDSCH 606b carrying the multicast TB scheduled for the unicast PDCCH and the start point of the NACK-only feedback resources 608 corresponding to the multicast TB in the multicast mode is greater than a threshold (e.g., M symbols).

[0074] Figure 7 is a flow chart illustrating a wireless communication method 700 for managing multicast feedback according to some embodiments of the present disclosure. Figure 1-7 , the wireless communication method 700 may be implemented by a UE (eg, a wireless communication device).

[0075] At 710, the UE receives a first TB from the network via unicast. At 720, the UE receives an indication from the network that the first TB received via unicast is the same as a second TB transmitted by the network via multicast. In some examples, the first TB and the indication are received before the second TB. In some examples, Figure 2-6 As shown, the first TB and the indication information are received after the second TB.

[0076] In some examples, in response to receiving the first TB and the indication information, or in response to receiving the indication information, the UE avoids providing negative feedback to the network. The negative feedback indicates to the network that the UE failed to correctly receive the second TB through multicast. That is, regardless of whether the UE receives the second TB, the UE determines that the second TB has been received by responding to receiving the first TB and the indication information or in response to receiving the indication information. In some embodiments, the first TB and the second TB are the same TB. The negative feedback is NACK feedback.

[0077] In some embodiments, according to the first indication method, the indication information is a HPN for scheduling the second TB in a multicast downlink control channel. The first TB is received in a unicast downlink shared channel of unicast. The unicast downlink control channel is used to schedule the first TB in the unicast downlink shared channel.

[0078] In some embodiments, according to the first indication method, the indication information is received from the network by signaling on a unicast downlink shared channel scheduled by a unicast downlink control channel. As disclosed in more detail, the time interval between the end point of the unicast downlink shared channel (e.g., the end of the last symbol) and the start point of the feedback resource corresponding to the second TB (e.g., the start symbol) is greater than a threshold.

[0079] In some embodiments, according to the first, second, third or fourth indication method, indication information is received from the network in a unicast downlink control channel used to schedule the first TB in the unicast downlink shared channel. As disclosed in more detail, the time interval between the end point of the CORESET of the unicast downlink control channel (e.g., the end of the last symbol) and the start point of the feedback resource corresponding to the second TB (e.g., the start symbol) is greater than a threshold.

[0080] In some embodiments, according to the second indication method, the indication information is an HPN for scheduling a second TB in a multicast downlink control channel. The multicast downlink control channel is defined (e.g., defined in a specification or signed using RRC signaling) as a first value range for using HPN in multicast mode. The unicast downlink control channel is defined (e.g., defined in a specification or signed using RRC signaling) as a second value range for using HPN in unicast mode. The first value range is a subset of the second value range. In some embodiments, each value of the first part of the second value range of the HPN is used to schedule a unicast downlink physical channel carrying a multicast TB. Each value of the second part of the second value range of the HPN is used to schedule a unicast downlink physical channel carrying a unicast TB.

[0081] In some embodiments, according to the third indication method, the indication information is an HPN in a multicast downlink control channel for scheduling a second TB. The multicast downlink control channel is defined (e.g., defined in a specification or signed using RRC signaling) as a first value range for using HPN in multicast mode. The unicast downlink control channel is defined (e.g., defined in a specification or signed using RRC signaling) as a second value range for using HPN in unicast mode. The first value range and the second value range are different. In some embodiments, each value of the second value range of HPN is used to schedule a unicast downlink physical channel carrying a unicast TB. Each value of the remaining value range of HPN is used to schedule a unicast downlink physical channel carrying a multicast TB. The second value range is different from the remaining value range. The remaining value range corresponds to the first value range.

[0082] In some embodiments, according to the fourth indication method, the indication information is the HPN used to schedule the second TB in the multicast downlink control channel. The network uses the unicast downlink control channel to schedule the first TB in the unicast downlink shared channel. The unicast downlink control channel includes the indication information and the multicast indication field. The multicast indication field indicates to the UE that the unicast downlink control channel is used to schedule the multicast TB or the unicast TB.

[0083] Figure 8 8 is a flow chart illustrating a wireless communication method 800 for managing multicast feedback according to some embodiments of the present disclosure. Figure 1-8 The wireless communication method 800 may be implemented by a network (eg, one or more base stations or network nodes). The method 800 corresponds to the method 700 implemented by a UE.

[0084] At 810, the network transmits a first TB and indication information to the UE. The first TB is transmitted via unicast. At 820, the network transmits a second TB to a plurality of UEs via multicast. The plurality of UEs includes the UE. The indication information indicates that the first TB transmitted via unicast is the same as the second TB transmitted by the network via multicast. In some examples, the first TB and indication information are transmitted before the second TB. In some examples, the first TB and indication information are transmitted after the second TB, such as Figure 2-6 shown.

[0085] In some embodiments, the UE avoids providing negative feedback to the network. The negative feedback indicates to the network that the UE failed to correctly receive the second TB via multicast. In some embodiments, the first TB and the second TB are the same. The negative feedback is NACK feedback.

[0086] In some embodiments, according to the first indication method, the indication information is used in the multicast downlink control channel to schedule the HPN of the second TB. The first TB is transmitted in the unicast downlink shared channel of unicast. The unicast downlink control channel is used to schedule the first TB in the unicast downlink shared channel.

[0087] In some embodiments, according to the first indication method, the indication information is transmitted by the network through signaling on a unicast downlink shared channel scheduled by a unicast downlink control channel. As disclosed in more detail herein, the time interval between the end point of the unicast downlink shared channel (e.g., the end of the last symbol) and the start point of the feedback resource corresponding to the second TB (e.g., the start symbol) is greater than a threshold.

[0088] In some embodiments, according to the first, second, third or fourth indication method, the indication information is transmitted by the network to the UE in a unicast downlink control channel used to schedule the first TB in the unicast downlink shared channel. As disclosed in more detail herein, the time interval between the end point of the CORESET of the unicast downlink control channel (e.g., the end of the last symbol) and the start point of the feedback resource corresponding to the second TB (e.g., the starting symbol) is greater than a threshold.

[0089] In some embodiments, according to the second indication method, the indication information is an HPN used in a multicast downlink control channel to schedule a second TB. The multicast downlink control channel is defined as a first value range of the HPN used in multicast mode. The unicast downlink control channel is defined as a second value range of the HPN used in unicast mode. The first value range is a subset of the second value range. In some examples, each value of the first part of the second value range of the HPN is used to schedule a unicast downlink physical channel carrying a multicast TB. Each value of the second part of the second value range of the HPN is used to schedule a unicast downlink physical channel carrying a unicast TB.

[0090] In some embodiments, according to the third indication method, the indication information is an HPN used in a multicast downlink control channel to schedule a second TB. The multicast downlink control channel is defined as a first value range of the HPN used in multicast mode. The unicast downlink control channel is defined as a second value range of the HPN used in unicast mode. The first value range and the second value range are different. In some examples, each value of the second value range of the HPN is used to schedule a unicast downlink physical channel carrying a unicast TB. Each value of the remaining value range of the HPN is used to schedule a unicast downlink physical channel carrying a multicast TB. The second value range is different from the remaining value range. The remaining value range corresponds to the first value range.

[0091] In some embodiments, according to the fourth indication method, the indication information is the HPN used to schedule the second TB in the multicast downlink control channel. The network uses the unicast downlink control channel to schedule the first TB in the unicast downlink shared channel. The unicast downlink control channel includes the indication information and the multicast indication field. The multicast indication field indicates to the UE that the unicast downlink control channel is used to schedule the multicast TB or the unicast TB.

[0092] Fig. 9A A block diagram of an example base station 902 (eg, communication node, network node, etc.) is shown in accordance with some embodiments of the present disclosure. Fig. 9B A block diagram of an example UE 901 according to some embodiments of the present disclosure is shown. Figure 1-9B UE 901 (e.g., wireless communication device, terminal, mobile device, mobile user, etc.) is an example implementation of the UE described herein, and base station 902 is an example implementation of the base station described herein. In particular, as described herein, UE 901 and base station 902 can perform methods 700 and 800, respectively.

[0093] The base station 902 and the UE 901 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In an illustrative embodiment, as described above, the base station 902 and the UE 901 may be used to transmit (e.g., send and receive) data symbols in a wireless communication environment. For example, the base station 902 may be a base station (e.g., gNB, eNB, etc.), a server, a node, or any suitable computing device used to implement various network functions.

[0094] The base station 902 includes a transceiver module 910, an antenna 912, a processor module 914, a memory module 916, and a network communication module 918. The modules 910, 912, 914, 916, and 918 are operably coupled and interconnected to each other via a data communication bus 920. The UE 901 includes a UE transceiver module 930, a UE antenna 932, a UE memory module 934, and a UE processor module 936. The modules 930, 932, 934, and 936 are operably coupled and interconnected to each other via a data communication bus 940. The base station 902 communicates with the UE 901 or another base station via a communication channel, which may be any wireless channel or other medium suitable for data transmission as described herein.

[0095] As is understood by those skilled in the art, the base station 902 and the UE 901 may also include Fig. 9A and 9BAny number of modules outside the modules shown. The various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented with hardware, computer-readable software, firmware, or any actual combination thereof. In order to illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described according to their functions. Whether such functions are implemented as hardware, firmware, or software depends on specific applications and design constraints to the entire system. The embodiments described herein can be implemented in a suitable manner for each specific application, but the decision of any implementation method should not be interpreted as limiting the scope of the present disclosure.

[0096] According to some embodiments, the UE transceiver 930 includes a radio frequency (RF) transmitter and an RF receiver, each of which includes a circuit coupled to an antenna 932. A duplex switch (not shown) can couple the RF transmitter or receiver to the antenna in a time division duplex manner. Similarly, according to some embodiments, the transceiver 910 includes an RF transmitter and an RF receiver, each of which has a circuit coupled to an antenna 912 or an antenna of another base station. The duplex switch can alternatively couple the RF transmitter or receiver to the antenna 912 in a time duplex manner. The operation of the two transceiver modules 910 and 930 can be coordinated in time so that the receiver circuit is coupled to the antenna 932 while the transmitter is coupled to the antenna 912 for receiving transmissions via a wireless transmission link. In some embodiments, there is tight time synchronization with a minimum guard time between changes in duplex direction.

[0097] The UE transceiver 930 and the transceiver 910 are configured to communicate via a wireless data communication link and cooperate with an appropriately configured RF antenna arrangement 912 / 932 that can support a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 910 and the transceiver 912 are configured to support industry standards such as long-term evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to specific standards and related protocols in application. On the contrary, the UE transceiver 930 and the base station transceiver 910 can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0098] The transceiver 910 and the transceiver of another base station (such as but not limited to the transceiver 920) are configured to communicate via a wireless data communication link and cooperate with an appropriately configured RF antenna arrangement that can support a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the transceiver 910 and the transceiver of another base station are configured to support industry standards such as LTE and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to specific standards and related protocols in application. On the contrary, the transceiver 910 and the transceiver of another base station can be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0099] According to various embodiments, the base station 902 may be a base station such as, but not limited to, an eNB, a serving eNB, a target eNB, a femto station, or a micro station. The base station 902 may be a RN, a conventional base station, a DeNB, or a gNB. In some embodiments, the UE 901 may be embodied in various types of UEs such as mobile phones, smart phones, personal digital assistants (PDAs), tablet computers, laptop computers, wearable computing devices, and the like. The processor modules 914 and 936 may be implemented or realized with a general-purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof, which is designed to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, and the like. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a digital signal processor core, or any other such configuration.

[0100] In addition, the methods or algorithms disclosed herein may be directly embodied in hardware, firmware, software modules executed by processor modules 914 and 936, respectively, or any practical combination thereof. Memory modules 916 and 934 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 916 and 934 may be coupled to processor modules 910 and 930, respectively, so that processor modules 910 and 930 may read information from and write information to memory modules 916 and 934, respectively. Memory modules 916 and 934 may also be integrated into their respective processor modules 910 and 930. In some embodiments, memory modules 916 and 934 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by processor modules 910 and 930, respectively. Memory modules 916 and 934 may also include non-volatile memory for storing instructions to be executed by processor modules 910 and 930, respectively.

[0101] The network communication module 918 generally represents the hardware, software, firmware, processing logic and / or other components of the base station 902 that enable bidirectional communication between the transceiver 910 and other network components and communication nodes that communicate with the base station 902. For example, the network communication module 918 can be configured to support Internet or WiMAX traffic. In a non-limiting deployment, the network communication module 918 provides an 802.3 Ethernet interface so that the transceiver 910 can communicate with a traditional Ethernet-based computer network. In this way, the network communication module 918 may include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). In some embodiments, the network communication module 918 includes a fiber optic transmission connection configured to connect the base station 902 to a core network. The terms "configured for", "configured to" and their variations used herein with respect to a specific operation or function refer to a device, component, circuit, structure, machine, signal, etc. It is physically constructed, programmed, formatted and / or arranged to perform a specified operation or function.

[0102] Although various embodiments of the present solution have been described above, it should be understood that these embodiments are presented by way of example only, rather than by way of limitation. Similarly, various figures may depict example architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the example features and functions of the present solution. However, it should be understood by these persons that the solution is not limited to the example architectures or configurations shown, but may be implemented using various alternative architectures and configurations. In addition, as those of ordinary skill in the art will appreciate, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.

[0103] It should also be understood that any reference to an element using names such as "first," "second," etc., herein generally does not limit the number or order of these elements. Instead, these names may be used herein as a convenient means of distinguishing two or more elements or instances of an element. Thus, a reference to a first and a second element does not mean that only two elements can be used, or that the first element must precede the second element in some manner.

[0104] In addition, it should be understood by those skilled in the art that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0105] It will also be understood by those of ordinary skill in the art that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of programs (e.g., computer program products), or design codes containing instructions (for convenience, referred to herein as "software" or "software modules"), or any combination of these technologies. In order to clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been generally described above according to their functions. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the overall system. A skilled technician may implement the described functionality in various ways for each specific application, but such implementation decisions will not result in a departure from the scope of this disclosure.

[0106] In addition, it will be appreciated by those of ordinary skill in the art that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented within or performed by an integrated circuit (IC), which may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device or any combination thereof. The logic blocks, modules, and circuits may also include antennas and / or transceivers to communicate with various components within a network or within a device. The general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration for performing the functions described herein.

[0107] If implemented in software, the function may be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein may be implemented as software stored on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and the computer communication media include any media that can transfer a computer program or code from one place to another. The storage medium can be any available medium that a computer can access. As an example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer.

[0108] In this application, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. In addition, for the purpose of discussion, various modules are described as separate modules; however, as is apparent to one of ordinary skill in the art, two or more modules can be combined to form a single module that performs the relevant functions of an embodiment of the present solution.

[0109] In addition, in the embodiment of the present solution, memory or other memory and communication components can be adopted.It should be understood that, for the sake of clarity, the above description has described the embodiment of the present solution with reference to different functional units and processors.However, it is obvious that any appropriate functional distribution between different functional units, processing logic elements or domains can be used without departing from the present solution.For example, the functionality illustrated as being performed by a separate processing logic element or controller can be performed by the same processing logic element or controller.Therefore, the reference to a specific functional unit is only a reference to a suitable device for providing the function, rather than indicating a strict logical or physical structure or organization.

[0110] Various modifications to the embodiments described in the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the embodiments shown herein, but to be consistent with the broadest scope consistent with the novel features and principles disclosed herein.

Claims

1. A wireless communication method, comprising: The wireless communication device receives a first transmission block TB from the network via unicast; The wireless communication device receives indication information from the network, the indication information indicating that the first TB received by the unicast is the same as the second TB transmitted by the network by multicast, wherein the indication information includes a hybrid automatic repeat request HARQ process number HPN, the HPN is in a multicast downlink control channel, and the multicast downlink control channel is used to schedule the second TB; as well as In response to receiving the first TB and the indication information, or in response to receiving the indication information, the wireless communication device avoids providing negative feedback to the network, wherein the negative feedback indicates to the network that the wireless communication device failed to correctly receive the second TB through the multicast.

2. The method according to claim 1, wherein The negative feedback is a negative acknowledgement NACK feedback.

3. The method according to claim 1, wherein: The indication information is received from the network via signaling on a unicast downlink shared channel scheduled by a unicast downlink control channel.

4. The method according to claim 3, wherein: A time interval between an end position of the unicast downlink shared channel and a start point of feedback resources corresponding to the second TB is greater than a threshold.

5. The method according to claim 1, wherein: The indication information is received from the network in a unicast downlink control channel, and the unicast downlink control channel is used to schedule the first TB in a unicast downlink shared channel.

6. The method according to claim 5, wherein: A time interval between an end position of a control resource set CORESET of the unicast downlink control channel and a start point of feedback resources corresponding to the second TB is greater than a threshold.

7. The method according to claim 1, wherein The multicast downlink control channel is defined as using a first value range of HPN; The unicast downlink control channel is defined to use the second value range of HPN; and The first value range is a subset of the second value range.

8. The method according to claim 7, wherein Each value of the first part of the second value range of HPN is used to schedule a unicast downlink physical channel carrying a multicast TB; and Each value of the second part within the second value range of HPN is used to schedule a unicast downlink physical channel carrying a unicast TB; and The first part within the second value range corresponds to the first value range.

9. The method according to claim 1, wherein The multicast downlink control channel is defined as using a first value range of HPN in multicast mode; The unicast downlink control channel is defined to use the second value range of HPN in unicast mode; and The first value range and the second value range are different.

10. The method according to claim 9, wherein Each value of the second value range of HPN is used to schedule a unicast downlink physical channel carrying a unicast TB; Each value of the remaining value range of HPN is used to schedule the unicast downlink physical channel carrying the multicast TB; The second value range is different from the remaining value range; and The remaining value range corresponds to the first value range.

11. The method according to claim 1, wherein The unicast downlink control channel is used by the network to schedule the first TB in a unicast downlink shared channel; The unicast downlink control channel includes the indication information and a multicast indication field; and The multicast indication field indicates to the wireless communication device that the unicast downlink control channel is used to schedule a multicast TB or a unicast TB.

12. A wireless communication device comprising a memory and at least one processor, wherein: The at least one processor is configured to read code from the memory and implement the method according to claims 1 to 11.

13. A computer program product comprising computer readable program medium code stored thereon, which, when executed by at least one processor, causes the at least one processor to implement the method according to claims 1 to 11.

14. A wireless communication method, comprising: The network transmits a first transmission block TB to the first wireless communication device via unicast and indication information; The network transmits a second TB to multiple wireless communication devices via multicast, wherein the multiple wireless communication devices include the first wireless communication device, and the indication information indicates that the first TB transmitted via the unicast is the same as the second TB transmitted by the network via the multicast, wherein the indication information includes a hybrid automatic repeat request HARQ process number HPN, and the HPN is in a multicast downlink control channel, and the multicast downlink control channel is used to schedule the second TB, wherein based on the first wireless communication device receiving the first TB and the indication information, or based on the first wireless communication device receiving the indication information, negative feedback is avoided from being provided by the first wireless communication device to the network, wherein the negative feedback indicates to the network that the first wireless communication device failed to correctly receive the second TB via the multicast.

15. The method according to claim 14, wherein The negative feedback is a negative acknowledgement NACK feedback.

16. The method according to claim 14, wherein: The indication information is transmitted by the network through signaling on a unicast downlink shared channel scheduled by a unicast downlink control channel.

17. The method according to claim 16, wherein: A time interval between an end position of the unicast downlink shared channel and a start point of feedback resources corresponding to the second TB is greater than a threshold.

18. The method according to claim 14, wherein: The indication information is transmitted by the network to the first wireless communication device in a unicast downlink control channel, and the unicast downlink control channel is used to schedule the first TB in a unicast downlink shared channel.

19. The method according to claim 18, wherein: A time interval between an end position of a control resource set CORESET of the unicast downlink control channel and a start point of feedback resources corresponding to the second TB is greater than a threshold.

20. The method of claim 14, wherein The multicast downlink control channel is defined as using a first value range of HPN in multicast mode; The unicast downlink control channel is defined to use the second value range of HPN in unicast mode; and The first value range is a subset of the second value range.

21. The method according to claim 20, wherein Each value of the first part of the second value range of HPN is used to schedule a unicast downlink physical channel carrying a multicast TB; and Each value of the second part within the second value range of HPN is used to schedule a unicast downlink physical channel carrying a unicast TB; and The first part within the second value range corresponds to the first value range.

22. The method of claim 14, wherein The multicast downlink control channel is defined as using a first value range of HPN in multicast mode; The unicast downlink control channel is defined to use the second value range of HPN in unicast mode; and The first value range and the second value range are different.

23. The method according to claim 22, wherein Each value of the second value range of HPN is used to schedule a unicast downlink physical channel carrying a unicast TB; Each value of the remaining value range of HPN is used to schedule the unicast downlink physical channel carrying the multicast TB; The second value range is different from the remaining value range; and The remaining value range corresponds to the first value range.

24. The method of claim 14, wherein A unicast downlink control channel is used by the network to schedule the first TB in a unicast downlink shared channel; The unicast downlink control channel includes the indication information and a multicast indication field; and The multicast indication field indicates to the first wireless communication device that the unicast downlink control channel is used to schedule a multicast TB or a unicast TB.

25. A wireless communication device comprising a memory and at least one processor, wherein: The at least one processor is configured to read code from the memory and implement the method according to claims 14 to 24.

26. A computer program product comprising computer readable program medium code stored thereon, which, when executed by at least one processor, causes the at least one processor to implement the method according to claims 14 to 24.

Images