Downlink control information indication for multicast and unicast transmission

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) can be configured with a mapping between downlink control information (DCI) codepoint values, multicast configurations, and unicast configurations. The DCI can then signal the UE to apply one of a multicast configuration or a unicast configuration to receive a shared data channel transmission. For example, for a given DCI field for a group common downlink control channel for multicast data, one or some DCI codepoint values can be associated with values configured for a multicast configuration, while remaining codepoints are associated with values configured for a unicast configuration. In some implementations, the UE can identify which multicast configuration or unicast configuration to apply based on the mapping, a type of data transmission scheduled by the DCI, a designated value for the DCI codepoint value, whether the shared data channel transmission is a retransmission, or a combination thereof.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. Patent Application No. 17 / 148,410, filed January 13, 2021, entitled “DOWNLINK CONTROL INFORMATION INDICATION FOR MULTICAST AND UNICAST TRANSMISSIONS”, which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following discussion relates to wireless communications, including downlink control information (DCI) indications for multicast and unicast transmissions. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcasting. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems, such as Long Term Evolution (LTE) systems, improved LTE (LTE-A) systems, or LTE-A Pro systems, and fifth-generation (5G) systems, which may be called New Radio (NR) systems. These systems can employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM).

[0005] A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each of which simultaneously supports communication with multiple communication devices (which may also be referred to as user equipment (UE)). In some examples, communication between wireless devices (e.g., between a base station and one or more UEs) can be divided into two categories: point-to-point (PTP) communication (e.g., unicast communication) and point-to-multipoint (PTM) communication (e.g., multicast communication, broadcast communication, etc.). Technologies are expected to be used to implement PTM communication. Summary of the Invention

[0006] The described technology relates to improved methods, systems, devices, and apparatuses for supporting downlink control information (DCI) indication for multicast and unicast transmissions. In summary, the described technology provides a user equipment (UE) receiving a code point mapping configuration that maps a set of DCI code point values ​​(e.g., code point indices) to a set of multicast configurations and a set of DCI code point values ​​to a set of unicast configurations. The UE can then receive a DCI (e.g., a control message) that signals to the UE to apply either a multicast configuration or a unicast configuration based on the code point mapping configuration to subsequently receive shared data channel transmissions. In some examples, the UE can identify which multicast or unicast configuration to apply for receiving shared data channel transmissions based on: the type of data transmission scheduled by the DCI (e.g., multicast data transmission or non-multicast data transmission), the indication value of the DCI code point value set (e.g., "unicast value," "empty value," or "no value"), whether the shared data channel transmission is a retransmission, or a combination thereof.

[0007] A method for wireless communication at a first UE is described. The method may include: receiving a code point configuration for a point-to-multipoint (PTM) transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations; receiving a control message scheduling a shared data channel transmission for at least one UE in a group of UEs comprising a set of multiple UEs, the set of multiple UEs including the first UE, the control message including a first code point index in the set of multiple code point indices; identifying a transmission configuration to be applied to receiving the shared data channel transmission based on the mapping and the first code point index, the transmission configuration being either a first multicast configuration in the set of multiple multicast configurations or a first unicast configuration in the set of multiple unicast configurations; and receiving the shared data channel transmission according to the identified transmission configuration.

[0008] An apparatus for wireless communication at a first UE is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a code point configuration for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations; receive a control message scheduling a shared data channel transmission for at least one UE in a group of UEs comprising a set of multiple UEs, the set of multiple UEs including the first UE, the control message including a first code point index in the set of multiple code point indices; identify a transmission configuration to be applied to receiving the shared data channel transmission based on the mapping and the first code point index, the transmission configuration being either a first multicast configuration in the set of multiple multicast configurations or a first unicast configuration in the set of multiple unicast configurations; and receive the shared data channel transmission according to the identified transmission configuration.

[0009] Another apparatus for wireless communication at a first UE is described. The apparatus may include: a unit for receiving a code point configuration for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations; a unit for receiving a control message scheduling a shared data channel transmission for at least one UE in a group of UEs comprising a set of multiple UEs, including the first UE, the control message including a first code point index from the set of multiple code point indices; a unit for identifying a transmission configuration to be applied to receiving the shared data channel transmission based on the mapping and the first code point index, the transmission configuration being either a first multicast configuration from the set of multiple multicast configurations or a first unicast configuration from the set of multiple unicast configurations; and a unit for receiving the shared data channel transmission according to the identified transmission configuration.

[0010] A non-transitory computer-readable medium is described, storing code for wireless communication at a first UE. The code may include instructions executable by a processor to: receive a code point configuration for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations; receive a control message scheduling a shared data channel transmission for at least one UE in a group of UEs comprising a set of multiple UEs, including the first UE, the control message including a first code point index from the set of multiple code point indices; identify a transmission configuration to be applied to receiving the shared data channel transmission based on the mapping and the first code point index, the transmission configuration being either a first multicast configuration from the set of multiple multicast configurations or a first unicast configuration from the set of multiple unicast configurations; and receive the shared data channel transmission according to the identified transmission configuration.

[0011] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the code point configuration may include operations, features, units, or instructions for performing the following: receiving a first code point mapping configuration that maps a first subset of the set of the plurality of code point indices to a set of the plurality of multicast configurations; and receiving a second code point mapping configuration that maps each code point index in the set of the plurality of code point indices to a corresponding unicast configuration in the set of the plurality of unicast configurations.

[0012] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, identifying the transport configuration may include operations, features, units or instructions for performing the following: identifying the transport configuration as the first multicast configuration based on the fact that the first code point index appears within a first subset of the set of the plurality of code point indices.

[0013] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, identifying the transport configuration may include operations, features, units or instructions for performing the following: identifying the transport configuration as the first unicast configuration based on the fact that the first code point index appears outside the first subset of the set of the plurality of code point indices.

[0014] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the shared data channel transmission may include operations, features, units, or instructions for receiving the shared data channel transmission according to parameters indicated by an identified transmission configuration.

[0015] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the parameters include Transmission Configuration Indicator (TCI) status, resource allocation, modulation and coding scheme (MCS), precoding matrix indicator (PMI), or any combination thereof.

[0016] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the control message may include operations, features, units, or instructions for performing the following: receiving the control message including the first code point index in a field having a bit width, the bit width being determined based on the number of first code point indices in a set of multiple code point indices corresponding to a set of multiple multicast configurations, the number of second code point indices in a set of multiple code point indices corresponding to a set of multiple unicast configurations, or both.

[0017] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the control message may include an operation, feature, unit, or instruction for performing the following: receiving the control message including the first code point index in a field having a bit width, the bit width being determined based on the mapping indicating the association between a corresponding code point index in a set of a plurality of code point indices and a corresponding index value in a set of a plurality of index values.

[0018] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, receiving the code point configuration may include operations, features, units or instructions for receiving the associated code point configuration.

[0019] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the association may be determined based on the ascending or descending order of parameters indicated in the code point configuration.

[0020] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the association may be determined based on the ascending or descending order of the identifiers (IDs) of one or more parameters indicated in the code point configuration.

[0021] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the code point configuration may include operations, features, units, or instructions for performing the following: receiving the code point configuration, the code point configuration indicating a unicast value corresponding to a second code point index value in a set of the plurality of code point indices and a null value corresponding to a third code point index value in a set of the plurality of code point indices.

[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing: receiving a second control message scheduled for a second shared data channel transmission for the UE group; and determining, based on a second code point index included in the second control message having the third code point index value, to avoid receiving the second shared data channel transmission or to avoid sending acknowledgment feedback for the second shared data channel transmission.

[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving an indication of a subgroup of the UE group to which the first UE belongs, wherein the identification of which of the first multicast configuration or the first unicast configuration to apply may be based on the first UE being in the subgroup.

[0024] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving the control message may include an operation, feature, unit, or instruction for performing the following: receiving a New Data Indicator (NDI) field in the control message, wherein the identification of which of the first multicast configuration or the first unicast configuration to apply may be based on the value of the NDI field.

[0025] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the control message may include operations, features, elements, or instructions for performing the following: receiving a group common control message having a cyclic redundancy check (CRC) scrambled by a group common radio network temporary identifier (RNTI) corresponding to the UE group, the group common control message being scheduled to be transmitted using a group common shared data channel scrambled by the group common RNTI, wherein the control message includes the group common control message, and the shared data channel transmission includes the group common shared data channel transmission.

[0026] A method for wireless communication at a base station is described. The method may include: transmitting a code point configuration for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations; transmitting a control message scheduling shared data channel transmission for a group of UEs comprising a set of multiple UEs, the control message including a first code point index from the set of multiple code point indices, the first code point index indicating a transmission configuration as either a first multicast configuration from the set of multiple multicast configurations or a first unicast configuration from the set of multiple unicast configurations; and transmitting the shared data channel transmission according to the indicated transmission configuration.

[0027] An apparatus for wireless communication at a first base station is described. The apparatus may include a processor, a memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: transmit a code point configuration for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations; transmit a control message scheduling a shared data channel transmission for a group of UEs comprising a set of multiple UEs, the control message including a first code point index in the set of multiple code point indices, the first code point index indicating a transmission configuration as either a first multicast configuration in the set of multiple multicast configurations or a first unicast configuration in the set of multiple unicast configurations; and transmit the shared data channel transmission according to the indicated transmission configuration.

[0028] Another apparatus for wireless communication at a base station is described. The apparatus may include: a unit for transmitting a code point configuration for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations; a unit for transmitting a control message scheduling shared data channel transmission for a group of UEs comprising a set of multiple UEs, the control message including a first code point index from the set of multiple code point indices, the first code point index indicating a transmission configuration as either a first multicast configuration from the set of multiple multicast configurations or a first unicast configuration from the set of multiple unicast configurations; and a unit for transmitting the shared data channel transmission according to the indicated transmission configuration.

[0029] A non-transitory computer-readable medium is described, storing code for wireless communication at a base station. The code may include instructions executable by a processor to: transmit a code point configuration for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations; transmit a control message scheduling shared data channel transmission for a group of UEs comprising a set of multiple UEs, the control message including a first code point index from the set of multiple code point indices, the first code point index indicating a transmission configuration as either a first multicast configuration from the set of multiple multicast configurations or a first unicast configuration from the set of multiple unicast configurations; and transmit the shared data channel transmission according to the indicated transmission configuration.

[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting the code point configuration may include operations, features, units, or instructions for performing the following: transmitting a first code point mapping configuration that maps a first subset of the set of the plurality of code point indices to a set of the plurality of multicast configurations; and transmitting a second code point mapping configuration that maps each code point index in the set of the plurality of code point indices to a corresponding unicast configuration in the set of the plurality of unicast configurations.

[0031] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the control message may include operations, features, units, or instructions for performing the following: sending the control message including the first code point index to indicate that the transport configuration may be the first multicast configuration based on the first code point index appearing within a first subset of the set of the plurality of code point indices.

[0032] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the control message may include operations, features, units, or instructions for performing the following: sending the control message including the first code point index to indicate that the transmission configuration may be the first unicast configuration based on the fact that the first code point index appears outside the first subset of the set of the plurality of code point indices.

[0033] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting the shared data channel transmission may include operations, features, units, or instructions for transmitting the shared data channel transmission according to parameters indicated by the transmission configuration.

[0034] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the parameters include TCI status, resource allocation, MCS, PMI, or any combination thereof.

[0035] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the control message may include operations, features, units, or instructions for performing the following: sending the control message including the first code point index in a field having a bit width, the bit width being determined based on the number of first code point indices in the set of the plurality of code point indices corresponding to the set of the plurality of multicast configurations, the number of second code point indices in the set of the plurality of code point indices corresponding to the set of the plurality of unicast configurations, or both.

[0036] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, sending the control message may include operations, features, units, or instructions for performing the following: sending the control message including the first code point index in a field having a bit width, the bit width being determined based on the mapping indicating the association between a corresponding code point index in a set of a plurality of code point indices and a corresponding index value in a set of a plurality of index values.

[0037] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting the code point configuration may include operations, features, units, or instructions for transmitting an indication of the associated code point configuration.

[0038] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the association may be determined based on the ascending or descending order of parameters indicated in the code point configuration.

[0039] In some examples of the methods, apparatuses and non-transitory computer-readable media described herein, the association may be determined based on the ascending or descending order of the IDs of one or more parameters indicated in the code point configuration.

[0040] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting the code point configuration may include operations, features, units, or instructions for performing the following: transmitting the code point configuration, the code point configuration indicating a unicast value corresponding to a second code point index value in a set of the plurality of code point indices and a null value corresponding to a third code point index value in a set of the plurality of code point indices. Attached Figure Description

[0041] Figure 1 An example of a wireless communication system that supports downlink control information (DCI) indication for multicast and unicast transmissions according to various aspects of this disclosure is shown.

[0042] Figure 2A and 2B An example of a wireless communication system is shown that supports indications for multicast and unicast transmissions according to various aspects of this disclosure.

[0043] Figure 3 An example of an indication scheme that supports indications for multicast and unicast transmissions according to various aspects of this disclosure is shown.

[0044] Figure 4 An example of a process flow showing the support for instructions for multicast and unicast transmissions according to various aspects of this disclosure is shown.

[0045] Figure 5 and 6 A block diagram of an apparatus supporting instructions for multicast and unicast transmissions according to various aspects of this disclosure is shown.

[0046] Figure 7 A block diagram of a communication manager supporting instructions for multicast and unicast transmissions according to various aspects of this disclosure is shown.

[0047] Figure 8 A schematic diagram of a system including an instruction for supporting multicast and unicast transmission is shown, according to various aspects of this disclosure.

[0048] Figure 9 and 10 A block diagram of an apparatus supporting instructions for multicast and unicast transmissions according to various aspects of this disclosure is shown.

[0049] Figure 11 A block diagram of a communication manager supporting instructions for multicast and unicast transmissions according to various aspects of this disclosure is shown.

[0050] Figure 12 A schematic diagram of a system including an instruction for supporting multicast and unicast transmission is shown, according to various aspects of this disclosure.

[0051] Figures 13 to 18 A flowchart illustrating a method for providing instructions for multicast and unicast transmissions in accordance with various aspects of this disclosure is shown. Detailed Implementation

[0052] In some examples, communication between wireless devices (e.g., between a base station and one or more user equipment (UEs)) can be categorized into two types: point-to-point (PTP) communication (e.g., unicast communication) and point-to-multipoint (PTM) communication (e.g., multicast communication, broadcast communication, etc.). For PTM communication (e.g., PTM transmission scheme 1) and for UEs connected in the same multicast / broadcast service (MBS) group, the base station can use a group common downlink control channel with cyclic redundancy check (CRC) scrambled by the group common radio network temporary identifier (RNTI) to schedule a group common downlink shared channel scrambled with the same group common RNTI. This scheme can be referred to as a group scheduling scheme based on the group common downlink control channel.

[0053] Additionally, UEs receiving these PTM communications can support sending acknowledgment feedback to indicate whether the PTM communication (e.g., multicast message) was successfully received. In some cases, a wider (e.g., UE-independent) beam can be used to transmit PTM communications, allowing all UEs in the MBS group to receive multicast data. However, if at least one UE sends a negative acknowledgment (NACK) message, the base station can also use a wider beam (e.g., the same wide beam received by all UEs in the MBS group or a different wide beam) to retransmit multicast data. This would cause UEs that successfully received and decoded multicast data in the initial transmission to receive and decode the same multicast data again, thus wasting processing power and battery life by receiving and decoding the same information more than once.

[0054] As described herein, a UE can be configured (e.g., by a base station) to have a mapping between downlink control information (DCI) code point values ​​and a multicast configuration, as well as a mapping between DCI code point values ​​and a unicast configuration. The base station can then use the DCI to signal to the UE that it is applying either a multicast or unicast configuration to receive subsequent data transmissions. For example, for a given DCI field of a group common downlink control channel used for multicast data, one or more DCI code point values ​​can be associated with values ​​configured for multicast receive configuration, while the remaining code points can be associated with values ​​configured for unicast receive configuration.

[0055] Alternatively, for code points in DCI fields that have no value in the multicast configuration, the UE can be configured with a "unicast value" or "no value" (e.g., null value). If the DCI field indicates "no value," the UE may not receive multicast data scheduled by the group common downlink control channel, or the UE may not send acknowledgment feedback for multicast data scheduled by the group common downlink control channel. Alternatively, for retransmissions of multicast data, one or more DCI fields can be interpreted as the retransmission being unicast. For example, for a DCI format that schedules retransmissions of multicast data, the DCI code points can be interpreted based on a non-multicast configuration. In some examples, the New Data Indicator (NDI) field in the group common downlink control channel can indicate whether the scheduled multicast data is a retransmission.

[0056] The aspects of this disclosure are first described in the context of a wireless communication system. Additionally, the aspects of this disclosure are illustrated by further wireless communication systems, indication schemes, and process flows. The aspects of this disclosure are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to DCI indications for multicast and unicast transmissions, and described in relation to the aforementioned diagrams.

[0057] Figure 1Examples of a wireless communication system 100 supporting DCI indications for multicast and unicast transmissions according to various aspects of this disclosure are shown. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an improved LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, communication with low-cost and low-complexity devices, or any combination thereof.

[0058] Base stations 105 can be distributed throughout a geographical area to form a wireless communication system 100, and can be devices of different forms or with different capabilities. Base stations 105 and UE 115 can communicate wirelessly via one or more communication links 125. Each base station 105 can provide a coverage area 110, and UE 115 and base station 105 can establish one or more communication links 125 on the coverage area 110. The coverage area 110 can be an example of a geographical area where base stations 105 and UE 115 can support signal transmission according to one or more radio access technologies.

[0059] UE 115 can be distributed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary, mobile, or both at different times. UE 115 can be devices of different forms or with different capabilities. Figure 1 Some example UE 115s are shown in the document. The UE 115 described herein may be able to communicate with various types of devices, such as other UE 115s, base station 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices), such as... Figure 1 As shown.

[0060] Base station 105 can communicate with core network 130, communicate with each other, or perform both operations. For example, base station 105 can be connected to core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base station 105 can communicate directly (e.g., directly between base stations 105) on backhaul links 120 (e.g., via X2, Xn, or other interfaces), or indirectly (e.g., via core network 130), or perform both operations. In some examples, backhaul link 120 can be or includes one or more radio links.

[0061] One or more of the base stations 105 described herein may include, or may be referred to by those skilled in the art as, base station transceiver, radio base station, access point, radio transceiver, node B, evolved node B (eNodeB, eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), home node B, home evolved node B, or other suitable terms.

[0062] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, wherein "device" may also be referred to as a unit, station, terminal, or client, and other examples. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, and other examples, which may be implemented in various items such as appliances, vehicles, meters, and other examples.

[0063] The UE 115 described in this document may be able to communicate with various types of devices, such as other UE 115s that can sometimes act as repeaters, as well as base station 105 and network devices, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, and other examples, such as... Figure 1 As shown.

[0064] UE 115 and base station 105 can wirelessly communicate with each other via one or more communication links 125 on one or more carriers. The term "carrier" can refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers.

[0065] In some examples (e.g., in a carrier aggregation configuration), carriers may also have acquisition or control signaling that coordinates operation against other carriers. Carriers may be associated with frequency channels (e.g., Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be positioned according to a channel grid for discovery by UE 115. Carriers may operate in standalone mode, where UE 115 can initiate acquisition and connection via a carrier, or in non-standalone mode, where different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0066] The communication link 125 shown in the wireless communication system 100 may include uplink transmission from UE 115 to base station 105, or downlink transmission from base station 105 to UE 115. The carrier may carry downlink or uplink communication (e.g., in FDD mode) or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0067] A carrier can be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth can be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth can be one of a number of defined bandwidths for a specific radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) can have a hardware configuration that supports communication on a specific carrier bandwidth, or can be configured to support communication on one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 can be configured to operate on a portion (e.g., a subband, BWP) or all of the carrier bandwidth.

