Control element utilization for latency critical uplink control signaling

Abstract

Systems, methods, apparatuses, and computer program products for control element utilization for latency critical uplink (UL) control signaling. A method may include preparing a transport block for uplink transmission to a network element. The method may also include attaching bits of feedback information to the transport block. The method may further include encoding the bits of the feedback information separately from the transport block. In addition, the method may include transmitting, to the network element, the transport block comprising the bits of the feedback information.

Description

TITLE:CONTROL ELEMENT UTILIZATION FOR LATENCY CRITICAL UPLINK CONTROL SIGNALINGFIELD:

[0001] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) new radio (NR) access technology, or 5G beyond, or sixth generation (6G) access technology, or other communications systems. For example, certain example embodiments may relate to control element utilization for latency critical uplink (UL) control signaling.BACKGROUND:

[0002] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE- Advanced (LTE- A), MulteFire, LTE-A Pro, fifth generation (5G) radio access technology or new radio (NR) access technology and / or sixth generation (6G) radio access technology. Fifth generation (5G) and sixth generation (6G) wireless systems refer to the next generation (NG) of radio systems and network architecture. 5G and 6G network technology is mostly based on new radio (NR) technology, but the 5G / 6G (or NG) network can also build on E-UTRAN radio. It is estimated that NR may provide bitrates on the order of 10-20 Gbit / s or higher, and may support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency communication (URLLC) as well as massive machine-type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low-latency connectivity and massive networking to support the Internet of Things (IoT).SUMMARY:

[0003] Some example embodiments may be directed to a method. The method may include receiving, from a network element, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The method may also include receiving, from the network element, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The method may further include placing the at least one code block at an end or a beginning of the transport block based on the configuration.

[0004] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor, and at least one memory including computer program code which, when executed by the at least one processor, cause the apparatus to at least receive, from a network element, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The apparatus may also be caused to receive, from the network element, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The apparatus may further be caused to place the at least one code block at an end or a beginning of the transport block based on the configuration.

[0005] Other example embodiments may be directed to an apparatus. The apparatus may include means for receiving, from a network element, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The apparatus may also include means for receiving, from the network element, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The apparatus may further include means for placing the at least one code block at an end or a beginning of the transport block based on the configuration.

[0006] In accordance with other example embodiments, a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method. The method may include receiving, from a network element, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The method may also include receiving, from the network element, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The method may further include placing the at least one code block at an end or a beginning of the transport block based on the configuration.

[0007] Other example embodiments may be directed to a computer program product that performs a method. The method may include receiving, from a network element, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The method may also include receiving, from the network element, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The method may further include placing the at least one code block at an end or a beginning of the transport block based on the configuration.

[0008] Other example embodiments may be directed to an apparatus that may include circuitry configured to receive, from a network element, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The apparatus may also include circuitry configured to receive, from the network element, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The apparatus may further include circuitry configured to place the at least one code block at an end or a beginning of the transport block based on the configuration.

[0009] Further example embodiments may be directed to a method. Themethod may include transmitting, to a user equipment, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The method may also include transmitting, to the user equipment, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The method may further include receiving, from the user equipment, the transport block based on the configuration. According to certain example embodiments, the at least one code block may be located at an end or a beginning of the transport block based on the configuration.

[0010] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor, and at least one memory including computer program code which, when executed by the at least one processor, cause the apparatus to at least transmit, to a user equipment, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The apparatus may also be caused to transmit, to the user equipment, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The apparatus may further be caused to receive, from the user equipment, the transport block based on the configuration. According to certain example embodiments, the at least one code block may be located at an end or a beginning of the transport block based on the configuration.

[0011] Other example embodiments may be directed to an apparatus. The apparatus may include means for transmitting, to a user equipment, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The apparatus may also include means for transmitting, to the user equipment, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The apparatus may further include means for receiving, from the user equipment, the transport block based on the configuration.According to certain example embodiments, the at least one code block may be located at an end or a beginning of the transport block based on the configuration.

[0012] In accordance with other example embodiments, a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method. The method may include transmitting, to a user equipment, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The method may also include transmitting, to the user equipment, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The method may further include receiving, from the user equipment, the transport block based on the configuration. According to certain example embodiments, the at least one code block may be located at an end or a beginning of the transport block based on the configuration.

[0013] Other example embodiments may be directed to a computer program product that performs a method. The method may include transmitting, to a user equipment, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The method may also include transmitting, to the user equipment, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The method may further include receiving, from the user equipment, the transport block based on the configuration. According to certain example embodiments, the at least one code block may be located at an end or a beginning of the transport block based on the configuration.

[0014] Other example embodiments may be directed to an apparatus that may include circuitry configured to transmit, to a user equipment, a configuration including at least one parameter indicating a size for at least one code blockof a transport block. The apparatus may also include circuitry configured to transmit, to the user equipment, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. Further, the apparatus may include circuitry configured to receive, from the user equipment, the transport block based on the configuration. According to certain example embodiments, the at least one code block may be located at an end or a beginning of the transport block based on the configuration.

[0015] Further example embodiments may be directed to a method. The method may include preparing a transport block for uplink transmission to a network element. The method may also include attaching bits of feedback information to the transport block. The method may further include encoding the bits of the feedback information separately from the transport block. In addition, the method may include transmitting, to the network element, the transport block comprising the bits of the feedback information.

[0016] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor, and at least one memory including computer program code which, when executed by the at least one processor, cause the apparatus to at least prepare a transport block for uplink transmission to a network element. The apparatus may also be caused to attach bits of feedback information to the transport block. The apparatus may further be caused to encode the bits of the feedback information separately from the transport block. In addition, the apparatus may be caused to transmit, to the network element, the transport block comprising the bits of the feedback information.

