Systems and methods for transmitting information

Abstract

The present configuration relates to a system, method, and non-transitory computer-readable medium for receiving a CI message, the CI message configured to indicate whether a data channel carries first data for a first wireless communication device or second data for a second wireless communication device.

Description

[Technical Field]

[0001] The present disclosure relates generally to wireless communications, and more particularly to control information (CI) and data communications. [Background technology]

[0002] In the 5th Generation Mobile Network System (5GC), CI and data are key technologies in the new radio / air interface (NR) system. Downlink and uplink features can include wireless communication between user equipment (UE) and the network. Sidelink features can include wireless communication between user equipment (UE). Summary of the Invention [Problem to be solved by the invention]

[0003] The exemplary configurations disclosed herein are intended to solve one or more problems associated with the prior art and to provide additional features, which will become readily apparent from the following detailed description in conjunction with the drawings. Based on various configurations, this specification discloses exemplary systems, methods, apparatus, and computer program products. However, these configurations are illustrative and not limiting, and it will be apparent to those skilled in the art upon reading this disclosure that various modifications can be made to the disclosed configurations without departing from the scope of the present disclosure. [Means for solving the problem]

[0004] In some configurations, the first wireless communication device may receive a message from the wireless communication node including control information (CI) to schedule a data channel for the first wireless communication device, the CI being configured to indicate whether the data channel will carry first data for the first wireless communication device or second data for the second wireless communication device.

[0005] In some configurations, the wireless communication node may schedule a data channel for a first wireless communication device by sending a message including a CI to the first wireless communication device, the CI being configured to indicate whether the data channel will carry first data for the first wireless communication device or second data for a second wireless communication device.

[0006] These and other aspects and embodiments thereof are described in more detail in the drawings, specification and claims.

[0007] Various exemplary configurations of the present solution will be described in detail below with reference to the drawings. The drawings provided are for illustrative purposes only and describe only exemplary configurations of the present solution, thereby facilitating the reader's understanding of the solution. Therefore, the drawings do not limit the breadth, scope, or applicability of the present solution. Furthermore, for clarity and ease of explanation, the drawings are not necessarily drawn to scale. [Brief explanation of the drawings]

[0008] [Figure 1] 1 illustrates an exemplary wireless communication system according to some configurations. [Figure 2] 1 shows a block diagram of an example base station and an example user equipment device according to some configurations. [Figure 3] 1 is a schematic diagram illustrating an exemplary wireless communication system according to various configurations. [Figure 4] 1 is a schematic diagram illustrating an exemplary wireless communication system according to various configurations. [Figure 5]1A and 1B are schematic diagrams illustrating example physical uplink shared channel (PUSCH) transmissions according to various configurations. [Figure 6] 1A-1C are schematic diagrams illustrating exemplary control information (CI) according to various configurations. [Figure 7] 1 is a diagram illustrating example physical downlink shared channel (PDSCH) scheduling according to various configurations. [Figure 8] 1 is a flowchart illustrating an exemplary method for transmitting information according to various configurations. [Figure 9] 1 is a flowchart illustrating an exemplary method for transmitting information according to various configurations. DETAILED DESCRIPTION OF THE INVENTION

[0009] Various exemplary configurations of the present solution will be described below with reference to the drawings, thereby enabling those skilled in the art to make and use the present solution. After reading this disclosure, those skilled in the art will be able to make various changes or modifications to the examples described herein without departing from the scope of the present solution. Therefore, the present solution is not limited to the exemplary configurations and applications described and illustrated herein. Furthermore, any specific order or hierarchy of steps in the methods disclosed herein is merely exemplary. Based on design preferences, the specific order or hierarchy of steps in a disclosed method or process can be rearranged without departing from the scope of the present solution. Therefore, the methods and techniques disclosed herein depict various steps or operations in an exemplary order, and unless otherwise stated, the present solution is not limited to the specific order or hierarchy shown.

[0010] In a wireless communication system, a wireless device (e.g., a first user equipment (UE)) can communicate with a network. As part of the communication, the first UE may have a transmission demand higher than a supporting threshold (e.g., higher than a supportable threshold). In this case, another UE can assist the first UE in transmitting data, provided that the two UEs can support and perform transmissions between each other (e.g., sidelink communication). This can increase data rates and reliability by splitting and copying data, respectively. However, this can also significantly increase air interface resource costs. The configurations disclosed herein provide enhancements (e.g., additions, updates, modifications) to the system (e.g., a second UE supporting the first UE's transmission), including enhancements to other aspects of the system, such as control information (CI) (e.g., downlink CI (DCI), sidelink CI (SCI)), hybrid automatic repeat-request (HARQ) feedback, data channels, or any combination thereof. Thus, a wireless communication system may support a CI that schedules at least a data channel for a UE, the CI indicating whether the data channel carries data for the UE or data for another UE.

[0011] FIG. 1 illustrates an exemplary wireless communication system 100 in which the techniques disclosed herein may be implemented, according to an embodiment of the present disclosure. In the following discussion, the wireless communication system 100 may implement any wireless network, such as a cellular network or a narrowband Internet of things (NB-IoT) network, and is referred to herein as system 100. The exemplary system 100 includes a BS 102 and a UE 104 that can communicate with each other via a communication link 110 (e.g., a wireless communication channel), and cell clusters 126, 130, 132, 134, 136, 138, and 140 that cover a geographic region 101. In FIG. 1, the BS 102 and the UE 104 are contained within the corresponding geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one BS operating at an allocated bandwidth to provide sufficient wireless coverage for prospective users.

[0012] For example, the BS 102 may operate with an allocated channel transmission bandwidth to provide sufficient coverage for the UE 104. The BS 102 and the UE 104 may communicate via a downlink radio frame 118 and an uplink radio frame 124, respectively. Each radio frame 118 / 124 may be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, the BS 102 and the UE 104 are described herein as non-limiting examples of "communication nodes," and generally, they are capable of performing the methods disclosed herein. According to various embodiments of the present solution, such communication nodes may be capable of wireless and / or wired communication.

[0013] In some embodiments, the wireless communication system 100 may support CI (e.g., DCI or SCI) and data communication. For example, CI communication is an important technology in New Radio (NR) systems. Data transmission techniques may include uplink data transmission, downlink data transmission, and sidelink data transmission in a data channel. To transmit data, a wireless communication device may configure resources via one or more control messages (e.g., DCI or SCI). The techniques described herein may provide enhancements to each aspect of the data transmission and CI process. For example, a first wireless communication device may receive a message including a CI from a wireless communication node to schedule a data channel for the first wireless communication device. The CI may be configured to indicate whether the data channel carries first data for the first wireless communication device or second data for a second wireless communication device.

[0014] 2 is a block diagram illustrating an exemplary wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) in accordance with some embodiments of the present solution. System 200 may include components and elements configured to support known or conventional operating characteristics that need not be described in detail herein. In one illustrative embodiment, system 200 may be used to transfer (e.g., transmit and receive) data symbols in a wireless communication environment (e.g., wireless communication environment 100 of FIG. 1), as described above.

