Acknowledgement signaling process for a radio access network - Patents.com

Abstract

Fifth generation wireless communication technologies are being developed with the goal of serving a wide variety of use cases. One area of ​​particular importance for many applications concerns signaling reliability. [Solution] A method for operating a target wireless node in a radio access network includes receiving a control message transmitted on a physical downlink control channel (PDCCH) and transmitting acknowledgement feedback regarding the control information.

Description

[Technical field]

[0001] The present disclosure relates to wireless or communications technologies, and in particular to radio access technologies, for example for mobile communications. [Background technology]

[0002] Currently, the fifth generation of wireless communication technologies is being developed with the goal of serving a wide variety of use cases, therefore the systems involved must be extremely flexible and new kinds of signaling and information may need to be transmitted.

[0003] One area that is of particular importance to many applications concerns signaling reliability. Summary of the Invention

[0004] The objective of the present disclosure is to present a technique that allows improved reliability of signaling by applying an acknowledgement signaling procedure for controlling signaling. The technique is particularly advantageously implemented in a fifth generation (5G) communication network or 5G radio access technology or radio access network (RAT / RAN), in particular according to 3GPP (3rd Generation Partnership Project, standardization body). A suitable RAN may in particular be a RAN according to NR, e.g. Release 15 or later, or LTE evolution. It is noted that in the following, the terms data (sub) structure and data block (sub) structure may be considered to be used synonymously.

[0005] Accordingly, a method of operating a target wireless node in a radio access network is disclosed, the method including receiving control information transmitted on a control channel and transmitting acknowledgement feedback regarding the control information.

[0006] A target wireless node for a wireless access network is also disclosed. The target wireless node is adapted to receive control information transmitted on a control channel. Moreover, the target wireless node is adapted to transmit acknowledgement feedback regarding the control information. The target wireless node may be adapted to comprise and / or utilize processing circuitry and / or radio circuitry, in particular a transmitter and / or a receiver and / or a transceiver, for example for receiving the control information and / or for transmitting the acknowledgement feedback.

[0007] For example, a wireless node that is targeted or may be targeted with the transmission of control information and / or data signaling may be considered a target wireless node. The target wireless node may be, in particular, a user equipment or a terminal. However, in some scenarios, for example, in backhaul or relay signaling, the target wireless node may be a network node.

[0008] Further described is a method of operating a transmitting wireless node in a radio access network, the method including retransmitting, to a target wireless node, the control information based on acknowledgement feedback regarding the control information. Alternatively or additionally, the method may include transmitting, to the target wireless node, a control message including the control information and error coding information for error coding the control information.

[0009] A transmitting radio node for a radio access network may be considered. The transmitting radio node is adapted to retransmit, to a target radio node, control information based on acknowledgement feedback regarding the control information. Alternatively or additionally, the transmitting radio node may be adapted to transmit, to the target radio node, a control message including the control information and error coding information for error coding the control information. The transmitting radio node may be adapted to comprise and / or utilize processing circuitry and / or radio circuitry, in particular a transmitter and / or a receiver and / or a transceiver, e.g. for receiving the acknowledgement feedback and / or for transmitting and / or retransmitting the control information and / or the control message and / or for error coding the control information.

[0010] In the approaches described herein, control information is subjected to an acknowledgment signaling procedure directly related to the control information, allowing improved reliability for the control information, especially for control information that does not schedule a data transmission, e.g., for reception or transmission.

[0011] In general, acknowledgement feedback related to control information may also be referred to as control acknowledgement feedback or control feedback.

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

[0013] Performing the retransmission may be based on the received acknowledgement feedback and / or may include receiving the acknowledgement feedback, e.g., on the indicated and / or configured resources and / or channels and / or according to the indicated and / or configured codebook. The codebook may be dynamically configured, e.g., utilizing multiple control messages, such as scheduling type messages or allocation and / or command type messages. Performing the retransmission may include transmitting the control information again, e.g., according to the feedback, if the control information was not correctly received. Such a retransmission may use a different transmission format or transmission mode and / or MCS and / or error coding than the previous transmission. The number of transmissions of a particular control information may be counted, and in some cases may be limited in number by a threshold, which may be predefined and / or configured or configurable. If the threshold is reached, the retransmission may be stopped. Performing the retransmission may be considered to include transmitting new control information and / or omitting a retransmission of the control information if correct reception is indicated by the feedback.

[0014] The control information may generally be transmitted in a control message, e.g., on a physical layer or channel, e.g., as a DCI or SCI message. The control message may be a command type message that may include and / or consist of command type information, or a scheduling type message, e.g., scheduling data signaling, that may include scheduling information.

[0015] The control information may include scheduling type control information (or, for short, scheduling type information), e.g., control information indicating resources and / or transmission parameters for reception of signaling and / or control information indicating resources and / or transmission parameters for transmission of signaling. The signaling may in particular be data signaling, e.g., on a data channel.

[0016] The control information may in particular include or consist of command type control information and / or be included in a command type message. In general, control information or control messages, e.g. DCI or SCI messages, may be distinguished between scheduling type information / messages and command type information / messages. Scheduling type messages may schedule transmissions (data signaling), e.g. on a data channel for reception or transmission for the target wireless node, e.g. in the downlink or uplink, respectively. Scheduling grants and scheduling allocations are examples of such scheduling type messages. Since data channel transmissions for reception usually go through an acknowledgement signaling procedure, the transmitting wireless node may infer, at least to a limited extent, the receipt of a scheduling allocation from the acknowledgement signaling associated with the transmission scheduled for reception. For data channel transmissions transmitted by the target wireless node, the transmission itself allows some inference regarding the receipt of a scheduling grant. Command type messages may be a different type of message, e.g. not scheduling a transmission on a data channel. A command type message may include a set of instructions, which may be configurable or flexible. Those instructions may be scheduling independent. The command type information may, for example, indicate and / or command a switch of bandwidth, for example to another bandwidth portion, and / or an activation or deactivation of a carrier and / or a cell and / or a bandwidth portion, and / or an activation or deactivation of a grant-free transmission, and / or an indication of a selection of a parameter or setting among a set of configured parameters or settings. In some variations, the command type message may be scheduling independent such that it does not schedule data signaling, or the command type message may have a structure in which such scheduling may be configurable or optional.For command type, there may be no scheduled transmission and the reception of control information may be inferred based on the scheduled transmission. Therefore, those techniques are particularly applicable to this case. However, the handling of scheduling type messages may also be advantageously improved, especially with respect to reliability, with the techniques described herein, since direct and unambiguous feedback may be provided. Note that scheduling type messages may contain command type information.

[0017] Scheduling of transmission or reception of data signaling may be referred to as scheduling of the corresponding data channel. The data channel may be a shared or dedicated channel. Examples of data channels are PDSCH in the downlink, PUSCH in the uplink, and PSSCH in the sidelink. In particular, a dedicated data channel for low latency and / or reliable transmission may be considered, for example, for URLLC.

[0018] Transmitting the acknowledgement feedback may generally include and / or be based on determining feedback information, e.g., one or more feedback or ACK / NACK bits. Such determination may include, for example, performing error decoding based on error coding bits, e.g., CRC and / or FEC bits associated with the control information, which may be included in a control message carrying the control information. Error decoding may include, for example, correcting the control information based on the FEC bits. The error coding bits may be determined based on the control information, e.g., utilizing an error coding scheme such as CRC and / or polar coding or LDPC coding or Reed-Muller coding. The control information may be represented by bits. The control information and, in some cases, error coding bits associated with the control information, such as 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 sub-structures, for each of which, for example, one or more feedback bits to indicate an ACK or NACK may be included in the acknowledgement feedback. Thus, at least one bit may be provided for the entirety of the control information and / or control message, and / or one bit may be provided for one or more substructures of the control information and / or control message, to which corresponding error coding may be associated and / or provided, e.g., in the control message. A control message may be considered similar to a transport block and / or a code block group. An acknowledgement process identifier, such as a HARQ identifier or an ARQ identifier, may be associated with the control information and / or control message. A bit subpattern representing reception (e.g., ACK / NACK or DTX / DRX) may generally be associated with the control information in the acknowledgement feedback.

[0019] Alternatively or additionally, transmitting the acknowledgement feedback may include and / or be based on selecting resources for transmission of the acknowledgement feedback. The resources may be, in particular, time and / or frequency and / or code resources, which in some variants may be selected or selectable from one or more resources, or one or more resource regions, or one or more pools of resources. Such resources or one or more regions or one or more pools may be configured in the target wireless node.

[0020] Generally, the acknowledgement feedback may be transmitted on resources scheduled and / or indicated by the control messages, in particular the control messages carrying the control information. Those resources may be time and / or frequency and / or code resources.

[0021] In general, the resources, especially for feedback for command type messages, may be considered to be selected from a pool of resources that may be configured for the target radio node based on higher layer signaling, such as MAC or RRC signaling. The resources may be associated with a particular channel and / or specifically with acknowledgement feedback for control information. In some cases, the resources may be configured globally for use by the target radio node. The resources may be in the same transmission timing structure as the received control information or in a later structure, e.g., in the next structure for which the resources are available, and / or in the same transmission timing structure as indicated by the control message carrying the configuration and / or control information. The transmission timing structure may be, in particular, a slot. In some cases, the resources may be associated with non-slot-based transmissions. The resources may be considered to be resources for data signaling, e.g., PUSCH ("UCI on PUSCH"). The acknowledgement feedback may be rate-matched or punctured on such resources.

[0022] In some variants, the control information includes a response resource indication indicating resources and / or transmission parameters for the transmission of the acknowledgement feedback. The indication may indicate, for example, a channel such as a control channel, e.g., PUCCH, which may be a short PUCCH or a long PUCCH and / or non-slot-based or slot-based, respectively. Alternatively or additionally, the indication may indicate a resource, a resource set or a resource region or a pool of resources, or one or more sets or regions or pools from which the resources may be selected for the transmission. The indication may indicate resources for data signaling, e.g., PUSCH resources. In this case, the resources may be implicitly indicated by a control message carrying the control information, and may optionally be set with another message, e.g., a scheduling grant or higher layer signaling. Indicating the resources may be expressed by indicating a transmission timing structure, such as a slot or minislot or subframe, in which the feedback must be transmitted, e.g., a structure of reception, or, in case of N>0, a structure after (e.g., the most recent N or equal to N). Selecting resources may include selecting resources from available (eg, configured) resources for transmission in the indicated transmission timing structure.

[0023] In some variations, the control information includes a second response resource indication indicating a second resource for transmission of the second acknowledgement feedback, the second acknowledgement feedback may relate to second information and / or signaling, such as data signaling, that is indicated for reception by the target wireless node. The second response resource indication may be in addition to or instead of the response resource indication described herein. The second information may be transmitted on a data channel and / or scheduled for transmission on a data channel and / or represented or carried by data signaling, among others. The second information may be indicated and / or configured and / or scheduled for reception by the control information and / or a control message carrying the control information, e.g., a scheduling allocation. Alternatively or additionally, the second information may be configured or scheduled by another message, e.g., a second control message. The second resource may be configured or configurable in the target wireless node, e.g., via higher layer signaling, such as MAC or RRC signaling, e.g., by a control message, e.g., with the second response resource indication or with one or more other messages. The resources and / or set and / or region and / or pool may be the same or different as in the acknowledgement feedback.

[0024] Transmitting the acknowledgement feedback may include, for example, transmitting the second acknowledgement feedback on the same or different resources as the acknowledgement feedback. In particular, the second acknowledgement feedback may be combined with the acknowledgement feedback for transmission.

[0025] The acknowledgement feedback and / or the second acknowledgement feedback may be transmitted based on a feedback codebook, e.g., a HARQ codebook, which may indicate which bit or bits of the feedback relate to which transmission and / or information and / or data structure (e.g., a transport block or a code block or a code block group), e.g., to indicate an acknowledgement or a negative acknowledgement or no transmission / no reception.

[0026] The sending of the acknowledgement feedback may be considered to be based on determining whether the control information and / or the second information have been correctly received, for example based on error coding and / or reception quality, which may be based on a determined signal quality, for example.

[0027] The control information may be transmitted in a control information message on a control channel, for example a physical channel, which may in particular be a dedicated or shared channel. The control channel may in particular be a PDCCH or a common control channel, or a PSCCH.