[0017] Other example embodiments may be directed to an apparatus. The apparatus may include means for preparing a transport block for uplink transmission to a network element. The apparatus may also include means for attaching bits of feedback information to the transport block. The apparatusmay further include means for encoding the bits of the feedback information separately from the transport block. In addition, the apparatus may include means for transmitting, to the network element, the transport block comprising the bits of the feedback information.

[0018] In accordance with other example embodiments, a non-transitory computer readable medium may be encoded with instructions that may, when executed in hardware, perform a method. The method may include preparing a transport block for uplink transmission to a network element. The method may also include attaching bits of feedback information to the transport block. The method may further include encoding the bits of the feedback information separately from the transport block. In addition, the method may include transmitting, to the network element, the transport block comprising the bits of the feedback information.

[0019] Other example embodiments may be directed to a computer program product that performs a method. The method may include preparing a transport block for uplink transmission to a network element. The method may also include attaching bits of feedback information to the transport block. The method may further include encoding the bits of the feedback information separately from the transport block. In addition, the method may include transmitting, to the network element, the transport block comprising the bits of the feedback information.

[0020] Other example embodiments may be directed to an apparatus that may include circuitry configured to prepare a transport block for uplink transmission to a network element. The apparatus may also include circuitry configured to attach bits of feedback information to the transport block. The apparatus may further include circuitry configured to encode the bits of the feedback information separately from the transport block. In addition, the apparatus may include circuitry configured to transmit, to the network element, the transport block comprising the bits of the feedback information.BRIEF DESCRIPTION OF THE DRAWINGS:

[0021] For proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:

[0022] FIG. 1 illustrates an example organization of a transport block (TB).

[0023] FIG. 2 illustrates an example TB organized into code block groups (CBGs).

[0024] FIG. 3 illustrates an example code block (CB) arrangement, according to certain example embodiments.

[0025] FIG. 4 illustrates an example CBG arrangement, according to certain example embodiments.

[0026] FIG. 5 illustrates an example header implemented in an uplink (UL) TB, according to certain example embodiments.

[0027] FIG. 6 illustrates an example flow diagram for preparing and transmitting a scheduled TB in UL, according to certain example embodiments.

[0028] FIG. 7 illustrates an example of another flow diagram for reception of UL scheduled data, according to certain example embodiments.

[0029] FIG. 8 illustrates TB configuration implementing HARQ bits, according to certain example embodiments.

[0030] FIG. 9 illustrates an example signal flow diagram, according to certain example embodiments.

[0031] FIG. 10 illustrates an example flow diagram of a method, according to certain example embodiments.

[0032] FIG. 11 illustrates an example flow diagram of another method, according to certain example embodiments.

[0033] FIG. 12 illustrates an example flow diagram of a further method, according to certain example embodiments.

[0034] FIG. 13 illustrates a set of apparatuses, according to certain example embodiments.

[0035] FIG. 14 illustrates an example of a 5G / 6G network and system architecture, according to certain example embodiments.

[0036] FIG. 15 illustrates an example 6G architecture, according to certain example embodiments.

[0037] FIG. 16 illustrates an example 6G radio access network (RAN) protocol stack, according to certain example embodiments.DETAILED DESCRIPTION:

[0038] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. The following is a detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for control element utilization for latency critical uplink (UL) control signaling. For instance, some example embodiments may be directed to using a medium access control control element (MAC-CE) for latency critical UL control signaling in 6G.

[0039] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “certain embodiments,” “an example embodiment,” “some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases “in certain embodiments,” “an example embodiment,” “in some embodiments,” “in other embodiments,” or other similar language, throughout this specification do not necessarily refer to the same group of embodiments, and the described features, structures, orcharacteristics may be combined in any suitable maimer in one or more example embodiments. Further, the terms “base station”, “cell”, “node”, “gNB”, “network” or other similar language throughout this specification may be used interchangeably.

[0040] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or,” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0041] In the specifications of the third generation partnership project (3 GPP), the network (e.g., gNB) may determine when a user equipment (UE) is scheduled with resources in UL by transmitting a scheduling grant to the UE in downlink control information (DCI). The gNB may, for example determine to schedule the UE on a certain number of physical resource blocks (PRBs) with a given modulation coding scheme (MCS) corresponding to a certain transport block size (TBS). Upon receiving the DCI with the UL scheduling grant, the UE may prepare the UL transmission accordingly.

[0042] FIG. 1 illustrates an example organization of a transport block (TB). As illustrated in FIG. 1, depending on the TBS, a TB may be organized into one or multiple code blocks (CBs) where each CB can have a size of up to, for example, 8448 bits in 5G NR, or another number of bits for 6G. In 5G NR, the CBs may include a mixture of information from various sources such as, for example, MAC-CEs and data from different logical channels (LCHs). Additionally, each CB in the TB may have its own cyclic redundancy check (CRC) in addition to the TB-level CRC (of size between 16 to 24 bits). At the receiver side, the data from the TB may first be forwarded to higher layers when the full TB has been correctly received (e.g., upon positive check of both the CB-level CRC and the TB-level CRC).

[0043] FIG. 2 illustrates an example TB organized into code block groups(CBGs). As illustrated in FIG. 2, 3 GPP NR introduced CBGs to facilitate partial retransmission of a TB. For instance, one or more consecutive CBs may be mapped to a CBG, and each CBG may be separately acknowledged (hybrid automatic repeat request (HARQ) acknowledgment / non-acknowledgment (ACK / NACK)) to the transmitter. The number of CBGs in a TB may be derived based on a radio resource control (RRC) parameter maxCodeBlockGroupsPerTransportBlock ENUMERATED {n2, n4, n6, n8}.

