CN111557078A - Acknowledgement signaling procedure for radio access network - Google Patents

Abstract

A method of operating a target radio node (10, 100) in a radio access network is disclosed. The method comprises the following steps: receiving control information transmitted on a control channel; and transmitting acknowledgement feedback related to the control information. The disclosure also relates to related methods and devices.

Description

Acknowledgment Signalling Procedures for Radio Access Networks

technical field

The present disclosure relates to wireless or telecommunication communication technologies, and in particular to radio access technologies such as for mobile communication.

Background technique

Currently, fifth-generation radio telecommunication technologies are being developed with the goal of serving various use cases. Therefore, the relevant systems must be very flexible and may need to convey new kinds of signaling and information.

One area of particular importance for many applications involves reliability of signaling.

SUMMARY OF THE INVENTION

It is an object of the present disclosure to propose a method that allows the reliability of signaling to be improved by applying an acknowledgment signaling procedure to control signaling. The method is particularly advantageously implemented in fifth generation (5G) telecommunication networks or 5G radio access technologies or networks (RAT/RAN), in particular according to 3GPP (3rd Generation Partnership Project, Standardization Organization). In particular, a suitable RAN may be a RAN according to NR (eg, Release 15 or later) or LTE evolved. It should be noted that in the following, the terms data (sub)structure and data block (sub)structure may be used synonymously.

Accordingly, a method of operating a target radio node in a radio access network is disclosed. The method includes: receiving control information transmitted on a control channel; and transmitting acknowledgement feedback related to the control information.

A target radio node of a radio access network is also disclosed. The target radio node is adapted to receive control information transmitted on the control channel. Furthermore, the target radio node is adapted to transmit acknowledgement feedback related to the control information. The target radio node may comprise and/or be adapted to utilize processing circuits and/or radio circuits, in particular transmitters and/or receivers and/or transceivers, in order to receive eg control information and/or transmit eg acknowledgement feedback.

A radio node that is or may be the target of transmission of eg control information and/or data signaling may be considered a target radio node. In particular, the target radio node may be a user equipment or a terminal. However, in some scenarios, eg for backhaul or relay signaling, the target radio node may be a network node.

Furthermore, a method of operating a transmitting radio node in a radio access network is described. The method includes retransmitting the control information to the target radio node based on acknowledgement feedback related to the control information. Alternatively or additionally, the method may include transmitting a control message to the target radio node, the control message including the control information and error coding information error coding the control information.

A transmitting radio node of a radio access network can be considered. The transmitting radio node is adapted to retransmit the control information to the target radio node based on acknowledgement feedback related to the control information. Alternatively or additionally, the transmitting radio node may be adapted to transmit a control message to the target radio node, the control message comprising the control information and error encoding information error encoding the control information. The transmitting radio node may comprise and/or be adapted to utilize processing circuits and/or radio circuits, in particular transmitters and/or receivers and/or transceivers, in order to receive e.g. acknowledgement feedback and/or transmit and/or retransmit e.g. control information and/or control messages and/or in order to error-encode control information.

With the methods described herein, control information is subject to an acknowledgment signaling process directly related to the control information, allowing improved reliability of control information, especially control information for unscheduled data transmissions (eg for reception or transmission) sex.

In general, confirmation feedback associated with control information may also be referred to as control confirmation feedback or control feedback.

The transmitting radio node may be a radio node adapted to transmit signaling, eg representing or including control information and/or data, to the target radio node. In particular, the transmitting radio node may be a network node. However, in some scenarios, eg for sidelink signaling, the transmitting radio node may be a user equipment or a terminal.

Performing the retransmission may be based on, and/or may include, receiving acknowledgement feedback, eg, on indicated and/or configured resources and/or channels and/or according to indicated and/or configured codebooks. For example, the codebook may be dynamically configured with a number of control messages like dispatch-type messages or assignment and/or command-type messages. Performing the retransmission may include transmitting the control information again if the control information is not correctly received, eg, based on feedback. This retransmission may use a different transmission format or mode and/or MCS and/or error coding than the previous transmission. The number of transmissions of certain control information may be counted, and in some cases may be limited in number by a threshold, which may be predefined and/or configurable or configurable. If the threshold is reached, retransmissions can be stopped. It can be considered that performing the retransmission includes: transmitting new control information; and/or ignoring the retransmission of the control information if the feedback indicates correct reception.

Control information may generally be conveyed in control messages, eg, on the physical layer or channel, eg, as DCI messages or SCI messages. A control message may be a command-type message, which may include and/or consist of command-type information, or a scheduling-type message, which may include scheduling information, such as scheduling data signaling.

Control information may include scheduling-type control information (or simply scheduling-type information), such as control information indicating resources and/or transmission parameters for receiving signaling, and/or indicating resources and/or transmissions for transmitting signaling Control information for the parameter. In particular, the signaling may be data signaling, eg on a data channel.

In particular, the control information may comprise or consist of command-type control information, and/or may be included in command-type messages. In general, control information or control messages, such as DCI or SCI messages, can be distinguished between scheduling-type information/messages and command-type information/messages. Scheduling messages may schedule transmissions on a data channel (data signaling), eg for reception or transmission by the target radio node, eg, in the downlink or uplink, respectively. Scheduling grants and scheduling assignments are examples of such scheduling-type messages. Since data channel transmissions for reception typically undergo an acknowledgment signaling process, the transmitting radio node may, at least to a limited extent, infer receipt of scheduling assignments from acknowledgement signaling associated with scheduling transmissions for reception. For data channel transmissions transmitted by the target radio node, the transmission itself allows some inferences to be made about the receipt of scheduling grants. The command message can be a different type of message, such as not scheduling transmissions on the data channel. Command messages may include sets of instructions, which may be configurable or flexible. Instructions can be independent of scheduling. For example, the command-type information may indicate and/or command switching of bandwidth to, for example, another bandwidth portion, and/or activation or deactivation of a carrier and/or cell and/or bandwidth portion, and/or activation or deactivation of exempt transmissions, and/or an indication of selecting a parameter or configuration from a set of configured parameters or configurations. In some variations, the command message may be independent of scheduling, such that it does not schedule data signaling, or it may have a structure in which such scheduling may be configurable or optional. For a command type, there may be no scheduled transmission on which the reception of inferred control information may be based. Therefore, these methods are particularly suitable for this situation. However, with the methods described herein, the handling of dispatched messages can also be advantageously improved, especially with regard to reliability, as immediate and unambiguous feedback can be provided. It should be noted that scheduling-type messages may include command-type information.

The scheduling of the transmission or reception of data signaling may be referred to as the scheduling of the corresponding data channel. Data channels can be shared or dedicated channels. Examples of data channels are: PDSCH in downlink, PUSCH in uplink, PSSCH channel in sidelink. Dedicated data channels may be considered, especially for low latency and/or high reliability transmission, eg for URLLC.

Transmitting acknowledgement feedback may generally include and/or be based on determining feedback information, such as one or more feedback or ACK/NACK bits. Such determination may include performing error decoding, eg, based on error-encoded bits, eg, CRC and/or FEC bits associated with control information that may be included in a control message carrying control information. Error decoding may include, for example, correcting control information based on the FEC bits. The error coded bits may be determined based on the control information, eg using an error coding scheme like CRC, and/or polar coding, or LDPC coding or Reed Muller coding. Control information can be represented by bits. Control information and, in some cases, error coding bits associated therewith (like error detection bits and/or error correction bits, such as CRC and/or FEC bits) may be considered to represent one or more data structures or substructures in which Each of the acknowledgment feedback may include one or more feedback bits, eg, to indicate ACK or NACK. Thus, at least one bit may be provided for the entire control information and/or control message, and/or one bit may be provided for one or more of its substructures, a corresponding error code may be associated to and/or provided for example in the control message the one or more substructures. Control messages can be considered similar to transport blocks and/or groups of code blocks. Acknowledgment process identifiers, such as HARQ or ARQ identifiers, may be associated with control information and/or control messages. Bit subpatterns representing reception (eg, ACK/NACK or DTX/DRX) can generally be associated with control information in acknowledgement feedback.

Alternatively or additionally, transmitting the acknowledgment feedback may include and/or be based on the resources selected for transmitting the acknowledgment feedback. In particular, the resources may be time and/or frequency and/or code resources, which in some variations may be selected or selectable from one or more resources or resource regions or resource pools. Such resources or area(s) or pool(s) may be configured for the target radio node.

In general, acknowledgement feedback may be transmitted on resources scheduled and/or indicated by control messages, particularly control messages carrying control information. The resources may be time and/or frequency and/or code resources.

In general, it may be considered that resources may be selected from a pool of resources configurable for the target radio node, eg based on feedback from higher layer signaling (eg MAC or RRC signaling), especially for command-type messages. These resources may be associated with specific channels, and/or may be specifically associated with acknowledgement feedback for control information. In some cases, resources may be widely configured for use by the target radio node. These resources may be in the same transmission timing structure as the received control information, or may be in a subsequent structure, such as the next structure in which the resource is available and/or the structure indicated by the configuration and/or the control message carrying the control information middle. In particular, the transmission timing structure may be a time slot. In some cases, resources may be associated with non-slot-based transmissions. These resources can be considered to be resources used for data signaling, such as PUSCH ("UCI on PUSCH"). Acknowledgement feedback can be rate matched or punctured on such resources.

In some variations, the control information includes a response resource indication indicating resources and/or transmission parameters used to transmit acknowledgement feedback. For example, the indication may indicate, respectively: a channel, such as a control channel, eg, PUCCH, which may be a short PUCCH or a long PUCCH; and/or non-slot-based or slot-based. Alternatively or additionally, the indication may indicate a resource, a resource set or resource region or resource pool, or one or more sets or regions or pools from which resources may be selected for transmission. The indication may indicate resources used for data signaling, such as PUSCH resources. In this case, the resource may be implicitly indicated by a control message carrying control information, and may optionally be configured with another message (eg, scheduling grant or higher layer signaling). The indicated resource may be represented by indicating the transmission timing structure (eg, a slot or minislot or subframe) in which the feedback must be transmitted, such as the received structure or subsequent (eg, latest or equal) N structures (wherein N>0). Selecting resources may include selecting resources from available (eg, configured) resources for transmission in the indicated transmission timing structure.

In some variations, the control information may include signaling (eg, data signaling) indicating for transmission of the second acknowledgment feedback (the second acknowledgment feedback relates to the second information) and/or for reception by the target radio node The second response resource indication of the second resource. The second response resource indication may be in addition to or in place of the response resource indication described herein. In particular, the second information may be transmitted and/or scheduled for transmission on the data channel, and/or represented or carried by data signaling. The second information may be indicated for receipt, and/or configured and/or scheduled by control information and/or control messages (eg, scheduling assignments) carrying control information. Alternatively or additionally, the second information may be configured or scheduled by another message (eg, a second control message). For example, from a target radio node configurable or configurable by a control message, eg, using a second response resource indication, or using one or more other messages (eg, via higher layer signaling like MAC or RRC signaling) The second resource is selected or selectable from the resource and/or resource set and/or resource area and/or resource pool. The resources and/or sets and/or regions and/or pools may be the same or different from the resources and/or sets and/or regions and/or pools used for acknowledgement feedback.

Transmitting the acknowledgment feedback may include transmitting the second acknowledgment feedback, eg, on the same or different resources as the acknowledgment feedback. In particular, the second acknowledgment feedback may be combined with the acknowledgment feedback for transmission.

The acknowledgment feedback and/or the second acknowledgment feedback may be transmitted based on a feedback codebook (eg, a HARQ codebook). A codebook may indicate which feedback bit/bits relate to which transmission and/or information and/or data structure (eg, transport block or code block or group of code blocks), eg, indicating acknowledgement or non-acknowledgement or non-transmission/reception.

It may be considered that transmitting the confirmation feedback is based on determining whether the control information and/or the second information has been received correctly, eg based on error coding and/or quality of reception. For example, the reception quality may be based on the determined signal quality.

Control information may be conveyed in control information messages, particularly on control channels, which may be dedicated or shared channels, such as physical channels. In particular, the channel may be PDCCH or common control channel or PSCCH.