[0068] The signal waveform transmitted on a carrier can consist of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as Orthogonal Frequency Division Multiplexing (OFDM) or Discrete Fourier Transform Spread Spectrum OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element can include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements UE 115 receives and the higher the order of the modulation scheme, the higher the data rate can be for UE 115. Wireless communication resources can refer to a combination of radio frequency spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further increase the data rate or data integrity used for communication with UE 115.

[0069] One or more digital schemes (numerologies) can be supported for a carrier, where the digital scheme may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier can be divided into one or more BWPs with the same or different digital schemes. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communication for UE 115 can be restricted to one or more active BWPs.

[0070] It can be expressed in a basic unit of time (which can be, for example, T). s =1 / (Δf) max ·N f The sampling period is ) seconds, where Δf max This can represent the maximum supported subcarrier spacing, and N f The time interval for base station 105 or UE 115 can be represented as a multiple of the maximum supported Discrete Fourier Transform (DFT) size. The time interval for communication resources can be organized based on radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0071] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., this depends on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N) symbols. f (Number) sampling periods. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0072] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Alternatively or additionally, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst form of a shortened TTI (sTTI)).

[0073] Physical channels can be multiplexed on a carrier using various techniques. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels on a downlink carrier. A control region (e.g., a control resource set (CORESET)) for physical control channels can be defined by the number of symbol periods and can extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) can be configured for a group of UEs 115. For example, one or more of the UEs 115 can monitor or search for control regions against control information based on one or more search space sets, and each search space set can include one or more control channel candidates arranged in a cascaded manner at one or more aggregation levels. The aggregation level for control channel candidates can refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to send control information to multiple UEs 115 and a UE-specific search space set used to send control information to a specific UE 115.

[0074] Each base station 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., on a carrier) to communicate with base station 105 and may be associated with an identifier used to distinguish neighboring cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a geographic coverage area 110 or a portion of geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors (such as the capabilities of base station 105), the range of such cells can range from small areas (e.g., structures, subsets of structures) to large areas. For example, a cell may be or include buildings, subsets of buildings, or external space between or overlapping geographic coverage areas 110, and other examples.

[0075] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 115 with a service subscription to a network provider supporting the macro cell. In contrast, small cells can be associated with a lower-power base station 105 and can operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells can provide unrestricted access to UE 115 with a service subscription to a network provider, or restricted access to UE 115 associated with the small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a residence or office). Base station 105 can support one or more cells and can also support communication on one or more cells using one or more component carriers.

[0076] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0077] In some examples, base station 105 may be mobile, and therefore provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. Wireless communication system 100 may include, for example, a heterogeneous network, in which different types of base stations 105 use the same or different radio access technologies to provide coverage for various geographic coverage areas 110.

[0078] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timing, and transmissions from different base stations 105 can be approximately time-aligned. For asynchronous operation, base stations 105 can have different frame timing, and in some examples, transmissions from different base stations 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0079] Some UE 115s (e.g., MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated machine-to-machine communication (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with base station 105 without human intervention. In some examples, M2M communication or MTC can include communication from devices that have integrated sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents it to humans interacting with the application. Some UE 115s can be designed to collect information or automate the behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing.

[0080] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via either transmission or reception, rather than simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power-saving techniques for UE 115 include entering a power-saving deep sleep mode when not engaged in active communication, when operating on limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs) within a carrier, within a carrier's guard band, or outside a carrier.

[0081] Wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. UE 115 can be designed to support ultra-reliable, low-latency, or mission-critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private or group communication and can be supported by one or more mission-critical services (such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData)). Support for mission-critical functions can include service prioritization, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency are used interchangeably herein.

[0082] In some examples, UE 115 may also be able to communicate directly with other UE 115s on a device-to-device (D2D) communication link 135 (e.g., using peer-to-peer (P2P) or D2D protocols). One or more UEs 115s utilizing D2D communication may be within the geographic coverage area 110 of base station 105. Other UEs 115s in such a group may be outside the geographic coverage area 110 of base station 105 or otherwise unable to receive transmissions from base station 105. In some examples, groups of UEs 115s communicating via D2D communication may utilize a one-to-many (1:M) system, wherein each UE 115 transmits to each other UE 115 in the group. In some examples, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving base station 105.

[0083] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information related to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., base station 105) using vehicle-to-network (V2N) communication, or both.

[0084] Core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), and can include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function unit (AMF)) managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function unit (UPF)) routing packets to or interconnecting with external networks. The control plane entity can manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UE 115 served by base station 105 associated with core network 130. User IP packets can be transmitted through the user plane entity, which can provide IP address allocation and other functions. The user plane entity can connect to IP services 150 for one or more network operators. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0085] Some network devices (e.g., base station 105) may include sub-components such as access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with UE 115 through one or more other access network transport entities 145 (which may be referred to as a radio headend, smart radio headend, or transmit / receive point (TRP)). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across individual network devices (e.g., radio headends and ANCs) or incorporated into a single network device (e.g., base station 105).

[0086] Wireless communication system 100 can operate using one or more frequency bands (typically in the range of 300 MHz to 300 GHz). The region from 300 MHz to 3 GHz is typically referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range extends from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but the waves can be sufficiently permeable to penetrate structures for use in macrocells to provide service to UE 115 located indoors. Transmission of UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 km) compared to the transmission of smaller frequencies and longer waves in the lower 300 MHz portion of the spectrum, such as the High Frequency (HF) or Very High Frequency (VHF) portions.

[0087] Wireless communication system 100 can utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communication system 100 can employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating in unlicensed radio frequency spectrum bands, devices (such as base station 105 and UE 115) can employ carrier sensing for collision detection and avoidance. In some examples, operation in unlicensed frequency bands can be based on carrier aggregation configurations that combine component carriers operating in licensed frequency bands (e.g., LAA). Operation in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and other examples.

[0088] Base station 105 or UE 115 may be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels (which may support MIMO operation or transmit or receive beamforming). For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with base station 105 may be located in different geographical locations. Base station 105 may have an antenna array having a number of rows and columns of antenna ports that base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, antenna panels may support radio frequency beamforming for signals transmitted via antenna ports.

[0089] Base station 105 or UE 115 can use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such a technique can be called spatial multiplexing. For example, a transmitting device can transmit multiple signals via different antennas or different combinations of antennas. Similarly, a receiving device can receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) (where multiple spatial layers are transmitted to the same receiving device) and multi-user MIMO (MU-MIMO) (where multiple spatial layers are transmitted to multiple devices).

[0090] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., base station 105, UE 115) to form or guide an antenna beam (e.g., transmit beam, receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating relative to a specific orientation of the antenna array experience constructive interference, while others experience destructive interference. Adjustments to the signals transmitted via the antenna elements can include applying amplitude offset, phase offset, or both to the signals carried via the antenna elements associated with the transmitting or receiving device. The adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device, or relative to some other orientation).

[0091] As part of beamforming operations, base station 105 or UE 115 may use beam scanning techniques. For example, base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Base station 105 may transmit some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times in different directions. For example, base station 105 may transmit signals according to different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions may be used (e.g., by a transmitting device (such as base station 105) or by a receiving device (such as UE 115)) to identify the beam direction for subsequent transmissions or receptions performed by base station 105.

[0092] Base station 105 may transmit signals (e.g., data signals associated with a specific receiving device, such as UE 115) in a single beam direction (e.g., a direction associated with a particular receiving device, such as UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on signals transmitted in one or more beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions and may report to base station 105 an indication of the signal received by UE 115 that has the highest signal quality or otherwise acceptable signal quality.

[0093] In some examples, multiple beam directions can be used to perform transmissions by a device (e.g., base station 105 or UE 115), and the device can use a combination of digital precoding or radio frequency beamforming to generate combined beams for (e.g., from base station 105 to UE 115) transmissions. UE 115 can report feedback indicating precoding weights for one or more beam directions, and this feedback can correspond to a configured number of beams spanning the system bandwidth or one or more subbands. Base station 105 can transmit reference signals that can be precoded or unprecoded (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)). UE 115 can provide feedback on beam selection, which can be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify beam directions for subsequent transmissions or receptions by UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0094] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105, the receiving device (e.g., UE 115) can attempt multiple receiving configurations (e.g., directional listening). For example, the receiving device can attempt multiple receiving directions by receiving via different antenna subarrays, by processing the received signals according to different antenna subarrays, by receiving according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different sets of directional listening weights), or by processing the received signals according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of the antenna array (any of these operations can be referred to as "listening" according to different receiving configurations or receiving directions). In some examples, the receiving device can use a single receiving configuration to receive along a single beam direction (e.g., when receiving data signals). A single receiver configuration can be aligned to a beam direction determined based on listening in different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening in multiple beam directions).

[0095] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer can be IP-based. The Radio Link Control (RLC) layer can perform packet fragmentation and reassembly for transmission over logical channels. The Media Access Control (MAC) layer can perform priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer can provide the establishment, configuration, and maintenance of RRC connections (which support radio bearers for user plane data) between the UE 115 and the base station 105 or core network 130. At the physical layer, transport channels can be mapped to physical channels.