[0044] Certain challenges exist with the transmission of critical feedback information such as HARQ ACK / NACK and channel state information (CSI) on MAC-CE. In 5G NR, such feedback information may be transmitted on a physical uplink control channel (PUCCH) or on a physical uplink shared channel (PUSCH) as physical layer (PHY) control information. However, transmission on PUCCH lacks flexibility and support for larger feedback payloads for 6G. On the other hand, when transmitting the HARQ ACK / NACK on MAC-CE, there is a risk that the HARQ round-trip time (RTT) may increase as compared to solutions with the feedback on PUCCH. This risk is particularly relevant if operating the UL transmission as in 5G NR, where UL transmissions are typically scheduled targeting a block error rate (BLER) of 10%-20% for the first transmission. Additionally, at the receiver, the data from the UL transmission may first be forwarded to higher layers when the full TB has been correctly received (e.g., all CB / CBGs in the TB are correctly received).

[0045] In view of the drawbacks and challenges described above, certain example embodiments may provide a way to use MAC-CE for latency critical UL control signaling. For example, the signaling may include CSI and HARQ feedback for 6G radio. In other example embodiments, the MAC-CE may provide a more flexible feedback channel for time-variant size feedback information.

[0046] In certain example embodiments, the delay-critical MAC-CEs may bemapped to one or more separate CBs, which are separate from the CBs carrying the rest of the TB. Additionally, the CBs with the delay-critical MAC-CE information may be grouped into a single CBG. In some example embodiments, when the UE is transmitting a TB to the gNB with CBs containing delay-critical MAC-CE information, the UE may transmit the CBs with MAC-CE information with a conservative MCS. For example, a conservative MCS may have a lower code rate, a lower-order modulation, or both, than other CBGs in the TB so that a lower BLER may be achieved for the delay-critical MAC-CE information.

[0047] According to certain example embodiments, the UL transmission from the UE may include a self-decodable header informing the gNB that a first (or last) set of CBs contains delay-critical MAC-CE information that can be decoded separately. The content of the first CB or set of CBs can be forwarded to, for example, the PHY layer if containing CSI and / or HARQ ACK / NACK.

[0048] According to other example embodiments, when the gNB schedules a UE for UL transmissions, the gNB may include in the scheduling signaling an indication of the MCS that the UE can use for the TB transmission. The gNB may also be in control of what is the more conservative MCS of the CBs containing MAC-CE information if the MAC-CE information is included in the TB. According to some example embodiments, the MAC-CE information may be included in the DCI or preconfigured with RRC for the UE.

[0049] In certain example embodiments, the gNB may configure the UE to use MAC-CE for UL transmission of certain control information such as, for example, CSI and HARQ feedback. The control information may also include multi-bit HARQ feedback for soft-HARQ schemes or CBG-based HARQ ACK / NACK feedback. The configuration by the gNB may also instruct the UE to pack (e.g., add or include) HARQ information and possibly other delay-critical information such as, for example, CSI feedback, into separate CBs in the TB (e.g., separate from the rest of the TB). For example, it may benecessary to know the number of bits that go into the separate CB or CBs for MAC-CEs before knowing how many bits the MAC-CEs actually need. In this example, the number of bits that the separate CB or CBs accommodate may be set to be sufficiently large to include the MAC-CEs.

[0050] According to certain example embodiments, the configuration from the gNB to the UE may also include a delta_MCS or absolute_MCS that instructs the UE on which MCS to use for the CB(s) containing the MAC-CE information (or delta to a code rate only, if it is practical to maintain the same modulation for the entire transmission in all cases). If an absolute MCS or coding rate is configured, the UE may transmit the CB with MAC-CE information with the MCS / coding rate. Otherwise, the UE may use the MCS that is given to the UE as part of the UL scheduling grant (sent on DCI). If delta_MCS is configured for the UE, the CBs containing delay-critical MAC-CEs may be transmitted with the MCS given as part of the UL scheduling grant, offset by delta_MCS. The delta_MCS may also refer to an offset of the coding rate such as, for example, a delta_MCS value of 1 / 2 or 2 may imply that the coding rate should be halved for the specific CBs (e.g., from 9 / 10 to 4.5 / 10). As an example, the MCS signalled to the UE as part of the UL scheduling grant may be an integer that points to a MCS table; each entry in the MCS tables may define the Modulation and Coding rate to use. The delta-MCS may also be expressed as an integer as a delta for table; as an example, if the MCS index equals N in the DCI UL scheduling grant, the UE may use MCS index N-delta_MCS for CB with MAC-CE info.

[0051] In certain example embodiments, delta_MCS may be configured using higher layer signaling such as, for example, RRC signaling. Additionally, the delta_MCS may be signaled using PHY signaling, and may be indicated in the scheduling DCI and signaled as part of a dedicated out-of-band header PUS CH information. In some example embodiments, a combination of RRC and PHY signaling may be used. For example, the gNB may configuremultiple delta_MCS values, and PHY signaling may be used to indicate which one is used. Alternatively, the RRC may configure the delta_MCS and the PHY signaling may indicate whether to use delta_MCS or not use delta_MCS.