In some variations, the control information may include an indication of the location of the acknowledgement feedback relative to the second acknowledgement feedback and/or in the feedback codebook. The second acknowledgement feedback and/or the associated second resource may be indicated in a control message (eg, a control message carrying control information). The location indication may include an indicator such as a Downlink Assignment Indicator (DAI), which may indicate a data structure for which acknowledgement feedback (eg, control feedback and/or other acknowledgement feedback) is scheduled and/or indicated (eg, control feedback and/or other acknowledgement feedback). transport blocks and/or code blocks and/or code block groups and/or messages and/or control/command messages) or count the number. Different control messages (eg, scheduling assignments) may include, eg, different-valued indicators representing counts. The control message may optionally include a total number indicator, which may indicate the total number of data structures for which feedback is scheduled and/or indicated. Such indicators may be referred to as total DAI. Alternatively or additionally, the location indication and/or indicator may indicate the scheduling and/or indicate the count or total number of bits used for feedback, respectively. The count may relate to the HARQ codebook, eg indicating where in the HARQ codebook the bit sub-patterns representing the feedback information of the data structure will be located. It is believed that different codebooks may be used for different types of data structures and/or channels and/or resource pools. The combined feedback may be based on the same codebook. In some variations, sub-pattern combinations involving control information may also involve data signaling, such as scheduling data signaling for reception, which may be scheduled through control messages carrying control information. In this case, there may be only one indicator, eg indicating a count, based on which the target radio node may include the sub-pattern in the codebook. The sub-pattern combination may include a sub-pattern indicating receipt of control information and a sub-pattern indicating receipt of data signaling, eg, in a pre-defined, or configured, or configurable order. For example, a sub-mode combination may include two bits, one of which may indicate ACK/NACK for control information and the other bit that indicates ACK/NACK for data signaling. Other orders or different sub-patterns may be considered.

Information, particularly control information, may be carried in associated messages that may be carried and/or represented by associated signaling. Information and/or messages and/or signaling may be associated with a particular channel. Accordingly, the information may be considered to be carried by the corresponding signaling and messages and/or on the associated channel.

In general, acknowledgement feedback may be transmitted on a control channel, eg, a dedicated or shared control channel, which may be a physical channel. For example, acknowledgement feedback may be transmitted on PUCCH or PSCCH.

In some variations, the acknowledgement feedback may be transmitted on a data channel, such as a dedicated or shared data channel, which may be a physical channel. For example, acknowledgement feedback may be transmitted on PUSCH or PSSCH.

Also described is a program product comprising instructions adapted to cause processing circuitry to control and/or perform the methods described herein.

A carrier medium arrangement that carries and/or stores the program product described herein is also contemplated.

In general, acknowledgment feedback or acknowledgment information related to transmissions and/or information (eg, control information) may be information that allows (at least) an ACK or NACK indicating information, such as a message or data structure or a substructure thereof. In some cases, instead of NACK, no feedback transmission may be provided in, for example, only one bit or one sub-mode codebook related to control information. In this case, a node expecting feedback may consider the non-transmission to be a NACK or an indication that the control message/information has been received in error or has not been received.

Acknowledgement feedback may also be referred to as acknowledgement response (or simply feedback), and/or may be considered a form of acknowledgement signaling. These terms are used interchangeably. The acknowledgment feedback may represent uplink signaling, control information or control signaling, and the control signaling involved in the acknowledgment feedback or signaling may be downlink signaling. However, a variant in which both are sidelink signaling (with different communication directions) are envisaged. In particular, the acknowledgement feedback may be HARQ feedback.

Acknowledgement signaling may generally represent and/or include and/or contain acknowledgement information, which may be structured based on a feedback configuration (eg, a codebook). The codebook may generally be dynamic, eg, based on one or more control messages, such as DCI information and/or scheduling assignments and/or command-type messages. Variations with one or more configured and/or predefined and/or static codebooks may be considered.

Configuration may generally be indicated and/or configured using one or more messages that may be associated with the same or different layers or types (eg, physical layer and/or RLC layer and/or MAC layer and/or RRC and/or DCI) . In particular, part of the configuration may be indicated and/or configured semi-statically/and/or using RRC and/or MAC signaling, and/or part may be pre-configured or pre-defined, and/or part may use eg DCI or SCI Signaling is dynamically indicated and/or configured.

The acknowledgement information may represent and/or include one or more bits, in particular a pattern of bits. A number of bits associated with a data substructure can be considered as subpatterns. The structure of the acknowledgment information may indicate the order, and/or meaning, and/or mapping and/or pattern of bits (or subpatterns of bits) of the information. The acknowledgment configuration, especially the feedback configuration, may indicate the size and/or the arrangement and/or mapping of the acknowledgment information carried by the acknowledgment signaling involved in the configuration. In particular, the structure or mapping may indicate: one or more data block structures, such as code blocks and/or groups of code blocks and/or transport blocks and/or messages, such as command messages, to which the acknowledgement information relates; and/or which The data block structure to which the bit or subpattern of bits is associated. In some cases, the mapping may involve one or more acknowledgment signaling processes (eg, processes with different identifiers) and/or one or more different data streams. The configuration may indicate which process(s) and/or data flow(s) the information relates to. In general, acknowledgement information may include one or more sub-patterns, each of which may relate to a data block structure, such as a code block or group of code blocks or a transport block. The sub-patterns may be arranged to indicate acknowledgment or non-acknowledgement of the associated data block structure or another retransmission state (eg non-scheduled or non-received). A sub-pattern can be considered to contain one bit, or in some cases more than one bit. It should be noted that the acknowledgment information may undergo significant processing before being transmitted as acknowledgment signaling. Different configurations may indicate different sizes and/or mappings and/or structures and/or modes.

The acknowledgment configuration, particularly the feedback configuration, may generally indicate the number of bits of acknowledgment information represented by the acknowledgment signaling and/or the size of the acknowledgment information, where the size may be represented by the number of bits and/or the number of modulation symbols.

It can be considered that the acknowledgment configuration, especially the feedback configuration, may indicate one or more acknowledgment bit sub-patterns to one or more data block structures involved in the acknowledgment bit sub-pattern (eg, to one or more code block groups or one or more transmissions). block or a combination thereof). An acknowledgement bit pattern may represent acknowledgement information, and an acknowledgement bit subpattern may represent a subpattern of the pattern.

The transport format may generally indicate one or more data block structures or substructures for transmission or reception and/or how to divide data blocks (eg, transport blocks) (and/or related structures) into, for example, sub-blocks or groups of sub-blocks, Such as one/more code blocks and/or one/more code block groups. In some cases, the transport format may involve more than one data block, and/or may involve more than one acknowledgment signaling process. It can be considered that the transport format indicates the size (in bits) and/or encoding of the one or more data block structures or substructures. The transport format may relate to signaling to be transmitted by the radio node or signaling to be received and/or acknowledgment signaling related to the signaling to be received. For different communication directions and/or different carrier and/or bandwidth parts and/or sets thereof and/or different configurations (especially different configurations of the set of confirmed configurations), available (eg, defined and/or configured) different transfer formats. In particular, the transport format used for transmission on the transport resource may be different from the transport format associated with the acknowledgment configuration (eg feedback configuration). The transport formats may be configured independently of each other, eg using different messages and/or different signaling, eg on different layers of the protocol stack.

An acknowledgment configuration (eg, a feedback configuration) may generally be a code block group configuration, which may indicate a mapping of one or more acknowledgment information sub-patterns (eg, one or more bits) to one or more code block groups, each of which A code block group may comprise or consist of the same or a different number of code blocks, in particular one or more code blocks. Each sub-pattern can be mapped to a code block group. In some variations, the acknowledgement configuration may indicate a mapping of one or more sub-modes to one or more transport blocks, each of which may include and/or consist of one or more code block groups composition. Each sub-mode can be mapped to a transport block. The acknowledgment configuration may involve a combination of one/more code block groups and one/more transport blocks, in particular with regard to the structure or transport format of the corresponding acknowledgment information. Feedback or acknowledgment information related to code block groups or transport blocks or code blocks may be configured and/or formatted in consideration of acknowledgment configuration.

The data block structure may correspond to data blocks scheduled for, eg, data signaling. For example, in the context of carrier aggregation and/or multi-antenna transmission (eg, MIMO (multiple-input multiple-output)), data blocks may be associated to individually scheduled transmissions, eg, separate channels and/or instances and/or carriers and/or Component carriers and/or data streams. The data blocks and/or associated data signaling may be used for the downlink, or in some cases, the sidelink. Acknowledgement signaling may generally be uplink signaling, but in some variations may be sidelink signaling. However, the case where the data signaling is uplink signaling can be considered, eg in the context of retransmission performed by the user equipment. The sub-pattern may represent, for example, acknowledgement information and/or feedback for the associated data block of the size indicated by the assignment indication. Different data blocks may be associated with different transmission instances and/or different acknowledgement signaling processes, eg, HARQ processes. The acknowledgment signaling procedures may include one or more acknowledgment signaling procedures that may involve the same communication direction.

A data block structure (or simply a data structure) may generally represent and/or be associated with scheduled data blocks and/or corresponding signaling. Data blocks may be scheduled for reception by eg control signaling (in particular control information messages), which may be scheduling assignments. In some cases, the scheduled data blocks may not be received, which may be reflected in the corresponding acknowledgment signaling. The number of data transmissions scheduled to be received by the user equipment (or the second radio node) may be represented by the number of data block structures and/or the number of assignment indications.

A data block structure may generally represent and/or correspond to a data block, which may generally be a block of data and/or bits. For example, a data block may be a transport block, a code block or a group of code blocks. It is contemplated that the data block structure represents a data block that is expected to undergo an acknowledgment signaling process. A data block may include one or more sub-blocks, which may be grouped into one or more sub-block groups, such as code block groups. In particular, a data block may be a transport block, which may include one or more code blocks and/or one or more code block groups. Transport blocks, code blocks or groups of code blocks can be represented accordingly in consideration of the data block structure. A sub-block group, such as a code block group, may include one or more sub-blocks, eg, code blocks. It is contemplated that a data block includes one or more groups of sub-blocks, which may be of the same or different sizes (eg, in terms of, eg, systematic and/or number of coded bits). It is conceivable that a data block comprises information bits or systematic bits (which can be regarded as representing the data to be transmitted and/or error detection bits) and/or coding bits, eg for error coding (such as error detection and/or especially error correction coding) ) bits and/or parity or CRC (Cyclic Redundancy Check) bits. Sub-blocks (eg, code blocks) and/or groups of sub-blocks (eg, groups of code blocks) may similarly include systematic and/or coded bits. In some cases, systematic bits may be considered to include information and error detection bits determined based on information bits. The parity bits can be thought of as representing error correction coded bits. It should be noted that for a data structure (such as a transport block) that includes one or more substructures (eg, CBGs or code blocks), the systematic bits and possibly parity bits of the substructure can be considered as information bits, which can be based on bits to perform error detection coding and/or error correction coding.

The acknowledgement signaling process may be a HARQ process, and/or identified by a process identifier (eg, a HARQ process identifier or sub-identifier). Acknowledgment signaling and/or associated acknowledgment information may be referred to as feedback. It should be noted that it is contemplated that the data blocks or structures that the sub-pattern may relate to carry data (eg, information and/or system and/or coded bits). However, depending on the transmission conditions, such data may or may not be received (or not received correctly), which may be indicated in the feedback accordingly. In some cases, the subpattern of acknowledgement signaling may include padding bits, eg, if the acknowledgement information for the data block requires fewer bits than indicated by the size of the subpattern. This can happen, for example, if the size is indicated with a larger cell size than is required for the feedback.

The acknowledgment information may generally indicate at least an ACK or NACK related to, eg, an acknowledgment signaling process or an element of a data block structure (eg, a data block, sub-block group, or sub-block). In general, there may be a specific sub-pattern and/or data block structure associated to the acknowledgment signaling process for which acknowledgment information may be provided.

The acknowledgment signaling process may determine a data block (eg, a transport block) based on coded bits associated with the data block and/or based on coded bits associated with one or more data blocks and/or sub-blocks and/or one or more sub-block groups. ) and/or its substructures of correct or incorrect receipt and/or corresponding confirmation. The acknowledgment information (determined by the acknowledgment signaling process) may relate to the entire block of data, and/or to one or more sub-blocks or groups of sub-blocks. A code block can be considered an example of a sub-block, and a group of code blocks can be considered an example of a group of sub-blocks. Accordingly, the associated sub-pattern may include one or more bits indicating the reception status or feedback of a data block and/or one or more bits indicating the reception status or feedback of one or more sub-blocks or groups of sub-blocks. The bits of each sub-pattern or sub-pattern may be associated and/or mapped to a particular data block or sub-block or group of sub-blocks. In some variations, correct receipt of a data block may be indicated if all sub-blocks or groups of sub-blocks are correctly identified. In this case, the sub-pattern may represent acknowledgment information for the entire data block, thereby reducing overhead compared to providing acknowledgment information for a sub-block or group of sub-blocks. The smallest structure (eg, subchunk/subchunk/data chunk) to which a submode provides confirmation information and/or is associated can be considered to be its (highest) resolution. In some variations, the sub-patterns may provide confirmation information about several elements of the data block structure and/or at different resolutions, eg, to allow more specific error detection. For example, even though the sub-mode indicates acknowledgement signaling related to the entire data block, in some variations, the sub-mode may provide higher resolution (eg, sub-block or sub-block group resolution). A sub-pattern may generally include one or more bits indicating ACK/NACK for a data block and/or one or more bits indicating ACK/NACK for a sub-block or group of sub-blocks or more than one sub-block or group of sub-blocks.