[0015] The system 200 generally includes a BS 202 and a UE 204. The BS 202 includes a base station (BS) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each of which is coupled and interconnected, as needed, via a data communication bus 220. The UE 204 includes a UE transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each of which is coupled and interconnected, as needed, via a data communication bus 240. The BS 202 communicates with the UE 204 over a communication channel 250, which may be any wireless channel or other medium suitable for data transmission as described herein.

[0016] In addition to the modules shown in FIG. 2 , system 200 may include any number of additional modules. The various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in the form of hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps are described generally according to their functionality. Whether such functionality is implemented as hardware, firmware, or software depends on the particular application and design constraints for the overall system. Those skilled in the art will be able to implement such functionality in an appropriate manner for each particular application, and such implementation decisions should not be interpreted as limiting the scope of the present disclosure.

[0017] According to some embodiments, the UE transceiver 230 may be referred to herein as an uplink transceiver 230. The uplink transceiver 230 includes a radio frequency (RF) transmitter and an RF receiver, each of which includes circuitry coupled to an antenna 232. A duplex switch (not shown) may alternately couple the uplink transmitter or the uplink receiver to the uplink antenna in a time-division duplex manner. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a “downlink” transceiver 210 and includes an RF transmitter and an RF receiver, each of which includes circuitry coupled to an antenna 212. A downlink duplex switch may alternately couple the downlink transmitter or the downlink receiver to the downlink antenna 212 in a time-division duplex manner. The operating times of the two transceiver modules 210 and 230 are adjustable so that the uplink receiver circuit is coupled to the uplink antenna 232 to receive signals transmitted over the wireless transmission link 250 when the downlink transmitter is coupled to the downlink antenna 212. In some embodiments, there is close time synchronization with minimal guard time between changes in duplex direction.

[0018] The UE transceiver 230 and the BS transceiver 210 communicate via a wireless data communication link 250 and are configured to cooperate with suitably configured RF antenna arrangements 212 / 232 capable of supporting a particular wireless communication protocol and modulation scheme. In some exemplary embodiments, the UE transceiver 210 and the BS transceiver 210 are configured to support industry standards, such as Long Term Evolution (LTE) and emerging 5G and 6G standards. However, the present disclosure is not necessarily limited in application to any particular standard and associated protocol. Rather, the UE transceiver 230 and the BS transceiver 210 may be configured to support alternative or additional wireless data communication protocols, including future standards or variants thereof.

[0019] According to various embodiments, for example, the BS 202 may be an evolved Node B (eNB), a serving eNB, a target eNB, a femto station, or a pico station. In some embodiments, the UE 204 may be various types of user equipment, such as, for example, a mobile phone, a smartphone, a personal digital assistant (PDA), a tablet computer, a laptop computer, a wearable computing device, etc. The processor modules 214 and 236 may be implemented or realized using a general-purpose processor, a content-addressable memory, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. As such, a processor may be realized as a microprocessor, a controller, a microcontroller, a state machine, etc. A processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, multiple microprocessors, a combination of one or more microprocessors and a digital signal processor core, or any other such configuration.

[0020] Additionally, the methods described in connection with the embodiments disclosed herein may be implemented directly in hardware, firmware, software modules executed by processor modules 214 and 236, respectively, or any practical combination thereof. Memory modules 216 and 234 may be embodied as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable magnetic disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 may be coupled to processor modules 210 and 230, respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234, respectively. Memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intervening information during execution of instructions to be executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0021] The network communications module 218 generally refers to the hardware, software, firmware, processing logic, and / or other components of the BS 202, and facilitates bidirectional communications between the BS transceiver 210 and other network components and communications nodes configured to communicate with the BS 202. For example, the network communications module 218 may be configured to support Internet or WiMAX traffic. In a non-limiting exemplary deployment, the network communications module 218 provides an 802.3 Ethernet interface, allowing the BS transceiver 210 to communicate with conventional Ethernet-based computer networks. As such, the network communications module 218 may include a physical interface (e.g., a Mobile Switching Center (MSC)) for connecting to a computer network. The terms “configured for,” “configured to,” and variations thereof, used herein with respect to a particular operation or function, refer to equipment, components, circuits, structures, machines, signals, etc., that are physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0022] 3 is a schematic diagram of an exemplary wireless communication system 300 according to various configurations. The wireless communication system 300 may outline wireless communication between a network 302 (e.g., a BS), a UE 304, and a UE 306. In some cases, the BS 302 may communicate wirelessly with the UE 304 and the UE 306, and the UE 304 may communicate wirelessly (e.g., sidelink communication) with the UE 306. In some examples, the UE 304 may also be referred to as a remote UE or an anchor UE, and the UE 306 may also be referred to as an aggregation UE. In some cases, a remote UE may be connected to multiple aggregation UEs. Additionally or alternatively, an aggregation UE may be connected to multiple remote UEs. The remote UE may also be connected to the network for transmission of uplink data and transmission of downlink data.

[0023] In wireless communication, the UE 306 may assist the UE 304 in transmitting data (e.g., uplink data, downlink data, sidelink data, etc.). In some cases, the BS 302 may be another UE, such that the wireless communication system 300 includes three UEs. For example, if the UE 306 assists the UE 304 in transmitting sidelink data, the other UE can replace the BS 302. The UE 304 may be connected to the UE 306 for data transmission (e.g., messages) between them. In a first exemplary embodiment, for downlink transmission, the network 302 may transmit downlink data associated with the UE 304 to the UE 306. The UE 306 may forward the received downlink data of the UE 304 to the UE 304. In a second exemplary embodiment, for uplink transmission, the UE 304 may transmit uplink data associated with the UE 304 to the UE 306. The UE 306 may forward (e.g., transmit, relay) the received uplink data of the UE 304 to the network 302.