[0052] According to certain example embodiments, the CB size may be predetermined for HARQ information. The HARQ information may be mapped into one or more CBs of a TB with small specification impact. According to some example embodiments, mapping the HARQ information into one or more CBs of a TB may involve the gNB configuring the UE to report HARQ feedback (e.g., MAC-CE) together withUL data transmissions (PUSCH). The configuration may include a number of bits, a number of CBs, or a combination of a number of bits and a number of CBs (e.g., number of CBs and corresponding size) to be used to carry the HARQ information. Alternatively, the number of bits for the CBs may be implicitly signaled to the UE. For example, the number of bits for the CBs may be derived from a combination of other parameters such as, for example, an expected HARQ feedback payload size that is a function of a time division duplex (TDD) pattern configured in the network, or a number of multiple input multiple output (MIMO) layers.

[0053] According to other example embodiments, the configuration may also include whether the CBs are to be placed at the beginning or at the end of the TB (or be fixed). For instance, FIG. 3 illustrates an example CB arrangement, according to certain example embodiments. In particular, FIG. 3 illustrates an example where one special CBO (with gNB-configured size) is placed at the beginning of the TB. The remaining CBs in the TB may be generated in the usual manner such as, for example, by segmentation according to the max CB size.

[0054] In certain example embodiments, CBG HARQ bits may be mapped to CBs to facilitate retransmission of only the data part of the TB or only the MAC-CE part of the TB. This may be accomplished as illustrated in FIG. 4by mapping the first CB of the TB (e.g., containing MAC-CEs) one-to-one to the CB(s) containing HARQ, and the remaining CBs can be grouped into CBGs according to legacy procedures. For instance, if the maxCodeBlockGroupsPerTransportBlock is configured to 4, 3 out of the 4 CBGs may be mapped to those CBGs that do not contain HARQ information. This mapping allows dedicated HARQ information for the first part of the TB containing HARQ information (e.g., MAC-CE), and allows the gNB to separately retransmit one or another part of the TB. Alternatively, the first CB (or CBs) may be considered as one CBG (CBGO), and the other CBs may be considered as another CBG (CBG1) without splitting the other CBs further to multiple CBGs.

[0055] According to certain example embodiments, the DCI scheduling the TB may include one or more fields (bits) instructing the UE whether the operation (with different size CBs) may be considered or not for the scheduled TB. According to some example embodiments, the gNB may know the approximate size(s) of the MAC-CE and configure the UE to always use a certain CB size for those CBs that appear in the first or last CBG (carrying MAC-CE information). Configuring the UE in this manner may make the MAC and PHY layer procedures independent from each other. Additionally, the PHY layer may be instructed or configured to generate a TB with a last or first CB(s) of different size and coding rate, and the MAC layer may be configured in parallel to place HARQ information (MAC-CE) at the beginning or end of the TB delivered to the PHY layer. This configuration may suggest that in addition to MAC-CEs, some user plane data bits may end up in the better protected CB(s) because the PHY layer may need to be dimensioned to at least fit the MAC-CEs on the first CB(s) before knowing the exact size of those MAC-CEs.

[0056] In certain example embodiments, the UL TB may include a dedicated self-decodable header. The PHY layer at the UE may be aware of the presenceof MAC-CE or HARQ information, and can autonomously determine whether or not the TB shall contain dedicated CB(s) for such HARQ bits. The header appended to the start of the transmission may be a single bit to indicate if the first (or last) CB / CBG contains MAC-CE information. In other example embodiments, the header may include multiple bits to indicate the size of the first CB / CBG (if it contains MAC-CE). This may be useful side information to ease the demodulation of the transmission for the gNB (e.g., when multiple size values are configured by the gNB for the UE to select). This example embodiment may require an indication from the MAC layer to the PHY layer (in the UE) indicating the presence, and optionally the size, of HARQ information in the MAC protocol data units (PDUs) delivered to the PHY layer.

[0057] FIG. 5 illustrates an example header implemented in an UL TB, according to certain example embodiments. In particular, FIG. 5 illustrates an example where the header (H) informs the gNB on how many CBs or bits are used to carry HARQ information (and subject to different coding rate). The feature in the example embodiments described above of mapping dedicated HARQ bits to those CB(s) may also be applicable in this example embodiment.

[0058] FIG. 6 illustrates an example flow diagram for preparing and transmitting a scheduled TB in UL, according to certain example embodiments. At 600, the procedure for UE UL scheduled transmission begins. At 605, upon reception of the UL scheduling grant, the UE fills the TB by creating CB(s) with MAC-CE information and potentially packs those into one CBG containing only such information. At 610, the CBs / CBGs for the TB containing data from LCHs and non-delay critical MAC-CEs are created. At 615, a self-decodable header is added to the UL transmission to indicate to the gNB whether the first CB(s) or CBG in the transmission contains delay-critical MAC-CEs, and possibly the size of the CB(s) or CBG.In certain example embodiments, the gNB may use this information contained in the header to determine that the CBG is self-decodable and that the corresponding MAC-CEs can be forwarded to the relevant units for further processing as soon as the CRC for the CB(s) or CBG is positive.

[0059] At 620, the PUSCH with the header and CBs / CBGs is transmitted on the radio resources, and with the MCS indicated in the scheduling grant (DCI) except for the header and the CBs containing MAC-CE. The CBs containing MAC-CE are transmitted using a MCS that adheres to absolute_MCS or delta_MCS configurations. At 625, the procedure for UE UL scheduled transmission ends.

[0060] FIG. 7 illustrates an example of another flow diagram for reception of UL scheduled data, according to certain example embodiments. At 700, the gNB procedure may include receiving UL scheduled data. At 705, the gNB first decodes the header in the start of the transmission. At 710, if the header informs the gNB that the first CB(s) contains delay-critical MAC-CEs, the gNB knows that the first CB(s) may be transmitted with a different MCS (as per absolute_MCS / delta_MCS configuration). At 715, when the CB(s) with delay-critical MAC-CEs has been correctly decoded (e.g., the CRC for the CB(s) is positive), the gNB may forward the content of the MAC-CEs to the relevant units (e.g., to PHY in case the MAC-CEs contain CSI). At 720, the remaining CBs in the transmission are treated as per legacy procedures. At 725, the gNB reception procedure ends.