[0096] UE 115 and base station 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correct data reception on communication link 125. HARQ can include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal and noise conditions). In some examples, the device can support same-slot HARQ feedback, where the device can provide HARQ feedback for data received in a previous symbol within a specific time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0097] In some examples, communication between wireless devices (e.g., between a base station and one or more UEs) can be categorized into two types: PTP communication (e.g., unicast communication) and PTM communication (e.g., multicast communication, broadcast communication, etc.). For example, for PTP communication and a connected UE 115 (e.g., an RRC_CONNECTED UE), a UE-specific downlink control channel (e.g., physical downlink control channel (PDCCH)) with a CRC scrambled by a UE-specific RNTI (e.g., cell RNTI (C-RNTI)) can be used to schedule a UE-specific downlink shared channel (e.g., physical downlink shared channel (PDSCH)) scrambled using the same UE-specific RNTI. Alternatively or concurrently, for the first type of PTM communication (e.g., PTM transmission scheme 1) and for UE 115 (e.g., RRC_CONNECTED UE) in the same MBS group in a connected state, a group common downlink control channel (e.g., PDCCH) with a CRC scrambled by a group common RNTI can be used to schedule a group common downlink shared channel (e.g., PDSCH) scrambled using the same group common RNTI. This first type of PTM communication can be referred to as a group scheduling scheme based on group common PDCCH. Alternatively or concurrently, for the second type of PTM communication (e.g., PTM transmission scheme 2) and for UE 115 (e.g., RRC_CONNECTED UE) in the same MBS group in a connected state, a UE-specific downlink control channel (e.g., PDCCH) with a CRC scrambled by a UE-specific RNTI (e.g., C-RNTI) can be used to schedule a group common PDSCH scrambled using a group common RNTI. This second type of PTM communication can be referred to as a group scheduling scheme based on UE-specific PDCCH.

[0098] For the described PTP and PTM communication schemes, "UE-specific" downlink control channels (e.g., UE-specific PDCCH) and "UE-specific" downlink shared channels (e.g., UE-specific PDSCH) can refer to downlink control channels or downlink shared channels that can be individually identified by the target UE 115 (e.g., the specific UE 115) and cannot be identified by other UEs 115 in the same MBS group as the target UE 115. Additionally, "group-common" downlink control channels (e.g., group-common PDCCH) and "group-common" downlink shared channels (e.g., group-common PDSCH) can refer to downlink control channels or downlink shared channels transmitted in the same time and frequency resources and recognizable by all UEs 115 in the same MBS group. In some cases, for a UE 115 in a connected state (e.g., an RRC_CONNECTED UE), if the initial transmission for multicast messages (e.g., multicast data) is based on a first type of PTM communication (e.g., PTM transmission scheme 1), the UE 115 may also support receiving one or more retransmissions using at least the first type of PTM communication.

[0099] Additionally, for a UE 115 receiving multicast messages in a connected state (e.g., an RRC_CONNECTED UE), at least for the first type of PTM communication, UE 115 may support HARQ-ACK feedback based on acknowledgment / negative acknowledgment (ACK / NACK), HARQ-ACK feedback based solely on NACK, or both, for multicast data. For HARQ-ACK feedback based on ACK / NACK for multicast data, and from the perspective of each UE, UE 115 may feedback ACK or NACK for multicast data. Alternatively or additionally, for HARQ-ACK feedback based on ACK / NACK for multicast data, and from the perspective of UE 115 within a group (e.g., UE 115 in the same MBS group), a given UE 115 within that group may configure Physical Uplink Control Channel (PUCCH) resources (e.g., shared or separate PUCCH resources) for ACK / NACK feedback. For HARQ-ACK feedback based solely on NACK for multicast data, from the perspective of each UE, if multicast data is not successfully received, UE 115 may send a NACK, and if multicast data is successfully received, UE 115 may not send any feedback. Alternatively, for HARQ-ACK feedback based solely on NACK for multicast data, from the perspective of UE 115 within a group, a given UE 115 within that group may configure PUCCH resources for NACK-only feedback. If both ACK / NACK-based HARQ-ACK feedback and NACK-only HARQ-ACK feedback are supported, UE 115 may use a feedback scheme (e.g., UE implementation) or may be instructed to use which feedback scheme.