[0028] In some variants, the control information may include a position indication indicating a position of the acknowledgement feedback for 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, e.g., a control message carrying the control information. The position indication may include an indicator such as a downlink allocation indicator (DAI), which may indicate or count the number of data structures (such as transport blocks and / or code blocks and / or code block groups and / or messages and / or control / command messages) for which the acknowledgement feedback, e.g., control feedback and / or other acknowledgement feedback, is scheduled and / or indicated. Different control messages, e.g., scheduling allocations, may include indicators of different values, e.g., 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 an indicator may be referred to as a total DAI. Alternatively or additionally, the position indication and / or indicator may indicate a count of bits scheduled and / or indicated for feedback, or a total number of bits, respectively. The count may refer to a HARQ codebook, e.g., indicate where in the HARQ codebook a bit sub-pattern representing feedback information for a data structure should be located. It may be considered 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, the sub-pattern combination for control information may also refer to data signaling, e.g., data signaling scheduled for reception, which may be scheduled by a control message carrying the control information.In such a case, for example, there may be only one indicator indicating one count, and based on that one indicator, the target wireless node may include sub-patterns in the codebook. The sub-pattern combination may include, for example, a sub-pattern indicating reception of control information and a sub-pattern indicating reception of data signaling, in a predefined or set or configurable order. For example, the sub-pattern combination may include two bits, one bit indicating an ACK / NACK for the control information and the other bit indicating an ACK / NACK for the data signaling. Other orders or different sub-patterns may be considered.

[0029] Information, particularly control information, may be carried in associated messages, which may be carried and / or represented by associated signaling. Information and / or messages and / or signaling may be associated with a particular channel. Thus, information may be considered to be carried by corresponding signaling and messages and / or on associated channels.

[0030] In general, the acknowledgement feedback may be transmitted on a control channel, such as a dedicated or shared control channel, which may be a physical channel. The acknowledgement feedback may be transmitted, for example, on a PUCCH or a PSCCH.

[0031] 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. The acknowledgement feedback may be transmitted, for example, on a PUSCH or a PSSCH.

[0032] Also described are program products comprising instructions adapted to cause processing circuitry to control and / or implement the methods described herein.

[0033] Also contemplated are carrier medium configurations that carry and / or store the program products described herein.

[0034] Acknowledgement feedback or acknowledgement information regarding a transmission and / or regarding information such as control information may generally be information that allows for (at least) an indication of an ACK or NACK for that information, e.g., a message or a data structure or a sub-structure thereof. In some cases, instead of a NACK, no transmission of feedback may be provided, e.g., in a one-bit or one-subpattern codebook that only relates to control information. In this case, a node expecting feedback may consider the non-transmission as a NACK or as an indication that the control message / information was received in error or that the control message / information was not received.

[0035] The acknowledgement feedback may also be referred to as an acknowledgement response (or, for short, simply feedback) and / or may be considered as a form of acknowledgement signaling. These terms may be used interchangeably. The acknowledgement feedback may represent uplink signaling, control information or control signaling, and the acknowledgement feedback or signaling therefor may be downlink signaling. However, variants are envisaged in which both may be sidelink signaling (with different communication directions). The acknowledgement feedback may in particular be HARQ feedback.

[0036] The acknowledgement signaling may generally represent and / or include and / or contain acknowledgement information, which may be structured based on a feedback configuration, e.g., a codebook. The codebook may generally be dynamic, e.g., based on one or more control messages, e.g., DCI information and / or scheduling allocations and / or command type messages. Variations involving configured and / or predefined and / or static codebook or codebooks may be considered.

[0037] The configurations may generally be indicated and / or configured with one or more messages, which may relate to the same or different layers or types, e.g., the physical layer and / or the RLC layer and / or the MAC layer and / or the RRC and / or the DCI. In particular, some of the configurations may be indicated and / or configured semi-statically and / or with RRC and / or MAC signaling, and / or some may be pre-configured or predefined, and / or some may be indicated and / or configured dynamically, e.g., with DCI or SCI signaling.

[0038] The acknowledgement information may represent and / or include one or more bits, in particular a pattern of bits. A number of bits relating to a data sub-structure may be considered as a sub-pattern. The structure of the acknowledgement information may dictate the order and / or meaning and / or mapping and / or pattern of bits (or sub-patterns of bits) of the information. The acknowledgement configuration, in particular the feedback configuration, may dictate the size of the acknowledgement information conveyed by the acknowledgement signaling to which the configuration relates and / or the configuration and / or mapping of the bits of the acknowledgement information. The structure or mapping may dictate in particular the data block structure or structures, e.g. code blocks and / or code block groups and / or transport blocks and / or messages, e.g. command messages, to which the acknowledgement information relates, and / or which bits or sub-patterns of bits relate to which data block structures. In some cases, the mapping may relate to one or more acknowledgement signaling processes, e.g. processes with different identifiers, and / or one or more different data streams. The configuration may dictate which process or processes and / or data stream or streams the information relates to. In general, the acknowledgement information may include one or more sub-patterns, each of which may relate to a data block structure, e.g., a code block or a code block group or a transport block. A sub-pattern may be configured to indicate an acknowledgement or a negative acknowledgement, or another retransmission state, such as non-scheduling or non-reception, of the associated data block structure. A sub-pattern may be considered to include one bit, or in some cases two or more bits. It should be noted that the acknowledgement information is subjected to significant processing before being transmitted using the acknowledgement signaling. Different configurations may indicate different sizes and / or mappings and / or structures and / or patterns.

[0039] The acknowledgement settings, and in particular the feedback settings, may generally indicate the number of bits of acknowledgement information represented by the acknowledgement signaling and / or the size of the acknowledgement information, which may be represented by a number of bits and / or a number of modulation symbols.

[0040] An acknowledgement configuration, in particular a feedback configuration, may be considered as indicating a mapping of one or more acknowledgement bit sub-patterns to one or more data block structures to which they relate, e.g., to one or more code block groups, or to one or more transport blocks, or to a combination thereof. An acknowledgement bit pattern may represent acknowledgement information, and an acknowledgement bit sub-pattern may represent a sub-pattern of a pattern.

[0041] A transmission format generally indicates one or more data block structures or sub-structures for transmission or reception and / or may indicate how a data block, such as a transport block (and / or related structure), is divided into sub-blocks or sub-block groups, such as, for example, one or more code blocks and / or one or more code block groups. A transmission format may in some cases relate to more than one data block and / or relate to more than one acknowledgement signaling process. A transmission format may be considered to indicate the size in bits and / or coding of one or more data block structures or sub-structures. A transmission format may relate to signaling to be transmitted by a wireless node, or to signaling to be received, and / or to acknowledgement signaling for signaling to be received. Different transmission formats may be utilized, e.g., defined and / or configured, for different communication directions and / or different carriers and / or bandwidth portions and / or different sets of carriers and / or bandwidth portions and / or different configurations, in particular different sets of acknowledgement configurations. In particular, a transmission format for a transmission on a transmission resource may differ from a transmission format associated with an acknowledgement configuration, such as a feedback configuration, which may be configured independently of one another, e.g., using different messages and / or different signaling, e.g., on different layers of a protocol stack.

[0042] An acknowledgement configuration, such as a feedback configuration, may generally be a code block group configuration, which may indicate the mapping of one or more acknowledgement information sub-patterns (e.g., one or more bits) to one or more code block groups, each of which may include or consist of the same or different number of code blocks, in particular one or more code blocks. Each sub-pattern may be mapped to one code block group. In some variants, an acknowledgement configuration may indicate the mapping of one or more sub-patterns to one or more transport blocks, each of which may include and / or consist of one or more code block groups. Each sub-pattern may be mapped to one transport block. An acknowledgement configuration may relate to a combination of one or more code block groups and one or more transport blocks, in particular with respect to a structure or transmission format of the corresponding acknowledgement information. An acknowledgement configuration may be considered as setting and / or formatting feedback or acknowledgement information for a code block group or a transport block or a code block.

[0043] The data block structure may correspond to scheduled data blocks, for example, for data signaling. The data blocks may be associated with separately scheduled transmissions, for example separate channels and / or instances and / or carriers and / or component carriers and / or data streams, for example in the context of carrier aggregation and / or multiple antenna transmission, for example MIMO (multiple input multiple output). The data blocks and / or associated data signaling may be for the downlink or, in some cases, for the sidelink. The acknowledgement signaling may generally be uplink signaling, but in some variants may be sidelink signaling. However, cases may be considered where the data signaling is uplink signaling, for example in the context of retransmissions performed by the user equipment. The sub-patterns may represent acknowledgement information and / or feedback for the associated data blocks, for example with a size indicated by the allocation indication. Different data blocks may be associated with different transmission instances and / or different acknowledgement signaling processes, for example HARQ processes. The acknowledgement signaling procedure may include one or more acknowledgement signaling processes, which may relate to the same communication direction.

[0044] A data block structure (or, for short, a data structure) may generally represent and / or relate to a scheduled data block and / or corresponding signaling. A data block may be scheduled for reception, for example, by a control signaling, in particular a control information message, which may be a scheduling allocation. In some cases, a scheduled data block may not be received, which may be reflected in a corresponding acknowledgement signaling. The number of data block structures and / or the number of allocation indications may be considered to represent the number of transmissions of data scheduled to be received by the user equipment (or second radio node).

[0045] The data block structure may generally represent and / or correspond to a data block, which may generally be a block of data and / or bits. The data block may be, for example, a transport block, a code block, or a code block group. The data block structure may be considered to represent a data block that may be intended to be subjected to an acknowledgement signaling process. The data block may include one or more sub-blocks, which may be grouped into one or more sub-block groups, for example, a code block group. The data block may in particular be a transport block, which may include one or more code blocks and / or one or more code block groups. The data block structure may thus be considered to represent a transport block, a code block, or a code block group. A sub-block group, such as a code block group, may include one or more sub-blocks, for example, a code block. The data block may be considered to include one or more sub-block groups, which may have the same or different sizes (e.g., in number of bits, for example, systemic and / or coding bits). A data block may be considered to include information or systematic bits (which may be considered to represent data to be transmitted and / or error detection bits) and / or coding bits, e.g., bits for error coding such as error detection and / or error correction coding in particular, and / or parity or CRC (Cyclic Redundancy Check) bits. A sub-block (e.g., code block) and / or a sub-block group (e.g., code block group) may similarly include systematic and / or coding bits. In some cases, the systematic bits may be considered to include information bits and error detection bits determined based on the information bits. The parity bits may be considered to represent error correction coding bits.It should be noted that for a data structure (such as a transport block) that includes one or more substructures (e.g., CBGs or code blocks), the systematic bits of the substructures, and possibly the parity bits of the substructures, may be considered as information bits, based on which error detection and / or error correction coding may be performed.

[0046] The acknowledgement signaling process may be a HARQ process and / or may be identified by a process identifier, e.g., a HARQ process identifier or sub-identifier. The acknowledgement signaling and / or the associated acknowledgement information may be referred to as feedback. It should be noted that the data block or structure to which the sub-pattern may relate may be intended to carry data (e.g., information and / or systemic and / or coding bits). However, depending on the transmission conditions, such data may or may not be received (or may not be correctly received), which may be indicated correspondingly in the feedback. In some cases, the sub-pattern of the acknowledgement signaling may include padding bits, e.g., if the acknowledgement information for a data block requires fewer bits than indicated as the size of the sub-pattern. Such may happen, e.g., if the size is indicated by a unit size larger than required for the feedback.

[0047] The acknowledgement information may generally indicate at least, for example, an ACK or NACK for an acknowledgement signaling process, or an element of a data block structure, such as a data block, a sub-block group, or a sub-block. In general, one particular sub-pattern and / or data block structure may be associated with an acknowledgement signaling process, and acknowledgement information may be provided for that one particular sub-pattern and / or data block structure.

[0048] The acknowledgement signaling process may determine the correct or incorrect reception and / or corresponding acknowledgement information of a data block, such as a transport block, and / or of a substructure of a data block, based on coding bits associated with the data block and / or based on coding bits associated with one or more data blocks and / or subblocks and / or subblock groups. The acknowledgement information (determined by the acknowledgement signaling process) may relate to the data block as a whole and / or to one or more subblocks or subblock groups. A code block may be considered as an example of a subblock, while a code block group may be considered as an example of a subblock group. Thus, an associated subpattern may include one or more bits indicating a reception status or feedback of the data block and / or one or more bits indicating a reception status or feedback of one or more subblocks or subblock groups. Each subpattern, or bits of that subpattern, may be associated with and / or mapped to a particular data block or subblock or subblock group. In some variants, correct reception for a data block may be indicated if all subblocks or subblock groups are correctly identified. In such cases, the sub-pattern may represent acknowledgement information for the data block as a whole, reducing overhead compared to providing acknowledgement information for sub-blocks or sub-block groups. The smallest structure (e.g., sub-block / sub-block group / data block) for which a sub-pattern provides acknowledgement information and / or to which the sub-pattern relates may be considered the (highest) resolution of that sub-pattern. In some variations, a sub-pattern may provide acknowledgement information for several elements of the data block structure and / or at different resolutions, e.g., to enable more specific error detection.For example, even if a sub-pattern indicates acknowledgement signaling for a data block as a whole, in some variants a higher resolution (e.g., sub-block resolution or sub-block group resolution) may be provided by the sub-pattern. A sub-pattern may include one or more bits to indicate an ACK / NACK for a data block in general and / or one or more bits to indicate an ACK / NACK for a sub-block or sub-block group, or for two or more sub-blocks or sub-block groups.