[0061] In certain example embodiments, HARQ information may be present at the PHY layer, and there may be separate encoding of the HARQ information and data in the UL TB. In some example embodiments, the HARQ information may be generated by the PHY layer. In this case, whenever the UE prepares a TB for UL transmission, the UE appends N additional bits to the TB. In certain example embodiments, the N bits may be appended with a different coding rate as compared to the rest of the TB. Insome example embodiments, the N bits of HARQ may be generated according to existing (or similar context of 6G) procedures for generating HARQ information, and may be similar, for example to procedures in 5G NR for multiplexing UL control information (UCI) on PUS CH. However, in NR, UCI may, by default, be sent on the PUCCH. Resources for PUCCH containing HARQ feedback may be determined based on KI data-to-HARQ feedback timing offset and a PUCCH resource indicator (PRI) field in the DCI.

[0062] In certain example embodiments, when a PUCCH overlaps or takes place in the same slot as a data transmission (PUSCH), the UCI may be multipl exed / appended to the TB of the PUSCH transmission. In contrast, certain example embodiments may append HARQ information to the PUSCH without dedicated PUCCH. In doing so, the UE may collect HARQ information bits of DL PDSCH receptions, and append the collected HARQ information bits to a PUSCH transmission.

[0063] FIG. 8 illustrates an example TB configuration implementing HARQ bits, according to certain example embodiments. According to certain example embodiments, HARQ information bits may be separately encoded from TB scheduled to be transmitted on PUSCH. The coded HARQ information bits may then be multiplexed on the resources allocated for PUSCH together with the coded TB. According to some example embodiments, the HARQ information bits may include a dedicated CRC. According to other example embodiments, the gNB may need to know the exact number of HARQ bits that are multiplexed together with the PUSCH. Here, the gNB may be in charge of scheduling the user in the DL direction, and the gNB may estimate in parallel the number of HARQ bits that the UE is expected to report at a certain time. Because those HARQ bits are not originated from the MAC manager, it may not be possible to apply HARQ procedure to retransmit those bits containing HARQ information (e.g., only the data (UL-SCH) part of the TB can be retransmitted). The decision onwhether to multiplex HARQ bits on PUSCH may also be controlled by the gNB based on one or more bits in the DCI.

[0064] FIG. 9 illustrates an example signal flow diagram, according to certain example embodiments. At 910, the UE 905 may be configured by the gNB 900 to include certain information such as, for example, CSI and HARQ feedback in MAC-CE and pack the information into separate CB(s) and a single CBG. In certain example embodiments, the configuration may include absolute_MCS or delta-MCS parameters. At 915, the gNB 900 transmits an UL scheduling grant to the UE 905 as DCI. At 920, the UE 905 prepares the UL transmission as defined under UE procedure. At 925, the UE 905 performs PUSCH transmission to the gNB 900, and the PUSCH transmission may include the TB including the CB(s) that contain MAC-CE. At 930, the gNB decodes the PUSCH transmission based on the defined procedure.

[0065] FIG. 10 illustrates an example flow diagram of a method, according to certain example embodiments. In an example embodiment, the method of FIG. 10 may be performed by a network entity, or a group of multiple network elements in a 3GPP system, such as LTE or 5G-NR. For instance, in an example embodiment, the method of FIG. 10 may be performed by a UE, similar to one of apparatuses 10 or 20 illustrated in FIG. 13.

[0066] As illustrated in FIG. 10, the method may include, at 1000, receiving, from a network element, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The method may also include, at 1005, receiving, from the network element, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The method may further include, at 1010, placing the at least one code block at an end or a beginning of the transport block based on the configuration.

[0067] According to certain example embodiments, the method may also include mapping the at least one code block of the transport block to at leastone code block group based on the configuration. According to some example embodiments, one code block group of the at least one code block group may include the at least one code block. According to other example embodiments, the method may further include mapping at least one control element with uplink control information into the at least one code block.

[0068] In certain example embodiments, the instructions may include at least one delta modulation coding scheme value or at least one absolute modulation coding scheme value configured by radio resource control signaling. In some example embodiments, the at least one delta modulation coding scheme value or the at least one absolute modulation coding scheme value may include instructions identifying a modulation coding scheme value to use for the at least one code block including control element information. In other example embodiments, the uplink control information or the control element information may include at least hybrid automatic repeat request feedback information.

[0069] According to certain example embodiments, the delta modulation coding scheme may be relative to the modulation coding scheme that is applicable for other remaining code blocks of the transport block, or the absolute modulation coding scheme may be distinct from the modulation coding scheme that is applicable for other remaining code blocks of the transport block. According to some example embodiments, the method may further include autonomously determining whether or not the transport block comprises a dedicated code block to store the control element information. According to other example embodiments, the method may also include including a header prior to the transport block.

[0070] In certain example embodiments, the header may include at least one bit indicating whether the at least one code block comprises control element information, or indicating the size of the at least one code block. In some example embodiments, the method may further include determining bits offeedback information of a received transmission.

[0071] FIG. 11 illustrates an example flow diagram of another method, according to certain example embodiments. In an example embodiment, the method of FIG. 11 may be performed by a network entity, or a group of multiple network elements in a 3GPP system, such as LTE or 5G-NR. For instance, in an example embodiment, the method of FIG. 11 may be performed by a NW or gNB, similar to one of apparatuses 10 or 20 illustrated in FIG. 13.