[0024] In some embodiments, the network 302 may transmit a message including a CI. For example, the network 302 may transmit a CI (e.g., a DCI or an SCI) to a UE (e.g., the UE 304, the UE 306, or both). Alternatively, another UE may transmit a CI (e.g., an SCI) to a UE (e.g., the UE 304, the UE 306, or both). The CI may schedule one or more physical downlink shared channels (PDSCHs), one or more physical uplink shared channels (PUSCHs), or one or more physical sidelink shared channels (PSSCHs) for the UE. The CI may indicate the owner (e.g., the UE 304 or the UE 306) of the data carried by the scheduled PDSCH or PUSCH. For example, the CI may indicate (e.g., via an identifier) ​​which data is carried by the scheduled PDSCH, PUSCH, or PSSCH. For example, the first field of a CI, a radio network temporary identifier of a CI, a search space index of a CI, or a control resource set index of a CI may be used to indicate an owner of data carried by a scheduled PDSCH, PUSCH, or PSSCH. In some cases, the owner may refer to the UE from which the data originates or the UE associated with the data.

[0025] In some cases, the UE 306 may be connected to multiple UEs 304 (e.g., multiple remote UEs). The CI (e.g., a first field included in the CI, a radio network temporary identifier of the CI, a search space index of the CI, or a control resource set index of the CI) may further indicate which remote UE the data carried by the scheduled PDSCH, PUSCH, or PSSCH is intended for.

[0026] In some examples, a CI for the UE 306 may be scrambled with Radio Network Temporary Identifier 1 (RNTI1) and RNTI2. A CI scrambled with RNTI1 may indicate that a scheduled PDSCH, PUSCH, or PSSCH carries data for the UE 304. For example, a CI may be scrambled with RNTI1, thereby allowing data carried by the scheduled PDSCH, PUSCH, or PSSCH to belong to the UE 304. A CI scrambled with RNTI2 may indicate that a scheduled PDSCH, PUSCH, or PSSCH can carry data for the UE 306. For example, a CI may be scrambled with RNTI2, thereby allowing data carried by the scheduled PDSCH, PUSCH, or PSSCH to belong to the UE 306.

[0027] 4 is a schematic diagram of an exemplary wireless communication system 400 according to various configurations. The wireless communication system 400 may outline wireless communication between a network 402 (e.g., a BS), a UE 404, a UE 406, and a UE 408. In some cases, the network 402 may be in wireless communication with the UE 404, the UE 406, and the UE 408, the UE 404 may be in wireless communication (e.g., sidelink communication) with the UE 406, and the UE 406 may be in wireless communication with the UE 408. In some examples, the UE 404 and the UE 408 may be referred to as remote UEs or anchor UEs, and the UE 406 may be referred to as an aggregation UE.

[0028] In some cases, the UE 406 may serve both the UE 404 and the UE 408. The network may send a CI (e.g., DCI or SCI) message to the UE 406. In some examples, the CI message of the UE 406 may include a first field to indicate the owner of the data carried by the PDSCH, PUSCH, or PSSCH. The first field may include two bits to indicate different mappings. For example, a value of "00" may indicate that the PDSCH, PUSCH, or PSSCH scheduled by the CI can carry data for the UE 406. A value of "01" may indicate that the PDSCH, PUSCH, or PSSCH scheduled by the CI can carry data for the UE 404. A value of "10" may indicate that the PDSCH, PUSCH, or PSSCH scheduled by the CI can carry data for the UE 408. While the mappings of 00, 01, and 10 are given as examples, other mappings are possible and may depend on the number of remote UEs and / or aggregation UEs.

[0029] In some examples, for the UE 406, the CI may indicate that the scheduled PDSCH carries downlink data for a remote UE (e.g., the UE 404 or the UE 408). The UE 406 may receive the PDSCH and decode the transport block carried by the PDSCH. The decoded transport block may be forwarded to the remote UE. For example, the UE 406 may transmit the transport block to the remote UE after successfully decoding the transport block of the data channel. Alternatively, the CI may indicate that the scheduled PDSCH carries downlink data for the UE 406. After being decoded, the transport block may be forwarded to a higher layer of the UE 406. For example, after successfully decoding the transport block of the data channel, the UE 406 may transmit the decoded transport block to a higher layer of the UE 406.

[0030] In some cases, for the UE 406, the CI may indicate that the scheduled PUSCH carries uplink data of a remote UE (e.g., second data of a second wireless communication device). The UE 406 may request the remote UE (e.g., the UE 404 or the UE 408) to generate (e.g., assemble) a transport block (or medium access control (MAC) protocol data unit (PDU)) for the scheduled PUSCH (e.g., for a data channel). The UE 406 may transmit time domain information of the scheduled PUSCH to at least the remote UE. The time domain information of the PUSCH may include at least one of a resource location and a resource size. The resource location may include at least one of an orthogonal frequency division multiplexing (OFDM) symbol number, a slot number, a subframe number, and a system frame number. The resource size may include at least the number of orthogonal frequency division multiplexing (OFDM) symbols occupied by the scheduled PUSCH. The remote UE may transmit a transport block (or MAC PDU) for the scheduled PUSCH to the UE 406. Alternatively, the CI may indicate that the scheduled PUSCH carries uplink data for the UE 406. The UE 406 may generate a transport block (or MAC PDU) for the scheduled PUSCH. In either case, the UE 406 may transmit a PUSCH carrying the transport block (or MAC PDU) to the network 402 (e.g., a BS).

[0031] In some embodiments, for the UE 406, the CI may indicate that the scheduled PSSCH carries sidelink data for a remote UE (e.g., the UE 404 or the UE 408). The UE 406 may receive the PSSCH and decode the transport blocks carried by the PSSCH. The decoded transport blocks may be forwarded to the remote UE. Alternatively, the CI may indicate that the scheduled PSSCH carries sidelink data for the UE 406. After decoding, the transport blocks may be forwarded to higher layers for the UE 406.

[0032] In some cases, for the UE 406, the CI may indicate that the scheduled PSSCH carries sidelink data of a remote UE (e.g., the UE 404 or the UE 408). The UE 406 may request the remote UE (e.g., the UE 404 or the UE 408) to generate (e.g., assemble) a transport block (or a MAC PDU) for the scheduled PSSCH. The UE 406 may transmit time-domain information of the scheduled PSSCH to at least the remote UE. The time-domain information of the PSSCH may include at least one of a resource location and a resource size. The resource location may include at least one of an OFDM symbol number, a slot number, a subframe number, and a system frame number. The resource size may include at least the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols occupied by the scheduled PSSCH. The remote UE may transmit a transport block (or a MAC PDU) for the scheduled PSSCH to the UE 406. Alternatively, the CI may indicate that the scheduled PSSCH carries sidelink data of the UE 406. The UE 406 may generate a transport block (or MAC PDU) for the scheduled PSSCH. In either case, the UE 406 may transmit the PSSCH carrying the transport block (or MAC PDU) to another UE.