[0049] The sub-blocks and / or sub-block groups may include information bits (representing data to be transmitted, e.g., user data and / or downlink / sidelink data or uplink data). The data blocks and / or sub-blocks and / or sub-block groups may also include one or more error detection bits, which may be determined with respect to and / or based on the information bits (for a sub-block group, one or more error detection bits may be determined based on the information bits and / or error detection bits and / or error correction bits of one or more sub-blocks of the sub-block group). The data blocks, or sub-structures such as sub-blocks or sub-block groups, may include error correction bits, which may be determined based on the information bits and error detection bits of the data blocks or sub-structures, in particular, by utilizing, for example, an error correction coding scheme, e.g., LDPC or polar coding. In general, the error correction coding (and / or associated bits) of a data block structure may cover and / or relate to the information bits and error detection bits of that structure. The sub-block groups may represent one or more code blocks, respectively, a combination of corresponding bits. A data block may represent a code block or a code block group, or a combination of two or more code block groups. A transport block may be divided into code blocks and / or code block groups, for example, based on the bit size of the information bits of the higher layer data structure provided for error coding, and / or size requirements or preferences for error coding, especially error correction coding. Such higher layer data structures are sometimes also referred to as transport blocks, which in this context represent information bits without error coding bits as described herein, but in Internet protocols such as TCP, higher layer error handling information may be included.However, such error handling information represents information bits in the context of this disclosure, as the described acknowledgement signaling procedures treat the error handling information accordingly.

[0050] In some variants, a sub-block, such as a code block, may include error correction bits, which may be determined based on one or more information bits and / or one or more error detection bits of the sub-block. An error correction coding scheme may be used to determine the error correction bits, for example based on LDPC or polar coding. In some cases, a sub-block or code block may be considered to be defined as a block or pattern of bits including information bits, one or more error detection bits determined based on the information bits, and one or more error correction bits determined based on the information bits and / or the one or more error detection bits. In a sub-block, such as a code block, the information bits (and, in some cases, one or more error correction bits) may be considered to be protected and / or covered by an error correction scheme or one or more corresponding error correction bits. A code block group may include one or more code blocks. In some variants, additional error detection bits and / or additional error correction bits are not applied, but either or both may be considered to be applied. A transport block may include one or more code block groups. Additional error detection bits and / or additional error correction bits may be considered to be not applied to a transport block, but either or both may be considered to be applied. In some particular variants, one or more code block groups may not include additional layers of error detection or error correction coding, and the transport block may include only additional error detection coding bits and no additional error correction coding. This may be true especially when the transport block size is larger than the code block size and / or the maximum size for error correction coding. Acknowledgement signaling sub-patterns (in particular indicating ACK or NACK) may relate to the code block, e.g., indicate whether the code block was received correctly.A sub-pattern may be considered for a sub-group, such as a code block group, or a data block, such as a transport block. In such a case, the sub-pattern may indicate an ACK if all sub-blocks or code blocks of a group, or a data / transport block, are correctly received (e.g., based on a logical AND operation), and a NACK, or another state of non-correct reception, if at least one sub-block or code block is not correctly received. It should be noted that a code block may be considered as correctly received not only if it is actually correctly received, but also if it can be correctly reconstructed based on soft combining and / or error correction coding.

[0051] A sub-pattern may relate to one acknowledgement signaling process, and / or one carrier, such as a component carrier, and / or a data block structure or data block. In particular, one (e.g., a specific and / or single) sub-pattern may be considered to relate to one (e.g., a specific and / or single) acknowledgement signaling process, e.g., a specific and / or single HARQ process, and to be mapped to that process, e.g., by a codebook. In a bit pattern, a sub-pattern may be considered to be one-to-one mapped to an acknowledgement signaling process and / or a data block or data block structure. In some variants, there may be multiple sub-patterns (and / or associated acknowledgement signaling processes) associated with that carrier, e.g., when multiple data streams transmitted on the same component carrier are subject to an acknowledgement signaling process. A sub-pattern may include one or more bits, and the number of those bits may be considered to represent the size or bit size of the sub-pattern. Different bit n-sets (n is 1 or more) of a sub-pattern may relate to different elements of the data block structure (e.g. data blocks or sub-blocks or sub-block groups) and / or represent different resolutions. Variants in which only one resolution is represented by a bit pattern, e.g. a data block, may be considered. Bit n-sets may represent acknowledgement information (also called 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 two or more bits, for example to improve disambiguity of the bit sequence representing ACK or NACK and / or to improve transmission reliability.

[0052] In general, the acknowledgement signaling may be signaling at one instance and / or in one transmission timing structure and / or scheduled for a common transmission, and / or the acknowledgement information may be jointly coded and / or modulated. The acknowledgement information may relate to multiple different transmissions associated with and / or represented by a data block structure, respectively associated data blocks or data signaling. The data block structures and / or corresponding blocks and / or signaling may be scheduled for simultaneous transmission, for example, for the same transmission timing structure, in particular within the same slot or subframe and / or on one or more same symbols. However, alternatives involving scheduling for non-simultaneous transmissions may be considered. For example, the acknowledgement information may relate to data blocks scheduled for different transmission timing structures, for example different slots (or minislots, or slots and minislots) or the like, and the data blocks may be received (or may not be received, or may be received erroneously) correspondingly. Scheduling signaling may generally include indicating resources, eg, time and / or frequency resources, for receiving or transmitting the scheduled signaling.

[0053] A radio node, in particular a configuring radio node, may generally be adapted to schedule data blocks or subject transmissions for transmission and / or provide and / or determine and / or configure associated allocation instructions that may include an aggregate allocation instruction. Configuring the second radio node or UE may include such scheduling and / or associated determining and / or setting and / or providing of allocation instructions.

[0054] The resource structure may represent time and / or frequency and / or code resources. In particular, the resource structure may include a number of resource elements and / or one or more resource blocks / PRBs. To the resource structure may be associated a type of signaling, in particular a control signaling, and / or a signaling format and / or a latency requirement. The latency requirement may in particular specify when a response has to be transmitted after receiving the signaling, with a delay that may allow for example processing. The requirement may specify a delay of one or two symbols between the end of the received signaling and the transmission of a response control signaling, in particular an acknowledgement signaling for the received signaling, for example a data signaling. The resource structure may correspond to resources in a transmission resource pool. Different resource structures may differ in at least one resource element. The resource structure may be configured and / or grouped in the transmission resource pool according to a configuration, which may for example be a higher layer configuration, for example based on MAC or RRC signaling. Short response control signaling may generally be associated with a short format, e.g., a short PUCCH or a short PSCCH, where applicable, e.g., according to NR standardization. Long response control signaling may generally be associated with a long format, e.g., a long PUCCH or a long PSCCH.

[0055] Signaling may be considered to carry a message and / or information if the message and / or information is represented in the (modulated) waveform of the signaling. In particular, extraction of the message and / or information may require demodulation and / or decoding of the 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 instructions or indicators representing the information, or two or more of them or a combination thereof. Information contained in such a message may be considered to be carried by the signaling that carries the message, or vice versa. However, signaling characteristics may relate to characteristics accessible without demodulation and / or decoding and / or may be determined or determinable independently of the accessible characteristics. However, in some cases, signaling may be considered to be demodulated and / or decoded to determine whether a characteristic is relevant to a particular signaling, for example, if the resources characterizing that signaling actually belong to control signaling and / or to signaling intended for a responding wireless node or user equipment. Also, in some cases, the characteristics may be provided as information in the message, especially if the characterization signaling does not carry a selection control message. In general, the selection of the resource structure may be based on one or more signaling characteristics. The signaling characteristics may in particular represent one or more resources, in particular in the time domain, of control or data signaling, such as PDSCH or PSSCH signaling, for example, the start and / or end and / or duration of the signaling, for example represented by one or more symbols, and / or the frequency range or resources of the signaling, for example represented by one or more subcarriers, and / or the numerology of the signaling. In some cases, the characteristics may indicate a message format, for example the format of the selection control message, for example the associated DCI or SCI format.In general, the signaling characteristic may be considered to represent a DCI format and / or a search space (e.g., a reception pool) and / or a code, e.g., a scrambling code, and / or an identity, e.g., one of different identities (such as an R-NTI or a C-NTI), allocated to the responding radio node or user equipment. The control signaling may be scrambled based on such an identity.

[0056] Transmitting acknowledgement information / feedback on resources may include, for example, in a UCI scenario on PUSCH, multiplexing acknowledgement information and data / data signaling on transmission resources. In general, transmitting acknowledgement information and / or feedback may include mapping the information to transmission resources and / or one or more modulation symbols, for example, based on a modulation coding scheme and / or a transmission format. The acknowledgement information may be punctured or rate matched. Acknowledgement information for different subject transmissions and / or different acknowledgement signaling processes may be mapped differently. For example, acknowledgement information for late subject transmissions and / or having a size smaller than a threshold size (e.g., 3 or 2 bits) may be punctured, and acknowledgement information for early (non-late) subject transmissions and / or having a size equal to or larger than the threshold size may be rate matched.

[0057] Acknowledgement feedback, and in particular control feedback, may generally be transmitted on resources and / or on channels and / or according to a transmission format according to one or more settings, which may be selectable, for example, based on one or more indications in the control information, e.g., a control message carrying the control information.

[0058] The approaches described herein enable the provision of feedback for control information with limited signaling overhead and may be easily implemented for flexible use.

[0059] The drawings are provided to illustrate the concepts and techniques described herein, but are not intended to limit their scope. [Brief description of the drawings]

[0060] [Figure 1] FIG. 2 is an exemplary diagram of a message being sent. [Diagram 2] FIG. 1 illustrates an exemplary wireless node implemented as user equipment. [Diagram 3] FIG. 2 illustrates an exemplary wireless node implemented as a network node. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0061] In the following, for illustrative purposes, the techniques are described in the context of the NR RAT. However, the techniques are generally applicable with other technologies. Also, communication in the uplink and downlink between a transmitting radio node (transmitting RN) such as a network node and a target radio node (target RN) such as a UE is described as an example. The techniques should not be construed as being limited to such communication, but may also be applied for sidelink or backhaul or relay communication. For ease of reference, in some cases, a channel is referred to to represent signaling or transmission on the channel. PUSCH may represent uplink data signaling, PDSCH downlink data signaling, PDCCH downlink control signaling (particularly one or more DCI messages such as a scheduling allocation or grant), PUCCH uplink control signaling, and in particular signaling of UCI. In some cases, UCI may be transmitted on the PUSCH or related resources instead of the PUCCH.

[0062] Minislot or non-slot-based transmissions may be considered. NR supports slot-based transmissions, where a DL allocation (or, in general, a scheduling allocation included in a DCI transmitted on a PDCCH) may be received at the beginning of a slot, and a scheduled DL transmission (e.g., a PDSCH) may generally start early in a slot.

[0063] Furthermore, NR also supports non-slot-based transmissions or minislots, where a scheduled DL transmission (e.g., PDSCH) can in principle start at any symbol and the transmission duration is flexible and usually (much) shorter than the slot duration. The scheduling PDCCH can either be located at the beginning of a slot or at the beginning of the actual DL transmission, or in the preferred CORESET. The latter is especially useful for low-latency transmissions, where the decision that a transmission needs to be scheduled occurs late and slot-based scheduling is no longer possible. Minislots are therefore especially useful for the above-mentioned low-latency transmissions that may interrupt (preempt) an already ongoing transmission.

[0064] In NR terminology, slot-based transmission is also denoted as PDSCH scheduling type A, and non-slot-based transmission (minislot) is denoted as PDSCH transmission type B.

[0065] Exemplary DL control signaling is described in more detail. DL allocations and UL grants may be included in a downlink control information (DCI) message, typically sent on the PDCCH. The resources that the UE searches for PDCCH candidates are typically organized in a control resource set (CORESET). Within the CORESET, the UE may be configured with one or more search spaces. A search space is a configuration of physical resources in the CORESET that the UE needs to search for PDCCH candidates and included DCI. Typically, PDCCH candidates and / or DCIs of different sizes are organized in different search spaces. The UE needs to determine whether the detected PDCCH candidate is for the UE. This may be done, for example, by including a UE identifier (e.g., RNTI) in the DCI or by scrambling the CRC of the encoded DCI with the UE identity (e.g., RNTI). In a polar code that may be used to encode the DCI, the UE identifier (e.g., RNTI) may also be placed on the frozen bit, which is a feature of the polar code.