[0072] As illustrated in FIG. 11, the method may include, at 1100, transmitting, to a user equipment, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The method may also include, at 1105, transmitting, to the user equipment, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The method may further include, at 1110, receiving, from the user equipment, the transport block based on the configuration. According to certain example embodiments, the at least one code block may be located at an end or a beginning of the transport block based on the configuration.

[0073] According to certain example embodiments, the instructions may include at least one delta modulation coding scheme value or at least one absolute modulation coding scheme value configured by radio resource control signaling. According to some example embodiments, the at least one delta modulation coding scheme value or the at least one absolute modulation coding scheme value may include instructions identifying a modulation coding scheme value to use for the at least one code block comprising control element information. According to other example embodiments, the delta modulation coding scheme may be relative to the modulation coding scheme that is applicable for other remaining code blocks of the transport block, or the absolute modulation coding scheme may be distinct from the modulation coding scheme that is applicable for other remaining code blocks of thetransport block.

[0074] FIG. 12 illustrates an example flow diagram of a further method, according to certain example embodiments. In an example embodiment, the method of FIG. 12 may be performed by a network entity, or a group of multiple network elements in a 3GPP system, such as LTE or 5G-NR. For instance, in an example embodiment, the method of FIG. 12 may be performed by a UE, similar to one of apparatuses 10 or 20 illustrated in FIG. 13.

[0075] As illustrated in FIG. 12, the method may include, at 1200, preparing a transport block for uplink transmission to a network element. The method may also include, at 1205, attaching bits of feedback information to the transport block. The method may further include, at 1210, encoding the bits of the feedback information separately from the transport block. In addition, the method may include, at 1215, transmitting, to the network element, the transport block comprising the bits of the feedback information.

[0076] According to certain example embodiments, the feedback information may include at least hybrid automatic repeat request feedback information. According to some example embodiments, the bits of the feedback information are encoded using a different coding rate compared to the rest of the transport block that does not include the hybrid automatic repeat request bits. According to other example embodiments, the bits of the feedback information may be separately encoded.

[0077] In certain example embodiments, the method may further include determining the bits of the feedback information of a received transmission. In some example embodiments, the method may also include transmitting a physical uplink shared channel with the bits of feedback information to the network element.

[0078] FIG. 13 illustrates a set of apparatuses 10 and 20 according to certain example embodiments. In certain example embodiments, apparatuses 10 and 20 may be elements in a communications network or associated with such anetwork. For example, apparatus 10 may be a UE, or other similar radio communication computer device, and apparatus 20 may be a BS, gNB, network, or other similar computing device.

[0079] In some example embodiments, apparatuses 10 and 20 may include one or more processors, one or more computer-readable storage medium (for example, memory, storage, or the like), one or more radio access components (for example, a modem, a transceiver, or the like), and / or a user interface. In some example embodiments, apparatuses 10 and 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technologies. It should be noted that one of ordinary skill in the art would understand that apparatuses 10 and 20 may include components or features not shown in FIG. 13.

[0080] As illustrated in the example of FIG. 13, apparatuses 10 and 20 may include or be coupled to a processor 12 and 22 for processing information and executing instructions or operations. Processors 12 and 22 may be any type of general or specific purpose processor. In fact, processors 12 and 22 may include one or more of general-purpose computers, special purpose computers, microprocessors, DSPs, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 12 and 22 is shown in FIG. 13, multiple processors may be utilized according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatuses 10 and 20 may include two or more processors that may form a multiprocessor system (e.g., in this case processors 12 may represent a multiprocessor) that may support multiprocessing. According to certain example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0081] Processors 12 and 22 may perform functions associated with the operation of apparatuses 10 and 20 including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatuses 10 and 20, including processes and examples illustrated in FIGs. 1-12.

[0082] Apparatuses 10 and 20 may further include or be coupled to a memories 14 and 24 (internal or external), which may be respectively coupled to processors 12 and 24 for storing information and instructions that may be executed by processors 12 and 24. Memories 14 and 24 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and / or removable memory. For example, memories 14 and 24 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non-transitory machine or computer readable media. The instructions stored in memories 14 and 24 may include program instructions or computer program code that, when executed by processors 12 and 22, enable the apparatuses 10 and 20 to perform tasks as described herein.

[0083] In certain example embodiments, apparatuses 10 and 20 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processors 12 and 22 and / or apparatuses 10 and 20 to perform any of the methods and examples illustratedinFIGs. 1-12.

[0084] In some example embodiments, apparatuses 10 and 20 may also include or be coupled to one or more antennas 15 and 25 for receiving a downlink signal and for transmitting via an UL from apparatuses 10 and 20. Apparatuses 10 and 20 may further include a transceivers 18 and 28 configured to transmit and receive information. The transceivers 18 and 28 may also include a radio interface (e.g., a modem) coupled to the antennas 15 and 25. The radio interface may correspond to a plurality of radio access technologies including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, and the like. The radio interface may include other components, such as filters, converters (for example, digital-to-analog converters and the like), symbol demappers, signal shaping components, an Inverse Fast Fourier Transform (IFFT) module, and the like, to process symbols, such as OFDMA symbols, carried by a downlink or an UL.

[0085] For instance, transceivers 18 and 28 may be configured to modulate information on to a carrier waveform for transmission by the antennas 15 and 25 and demodulate information received via the antenna 15 and 25 for further processing by other elements of apparatuses 10 and 20. In other example embodiments, transceivers 18 and 28 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, apparatus 10 may include an input and / or output device (I / O device). In certain example embodiments, apparatuses 10 and 20 may further include a user interface, such as a graphical user interface or touchscreen.