[0033] In some examples, the network 402 may configure a logical channel configuration for one or more of the UEs (e.g., the UE 404, the UE 406, the UE 408). The configuration may include an allowed data type. In some cases, a logical channel may be configured with multiple allowed data types. The data type may include data for a remote UE (e.g., the UE 404 or the UE 408) or data for an aggregation UE (e.g., the UE 406). The network 402 may schedule a data channel (e.g., a PUSCH or a physical sidelink shared channel (PSSCH)) for the UE. The network 402 may configure the data type to be carried for the data channel (e.g., a PUSCH or a PSSCH).

[0034] The UE may select one or more logical channels, which satisfy the data type carried on the data channel. For example, the allowed data type of the logical channel may match the data type carried by the data channel. Data of the selected logical channel may be mapped to (e.g., carried by) the data channel (e.g., PUSCH or PSSCH). The data type may be indicated (e.g., reflected) by the RNTI, first field, search space index, and control resource set index of the CI. For example, the network 402 may configure the allowed RNTI, allowed first field value, allowed search space index, and / or allowed control resource set index for the logical channel.

[0035] In some cases, the network 402 may configure allowed RNTI values ​​for logical channels. For example, the configured allowed RNTI may be a first RNTI for a first logical channel. The configured allowed RNTI may be a second RNTI for a second logical channel. In some cases, the network 402 may select a first logical channel for a first data channel (e.g., a PUSCH or a PSSCH) scheduled by a first CI scrambled by the first RNTI. Data of the first logical channel may be mapped to (e.g., carried by) the first data channel. In some cases, the network 402 may select a second logical channel for a second data channel (e.g., a PUSCH or a PSSCH) scheduled by a second CI scrambled by the second RNTI. Data of the second logical channel may be mapped to (e.g., carried by) the second data channel.

[0036] In some examples, the network 402 may configure multiple allowed RNTI values ​​for a logical channel. A logical channel may be selected for a data channel (e.g., a PUSCH or a PSSCH) scheduled by a CI, and the CI is scrambled with one of the multiple allowed RNTI values. For a third logical channel, the configured allowed RNTIs may be the third RNTI and the fourth RNTI. A third logical channel may be selected for a third data channel (e.g., a PUSCH or a PSSCH) scheduled by a CI scrambled by the third RNTI or the fourth RNTI. Data of the third logical channel may be mapped to (e.g., carried by) the third data channel.

[0037] In some cases, the UE 406 may be configured with five logical channels, denoted LCH1, LCH2, LCH3, LCH4, and LCH5, respectively. The network 402 may configure allowed first field values ​​for some logical channels. For example, for LCH1, the allowed first field value may include '00'. For LCH2, the allowed first field value may include '00'. For LCH3, the allowed first field value may include '01' and / or '10'. For LCH4, the allowed first field value may include '10'. While a mapping of 00, 01, and 10 is given as an example, other mappings are possible and may depend on the number of remote UEs and / or aggregated UEs. In some cases, the network 402 may not configure an allowed first field value for LCH5. For example, LCH5 may be selected for any PUSCH or PSSCH, and data from LCH5 may be mapped to any PUSCH or PSSCH.

[0038] In some cases, for a PUSCH or PSSCH scheduled by a CI whose first field has a value of "00", LCH1, LCH2, and LCH5 may be selected. Data in LCH1, LCH2, and / or LCH5 may be mapped to a PUSCH or PSSCH. For a PUSCH or PSSCH scheduled by a CI whose first field has a value of "01", LCH3 and LCH5 may be selected. Data in LCH3 and / or LCH5 may be mapped to a PUSCH or PSSCH. For a PUSCH or PSSCH scheduled by a CI whose first field has a value of "10", LCH3, LCH4, and LCH5 may be selected. Data in LCH3, LCH4, and / or LCH5 may be mapped to a PUSCH or PSSCH.

[0039] In some embodiments, a remote UE (e.g., UE 404 or UE 408) may transmit a transport block (or MAC PDU) for a scheduled PUSCH or PSSCH to the UE 406. For each transport block (or MAC PDU) transferred from the remote UE to the UE 406, the UE 406 may transmit a transmission report to the remote UE, the transmission report indicating whether the transport block (or MAC PDU) was successfully delivered. The remote UE may store the transport block (or MAC PDU) in a buffer until it receives a transmission report indicating successful delivery of the transport block (or MAC PDU) or receives a new scheduling with a HARQ process corresponding to the transport block (or MAC PDU). In some cases, the UE 406 may transmit a transmission report indicating unsuccessful delivery of the transport block (or MAC PDU), or the UE 406 may not transmit any transmission report for the transport block (or MAC PDU). Such a transport block (or MAC PDU) may be referred to as an undelivered transport block (or MAC PDU).

[0040] In some cases, a remote UE may transmit an undelivered transport block (or MAC PDU) to the network 402 or another UE. In some embodiments, a first HARQ process of the remote UE may be associated with (e.g., corresponds to) a second HARQ process of an aggregation UE (e.g., UE 406). The network 402 may configure the association. The CI may schedule a PDSCH, PUSCH, or PSSCH with the first HARQ process for the remote UE. The CI may indicate whether the scheduled PDSCH, PUSCH, or PSSCH carries an undelivered transport block. The undelivered transmission carried by the PDSCH, PUSCH, or PSSCH may have a second HARQ process previously transmitted within the UE 406. For example, a second field of the CI may indicate whether the scheduled PDSCH, PUSCH, or PSSCH carries an undelivered transport block. In some cases, the second field may be set to instruct the remote UE to retransmit the transmission block over a data channel, where the transmission block is delivered from the UE 406 to the remote UE.

[0041] For example, the second field may include one bit with a value of "0," indicating that the PDSCH, PUSCH, or PSSCH does not carry an undelivered transport block. The remote UE may retransmit the transport block (or MAC PDU) corresponding to the first HARQ process or transmit a new transport block (or MAC PDU) corresponding to the first HARQ process. A value of "1" in the second field may indicate that the PDSCH, PUSCH, or PSSCH carries an undelivered transport block using the second HARQ process. The remote UE may retransmit the transport block (or MAC PDU) corresponding to the second HARQ process. Alternatively, the remote UE may regenerate a new transport block (or MAC PDU) to include the data carried in the undelivered transport block (or MAC PDU). The newly generated transport block may be transmitted by the remote UE to the network or another UE.

[0042] In some embodiments, the CI may schedule a data channel for the UE 406. The CI may indicate that the data channel carries data for the UE 406. A specific time interval may be used for the data channel carrying data for the UE 406. The interval between the CI (e.g., the last symbol of the physical control channel (PDCCH) or physical sidelink control channel (PSCCH) carrying the CI) and the data channel carrying data for the UE 406 (e.g., the first symbol of the data channel) may be equal to or greater than the specific time interval. The specific time interval may be specified by a protocol or indicated by the network 402.