[0066] A carrier may be partitioned into bandwidth parts (BWPs). A bandwidth part may have multiple usages. One of the envisioned usage scenarios is to allow multiple numerologies to be mixed in the frequency domain on the same carrier. A BWP configuration may indicate a set of frequency domain resources and the associated numerology. A UE may be configured with one or multiple BWP parts. DL and UL configurations (and / or SL configurations) may be independent of each other. In general, each BWP has its own associated CORESET for scheduling DCI.

[0067] FIG. 1 shows a schematic message diagram. A transmitting RN may transmit a control message, e.g., a DCI message. The message may be transmitted on an associated control channel, such as a PDCCH. A target RN may receive the control message. Based on the control message, the target RN may provide acknowledgement feedback, e.g., on a control channel, such as a PUCCH, or a data channel, such as a PUSCH. Other channels may be used, if applicable. If the control message is of a scheduling type, the control message may schedule data signaling to be received by the target RN, e.g., on a data channel, such as a PDSCH. In such scheduling, a second acknowledgement feedback for the data signaling may be scheduled and / or indicated by the control message. The target RN may transmit the second acknowledgement feedback in addition to the acknowledgement feedback. The feedbacks may be transmitted at different times (as indicated), e.g., different transmission occasions and / or slots and / or symbol time intervals, or may be transmitted simultaneously, e.g., multiplexed or combined. In particular, the feedbacks may be combined based on a feedback configuration, which may represent a codebook. The acknowledgement feedback may be HARQ or ARQ feedback.

[0068] In general, feedback may be considered to relate to information or signaling if the feedback is determined based on evaluating error coding contained in and / or calculated for the information and / or if the feedback is adapted to indicate the reception status of the information or signaling, e.g., an acknowledgment or a negative acknowledgment.

[0069] 2 illustrates diagrammatically a radio node, particularly a terminal or wireless device 10, which may in particular be implemented as a UE (user equipment). The radio node 10 comprises a processing circuitry 20 (sometimes referred to as control circuitry), which may comprise a controller connected to a memory. Any module of the radio node 10, e.g., a communication module or a decision module, may be implemented in and / or executable by the processing circuitry 20, in particular as a module in the controller. The radio node 10 also comprises a radio circuitry 22 providing receiving and transmitting or transceiving functionality (e.g., one or more transmitters and / or receivers and / or transceivers), which is connected or connectable to the processing circuitry. An antenna circuitry 24 of the radio node 10 is connected or connectable to the radio circuitry 22 for collecting or forwarding and / or amplifying signals. The radio circuitry 22 and the processing circuitry 20, which controls the radio circuitry 22, are configured for cellular communication with a network, e.g., a RAN as described herein, and / or for sidelink communication. The wireless node 10 may generally be adapted to perform any of the methods of operating a wireless node, such as a terminal or UE, disclosed herein, and in particular the wireless node 10 may comprise corresponding circuit elements, e.g., processing circuit elements, and / or modules.

[0070] 3 illustrates in particular a schematic diagram of a radio node 100, which may be implemented as a network node 100, e.g., an eNB or gNB, or the like for NR. The radio node 100 comprises a processing circuit element 120 (sometimes referred to as control circuitry), which may comprise a controller coupled to a memory. Any module of the node 100, e.g., a transmitting module and / or a receiving module and / or a configuration module, may be implemented in and / or executable by the processing circuit element 120. The processing circuit element 120 is connected to control a radio circuit element 122 of the node 100, which provides receiver and transmitter and / or transceiver functionality (e.g., comprising one or more transmitters and / or receivers and / or transceivers). An antenna circuit element 124 may be connected or connectable to the radio circuit element 122 for signal reception or transmission and / or amplification. The node 100 may be adapted to perform any of the methods for operating a radio node or a network node disclosed herein, and in particular the node 100 may comprise corresponding circuit elements, e.g., processing circuit elements, and / or modules. The antenna circuit element 124 may be connected to and / or comprise an antenna array. The node 100, respectively, the circuit elements of the node 100 may be adapted to perform any of the methods for operating a network node or a radio node described herein, and in particular the node 100 may comprise corresponding circuit elements, e.g., processing circuit elements, and / or modules. The radio node 100 may generally comprise communication circuit elements for communication with another network node, such as a radio node, and / or with a core network and / or the Internet or local net, in particular with an information system that may provide information and / or data to be transmitted to user equipment.

[0071] References to a particular resource structure, such as a transmission timing structure and / or a symbol and / or a slot and / or a minislot and / or a subcarrier and / or a carrier, may refer to a particular numerology, which may be predefined and / or configured or configurable. A transmission timing structure may represent a time interval that may cover one or more symbols. Some examples of transmission timing structures are transmission time intervals (TTIs), subframes, slots and minislots. A slot may include a predefined, e.g., predefined and / or configured or configurable number of symbols, e.g., 6 or 7 or 12 or 14. A minislot may include a number of symbols smaller (e.g., configurable or configurable) than the number of symbols of a slot, in particular 1, 2, 3 or 4 symbols. A transmission timing structure may cover a time interval of a particular length, which may depend on the symbol time length and / or cyclic prefix used. A transmission timing structure may refer to and / or cover a particular time interval in a time stream, e.g., synchronized for communication. The timing structures used and / or scheduled for transmission, e.g., slots and / or minislots, may be scheduled with respect to and / or synchronized to timing structures provided and / or defined by other transmit timing structures. Such transmit timing structures may define a timing grid, e.g., by symbol time intervals within the individual structures representing the smallest timing unit. Such a timing grid may be defined, e.g., by slots or subframes (in some cases, a subframe may be considered as a particular variant of a slot). The transmit timing structure may have a duration (length of time) determined based on the duration of the symbols of the transmit timing structure, possibly in addition to one or more cyclic prefixes used. The symbols of the transmit timing structure may have the same duration or, in some variants, different durations.The number of symbols in the transmission timing structure may be predefined and / or set or configurable and / or numerology dependent. The timing of the minislot may be set or configurable in general, in particular by the network and / or network node. The timing may be configurable to start and / or end at any symbol of the transmission timing structure, in particular one or more slots.

[0072] In general, a program product comprising instructions adapted, in particular when executed on processing circuitry and / or control circuitry, to cause the processing circuitry and / or control circuitry to perform and / or control any of the methods described herein is contemplated. Also contemplated is a carrier medium arrangement carrying and / or storing a program product as described herein.

[0073] A carrier medium configuration may comprise one or more carrier media. Generally, a carrier medium may be accessible and / or readable and / or receivable by a processing circuit element or a control circuit element. Storing data and / or program products and / or codes may be seen as part of conveying data and / or program products and / or codes. A carrier medium may generally comprise a guide / transport medium and / or a storage medium. A guide / transport medium may be adapted to convey and / or carry and / or store signals, in particular electromagnetic and / or electrical and / or magnetic and / or optical signals. A carrier medium, in particular a guide / transport medium, may be adapted to guide such signals and convey them. A carrier medium, in particular a guide / transport medium, may comprise an electromagnetic field, e.g. radio waves or microwaves, and / or a light-transmitting material, e.g. glass fiber, and / or a cable. A storage medium may comprise at least one of a memory, which may be volatile or non-volatile, a buffer, a cache, an optical disk, a magnetic memory, a flash memory, etc.

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

[0075] Moreover, generally, a method of operating an information system may be considered, the method including providing information. Alternatively or additionally, an information system adapted to provide information may be considered. Providing information may include providing information for and / or to a target system, the target system may comprise and / or be implemented as a radio access network and / or a radio node, in particular a network node or a user equipment or a terminal. Providing information may include forwarding information and / or streaming information and / or sending information and / or passing information, and / or providing information for such and / or for download, and / or triggering such providing, for example by triggering a different system or node to stream information and / or forward information and / or send information and / or pass information. The information system may comprise the target and / or be connected or connectable to the target, for example via one or more intermediate systems, for example a core network and / or the Internet and / or a private or local network. The information may be provided using and / or through such one or more intermediate systems. Providing the information may be for wireless transmission and / or for transmission over an air interface and / or using a RAN or wireless node as described herein. Connecting the information system to the target and / or providing the information may be based on and / or adapted to a target indication. The target indication may indicate the target and / or indicate one or more parameters of a transmission relating to the target and / or a path or connection over which the information is provided to the target.Such one or 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. Exemplary parameters may, for example, indicate the type and / or nature and / or transmission capacity (e.g., data rate) and / or latency and / or reliability and / or cost of the target, and / or indicate the quality of service and / or latency and / or data throughput and / or prioritization, in particular, exemplary parameters may indicate the capability to provide the above, respectively, one or more estimates thereof. The target indication may be provided by the target or determined by the information system, for example based on information received from the target and / or historical information, and / or provided by a user, for example a user operating the target or a device communicating with the target, for example via the RAN and / or the air interface. For example, the user may indicate that information should be provided via the RAN by selecting from selections provided by the information system, for example on a user application or user interface, which may be, for example, a web interface, on user equipment communicating with the information system. The information system may comprise one or more information nodes. An information node may generally comprise processing circuitry and / or communication circuitry. In particular, an information system and / or an information node may be implemented as a computer and / or computer configuration, e.g., a host computer or host computer configuration, and / or a server or server configuration. In some variations, an interaction server (e.g., a web server) of the information system may provide a user interface and may trigger, based on user input, the sending and / or streaming of information offerings to users (and / or targets) from another server, which may be connected or connectable to the interaction server and / or be part of the information system or connected or connectable to the information system.The information may be any kind of data, in particular data intended for a user to use in a terminal, for example video data and / or audio data and / or location data and / or interactive data and / or game-related data and / or environmental data and / or technical data and / or traffic data and / or vehicle data and / or situational data and / or operational data. The information provided by the information system may be mapped and / or mappable and / or intended for mapping to a communication or data signaling and / or one or more data channels described herein (which may be signaling or one or more channels of the air interface and / or used within the RAN and / or for wireless transmission). The information may be formatted based on a target indication and / or target, for example with respect to data amount and / or data rate and / or data structure and / or timing, which may in particular be considered as being intended for mapping to a communication or data signaling and / or one or more data channels. Mapping information to data signaling and / or one or more data channels may be considered to refer to using the signaling / channel(s) to carry data by the signaling / channel(s) underlying the transmission, e.g., on a higher layer of communication. The target indication may generally include different components, which may have different sources, and / or different components may indicate different characteristics of the target and / or one or more communication paths to the target. The format of the information may be specifically selected, e.g., from a set of different formats, for information to be transmitted over the air interface and / or by the RAN described herein. This may be particularly appropriate since the air interface may be limited in terms of capacity and / or predictability, and / or potentially cost sensitive.The format may be selected to accommodate the transmission instruction, which may in particular indicate that a RAN or wireless node as described herein is on the path (which may be the indicated and / or planned and / or expected path) of information between the target and the information system. The (communication) path of information may represent one or more interfaces (e.g., air and / or cable interfaces) and / or one or more intermediate systems (if any) through which the information passes or should pass between the information system and / or the node providing or forwarding the information and the target. The path may be (at least partially) undetermined when the target instruction is provided, and / or the information is provided / forwarded by the information system, which may comprise multiple dynamically selected paths, for example when the Internet is involved. The information and / or the format used for the information may be packet-based and / or may be mapped to packets and / or may be mappable to packets and / or may be subject to mapping to packets. Alternatively or additionally, a method for operating a target device may be considered, which includes providing a target indicating to an information system. As a further alternative or addition, a target device may be considered, the target device adapted to provide target instructions to the information system. In another approach, a target instruction tool adapted to provide target instructions to the information system and / or comprising an instruction module for providing target instructions to the information system may be considered. The target device may generally be a target as described above. The target instruction tool may comprise and / or be implemented as software and / or an application or app and / or a web interface or user interface and / or may comprise one or more modules for implementing actions performed and / or controlled by the tool.The tool and / or the target device may be adapted to receive a user input, and / or the method may include receiving a user input, and based on the user input, target instructions may be determined and / or provided. Alternatively or additionally, the tool and / or the target device may be adapted to receive information and / or communication signaling carrying the information, and / or act on the information, and / or present the information (e.g., on a screen and / or as audio or other form of instructions), and / or the method may include receiving information and / or communication signaling carrying the information, and / or act on the information, and / or present the information (e.g., on a screen and / or as audio or other form of instructions). The information may be based on the received information and / or communication signaling carrying the information. Presenting the information may include processing the received information, e.g., decoding and / or converting, in particular between different formats and / or for the hardware used for presenting. Operating on the information may not depend on or involve presenting and / or proceeding or success, and / or may not involve user interaction or even user reception, for example for target devices without (e.g., normal) user interaction, such as automated processes or MTC devices for automotive or transportation or industrial applications. Information or communication signaling may be expected and / or received based on the target instructions. Presenting and / or operating on the information may generally include one or more processing steps, particularly decoding the information, executing the information, interpreting the information, and / or transforming the information.Operating on the information may generally include relaying and / or transmitting the information, e.g., over an air interface, and relaying and / or transmitting the information may include mapping the information onto signaling (such mapping may generally include one or more layers, e.g., For example, the target indication may relate to one or more layers of the air interface, e.g., the RLC (Radio Link Control) layer and / or the MAC layer and / or one or more physical layers). The information may be transferred (or mapped) onto communication signaling based on the target indication, which may make the information particularly suitable for use in the RAN (e.g., for a network node or a target device, such as a UE or terminal in particular). The tool may be generally adapted for use in a target device, such as a UE or terminal. Generally, the tool may provide multiple functionalities, e.g., for providing and / or selecting a target indication, and / or for presenting, e.g., video and / or audio, and / or for operating on and / or storing the received information. Providing the target indication may include, for example, in the RAN, sending or forwarding the indication as signaling and / or the indication carried on the signaling, if the target device is a UE or a tool for a UE. It should be noted that such provided information may be forwarded to the information system via one or more additional communication interfaces and / or paths and / or connections. The target indication may be a higher layer indication and / or the information provided by the information system may be higher layer information, e.g., application layer or user layer, in particular above a radio layer such as a transport layer and a physical layer. The target indication may be mapped onto physical layer radio signaling, e.g., related to or on a user plane, and / or the information may be mapped onto physical layer radio communication signaling, e.g., related to or on a user plane (in particular in the reverse communication direction). The described approach enables the target indication to be provided and facilitates the information to be provided in a specific format that is particularly suitable and / or adapted to efficiently use the air interface.The user input may represent, for example, a selection from a number of possible transmission modes or formats, and / or paths, for example in terms of data rate and / or packaging and / or size of information to be provided by the information system.