Sub-blocks and/or groups of sub-blocks may include information bits (which represent data to be transmitted, eg, user data and/or downlink/sidelink data or uplink data). It is contemplated that data blocks and/or sub-blocks and/or sub-block groups further include one or more error detection bits, which may be related to and/or determined based on information bits (for sub-block groups, The one/more error detection bits may be determined based on information bits and/or error detection bits and/or error correction bits of one/more sub-blocks of the sub-block group). Data blocks or substructures (eg, subblocks or groups of subblocks) may include error correction bits, in particular, these error correction bits may be based on the information of the block or substructure, eg, using an error correction coding scheme (eg, LDPC or polar coding) bits and error detection bits to determine. In general, the error correction coding of a data block structure (and/or associated bits) may cover and/or relate to the information bits and error detection bits of the structure. A sub-block group may represent a combination of one or more code blocks (corresponding bits, respectively). A data block may represent a code block or group of code blocks or a combination of more than one group of code blocks. For example, the transport block may be split into code blocks and/or code blocks based on the bit size of the information bits of the higher layer data structures provided for error coding and/or size requirements or preferences for error coding (especially error correction coding) Group. Such higher-layer data structures are also sometimes referred to as transport blocks, which in this context represent information bits that do not have the error-coding bits described herein, but may contain higher-layer error handling, for example, for Internet protocols such as TCP (errorhandling) information. However, in the context of the present disclosure, such error handling information represents bits of information as the described acknowledgement signaling process handles them accordingly.

In some variations, a subblock (eg, a code block) may include error correction bits, which may be determined based on one/more information bits and/or one/more error detection bits of the subblock. Error correction coding schemes may be used to determine error correction bits, eg, based on LDPC or polar coding. In some cases, a sub-block or code block may be considered to be defined as including information bits, one/more error detection bits determined based on the information bits, and one/more correction bits determined based on the information bits and/or one/more error detection bits A pattern or block of misplaced bits. It is contemplated that, within a sub-block (eg, a code block), information bits (and possibly one/more error correction bits) are protected and/or covered by an error correction scheme or corresponding error correction bit/bits. A code block group may include one or more code blocks. In some variations, no additional error detection bits and/or error correction bits are applied, however, application of either or both may be contemplated. A transport block may include one or more code block groups. It is contemplated that no additional error detection and/or error correction bits may be applied to the transport block, however, either or both may be contemplated. In some specific variations, the code block group(s) do not include additional error detection or error correction coding layers, and the transport block may only include additional error detection coded bits, but not additional error correction coding. This is especially the case if the transport block size is larger than the code block size and/or the maximum size for error correction coding. A sub-pattern of acknowledgment signaling (specifically indicating ACK or NACK) may relate to the code block, eg, to indicate whether the code block has been received correctly. It can be considered that sub-patterns refer to sub-groups (eg code block groups) or data blocks (eg transport blocks). In such a case, it may indicate an ACK if all sub-blocks or code blocks of the group or data/transport block were received correctly (eg, based on a logical AND (AND) operation); and if at least one sub-block has not been received correctly or code block, it may indicate a NACK or another state of incorrect reception. It should be noted that a code block is considered to be correctly received not only when it has actually been received correctly, but also when it is correctly reconstructed based on soft combining and/or error correction coding.

A sub-mode may involve an acknowledgment signaling process and/or a carrier (eg, a component carrier) and/or a data block structure or data block. In particular, it is contemplated that one (eg, specific and/or single) sub-pattern involves (eg, maps via a codebook to) one (eg, specific and/or single) acknowledgment signaling process, such as specific and/or or a single HARQ process. It is contemplated that, in a bit pattern, sub-patterns map on a one-to-one basis to acknowledgment signaling procedures and/or data blocks or data block structures. In some variations, there may be multiple sub-modes (and/or associated acknowledgment signaling procedures) associated to the same component carrier, eg, if multiple data streams transmitted on the carrier are subject to acknowledgment signaling procedures. A subpattern may include one or more bits, the number of which can be considered to represent its size or bit size. Different n-tuples of bits of a sub-pattern (n being 1 or greater) may be associated with different elements of a data block structure (eg, a data block or sub-block or group of sub-blocks), and/or represent different resolutions. Variations in which bit patterns (eg, data blocks) represent only one resolution can be considered. The n-tuple of bits may represent acknowledgment information (aka feedback), in particular ACK or NACK, and optionally (if n>1), DTX/DRX or other reception status. ACK/NACK may be represented by one bit or by more than one bit, eg, to improve disambiguation of bit sequences representing ACK or NACK and/or to improve transmission reliability.

In general, acknowledgement signaling may be signaling at one instance and/or within a transmission timing structure, and/or scheduled for common transmission, and/or may jointly encode and/or modulate acknowledgement information. The acknowledgment information may relate to a number of different transmissions, which may be associated with and/or represented by a data block structure, associated data blocks or data signaling, respectively. The data block structure and/or corresponding blocks and/or may be scheduled for synchronous transmissions, for example, for the same transmission timing structure, in particular within the same time slot or subframe and/or on the same symbol/symbols or signaling. However, alternatives to scheduling utilizing asynchronous transmissions may be considered. For example, the acknowledgement information may relate to data blocks scheduled for different transmission timing structures (eg, different time slots (or minislots or timeslots and minislots), etc.), which may be received (or not received accordingly) or received incorrectly). Scheduling signaling may generally include signaling indicative of resources, such as time and/or frequency resources, such as for receiving or transmitting scheduling.

A radio node, in particular a configuration radio node in general, may be adapted to schedule data block or subject transmissions for transmission, and/or be adapted to provide and/or determine and/or configure associated assignment indications, which may include total Assign instructions. Configuring the second radio node or UE may include an associated determination and/or configuration and/or provision of such scheduling and/or assignment indications.

The resource structure may represent time and/or frequency and/or code resources. In particular, the resource structure may comprise multiple resource elements and/or one or more resource blocks/PRBs. There may be signaling types (especially control signaling) and/or signaling formats and/or latency requirements associated with the resource structure. In particular, the latency requirement may define when the response has to be transmitted after the signalling is received, eg with a delay that can account for processing. The requirement may define a delay of 1 symbol or 2 symbols between the end of received signaling and the transmission of response control signaling, particularly acknowledgement signaling related to received signaling (eg, data signaling) . The resource structure may correspond to the resources in the transmission resource pool. Different resource structures may differ in at least one resource element. For example, resource structures may be arranged and/or grouped in a transmission resource pool based on eg MAC or RRC signaling according to a configuration which may be a higher layer configuration. According to eg NR standardization (if applicable), short response control signaling may generally be associated to a short format, such as short PUCCH or short PSCCH. Long Response Control Signaling can generally be associated to a long format, such as Long PUCCH or Long PSCCH.

If a message and/or information is represented in a (modulated) waveform of the signaling, the signaling may be considered to carry the message and/or information. In particular, the extraction of messages and/or information may require demodulation and/or decoding of signaling. Information may be considered to be contained in a message if the message includes values and/or parameters and/or bit fields and/or indications or indicators representing information, or more than one or a combination thereof. The information contained in such a message may be considered to be carried by the signaling carrying the message, and vice versa. However, signaling characteristics may relate to characteristics that are accessible without demodulation and/or decoding, and/or may be determined or determinable independently of demodulation and/or decoding. However, in some cases, it may be considered to demodulate and/or decode signaling to determine whether characteristics are associated with a particular signaling, such as whether the resource characterizing signaling actually belongs to control signaling and/or to intended In response to radio node or user equipment signaling. Also, in some cases, characteristics may be provided as information in the message, especially if the signaling of the characterization is not carrying a selection control message. In general, the selection of the resource structure may be based on one or more than one signaling characteristic. In particular, a signalling characteristic may represent one or more resources (in particular in the time domain), such as the start and/or end and/or duration of signalling, eg in one/more symbols, and/or in For example, the frequency range or resources of signaling represented by one/more subcarriers, and/or the numerology of signaling, in particular control signaling or data signaling (eg PDSCH signaling or PSSCH signaling). In some cases, the characteristic may indicate the message format, eg, the format of the selection control message, eg, the associated DCI or SCI format. It can generally be considered that the signaling characteristics represent and/or indicate the DCI format and/or search space (eg, receive pool) and/or code (eg, scrambling code) and/or identity, eg, assigned to the responding radio One of the different identities of a node or user equipment (eg R-NTI or C-NTI). Control signaling may be scrambled based on such an identity.

For example for UCI on PUSCH scenario, transmitting acknowledgment information/feedback on resources may include multiplexing acknowledgment information and data/data signaling on transmission resources. In general, transmitting acknowledgment information and/or feedback may include mapping the information to transmission resources and/or one or more modulation symbols, eg, based on a modulation and coding scheme and/or transport format. Acknowledgements can be punched or rate matched. Acknowledgment information related to different subject transmissions and/or acknowledgment signaling procedures may be mapped differently. For example, acknowledgment information related to late subject transmissions and/or having a size less than a threshold size (eg, 3 or 2 bits) may be punctured, while acknowledgment information related to earlier (non-late) subject transmissions may be punctured Acknowledgments on and/or having a size equal to or greater than the threshold size are rate matched.

Acknowledgment feedback, particularly control feedback, may be transmitted generally on resources and/or on channels and/or according to a transport format according to one or more configurations, which may be based, for example, on control information (eg, carrying control One or more indications of information control messages) can be selected.

The methods described herein facilitate providing feedback of control information with limited signaling overhead and are easy to implement for flexible use.

Description of drawings

The figures are provided to illustrate the concepts and methods described herein and are not intended to limit their scope. The accompanying drawings include:

FIG. 1 shows an exemplary diagram of a transmitted message;

Figure 2 shows an exemplary radio node implemented as user equipment; and

Figure 3 shows an exemplary radio node implemented as a network node.

Detailed ways

In the following, for illustrative purposes, the methods are described in the context of NR RATs. However, they are generally applicable to other technologies. Meanwhile, communication in uplink and downlink between a transmitting radio node (transmitting RN) (eg a network node) and a target radio node (target RN) (eg UE) is described by way of example. These methods should not be construed as limited to this type of communication, but are also applicable to sidelink or backhaul or relay communication. For ease of reference, in some cases a channel is referred to to mean signaling or transmission over a channel. PUSCH may represent uplink data signaling, PDSCH may represent downlink data signaling, PDCCH may represent downlink control signaling (in particular one or more DCI messages such as scheduling assignments or grants), and PUCCH may represent uplink Link control signaling, especially UCI signaling. In some cases, the UCI may be transmitted on the PUSCH or associated resources instead of the PUCCH.

Minislot-based or non-slot-based transmissions may be considered. NR supports slot-based transmission, where DL assignments (or scheduling assignments, which are typically included in DCI transmitted on PDCCH) can be received at the beginning of a slot. Scheduled DL transmissions (eg, PDSCH) may also typically start early in the slot.

In addition, NR also supports non-slot-based transmission or mini-slots. Here, a scheduled DL transmission (eg, PDSCH) can in principle start at any symbol, and the transmission duration is flexible and typically (significantly) shorter than the slot duration. The scheduled PDCCH may be at the beginning of the slot, or at the beginning of the actual DL transmission, or in an appropriate CORESET. The latter is especially useful for low-latency transmissions, where the determination that a transmission needs to be scheduled occurs late and slot-based scheduling is no longer possible. Therefore, minislots are particularly useful for the aforementioned low-latency transmissions that may interrupt (preempt) transmissions that are already in progress.

In NR terminology, slot-based transmissions are also referred to as PDSCH scheduling type A, while non-slot-based transmissions (minislots) are denoted PDSCH transmission type B.

Exemplary DL control signaling is discussed in more detail. DL assignments and UL grants may be included in downlink control information (DCI) messages typically sent on the PDCCH. The resources that the UE searches for PDCCH candidates are usually organized in Control Resource Sets (CORESET). Within CORESET, the UE may have configured one or more search spaces. The search space is the arrangement of physical resources within the CORESET that the UE needs to search for PDCCH candidates and included DCIs. Typically, PDCCH candidates and/or DCIs of different sizes are organized in different search spaces. The UE needs to determine whether the detected PDCCH candidates are intended for the UE. For example, this may be done by including the UE identifier (eg, RNTI) into the DCI or scrambling the CRC of the encoded DCI with the UE identity (eg, RNTI). For polar codes that can be used to encode DCI, the UE identity (eg, RNTI) can also be placed on the freeze bit, which is a particularity of polar codes.