[0043] A UE (e.g., UE 406, 404, or 408) may report an additional time interval. The additional time interval may be used for a data channel carrying data for a remote UE (e.g., UE 404 or UE 408). The interval between a CI (e.g., the last symbol of a PDCCH or PSCCH carrying the CI) and a data channel (e.g., the first symbol of the data channel) carrying data for the remote UE (e.g., UE 404 or UE 408) may be equal to or greater than the sum of the specified time interval and the reported additional time interval.

[0044] For example, the particular time interval is N1 symbols and the additional time interval is N2 symbols. If the CI indicates that the scheduled data channel carries data for the UE 406, the interval between the last symbol of the PDCCH or PSCCH carrying the CI and the first symbol of the scheduled data channel may be greater than or equal to N1 symbols. If the CI indicates that the scheduled data channel carries data for a remote UE (e.g., the UE 404 or UE 408), the interval between the last symbol of the PDCCH or PSCCH carrying the CI and the first symbol of the scheduled data channel may be greater than or equal to (N1 + N2) symbols.

[0045] 5 is a schematic diagram of an example PUSCH transmission 500 according to various configurations. The transmission 500 may include a first PUSCH 502, a second PUSCH 504, and a third PUSCH 506. In some cases, the PUSCHs 502, 504, and 506 may be transmitted during a time interval 508. The network and UEs shown herein may be examples corresponding to the network 402 and UEs 404, 406, or 408 illustrated in FIG. 4.

[0046] In some embodiments, the network may transmit a CI (e.g., a DCI or an SCI) to a UE (e.g., a remote UE or an aggregation UE). The CI may schedule at least one PDSCH or PSSCH for the UE. In some examples, the CI may indicate that a data channel carries data (e.g., second data) for the UE. In a first example, the UE may transmit a PUCCH to the network (e.g., a wireless communication node) only if the HARQ-ACK information bit corresponding to at least one data channel has an ACK value. In a second example, the UE may not transmit a PUCCH to the network if the HARQ-ACK information bit corresponding to the data channel has a NACK value or if the HARQ-ACK information bits corresponding to all data channels have NACK values. In a third example, the UE may transmit a PUCCH carrying HARQ-ACK information corresponding to the data channel to the network, regardless of the value of the HARQ-ACK information.

[0047] For example, the network may configure a feedback mode for the UE. The feedback mode may include at least an ACK-only feedback mode and an ACK / NACK feedback mode. For the ACK-only feedback mode, the UE may transmit a PUCCH only if the UE correctly decodes at least one PDSCH or PSSCH (e.g., the HARQ-ACK information bit corresponding to at least one PDSCH or PSSCH has an ACK value). For example, if the UE does not correctly decode a PDSCH or PSSCH (e.g., the HARQ-ACK information bit corresponding to a PDSCH or PSSCH has a NACK value or the HARQ-ACK information bits corresponding to all PDSCHs or PSSCHs are NACK values), the UE may not transmit a PUCCH.

[0048] For the ACK / NACK-only feedback mode, the UE may transmit a PUCCH to carry HARQ-ACK information regardless of whether the UE correctly decodes the PDSCH or PSSCH (e.g., the HARQ-ACK information bit value). If the UE correctly decodes the transport block or detects that the CI indicates an SPS PDSCH or SPS PSSCH release, the UE may generate HARQ-ACK information with an ACK value. Otherwise, the UE may generate HARQ-ACK information with a NACK value.

[0049] In some cases, the network may configure a feedback mode for the UE via radio resource control (RRC) signaling, a medium access control unit (MAC CE), or a CI. The feedback mode may correspond to (e.g., be associated with) data carried by the PDSCH, PUSCH, or PSSCH. For example, ACK-only feedback may correspond to data for remote UEs. ACK / NACK feedback may correspond to data for aggregation UEs. For example, if the PDSCH carries data for remote UEs, ACK-only feedback may be used for the PDSCH. If the PDSCH carries data for aggregation UEs, ACK / NACK feedback may be used for the PDSCH.

[0050] Alternatively, the CI may indicate the owner and feedback mode of data carried by the scheduled PDSCH, PUSCH, or PSSCH. For example, a field included in the CI, such as a radio network temporary identifier of the CI, a search space index of the CI, or a control resource set index of the CI, may be used to indicate the owner and feedback mode of data carried by the scheduled PDSCH, PUSCH, or PSSCH. For example, the CI may indicate that the scheduled PDSCH carries downlink data of a remote UE and that ACK-only feedback is applied to the PDSCH. Alternatively, the CI may indicate that the scheduled PDSCH carries downlink data of an aggregation UE and that ACK / NACK feedback is applied to the PDSCH. Furthermore, the CI may indicate that the scheduled PSSCH carries sidelink data of a remote UE and that ACK-only feedback is applied to the PSSCH. Alternatively, the CI may indicate that the scheduled PSSCH carries sidelink data of an aggregation UE and that ACK / NACK feedback is applied to the PSSCH.

[0051] In some embodiments, the ACK-only feedback mode may be applied to one or more PDSCHs for the UE. The PUCCH resources for the ACK-only feedback may overlap with another PUCCH transmission or a PUSCH transmission, at least in the time domain. In this case, for one or more PDSCHs, the UE may convert the ACK-only mode to an ACK / NACK feedback mode. For example, the UE may use ACK / NACK feedback for one or more PDSCHs. According to an embodiment, the UE may generate HARQ-ACK information, which includes an ACK or NACK for one or more PDSCHs.

[0052] In some embodiments, at least a first PUCCH corresponding to the ACK-only feedback mode may overlap in the time domain with a second PUCCH corresponding to the ACK-only feedback mode. The first PUCCH may carry first HARQ-ACK information. The second PUCCH may carry second HARQ-ACK information. The UE may multiplex the first HARQ-ACK information and the second HARQ-ACK information. After multiplexing, the UE may select a PUCCH resource based on the HARQ-ACK information. The UE may transmit the selected PUCCH resource.

[0053] For example, the network 402 may configure multiple PUCCH resources. Table 1 below shows the mapping between HARQ-ACK information and PUCCH resources. The UE may select a PUCCH resource based on the mapping relationship. If the HARQ-ACK information is {1}, {1,0}, {1,0,0}, or {1,0,0,0}, the UE may select a first PUCCH resource among the multiple PUCCH resources. If the HARQ-ACK information is {0,1}, {0,1,0}, or {0,1,0,0}, the UE may select a second PUCCH resource among the multiple PUCCH resources, and so on. In either case, the UE may transmit the selected PUCCH resource to indicate the corresponding HARQ-ACK information to the network.