[0076] In general, the numerology and / or subcarrier spacing may dictate the bandwidth (in the frequency domain) of the subcarriers of a carrier, and / or the number of subcarriers in a carrier, and / or the numbering of the subcarriers in a carrier. Different numerologies may differ, in particular in the bandwidth of the subcarriers. In some variations, all subcarriers in a carrier have the same bandwidth associated with them. The numerology and / or subcarrier spacing may differ between carriers, in particular with respect to the subcarrier bandwidth. The symbol time length and / or the time length of the timing structure for a carrier may depend on the carrier frequency and / or the subcarrier spacing and / or the numerology. In particular, different numerologies may have different symbol time lengths.

[0077] Signaling may generally include one or more sy and / or signals and / or messages. A signal may include or represent one or more bits. An instruction may represent signaling and / or be implemented as a signal or as multiple signals. One or more signals may be included in and / or represented by a message. Signaling, particularly control signaling, may include multiple signals and / or messages, which may be transmitted on different carriers and / or relate to different signaling processes, e.g., represent and / or relate to one or more such processes and / or corresponding information. The instructions may include and / or be included in signaling and / or signals and / or messages that may be transmitted on different carriers and / or that may be associated with different acknowledgement signaling processes, e.g., represent and / or relate to one or more such processes. Signaling associated with a channel may be transmitted to represent signaling and / or information for that channel and / or such that the signaling is interpreted by the transmitter and / or receiver as belonging to that channel. Such signaling may generally conform to transmission parameters and / or one or more formats for the channel.

[0078] The reference signaling may be signaling that includes one or more reference symbols and / or structures. The reference signaling may be adapted to measure and / or estimate and / or represent transmission conditions, e.g., channel conditions and / or transmission path conditions and / or channel (or signal or transmission) quality. The transmission characteristics (e.g., signal strength and / or format and / or modulation and / or timing) of the reference signaling may be considered to be available to both the transmitter and receiver of the signaling (e.g., by virtue of being predefined and / or configured or configurable and / or communicated). For example, different types of reference signaling may be considered with respect to uplink, downlink or sidelink, cell-specific (in particular cell-wide, e.g., CRS) or device or user-specific (addressed to a particular target or user equipment, e.g., CSI-RS), demodulation-related (e.g., DMRS), and / or signal strength-related, e.g., power-related or energy-related or amplitude-related (e.g., SRS or pilot signaling), and / or phase-related, etc.

[0079] The uplink or sidelink signaling may be OFDMA (orthogonal frequency division multiple access) or SC-FDMA (single carrier frequency division multiple access) signaling. The downlink signaling may in particular be OFDMA signaling. However, the signaling is not limited thereto (filter bank-based signaling may be considered as one alternative).

[0080] A wireless node may generally be considered as a device or node adapted for wireless and / or radio (and / or microwave) frequency communication and / or for communication utilizing an air interface, e.g., in accordance with a communication standard.

[0081] The radio node may be a network node, or a user equipment or terminal. The network node may be any radio node of a wireless communication network, such as 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 point (TP), and / or an access point (AP), and / or other node, particularly for the RAN described herein.

[0082] The terms wireless device, user equipment (UE) and terminal may be considered interchangeable in the context of this disclosure. A wireless device, user equipment or terminal may represent an end device for communication utilizing a wireless communication network and / or may be implemented as user equipment according to a standard. Examples of user equipment may include a phone such as a smartphone, a personal communication device, a mobile phone or terminal, a computer, particularly a laptop, a sensor or machine with wireless capabilities (and / or adapted for an air interface), particularly for MTC (machine-type communication, sometimes called M2M (machine-to-machine)), or a vehicle adapted for wireless communication. A user equipment or terminal may be mobile or fixed.

[0083] A radio node may generally comprise processing circuitry and / or radio circuitry. A radio node, particularly a network node, may in some cases comprise cable and / or communication circuitry by which the radio node may be connected or connectable to another radio node and / or a core network.

[0084] The circuit elements may comprise integrated circuit elements. The processing circuit elements may comprise one or more processors, and / or controllers (e.g., microcontrollers), and / or ASICs (Application Specific Integrated Circuit Elements), and / or FPGAs (Field Programmable Gate Arrays), or the like. The processing circuit elements may comprise one or more memories or memory configurations and / or be considered as being (operably) connected or connectable to one or more memories or memory configurations. The memory configurations may comprise one or more memories. The memories may be adapted to store digital information. Examples for memories include volatile and non-volatile memories, and / or random access memories (RAMs), and / or read-only memories (ROMs), and / or magnetic and / or optical memories, and / or flash memories, and / or hard disk memories, and / or EPROMs or EEPROMs (erasable programmable ROMs or electrically erasable programmable ROMs).

[0085] The radio circuit element may comprise one or more transmitters and / or receivers and / or transceivers (the transceiver may operate or be operable as a transmitter and receiver, and / or may comprise joint or separate circuit elements for receiving and transmitting, for example in one package or housing), and / or may comprise one or more amplifiers and / or oscillators and / or filters, and / or may comprise antenna circuit elements and / or one or more antennas and / or antenna arrays, and / or may be connected or connectable to antenna circuit elements and / or one or more antennas and / or antenna arrays. The antenna array may comprise one or more antennas, which may be configured as a dimensional array, for example a 2D or 3D array, and / or an antenna panel. As an example of an antenna array, a remote radio head (RRH) may be considered. However, in some variants, the RRH may also be implemented as a network node, depending on the type of circuit elements and / or functionality implemented in the RRH.

[0086] The communication circuitry may comprise wireless circuitry and / or cable circuitry. The communication circuitry may generally comprise one or more interfaces, which may be one or more air interfaces, and / or one or more cable interfaces, and / or one or more optical interfaces, e.g., laser-based. The one or more interfaces may in particular be packet-based. The cable circuitry and / or cable interface may comprise one or more cables (e.g., fiber-optic and / or wire-based) and / or be connected or connectable to one or more cables, which may be connected or connectable, directly or indirectly (e.g., via one or more intermediate systems and / or interfaces), to targets, e.g., controlled by the communication circuitry and / or processing circuitry.

[0087] Any one 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 wireless node, e.g., different circuit elements or different parts of a circuit element. Modules may be considered to be distributed across different components and / or circuit elements. The program products described herein may comprise modules that pertain to a device (e.g., user equipment or network node) on which the program product is intended to be executed (execution may be performed on and / or controlled by the associated circuit elements).

[0088] The radio access network may be a wireless communication network and / or a radio access network (RAN), in particular according to a communication standard. The communication standard may in particular be a standard according to 3GPP and / or 5G, for example NR or LTE, in particular LTE Evolution.

[0089] The wireless communication network may be and / or include a radio access network (RAN), which may be and / or include any type of cellular and / or wireless radio network, which may be connected or connectable to a core network. The approaches described herein are particularly suitable for 5G networks, e.g., LTE Evolution and / or NR (New Radio), respectively, their successors. The RAN may comprise one or more network nodes, and / or one or more terminals, and / or one or more radio nodes. The network node may be a radio node adapted in particular for radio and / or wireless and / or cellular communication with one or more terminals. A terminal may be any device adapted for radio and / or wireless and / or cellular communication with or within a RAN, such as a user equipment (UE) or a mobile phone or a smartphone or a computing device or a vehicular communication device or a device for machine type communication (MTC). A terminal may be mobile or in some cases fixed. A RAN or a wireless communication network may comprise at least one network node and a UE, or at least two wireless nodes. In general, a wireless communication network or system, such as a RAN or a RAN system, may be considered, comprising at least one wireless node, and / or at least one network node, and at least one terminal.

[0090] Transmitting in the downlink may refer to transmission from a network or network node to a terminal. Transmitting in the uplink may refer to transmission from a terminal to a network or network node. Transmitting in the sidelink may refer to (direct) transmission from one terminal to another terminal. Uplink, downlink and sidelink (e.g., sidelink transmission and reception) may be considered as communication directions. In some variants, uplink and downlink may also be used to describe wireless communication between network nodes, for example, for wireless backhaul and / or relay communication and / or (wireless) network communication, especially communications terminating in such, e.g., between base stations or similar network nodes. Backhaul and / or relay communication and / or network communication may be considered to be implemented as a form of sidelink or uplink communication or the like.

[0091] Control information or control information messages or corresponding signaling (control signaling) may be transmitted on a control channel, e.g., a physical control channel, which may be a downlink channel (or a sidelink channel in some cases, e.g., one UE schedules another UE). For example, control information / allocation information may be signaled by a network node on a PDCCH (Physical Downlink Control Channel) and / or a PDSCH (Physical Downlink Shared Channel) and / or a HARQ-specific channel. For example, acknowledgement signaling, as a form of control information or signaling such as uplink control information / signaling, may be transmitted by a terminal on a PUCCH (Physical Uplink Control Channel) and / or a PUSCH (Physical Uplink Shared Channel) and / or a HARQ-specific channel. For multi-component / multi-carrier indication or signaling, multiple channels may be applied.

[0092] Signaling may generally be considered to represent an electromagnetic wave structure (e.g., over a time and frequency interval), which is intended to convey information to at least one specific or general target (e.g., one that may pick up the signaling). The process of signaling may include transmitting signaling. Transmitting signaling, particularly control signaling or communication signaling, including or representing, for example, acknowledgement signaling and / or resource request information, may include coding and / or modulation. The coding and / or modulation may include error detection coding and / or forward error correction coding and / or scrambling. Receiving the control signaling may include corresponding decoding and / or demodulation. The error detection coding may include and / or be based on parity or checksum techniques, for example CRC (Cyclic Redundancy Check). The forward error correction coding may include and / or be based on, for example, turbo coding, and / or Reed-Muller coding, and / or polar coding, and / or LDPC coding (Low Density Parity Check). The type of coding used may be based on the channel (e.g., physical channel) to which the coded signal is associated. The code rate may represent the ratio of the number of information bits before encoding to the number of coded bits after encoding, taking into account that the coding adds coding bits for error detection coding and forward error correction. The coded bits may refer to the information bits (also called systematic bits) and the coding bits.

[0093] The communication signaling may include and / or represent and / or be implemented as data signaling and / or user plane signaling. The communication signaling may be associated with a data channel, for example a physical downlink channel or a physical uplink channel or a physical sidelink channel, in particular a PDSCH (Physical Downlink Shared Channel) or a PSSCH (Physical Sidelink Shared Channel). In general, the data channel may be a shared channel or a dedicated channel. The data signaling may be associated with and / or on the data channel.

[0094] An indication may generally explicitly and / or implicitly indicate the information that the indication represents and / or indicates. An implicit indication may be based, for example, on the location and / or resources used for transmission. An explicit indication may be based, for example, on parameterization, with one or more parameters, and / or one or more indexes, and / or one or more bit patterns representing the information. In particular, the control signaling described herein based on the utilized resource sequence may be considered to implicitly indicate the control signaling type.

[0095] A resource element may generally describe the smallest individually usable and / or encodable and / or decodable and / or modulatable and / or demodulatable time-frequency resource and / or may describe a time-frequency resource covering a symbol duration in time and a subcarrier in frequency. A signal may be and / or may be assigned to a resource element. A subcarrier may be a subband of a carrier, e.g., as defined by a standard. A carrier may define a frequency and / or a frequency band for transmission and / or reception. In some variants, a (jointly coded / modulated) signal may cover two or more resource elements. A resource element may generally be as defined by a corresponding standard, e.g., NR or LTE. Different resource elements have different extensions (lengths / widths) in the time and / or frequency domains, in particular, resource elements may relate to different carriers, since the symbol duration and / or subcarrier spacing (and / or numerology) may differ between different symbols and / or subcarriers.