The carrier can be divided into bandwidth parts (BWP). The bandwidth portion can have a variety of uses. One of the envisaged usage scenarios is to enable multiple parameter sets mixed in the frequency domain on the same carrier. The BWP configuration may indicate a set of frequency domain resources and an associated set of parameters. One or more BWP parts may be configured for the UE. DL and UL configuration (and/or SL configuration) can be independent of each other. Typically, each BWP has its own associated CORESET for scheduling DCI.

Figure 1 schematically shows a message graph. The transmitting RN may transmit control messages, such as DCI messages. Messages may be transmitted on associated control channels such as PDCCH. The target RN may receive control messages. Based on control messages, it may provide acknowledgement feedback, eg on control channels (eg PUCCH) or data channels (eg PUSCH). Other channels may be used if applicable. If the control message is of the scheduling type, it may eg schedule the data signaling to be received by the target RN, eg on a data channel such as PDSCH. With this scheduling, a second acknowledgement feedback related to data signaling may be scheduled and/or indicated by a message. In addition to the acknowledgment feedback, the target RN may also transmit a second acknowledgment feedback. The feedback may be transmitted at different times (as indicated), eg, at different transmission occasions and/or time slots and/or symbol time intervals, or may be transmitted simultaneously, eg, multiplexed or combined. In particular, the feedback can be combined based on a feedback configuration that can represent a codebook. The acknowledgement feedback can be HARQ or ARQ feedback.

In general, the feedback may be determined based on evaluating error codes incorporated into and/or computed for the information, and/or if the feedback is suitable to indicate the reception status of the information or signaling (eg, acknowledgment or non-acknowledgment). deemed to involve information or signaling.

Figure 2 schematically shows a radio node, in particular a terminal or wireless device 10, which may in particular be implemented as a UE (User Equipment). The radio node 10 includes a processing circuit (which may also be referred to as a control circuit) 20, which may include a controller connected to a memory. Any module of the radio node 10 , eg a communication module or a determination module, in particular as a module in a controller, may be implemented in and/or executable by the processing circuit 20 . The radio node 10 also includes a radio circuit 22 that provides receive and transmit or transceive functionality (eg, one or more transmitters and/or receivers and/or transceivers), the radio circuit 22 being connected or connectable to processing circuitry. The antenna circuit 24 of the radio node 10 is connected or connectable to the radio circuit 22 to collect or transmit and/or amplify the signal. The radio circuit 22 and the processing circuit 20 that controls it are configured for cellular communication and/or side link communication with a network (eg, a RAN as described herein). The radio node 10 may generally be adapted to carry out any method of operating a radio node (eg, a terminal or UE) disclosed herein; in particular, it may include corresponding circuits (eg, processing circuits) and/or modules.

Figure 3 schematically shows a radio node 100, in particular the radio node 100 may be implemented as a network node 100 (eg an eNB, gNB or similar node for NR). The radio node 100 includes a processing circuit (which may also be referred to as a control circuit) 120, which may include a controller connected to a memory. Any module of node 100 , eg, a transmit module and/or a receive module and/or a configuration module, may be implemented in and/or executable by processing circuit 120 . Processing circuitry 120 is connected to control radio circuitry 122 of node 100 that provides receiver and transmitter and/or transceiver functionality (eg, including one or more transmitters and/or receivers and/or transceivers) . Antenna circuit 124 may be connected or connectable to radio circuit 122 for signal reception or transmission and/or amplification. Node 100 may be adapted to carry out any of the methods disclosed herein for operating a radio node or a network node; in particular, it may include corresponding circuitry (eg, processing circuitry) and/or modules. Antenna circuitry 124 may be connected to and/or include an antenna array. Node 100 (respectively, its circuitry) may be adapted to perform any method of operating a network node or radio node described herein; in particular, it may include corresponding circuitry (eg, processing circuitry) and/or modules. The radio node 100 may generally include communication circuitry, eg, to communicate with another network node (eg, a radio node) and/or with a core network and/or the Internet or a local network, in particular with an information system that may provide information to be transmitted to User equipment information and/or data.

References to specific resource structures, such as transmission timing structures and/or symbols and/or timeslots and/or mini-slots and/or sub-carriers and/or carriers, may refer to specific sets of parameters, which may be predetermined Defined and/or configured or configurable. A transmission timing structure may represent a time interval, which may cover one or more symbols. Some examples of transmission timing structures are transmission time intervals (TTIs), subframes, slots, and minislots. A time slot may include a predetermined (eg, predefined and/or configured or configurable) number of symbols, eg, 6 or 7 or 12 or 14. A mini-slot may comprise a smaller number of symbols than the number of symbols of the slot (in particular, it may be configurable or configured), in particular 1, 2, 3 or 4 symbols. The transmission timing structure may cover a time interval of a specific length, which may depend on the symbol time length and/or cyclic prefix used. Transmission timing structures may relate to and/or cover specific time intervals in the time stream, eg, to synchronize for communication. Timing structures (eg, slots and/or minislots) used for and/or scheduled for transmission may be scheduled and/or synchronized in relation to timing structures provided and/or defined by other transmission timing structures. Such transmission timing structures may define a timing grid, eg, where the symbol time interval within each structure represents the smallest timing unit. Such timing grids may, for example, be defined by slots or subframes (where in some cases a subframe may be considered a specific variation of a slot). The transmission timing structure may have a duration (length in time) determined based on the duration of its symbols, possibly in addition to the cyclic prefix/prefixes used. The symbols of the transmission timing structure may have the same duration, or, in some variations, may have different durations. The number of symbols in the transmission timing structure may be predefined and/or configured or configurable, and/or may depend on a parameter set. The timing of minislots may generally be configured or configurable, in particular by the network and/or network nodes. Timing may be configurable to start and/or end at any symbol of the transmission timing structure, particularly at one or more time slots.

A program product is generally considered a package comprising instructions adapted to cause processing and/or control circuitry to perform and/or control any of the methods described herein, particularly when executed on processing and/or control circuitry. Also contemplated is a carrier medium arrangement that carries and/or stores a program product as described herein.

The carrier medium arrangement may comprise one or more carrier mediums. In general, the carrier medium is accessible and/or readable and/or receivable by processing or control circuitry. Storing data and/or program product and/or code may be considered part of carrying the data and/or program product and/or code. Carrier media may generally include boot/transmission media and/or storage media. The guiding/transmission medium may be suitable for carrying and/or carrying and/or storing signals, in particular electromagnetic and/or electrical and/or magnetic and/or optical signals. A carrier medium, in particular a guiding/transmission medium, may be suitable for guiding such signals to carry them. The carrier medium, in particular the guiding/transmission medium, may comprise electromagnetic fields, eg radio waves or microwaves, and/or light-transmitting materials, eg glass fibers and/or cables. The storage medium may include at least one of memory, buffer, cache, optical disk, magnetic memory, flash memory, and the like, which may be volatile or nonvolatile.

A system is described comprising one or more radio nodes, in particular network nodes and user equipment, as described herein. The system may be a wireless communication system, and/or provide and/or represent a radio access network.

Furthermore, a method of operating an information system that includes providing information is generally contemplated. Alternatively or additionally, an information system suitable for providing information may be considered. Providing information may include providing information to and/or to a target system, which may comprise and/or be implemented as a radio access network and/or radio nodes, in particular network nodes or user equipment or terminals. Providing information may include: transmitting and/or streaming and/or sending and/or delivering information, and/or providing information for this and/or for downloading, and/or for example by triggering different systems or nodes to stream and/or transmit and/or sending and/or delivering information to trigger such provision. An information system may include a target, and/or may be connected or connectable to a target, eg, via one or more intermediary systems, eg, a core network and/or the Internet and/or a private or local network. Information may be utilized and/or provided via such one/more intermediary systems. The information is provided for radio transmission and/or for transmission via the air interface and/or with a RAN or radio node as described herein. Connecting the information system to the target and/or providing the information may be based on the target indication and/or may be adapted to the target indication. The target indication may indicate the target and/or one or more parameters of the transmission related to the target and/or the path or connection through which information is provided to the target. Such one/more parameters may relate in particular to the air interface and/or the radio access network and/or the radio node and/or the network node. Example parameters may indicate, for example, the type and/or nature of the target, and/or transmission capacity (eg, data rate), and/or latency, and/or reliability, and/or cost, and/or indicate quality of service and/or Or latency and/or data throughput and/or prioritization, in particular, they may indicate the ability to provide such parameters (respectively, one or more estimates thereof). The target indication may be provided by the target, or determined by an information system, eg, based on information received from the target and/or historical information, and/or by a user (eg, a user operating the target or a device in communication with the target), eg, via the RAN and/or Air interface provided. For example, a user may indicate on a user equipment in communication with the information system that information is to be provided via the RAN by selecting from options provided by the information system, eg, on a user application or user interface (which may be a web interface). An information system may include one or more information nodes. An information node may generally include processing circuitry and/or communication circuitry. In particular, an information system and/or an information node may be implemented as a computer and/or an arrangement of computers, such as a mainframe computer or an arrangement of mainframe computers and/or a server or an arrangement of servers. In some variations, an interactive server (eg, a web server) of the information system may provide a user interface and may trigger the transfer and/or streaming of an information supply from another server to a user (and/or target) based on user input, and another A server may be connected or connectable to an interactive server and/or may be part of or connectable to or connectable to an information system. Information can be any kind of data, especially data intended for the user for use at the terminal, such as video data and/or audio data and/or location data and/or interaction data and/or game-related data and/or environment data and/or technical data and/or business data and/or vehicle data and/or indirect data and/or operational data. As described herein, the information provided by the information system may be and/or may be mapped to and/or is expected to be mapped to communication or data signaling and/or one or more data channels (which may be air interface signaling or one/more channels and/or may be used within the RAN and/or for radio transmission). It may be considered that information is formatted based on target indication and/or target, for example with respect to data volume and/or data rate and/or data structure and/or timing, which may in particular relate to communication or data signalling and/or one or Mapping of multiple data channels. Mapping information to data signaling and/or data channel(s) may be seen as referring to the use of signaling/channel/channels to carry data, signaling/channel/channels, eg at higher layers of communication at the bottom of the transmission. The target indication may generally include different components, which may have different origins, and/or may indicate different characteristics of the target and/or the communication path(s) to the target. In particular, the format of the information may be selected for the information to be transmitted over the air interface and/or by the RAN as described herein, eg from a set of different formats. This may be particularly relevant because the air interface may be limited in capacity and/or predictability, and/or potentially cost-sensitive. The format may be selected to suit the transmission indication, which may specifically indicate the information path between the target and the information system as described herein by the RAN or radio node (which may be indicated and/or planned and/or expected) path). A (communication) path of information may represent one or more interfaces (eg, air and/or cable interfaces) used or to be used to communicate information between a node and/or information system that provides or transmits information and a target and/or or one/more intermediate systems (if any). When providing target indication and/or providing/transmitting information through an information system, the path may be (at least in part) indeterminate, eg if the Internet is involved, the Internet may include a number of dynamically selected paths. The information and/or the format for the information may be packet-based, and/or mapped and/or mappable and/or expected to map to packets. Alternatively or additionally, a method for operating a target device that includes providing a target indication to an information system is also contemplated. More alternatively or additionally, a target device may be considered, the target device being adapted to provide a target indication to an information system. In another approach, a target indication tool may be considered that is adapted to provide target indication to an information system and/or includes an indication module for providing target indication to an information system. The target device may generally be a target as described above. The goal indication tool may include and/or be implemented as software and/or an application or app, and/or a web interface or user interface, and/or may include one or more for implementing actions performed and/or controlled by the tool module. The tool and/or the target device may be adapted to receive user input, and/or the method may comprise receiving user input, and a target indication may be determined and/or provided based on the user input. Alternatively or additionally, the tool and/or target device may be adapted and/or the method may include receiving information and/or communication signaling carrying information, and/or operating on information and/or converting information ( For example, on a screen and/or as audio or as other forms of indication). The information may be based on received information and/or communication signaling carrying the information. Rendering the information may include processing the received information, such as decoding and/or converting, in particular between different formats and/or for hardware used for rendering. Manipulating the information may be independent of presentation or non-presentation, and/or continued or successful presentation, and/or, for example, for automated processes for automotive or transportation or industrial use or target devices without (eg, conventional) user interaction (such as MTC device), there may be no user interaction or even no user reception. Information or communication signaling may be expected and/or received based on the target indication. The presentation and/or manipulation of information may generally include one or more processing steps, in particular decoding and/or executing and/or interpreting and/or transforming the information. Manipulating the information may generally include relaying and/or transmitting the information, eg, over an air interface, which may include mapping the information to signaling (such mapping may generally involve one or more layers, eg, one or more of the air interface) layers, such as the RLC (Radio Link Control) layer and/or the MAC layer and/or one/more physical layers). Information may be imprinted (or mapped) on the communication signaling based on the target indication, which may make it particularly suitable for use in the RAN (eg, for target devices such as network nodes or in particular UEs or terminals). The tool may generally be suitable for use on a target device such as a UE or terminal. In general, the tool may provide a variety of functionality, eg, for providing and/or selecting target indications, and/or presenting eg video and/or audio, and/or manipulating and/or storing received information. Providing the target indication may include transmitting or transmitting the indication in the RAN as signaling, and/or carried on signaling, eg, where the target device is a UE or a tool of the UE. It should be noted that such provided information may be communicated to the information system via one or more additional communication interfaces and/or paths and/or connections. The target indication may be higher layer information, and/or the information provided by the information system may be higher layer information, such as the application layer or the user layer, in particular layers above the radio layer, such as the transport layer and the layer above the physical layer . Target indications may be mapped on physical layer radio signaling, e.g., related to or on the user plane, and/or information may be mapped on physical layer radio signaling, e.g., related to or on the user plane (especially in the reverse communication direction). The described methods allow for the provision of target indications, thereby facilitating the provision of information in a specific format particularly suitable and/or suitable for efficient use of the air interface. For example, the user input may represent a selection from a variety of possible transmission modes or formats and/or paths, eg, in terms of data rate and/or packaging and/or size of information to be provided by the information system.