[0100] In some examples, a wider (e.g., UE-specific) beam can be used to transmit the multicast PDSCH (e.g., carrying multicast data), so that any UE 115 that wants to receive the multicast PDSCH (e.g., UE 115 in the same MBS group) can receive the multicast PDSCH. If a HARQ-ACK feedback scheme for multicast data is supported (e.g., HARQ-ACK feedback based on ACK / NACK or HARQ-ACK feedback based on NACK only), and if at least one UE 115 (e.g., not all UE 115) sends a NACK, the network (e.g., base station 105 or another network device) can retransmit the same multicast data. In some cases, for the retransmission of multicast data, there may be an optimal resource allocation, modulation and coding scheme (MCS), precoding (e.g., as indicated by the precoding matrix indicator (PMI), transmit beam (e.g., as indicated by the transmission configuration indicator (TCI)-state), or a combination thereof, for the UE 115 requesting retransmission.

[0101] If retransmissions of multicast data can be sent using PTM communication of the second type as previously described (e.g., PTM transmission scheme 2, group scheduling scheme based on UE-specific PDCCH, etc.), then UE-specific DCI can be used to indicate UE-specific resource allocation, MCS, precoding, TCI state, or combinations thereof for a given UE 115. However, if the initial transmission and retransmission of the same multicast data are constrained to be sent using PTM communication of the first type as previously described (e.g., PTM transmission scheme 1, group scheduling scheme based on group common PDCCH, etc.), it is unclear how to efficiently send retransmissions of multicast data without placing an unnecessary processing burden on the UE 115 that previously successfully received and decoded the multicast data.

[0102] For example, since a wider beam can be used to transmit multicast PDSCH, and the first type of PTM communication uses group common parameters (e.g., group common RNTI) to schedule multicast data transmission, when multicast data is retransmitted, base station 105 can retransmit the multicast data such that all UEs 115 within the same group (e.g., MBS group) receive the retransmission (e.g., based on the wider beam and group common parameters). Each UE 115 in that group can then at least partially decode the retransmission to identify it as a retransmission of previously transmitted multicast data. For any UE 115 that previously failed to receive multicast data, these UEs 115 can then decode the remainder of the retransmission to receive the multicast data. However, any UE 115 that previously successfully received and decoded multicast data can decode the retransmission to determine that it contains data that was already successfully received, thus wasting the processing power and battery life of those UEs 115.

[0103] The wireless communication system 100 can support efficient techniques for indicating whether a multicast or unicast configuration is to be applied to transmit shared data channel transmissions (e.g., multicast data, multicast PDSCH, unicast PDSCH, etc.). For example, UE 115 can be configured (e.g., by base station 105) to have mappings between DCI code point values ​​and multicast configurations, as well as mappings between DCI code point values ​​and unicast configurations. Base station 105 can then use the DCI to signal to UE 115 to apply either a multicast or unicast configuration to receive subsequent shared data channel transmissions (e.g., multicast PDSCH). For example, for a given DCI field of a group common downlink control channel for multicast data, one or more DCI code point values ​​can be associated with values ​​configured for multicast receive configurations, while the remaining code points are associated with values ​​configured for unicast receive configurations. In some implementations, the UE may identify which multicast or unicast configuration to apply for receiving shared data channel transmissions based on the following: the type of data transmission scheduled by the DCI (e.g., multicast data transmission or non-multicast data transmission) and mapping, the indication value of the DCI code point value set (e.g., "unicast value" or "empty value" or "no value"), whether the shared data channel transmission is a retransmission (e.g., as indicated by the NDI field), or a combination thereof.

[0104] Figure 2A and 2B Examples of wireless communication systems 200 and 201 supporting indications for multicast and unicast transmissions according to various aspects of this disclosure are shown. Wireless communication systems 200 and 201 may implement aspects of wireless communication system 100, or may be implemented by aspects of wireless communication system 100. For example, wireless communication systems 200 and 201 may include base station 105-a and one or more UEs 115, which may respectively represent examples of base station 105 and UE 115, as referenced. Figure 1 As described.

[0105] In some examples, one or more UEs 115 may be part of the same group (e.g., an MBS group) from which base station 105-a receives the same overtext multicast or broadcast data. For example, base station 105-a may use the type of PTM communication as previously described to send multicast data to one or more UEs 115. Alternatively, one or more UEs 115 may be grouped into separate subgroups 205 (e.g., based on which UEs 115 are close to each other or based on which UEs 115 have similar transmission parameters), such as a first subgroup 205-a and a second subgroup 205-b.

[0106] As in this article and Figure 2A and 2BAs described in the examples, both the initial transmission and any subsequent retransmission of the multicast PDSCH (e.g., shared data channel transmission, multicast data transmission, etc.) can be sent using the first type of PTM communication (e.g., PTM transmission scheme 1) as previously described. That is, base station 105-a can use a group common RNTI instead of a UE-specific RNTI to send a DCI 215 (e.g., DCI format) for scheduling shared data transmission 220 (e.g., multicast PDSCH). For example, the techniques described herein can enable a group common downlink control channel (e.g., group common PDCCH) with a CRC scrambled by the group common RNTI to schedule a group common downlink shared channel (e.g., group common PDSCH, shared data transmission 220, multicast PDSCH, multicast data, etc.) scrambled using the same group common RNTI. In some examples, the group common downlink control channel may include parameters for a unicast downlink shared channel (e.g., unicast PDSCH) for transmitting data (e.g., multicast data) to be carried in the group common downlink shared channel. For example, parameters used for a unicast downlink shared channel may include UE 115-specific resource allocation, MCS, precoding, or TCI state. The unicast downlink shared channel used herein may refer to a downlink shared channel scheduled or configured using C-RNTI, configured scheduled RNTI (CS-RNTI), or MCS-C-RNTI.

[0107] In some implementations, one or more UEs 115 in a group receiving the same multicast or broadcast data from base station 105-a can be configured with multicast and non-multicast configurations (e.g., unicast configurations). The multicast configuration can represent a configuration for multicast PDSCH (e.g., scheduling or configuration using a group common RNTI), and the non-multicast configuration can represent a configuration for non-multicast PDSCH (e.g., scheduling or configuration using C-RNTI, CS-RNTI, MCS-C-RNTI, etc.). Additionally, base station 105-a can provide multicast configurations to one or more UEs 115 via RRC signaling as part of the multicast PDSCH configuration, and can also provide unicast configurations to one or more UEs 115 via RRC signaling as part of the unicast PDSCH configuration.

[0108] When receiving multicast and unicast configurations, one or more UEs 115 can also receive or determine a mapping between different codepoint values ​​(e.g., codepoint indices) and each multicast configuration in the multicast configuration and each unicast configuration in the unicast configuration. In some examples, the codepoint value can be a DCI field codepoint, a DCI codepoint index, or other DCI values. Table 1 shows examples of mappings between different codepoint values ​​and each multicast configuration in the multicast configuration and each unicast configuration in the unicast configuration.

[0109] Table 1 - Example Code Point Mapping Configuration

[0110]

[0111] As shown in Table 1, for a given DCI field of a group common PDCCH used for multicast PDSCH, one or more code points can be associated with values ​​configured for multicast PDSCH reception, while the remaining code points can be associated with values ​​configured for unicast PDSCH reception. For the DCI format of scheduled non-multicast PDSCH, UE 115 can interpret the DCI code points based on values ​​used for non-multicast configuration (e.g., values ​​1, 2, 3, or 4 used for non-multicast configuration). Alternatively, for the DCI format of scheduled multicast PDSCH, UE 115 can interpret the DCI field as indicating a multicast or non-multicast configuration based on the DCI code points. For example, using Table 1 as an example and for the DCI format of scheduled multicast PDSCH, UE 115 can interpret “00” and “01” as indicating a multicast configuration for scheduled multicast PDSCH, and can interpret “10” and “11” as indicating a non-multicast configuration for scheduled multicast PDSCH. Each value may correspond to a different configuration for sending the multicast PDSCH, such as the corresponding resource allocation, MCS, precoding (e.g., determined via the corresponding PMI) or TCI state (e.g., beam), where the multicast configuration applies to all UE 115 in the MBS group and the unicast configuration applies to a single UE 115 or a subset of UE 115 in the MBS group (e.g., subgroup 205).

[0112] In some examples, a non-multicast configuration can be specified for each subgroup 205. For instance, base station 105-a can configure a non-multicast configuration for UE 115 based on which subgroup 205 is configured to receive the same multicast or broadcast data from base station 105-a (e.g., an MBS group). Figure 2A and 2BAs shown in the example, UE115 in the first subgroup 205-a can be configured with a first set of values ​​for non-multicast configuration mapped to each DCI value, and UE in the second subgroup 205-b can be configured with a second set of values ​​for non-multicast configuration mapped to each DCI value (e.g., DCI field code point, code point index, etc.).

[0113] In some implementations, DCI values ​​may correspond to TCI status fields (e.g., code point indexes), and each value used for multicast and non-multicast configurations may correspond to a different TCI status (e.g., a different beam). A TCI status indicated for a multicast configuration may correspond to a wider beam that can be used to reach all UEs 115 in a group (e.g., an MBS group) receiving the same multicast or broadcast data from base station 105-a, and a TCI status indicated for a unicast configuration may correspond to a narrower beam that can be used to reach a single UE 115 or a subset of UEs 115 (e.g., subgroup 205 or a subgroup of UEs 115 within subgroup 205). Table 2 shows examples of the mapping between different code point values ​​(e.g., TCI status fields) and each multicast configuration (e.g., the corresponding TCI status for multicast transmission) in the multicast configuration and each unicast configuration (e.g., the corresponding TCI status for non-multicast transmission) in the unicast configuration, where the unicast configuration is also configured or indicated for each subgroup 205 (e.g., or a different grouping configuration).

[0114] Table 2 - Example Code Point and TCI State Mapping Configuration

[0115]

[0116] In Table 2, for a given UE 115 in a group (e.g., an MBS group) receiving the same multicast or broadcast data from base station 105-a, a TCI state for unicast PDSCH and one or more TCI states for multicast PDSCH can be configured. If the code point of the TCI state field (e.g., in a control message scheduling multicast data transmission, such as a multicast PDCCH or DCI or both) has an associated TCI state configured for multicast PDSCH, then UE 115 can assume that the TCI state for multicast PDSCH is used for transmitting subsequent multicast data transmission. Alternatively, if the code point of the TCI state field does not have an associated TCI state configured for multicast PDSCH, then UE 115 can assume that the TCI state for unicast PDSCH is used for transmitting subsequent multicast data transmission (e.g., using PTM transmission scheme 1), where the corresponding configured TCI state for the group is used by UE 115.

[0117] In some implementations, the bit width used for the size of the DCI field (e.g., to indicate which multicast or unicast configuration to apply) can be determined by the maximum of the number of necessary code points required for the DCI field indication. For example, if two (2) code points are necessary to indicate a multicast PDSCH sent using a multicast configuration (e.g., two multicast configurations are configured), and four (4) code points are necessary to indicate a unicast PDSCH sent using a unicast configuration (e.g., carrying multicast data in some implementations described herein) (e.g., four unicast configurations are configured), then the DCI field size can be two (2) bits (e.g., to indicate four possible configurations). Alternatively or additionally, the bit width used for the size of the DCI field can be determined based on the association between code points and index values ​​that are explicitly configured (e.g., via RRC signaling). For example, the association between code points in a DCI field and configured index values ​​can be determined based on ascending or descending order of parameters in the configuration (e.g., RRC parameters), or based on descending or ascending order of identifiers (IDs) of parameters in a parameter list (e.g., an RRC parameter list), or can be explicitly configured, or a combination thereof.

[0118] Additionally, in some implementations, base station 105-a can configure specific values ​​for any DCI value that does not have an associated value for multicast configuration (e.g., or TCI state). For example, for a code point in a DCI field that has no value in a multicast configuration, UE 115 can be configured with a "unicast value" or "no value" (e.g., null value). In some examples, these specific values ​​(e.g., "unicast value" or "no value") can be configured to be specific to which subgroup 205 UE 115 belongs. Table 3 shows examples of mappings between different code point values ​​(e.g., TCI state fields) and each multicast configuration (e.g., the corresponding TCI state for multicast transmission) and each unicast configuration (e.g., the corresponding TCI state for non-multicast transmission) in the multicast configuration, where both the unicast and multicast configurations are configured or indicated for each subgroup 205 (e.g., or different grouping configurations).

[0119] Table 3 - Examples of UE subgroup-specific code point and TCI state mapping configurations

[0120]

[0121]

[0122] Using Table 3, if the TCI status field (e.g., DCI value, DCI field code point, code point index, etc.) corresponds to a “unicast value” for multicast configuration, then UE 115 may assume that the unicast PDSCH configured for the corresponding subgroup 205 to which UE 115 belongs is used to transmit multicast data (e.g., shared data transmission 220). Alternatively, if the TCI status field corresponds to “no value”, then UE 115 may avoid receiving multicast data (e.g., multicast PDSCH, shared data transmission 220, etc.) scheduled by a control channel carrying the TCI status field (e.g., a multicast PDCCH carrying an indication of which DCI configuration to apply), or UE 115 may not send HARQ-ACK feedback for multicast data scheduled by the control channel, or both. For unexpected UE 115 (e.g., UE 115 to which this particular instance of multicast data transmission is directed), multicast data reception or HARQ-ACK transmission may be omitted.

[0123] exist Figure 2A In the example, base station 105-a can use wide beam 210 to send shared data transmission 220 to a set of UEs 115 subscribed to an MBS group in order to receive multicast or broadcast data from base station 105-a. In some examples, base station 105-a can use wide beam 210 for the initial transmission of shared data transmission 220 or for retransmissions of shared data transmission 220. For example, wide beam 210 can be used for the initial transmission, giving each UE 115 in the MBS group an opportunity to receive shared data transmission 220. Alternatively or additionally, if multiple NACKs for previous transmissions of shared data transmission 220 are received from multiple corresponding UEs 115, base station 105-a can determine to use wide beam 210 for retransmissions of shared data transmission 220, so that those UEs 115 that sent NACKs can attempt to receive shared data transmission in the retransmission.

[0124] To indicate that the shared data transmission 220 is transmitted according to the wide beam 210 (e.g., or additional transmission parameters for indicating a multicast configuration), base station 105-a may transmit DCI 215-a in the control channel (e.g., multicast PDSCH) that schedules the shared data transmission 220. DCI 215-a includes a set of code point values ​​(e.g., DCI values, code point indices, etc.) mapped to different multicast and unicast configurations indicated to each UE 115 (e.g., via RRC signaling as previously described). For example, using Tables 1, 2, and 3 previously described, base station 105-a may indicate '00' or '01' in DCI 215-a to indicate that the shared data transmission 220 is transmitted using a multicast configuration.

[0125] Alternatively or alternatively, in Figure 2BIn one example, base station 105-a may use a narrower beam 225 (e.g., compared to a wider beam 210, such as a UE-specific beam) to transmit shared data transmission 220 to a subset of UEs 115 subscribed to an MBS group. In some examples, base station 105-a may use the narrower beam 225 for retransmissions of shared data transmission 220. For example, base station 105-a may receive one or more NACKs for the initial transmission of shared data transmission 220, but may receive one or more NACKs from UEs 115 within a subset of UEs 115 (e.g., in a second subgroup 205-b). Accordingly, base station 105-a may transmit shared data transmission 220 directed to a subset of UEs 115 (e.g., using a narrower beam 225, such as a UE-specific beam directed to a specific UE 115 within the subset of UEs 115), instead of using the wide beam 210 received by all UEs 115 in the MBS group. This could result in unnecessary power consumption and processing for those UEs 115 that have successfully received the shared data transmission 220 (e.g., UEs 115 in the first subgroup 205-a).

[0126] To indicate that the shared data transmission 220 is transmitted according to a narrower beam 225 (e.g., or additional transmission parameters for indicating a non-multicast configuration, such as parameters for indicating a UE-specific beam), base station 105-a may transmit DCI 215-b in a control channel (e.g., multicast PDSCH) that schedules the shared data transmission 220. DCI 215-b includes a set of code point values ​​(e.g., DCI values, code point indices, etc.) mapped to different multicast and unicast configurations indicated to each UE 115 (e.g., via RRC signaling as previously described). For example, using Tables 1, 2, and 3 previously described, base station 105-a may indicate '10' or '11' in DCI 215-a to indicate that the shared data transmission 220 is transmitted using a non-multicast configuration (e.g., specific to different subgroups 205 as shown in Tables 2 and 3).

[0127] Figure 3 An example of an indication scheme 300 supporting indications for multicast and unicast transmissions according to various aspects of this disclosure is shown. Indication scheme 300 may be implemented by, or may be implemented by, various aspects of wireless communication systems 100, 200, and 201. For example, indication scheme 300 may include a base station 105-b and one or more UEs 115, which may respectively represent as referred to in the reference... Figure 1-2BExamples of base station 105 and UE 115 described. Additionally, one or more UEs 115 may be part of the same group (e.g., an MBS group) receiving the same multicast or broadcast data from base station 105-b. For example, base station 105-b may use a type of PTM communication (e.g., PTM transmission scheme 1) as previously described to send multicast data to one or more UEs 115. Furthermore, one or more UEs 115 may be grouped into separate subgroups 305 (e.g., based on which UEs 115 are close to each other or based on which UEs 115 have similar transmission parameters), such as a first subgroup 305-a and a second subgroup 305-b. In some examples, base station 105-b may use a wide beam 310 to send shared data transmission 320 to one or more UEs 115, or may use different beams to send shared data transmission 320 to a subset of the one or more UEs 115.

[0128] In some implementations, for retransmissions of shared data transmission 320 (e.g., multicast PDSCH, multicast data, etc.), one or more DCI fields in the control message scheduling the shared data transmission 320 can be interpreted as if the shared data transmission was sent according to a non-multicast configuration (e.g., unicast configuration). In some examples, base station 105-a can indicate whether the shared data transmission 320 is an initial transmission or a retransmission based on whether the NDI 325 (e.g., the NDI field) field in DCI 315 switches from the last DCI format of the shared data transmission 320 (e.g., multicast PDSCH) with the same HARQ process ID.

[0129] As previously referred to Figure 2A and 2B As described, one or more UEs 115 in a group receiving the same multicast or broadcast data from base station 105-b can be configured with multicast and non-multicast configurations (e.g., unicast configurations). The multicast configuration can represent a configuration for multicast PDSCH (e.g., scheduling or configuration using group common RNTI), and the non-multicast configuration can represent a configuration for non-multicast PDSCH (e.g., scheduling or configuration using C-RNTI, CS-RNTI, MCS-C-RNTI, etc.). Additionally, base station 105-b can provide multicast configurations to one or more UEs 115 via RRC signaling as part of the multicast PDSCH configuration, and can also provide unicast configurations to one or more UEs 115 via RRC signaling as part of the unicast PDSCH configuration.

[0130] When receiving multicast and unicast configurations, one or more UEs 115 can also receive or determine a mapping (e.g., via codepoint configuration) between different codepoint values ​​(e.g., codepoint indices) and each multicast configuration in the multicast configuration and each unicast configuration in the unicast configuration. In some examples, the codepoint value may be a DCI field codepoint, a DCI codepoint index, or other DCI values. Table 4 shows examples of mappings between different codepoint values ​​and each multicast configuration in the multicast configuration and each unicast configuration in the unicast configuration.

[0131] Table 4 - Examples of code point mapping configurations

[0132]

[0133] For reference Figure 2A and 2B Unlike Tables 1, 2, and 3, Table 4 may include specific values ​​for multicast and non-multicast configurations mapped to each DCI code point. For example, base station 105-b may be configured with specific values ​​instead of values ​​not defined for multicast configurations mapped to DCI code points "10" and "11," or with a "unicast value" or "no value" configured for multicast configurations mapped to DCI code points "10" and "11." Therefore, for the initial transmission of the shared data transmission 320 in the DCI format (e.g., NDI 325 is switched), UE 115 may interpret the DCI code points based on the multicast configuration values. Alternatively, for the retransmission of the shared data transmission 320 in the DCI format (e.g., NDI 325 is not switched), UE 115 may interpret the DCI code points based on the non-multicast configuration.

[0134] For example, base station 105-b can send DCI 315 to schedule shared data transmission 320 based on the mapping of DCI code points included in DCI 315 to corresponding values ​​for multicast or non-multicast configuration. To indicate to UE 115 which multicast or non-multicast configuration value to apply for receiving shared data transmission 320, base station 105-b can include NDI 325 in DCI 315 to indicate whether shared data transmission 320 is an initial transmission of multicast data or a retransmission of multicast data. If NDI 325 indicates that shared data transmission 320 is an initial transmission, UE 115 can use the multicast configuration value to apply for receiving shared data transmission 320. Alternatively, if NDI 325 indicates that shared data transmission 320 is a retransmission, UE 115 can use the non-multicast configuration value to apply for receiving shared data transmission 320.

[0135] Figure 4Examples of process flow 400 supporting indications for multicast and unicast transmissions according to various aspects of this disclosure are shown. In some examples, process flow 400 may implement aspects of wireless communication systems 100, 200, and 201. For example, process flow 400 may include base station 105-c and UE 115-a, which may be examples of corresponding base station 105 and UE 115, as referenced above. Figures 1 to 3 As stated above.

[0136] In the following description of process flow 400, the operations between UE 115-a and base station 105-c may be performed in different orders or at different times. Some operations may also be excluded from process flow 400, or other operations may be added to process flow 400. It is to be understood that although UE 115-a and base station 105-c are shown to perform multiple operations of process flow 400, any wireless device can perform the operations shown.

[0137] At 405, UE 115-a can receive code point configuration for the PTM transmission scheme from base station 105-c. This code point configuration indicates the mapping between the code point index set, the multicast configuration set, and the unicast configuration set.

[0138] At 410, UE 115-a can receive a control message from base station 105-c. This control message schedules shared data channel transmission for at least one UE in a UE group comprising a set of UEs, including a first UE. The control message includes a first code point index from a set of code point indices. In some examples, the shared data channel transmission may include a shared data channel associated with a group common RNTI (e.g., a parameter similar to a group UE ID). For example, UE 115-a can receive a group common control message from base station 105-c having a CRC scrambled by a group common RNTI corresponding to the UE group, and this group common control information can schedule group common shared data channel transmission scrambled using the group common RNTI, wherein the control message includes a group common control message, and the shared data channel transmission includes group common shared data channel transmission.

[0139] In some implementations, UE 115-a can receive from base station 105-c a control message that includes a first code point index in a field having a bit width, the bit width being determined based on the number of first code point indices in the code point index set corresponding to a multicast configuration set, the number of second code point indices in the code point index set corresponding to a unicast configuration set, or both.

[0140] Alternatively or alternatively, UE 115-a may receive from base station 105-c a control message including a first code point index in a field having a bit width, the bit width being determined based on a mapping indicating the association between corresponding code point indices in a set of code point indices and corresponding index values ​​in a set of index values. For example, UE 115-a may receive a code point configuration indicating the association. In some implementations, the association may be determined based on the ascending or descending order of the parameters indicated in the code point configuration. Alternatively or alternatively, the association may be determined based on the ascending or descending order of the identifiers of one or more parameters indicated in the code point configuration.

[0141] In some implementations, UE 115-a may receive a code point configuration from base station 105-c at 405, which indicates a unicast value corresponding to a second code point index value in the code point index set and a null value corresponding to a third code point index value in the code point index set. Subsequently, UE 115-a may receive a second control message from base station 105-c scheduled for transmission on the second shared data channel for the UE group, and UE 115-a may determine whether to avoid receiving the second shared data channel transmission or avoid sending acknowledgment feedback for the second shared data channel transmission based on the fact that the second code point index included in the second control message has a third code point index value.

[0142] At 415, UE 115-a can receive an indication from base station 105-c of a subgroup of the UE group to which UE 115-a belongs. For example, base station 105-a can assign each UE 115 in the UE group to a corresponding subgroup. In some implementations, each subgroup may include a subset of the UE group based on which UE 115s are geographically close to each other or which UE 115s have similar transmission parameters.

[0143] At 420, UE 115-a can receive the NDI field from the control message from base station 105-c. For example, the NDI can indicate whether the shared data channel transmission is a retransmission of a previous shared data channel transmission.

[0144] At 425, UE 115-a can identify, based on the mapping and the first code point index, the transmission configuration to be applied (e.g., from base station 105-c) to receive shared data channel transmissions. This transmission configuration is one of a first multicast configuration in a multicast configuration set or a first unicast configuration in a unicast configuration set. In some implementations, identifying which of the first multicast configurations or first unicast configurations to apply can be based on UE 115-a's position in the subgroup. Alternatively or additionally, identifying which of the first multicast configurations or first unicast configurations to apply can be based on the value of the NDI field. Furthermore, the first unicast configuration (e.g., or any unicast configuration in the unicast configuration set) can include configurations (e.g., parameters similar to the UE ID) for shared data channel transmissions associated with the C-RNTI.

[0145] In some implementations, when a codepoint configuration is received at 405, UE 115-a can receive a first codepoint mapping configuration and a second codepoint mapping configuration. The first codepoint mapping configuration maps a first subset of the codepoint index set to a multicast configuration set, and the second codepoint mapping configuration maps each codepoint index in the codepoint index set to a corresponding unicast configuration in the unicast configuration set. Subsequently, at 425, UE 115-a can identify that the transport configuration is a first multicast configuration based on the first codepoint index appearing within the first subset of the codepoint index set. Alternatively, at 425, UE 115-a can identify that the transport configuration is a first unicast configuration based on the first codepoint index appearing outside the first subset of the codepoint index set.

[0146] At 430, UE 115-a can receive shared data channel transmissions from base station 105-c according to the identified transmission configuration. For example, UE 115-a can receive shared data channel transmissions according to parameters indicated by the identified transmission configuration. In some examples, parameters may include TCI status, resource allocation, MCS, PMI, or any combination thereof.

[0147] Figure 5 A block diagram 500 of a device 505 supporting indications for multicast and unicast transmissions according to various aspects of this disclosure is shown. Device 505 may be an example of various aspects of UE 115 as described herein. Device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. Device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0148] Receiver 510 may provide a unit for receiving information such as packets, user data, control information associated with various information channels (e.g., control channels, data channels, and information channels associated with indications for multicast and unicast transmissions), or any combination thereof. Information may be transmitted to other components of device 505. Receiver 510 may utilize a single antenna or a collection of multiple antennas.