[0096] A resource may generally represent a time frequency and / or code resource over which signaling, e.g., according to a particular format, is communicated, e.g., transmitted and / or received, and / or intended to be transmitted and / or received.

[0097] A resource pool may generally indicate and / or include resources, particularly time-frequency resources, e.g., time and frequency intervals, and / or code resources, which may be contiguous or interrupted. A resource pool may indicate and / or include, in particular, resource elements and / or resource blocks, e.g., PRBs. A radio node, such as a user equipment, may be considered to have a resource pool configured if the radio node receives a corresponding control signaling that configures the radio node therewith. Such control signaling may be transmitted, in particular, by a receiving radio node as described herein. The control signaling may be, in particular, higher layer signaling, e.g., 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 have a resource pool configured if the responding radio node or user equipment is informed of the corresponding configuration, e.g., that the responding radio node or user equipment may access resources in the pool to transmit. Such a configuration may be predefined in some cases, e.g., based on a standard and / or default configuration. A resource pool may be dedicated to one responding radio node or user equipment or, in some cases, shared among several responding radio nodes or user equipment. A resource pool may be considered to be generic or may be for a specific type of signaling, e.g., control signaling or data signaling. A transmission resource pool may be specifically for control signaling, e.g., uplink control signaling and / or sidelink control signaling, and / or may be dedicated to a user equipment / responding radio node. A resource pool may be considered to include multiple resource structures, which may be organized, for example, in sub-pools or groups related to and / or following a type of (received or scheduled) signaling or a type of responding control signaling. Each group or sub-pool may include a certain number of resource structures, which may be represented by an indicator and / or a bit field in the selection control information.For example, the maximum number of resource structures in a group may correspond to the maximum number of different values ​​that can be represented by a bit field or indicator. Different groups may have different numbers of resource structures. In general, a group may be considered to include 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 space of availability of resources and / or resource structures available for a particular signaling. In particular, a transmission resource pool may be considered to represent a (time / frequency and / or code) domain or space of resources available for responsive control signaling.

[0098] The signaling characteristics may represent resources and / or resource structures in the receiving resource pool that may differ from the transmitting resource pool. The resources and / or resource structures representing the signaling characteristics of the characterizing signaling, in particular the downlink (or sidelink) control signaling, and / or the corresponding pool may in particular include one or more CORESETs (COntrol REsource SETs), each of which may represent a group or a subpool. A CORESET may relate to a particular time interval, for example one or more symbols, in particular in a transmission timing structure such as a slot. A first CORESET may be considered to be set for one, two or three first symbols in a slot. A second CORESET may be set for one or more subsequent symbols, for example the fifth and / or sixth symbol of the same slot. In this case, the second CORESET may in particular correspond to minislot-related signaling and may include, for example, short (e.g., one or two symbols) responsive control signaling and / or short latency requirements (e.g., one or two symbols) and / or resource structures related to received or scheduled transmissions during and / or in response to a minislot, e.g., minislot data signaling. The first CORESET may relate to slot-based signaling, e.g., long data signaling (longer than two, three or four symbols) and / or responsive control signaling with relaxed latency requirements (e.g., allowing transmissions of more than one or two symbols and / or in later transmission timing structures such as later slots or subframes) and / or long responsive control signaling, e.g., longer than two or three or four symbols. In general, different CORESETs may be separated in the time domain by at least one symbol, in particular by one, two, three or four symbols.Depending on which of the groups or sub-pools, in particular the CORESET, the characterization signaling may be related to a particular sub-pool or group of the transmission resource pool. The receiving resource pool may be predefined for the responding radio node and / or configured, for example, by the receiving radio node, which may alternatively or additionally configure the transmission resource pool. The pool configuration may generally be predefined or may be performed by the network or network node (e.g., the receiving radio node) or by another responding radio node requiring corresponding functionality and / or also operating as a receiving radio node, for example in a sidelink communication (where the configuration may be performed by another UE, or by the network / network node).

[0099] The boundary symbol may generally represent a start or end symbol for transmitting and / or receiving. The start symbol may in particular be a start symbol of uplink or sidelink signaling, e.g., control or data signaling. Such signaling may be on a data or control channel, e.g., a physical channel, in particular, a physical uplink shared channel (such as a PUSCH) or a sidelink data or shared channel, or a physical uplink control channel (such as a PUCCH) or a sidelink control channel. If the start symbol is related to control signaling (e.g., on a control channel), the control signaling is in response to received signaling (in the sidelink or downlink), e.g., may represent an acknowledgement signaling related to the received signaling, which may be a HARQ or ARQ signaling. The end symbol may represent an end symbol (in time) of a downlink or sidelink transmission or signaling that may be intended for or scheduled for a wireless node or user equipment. Such downlink signaling may in particular be data signaling on a physical downlink channel, such as a shared channel, e.g., a Physical Downlink Shared Channel (PDSCH). A start symbol may be determined based on and / or with respect to such an end symbol.

[0100] Configuring a radio node, in particular a terminal or user equipment, may refer to the radio node being adapted or operated or set to operate and / or instructed to operate according to its configuration. Configuring may be performed by another device, e.g. a network node (e.g. a radio node of a network, such as a base station or eNodeB) or a network, in which case configuring may include transmitting configuration data to the radio node to be configured. Such configuration data may represent the configuration to be configured and / or include one or more instructions regarding the configuration, e.g. configuration for transmitting and / or receiving on allocated resources, in particular frequency resources. The radio node may configure itself based on configuration data received, e.g. from the network or network node. The network node may utilize and / or be adapted to utilize one or more circuit elements of the network node for the configuration. The allocation information may be considered as a form of configuration data. The configuration data may include and / or be represented by the configuration information and / or one or more corresponding instructions and / or one or more messages.

[0101] In general, configuring may include determining configuration data representative of the configuration and providing, e.g., transmitting, (in parallel and / or sequentially), the configuration data to one or more other nodes, which may further transmit the configuration data to the wireless node (or to another node, which may be repeated until the configuration data reaches the wireless device). Alternatively or additionally, configuring the wireless node, e.g., by a network node or other device, may include receiving the configuration data and / or data related to the configuration data from another node, such as a network node, which may be a higher level node of the network, and / or transmitting the received configuration data to the wireless node. Thus, determining the configuration and transmitting the configuration data to the wireless node may be performed by different network nodes or entities that may be capable of communicating over a suitable interface, e.g., the X2 interface in the case of LTE, or a corresponding interface for NR. Configuring the terminal may include scheduling downlink and / or uplink transmissions for the terminal, e.g., downlink data and / or downlink control signaling and / or DCI and / or uplink control or data or communication signaling, in particular acknowledgment signaling, and / or configuring resources and / or a resource pool for resources.

[0102] A resource structure may be considered to be adjacent to another resource structure in the frequency domain if the resource structure and the other resource structure share a common boundary frequency, e.g., one as an upper frequency boundary and the other as a lower frequency boundary. Such a boundary may be represented, for example, by the upper end of the bandwidth allocated to subcarrier n, which also represents the lower end of the bandwidth allocated to subcarrier n+1. A resource structure may be considered to be adjacent to another resource structure in the time domain if the resource structure and the other resource structure share a common boundary time, e.g., one as an upper (or right in the figure) boundary and the other as a lower (or left in the figure) boundary. Such a boundary may be represented, for example, by the end of the symbol time interval allocated to symbol n, which also represents the beginning of the symbol time interval allocated to symbol n+1.

[0103] In general, a resource structure being adjacent to another resource structure in a domain may also be referred to as abutting and / or bordering the other resource structure in the domain.

[0104] A resource structure generally represents a structure in the time and / or frequency domain, and may represent a time interval and a frequency interval in particular. A resource structure may include and / or consist of resource elements, and / or a time interval of a resource structure may include and / or consist of one or more symbol time intervals, and / or a frequency interval of a resource structure may include and / or consist of one or more subcarriers. A resource element may be considered as an example of a resource structure, a slot or minislot or a physical resource block (PRB), or some of them may be considered as others. A resource structure may relate to a particular channel, e.g., PUSCH or PUCCH, in particular a resource structure smaller than a slot or PRB.

[0105] Examples of resource structures in the frequency domain include a bandwidth or band, or a bandwidth portion. A bandwidth portion may be a portion of a bandwidth available for a wireless node to communicate, for example due to circuit elements and / or configuration and / or regulations and / or standards. A bandwidth portion may be configured or configurable for a wireless node. In some variations, a bandwidth portion may be a portion of a bandwidth used by a wireless node to communicate, for example to transmit and / or receive. A bandwidth portion may be smaller than a bandwidth (which may be a device bandwidth defined by a device's circuit elements / configuration and / or a system bandwidth, for example available for a RAN). A bandwidth portion may be considered to include one or more resource blocks or resource block groups, in particular one or more PRBs or PRB groups. A bandwidth portion may relate to and / or include one or more carriers. A resource pool or region or set may generally include one or more (in particular two or a multiple of two greater than two) resources or resource structures. A resource or resource structure may include one or more resource elements (in particular, two or a multiple of two resource elements greater than two) or one or more PRBs or PRB groups (in particular, two or a multiple of two PRBs or PRB groups greater than two), which may be contiguous in frequency.

[0106] A carrier may generally represent a frequency range or band and / or relate to a center frequency and an associated frequency interval. A carrier may be considered to include multiple subcarriers. A carrier may have allocated thereto a center frequency or center frequency interval, for example, represented by one or more subcarriers (each subcarrier may generally be allocated a frequency bandwidth or interval). Different carriers may be non-overlapping and / or adjacent in the frequency domain.

[0107] It should be noted that the term "wireless" in this disclosure may be considered to refer to wireless communications in general, and may also include wireless communications utilizing microwave and / or millimeter and / or other frequencies between 100 MHz or 1 GHz and 100 GHz or 20 GHz or 10 GHz in particular. Such communications may utilize one or more carriers.

[0108] A radio node, in particular a network node or terminal, may generally be any device adapted to transmit and / or receive 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 (sometimes referred to as an LBT carrier), e.g., an unlicensed carrier. A carrier may be considered to be part of a carrier aggregate.

[0109] Receiving or transmitting on a cell or carrier may refer to receiving or transmitting using a frequency (band) or spectrum associated with the cell or carrier. A cell may generally include and / or be defined by or for one or more carriers, in particular at least one carrier for UL communication / transmission (called a UL carrier) and at least one carrier for DL ​​communication / transmission (called a DL carrier). A cell may be considered to include different numbers of UL and DL carriers. Alternatively or additionally, a cell may include at least one carrier for UL and DL communication / transmission, for example in a TDD-based approach.

[0110] A channel may generally be a logical channel, a transport channel or a physical channel. A channel may comprise and / or be configured on one or more carriers, particularly multiple subcarriers. A channel for carrying and / or carrying control signaling / control information may be considered as a control channel, particularly if the channel is a physical layer channel and / or if the channel carries control plane information. Similarly, a channel for carrying and / or carrying data signaling / user information may be considered as a data channel, particularly if the channel is a physical layer channel and / or if the channel carries user plane information. A channel may be defined for a particular communication direction or for two complementary communication directions (e.g., UL and DL, or sidelink in two directions), in which case it may be considered as having two component channels, one component channel for each direction. Examples of channels include channels for low latency and / or reliable transmissions, which may be for control and / or data, particularly for Ultra-Reliable Low Latency Communications (URLLC).

[0111] In general, a symbol may represent and / or be associated with a symbol time length, which may depend on the carrier and / or subcarrier spacing and / or numerology of the associated carrier. Thus, a symbol may be considered to indicate a time interval having a symbol time length with respect to the frequency domain. The symbol time length may depend on the carrier frequency and / or bandwidth and / or numerology and / or subcarrier spacing of or associated with the symbol. Thus, different symbols may have different symbol time lengths. In particular, numerologies with different subcarrier spacing may have different symbol time lengths. In general, the symbol time length may be based on and / or include a guard time interval or a cyclic extension, such as a prefix or postfix.

[0112] A sidelink may generally refer to a communication channel (or channel structure) between two UEs and / or terminals, where data is transmitted between participants (UEs and / or terminals) via the communication channel, e.g., directly and / or without being relayed via a network node. A sidelink may be established only over one or more air interfaces of the participants, which may be directly linked via a sidelink communication channel, and / or directly over those air interfaces. In some variants, sidelink communication may be performed without interaction by a network node, e.g., on fixedly defined resources and / or on resources negotiated between the participants. Alternatively or additionally, a network node may be considered to provide some control functionality, e.g., by configuring resources for sidelink communication, in particular one or more resource pools, and / or by monitoring the sidelink, e.g., for charging purposes.

[0113] Sidelink communication may also be referred to as device-to-device (D2D) communication, e.g., in the context of LTE, and / or in some cases as ProSe (Proximity Services) communication. Sidelink may be implemented in the context of V2x communication (vehicle communication), e.g., V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), and / or V2P (vehicle-to-person). A device adapted for sidelink communication may be considered as user equipment or terminal.