In general, the parameter set and/or subcarrier spacing may indicate the bandwidth (in the frequency domain) of the subcarriers of the carrier and/or the number of subcarriers in the carrier and/or the numbering of the subcarriers in the carrier. In particular, different parameter sets may differ in the bandwidth of the subcarriers. In some variations, all sub-carriers in a carrier have the same bandwidth associated with them. Parameter sets and/or subcarrier spacing may differ from carrier to carrier, particularly with respect to subcarrier bandwidth. The carrier-related symbol time length and/or the time length of the timing structure may depend on the carrier frequency and/or subcarrier spacing and/or parameter set. In particular, different parameter sets may have different symbol time lengths.

Signaling may generally include one or more symbols and/or signals and/or messages. A signal may comprise or represent one or more bits. The indication may represent signaling, and/or may be implemented as a signal or as multiple signals. One or more signals may be included in or represented by a message. Signaling, especially control signaling, may include multiple signals and/or messages, which may be carried on different carriers and/or may be associated with different signaling procedures, such as representing and/or relating to a or more such procedures and/or corresponding information. The indication may comprise and/or be contained within signaling and/or multiple signals and/or messages that may be transmitted on different carriers and/or may be associated with different acknowledgement signaling procedures , eg, to represent and/or relate to one or more of such processes. Signaling associated with a channel may be transmitted such that the signaling and/or information for the channel is represented and/or the signaling is interpreted by the transmitter and/or receiver as belonging to the channel. Such signaling may generally conform to the transmission parameters and/or format(s) of the channel.

Reference signaling may be signaling that includes one or more reference symbols and/or structures. The reference signaling may be suitable for measuring and/or estimating and/or representing transmission conditions, such as channel conditions and/or transmission path conditions and/or channel (or signal or transmission) quality. It may be considered that the transmission characteristics (eg, signal strength and/or form and/or modulation and/or timing) of reference signaling (eg, as pre-defined and/or configured or configurable and/or being delivered) are important for Both transmitters and receivers of signaling are available. Different types of reference signaling can be considered, for example relating to uplink, downlink or sidelink; being cell-specific (especially cell-wide, eg CRS) or device or user specific (addressing to a specific target or user equipment (eg, CSI-RS), demodulation-related (eg, DMRS), and/or signal strength-related (eg, power-related, energy-related, or amplitude-related signaling (eg, SRS or pilot signaling)) and/or phase dependent, etc.

Uplink or sidelink signaling may be OFDMA (Orthogonal Frequency Division Multiple Access) or SC-FDMA (Single Carrier Frequency Division Multiple Access) signaling. In particular, the downlink signaling may be OFDMA signaling. However, the signaling is not limited to this (filter library based signaling can be considered as an alternative).

A radio node can generally be regarded as a device or node suitable for wireless and/or radio (and/or microwave) frequency communication and/or communication using an air interface, eg, according to a communication standard.

A radio node may be a network node or a user equipment or terminal. A network node may be any radio node of a wireless communication network, eg a base station and/or a gNodeB (gNB) and/or an eNodeB (eNB) and/or a relay node and/or a micro/nano/pico/femto node and/or a transmission Points (TPs) and/or Access Points (APs) and/or other nodes especially for the RAN described herein.

In the context of this disclosure, the terms wireless device, user equipment (UE) and terminal may be considered interchangeable. A wireless device, user equipment or terminal may represent an end device for communicating using a wireless communication network, and/or may be implemented as user equipment according to a standard. Examples of user equipment may include: telephones (eg smart phones), personal communication devices, mobile phones or terminals, computers (especially laptops), radio capable (and/or suitable for an air interface) especially for MTC (Machine-Type Communication, sometimes referred to as M2M Machine-to-Machine) sensors or machines, or vehicles suitable for wireless communication. User equipment or terminals can be mobile or stationary.

A radio node may generally include processing circuitry and/or radio circuitry. In some cases, a radio node, in particular a network node, may comprise cable circuits and/or communication circuits whereby it may be or may be connected to another radio node and/or a core network.

The circuit may include an integrated circuit. The processing circuitry may include one or more processors and/or controllers (eg, microcontrollers) and/or ASICs (application specific integrated circuits) and/or FPGAs (field programmable gate arrays), among others. It may be considered that the processing circuit includes and/or is (operably) connected or connectable to one or more memories or memory arrangements. The memory arrangement may include one or more memories. The memory may be suitable for storing digital information. Examples of memory include: volatile and nonvolatile memory, and/or random access memory (RAM), and/or read only memory (ROM), and/or magnetic and/or optical memory, and/or flash memory Flash memory, and/or hard disk memory, and/or EPROM or EEPROM (erasable programmable ROM or electrically erasable programmable ROM).

A radio circuit may include one or more transmitters and/or receivers and/or transceivers (transceivers may or may be operable as transmitters and receivers, and/or may be included, for example, in a package or housing for receiving and transmitted combined or separate circuits), and/or may include one or more amplifiers and/or oscillators and/or filters, and/or may include and/or be connected or connectable to an antenna circuit and/or one or Multiple antennas and/or antenna arrays. An antenna array may include one or more antennas, which may be arranged in a dimensional array (eg, a 2D or 3D array) and/or an antenna panel. A Remote Radio Head (RRH) can be seen as an example of an antenna array. However, in some variations, the RRH may also be implemented as a network node, depending on the kind of circuitry and/or functionality implemented therein.

Communication circuits may include radio circuits and/or cable circuits. The communication circuit may generally include one or more interfaces, which may be one/more air interfaces and/or one/more cable interfaces and/or one/more optical interfaces (eg, laser-based interfaces) ). In particular, one/more interfaces may be packet based. The cable circuit and/or cable interface may include and/or be connected or connectable to one or more cables (eg, fiber optic and/or wire-based cables) that may be directly or indirectly (eg, via One or more intermediate systems and/or interfaces) are connected or connectable to the target, eg, controlled by communications circuitry and/or processing circuitry.

Any or all of the modules disclosed herein may be implemented in software and/or firmware and/or hardware. Different modules may be associated with different components of the radio node, eg, different circuits or different parts of circuits. It is contemplated that the modules are distributed over different components and/or circuits. A program product as described herein may include modules related to an apparatus (eg, a user equipment or a network node) on which the program product is intended to be executed (execution may be performed on an associated circuit and/or by an associated circuit control).

The radio access network may be a wireless communication network and/or a radio access network (RAN) in particular according to a communication standard. In particular, the communication standard may be a standard according to 3GPP and/or 5G, eg a standard according to NR or LTE, in particular LTE Evolution.

A wireless communication network may be and/or may include a radio access network (RAN), which may be and/or may include any kind of cellular and/or wireless radio network that may be connected or connectable to a core network. The methods described herein are particularly suitable for 5G networks, such as LTE evolution and/or NR (New Radio), and their successors accordingly. A RAN may include one or more network nodes, and/or one or more terminals, and/or one or more radio nodes. In particular, a network node may be a radio node suitable for radio and/or wireless and/or cellular communication with one or more terminals. A terminal may be any device suitable for radio and/or wireless and/or cellular communication with or within the RAN, such as user equipment (UE) or mobile phone or smartphone or computing device or vehicular communication device or for machine type Communication (MTC) devices, etc. Terminals may be mobile, or in some cases stationary. A RAN or wireless communication network may comprise at least one network node and a UE or at least two radio nodes. Generally a wireless communication network or system, eg a RAN or a RAN system, can be considered including at least one radio node and/or at least one network node and at least one terminal.

Transmission in the downlink may involve transmission from a network or a network node to a terminal. Transmission in the uplink may involve transmission from a terminal to a network or network node. Transmission in the side link may involve (direct) transmission from one terminal to another. Uplink, downlink, and sidelinks (eg, sidelink transmission and reception) can be considered communication directions. In some variations, uplink and downlink may also be used to describe wireless communications between network nodes, eg for wireless backhaul and/or relay communications and/or between eg base stations or similar network nodes (wireless ) network communications, especially communications terminated here. It is contemplated that backhaul and/or relay communications and/or network communications are implemented as sidelink or uplink communications or the like.

Control information or control information messages or corresponding signaling may be conveyed on a control channel (eg, a physical control channel), which may be a downlink channel (or in some cases, such as where one UE schedules another UE down the sidelink channel). For example, the control information/allocation information may be signaled by the network node on PDCCH (Physical Downlink Control Channel) and/or PDSCH (Physical Downlink Shared Channel) and/or HARQ specific channels. Acknowledgment signaling may be transmitted by the terminal on PUCCH (Physical Uplink Control Channel) and/or PUSCH (Physical Uplink Shared Channel) and/or HARQ specific channels, for example as control information or signaling (such as uplink control information/signaling) form. Multiple channels are available for multi-component/multi-carrier indication or signaling.

Signaling can generally be viewed as a representation (eg, over time intervals and frequency intervals) of electromagnetic wave structures intended to convey information to at least one specific or general target (eg, anyone who might pick up the signaling). The process of signaling may include transmitting signaling. Transmitting signaling, particularly control signaling or communication signaling (eg, including or representing acknowledgement signaling and/or resource request information) may include coding and/or modulation. Coding and/or modulation may include error detection coding and/or forward error correction coding and/or scrambling. Receiving control signaling may include corresponding decoding and/or demodulation. Error detection coding may include and/or may be based on parity or checksum methods, such as CRC (Cyclic Redundancy Check). Forward error correction coding may include and/or may be based on eg turbo coding and/or Reed-Muller coding and/or polar coding and/or LDPC (Low Density Parity Check) coding. The type of encoding used may be based on the channel (eg, physical channel) associated with the encoded signal. The code rate may represent the ratio of the number of bits of information before encoding to the number of bits of encoding after encoding, taking into account that encoding increases the number of encoded bits for error detection encoding and forward error correction. Encoded bits may refer to information bits (also known as systematic bits) plus encoded bits.

Communication signaling may include and/or be represented and/or implemented as data signaling and/or user plane signaling. The communication signaling may be linked to a data channel, such as a physical downlink channel or a physical uplink channel or a physical sidelink channel, in particular PDSCH (Physical Downlink Shared Channel) or PSSCH (Physical Sidelink Shared Channel). In general, the data channel can be a shared channel or a dedicated channel. Data signaling may be signaling associated to and/or on a data channel.

An indication may generally indicate explicitly and/or implicitly the information it represents and/or indicates. Implicit indications may be based, for example, on the location and/or resources used for transmission. The explicit indication may be based, for example, on parameterization of one or more parameters and/or one or more indices and/or one or more bit patterns representing information. In particular, it is contemplated that the control signaling based on the sequence of utilized resources described herein implicitly indicates the type of control signaling.

A resource element may generally describe the smallest individually usable and/or coded and/or decodable and/or modulated and/or demodulated time-frequency resource, and/or may describe a temporally covering symbol time length and Time-frequency resources that cover subcarriers in frequency. Signals may be assignable and/or assigned to resource elements. A sub-carrier may be a sub-band of a carrier, eg defined by a standard. A carrier may define a frequency and/or frequency band used for transmission and/or reception. In some variations, the signal (joint coding/modulation) may cover more than one resource element. The resource elements may generally be defined by the corresponding standard (eg, NR or LTE). Since the symbol time length and/or subcarrier spacing (and/or parameter set) may vary between different symbols and/or subcarriers, different resource elements may have different spreads in the time and/or frequency domains (length/width), especially involving resource elements of different carriers.