[0149] Transmitter 515 may provide a unit for transmitting signals generated by other components of device 505. For example, transmitter 515 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with indications for multicast and unicast transmissions). In some examples, transmitter 515 may be co-located with receiver 510 in a transceiver module. Transmitter 515 may utilize a single antenna or a collection of multiple antennas.

[0150] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of units for performing various aspects of instructions for multicast and unicast transmissions as described herein. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0151] In some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may be implemented in hardware (e.g., in communication management circuitry). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise support units for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., executing instructions stored in memory via the processor).

[0152] Alternatively or additionally, in some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 520, receiver 510, transmitter 515, or various combinations thereof or components thereof may be performed by a general-purpose processor, DSP, central processing unit (CPU), ASIC, FPGA, or any combination of these or other programmable logic devices (e.g., units configured or otherwise supported for performing the functions described in this disclosure).

[0153] In some examples, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, transmitter 515, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, the communication manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated with the receiver 510, transmitter 515, or both to receive information, send information, or perform various other operations described herein.

[0154] According to the examples disclosed herein, the communication manager 520 may support wireless communication at a first UE. For example, the communication manager 520 may be configured or otherwise support elements for receiving code point configurations for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations. The communication manager 520 may be configured or otherwise support elements for receiving control messages that schedule shared data channel transmissions for at least one UE in a group of UEs comprising a set of multiple UEs, including the first UE, the control messages including a first code point index from the set of multiple code point indices. The communication manager 520 may be configured or otherwise support elements for identifying a transmission configuration to be applied to receiving shared data channel transmissions based on the mapping and the first code point index, the transmission configuration being one of a first multicast configuration from the set of multiple multicast configurations or a first unicast configuration from the set of multiple unicast configurations. The communication manager 520 may be configured or otherwise support elements for receiving shared data channel transmissions according to the identified transmission configuration.

[0155] By including or configuring the communication manager 520 according to the examples described herein, device 505 (e.g., a processor that controls or is otherwise coupled to receiver 510, transmitter 515, communication manager 520, or a combination thereof) can support techniques for improving reliability, reducing processing, and lowering power consumption. For example, device 505 can be configured more specifically to have improved reliability based on the transmission of multicast data. Additionally or alternatively, if device 505 has successfully received multicast data, device 505 can avoid receiving subsequent transmissions of multicast data, or the transmission of multicast data can be de-directed to device 505, thereby saving the processing power and power consumption incurred in decoding the transmission to obtain the received multicast data.

[0156] Figure 6 A block diagram 600 of a device 605 supporting indications for multicast and unicast transmissions according to various aspects of this disclosure is shown. Device 605 may be an example of various aspects of device 505 or UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. Device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0157] Receiver 610 may provide a unit for receiving information such as packets, user data, control information associated with various information channels (e.g., control channels, data channels, and information channels associated with indications for multicast and broadcast transmissions), or any combination thereof. Information may be transmitted to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0158] Transmitter 615 may provide a unit for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with indications for multicast and unicast transmissions). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0159] Device 605 or its various components may be examples of units for performing various aspects of instructions for multicast and unicast transmissions as described herein. For example, communication manager 620 may include code point configuration component 625, control message receiving component 630, transmission configuration identifier 635, shared data channel receiving component 640, or any combination thereof. Communication manager 620 may be examples of various aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use receiver 610, transmitter 615, or both, or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, communication manager 620 may receive information from receiver 610, send information to transmitter 615, or be integrated with receiver 610, transmitter 615, or both to receive information, send information, or perform various other operations as described herein.

[0160] According to the examples disclosed herein, the communication manager 620 may support wireless communication at the first UE. The code point configuration component 625 may be configured or otherwise supported for receiving code point configurations for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations. The control message receiving component 630 may be configured or otherwise supported for receiving control messages that schedule shared data channel transmissions for at least one UE in a group of UEs comprising a set of multiple UEs, including the first UE, the control messages including a first code point index from the set of multiple code point indices. The transmission configuration identifier 635 may be configured or otherwise supported for identifying a transmission configuration to be applied to receiving shared data channel transmissions based on the mapping and the first code point index, the transmission configuration being a first multicast configuration from a set of multiple multicast configurations or a first unicast configuration from a set of multiple unicast configurations. The shared data channel receiving component 640 may be configured or otherwise supported for receiving shared data channel transmissions according to the identified transmission configuration.

[0161] Figure 7A block diagram 700 of a communication manager 720 supporting indications for multicast and unicast transmissions according to various aspects of this disclosure is shown. The communication manager 720 may be an example of aspects of the communication manager 520, communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of units for performing various aspects of indications for multicast and unicast transmissions as described herein. For example, the communication manager 720 may include a code point configuration component 725, a control message receiving component 730, a transport configuration identifier 735, a shared data channel receiving component 740, a field size determination component 745, a specific code point value component 750, a subgroup indication component 755, an NDI component 760, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0162] According to the examples disclosed herein, the communication manager 720 may support wireless communication at the first UE. The code point configuration component 725 may be configured or otherwise supported for receiving code point configurations for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations. The control message receiving component 730 may be configured or otherwise supported for receiving control messages that schedule shared data channel transmissions for at least one UE in a group of UEs comprising a set of multiple UEs, including the first UE, the control messages including a first code point index from the set of multiple code point indices. The transmission configuration identifier 735 may be configured or otherwise supported for identifying a transmission configuration to be applied to receiving shared data channel transmissions based on the mapping and the first code point index, the transmission configuration being a first multicast configuration from a set of multiple multicast configurations or a first unicast configuration from a set of multiple unicast configurations. The shared data channel receiving component 740 may be configured or otherwise supported for receiving shared data channel transmissions according to the identified transmission configuration.

[0163] In some examples, to support receive codepoint configurations, the codepoint configuration component 725 may be configured or otherwise supported to support a unit for receiving a first codepoint mapping configuration that maps a first subset of a set of multiple codepoint indices to a set of multiple multicast configurations. In some examples, to support receive codepoint configurations, the codepoint configuration component 725 may be configured or otherwise supported to support a unit for receiving a second codepoint mapping configuration that maps each codepoint index in the set of multiple codepoint indices to a corresponding unicast configuration in the set of multiple unicast configurations.

[0164] In some examples, to support the identification of transport configurations, the transport configuration recognizer 735 may be configured or otherwise supported to identify a unit of a first multicast configuration based on the first code point index appearing in a first subset of a set of multiple code point indices.

[0165] In some examples, to support the identification of transport configurations, the transport configuration recognizer 735 may be configured or otherwise supported to identify a unit that is a first unicast configuration based on the fact that the first code point index appears outside a first subset of the set of multiple code point indices.

[0166] In some examples, in order to support receiving shared data channel transmissions, the shared data channel receiving component 740 may be configured or otherwise supported to receive shared data channel transmissions according to parameters indicated by the identified transmission configuration.

[0167] In some examples, parameters include TCI status, resource allocation, MCS, PMI, or any combination thereof.

[0168] In some examples, to support the reception of control messages, the field size determination component 745 may be configured or otherwise supported for receiving control messages that include a first code point index in a field having a bit width, the bit width being determined based on the number of first code point indices corresponding to a set of multiple multicast configurations in a set of multiple code point indices, the number of second code point indices corresponding to a set of multiple unicast configurations in a set of multiple code point indices, or both.

[0169] In some examples, to support the reception of control messages, the field size determination component 745 may be configured or otherwise supported for receiving control messages that include a first code point index in a field having a bit width, the bit width being determined based on a mapping between a corresponding code point index in a set of multiple code point indices and a corresponding index value in a set of multiple index values.

[0170] In some examples, to support receive code point configuration, the field size determination component 745 can be configured or otherwise support a unit for receiving code point configuration associated with the indication.

[0171] In some examples, the association is determined based on the ascending or descending order of the parameters indicated in the code point configuration.

[0172] In some examples, the association is determined based on the ascending or descending order of the IDs of one or more parameters indicated in the code point configuration.

[0173] In some examples, to support receive code point configuration, a specific code point value component 750 may be configured or otherwise support a unit for receive code point configuration, wherein the code point configuration indicates a unicast value corresponding to a second code point index value in a set of multiple code point indices and a null value corresponding to a third code point index value in a set of multiple code point indices.

[0174] In some examples, the specific code point value component 750 may be configured or otherwise supported as a unit for receiving a second control message scheduled for a second shared data channel transmission for a UE group. In some examples, the specific code point value component 750 may be configured or otherwise supported as a unit for determining whether to avoid receiving a second shared data channel transmission or avoid sending an acknowledgment feedback for a second shared data channel transmission based on a second code point index included in the second control message having a third code point index value.

[0175] In some examples, the subgroup indication component 755 may be configured or otherwise supported for receiving an indication of a subgroup of a UE group to which the first UE belongs, wherein identifying which of the first multicast configuration or the first unicast configuration to apply is based on the first UE being in that subgroup.

[0176] In some examples, to support receiving control messages, the NDI component 760 can be configured or otherwise supports a unit for receiving NDI fields in control messages, wherein identifying which of the first multicast configuration or the first unicast configuration to apply is based on the value of the NDI field.

[0177] In some examples, to support receiving control messages, the control message receiving component 730 may be configured or otherwise supported for receiving group common control messages with a CRC scrambled by a group common RNTI corresponding to the UE group, the group common control message scheduling utilizing a group common shared data channel scrambled by the group common RNTI, wherein the control message includes group common control messages, and the shared data channel transmission includes group common shared data channel transmission.

[0178] Figure 8A schematic diagram of a system 800 including indications for device 805 supporting multicast and unicast transmissions is shown according to various aspects of this disclosure. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may wirelessly communicate with one or more base stations 105, UE 115, or any combination thereof. Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, a memory 830, a code 835, and a processor 840. These components may communicate electronically via one or more buses (e.g., bus 845) or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0179] I / O controller 810 can manage input and output signals for device 805. I / O controller 810 can also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 can utilize, for example... This can be an operating system such as I / O controller 810 or another known operating system. Alternatively, I / O controller 810 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, I / O controller 810 may be implemented as part of a processor (such as processor 840). In some cases, a user may interact with device 805 via I / O controller 810 or via hardware components controlled by I / O controller 810.

[0180] In some cases, device 805 may include a single antenna 825. However, in other cases, device 805 may have more than one antenna 825, which are capable of transmitting or receiving multiple wireless transmissions simultaneously. Transceiver 815 may communicate bidirectionally via one or more antennas 825, wired or wireless links as described herein. For example, transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 815 may also include a modem for modulating packets, providing modulated packets to one or more antennas 825 for transmission, and demodulating packets received from one or more antennas 825. Transceiver 815, or transceiver 815 and one or more antennas 825, may be an example of transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof or components thereof as described herein.

[0181] Memory 830 may include random access memory (RAM) and read-only memory (ROM). Memory 830 may store computer-readable, computer-executable code 835, which includes instructions that, when executed by processor 840, cause device 805 to perform the various functions described herein. Code 835 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 835 may not be directly executable by processor 840, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, in addition, memory 830 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0182] Processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 840 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 840. Processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting instructions for multicast and unicast transmissions). For example, device 805 or components of device 805 may include processor 840 and memory 830 coupled to processor 840, processor 840 and memory 830 being configured to perform the various functions described herein.

[0183] According to the examples disclosed herein, the communication manager 820 can support wireless communication at a first UE. For example, the communication manager 820 can be configured or otherwise supported to support elements for receiving code point configurations for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations. The communication manager 820 can be configured or otherwise supported to support elements for receiving control messages that schedule shared data channel transmissions for at least one UE in a group of UEs comprising a set of multiple UEs, including the first UE, the control messages including a first code point index from the set of multiple code point indices. The communication manager 820 can be configured or otherwise supported to support elements for identifying a transmission configuration to be applied to receiving shared data channel transmissions based on the mapping and the first code point index, the transmission configuration being one of a first multicast configuration from the set of multiple multicast configurations or a first unicast configuration from the set of multiple unicast configurations. The communication manager 820 can be configured or otherwise supported to support elements for receiving shared data channel transmissions according to the identified transmission configuration.

[0184] By including or configuring the communication manager 820 according to the examples described herein, device 805 can support techniques for improving communication reliability, improving and reducing processing-related user experience, reducing power consumption, and other advantages. For example, using code point configuration, the transmission of multicast data can be more specifically configured for devices that have not yet fully received the multicast data. Therefore, multicast data-based transmission is more suitable for these devices, which can have improved communication reliability. Additionally, devices that have previously successfully received multicast data can ignore the transmission of multicast data, or the transmission can be omitted from those devices, and thus, these devices can have reduced processing and reduced power consumption.