[0054] [Table 1]

[0055] In some embodiments, the network may transmit a CI, which is used to schedule a PUSCH, a PDSCH, or a PSSCH to a UE (e.g., a remote UE or an aggregation UE). If there are multiple data channels within a time interval, the multiple data channels may carry the same transport block. For example, a first data channel and a second data channel may define a time interval and carry the same transport block. Additionally or alternatively, if there are multiple data channels within a time interval and have the same HARQ process number, the multiple data channels may carry the same transport block. For example, a first data channel and a second data channel may have the same HARQ process number and therefore carry the same transport block.

[0056] In some cases, the time interval may be set by the network or specified by a protocol. The time interval may include one or more slots, OFDM symbols, frames, or milliseconds. The data channel may include a PDSCH, a PUSCH, or a PSSCH. Each of the multiple data channels may be used for an aggregation UE or a remote UE.

[0057] In some cases, PUSCH 502, PUSCH 504, and PUSCH 506 are transmitted within time interval 508. In some examples, different PUSCHs 502, 504, and 506 may include different HARQ process numbers (HPNs). For example, PUSCH 502 may include HPN 5. PUSCH 504 may include HPN 3. PUSCH 506 may include HPN 3. Thus, PUSCH 504 and PUSCH 506 may carry the same transport block because they are within the configured time interval 508 and have the same HPN. PUSCH 502 may carry a different transport block than PUSCH 504 and PUSCH 506 because it has a different HPN from the HPNs of PUSCHs 504 and 506.

[0058] FIG. 6 is a schematic diagram of an example CI 600 according to a different configuration. CI 600 may be an example of a DCI or SCI according to various embodiments described in references 1-5 herein. The CI may include a first information block 602 and a second information block 608. In some cases, the second information block 608 may include a first sub-block 604 and a second sub-block 606. The network and UE shown here may be examples corresponding to network 402 and UE 404, 406, or 408 described in reference 4.

[0059] In some embodiments, the network may configure an RNTI for at least one UE (e.g., an aggregation UE or a remote UE). In some cases, the RNTI may be used to scramble the CI 600. Multiple UEs may monitor and detect the CI 600. The same RNTI may be configured for UEs, and the UEs may include aggregation UEs, remote UEs, or other types of UEs.

[0060] In some examples, the CI 600 may schedule at least a PUSCH, a PDSCH, or a PSSCH for a UE. Alternatively, the CI 600 may schedule multiple PUSCHs, PDSCHs, or PSSCHs for each of a plurality of UEs. For example, the UEs may include two UEs. One UE may be a remote UE, while the other UE may be an aggregation UE. The CI 600 may schedule two PUSCHs. A first PUSCH may be used for the aggregation UE, and a second PUSCH may be used for the remote UE.

[0061] In some embodiments, the UE may detect (e.g., monitor) CIs 600 within a search space. For example, the network may configure multiple search spaces for the UE. A search space may be associated with an RNTI. Alternatively, a search space may be associated with multiple RNTIs, or vice versa. In some cases, the network may configure the association. The UE may monitor CIs 600 scrambled with the associated RNTIs only in the search space. For example, the UE may monitor CIs 600 scrambled with the associated RNTIs only in the search space.

[0062] For example, three RNTIs, denoted RNTI1, RNTI2, and RNTI3, may be configured for the first UE, and RNTI1 and RNTI3 may be associated with search space 1. RNTI2 may be associated with search space 2. Thus, the first UE can monitor CIs 600 scrambled by RNTI1 or RNTI3 only in search space 1. UE1 can monitor CIs 600 scrambled by RNTI2 only in search space 2. In some cases, two search spaces, denoted search space 1 and search space 2, may be configured for the first UE.

[0063] The control resource set (CORESET) may include at least a resource location and size in the frequency domain for a UE (e.g., a remote UE or an aggregation UE) to monitor the CI 600. The network may configure multiple CORESETs for the UE. In some cases, a CORESET may be associated with an RNTI. Alternatively, one CORESET may be associated with multiple RNTIs, or vice versa. The network may configure the association relationship. The UE may monitor the CI 600 scrambled by the RNTI only in the associated CORESET. For example, in the CORESET, the UE may monitor only the CI 600 scrambled by the associated RNTI.

[0064] For example, the network may configure three CORESETs for the UE, denoted as CORESET1, CORESET2, and CORESET3, respectively. RNTI1 and RNTI3 may be associated with CORESET1. RNTI2 may be associated with CORESET2 and CORESET3. Thus, the UE can monitor CIs 600 scrambled by RNTI1 or RNTI3 only in CORESET1. The UE can monitor CIs 600 scrambled by RNTI2 only in CORESET2 or CORESET3.

[0065] In some cases, the size of the CI 600 for scheduling the PUSCH, PDSCH, or PSSCH may be configured by the network. For example, the CI 600 may include a first type field. The network may configure the size of the first type field for multiple UEs. The first type field may be common to the UEs. The UEs may determine the same value indicated by the first type field. In some examples, the CI 600 may include a second type field. The second type field may be specific to one of the multiple UEs.

[0066] In some cases, the CI 600 may include multiple information blocks. The first information block 602 may include a first type field. The second information block 608 may include multiple sub-blocks. Each of the sub-blocks 604 and 606 may include a second type field. Each of the sub-blocks 604 and 606 may be specific to (e.g., correspond to) only one of the UEs. For example, the first information block 602 may be jointly configured for a first UE and a second UE (e.g., wireless communication device), and the second information block 608 includes at least a first sub-block 604 configured exclusively for the first UE and a second sub-block 606 configured exclusively for the second UE.

[0067] In some cases, the network may set the starting position and length of the corresponding sub-block for each of the UEs. For example, the network (e.g., a wireless node) may set at least one of the starting bit and length of each of the first sub-block 604 and the second sub-block 606. The starting position of a sub-block (e.g., sub-block 604 or 606) may include the position of the first bit of the sub-block in the CI 600. The length of the sub-block may include the number of bits of the sub-block. In some cases, a sub-block may include all second type fields for the corresponding UE.

[0068] In some cases, the first information block 602 (e.g., a first type field) may include at least one of a CI format identifier, a carrier indicator, an uplink (UL) / supplementary uplink (SUL) indicator, a frequency domain resource allocation, a time domain resource allocation, a frequency hopping, a priority indicator, an invalid symbol mode indicator, a channel access CPext, a virtual resource block (VRP) to physical resource block (PRB) mapping, a PRB bundling size indicator, a rate matching indicator, or a ZP CSI-RS trigger.