[0086] In certain example embodiments, memories 14 and 34 store software modules that provide functionality when executed by processors 12 and 22. The modules may include, for example, an operating system that provides operating system functionality for apparatuses 10 and 20. The memory mayalso store one or more functional modules, such as an application or program, to provide additional functionality for apparatuses 10 and 20. The components of apparatuses 10 and 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to certain example embodiments, apparatuses 10 and 20 may optionally be configured to communicate each other (in any combination) via a wireless or wired communication links 70 according to any radio access technology, such as NR.

[0087] According to certain example embodiments, processors 12 and 22 and memories 14 and 24 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceivers 18 and 28 may be included in or may form a part of transceiving circuitry.

[0088] For instance, in certain example embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to receive, from a network element, a configuration including at least one parameter indicating a size for at least one code block of a transport block. Apparatus 10 may also be controlled by memory 14 and processor 12 to receive, from the network element, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. Apparatus 10 may further be controlled by memory 14 and processor 12 to place the at least one code block at an end or a beginning of the transport block based on the configuration.

[0089] In other example embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to transmit, to a user equipment, a configuration including at least one parameter indicating a size for at least one code block of a transport block. Apparatus 20 may also be controlled by memory 24 and processor 22 to transmit, to the user equipment, instructions to use a different modulation or coding rate for the at least one code block compared to othercode blocks of the transport block. Apparatus 20 may further be controlled by memory 24 and processor 22 to receive, from the user equipment, the transport block based on the configuration. According to certain example embodiments, the at least one code block may be located at an end or a beginning of the transport block based on the configuration.

[0090] In other example embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to prepare a transport block for uplink transmission to a network element. Apparatus 10 may also be controlled by memory 14 and processor 12 to attach bits of feedback information to the transport block. Apparatus 10 may further be controlled by memory 14 and processor 12 to encode the bits of the feedback information separately from the transport block. In addition, apparatus 10 may be controlled by memory 14 and processor 12 to transmit, to the network element, the transport block comprising the bits of the feedback information.

[0091] In some example embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, and / or computer program code for causing the performance of the operations.

[0092] Certain example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for receiving, from a network element, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The apparatus may also include means for receiving, from the network element, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The apparatus may further include means for placing the at least one code block at an end or a beginning of the transport block based on the configuration.

[0093] Other example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for transmitting, to a user equipment, a configuration including at least one parameter indicating a size for at least one code block of a transport block. The apparatus may also include means for transmitting, to the user equipment, instructions to use a different modulation or coding rate for the at least one code block compared to other code blocks of the transport block. The apparatus may further include means for receiving, from the user equipment, the transport block based on the configuration. According to certain example embodiments, the at least one code block may be located at an end or a beginning of the transport block based on the configuration.

[0094] Other example embodiments may be directed to an apparatus that includes means for performing any of the methods described herein including, for example, means for preparing a transport block for uplink transmission to a network element. The apparatus may also include means for attaching bits of feedback information to the transport block. The apparatus may further include means for encoding the bits of the feedback information separately from the transport block. In addition, the apparatus may include means for transmitting, to the network element, the transport block comprising the bits of the feedback information.

[0095] FIG. 14 illustrates an example of a 5G / 6G network and system architecture, according to certain example embodiments. Shown are multiple network functions that may be implemented as software operating as part of a network device or dedicated hardware, as a network device itself or dedicated hardware, or as a virtual function operating as a network device or dedicated hardware. The UE illustrated in FIG. 13 may be similar to UE 10. The user plane function (UPF) may provide services such as intra-RAT and inter-RAT mobility, routing and forwarding of data packets, inspection of packets, user plane quality of service (QoS) processing, buffering of downlink packets, and / ortriggering of downlink data notifications. The application function (AF) may primarily interface with the core network to facilitate application usage of traffic routing and interact with the policy framework.

[0096] FIG. 15 illustrates an example 6G architecture, according to certain example embodiments. In particular, the 6G architecture in FIG. 14 may support LCM configured to natively support AI / ML, cloud-native functionalities. Additionally, 6G gNBs may be configured to support multi-RAT spectrum sharing (MRSS).

[0097] FIG. 16 illustrates an example 6G RAN protocol stack, according to certain example embodiments. The 6G RAN protocol stack may share some similarities with a 5G RAN protocol stack. For example, the depicted 6G RAN protocol stack may incorporate service data application protocol (SDAP), packet data convergence protocol (PDCP), radio link control (RLC), and medium access control (MAC) functions, which may interface with multiple radio protocol units (RPUs).

[0098] Certain example embodiments described herein provide several technical improvements, enhancements, and / or advantages. For instance, in some example embodiments, it may be possible to reduce the latency of delay-critical MAC-CEs in the UL at least because the information is transmitted in a separate, self-decodable CB / CBG that the gNB can immediately process and forward to the PHY layer if it contains CSI and / or HARQ ACK / NACK. In certain example embodiments, the information may be transmitted without waiting for all the CBs in the TB to be correctly received. According to other example embodiments, the use of more conservative MCS for the CBs with delay-critical MAC-CE information may lower the BLER for such CBG that includes the delay-critical information. The BLER may be lower than the usual 10%-20% BLER for UL transmissions. Use of these conservative MCS may also make it possible to run separate HARQ strategies for delay-critical MAC-CEs (e g., no HARQ for delay-critical MAC-CEs).