[0114] The sidelink communication channel (or structure) may include one or more (e.g., physical or logical) channels, such as a PSCCH (e.g., a physical sidelink control channel, which may carry control information such as an acknowledgement position indication) and / or a PSSCH (e.g., a physical sidelink shared channel, which may carry data signaling and / or acknowledgement signaling). A sidelink communication channel (or structure) may be considered to relate to and / or use one or more carriers and / or one or more frequency ranges associated with and / or used by the cellular communication, e.g., in accordance with a particular license and / or standard. The participants share (physical) channels and / or resources of the sidelink, in particular in the frequency domain and / or relating to frequency resources such as carriers, such that on the (physical) channels and / or resources two or more participants transmit, e.g. simultaneously and / or time shifted, and / or a particular channel and / or resource may be relevant to a particular participant, such that, e.g., only one participant transmits on a particular channel, or on one particular resource or on multiple particular resources, e.g. in the frequency domain and / or relating to one or more carriers or subcarriers.

[0115] The sidelink may conform to and / or be implemented according to a particular standard, e.g., an LTE-based standard and / or NR. The sidelink may utilize TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex) technologies, e.g., as configured by a network node and / or pre-configured between the participants and / or negotiated between the participants. A user equipment may be considered adapted for sidelink communication if the user equipment and / or radio and / or processing circuitry of the user equipment is adapted for utilizing sidelink, e.g., on one or more frequency ranges and / or carriers and / or in one or more formats, in particular according to a particular standard. In general, a radio access network may be considered to be defined by two participants of sidelink communication. Alternatively or additionally, the radio access network may be represented and / or defined with and / or involve network nodes and / or communication with such nodes.

[0116] Communicating or communicating may generally include transmitting and / or receiving signaling. Communication over the sidelink (or sidelink signaling) may include utilizing the sidelink for communication (respectively, for signaling). Sidelink transmission and / or transmitting on the sidelink may be considered to include transmission utilizing the sidelink, e.g., associated resources and / or transmission formats and / or circuit elements, and / or air interface. Sidelink reception and / or receiving on the sidelink may be considered to include reception utilizing the sidelink, e.g., associated resources and / or transmission formats and / or circuit elements, and / or air interface. Sidelink control information (e.g., SCI) may generally be considered to include control information transmitted utilizing the sidelink.

[0117] In general, carrier aggregation (CA) may refer to the concept of a radio connection and / or communication link between a wireless and / or cellular communication network and / or a network node and a terminal, or on a sidelink including multiple carriers for at least one direction of transmission (e.g., DL and / or UL), as well as an aggregation of carriers. The corresponding communication link may be referred to as a carrier aggregated communication link, or CA communication link, and the carriers in the carrier aggregation may be referred to as component carriers (CCs). In such a link, data may be transmitted across two or more and / or all carriers (aggregates of carriers) of the carrier aggregation. The carrier aggregation may include one (or more) dedicated control carriers and / or primary carriers (e.g., sometimes referred to as primary component carriers or PCCs), over which control information may be transmitted, and the control information may refer to the primary carrier and other carriers, sometimes referred to as secondary carriers (or secondary component carriers (SCCs)). However, in some approaches, the control information may be sent across more than one carrier of an aggregate, for example, one or more PCCs and one PCC and one or more SCCs.

[0118] A transmission may generally relate to a particular channel and / or a particular resource, in particular with a start symbol and an end symbol in time and covering an interval between the start and end symbols. 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 must be realized. For example, a scheduled downlink transmission may not be received or a scheduled uplink transmission may not be transmitted due to power limitations or other effects (e.g., a channel on an unlicensed carrier being occupied). A transmission may be scheduled for a transmission timing sub-structure within a transmission timing structure such as a slot (e.g., a mini-slot and / or one that covers only a portion of the transmission timing structure). A boundary symbol may indicate the symbol in the transmission timing structure at which a transmission starts or ends.

[0119] Predefined in the context of the present disclosure may refer to the relevant information being defined, e.g., in a standard, and / or being available without specific configuration from the network or network node, e.g., stored in a memory, e.g., independent of being configured. Configured or configurable may be considered to relate to the corresponding information being set / configured, e.g., by the network or network node.

[0120] A setting or schedule, such as a minislot setting and / or a structure setting, may schedule a transmission, for example, for a time / transmission for which the setting is valid, and / or the transmission may be scheduled by a separate signaling or a separate setting, for example, a separate RRC signaling and / or a downlink control information signaling. The scheduled transmission or transmissions may represent signaling to be transmitted by the device for which the scheduled transmission is scheduled, or signaling to be received by the device for which the scheduled transmission is scheduled, depending on which side of the communication the device is on. It should be noted that the downlink control information, or in particular DCI signaling, may be considered as physical layer signaling, as opposed to higher layer signaling, such as MAC (Medium Access Control) signaling or RRC layer signaling. The higher the layer of signaling, the less frequent / more time / resource consuming that signaling may be considered, at least in part, due to the fact that the information contained in such signaling must be passed through several layers, each of which requires processing and handling.

[0121] The scheduled transmissions and / or transmission timing structures such as minislots or slots may relate to a particular channel, in particular a physical uplink shared channel, a physical uplink control channel, or a physical downlink shared channel, e.g. PUSCH, PUCCH or PDSCH, and / or to a particular cell and / or carrier aggregation. The corresponding configuration, e.g. a scheduling configuration or a symbol configuration, may relate to such a channel, cell and / or carrier aggregation. The scheduled transmissions may be considered to represent transmissions on a physical channel, in particular a shared physical channel, e.g. a physical uplink shared channel or a physical downlink shared channel. For such channels, a semi-persistent configuration may be particularly suitable.

[0122] In general, the configuration may be a setting that dictates timing and / or may be expressed or configured with corresponding configuration data. The configuration may be embedded and / or included in messages or settings or corresponding data that may dictate and / or schedule resources, particularly in a semi-persistent and / or semi-static manner.

[0123] The control region of the transmission timing structure may be an interval in time that is intended or scheduled or reserved for control signaling, in particular downlink control signaling, and / or for a particular control channel, e.g., a physical downlink control channel such as the PDCCH. The interval may include and / or consist of several symbols in time, which may be configured or configurable, e.g., by (UE-specific) dedicated signaling (which may be single-cast and, e.g., addressed or targeted to a particular UE), e.g., on the PDCCH or RRC signaling, or on a multicast or broadcast channel. In general, the transmission timing structure may include a control region that covers a configurable number of symbols. In general, the boundary symbol may be considered to be configured to be after the control region in time.

[0124] The duration of the symbols of the transmission timing structure (symbol time length or interval) may generally depend on the numerology and / or carrier, which may be configurable. The numerology may be the numerology to be used for the scheduled transmission.

[0125] Scheduling or for a device and / or scheduling related transmissions or signaling may be considered to include or be a form of configuring the device with resources and / or to be a form of instructing the device of those resources, for example, to use for communicating. Scheduling may in particular relate to a transmission timing structure, or a sub-structure of the transmission timing structure (e.g., a slot, or a minislot, which may be considered a sub-structure of a slot). Boundary symbols may be considered to be identified and / or determined with respect to the transmission timing structure, even if a sub-structure is scheduled, for example, even if the underlying timing grid is defined based on the transmission timing structure. Signaling instructing scheduling may include corresponding scheduling information, and / or may be considered to represent or include configuration data instructing the scheduled transmission and / or including scheduling information. Such configuration data or signaling may be considered as resource configuration or scheduling configuration. It should be noted that such configuration in some cases (especially as a single message) may not be complete without other configuration data, for example, configured with other signaling, for example, higher layer signaling. In particular, a symbol configuration may be provided in addition to a scheduling / resource configuration to identify exactly which symbols are allocated to a scheduled transmission. The scheduling (or resource) configuration may indicate one or more transmission timing structures and / or amounts of resources (e.g., in number of symbols or length of time) for the scheduled transmission.

[0126] A scheduled transmission may be, for example, a transmission scheduled by a network or a network node. A transmission may be, in this context, an uplink (UL) or downlink (DL) or sidelink (SL) transmission. Thus, a device, for which a scheduled transmission is scheduled, for example, a user equipment, may be scheduled to receive (for example, in DL or SL) or to transmit (for example, in UL or SL) the scheduled transmission. Scheduling a transmission may be considered to include, in particular, configuring the scheduled device with one or more resources for this transmission and / or informing the device that the transmission is intended for and / or scheduled for some resource. A transmission may be scheduled to cover a time interval, in particular several consecutive symbols, which may form a continuous interval in time between (and including) a start symbol and an end symbol. The start symbol and the end symbol of a (for example, scheduled) transmission may be in the same transmission timing structure, for example, in the same slot. However, in some cases, the end symbol may be in a later transmission timing structure than the start symbol, in particular a structure that follows in time. A scheduled transmission may be associated with and / or indicated by a duration, e.g., in a number of symbols or a number of associated time intervals. In some variations, there may be different transmissions scheduled in the same transmission timing structure. A scheduled transmission may be considered to be associated with a particular channel, e.g., a shared channel such as the PUSCH or PDSCH.

[0127] In the context of the present disclosure, a distinction may be made between dynamically scheduled or aperiodic transmissions and / or configurations and semi-static or semi-persistent or periodic transmissions and / or configurations. The term "dynamic" or similar terms may generally relate to a valid and / or scheduled and / or configured configuration / transmission for a (relatively) short time scale and / or a (e.g., predefined and / or configured and / or limited and / or well-defined) number of occurrences and / or for one or more transmission timing structures, such as slots or slot aggregation, and / or for one or more (e.g., a specific number) of transmissions / occurrences. Dynamic configuration may be based on low-level signaling, e.g., control signaling on the physical layer and / or MAC layer, especially in the form of DCI or SCI. Periodic / semi-static may relate to a longer time scale, e.g., several slots and / or more than one frame, and / or an undefined number of occurrences, e.g., until an incompatibility due to the dynamic configuration or until a new periodic configuration is reached. The periodic or semi-static configuration may be configured based on and / or in conjunction with higher layer signaling, in particular RCL layer signaling and / or RRC signaling and / or MAC signaling.

[0128] A transmission timing structure may define intervals (respectively their associated time intervals) that include multiple symbols and / or include several symbols. It should be noted that in the context of this disclosure, references to symbols for ease of reference may be interpreted as referring to the time domain projection or time interval or time component or duration or length of time of the symbol, unless it is clear from the context that frequency domain components must also be considered. Examples of transmission timing structures include slots, subframes, minislots (which may also be considered as substructures of slots), and slot aggregations (which may include multiple slots and may be considered as superstructures of slots), respectively, their time domain components. A transmission timing structure generally defines a time domain extension (e.g., interval or length or duration) of a transmission timing structure and may include multiple symbols 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 succession of such transmission timing structures, which may, for example, define a timing grid with the symbol representing the smallest grid structure. The transmission timing structure and / or the boundary symbols or scheduled transmissions may be determined or scheduled with respect to such a timing grid. The receiving transmission timing structure may be, for example, a transmission timing structure with respect to which the scheduling control signaling is received. The transmission timing structure may be, in particular, a slot or subframe, or in some cases a minislot.

[0129] The feedback signaling may be considered as a form of control signaling, e.g., uplink or sidelink control signaling, such as UCI (uplink control information) signaling or SCI (sidelink control information) signaling. The feedback signaling may comprise and / or represent, among others, acknowledgement signaling and / or acknowledgement information and / or measurement reports.

[0130] The acknowledgement information may include an indication of a particular value or state for an acknowledgement signaling process, for example ACK or NACK or DTX. Such an indication may represent, for example, a bit or a bit value or a bit pattern or an information switch. For example, different levels of acknowledgement information, providing differentiated information on the quality of reception and / or error location in one or more received data elements, may be considered as and / or represented by control signaling. The acknowledgement information may generally indicate an acknowledgement or a negative acknowledgement or non-reception or different levels thereof, for example representing an ACK or NACK or DTX. The acknowledgement information may relate to one acknowledgement signaling process. The acknowledgement signaling may include acknowledgement information for one or more acknowledgement signaling processes, in particular one or more HARQ or ARQ processes. It may be considered that a certain number of bits of the information size of the control signaling is allocated to each acknowledgement signaling process for which the acknowledgement information relates. The measurement report signaling may include measurement information.