Resources may generally represent time-frequency and/or code resources over which signaling may be communicated (eg, transmitted and/or received), eg, according to a particular format, and/or on which signaling may be expected to be transmitted and/or or receive.

A resource pool may indicate and/or include resources in general, particularly time-frequency resources, such as time and frequency intervals (which may be continuous or interrupted) and/or code resources. In particular, a resource pool may indicate and/or include resource elements and/or resource blocks, eg, PRBs. If a radio node, such as a user equipment, receives corresponding control signaling configured for it, it may be deemed to be configured with a resource pool. In particular, such control signaling may be transmitted by a receiving radio node as described herein. In particular, the control signaling may be higher layer signaling, such as MAC and/or RRC signaling, and/or may be semi-static or semi-persistent. In some cases, a responding radio node or user equipment may be considered to be configured with a resource pool if it is informed, for example, of the corresponding configuration that it can access resources in the resource pool for transmission. In some cases, such configurations may be predefined, eg, based on standard and/or default configurations. The resource pool may be dedicated to one responding radio node or user equipment, or in some cases may be shared among several responding radio nodes or user equipment. It is contemplated that the resource pool may be generic, or used for specific types of signaling, such as control signaling or data signaling. In particular, the transmission resource pool may be used for control signaling, eg uplink control signaling and/or sidelink control signaling, and/or may be dedicated to user equipment/responding radio nodes. It is contemplated that a resource pool comprises a plurality of resource structures, which may eg be arranged in sub-pools or groups in relation to or/or according to the type of signaling (received or scheduled) or the type of response control signaling. Each group or subpool may include a number of resource structures, where the number may be represented by an indicator and/or bit field of the selection control information. For example, the maximum number of resource structures in a group may correspond to the maximum number of distinct values that can be represented by a bit field or indicator. Different groups can have different numbers of resource structures. It is generally contemplated that a group includes a smaller number of resource structures than can be represented by an indicator or bit field. A resource pool may represent a search space and/or availability space of resources and/or resource structures that may be used for a particular signaling. In particular, a transmission resource pool can be viewed as representing a (time/frequency and/or code) domain or space of resources available to respond to control signaling.

The signaling characteristics may represent resources and/or resource structures in the receive resource pool, which may be different from the transmit resource pool. In particular, the resources and/or resource structures, and/or the corresponding pools representing the signalling characteristics characterizing signalling, in particular downlink (or sidelink) control signalling, may comprise one or more CORESET (Control Resource set), where each CORESET can represent a group or subpool. A CORESET may be associated to a specific time interval, eg one or more symbols, in particular in a transmission timing structure such as a slot. It is contemplated that the first CORESET is configured for the first 1, 2 or 3 symbols in the slot. A second CORESET may be configured for one or more subsequent symbols (eg, the 5th and/or 6th symbols) of the same slot. In this case, in particular, the second CORESET may correspond to mini-slot related signaling, eg including association to short (eg, 1 or 2 symbols) response control signaling, and/or short delay requirements (eg, 1 or 2 symbols), and/or a transmission received or scheduled in a minislot and/or a resource structure in response to a minislot (eg, minislot data signaling). The first CORESET may be associated with slot-based signaling, such as long data signaling (eg, more than 2, 3, or 4 symbols), and/or with relaxed latency requirements (eg, more than 1 or 2 symbols) , and/or response control signaling that allows transmission in subsequent transmission timing structures (eg, subsequent slots or subframes), and/or long response control signals (eg, more than 2 or 3 or 4 symbols). In general, different CORESETs may be separated in the time domain by at least 1 symbol, in particular 1, 2, 3 or 4 symbols. Depending on which groups or sub-pools (especially CORESET) the characterization signaling is received, it may be associated to a specific sub-pool or group of the transport resource pool. The receiving resource pool may be pre-defined and/or may eg be configured by the receiving radio node to the responding radio node, alternatively or additionally, the receiving radio node may configure the transmission resource pool. Pool configuration may generally be pre-defined, or performed by the network or network node (eg, receiving radio node) or another responding radio node that assumes corresponding functionality and/or eg in side-link communication Also operates as a receiving radio node, (wherein configuration can be performed by another UE or a network/network node).

A boundary symbol may generally represent a start or end symbol for transmission and/or reception. In particular, the start symbol may be the start symbol of uplink or sidelink signaling (eg, control signaling or data signaling). Such signaling may be on a data channel or a control channel, such as a physical channel, in particular a physical uplink shared channel (such as PUSCH) or a sidelink data or shared channel, or a physical uplink control channel (such as PUCCH) or side link control channel. If the start symbol is associated with control signaling (eg, on a control channel), the control signaling may be responsive to received signaling (in sidelink or downlink) representing, for example, acknowledgement signaling associated with it , the confirmation signaling can be HARQ or ARQ signaling. The end symbol may represent the end symbol (in time) of downlink or sidelink transmission or signaling expected or scheduled to a radio node or user equipment. In particular, such downlink signaling may be, for example, data signaling on a physical downlink channel like a shared channel (eg PDSCH (Physical Downlink Shared Channel)). Start symbols may be determined based on and/or relative to such end symbols.

Configuring a radio node, in particular a terminal or user equipment, may refer to being adapted or caused or to set and/or command the radio node to operate according to the configuration. Configuration may be done by another device or network, such as a network node (eg, a radio node of the network, such as a base station or eNodeB), where configuration is done by the network, it may include transmitting configuration data to the device to be configured. radio node. Such configuration data may represent the configuration to be configured and/or include one or more instructions relating to the configuration, eg, the configuration for transmitting and/or receiving on allocated resources, particularly frequency resources. The radio node may configure itself eg based on configuration data received from the network or network nodes. A network node may be configured with and/or adapted to utilize its circuit/circuitry. Allocation information can be thought of as a form of configuration data. Configuration data may include and/or be represented by configuration information and/or one or more corresponding indications and/or one/more messages.

In general, configuring may include determining configuration data representing the configuration and providing (eg, transmitting) it (in parallel and/or serially) to one or more other nodes, which may further forward it to the radio node (or another node, this may be repeated until it reaches the wireless device). Alternatively or additionally, configuring a radio node, eg, by a network node or other means, may include, eg, receiving configuration data and/or data related to the configuration data from another node, such as a network node, which may be a network and/or transmit the received configuration data to the radio node. Thus, determining the configuration and transmitting the configuration data to the radio node may be performed by different network nodes or entities capable of communicating via a suitable interface, eg an X2 interface in the case of LTE, or a corresponding interface. Configuring the terminal may include scheduling downlink and/or uplink transmissions for the terminal, such as downlink data and/or downlink control signaling and/or DCI and/or uplink control or data or communication signaling , especially acknowledgment signaling; and/or configure resources and/or resource pools for this purpose.

If a resource structure shares a common boundary frequency with another resource structure, eg one is an upper frequency boundary and the other is a lower frequency boundary, the resource structure may be considered adjacent to another resource structure in the frequency domain. For example, such a boundary may be represented by the upper end of the bandwidth assigned to subcarrier n, which also represents the lower end of the bandwidth assigned to subcarrier n+1. A resource structure can be considered at time if it shares a common boundary time with another resource structure, for example one is the upper (or right in the figure) boundary and the other is the lower (or left in the figure) boundary The domain is adjacent to another resource structure. For example, such a boundary may be represented by the end of the symbol time interval assigned to symbol n, which also represents the beginning of the symbol time interval assigned to symbol n+1.

In general, a resource structure being adjacent to another resource structure in a domain may also be referred to as adjoining and/or bordering another resource structure in the domain.

The resource structure may generally represent the structure in the time domain and/or the frequency domain, in particular time intervals and frequency intervals. The resource structure may include and/or consist of resource elements, and/or the time interval of the resource structure may include and/or consist of one/more symbol time intervals, and/or the time interval of the resource structure may A frequency interval may include and/or consist of one/more subcarriers. Resource elements may be considered as examples of resource structures, and time slots or mini-slots or physical resource blocks (PRBs) or parts thereof may be considered other examples. A resource structure may be associated to a specific channel, such as PUSCH or PUCCH, especially a resource structure that is smaller than a slot or a PRB.

Examples of resource structures in the frequency domain include bandwidths or frequency bands or portions of bandwidths. The bandwidth portion may be the portion of the bandwidth available for the radio node to communicate due to eg circuitry and/or configuration and/or regulations and/or standards. The bandwidth portion may be configurable or configurable for the radio node. In some variations, the bandwidth portion may be the bandwidth portion used for communication (eg, transmission and/or reception) by the radio node. The bandwidth portion may be smaller than the bandwidth (which may be the device bandwidth defined by the circuit/configuration of the device and/or the system bandwidth available for the RAN, for example). It is contemplated that the bandwidth portion comprises one or more resource blocks or groups of resource blocks, in particular one or more PRBs or groups of PRBs. The bandwidth portion may involve and/or include one or more carriers. A resource pool or area or set may generally include one or more (in particular, two or more than two multiples of two) resources or resource structures. A resource or resource structure may include one or more resource elements (in particular, two or more resource elements that are a multiple of two) or one or more PRBs or PRB groups (in particular, two or more than two resource elements) multiples of two PRBs or PRB groups), which may be consecutive in frequency.

A carrier may generally represent a frequency range or frequency band, and/or refer to a center frequency and associated frequency spacing. It can be considered that the carrier includes multiple sub-carriers. A carrier may have a center frequency or center frequency spacing assigned to it, eg, represented by one or more sub-carriers (typically, each sub-carrier may be assigned a bandwidth or spacing). The different carriers may not overlap, and/or may be adjacent in the frequency domain.

It should be noted that the term "radio" in this disclosure may be considered to refer to wireless communications in general, and may also include wireless communications using microwave and/or millimeter and/or other frequencies, particularly at 100 MHz or 1 GHz and 100 GHz or wireless communication between 20 or 10 GHz. Such communications may use one or more carriers.

A radio node, in particular a network node or terminal in general may be any device suitable for transmitting and/or receiving radio and/or wireless signals and/or data, in particular communication data, in particular on at least one carrier. The at least one carrier may include a carrier accessed based on an LBT procedure (which may be referred to as an LBT carrier), such as an unlicensed carrier. It can be considered that the carrier is part of carrier aggregation.

Receiving or transmitting on a cell or carrier may refer to receiving or transmitting using a frequency (frequency band) or spectrum associated with the cell or carrier. A cell may generally comprise and/or be defined by or for one or more carriers, in particular, at least one carrier for UL communication/transmission (referred to as UL carrier) and at least one carrier for DL communication/transmission (referred to as UL carrier). is the DL carrier). It is contemplated that a cell includes different numbers of UL carriers and DL carriers. Alternatively or additionally, eg in a TDD based approach, a cell may comprise at least one carrier for UL communication/transmission and DL communication/transmission.

Channels can generally be logical, transport or physical channels. A channel may comprise one or more carriers, in particular multiple sub-carriers, and/or may be arranged on one or more carriers, in particular multiple sub-carriers. A channel that carries and/or is used to carry control signaling/control information may be considered a control channel, especially if it is a physical layer channel and/or if it carries control plane information. Similarly, a channel carrying and/or used to carry data signaling/user information may be considered a data channel, especially if it is a physical layer channel and/or if it carries user plane information. A channel can be defined for a specific communication direction, or for two complementary communication directions (eg, UL and DL, or sidelink in both directions), in which case it can be considered to have two components Channels, one in each direction. Examples of channels include channels for low-latency and/or high-reliability transmission, particularly channels for ultra-reliable low-latency communications (URLLC), which may be used for control and/or data.

In general, a symbol may represent and/or be associated with a symbol time length, which may depend on a carrier and/or subcarrier spacing and/or a parameter set of an associated carrier. Therefore, a symbol can be regarded as a time interval with a symbol time length relative to the frequency domain indication. The symbol time length may depend on the carrier frequency and/or bandwidth and/or parameter set and/or subcarrier spacing of the symbol or associated to the symbol. Therefore, different symbols may have different symbol time lengths. In particular, parameter sets with different subcarrier spacings may have different symbol time lengths. In general, the symbol time length may be based on and/or include a guard time interval or cyclic extension (eg, prefix or suffix).