[0069] If the frequency domain resource allocation and the time domain resource allocation are first type fields, the same resources may be allocated for the data channels of the UE. In some cases, the UE may be configured with different antenna ports.

[0070] In some cases, the network may configure whether at least one of the following fields is a first type field or a second type field: modulation and coding scheme (MCS), new data indicator (NDI), redundancy version (RV), HPN, SRS request, SRS offset indicator, PUCCH resource indicator (PRI), PDSCH to HARQ feedback timing indicator, transmission configuration indication (TCI), code block group (CBG) transmission information (CBGTI), downlink assignment indicator (DAI), transmission power command (TPC) for scheduled PUSCH. command), SRS resource set indicator, SRS resource indicator, precoding information and number of layers, antenna port, PTRS-DMRS association, β offset (β_offset) indicator, DMRS sequence initialization, UL-SCH indicator, CSI request, open loop power control parameter set indication, TPC for PUCCH, one shot HARQ-ACK request, extended Type 3 codebook indicator, PDSCH group index, new feedback indicator, number of requested PDSCH groups, HARQ-ACK retransmission indicator, CBG flushing out information (CBGFI), or PUCCH cell indicator.

[0071] Additionally or alternatively, the second information block 608 (e.g., a second type field) may include at least one of a DAI, a TPC for the scheduled PUSCH, an SRS resource set indicator, an SRS resource indicator, precoding information and number of layers, an antenna port, a PTRS-DMRS association, a β offset indicator, a DMRS sequence initialization, a UL-SCH indicator, a CSI request, an open-loop power control parameter set indication, a TPC for the PUCCH, a one-shot HARQ-ACK request, an extended Type 3 codebook indicator, a PDSCH group index, a new feedback indicator, a number of requested PDSCH groups, a HARQ-ACK retransmission indicator, a CBGFI, or a PUCCH cell indicator.

[0072] In some embodiments, if at least one of MCS, NDI, RV, and CBGTI belongs to a first type field or is common to the UE, the data channels scheduled by the CI 600 may carry the same transport block (or MAC PDU). Otherwise, the data channels scheduled by the CI 600 may carry different transport blocks (or MAC PDUs). In some embodiments, if at least one of MCS, NDI, and RV belongs to a first type field or is common to the UE, an ACK-only feedback mode may be applied to the UE. Otherwise, an ACK / NACK feedback mode may be applied to the UE.

[0073] In some cases, the network may configure a CI 600 for the first UE and the second UE. A first information block 602 of the CI 600 may start from the first bit (e.g., a1) of the CI 600. The first information block 602 may include a first type field. The network may configure the first type field to include one or more identifiers of the CI 600 format, frequency domain resource allocation, time domain resource allocation, and / or VRB-PRB mapping. In some cases, the number of bits in these fields may be 1, 13, 4, and 1, respectively (e.g., based on protocol configuration or definition). The first information block may include 18 bits, a1 through a18.

[0074] The second information block 608 of the CI 600 may include two sub-blocks. The first sub-block 604 (e.g., sub-block 1) may be used for the first UE, and the second sub-block 606 (e.g., sub-block 2) may be used for the second UE. The network may configure the second type field to include MCS, NDI, RV, HPN, DAI, antenna port(s), PUCCH resource indicator, TPC for PUCCH and / or PDSCH-to-HARQ feedback timing indicator for UE1 and UE2. In some cases, the number of bits of the second type field may be 5, 1, 2, 4, 2, 4, 3, 2, and 3 bits for the first UE and the second UE, respectively (e.g., based on protocol configuration or definition). The first sub-block 604 (e.g., sub-block 1) or the second sub-block 606 (e.g., sub-block 2) may include 26 bits.

[0075] In some cases, the network may set the start bit of a first subblock 604 (e.g., subblock 1) for a first UE to a19. In this case, the first subblock 604 (e.g., subblock 1) may include a19, a20, ..., a44. The network may set the start bit of a second subblock 606 (e.g., subblock 2) for a UE 2 to a45. In this case, the second subblock (e.g., subblock 2) may include a45, a46, ..., a70.

[0076] FIG. 7 is a schematic diagram of an example PDSCH scheduling 700 according to various configurations. The PDSCH scheduling 700 may be scheduled by the network via a CI 702 (e.g., a DCI or SCI). In some cases, the CI 702 may indicate PDSCH resources for each UE. For example, the CI 702 may indicate a first PDSCH resource set 706 for a first UE and a second PDSCH resource set 708 for a second UE. The network may allocate the same resources in both the time domain and the frequency domain to both the first UE and the second UE. For example, the CI 702 may schedule two PDSCHs. The PDSCH 706 and the PDSCH 708 may occupy the same resources. The first UE may demodulate only the PDSCH 706, and the second UE may demodulate only the PDSCH 708. In some cases, the CI 702 may indicate antenna ports 0 and 1 for the first UE and antenna ports 2 and 3 for the second UE. Antenna ports 0 and 1 may be used to transmit the PDSCH 706. Antenna ports 2 and 3 may be used to transmit the PDSCH 708.

[0077] 8 is a flowchart of an example method 800 for transmitting information according to various configurations. In some cases, the method 800 may include configuring a CI message to indicate whether a data channel of a first wireless communication device carries data for the first wireless communication device or a second wireless communication device.

[0078] At 802, a first wireless communication device may receive a message including a CI from a wireless communication node to schedule a data channel for the first wireless communication device. At 804, the CI is configured to indicate whether the data channel carries first data for the first wireless communication device or second data for a different second wireless communication device. In some cases, the first wireless communication device may be a first UE (e.g., a remote UE, an aggregation UE, or another type of UE), and the second wireless communication device may be a second UE (e.g., a remote UE, an aggregation UE, or another type of UE). In some examples, the CI may be an example of a DCI or an SCI.

[0079] 9 is a flowchart of an example method 900 for transmitting information according to various configurations. In some cases, the method 900 may include configuring a CI message to indicate whether a data channel of a first wireless communication device carries data for the first wireless communication device or a second wireless communication device.

[0080] At 902, the wireless communication node may send a message including a CI to a first wireless communication device to schedule a data channel for the first wireless communication device. At 904, the CI is configured to indicate whether the data channel carries first data for the first wireless communication device or second data for a different second wireless communication device. In some cases, the first wireless communication device may be a first UE (e.g., a remote UE, an aggregation UE, or another type of UE), and the second wireless communication device may be a second UE (e.g., a remote UE, an aggregation UE, or another type of UE). In some examples, the CI may be an example of a DCI or an SCI.