[0099] In other example embodiments, using MAC-CE for feedback information provides a flexible and scalable solution as compared to using PUCCH. This may be particularly relevant for 6G which may include multibit HARQ feedback, larger and variable size CSI feedback (given larger number of supported antenna ports), and flexible support for carrier aggregation (CA).

[0100] A computer program product may include one or more computerexecutable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of it. Modifications and configurations required for implementing functionality of certain example embodiments may be performed as routine(s), which may be implemented as added or updated software routine(s). Software routine(s) may be downloaded into the apparatus.

[0101] As an example, software or a computer program code or portions of it may be in a source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and / or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

[0102] In other example embodiments, the functionality may be performed by hardware or circuitry included in an apparatus (e.g., apparatus 10 or apparatus 20), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array(FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, a non-tangible means that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0103] According to certain example embodiments, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, including at least a memory for providing storage capacity used for arithmetic operation and an operation processor for executing the arithmetic operation.

[0104] One having ordinary skill in the art will readily understand that the disclosure as discussed above may be practiced with procedures in a different order, and / or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the disclosure has been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments. Although the above embodiments refer to 5G NR and LTE technology, the above embodiments may also apply to any other present or future 3GPP technology, such as LTE-advanced, and / or fourth generation (4G) technology.

[0105] Partial Glossary:

[0106] 3GPP 3rd Generation Partnership Project

[0107] 5G 5th Generation

[0108] 5GC 5G Core

[0109] 5GCN 5G Core Network

[0110] 5GS 5G System

[0111] 5QI 5G QoS Identifier

[0112] BS Base Station

[0113] CB Code Block

[0114] CBG Code Block Group

[0115] CE Control Element

[0116] CQI Channel Quality Indicator

[0117] DCI Downlink Control Information

[0118] DL Downlink

[0119] eNB Enhanced Node B

[0120] E-UTRAN Evolved UTRAN

[0121] gNB 5G or Next Generation NodeB

[0122] LCH Logical Channel

[0123] LTE Long-Term Evolution[0124JLTE-M Long-Term Evolution Machine Type Communication

[0125] MAC Medium Access Control[0126JMAC-CE MAC Control Element

[0127] MCS Modulation and Coding Scheme

[0128] NR New Radio

[0129] NW Network

[0130] PDCCH Physical Downlink Control Channel

[0131] PDSCH Physical Downlink Shared Channel

[0132] PUCCH Physical Uplink Control Channel

[0133] PUSCH Physical Uplink Shared Channel

[0134] RAN Radio Access Network

[0135] RRC Radio Resource Control

[0136] UE User Equipment

[0137] UL Uplink

Claims

WE CLAIM:

1. An apparatus, comprising:at least one processor; andat least one memory including computer program code which, when executed by the at least one processor, cause the apparatus to at least:prepare a transport block for uplink transmission to a network element;attach bits of feedback information to the transport block; encode the bits of the feedback information separately from the transport block; andtransmit, to the network element, the transport block comprising the bits of the feedback information.

2. The apparatus according to claim 1, wherein the feedback information comprises at least hybrid automatic repeat request feedback information.

3. The apparatus according to claims 1 or 2, wherein the bits of the feedback information are encoded using a different coding rate compared to the rest of the transport block that does not include the hybrid automatic repeat request bits.

4. The apparatus according to any one of claims 1-3, wherein the bits of the feedback information are separately encoded.

5. The apparatus according to any one of claims 1-4, wherein the computer program code, when executed by the at least one processor, further causes the apparatus to at least:determine the bits of the feedback information of a received transmission.

6. The apparatus according to claim 5, wherein the computer program code, when executed by the at least one processor, further causes the apparatus to at least:transmit a physical uplink shared channel with the bits of feedback information to the network element.

7. An apparatus, comprising:means for preparing a transport block for uplink transmission to a network element;means for attaching bits of feedback information to the transport block; means for encoding the bits of the feedback information separately from the transport block; andmeans for transmitting, to the network element, the transport block comprising the bits of the feedback information.

8. The apparatus according to claim 7, wherein the feedback information comprises at least hybrid automatic repeat request feedback information.

9. The apparatus according to claims 7 or 8, wherein the bits of the feedback information are encoded using a different coding rate compared to the rest of the transport block that does not include the hybrid automatic repeat request bits.

10. The apparatus according to any one of claims 7-9, wherein the bits of the feedback information are separately encoded.

11. The apparatus according to any one of claims 7-10, further comprising: means for determining the bits of the feedback information of a received transmission.

12. The apparatus according to claim 11, further comprising:means for transmitting a physical uplink shared channel with the bits of feedback information to the network element.

13. A method, comprising:preparing a transport block for uplink transmission to a network element;attaching bits of feedback information to the transport block; encoding the bits of the feedback information separately from the transport block; andtransmitting, to the network element, the transport block comprising the bits of the feedback information.

14. The method according to claim 13, wherein the feedback information comprises at least hybrid automatic repeat request feedback information.

15. The method according to claims 13 or 14, wherein the bits of the feedback information are encoded using a different coding rate compared to the rest of the transport block that does not include the hybrid automatic repeat request bits.

16. The method according to any one of claims 13-15, wherein the bits of the feedback information are separately encoded.

17. The method according to any one of claims 13-16, further comprising:determining the bits of the feedback information of a received transmission.

18. The method according to claim 17, further comprising:transmitting a physical uplink shared channel with the bits of feedback information to the network element.

19. A non- transitory computer readable medium comprising program instructions stored thereon for performing the method according to any of claims 13-18.

20. An apparatus comprising circuitry configured to cause the apparatus to perform the method according to any of claims 13-18.

Images