A sidelink may generally represent a communication channel (or channel structure) between two UEs and/or terminals, wherein the participants (UEs and and/or terminals). Sidelinks may be established only via and/or directly via one/more air interfaces of the participants, which may be directly linked via sidelink communication channels. In some variations, sidelink communications may be performed without network node interaction, eg, on fixed defined resources and/or on resources negotiated between participants. Alternatively or additionally, it may be considered that the network node provides some control functionality, eg by configuring resources, in particular one or more resource pools, for sidelink communication and/or monitoring sidelinks for eg charging purposes.

Sidelink communication may also be referred to as device-to-device (D2D) communication, and/or in some cases, such as in the context of LTE, as ProSe (proximity service) communication. Sidelinks may be implemented in the context of V2x communications (vehicle communications), eg, V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), and/or V2P (vehicle-to-person). Any apparatus suitable for side-link communication may be regarded as user equipment or terminal.

The sidelink communication channel (or structure) may include one or more (eg, physical or logical) channels, such as PSCCH (Physical Sidelink Control Channel, which may eg carry control information such as an acknowledgment location indication) and/or PSSCH (Physical side link shared channel, which may carry data and/or acknowledgment signaling, for example). It is contemplated that the side link communication channel (or structure) involves and/or uses one or more carriers and/or one/more carriers associated with and/or used by cellular communications, eg, in accordance with certain licenses and/or standards. frequency range. Participants may share (physical) channels and/or resources, especially resources in the frequency domain and/or resources related to frequency resources (eg carriers) of side links, such that two or more participants in their transmit on, for example, simultaneously and/or time-shifted, and/or there may be specific channels and/or resources associated with specific participants, such that, for example, only one participant is on a specific channel or on one or more specific resources (eg, on resources in the frequency domain and/or resources related to one or more carriers or sub-carriers).

The sidelink may follow and/or be implemented according to a specific standard, such as an LTE-based standard and/or NR. The side link may utilize TDD (Time Division Duplex) and/or FDD (Frequency Division Duplex) techniques, eg configured by the network node, and/or pre-configured and/or negotiated between the participants. If the user equipment and/or its radio circuits and/or processing circuits are suitable for utilizing sidechains, eg on one or more frequency ranges and/or carriers and/or in one or more formats (in particular according to specific standards) The user equipment can be regarded as suitable for side link communication. It can generally be considered that the radio access network is defined by two participants in side-link communication. Alternatively or additionally, a radio access network may be represented by a network node, and/or a radio access network may be defined by a network node, and/or a radio access network may be associated with a network node and/or communications with such nodes .

Communicating or communicating may generally include transmitting and/or receiving signaling. Communication on the sidelink (or sidelink signaling) may include utilizing the sidelink for communication (respectively, for signaling). Sidelink transmissions and/or transmissions on the sidelinks may be considered to include transmissions utilizing the sidelinks, eg, utilizing associated resources and/or transport formats and/or circuits and/or air interfaces. Sidelink receiving and/or receiving on the sidelink may be considered to include receiving with the sidelink (eg, associated resources and/or transport format and/or circuitry and/or air interface). Sidelink control information (eg, SCI) can generally be considered to include control information conveyed using the sidelink.

In general, carrier aggregation (CA) may refer to a wireless and/or cellular communication network and/or a sidelink comprising multiple carriers between a network node and a terminal or for at least one transmission direction (eg, DL and/or UL) The concept of radio connections and/or communication links over the Internet and the aggregation of carriers. The corresponding communication link may be referred to as a carrier aggregated communication link or a CA communication link; a carrier in a carrier aggregation may be referred to as a component carrier (CC). In such a link, data may be transmitted over more than one carrier and/or all carriers of a carrier aggregation (aggregation of carriers). Carrier aggregation may include one (or more) dedicated control carrier(s) and/or primary carriers (which may be referred to as primary component carriers or PCCs, for example) on which control information may be transmitted, where control information may relate to the primary carrier and other carriers , other carriers may be referred to as secondary carriers (or secondary component carriers SCC). However, in some approaches, control information may be sent over more than one carrier aggregated (eg, one or more PCCs, and one PCC and one or more SCCs).

A transmission may generally involve a specific channel and/or a specific resource, in particular having a start symbol and an end symbol in time to cover the gap in between. A scheduled transmission may be a scheduled and/or expected transmission and/or a transmission for which resources are scheduled or provided or reserved. However, not every scheduled transmission has to be implemented. For example, scheduled downlink transmissions may not be received, or scheduled uplink transmissions may not be transmitted, due to power constraints or other effects (eg, occupied channels on unlicensed carriers). Transmissions may be scheduled for transmission timing substructures within a transmission timing structure like slots (eg, mini-slots and/or covering only a portion of the transmission timing structure). A boundary symbol may indicate a symbol in the transmission timing structure at which a transmission begins or ends.

In the context of the present disclosure, predefined may refer to a correlation that is defined, for example, in a standard and/or that is available (eg, stored in memory) without (eg, configuration-independent) specific configuration from the network or network node. information. Configured or configurable may be considered to refer to corresponding information set/configured by eg a network or network node.

Configuration or scheduling (eg mini-slot configuration and/or structural configuration) may schedule transmissions, e.g. for time/transmission it is valid, and/or may be available through separate signaling or separate configuration (e.g. separate RRC signaling and/or downlink control information signaling) to schedule transmissions. Depending on which side of the communication the device is on, the scheduled transmission/transmissions may represent signaling to be transmitted by the device for which it is scheduled or signaling to be received by the device for which it is scheduled. It should be noted that downlink control information or in particular DCI signaling can be regarded as physical layer signaling compared to higher layer signaling such as MAC (Medium Access Control) signaling or RRC layer signaling. The higher the layer of signaling, the less frequently/time/resources it can be considered to be consumed, at least in part because: the information contained in such signaling must be passed through several layers, each Layers need to be processed and disposed of.

Scheduled transmissions and/or transmission timing structures like mini-slots or time-slots may relate to specific channels, in particular Physical Uplink Shared Channels, Physical Uplink Control Channels or Physical Downlink Shared Channels such as PUSCH, PUCCH or PDSCH, and/or may relate to a specific cell and/or carrier aggregation. Corresponding configurations (eg, scheduling configurations or symbol configurations) may relate to such channel, cell, and/or carrier aggregation. It is contemplated that a scheduled transmission represents a transmission on a physical channel, in particular a shared physical channel, such as a physical uplink shared channel or a physical downlink shared channel. For such channels, a semi-persistent configuration may be particularly suitable.

In general, a configuration may be a configuration that indicates timing, and/or may be represented or configured with corresponding configuration data. The configuration may be embedded and/or included in a message or configuration or corresponding data, whereby resources may in particular be indicated and/or scheduled semi-persistently and/or semi-statically.

The control region of the transmission timing structure may be planned, scheduled or reserved for control signaling (particularly downlink control signaling) and/or for specific control channels (eg physical downlink control channels like PDCCH) interval in time. The interval may comprise and/or consist of multiple symbols in time, which may for example be (UE-specific) dedicated signaling (which may be unicast, eg addressed or intended to a particular UE, eg on the PDCCH) ) or RRC signaling or configurable or configurable on a multicast or broadcast channel. In general, the transmission timing structure may include a control region covering a configurable number of symbols. It can be considered that, in general, the boundary symbols are configured to follow the control region in time.

The duration of the symbols of the transmission timing structure (symbol time length or interval) may generally depend on a parameter set and/or carrier, which may be configurable. A parameter set may be a parameter set to be used for scheduling transmissions.

Scheduling a device or for a device and/or related transmissions or signaling may be considered to include configuring resources for a device or a form of configuring resources and/or an indication to a device, eg, for communication. In particular, scheduling may relate to a transmission timing structure or a substructure thereof (eg, timeslots or minislots, which may be considered as substructures of timeslots). It is contemplated that even for scheduled substructures, eg, if the underlying timing grid is defined based on the transmission timing structure, boundary symbols may still be identified and/or determined for the transmission timing structure. Signaling indicating scheduling may include corresponding scheduling information, and/or may be viewed as representing or containing configuration data indicating scheduling transmissions and/or including scheduling information. Such configuration data or signaling can be regarded as resource configuration or scheduling configuration. It should be noted that in some cases such configuration (especially as a single message) may not be complete, it has no other configuration data, eg is not configured with other signaling, eg higher layer signaling. In particular, in addition to scheduling/resource configuration, symbol configuration may be provided to identify exactly which symbols are assigned to scheduled transmissions. A scheduling (or resource) configuration may indicate one or more transmission timing structures and/or an amount of resources (eg, in number of symbols or length of time) used to schedule transmissions.

A scheduled transmission may be, for example, a transmission scheduled by the network or a network node. In this context, transmissions may be uplink (UL) or downlink (DL) or sidelink (SL) transmissions. Accordingly, an apparatus (eg, user equipment) for which a scheduled transmission is scheduled may be scheduled to receive (eg, in DL or SL) or transmit (eg, in UL or SL) the scheduled transmission. In particular, scheduling a transmission may be considered to include configuring the scheduled device(s) with one or more resources for the transmission and/or informing the device that the transmission is expected and/or scheduled for some resources. Transmissions may be scheduled to cover a certain time interval, in particular a plurality of consecutive symbols, which may form a temporally consecutive interval between (and including) the start symbol and the end symbol. The start and end symbols of a (eg, scheduled) transmission may be in the same transmission timing structure, eg, in the same time slot. However, in some cases the end symbol may be in a later transmission timing structure than the start symbol, especially in temporally subsequent structures. For scheduled transmissions, the duration may be associated and/or indicated, eg, over a certain number of symbols or associated time intervals. In some variations, different transmissions may be scheduled in the same transmission timing structure. Scheduled transmissions can be viewed as being associated with a specific channel, eg a shared channel like PUSCH or PDSCH.

In the context of the present disclosure, a distinction can be made between dynamically scheduled or aperiodic transmission and/or configuration and semi-static or semi-persistent or periodic transmission and/or configuration. The term "dynamic" or similar terms may generally relate to a (relatively) short time scale and/or (eg, predefined and/or configured and/or limited and/or unambiguous) a certain number of events and/or transmission timing Structure (eg, one or more transmission timing structures like a slot or slot aggregation), and/or valid and/or scheduled and/or configured for one or more (eg, a specific number of) transmissions/events configuration/transmission. The dynamic configuration may be based on lower level signaling, such as control signaling on the physical layer and/or the MAC layer, in particular in the form of DCI or SCI. Periodic/semi-static may involve longer timescales (eg, several slots and/or more than one frame) and/or an undefined number of events, eg, until a dynamic configuration contradicts, or until a new periodic configuration arrival. The periodic or semi-static configuration may be based on and/or configured with higher layer signaling, in particular RCL layer signaling and/or RRC signaling and/or MAC signaling.

A transmission timing structure may include multiple symbols, and/or define an interval including several symbols (respectively, their associated time intervals). Unless it is clear from the context that the frequency domain component must also be considered, in the context of this disclosure it should be noted that, for ease of reference, a reference to a symbol may be interpreted as referring to a time domain projection or a time interval or a time component or duration or length in time. Examples of transmission timing structures include slots, subframes, minislots (which in turn can be viewed as a substructure of slots), slot aggregations (which can include multiple slots and can be viewed as a superstructure of slots) , and correspondingly, their time domain components. A transmission timing structure may generally include a number of symbols that define a time domain extension (eg, interval or length or duration) of the transmission timing structure and are arranged adjacent to each other in a numbered sequence. A timing structure, which may also be considered or implemented as a synchronization structure, may be defined by a series of such transmission timing structures, which may eg define a timing grid with symbols representing a minimal grid structure. Transmission timing structures and/or boundary symbols or scheduled transmissions may be determined or scheduled for such timing grids. The received transmission timing structure may be, for example, a transmission timing structure with respect to a timing grid in which scheduling control signaling is received. In particular, the transmission timing structure may be a slot or a subframe, or in some cases, a mini-slot.

Feedback signaling can be regarded as a form of control signaling, such as uplink or sidelink control signaling, such as UCI (Uplink Control Information) signaling or SCI (Sidelink Control Information) signaling. In particular, feedback signaling may include and/or represent acknowledgment signaling and/or acknowledgment information and/or measurement reports.

Acknowledgment information may include an indication of a particular value or state of the acknowledgment signaling process, such as ACK or NACK or DTX. For example, such indications may represent bits or bit values or bit patterns or information switching. Different levels of acknowledgment information providing eg differentiated information on reception quality and/or error location in the received data element/s may be considered and/or represented by control signaling. Acknowledgment information may generally indicate acknowledgment or non-acknowledgement or non-reception or different levels thereof, eg ACK or NACK or DTX. Acknowledgment information may involve an acknowledgment signaling process. The acknowledgment signaling may include acknowledgment information related to one or more acknowledgment signaling processes, in particular one or more HARQ or ARQ processes. It is contemplated that, for each acknowledgment signaling process to which the acknowledgment information belongs, a specific number of bits of the information size of the control signaling is assigned. Measurement report signaling may include measurement information.