[0131] Signaling may generally include one or more symbols and / or signals and / or messages. A signal may include and / or represent one or more bits, which may be modulated into a common modulated signal. An instruction may represent signaling and / or be implemented as a signal or as multiple signals. One or more signals may be included in and / or represented by a message. Signaling, particularly control signaling, may include multiple signals and / or messages, which may be transmitted on different carriers and / or relate to different acknowledgement signaling processes, e.g., represent and / or relate to one or more such processes. The instructions may include and / or be contained in signaling and / or multiple signals and / or messages, which may be transmitted on different carriers and / or relate to different acknowledgment signaling processes, e.g., represent and / or relate to one or more such processes.

[0132] Signaling utilizing and / or on and / or related to a resource or resource structure may be signaling covering the resource or structure, on one or more associated frequencies, and / or in one or more associated time intervals. A signaling resource structure may be considered to include and / or encompass one or more substructures, which may be associated with one or more different channels and / or one or more types of signaling, and / or may include one or more holes (one or more resource elements that are not scheduled for transmission or reception of a transmission). A resource substructure, e.g., a feedback resource structure, may generally be contiguous in time and / or frequency within an associated interval. A substructure, in particular a feedback resource structure, may be considered to represent a rectangle filled with one or more resource elements in a time / frequency space. However, in some cases, a resource structure or substructure, in particular a frequency resource range, may represent a non-contiguous pattern of resources in one or more domains, e.g., time and / or frequency. Resource elements of a substructure may be scheduled for associated signaling.

[0133] It should be noted that, in general, the number of bits or bit rate associated with a particular signaling that may be carried on a resource element may be based on a modulation coding scheme (MCS). Thus, the bits or bit rate may be viewed as a form of resource, representing a resource structure or extent in frequency and / or time, for example, depending on the MCS. The MCS may be set or configurable, for example, by control signaling, for example, DCI or MAC (medium access control) or RRC (radio resource control) signaling.

[0134] Different formats for control information may be considered, e.g., different formats for control channels such as the Physical Uplink Control Channel (PUCCH). The PUCCH may carry the control information or corresponding control signaling, e.g., the Uplink Control Information (UCI). The UCI may include feedback signaling, and / or acknowledgement signaling, such as HARQ feedback (ACK / NACK), and / or measurement information signaling, including, e.g., channel quality information (CQI), and / or scheduling request (SR) signaling. One of the supported PUCCH formats may be short, e.g., occurring 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, e.g., as sidelink control information (SCI), in particular on a (physical) sidelink control channel such as the (P)SCCH.

[0135] A code block may be considered a data element such as a transport block or a sub-element or sub-structure of a data block, e.g., a transport block may include one or more code blocks.

[0136] A scheduling allocation may be configured with a control signaling, e.g., a downlink control signaling or a sidelink control signaling. Such a control signaling may be considered to represent and / or include a scheduling signaling that may indicate the scheduling information. A scheduling allocation may be considered as scheduling information that indicates the scheduling of a signaling / transmission of a signaling, and in particular may relate to a signaling received or to be received by a device for which the scheduling allocation is configured. A scheduling allocation may be considered to indicate data (e.g., a data block or element and / or a channel and / or a data stream), and / or a (related) acknowledgement signaling process, and / or one or more resources on which the data (or, in some cases, a reference signaling) should be received, and / or one or more resources for related feedback signaling, and / or a feedback resource range on which the related feedback signaling should be transmitted. A transmission related to an acknowledgement signaling process, and / or related resources or resource structures may be configured and / or scheduled, e.g., by a scheduling allocation. Different scheduling allocations may be associated with different acknowledgement signaling processes. A scheduling allocation may be considered as an example of downlink control information or signaling, e.g., if transmitted by a network node and / or provided on the downlink (or sidelink control information, if transmitted using the sidelink and / or by a user equipment).

[0137] A scheduling grant (e.g., an uplink grant) may represent control signaling (e.g., downlink control information / signaling). A scheduling grant may be considered to configure a signaling resource range and / or resources for uplink (or sidelink) signaling, in particular uplink control signaling and / or feedback signaling, e.g., acknowledgement signaling. Configuring a signaling resource range and / or resources may include configuring or scheduling a signaling resource range and / or resources for transmission by the configured radio node. A scheduling grant may indicate channels and / or possible channels that should be used / available for feedback signaling, in particular whether a shared channel such as PUSCH can / should be used. A scheduling grant may generally indicate one or more uplink resources and / or uplink channels and / or formats for control information regarding the associated scheduling allocation. Both the grant and the one or more allocations may be considered as control information (downlink or sidelink) and / or may be associated with and / or transmitted with different messages.

[0138] A resource structure in the frequency domain (sometimes referred to as a frequency interval and / or range) may be represented by a subcarrier grouping. A subcarrier grouping may include one or more subcarriers, each of which may represent a particular frequency interval and / or bandwidth. The bandwidth of the subcarriers, the length of the interval in the frequency domain, may be determined by the subcarrier spacing and / or numerology. The subcarriers may be configured such that each subcarrier is adjacent to at least one other subcarrier of the grouping in frequency space (for grouping sizes larger than one). The subcarriers of a grouping may be associated with the same carrier, e.g., configurable or set or predefined. A physical resource block may be considered to represent a grouping (in the frequency domain). A subcarrier grouping may be considered to be associated with a particular channel and / or a particular type of signaling, whose transmission for such channel or signaling is scheduled and / or transmitted and / or intended and / or configured for at least one, or multiple, or all subcarriers in the grouping. Such associations may be time-dependent, e.g., set or configurable or predefined, and / or dynamic or semi-static. Associations may be different for different devices, e.g., set 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 one or more groupings without associated signaling (e.g., as seen from a particular device).One example of a pattern is a comb, where between pairs of groupings associated with the same signaling / channel, one or more groupings associated with one or more different channels and / or signaling types, and / or one or more groupings with no associated channel / signaling are configured.

[0139] Exemplary types of signaling include signaling of a particular communication direction, in particular uplink signaling, downlink signaling, sidelink signaling, as well as reference signaling (e.g., SRS or CRS or CSI-RS), communication signaling, control signaling, and / or signaling related to a particular channel such as PUSCH, PDSCH, PUCCH, PDCCH, PSCCH, PSSCH, etc.

[0140] The operating conditions may relate to the loading of the RAN, or to an application or use case of the transmission or signaling, and / or to a quality of service (QoS) condition (or requirement) for the transmission or signaling. The QoS may relate, for example, to a data rate and / or a priority and / or a latency and / or a transmission quality, e.g., a BLER or a BER. The use of URLLC may be considered as a quality of service related condition.

[0141] In this disclosure, for purposes of explanation and not limitation, specific details are set forth (such as particular network functions, processes and signaling steps) 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 may be implemented in other variations and variations that depart from these specific details.

[0142] For example, the concepts and aspects are described in part in the context of Long Term Evolution (LTE) or LTE-Advanced (LTE-A) or new wireless mobile or wireless communication technologies, but this does not preclude the use of the concepts and aspects with respect to additional or alternative mobile communication technologies, such as Global System for Mobile Communications (GSM). It will be appreciated that although the described variations may relate to several Technical Specifications (TS) of the Third Generation Partnership Project (3GPP), the techniques, concepts and aspects may also be implemented with respect to different Performance Management (PM) specifications.

[0143] Moreover, those skilled in the art will appreciate that the services, functions, and steps described herein may be implemented using software operating in conjunction with a programmed microprocessor, or using an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), or a general purpose computer. Also, while the variations described herein are elucidated in the context of methods and devices, it will be appreciated that the concepts and aspects presented herein may also be embodied in program products, as well as in systems comprising control circuitry, such as a computer processor, and memory coupled to the processor, the memory being encoded with one or more programs or program products that perform the services, functions, and steps disclosed herein.

[0144] The advantages of the aspects and variations presented herein will be fully understood from the above description, and it will be apparent that various changes may be made in the form, construction and arrangement of those exemplary aspects without departing from the scope of the concepts and aspects described herein or sacrificing all of its advantageous effects. The aspects presented herein may be modified in many ways.

[0145] Some useful abbreviations include: Abbreviation Description ACK / NACK Acknowledgement / Negative Acknowledgement ARQ Automatic Repeat Request CAZAC Constant Amplitude Zero Cross Correlation CBG Code Block Group CDM code division multiplexing CM Cubic Metric 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 Allocation Indicator DCI Downlink Control Information DFT Discrete Fourier Transform DM(-)RS Demodulation reference signal (signaling) FDM frequency division multiplexing HARQ Hybrid Automatic Repeat Request IFFT Inverse Fast Fourier Transform MBB Mobile Broadband MCS Modulation and Coding Scheme MIMO Multiple Input Multiple Output MRC Maximum Ratio Combination MRT maximum ratio transmission MU-MIMO Multi-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 PRACH 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 Quality of Service RB Resource Block RNTI Radio Network Temporary Identifier RRC Radio Resource Control SC-FDM / A Single Carrier Frequency Division Multiplexing / Multiple Access SCI Sidelink Control Information SINR Signal to Interference Plus Noise Ratio SIR Signal to Interference 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 and highly reliable communication VL-MIMO Very Large Multiple Input Multiple Output ZF Zero Forcing Abbreviations may be assumed to follow 3GPP usage where applicable.

Claims

1. 1. A method of operating a target wireless node in a radio access network, the method comprising: receiving control information transmitted on a control channel from a transmitting wireless node; transmitting a first acknowledgment feedback regarding the control information; Including, The control information is a first response resource indication indicating resources for transmission of the first acknowledgment feedback; and - scheduling type control information indicating resources and / or parameters for reception of data signaling by the target wireless node; a second response resource indication indicating a second resource for transmitting a second acknowledgement feedback regarding the data signaling after transmitting the first acknowledgement feedback; and A method comprising:

2. The method of claim 1, wherein the control information further includes command type control information.

3. A method as described in claim 1 or 2, wherein sending the first acknowledgment feedback is based on determining whether the control information has been correctly received based on error coding and / or reception quality.

4. A method according to any one of claims 1 to 3, wherein the control information further comprises a position indication indicating a position of the first acknowledgment feedback relative to the second acknowledgment feedback and / or in a feedback codebook.

5. A target wireless node for a radio access network, the target wireless node comprising: receiving control information transmitted on a control channel from a transmitting wireless node; Transmitting a first acknowledgement feedback regarding the control information It is adapted for The control information is a first response resource indication indicating resources for transmission of the first acknowledgment feedback; and - scheduling type control information indicating resources and / or parameters for reception of data signaling by the target wireless node; a second response resource indication indicating a second resource for transmitting a second acknowledgement feedback regarding the data signaling after transmitting the first acknowledgement feedback; and A target wireless node including:

6. The target wireless node of claim 5, wherein the control information further includes command type control information.

7. A target wireless node as described in claim 5 or 6, wherein the control information further includes a position instruction indicating a position of the first acknowledgment feedback relative to the second acknowledgment feedback and / or in a feedback codebook.

8. 1. A method of operating a transmitting radio node in a radio access network, the method comprising: transmitting control information to a target wireless node on a control channel; receiving a first acknowledgment feedback regarding the control information; retransmitting the control information to the target wireless node based on the first acknowledgement feedback; The control information is a first response resource indication indicating resources for transmission of the first acknowledgment feedback; and - scheduling type control information indicating resources and / or parameters for reception of data signaling by the target wireless node; a second response resource indication indicating a second resource for transmitting a second acknowledgement feedback regarding the data signaling after transmitting the first acknowledgement feedback; and Including, method.

9. The method of claim 8, wherein the control information further includes command type control information.

10. A method as described in claim 8 or 9, wherein the control information further includes a position instruction indicating a position of the first acknowledgement feedback relative to the second acknowledgement feedback and / or in a feedback codebook.

11. A transmitting radio node for a radio access network, the transmitting radio node comprising: Transmitting control information to the target wireless node on a control channel; receiving a first acknowledgment feedback regarding the control information; retransmitting the control information to the target wireless node based on the first acknowledgement feedback. It is adapted for The control information is a first response resource indication indicating resources for transmission of the first acknowledgment feedback; and - scheduling type control information indicating resources and / or parameters for reception of data signaling by the target wireless node; a second response resource indication indicating a second resource for transmitting a second acknowledgement feedback regarding the data signaling after transmitting the first acknowledgement feedback; and a transmitting wireless node.

12. The transmitting wireless node of claim 11 , wherein the control information further comprises command type control information.

13. The transmitting radio node of claim 11 or 12, wherein the control information further comprises a position indication indicating a position of the first acknowledgement feedback relative to the second acknowledgement feedback and / or in a feedback codebook.

14. A computer program comprising instructions adapted to cause processing circuitry to carry out the method of claim 1.

15. A computer program comprising instructions adapted to cause a processing circuit element to carry out the method of claim 8.

Images