[0185] In some examples, the communication manager 820 may be configured to cooperate with transceiver 815, one or more antennas 825, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 820 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported or performed by processor 840, memory 830, code 835, or any combination thereof. For example, code 835 may include instructions executable by processor 840 to cause device 805 to perform various aspects of the indications for multicast and unicast transmissions as described herein, or processor 840 and memory 830 may be otherwise configured to perform or support such operations.

[0186] Figure 9A block diagram 900 of a device 905 supporting indications for multicast and unicast transmissions according to various aspects of this disclosure is shown. Device 905 may be an example of various aspects of base station 105 as described herein. Device 905 may include a receiver 910, a transmitter 915, and a communication manager 920. Device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0187] Receiver 910 may provide a unit for receiving information such as packets, user data, control information associated with various information channels (e.g., control channels, data channels, and information channels associated with indications for multicast and unicast transmissions), or any combination thereof. Information may be transmitted to other components of device 905. Receiver 910 may utilize a single antenna or a collection of multiple antennas.

[0188] Transmitter 915 may provide a unit for transmitting signals generated by other components of device 905. For example, transmitter 915 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with indications for multicast and unicast transmissions). In some examples, transmitter 915 may be co-located with receiver 910 in a transceiver module. Transmitter 915 may utilize a single antenna or a collection of multiple antennas.

[0189] The communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or various components thereof, may be examples of units for performing various aspects of instructions for multicast and unicast transmissions as described herein. For example, the communication manager 920, receiver 910, transmitter 915, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0190] In some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include a processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured or otherwise supporting units for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., executing instructions stored in memory via the processor).

[0191] Alternatively or additionally, in some examples, the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 920, receiver 910, transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination of these or other programmable logic devices (e.g., a unit configured or otherwise supported for performing the functions described in this disclosure).

[0192] In some examples, the communication manager 920 can be configured to use or otherwise cooperate with the receiver 910, transmitter 915, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, the communication manager 920 can receive information from the receiver 910, send information to the transmitter 915, or integrate with the receiver 910, transmitter 915, or both to receive information, send information, or perform various other operations as described herein.

[0193] According to the examples disclosed herein, the communication manager 920 can support wireless communication at a base station. For example, the communication manager 920 can be configured or otherwise supported to support elements for transmitting code point configurations for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations. The communication manager 920 can be configured or otherwise supported to support elements for transmitting control messages that schedule shared data channel transmission for a group of UEs comprising a set of multiple UEs, the control messages including a first code point index from the set of multiple code point indices, the first code point index indicating a transmission configuration as one of a first multicast configuration from the set of multiple multicast configurations or a first unicast configuration from the set of multiple unicast configurations. The communication manager 920 can be configured or otherwise supported to support elements for transmitting shared data channel transmissions according to the indicated transmission configuration.

[0194] Figure 10 A block diagram 1000 of a device 1005 supporting indications for multicast and unicast transmissions according to various aspects of this disclosure is shown. Device 1005 may be an example of aspects of device 905 or base station 105 as described herein. Device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. Device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0195] Receiver 1010 may provide a unit for receiving information such as packets, user data, control information associated with various information channels (e.g., control channels, data channels, and information channels associated with indications for multicast and unicast transmissions), or any combination thereof. Information may be transmitted to other components of device 1005. Receiver 1010 may utilize a single antenna or a collection of multiple antennas.

[0196] Transmitter 1015 may provide a unit for transmitting signals generated by other components of device 1005. For example, transmitter 1015 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with indications for multicast and unicast transmissions). In some examples, transmitter 1015 may be co-located with receiver 1010 in a transceiver module. Transmitter 1015 may utilize a single antenna or a collection of multiple antennas.

[0197] Device 1005 or its various components may be examples of units for performing various aspects of instructions for multicast and unicast transmissions as described herein. For example, communication manager 1020 may include code point configuration transmission component 1025, control message transmission component 1030, shared data channel transmission component 1035, or any combination thereof. Communication manager 1020 may be examples of various aspects of communication manager 920 as described herein. In some examples, communication manager 1020 or its various components may be configured to use receiver 1010, transmitter 1015, or both, or otherwise cooperate with receiver 1010, transmitter 1015, or both to perform various operations (e.g., receiving, monitoring, transmitting). For example, communication manager 1020 may receive information from receiver 1010, send information to transmitter 1015, or integrate with receiver 1010, transmitter 1015, or both to receive information, send information, or perform various other operations as described herein.

[0198] According to the examples disclosed herein, the communication manager 1020 can support wireless communication at a base station. The code point configuration transmission component 1025 can be configured or otherwise supported to support elements for transmitting code point configurations for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations. The control message transmission component 1030 can be configured or otherwise supported to support elements for transmitting control messages that schedule shared data channel transmission for a group of UEs comprising a set of multiple UEs, the control message including a first code point index from a set of multiple code point indices, the first code point index indicating a transmission configuration as one of a first multicast configuration from a set of multiple multicast configurations or a first unicast configuration from a set of multiple unicast configurations. The shared data channel transmission component 1035 can be configured or otherwise supported to support elements for transmitting shared data channel transmissions according to the indicated transmission configuration.

[0199] Figure 11 A block diagram 1100 of a communication manager 1120 supporting indications for multicast and unicast transmissions according to various aspects of this disclosure is shown. The communication manager 1120 may be an example of aspects of the communication manager 920, communication manager 1020, or both as described herein. The communication manager 1120 or its various components may be examples of units for performing various aspects of the indications for multicast and unicast transmissions as described herein. For example, the communication manager 1120 may include a code point configuration transmission component 1125, a control message transmission component 1130, a shared data channel transmission component 1135, a field size component 1140, a specific code point value indicator 1145, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0200] According to the examples disclosed herein, the communication manager 1120 can support wireless communication at a base station. The code point configuration transmission component 1125 can be configured or otherwise supported to support elements for transmitting code point configurations for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations. The control message transmission component 1130 can be configured or otherwise supported to support elements for transmitting control messages that schedule shared data channel transmission for a group of UEs comprising a set of multiple UEs, the control message including a first code point index from a set of multiple code point indices, the first code point index indicating a transmission configuration as one of a first multicast configuration from a set of multiple multicast configurations or a first unicast configuration from a set of multiple unicast configurations. The shared data channel transmission component 1135 can be configured or otherwise supported to support elements for transmitting shared data channel transmissions according to the indicated transmission configuration.

[0201] In some examples, to support sending codepoint configurations, the codepoint configuration transmission component 1125 may be configured or otherwise supported to support a unit for sending a first codepoint mapping configuration, which maps a first subset of a set of multiple codepoint indices to a set of multiple multicast configurations. In some examples, to support sending codepoint configurations, the codepoint configuration transmission component 1125 may be configured or otherwise supported to support a unit for sending a second codepoint mapping configuration, which maps each codepoint index in the set of multiple codepoint indices to a corresponding unicast configuration in the set of multiple unicast configurations.

[0202] In some examples, to support the sending of control messages, the code point configuration transmission component 1125 may be configured or otherwise supported for sending control messages including a first code point index to indicate that the transmission configuration is a unit of a first multicast configuration based on the first code point index appearing in a first subset of a set of multiple code point indices.

[0203] In some examples, to support the sending of control messages, the code point configuration transmission component 1125 may be configured or otherwise supported for sending control messages including a first code point index to indicate that the transmission configuration is a unit of a first unicast configuration based on the fact that the first code point index appears outside a first subset of a set of multiple code point indices.

[0204] In some examples, to support the transmission of shared data channel transmissions, the shared data channel transmission component 1135 may be configured or otherwise supported as a unit for transmitting shared data channel transmissions according to parameters indicated by the transmission configuration.

[0205] In some examples, parameters include TCI status, resource allocation, MCS, PMI, or any combination thereof.

[0206] In some examples, to support the sending of control messages, the field size component 1140 can be configured or otherwise supported for sending units that include a first code point index in a field having a bit width, the bit width being determined based on the number of first code point indices corresponding to a set of multiple multicast configurations in a set of multiple code point indices, the number of second code point indices corresponding to a set of multiple unicast configurations in a set of multiple code point indices, or both.

[0207] In some examples, to support the sending of control messages, the field size component 1140 can be configured or otherwise supported for sending units that include a first code point index in a field having a bit width, the bit width being determined based on a mapping between a corresponding code point index in a set of multiple code point indices and a corresponding index value in a set of multiple index values.

[0208] In some examples, to support transmit code point configuration, the field size component 1140 can be configured or otherwise supports a unit for transmitting code point configuration associated with the transmit indication.

[0209] In some examples, the association is determined based on the ascending or descending order of the parameters indicated in the code point configuration.

[0210] In some examples, the association is determined based on the ascending or descending order of the identifiers of one or more parameters indicated in the code point configuration.

[0211] In some examples, to support transmit code point configuration, a specific code point value indicator 1145 may be configured or otherwise support a unit for transmit code point configuration, the code point configuration indicating a unicast value corresponding to a second code point index value in a set of multiple code point indices and a null value corresponding to a third code point index value in a set of multiple code point indices.

[0212] In some examples, the control message transmission component 1130 may be configured or otherwise supported for sending indications to two or more subgroups of the UE group to which each UE in the UE group belongs, wherein the indication to a first multicast configuration or a first unicast configuration is based on the indication to two or more subgroups.

[0213] In some examples, to support the sending of control messages, the control message transmission component 1130 may be configured or otherwise supported to support elements for sending NDI fields in control messages, wherein the indication of a first multicast configuration or a first unicast configuration is based on the value of the NDI field.

[0214] In some examples, to support the transmission of control messages, the control message transmission component 1130 may be configured or otherwise supported for transmitting group common control messages with a CRC scrambled by a group common RNTI corresponding to the UE group, the group common control message scheduling utilizing a group common shared data channel transmission scrambled by the group common RNTI, wherein the control message includes group common control messages, and the shared data channel transmission includes group common shared data channel transmission.

[0215] Figure 12A schematic diagram of a system 1200 including indications for device 1205 for multicast and unicast transmissions is shown according to various aspects of this disclosure. Device 1205 may be an example of device 905, device 1005, or base station 105 as described herein, or may include components thereof. Device 1205 may wirelessly communicate with one or more base stations 105, UE 115, or any combination thereof. Device 1205 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1220, a network communication manager 1210, a transceiver 1215, an antenna 1225, a memory 1230, code 1235, a processor 1240, and an inter-station communication manager 1245. These components may be electronically communicated or otherwise coupled via one or more buses (e.g., bus 1250).

[0216] The network communication manager 1210 can manage communication with the core network 130 (e.g., via one or more wired backhaul links). For example, the network communication manager 1210 can manage the transmission of data communication to client devices (e.g., one or more UEs 115).

[0217] In some cases, device 1205 may include a single antenna 1225. However, in other cases, device 1205 may have more than one antenna 1225, which may be capable of transmitting or receiving multiple wireless transmissions simultaneously. Transceiver 1215 may communicate bidirectionally via one or more antennas 1225, wired or wireless links as described herein. For example, transceiver 1215 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1215 may also include a modem for modulating packets, providing modulated packets to one or more antennas 1225 for transmission, and demodulating packets received from one or more antennas 1225. Transceiver 1215, or transceiver 1215 and one or more antennas 1225, may be an example of transmitter 915, transmitter 1015, receiver 910, receiver 1010, or any combination thereof or components thereof as described herein.

[0218] Memory 1230 may include RAM and ROM. Memory 1230 may store computer-readable, computer-executable code 1235, which includes instructions that, when executed by processor 1240, cause device 1205 to perform the various functions described herein. Code 1235 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1235 may not be directly executable by processor 1240, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some additional cases, memory 1230 may also contain a BIOS, which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0219] Processor 1240 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1240 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1230) to cause device 1205 to perform various functions (e.g., functions or tasks supporting instructions for multicast and unicast transmissions). For example, device 1205 or components thereof may include processor 1240 and memory 1230 coupled to processor 1240, processor 1240 and memory 1230 being configured to perform the various functions described herein.

[0220] Inter-site communication manager 1245 can manage communication with other base stations 105 and may include a controller or scheduler for cooperating with other base stations 105 to control communication with UE 115. For example, inter-site communication manager 1245 can coordinate the scheduling of transmissions to UE 115 to implement various interference mitigation techniques such as beamforming or joint transmission. In some examples, inter-site communication manager 1245 may provide an X2 interface within LTE / LTE-A wireless communication network technology to facilitate communication between base stations 105.

[0221] According to the examples disclosed herein, the communication manager 1220 can support wireless communication at a base station. For example, the communication manager 1220 can be configured or otherwise supported to support elements for transmitting code point configurations for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations. The communication manager 1220 can be configured or otherwise supported to support elements for transmitting control messages that schedule shared data channel transmissions for a group of UEs comprising a set of multiple UEs, the control messages including a first code point index from a set of multiple code point indices, the first code point index indicating a transmission configuration as one of a first multicast configuration from a set of multiple multicast configurations or a first unicast configuration from a set of multiple unicast configurations. The communication manager 1220 can be configured or otherwise supported to support elements for transmitting shared data channel transmissions according to the indicated transmission configuration.

[0222] In some examples, the communication manager 1220 may be configured to cooperate with transceiver 1215, one or more antennas 1225, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 1220 is shown as a separate component, in some examples, one or more functions described with reference to the communication manager 1220 may be supported or performed by processor 1240, memory 1230, code 1235, or any combination thereof. For example, code 1235 may include instructions executable by processor 1240 to cause device 1205 to perform various aspects of the indications for multicast and unicast transmissions as described herein, or processor 1240 and memory 1230 may be otherwise configured to perform or support such operations.

[0223] Figure 13 A flowchart illustrating a method 1300 that supports indications for multicast and unicast transmission according to various aspects of this disclosure is shown. Operation of method 1300 can be implemented by a UE or its components as described herein. For example, operation of method 1300 can be implemented by, as referred to... Figures 1 to 8 The UE 115 described herein is used to perform this function. In some examples, the UE may execute a set of instructions to control the functional units of the UE to perform the described function. Alternatively or concurrently, the UE may use dedicated hardware to perform aspects of the described function.

[0224] At 1305, the method may include: receiving a codepoint configuration for a PTM transmission scheme, the codepoint configuration indicating a mapping between a set of multiple codepoint indices, a set of multiple multicast configurations, and a set of multiple unicast configurations. The operation at 1305 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1305 may be provided by reference to... Figure 7The code point configuration component 725 is described and executed.