Signaling may generally include one or more symbols and/or signals and/or messages. The signal may include and/or represent one or more bits, which may be made into a common modulated signal. The indication may represent signaling, and/or be implemented as a signal or signals. One or more signals may be included in and/or represented by a message. Signaling, especially control signaling, may include multiple signals and/or messages, which may be carried on different carriers and/or be associated with different acknowledgement signaling procedures, such as representing and/or involving one or more such process. An indication may include and/or be included in signaling and/or multiple signals and/or messages, which may be transmitted on different carriers and/or associated with different acknowledgement signaling procedures, such as Represents and/or involves one or more of such processes.

The signaling utilizing, and/or on, and/or associated to, a resource or resource structure may be signaling overlying the resource or structure, signaling on an associated frequency/frequency and/or signaling in the associated time interval/intervals. It is contemplated that the signaling resource structure includes and/or encompasses one or more substructures that may be associated with one or more different channels and/or signaling types, and/or include one or more holes (not one or more resource elements that schedule transmission or reception for transmission). Resource substructures (eg, feedback resource structures) may generally be contiguous within associated intervals in time and/or frequency. It is contemplated that the substructure, in particular the feedback resource structure, represents a rectangle in time/frequency space filled with one or more resource elements. However, in some cases, a resource structure or substructure, particularly a frequency resource range, may represent a non-contiguous pattern of resources in one or more domains (eg, time and/or frequency). The resource elements of the substructure may be scheduled for associated signaling.

In general, it should be noted that the number of bits or bit rate that may be carried on a resource element associated with a particular signaling may be based on a modulation and coding scheme (MCS). Thus, a bit or bit rate can be seen as a form of resource representing a resource structure or range in frequency and/or time, eg according to the MCS. For example, the MCS may be configured or configurable through control signaling, such as DCI or MAC (Medium Access Control) or RRC (Radio Resource Control) signaling.

Different formats of control information can be considered, eg different formats of control channels like the Physical Uplink Control Channel (PUCCH). The PUCCH may carry control information or corresponding control signaling, such as uplink control information (UCI). UCI may include feedback signaling and/or acknowledgement signaling (like HARQ feedback (ACK/NACK)) and/or measurement information signaling, eg including channel quality information (CQI) and/or scheduling request (SR) signaling. One PUCCH format supported may be short, and may occur, for example, at the end of a slot interval, and/or multiplexed and/or adjacent to the PUSCH. Similar control information may be provided on the sidelink, in particular on a (physical) sidelink control channel like (P)SCCH, eg as sidelink control information (SCI).

A code block can be viewed as a data element or a sub-element or sub-structure of a data block (eg, a transport block), eg, a transport block may include one or more code blocks.

Control signaling, such as downlink control signaling or sidelink control signaling, may be configured for scheduling assignments. Such control signaling may be considered to represent and/or include scheduling signaling, which may indicate scheduling information. Scheduling assignments may be regarded as scheduling information indicating the scheduling/transmission of signaling, in particular signaling received or to be received by a device configured with scheduling assignments. It is contemplated that a scheduling assignment may indicate data (eg, data blocks or elements and/or channels and/or data streams) and/or (associated) acknowledgment signaling processes and/or on which data will be received (or in some reference signaling in the case of), and/or resource/resources indicating the associated feedback signaling, and/or a range of feedback resources on which the associated feedback signaling will be transmitted. Transmissions associated with the acknowledgment signaling process, and/or associated resources or resource structures, may be configured and/or scheduled, eg, by scheduling assignments. Different scheduling assignments may be associated with different acknowledgement signaling procedures. For example, a scheduling assignment may be considered an example of downlink control information or signaling if transmitted by the network node and/or provided on the downlink (or if the sidelink is used and/or transmitted by the user equipment). as side link control information).

Scheduling grants (eg, uplink grants) may represent control signaling (eg, downlink control information/signaling). It is contemplated that scheduling grants configure signaling resource ranges and/or resources for uplink (or sidelink) signaling, particularly uplink control signaling and/or feedback signaling (eg, acknowledgment signaling). Configuring the signaling resource range and/or resource may include configuring or scheduling it for transmission by the configured radio node. Scheduling grants may indicate channels and/or possible channels to be/available for feedback signaling, in particular whether shared channels such as PUSCH may/will be used. A scheduling grant may generally indicate the format of one or more uplink resources and/or uplink channels and/or control information related to the associated scheduling assignment. The grant and the assignment/assignments may be considered (downlink or sidelink) control information, and/or may be associated with, and/or transmitted with, different messages.

The resource structure in the frequency domain, which may be referred to as frequency spacing and/or range, may be represented by subcarrier groupings. A subcarrier grouping may include one or more subcarriers, where each subcarrier may represent a particular frequency interval and/or bandwidth. The bandwidth of the subcarriers (ie, the length of the interval in the frequency domain) may be determined by the subcarrier spacing and/or parameter set. The sub-carriers may be arranged such that each sub-carrier is adjacent in frequency space (for group sizes greater than 1) to at least one other sub-carrier of the group. The grouped sub-carriers may be associated to the same carrier, eg configurable or configured or predefined. Physical resource blocks can be viewed as representing groupings (in the frequency domain). A subcarrier grouping may be considered to be associated with a particular channel or signaling if the transmission of a particular channel or signaling is scheduled and/or transmitted and/or planned and/or configured for at least one, or more, or all subcarriers in the subcarrier grouping or this type of signaling. Such associations may be time-dependent, eg, configured or configurable or predefined, and/or dynamic or semi-static. The associations may be different for different devices, eg, configured or configurable or predefined, and/or dynamic or semi-static. Patterns of subcarrier groupings may be considered, which may include one or more subcarrier groupings (which may be associated with the same or different signaling/channels), and/or (eg, from the perspective of a particular device) have no associated One or more groups of signaling. An example of a pattern is a comb, for which, between pairs of groups associated to the same signaling/channel, there are arranged one or more groupings associated to one or more different channels and/or signaling types, and/or One or more groupings that do not have an associated channel/signaling.

Example types of signaling include: signaling for specific communication directions, especially uplink signaling, downlink signaling, sidelink signaling; and reference signaling (such as SRS or CRS or CSI-RS), communication Signaling, control signaling, and/or signaling associated with a particular channel (eg, PUSCH, PDSCH, PUCCH, PDCCH, PSCCH, PSSCH, etc.).

The operational conditions may relate to the load of the RAN, the application or use case of the transmission or signaling, and/or the quality of service (QoS) conditions (or requirements) of the transmission or signaling. For example, QoS may relate to data rate and/or priority and/or delay and/or transmission quality, such as BLER or BER. The use of URLLC can be regarded as a condition related to quality of service.

In this disclosure, for purposes of explanation and not limitation, specific details are set forth, such as specific network functions, procedures, and signaling steps, in order to provide a thorough understanding of the techniques presented herein. It will be apparent to those skilled in the art that the concepts and aspects of the present invention may be practiced in other modifications and variations from these specific details.

For example, these concepts and variants are partly described in the context of Long Term Evolution (LTE) or LTE-Advanced (LTE-A) or New Radio mobile or wireless communication technologies; ) additional or alternative mobile communication technologies using the inventive concepts and aspects. While the described variants may relate to certain technical specifications (TS) of the 3rd Generation Partnership Project (3GPP), it will be appreciated that the present methods, concepts and aspects may also be implemented in conjunction with different performance management (PM) specifications.

Furthermore, those skilled in the art will appreciate that the services, functions and steps explained herein may be implemented using software operating in conjunction with a programmed microprocessor, or using application specific integrated circuits (ASICs), digital signal processors (DSPs), field programmable Gate Array (FPGA) or general purpose computer. It will also be appreciated that although the variants described herein are set forth in the context of methods and apparatus, the concepts and aspects presented herein can also be embodied in program products and systems including control circuits, such as computer processors and couplings to the memory of the processor, wherein the memory is encoded with one or more programs or program products that perform the services, functions, and steps disclosed herein.

It is believed that the advantages of the aspects and variations presented herein will be fully appreciated from the foregoing description, and will be appreciated without departing from the scope of the concepts and aspects described herein, or without sacrificing all of its advantageous effects , various changes may be made in the form, construction and arrangement of its exemplary aspects. The aspects presented herein can be varied in a number of ways.

Some useful abbreviations include:

<u>Abbreviation</u> <u>Explain</u> ACK/NACK Ack/Negative Ack ARQ Automatically retransmit requests CAZAC constant amplitude zero autocorrelation CGB code block group CDM code division multiplexing CM cubic measure CORESET control channel resource set CQI channel quality information CRC Cyclic Redundancy Check CRS common reference signal CSI channel state information CSI-RS Channel State Information Reference Signal DAI downlink assignment indicator DCI downlink control information DFT discrete Fourier transform DM(-)RS Demodulation reference signal (signaling) FDM frequency division multiplexing HARQ Hybrid automatic retransmission request IFFT Inverse Fast Fourier Transform MBB mobile broadband MCS Modulation and Coding Schemes MIMO Multiple Input Multiple Output MRC Maximum ratio combined MRT maximum ratio transfer MU-MIMO Multiple User Multiple Input Multiple Output OFDM/A Orthogonal Frequency Division Multiplexing/Multiple Access PAPR Peak-to-average power ratio PDCCH physical downlink control channel PDSCH physical downlink shared channel PARCH physical random access channel PRB physical resource block PUCCH physical uplink control channel PUSCH physical uplink shared channel (P)SCCH (Physical) Sidelink Control Channel (P)SSCH (Physical) Sidelink Shared Channel QoS service quality RB resource block RNTI Radio Network Temporary Identifier RRC radio resource control SC-FDM/A Single carrier frequency division multiplexing/multiple access SCI side link control information SINR signal to interference plus noise ratio SIR letter to dry ratio SNR signal to noise ratio SR scheduling request SRS Sounding Reference Signal (Signaling) SVD singular value decomposition TDM time division multiplexing UCI uplink control information UE User equipment URLLC Ultra-low-latency high-reliability communication VL-MIMO very mostly input multiple output ZF forcing to zero

Abbreviations are deemed to follow 3GPP usage, if applicable.

Claims (15)

1. A method of operating a target radio node (10, 100) in a radio access network, the method comprising: receiving control information transmitted on the control channel; and Confirmation feedback related to the control information is transmitted. 2. A target radio node (10, 100) of a radio access network, the target radio node (10, 100) being adapted to receive control information transmitted on a control channel and also adapted to transmit in relation to said control information confirmation feedback. 3. A method of operating a transmitting radio node (10, 100) in a radio access network, the method comprising retransmitting control information to a target radio node (10, 100) based on acknowledgement feedback related to the control information. 4. A transmitting radio node (10, 100) of a radio access network, the transmitting radio node (10, 100) being adapted to retransmit all information to a target radio node (10, 100) based on acknowledgement feedback related to control information the control information. 5. The method or apparatus of one of the preceding claims, wherein the control information comprises command-type control information. 6. The method or apparatus of one of the preceding claims, wherein the control information comprises scheduling-type control information, such as control information and/or control information indicating resources and/or transmission parameters for receiving signaling Control information for resources and/or transmission parameters used to transmit signaling such as data signaling. 7. The method or apparatus of one of the preceding claims, wherein the control information comprises a response resource indication indicating the resources used to transmit the acknowledgement feedback. 8. The method or apparatus of one of the preceding claims, wherein the control information comprises a second response resource indication indicating a second resource for transmitting a second acknowledgement feedback, the second acknowledgement feedback being associated with the first acknowledgment feedback. The second information is related to the reception by the target radio node. 9. The method or apparatus of one of the preceding claims, wherein transmitting the acknowledgement feedback is based on determining whether the control information has been received correctly, eg based on error coding and/or quality of reception. 10. The method or apparatus of one of the preceding claims, wherein the control information is transmitted in a control information message, in particular on a control channel, such as a dedicated or shared channel. 11. The method or apparatus of one of the preceding claims, wherein the control information comprises a position indication indicating the position of the acknowledgment feedback relative to a second acknowledgment feedback and/or in a feedback codebook. 12. The method or apparatus of one of the preceding claims, wherein the acknowledgement feedback is transmitted on a control channel, eg a dedicated or shared control channel. 13. The method or apparatus of one of the preceding claims, wherein the acknowledgement feedback is transmitted on a data channel, eg a dedicated or shared data channel. 14. A program product comprising instructions adapted to cause a processing circuit to control and/or perform a method according to one of claims 1, 3 or 5 to 13. 15. A carrier medium arrangement carrying and/or storing a program product according to claim 14.

Images