[0081] Various configurations of the present solution have been described above, but they are intended to be illustrative and not limiting. Similarly, various diagrams may depict example architectures or configurations, and providing these example architectures or configurations allows those skilled in the art to understand example features and functionality of the present solution. However, the present solution is not limited to the example architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Also, one or more features of some configurations can be combined with one or more features of other configurations described herein. Thus, the breadth and scope of the present disclosure should not be limited to any of the above-described illustrative configurations.

[0082] Additionally, any designation of elements herein using designations such as "first," "second," etc., generally does not limit the number or order of those elements. Rather, these designations may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, the designations of first and second elements do not imply that only two elements are used or that the first element must precede the second element in some manner.

[0083] Additionally, information and signals may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, and symbols (as referred to in the above description) may be represented as voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0084] Any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital embodiments, analog embodiments, or a combination of both), firmware, various forms of programs or design code incorporating instructions (which may be referred to herein for convenience as "software" or "software modules"), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps have been described above based on their functionality. Whether such functionality is implemented as hardware, firmware, software, or a combination of these technologies depends on the particular application and design constraints imposed on the overall system. Those skilled in the art may implement the described functions in various ways for each particular application, but such implementation decisions do not cause a departure from the scope of the present disclosure.

[0085] Additionally, the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented within or performed by an integrated circuit (IC). The integrated circuit may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), other programmable logic devices, or any combination thereof. The logic blocks, modules, and circuits may further include an antenna and / or a transceiver to communicate with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors and a DSP core, or any other suitable configuration that performs the functions described herein.

[0086] When implemented in software, the functions may be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein may be implemented as software stored on a computer-readable medium. Computer-readable media includes computer storage media and communication media, including any medium that can transmit a computer program or code from one place to another. A storage medium may be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk memory, magnetic disk memory or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0087] As used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Also, for purposes of discussion, various modules are described as discrete modules; however, two or more modules may be combined to form a single module that performs associated functions related to the configuration of the present solution.

[0088] Memory or other storage and communication components may also be used in the implementation of the solution. For clarity, the above description describes the implementation of the solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements, or domains may be used without departing from the solution. For example, functions performed by separate processing logic elements or controllers shown may be performed by the same processing logic element or controller. Thus, references to specific functional units do not indicate a strict logical or physical structure or organization, but merely references to suitable apparatus for providing said functionality.

[0089] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. 1. A wireless communication method, comprising: a first wireless communication device receiving a message including control information CI from a wireless communication node to schedule a data channel for said first wireless communication device; 10. A method of wireless communication, wherein the CI is configured to indicate whether the data channel carries first data for the first wireless communication device or second data for a different second wireless communication device.

2. 2. The wireless communication method of claim 1, wherein the CI includes a radio network temporary identifier (RNTI), a first field, a control resource set (CORESET) index, or a search space index, the CI being configured to indicate whether the data channel carries the first data or the second data.

3. If the CI indicates that the data channel carries the second data, the method further comprises: The wireless communication method of claim 1 , further comprising the step of the first wireless communication device requesting the second wireless communication device to generate a transmission block for the data channel.

4. If the CI indicates that the data channel carries the second data, the method further comprises: The wireless communication method of claim 1 , further comprising the step of, after the first wireless communication device decodes the transmission block, the first wireless communication device transmitting the decoded transmission block to the second wireless communication device.

5. If the CI indicates that the data channel carries the second data, the method further comprises:

2. The wireless communication method of claim 1, further comprising the step of: the first wireless communication device transmitting a PUCCH to the wireless communication node only if a HARQ-ACK information bit corresponding to the at least one data channel has an ACK value.

6. If the CI indicates that the data channel carries the second data, the method further comprises:

2. The wireless communication method of claim 1, further comprising: when a HARQ-ACK information bit corresponding to the data channel has a NACK value, or when HARQ-ACK information bits corresponding to all of the data channels have a NACK value, the first wireless communication device does not transmit a PUCCH to the wireless communication node.

7. If the CI indicates that the data channel carries the first data, the method further comprises:

2. The wireless communication method of claim 1, further comprising the step of: the first wireless communication device transmitting a PUCCH to the wireless communication node regardless of the value of the HARQ-ACK information, wherein the PUCCH carries HARQ-ACK information corresponding to the data channel.

8. If the CI indicates that the data channel carries the first data, the method further comprises: After successfully decoding a transmission block of the data channel, The wireless communication method of claim 1 , further comprising the step of the first wireless communication device transmitting the decoded transport block to a higher layer of the first wireless communication device.

9. 2. The wireless communication method of claim 1, wherein the CI includes a second field, the second field being set to instruct the first wireless communication device to retransmit a transmission block via the data channel, and the transmission block being transferred from the first wireless communication device to the second wireless communication device.

10. The wireless communication method of claim 9 , wherein a first HARQ process corresponding to the first wireless communication device is associated with a second HARQ process corresponding to the second wireless communication device.

11. 2. The wireless communication method according to claim 1, wherein a time interval is set for the data channel and at least a second data channel, and the data channel and the second data channel carry the same transmission block.

12. The wireless communication method of claim 11 , wherein the data channel and the second data channel have the same HARQ process number.

13. 2. The wireless communication method of claim 1, wherein the CI includes at least a first information block and a second information block, the first information block being jointly configured for the first wireless communication device and the second wireless communication device, and the second information block having at least a first sub-block being configured exclusively for the first wireless communication device and a second sub-block being configured exclusively for the second wireless communication device.

14. The wireless communication method of claim 13 , wherein a wireless communication node sets at least one of a start bit and a length of each of the first sub-block and the second sub-block.

15. the first information block includes at least one of an identifier for a control information format, a carrier indicator, a frequency domain resource allocation, a time domain resource allocation, a frequency hopping, and a priority indicator; The wireless communication method according to claim 13, wherein the second information block includes at least one of a transmission power command (TPC), precoding information and a layer number, and an antenna port.

16. 1. A wireless communication method, comprising: a wireless communication node transmitting a message including control information CI to a first wireless communication device to schedule a data channel for the first wireless communication device; 10. A method of wireless communication, wherein the CI is configured to indicate whether the data channel carries first data for a first wireless communication device or second data for a different second wireless communication device.

17. A wireless communication device comprising a processor and a memory, said processor configured to read code from said memory and to perform a method according to any one of claims 1 to 16.

18. 17. A computer program product comprising computer readable program medium code stored on said computer program product, said code, when executed by a processor, causing said processor to perform the method of any one of claims 1 to 16.

Images