[0225] At 1310, the method may include: receiving a control message that schedules shared data channel transmission for at least one UE in a UE group comprising a set of multiple UEs, the set of multiple UEs including a first UE, and the control message including a first code point index in a set of multiple code point indices. The operation of 1310 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1310 may be derived from references... Figure 7 The control message receiving component 730 described is used to perform this action.

[0226] At 1315, the method may include: identifying a transport configuration to be applied to receiving a shared data channel transmission based on a mapping and a first code point index, wherein the transport configuration is a first multicast configuration in a set of multiple multicast configurations or a first unicast configuration in a set of multiple unicast configurations. The operation at 1315 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1315 may be derived from, as referenced... Figure 7 The described transmission configuration recognizer 735 is used to perform this.

[0227] At 1320, the method may include: receiving a shared data channel transmission according to the identified transmission configuration. The operation of 1320 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1320 may be derived from references... Figure 7 The shared data channel receiving component 740 described herein performs this action.

[0228] Figure 14 A flowchart illustrating a method 1400 that provides instructions for supporting multicast and unicast transmissions according to various aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE or its components as described herein. For example, operation of method 1400 can be implemented by, as referred to... Figures 1 to 8 The UE 115 described is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional units of the UE to perform the described function. Alternatively or separately, the UE can use dedicated hardware to perform aspects of the described function.

[0229] At 1405, the method may include: receiving a codepoint configuration for a PTM transmission scheme, the codepoint configuration indicating a mapping between a set of multiple codepoint indices, a set of multiple multicast configurations, and a set of multiple unicast configurations. The operation at 1405 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1405 may be provided by reference to... Figure 7 The code point configuration component 725 is described and executed.

[0230] At 1410, the method may include: receiving a first codepoint mapping configuration that maps a first subset of a set of multiple codepoint indices to a set of multiple multicast configurations. The operation of 1410 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1410 may be derived from references... Figure 7 The code point configuration component 725 is described and executed.

[0231] At 1415, the method may include: receiving a second codepoint mapping configuration that maps each codepoint index in a set of multiple codepoint indices to a corresponding unicast configuration in a set of multiple unicast configurations. The operation at 1415 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1415 may be provided by reference to... Figure 7 The code point configuration component 725 is described and executed.

[0232] At 1420, the method may include: receiving a control message that schedules shared data channel transmission for at least one UE in a UE group comprising a set of multiple UEs, the set of multiple UEs including a first UE, and the control message including a first code point index in a set of multiple code point indices. The operation at 1420 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1420 may be derived from references... Figure 7 The control message receiving component 730 described is used to perform this action.

[0233] At 1425, the method may include: identifying a transport configuration to be applied to receiving a shared data channel transmission based on a mapping and a first code point index, wherein the transport configuration is a first multicast configuration in a set of multiple multicast configurations or a first unicast configuration in a set of multiple unicast configurations. The operation at 1425 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1425 may be derived from, as referenced... Figure 7 The described transmission configuration recognizer 735 is used to perform this.

[0234] At 1430, the method may include: receiving a shared data channel transmission according to the identified transmission configuration. The operation at 1430 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1430 may be derived from, as referenced... Figure 7 The shared data channel receiving component 740 described herein performs this action.

[0235] Figure 15 A flowchart illustrating a method 1500 that provides instructions for supporting multicast and unicast transmissions according to various aspects of this disclosure is shown. Operation of method 1500 can be implemented by a UE or its components as described herein. For example, operation of method 1500 can be implemented by, as referred to... Figures 1 to 8The UE 115 described is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional units of the UE to perform the described function. Alternatively or separately, the UE can use dedicated hardware to perform aspects of the described function.

[0236] At 1505, the method may include: receiving a codepoint configuration for a PTM transmission scheme, the codepoint configuration indicating a mapping between a set of multiple codepoint indices, a set of multiple multicast configurations, and a set of multiple unicast configurations. The operation at 1505 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1505 may be provided by reference to... Figure 7 The code point configuration component 725 is described and executed.

[0237] At 1510, the method may include: receiving a control message, the control message scheduling shared data channel transmission for at least one UE in a UE group comprising a set of multiple UEs, the set of multiple UEs including a first UE, and the control message including a first code point index in a set of multiple code point indices. The operation of 1510 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1510 may be derived from references... Figure 7 The control message receiving component 730 described is used to perform this action.

[0238] At 1515, the method may include: identifying a transport configuration to be applied to receiving a shared data channel transmission based on a mapping and a first code point index, wherein the transport configuration is a first multicast configuration in a set of multiple multicast configurations or a first unicast configuration in a set of multiple unicast configurations. The operation at 1515 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1515 may be derived from, as referenced... Figure 7 The described transmission configuration recognizer 735 is used to perform this.

[0239] At 1520, the method may include: receiving a shared data channel transmission according to the identified transmission configuration. The operation at 1520 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1520 may be derived from, as referenced... Figure 7 The shared data channel receiving component 740 described herein performs this action.

[0240] At 1525, the method may include receiving a shared data channel transmission according to parameters indicated by the identified transmission configuration. The operation at 1525 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1525 may be derived from references... Figure 7 The shared data channel receiving component 740 described herein performs this action.

[0241] Figure 16A flowchart illustrating a method 1600 that provides instructions for supporting multicast and unicast transmissions according to various aspects of this disclosure is shown. Operation of method 1600 can be implemented by a UE or its components as described herein. For example, operation of method 1600 can be performed by, as described in reference... Figures 1 to 8 The UE 115 described is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional units of the UE to perform the described function. Alternatively or separately, the UE can use dedicated hardware to perform aspects of the described function.

[0242] At 1605, the method may include: receiving a codepoint configuration for a PTM transmission scheme, the codepoint configuration indicating a mapping between a set of multiple codepoint indices, a set of multiple multicast configurations, and a set of multiple unicast configurations. The operation of 1605 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1605 may be provided by reference to... Figure 7 The code point configuration component 725 is described and executed.

[0243] At 1610, the method may include: receiving a control message that schedules shared data channel transmission for at least one UE in a UE group comprising a set of multiple UEs, the set of multiple UEs including a first UE, and the control message including a first code point index in a set of multiple code point indices. Operation 1610 can be performed according to examples as disclosed herein. In some examples, aspects of operation 1610 may be derived from references... Figure 7 The control message receiving component 730 described is used to perform this action.

[0244] At 1615, the method may include: receiving a control message that includes a first code point index in a field having a bit width, the bit width being determined based on the number of first code point indices corresponding to a set of multiple multicast configurations in a set of multiple code point indices, the number of second code point indices corresponding to a set of multiple unicast configurations in a set of multiple code point indices, or both. The operation at 1615 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1615 may be provided by reference to... Figure 7 The size of the described field determines the execution of component 745.

[0245] At 1620, the method may include: identifying a transmission configuration to be applied to receiving a shared data channel transmission based on a mapping and a first code point index, wherein the transmission configuration is a first multicast configuration in a set of multiple multicast configurations or a first unicast configuration in a set of multiple unicast configurations. The operation at 1620 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1620 may be derived from, as referenced... Figure 7 The described transmission configuration recognizer 735 is used to perform this.

[0246] At 1625, the method may include: receiving a shared data channel transmission according to the identified transmission configuration. The operation at 1625 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1625 may be derived from, as referenced... Figure 7 The shared data channel receiving component 740 described herein performs this action.

[0247] Figure 17 A flowchart illustrating a method 1700 that provides instructions for supporting multicast and unicast transmissions according to various aspects of this disclosure is shown. Operation of method 1700 can be implemented by a UE or its components as described herein. For example, operation of method 1700 can be implemented by, as referred to... Figures 1 to 8 The UE 115 described is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional units of the UE to perform the described function. Alternatively or separately, the UE can use dedicated hardware to perform aspects of the described function.

[0248] At 1705, the method may include: receiving a codepoint configuration for a PTM transmission scheme, the codepoint configuration indicating a mapping between a set of multiple codepoint indices, a set of multiple multicast configurations, and a set of multiple unicast configurations. The operation of 1705 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1705 may be provided by reference to... Figure 7 The code point configuration component 725 is described and executed.

[0249] At 1710, the method may include: receiving a control message that schedules shared data channel transmission for at least one UE in a UE group comprising a set of multiple UEs, the set of multiple UEs including a first UE, and the control message including a first code point index in a set of multiple code point indices. Operation 1710 can be performed according to examples as disclosed herein. In some examples, aspects of operation 1710 may be derived from references... Figure 7 The control message receiving component 730 described is used to perform this action.

[0250] At 1715, the method may include: receiving a control message including a first code point index in a field having a bit width, the bit width being determined based on a mapping indicating the association between a corresponding code point index in a set of multiple code point indices and a corresponding index value in a set of multiple index values. The operation of 1715 can be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1715 may be provided by reference to... Figure 7 The size of the described field determines the execution of component 745.

[0251] At 1720, the method may include: identifying a transport configuration to be applied to receiving a shared data channel transmission based on a mapping and a first code point index, wherein the transport configuration is a first multicast configuration in a set of multiple multicast configurations or a first unicast configuration in a set of multiple unicast configurations. The operation at 1720 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1720 may be derived from, as referenced... Figure 7 The described transmission configuration recognizer 735 is used to perform this.

[0252] At 1725, the method may include: receiving a shared data channel transmission according to the identified transmission configuration. The operation at 1725 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1725 may be derived from, as referenced... Figure 7 The shared data channel receiving component 740 described herein performs this action.

[0253] Figure 18 A flowchart illustrating a method 1800 that provides instructions for supporting multicast and unicast transmissions according to various aspects of this disclosure is shown. Operation of method 1800 can be implemented by a base station or its components as described herein. For example, operation of method 1800 can be implemented by, as referred to... Figures 1 to 4 The base station 105 described in 9 to 12 is used to perform this function. In some examples, the base station may execute a set of instructions to control the functional units of the base station to perform the described functions. Alternatively or concurrently, the base station may use dedicated hardware to perform aspects of the described functions.

[0254] At 1805, the method may include: sending a code point configuration for a PTM transmission scheme, the code point configuration indicating a mapping between a set of multiple code point indices, a set of multiple multicast configurations, and a set of multiple unicast configurations. The operation at 1805 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1805 may be provided by reference to... Figure 11 The described code point configuration is used by the transmission component 1125 to perform this.

[0255] At 1810, the method may include: sending a control message that schedules transmission on a shared data channel for a group of UEs comprising a set of multiple UEs; the control message includes a first code point index from a set of multiple code point indices, the first code point index indicating a transmission configuration as one of a first multicast configuration from a set of multiple multicast configurations or a first unicast configuration from a set of multiple unicast configurations. Operation 1810 may be performed according to examples as disclosed herein. In some examples, aspects of operation 1810 may be derived from references to... Figure 11 The control message transmission component 1130 described is used to perform this.

[0256] At 1815, the method may include: transmitting a shared data channel transmission according to the indicated transmission configuration. The operation at 1815 can be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1815 may be derived from references... Figure 11 The shared data channel transmission component 1135 described herein is used to perform this action.

[0257] The following provides a summary of various aspects of this disclosure:

[0258] Aspect 1: A method for wireless communication at a first UE, comprising: receiving a code point configuration for a point-to-multipoint transmission scheme, the code point configuration indicating a mapping between a plurality of code point indices, a plurality of multicast configurations, and a plurality of unicast configurations; receiving a control message scheduling a shared data channel transmission for at least one UE in a group of UEs comprising a plurality of UEs, the plurality of UEs including the first UE, the control message including a first code point index among the plurality of code point indices; identifying a transmission configuration to be applied to receiving the shared data channel transmission based at least in part on the mapping and the first code point index, the transmission configuration being one of a first multicast configuration among the plurality of multicast configurations or a first unicast configuration among the plurality of unicast configurations; and receiving the shared data channel transmission according to the identified transmission configuration.

[0259] Aspect 2: According to the method of aspect 1, receiving the code point configuration includes: receiving a first code point mapping configuration, the first code point mapping configuration mapping a first subset of the plurality of code point indices to the plurality of multicast configurations; and receiving a second code point mapping configuration, the second code point mapping configuration mapping each of the plurality of code point indices to a corresponding unicast configuration among the plurality of unicast configurations.

[0260] Aspect 3: According to the method of aspect 2, identifying the transmission configuration includes: identifying the transmission configuration as the first multicast configuration based at least in part on the fact that the first code point index appears in the first subset of the plurality of code point indices.

[0261] Aspect 4: According to the method of aspect 2, identifying the transmission configuration includes: identifying the transmission configuration as the first unicast configuration based at least in part on the fact that the first code point index appears outside the first subset of the plurality of code point indices.

[0262] Aspect 5: The method according to any one of Aspects 1 to 4, wherein receiving the shared data channel transmission comprises: receiving the shared data channel transmission according to parameters indicated by the identified transmission configuration.

[0263] Aspect 6: The method according to aspect 5, wherein the parameters include transmission configuration indicator status, resource allocation, modulation and coding scheme, precoding matrix indicator, or any combination thereof.

[0264] Aspect 7: The method according to any one of Aspects 1 to 6, wherein receiving the control message comprises: receiving the control message including the first code point index in a field having a bit width, the bit width being determined at least in part based on the number of first code point indices corresponding to the plurality of multicast configurations, the number of second code point indices corresponding to the plurality of unicast configurations, or both.

[0265] Aspect 8: The method according to any one of Aspects 1 to 6, wherein receiving the control message comprises: receiving the control message including the first code point index in a field having a bit width, the bit width being determined at least in part based on the mapping indicating the association between a corresponding code point index among the plurality of code point indices and a corresponding index value among the plurality of index values.

[0266] Aspect 9: According to the method of aspect 8, receiving the code point configuration includes: receiving an indication of the associated code point configuration.

[0267] Aspect 10: The method according to any one of Aspects 8 to 9, wherein the association is determined at least in part based on the ascending or descending order of parameters indicated in the code point configuration.

[0268] Aspect 11: The method according to any one of Aspects 8 to 9, wherein the association is determined at least in part based on the ascending or descending order of identifiers of one or more parameters indicated in the code point configuration.

[0269] Aspect 12: The method according to any one of Aspects 1 to 11, wherein receiving the code point configuration includes: receiving the code point configuration, the code point configuration indicating a unicast value corresponding to a second code point index value among the plurality of code point indices and a null value corresponding to a third code point index value among the plurality of code point indices.

[0270] Aspect 13: The method according to aspect 12 further includes: receiving a second control message scheduled for a second shared data channel transmission for the UE group; and determining, at least in part, to avoid receiving the second shared data channel transmission or to avoid sending an acknowledgment feedback for the second shared data channel transmission based on a second code point index included in the second control message having the third code point index value.

[0271] Aspect 14: The method according to any one of Aspects 1 to 13 further includes: receiving an indication of a subgroup of the UE group to which the first UE belongs, wherein the identification of which of the first multicast configuration or the first unicast configuration to be applied is at least in part based on the first UE being in the subgroup.

[0272] Aspect 15: The method according to any one of Aspects 1 to 14, wherein receiving the control message includes: receiving a new data indicator field in the control message, wherein the identification of which of the first multicast configuration or the first unicast configuration to be applied is at least in part based on the value of the new data indicator field.

[0273] Aspect 16: The method according to any one of Aspects 1 to 15, wherein receiving the control message comprises: receiving a group common control message having a cyclic redundancy check scrambled by a group common radio network temporary identifier corresponding to the UE group, the group common control message scheduling a group common shared data channel transmission scrambled by the group common radio network temporary identifier, wherein the control message includes the group common control message, and the shared data channel transmission includes the group common shared data channel transmission.

[0274] Aspect 17: A method for wireless communication at a base station, comprising: transmitting a code point configuration for a point-to-multipoint transmission scheme, the code point configuration indicating a mapping between a plurality of code point indices, a plurality of multicast configurations, and a plurality of unicast configurations; transmitting a control message scheduling a shared data channel transmission for a group of UEs comprising a plurality of UEs, the control message including a first code point index among the plurality of code point indices, the first code point index indicating a transmission configuration as a first multicast configuration among the plurality of multicast configurations or a first unicast configuration among the plurality of unicast configurations; and transmitting the shared data channel transmission according to the indicated transmission configuration.

[0275] Aspect 18: According to the method of aspect 17, sending the code point configuration includes: sending a first code point mapping configuration, the first code point mapping configuration mapping a first subset of the plurality of code point indices to the plurality of multicast configurations; and sending a second code point mapping configuration, the second code point mapping configuration mapping each of the plurality of code point indices to a corresponding unicast configuration in the plurality of unicast configurations.

[0276] Aspect 19: According to the method of aspect 18, sending the control message includes: sending the control message including the first code point index to indicate, at least in part, that the transport configuration is the first multicast configuration based on the first code point index appearing in the first subset of the plurality of code point indices.

[0277] Aspect 20: According to the method of aspect 18, sending the control message includes: sending the control message including the first code point index to indicate, at least in part, that the transmission configuration is the first unicast configuration based on the fact that the first code point index appears outside the first subset of the plurality of code point indices.

[0278] Aspect 21: The method according to any one of Aspects 17 to 20, wherein sending the shared data channel transmission comprises: sending the shared data channel transmission according to parameters indicated by the transmission configuration.

[0279] Aspect 22: The method according to aspect 21, wherein the parameters include transmission configuration indicator status, resource allocation, modulation and coding scheme, precoding matrix indicator, or any combination thereof.

[0280] Aspect 23: The method according to any one of Aspects 17 to 22, wherein sending the control message comprises: sending the control message including the first code point index in a field having a bit width, the bit width being determined at least in part based on the number of first code point indices corresponding to the plurality of multicast configurations, the number of second code point indices corresponding to the plurality of unicast configurations, or both.

[0281] Aspect 24: The method according to any one of Aspects 17 to 22, wherein sending the control message comprises: sending the control message including the first code point index in a field having a bit width, the bit width being determined at least in part based on the mapping indicating the association between a corresponding code point index among the plurality of code point indices and a corresponding index value among the plurality of index values.

[0282] Aspect 25: According to the method of aspect 24, sending the code point configuration includes: sending an indication of the associated code point configuration.

[0283] Aspect 26: The method according to any one of Aspects 24 to 25, wherein the association is determined at least in part based on the ascending or descending order of parameters indicated in the code point configuration.

[0284] Aspect 27: The method according to any one of Aspects 24 to 25, wherein the association is determined at least in part based on the ascending or descending order of identifiers of one or more parameters indicated in the code point configuration.

[0285] Aspect 28: The method according to any one of Aspects 17 to 27, wherein sending the code point configuration includes: sending the code point configuration indicating a unicast value corresponding to a second code point index value among the plurality of code point indices and a null value corresponding to a third code point index value among the plurality of code point indices.

[0286] Aspect 29: An apparatus for wireless communication at a first UE, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 1 to 16.

[0287] Aspect 30: An apparatus for wireless communication at a first UE, comprising at least one unit for performing the method according to any one of aspects 1 to 16.

[0288] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication at a first UE, the code comprising instructions executable by a processor to perform the method according to any one of aspects 1 to 16.

[0289] Aspect 32: An apparatus for wireless communication at a base station, comprising a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of aspects 17 to 28.

[0290] Aspect 33: An apparatus for wireless communication at a base station, comprising at least one unit for performing the method according to any one of aspects 17 to 28.

[0291] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code including instructions executable by a processor to perform a method according to any one of aspects 17 to 28.

[0292] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0293] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used extensively in the description, the techniques described herein apply beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described can be applied to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0294] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0295] The various illustrative blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0296] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions can be stored as one or more instructions or code on or transmitted through a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including being distributed such that different parts of the functions are implemented in different physical locations.

[0297] Computer-readable media includes both non-transitory computer storage media and communication media, with communication media encompassing any medium that facilitates the transfer of computer programs from one place to another. Non-transitory storage media can be any available medium accessible by a general-purpose computer or a special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired units of program code in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically copy data magnetically, while optical discs use lasers to copy data optically. The combinations described above are also included within the scope of computer-readable media.

[0298] As used herein (including in the claims), the word "or" in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same way as the phrase "at least partially based on".

[0299] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by a dash and a second reference numeral following the reference numeral, used to differentiate between similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, without regard to the second reference numeral or other subsequent reference numerals.

[0300] This document describes exemplary configurations in conjunction with the accompanying drawings, and does not represent all examples that can be implemented or that are within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," and not "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques can be implemented without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0301] The description herein is provided to enable those skilled in the art to implement or use the present disclosure. Various modifications to the present disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is given the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a first user equipment (UE), comprising: Receive code point configuration for a point-to-multipoint transmission scheme, the code point configuration indicating a mapping between multiple code point indices, multiple multicast configurations and multiple unicast configurations; A control message is received, the control message scheduling shared data channel transmission for at least one UE in a UE group including multiple UEs, the multiple UEs including the first UE, the control message including the first code point index among the multiple code point indices; The transmission configuration to be applied to receiving the shared data channel transmission is identified at least in part based on the mapping and the first code point index, the transmission configuration being a first multicast configuration among the plurality of multicast configurations or a first unicast configuration among the plurality of unicast configurations; as well as The shared data channel transmission is received according to the identified transmission configuration.

2. The method according to claim 1, wherein, Receiving the code point configuration includes: Receive a first code point mapping configuration, wherein the first code point mapping configuration maps a first subset of the plurality of code point indices to the plurality of multicast configurations; and Receive a second code point mapping configuration, which maps each of the plurality of code point indices to a corresponding unicast configuration among the plurality of unicast configurations.

3. The method according to claim 2, wherein, Identifying the transmission configuration includes: The transmission configuration is identified as the first multicast configuration based at least in part on the fact that the first code point index appears within the first subset of the plurality of code point indices.

4. The method according to claim 2, wherein, Identifying the transmission configuration also includes: The transmission configuration is identified as the first unicast configuration based at least in part on the fact that the first code point index appears outside the first subset of the plurality of code point indices.

5. The method according to claim 1, wherein, Receiving the shared data channel transmission includes: The shared data channel transmission is received according to the parameters indicated by the identified transmission configuration.

6. The method according to claim 5, wherein, The parameters include transmission configuration indicator status, resource allocation, modulation and coding scheme, precoding matrix indicator, or any combination thereof.

7. The method according to claim 1, wherein, Receiving the control message includes: The control message is received, which includes the first code point index in a field having a bit width, the bit width being determined at least in part based on the number of first code point indices corresponding to the plurality of multicast configurations, the number of second code point indices corresponding to the plurality of unicast configurations, or both.

8. The method according to claim 1, wherein, Receiving the control message includes: The control message is received, which includes the first code point index in a field having a bit width, the bit width being determined at least in part based on the mapping indicating the association between a corresponding code point index among the plurality of code point indices and a corresponding index value among the plurality of index values.

9. The method according to claim 8, wherein, Receiving the code point configuration includes: Receive the associated code point configuration as indicated.

10. The method according to claim 8, wherein, The association is determined, at least in part, based on the ascending or descending order of the parameters indicated in the code point configuration.

11. The method according to claim 8, wherein, The association is determined, at least in part, based on the ascending or descending order of the identifiers of one or more parameters indicated in the code point configuration.

12. The method according to claim 1, wherein, Receiving the code point configuration includes: The code point configuration is received, wherein the code point configuration indicates a unicast value corresponding to a second code point index value among the plurality of code point indices and a null value corresponding to a third code point index value among the plurality of code point indices.

13. The method of claim 12, further comprising: Receive a second control message scheduled for transmission of the second shared data channel for the UE group; as well as The determination to avoid receiving the second shared data channel transmission or to avoid sending acknowledgment feedback for the second shared data channel transmission is based at least in part on the fact that the second code point index included in the second control message has the third code point index value.

14. The method according to claim 1, further comprising: Receive an indication of a subgroup of the UE group to which the first UE belongs, wherein the identification of which of the first multicast configuration or the first unicast configuration to apply is at least in part based on the first UE being in the subgroup.

15. The method according to claim 1, wherein, Receiving the control message includes: Receive a new data indicator field in the control message, wherein the identification of which of the first multicast configuration or the first unicast configuration to apply is at least in part based on the value of the new data indicator field.

16. The method according to claim 1, wherein, Receiving the control message includes: A group common control message with cyclic redundancy check scrambled by a group common radio network temporary identifier corresponding to the UE group is received. The group common control message schedules transmission of a group common shared data channel scrambled by the group common radio network temporary identifier, wherein the control message includes the group common control message, and the shared data channel transmission includes the group common shared data channel transmission.

17. A method for wireless communication at a base station, comprising: Send a code point configuration for a point-to-multipoint transmission scheme, the code point configuration indicating a mapping between multiple code point indices, multiple multicast configurations and multiple unicast configurations; Sending a control message, the control message scheduling transmission on a shared data channel for a UE group including multiple UEs, the control message including a first code point index among the plurality of code point indices, the first code point index indicating a transmission configuration as one of a first multicast configuration among the plurality of multicast configurations or a first unicast configuration among the plurality of unicast configurations; and The shared data channel transmission is sent according to the indicated transmission configuration.

18. The method according to claim 17, wherein, Sending the code point configuration includes: Send a first codepoint mapping configuration, which maps a first subset of the plurality of codepoint indices to the plurality of multicast configurations; and Send a second code point mapping configuration, which maps each of the plurality of code point indices to a corresponding unicast configuration among the plurality of unicast configurations.

19. The method according to claim 18, wherein, Sending the control message includes: Send the control message including the first code point index to indicate, at least in part, that the transport configuration is the first multicast configuration based on the first code point index appearing within the first subset of the plurality of code point indices.

20. The method according to claim 18, wherein, Sending the control message includes: Send the control message including the first code point index to indicate, at least in part, that the transport configuration is the first unicast configuration based on the fact that the first code point index appears outside the first subset of the plurality of code point indices.

21. The method according to claim 17, wherein, Sending the shared data channel transmission includes: The shared data channel transmission is sent according to the parameters indicated by the transmission configuration.

22. The method according to claim 21, wherein, The parameters include transmission configuration indicator status, resource allocation, modulation and coding scheme, precoding matrix indicator, or any combination thereof.

23. The method according to claim 17, wherein, Sending the control message includes: The control message is sent in a field having a bit width that includes the first code point index, the bit width being determined at least in part based on the number of first code point indices corresponding to the plurality of multicast configurations, the number of second code point indices corresponding to the plurality of unicast configurations, or both.

24. The method according to claim 17, wherein, Sending the control message includes: The control message is sent in a field having a bit width that includes the first code point index, the bit width being determined at least in part based on the mapping that indicates the association between a corresponding code point index among the plurality of code point indices and a corresponding index value among the plurality of index values.

25. The method according to claim 24, wherein, Sending the code point configuration includes: Send an indication of the associated code point configuration.

26. The method according to claim 24, wherein, The association is determined, at least in part, based on the ascending or descending order of the parameters indicated in the code point configuration.

27. The method according to claim 24, wherein, The association is determined, at least in part, based on the ascending or descending order of the identifiers of one or more parameters indicated in the code point configuration.

28. The method according to claim 17, wherein, Sending the code point configuration includes: Send the code point configuration, which indicates a unicast value corresponding to a second code point index value among the plurality of code point indices and a null value corresponding to a third code point index value among the plurality of code point indices.

29. An apparatus for wireless communication at a first user equipment (UE), comprising: processor; Memory coupled to the processor; as well as Instructions, which are stored in the memory and can be executed by the processor, cause the device to perform the following operations: Receive code point configuration for a point-to-multipoint transmission scheme, the code point configuration indicating a mapping between multiple code point indices, multiple multicast configurations and multiple unicast configurations; A control message is received, the control message scheduling shared data channel transmission for at least one UE in a UE group including multiple UEs, the multiple UEs including the first UE, the control message including the first code point index among the multiple code point indices; The transmission configuration to be applied to receiving the shared data channel transmission is identified at least in part based on the mapping and the first code point index, the transmission configuration being a first multicast configuration among the plurality of multicast configurations or a first unicast configuration among the plurality of unicast configurations; as well as The shared data channel transmission is received according to the identified transmission configuration.

30. An apparatus for wireless communication at a base station, comprising: processor; Memory coupled to the processor; as well as Instructions, which are stored in the memory and can be executed by the processor, cause the device to perform the following operations: Send a code point configuration for a point-to-multipoint transmission scheme, the code point configuration indicating a mapping between multiple code point indices, multiple multicast configurations and multiple unicast configurations; Sending a control message, the control message scheduling transmission on a shared data channel for a UE group including multiple UEs, the control message including a first code point index among the plurality of code point indices, the first code point index indicating a transmission configuration as one of a first multicast configuration among the plurality of multicast configurations or a first unicast configuration among the plurality of unicast configurations; and The shared data channel transmission is sent according to the indicated transmission configuration.

Images