DE202017007176U1 - Resource signaling for a PUCCH - Google Patents

Abstract

A user equipment, UE, (10) for a New Radio, NR, radio access network, the UE comprising: a processing circuit (20), the UE being configured to use the processing circuit to provide a hybrid automatic retry request, HARQ, feedback to send that relates to downlink data sent on a shared downlink physical channel, PDSCH, the downlink data comprising at least one downlink data element, the HARQ feedback having an uplink signaling format that has at least one acknowledgment -Substructure, wherein each of the substructures carries confirmation information relating to a downlink data element, each of the confirmation substructures being mapped to another one of the downlink data elements based on at least one confirmation position information that is contained in one of the UE received downlink control signaling is provided, wherein the confirmation position sa specification includes specifying a timing, the specification of the timing includes a timing bit pattern of more than one bit that explicitly specifies a slot for sending the HARQ feedback, the slot comprising at least 14 symbol time intervals; the confirmation position indication further includes a resource selection statement comprising a resource bit pattern, the resource bit pattern comprising more than one bit and explicitly indicating a physical uplink control channel, PUCCH, resource for sending the HARQ feedback, the resource bit pattern from the timing Bit pattern is present separately; andwherein the PUCCH resource is a time frequency resource and is selected by the resource selection indication from a pool of resources with which the UE is configured to be available for sending the HARQ feedback in the slot specified by the indication of the timing is specified.

Description

Technical field

This disclosure relates to wireless communication technology, particularly in the context of radio access technology / networks (RAT / RANs).

background

New wireless communication technologies, such as 5G technologies such as 3GPP New Radio, are currently in development and have been introduced for a wide range of use cases. To cover this wide field, greater flexibility in signaling is desirable, especially in control signaling.

Summary of the invention

An object of the present disclosure is to provide approaches that enable flexible transmission of an uplink control signaling or an acknowledgment signaling. In the context of this disclosure, acknowledgment signaling may be considered a form of uplink control signaling, and / or may be included and / or implemented therein or implemented separately. The uplink control signaling can include confirmation signaling, for example, in addition to planning issues and / or measurement reporting. Alternatively, the confirmation signaling can be implemented to only capture confirmation information by using an individual message.

According to the present disclosure, a user device (UE) and a network node according to independent claims 1 and 6 are provided. Preferred embodiments of the user device and the network node are specified in the respective dependent claims.

A user device, UE, for a radio access network is disclosed by way of example. The UE is set up to send an acknowledgment signaling relating to downlink data. The downlink data comprises one or more downlink data elements. The confirmation signaling has an uplink signaling format which comprises one or more confirmation substructures, each of the substructures carrying confirmation information relating to a downlink data element. Furthermore, each of the confirmation substructures is mapped to another one of the downlink data elements on the basis of at least one confirmation position specification, which is provided in a downlink control signaling received by the UE. The UE can comprise a processing circuit and / or a radio circuit, in particular a transmitter or a receiver, and / or can be set up to use the same for transmitting the confirmation signaling. Alternatively or additionally, the UE can comprise a transmission module for such transmission. It can be considered that the UE comprises a receiver and / or a receiving module for receiving downlink data and / or a downlink control signaling, for example from a network node.

A non-claimed method for operating a user device, UE, in a radio access network, which explains the present disclosure, is also disclosed. The method comprises sending an acknowledgment signaling that relates to downlink data, the downlink data comprising one or more downlink data elements. The confirmation signaling has an uplink signaling format which has one or more confirmation substructures, each of the substructures carrying confirmation information relating to a downlink data element. Furthermore, each of the confirmation substructures is mapped to another one of the downlink data elements on the basis of at least one confirmation position information, which is provided in a downlink control signaling received by the UE. The method may include receiving downlink data and / or downlink control signaling, for example from a network node.

For example, a network node for a radio access network can be considered. The network node is set up to send a downlink control signaling that includes a confirmation position indication. The confirmation position specification specifies a mapping of at least one confirmation substructure of an uplink signaling format, which comprises one or more confirmation substructures, to a corresponding data element of downlink data, the confirmation substructure being mapped to carry confirmation information that affect the downlink data element. The network node can comprise a processing circuit and / or a radio circuit, in particular a transmitter or a receiver, and / or can be set up to use the same for sending the confirmation signaling. Alternatively or additionally, the network node can comprise a transmission module for such transmission.

In addition, an unclaimed method for operating a network node in a radio access network that explains the present disclosure is disclosed. The process includes a Send downlink control signaling that includes an acknowledgment position. The confirmation position specification specifies a mapping of at least one confirmation substructure of an uplink signaling format, which comprises one or more confirmation substructures, to a corresponding data element of downlink data, the confirmation substructure being mapped to carry confirmation information that affect the downlink data element.

Sending the downlink control signaling may be sending to one or more than one UE. It can generally be considered that sending the downlink control signaling is an example and / or part of the configuration of the UE (s), in particular configuration on the physical layer and / or dynamic configuration.

Alternatively, a network node can be considered for a RAN, the network node being arranged to receive the acknowledgment signaling, which has an uplink signaling format described here. In some variations, the network node can be implemented as a network node that is set up to send the downlink control signaling described here. Regardless, a non-claimed method of operating a network node in a RAN illustrative of the present disclosure may be considered, the method comprising receiving the acknowledgment signaling having an uplink signaling format described herein. The method can include sending the downlink control signaling described here, in particular before receiving, and / or for configuring the confirmation signaling or the format. Receiving the acknowledgment signaling can be based on a corresponding configuration, which can be known to the network node, which can determine it itself (for configuring the UE) and / or can have received corresponding information from another network node and / or the UE. The network node can comprise and / or use a receiver and / or a receiving module for such receiving.

The proposed approaches enable flexible signaling to a UE, which substructure, for example a resource, is to be used for confirmation signaling. Thus, the confirmation signaling can be set up for a wide range of use cases and situations, which ensures reliable information. It should be noted that in the context of this disclosure, a single acknowledgment substructure in an uplink signaling format that is mapped to a single data element is considered to represent an image of each of the format's confirmation substructures to a different data element, if none Mapping of the substructure to more than a single data element (or vice versa) is present.

The confirmation substructures can be sent in the same message and / or the same format and / or coded and / or modulated together and / or sent on the same resources, which can be an uplink control signaling resource. Such a resource can be configured with the UE, for example in a resource pool. In particular, a resource and / or a resource pool can be preconfigured, for example before receiving the data elements and / or the downlink control signaling. The mapping described here can generally be viewed as mapping a data item (s) to different substructures sent on the same resource.

In general, the downlink control signaling and the downlink data can be sent on different channels, in particular different physical channels. The downlink signaling can be sent through a network node. The downlink control signaling may include downlink control information (DCI) and / or may be broadcast on one (or more than one shared or dedicated channel, for example a downlink control channel, for example a PDCCH (physical downlink control channel) or a shared one Channel or broadcast channel The downlink data may be broadcast on one (or more than one) shared or dedicated channel, for example a PDSCH (shared physical downlink channel).

The downlink control signaling can comprise a different message, for example different DCI messages, which were received in particular (by the UE) and / or were sent (by the network node) in different time structures or TTIs.

Confirmation information can represent confirmation or non-confirmation, for example the correct receipt of the corresponding data element, and can optionally represent an indication of non-receipt. In particular, the confirmation information can represent an ARQ (automatic repeat request) and / or a HARQ (hybrid automatic repeat request) feedback. Correct reception may include correct decoding / demodulation, for example according to an ARQ or HARQ process, for example based on error detection and / or forward error correction coding, which in turn may be based on the receipt of a data element. Accordingly, incorrect reception (non-confirmation) can refer to detection of an error during decoding / demodulation. A non-reception can indicate a non-reception of a data element and / or a non-reception of a confirmation position indication, which indicates an image relating to the data element. The non-reception can be indicated, for example, by a DTX (discontinuous reception) specification.

The confirmation position indication can choose between two or more different uplink signaling formats. A radio node can select the confirmation position information on the basis of a suitable uplink signaling format and / or be set up for selection. The uplink signaling formats can correspond to and / or be configured for specific uplink resources. For different configured (or planned) uplink resources, for example, different uplink signaling formats can be used and / or associated, for example depending on the size (in the time-frequency space, for example represented by resource elements) of the resource (s).

It can be considered that the confirmation position information indicates a time specification and / or a resource for sending the confirmation signaling. The timing may generally represent a time structure or interval used for transmission, for example a slot or a mini-slot or a shortened slot or the like, in particular a specific time structure or such an interval. The program can be provided within this time structure or this interval, for example at the beginning or at the end, but is not limited to this. Such a time structure or such an interval or a TTI can represent and / or comprise a multiplicity of symbols or resource elements (in time), or the associated time intervals, for example at least 2, at least 3, at least 4, at least 7 or at least 14 such time intervals, for example symbol time intervals. In general, the timing can be represented by a timing difference or time shift, for example between the timing of receipt of the confirmation position information and / or the data / data element (s) that it concerns and the intended or planned broadcasting time structure to Example of sending the corresponding confirmation signaling. In some variants, the time reference or time shift can be represented by a time value (for example in seconds or its subunits) or a time structure number, for example a difference in the slot number between reception and transmission. For example, such a difference can be an integer.

The downlink control signaling can comprise one or more messages, wherein each message can comprise at least one confirmation position indication. The message can be DCI messages, for example. Different messages can relate to different data elements and / or data that are provided on different downlink channels.

It can be considered that the confirmation position information relates to a single downlink data element. Different confirmation position information can relate to different data elements and / or can be included in different messages. In some variations, however, a message may include more than a single confirmation position information, and / or a confirmation position information may relate to more than a single data element. In the latter case, one-to-one maps of data elements to substructures can be provided by the specification.

In general, a single data element can be associated and / or mapped with each confirmation substructure. It can be considered that the mapping between data elements and confirmation substructures is a one-to-one mapping.

The confirmation position information may include a resource selection information, such as a resource selection parameter. The resource selection statement may indicate a resource for sending the confirmation statement, the resource being selected from a number of possible resources configured for confirmation signaling and / or uplink control signaling, for example on a PUCCH. For example, a resource selection parameter can be an ARI (ACK / NACK resource indicator). The resource can be a resource of a pool of resources that is repeatedly configured for a plurality of time structures or intervals, for example slots and / or mini-slots or shortened slots, so that the resources are available for each structure or interval of this plurality (mindful of the fact that these are shifted in time).

Alternatively or additionally, the confirmation position information can include an indication of a time specification, such as a time specification parameter, the specification of the time specification indicating a time specification for sending the confirmation signaling and also indicating to which confirmation A data element is mapped to a resource's substructure. The time specification can be present as described here, and can in particular be represented by a difference in the time structure or the interval, for example a difference in the slot or in the mini-slot or in the shortened slot, in particular between the slot of the reception, for example the confirmation position indication and / or the data element (s), and the time structure or interval (intended or specified or planned or configured) for transmission. It should be noted that the data element (s) and the corresponding confirmation position information can be sent (or received) in the same time structure or the same interval or in different time structures or intervals, depending on whether and / or how theirs respective channels are synchronized and / or timed. The specification of the time specification can be referenced (for example by the UE and / or the network node) to either-or (if differently fixed in time) or both-as-also (for example if defined at the same time). The reference can be defined and / or implied and / or configured by the standard. A timing parameter can be represented and / or implemented as a timing indicator.

In general, a timing may indicate a time interval, such as a slot or a mini-slot or a shortened slot for sending the acknowledgment signaling. A time structure or interval, as described here, can generally be represented by a slot and / or a mini-slot and / or a shortened slot and / or can be viewed as a representation of a transmission time interval (TTI).

A non-claimed program product is also disclosed that includes instructions that cause processing circuitry to perform and / or control any of the non-claimed methods described herein that explain the present disclosure.

Furthermore, a non-claimed carrier medium arrangement is disclosed which carries and / or stores a program product described here.

A statement, in particular a confirmation position statement, can explicitly and / or implicitly state the information that it represents and / or specifies. An implicit specification can be based, for example, on a position and / or a resource that is or will be used for the shipment. An explicit specification can be based, for example, on a parameterization with one or more parameters and / or an index or more indices and / or one or more bit patterns that represent or represent the information. In particular, an acknowledgment position specification can include a resource selection specification (for example an ARI) with a bit pattern of a single or more than one bit and / or a specification of the timing (for example a timing indicator) with a bit pattern of a single or more than one bit , This information can be combined with one another, for example coded together to represent a position or sent separately. Such a transmission can take place in the same message but with separate information, for example in accordance with a downlink control signaling format that can be defined by a standard.

Signaling on a resource and / or resource structure associated with a specific channel may be considered to include and / or relate to signals and / or symbols of the specific channel. For example, signaling on a PUCCH resource structure may include and / or relate to and / or associate with the PUCCH, whereas signaling on a PUSCH resource structure may include the PUCCH and / or the signaling of the PUCCH may and / or associated with the PUCCH. Thus the signaling on the PUCCH or a related resource structure is different from the signaling on a PUSCH.

The signaling can take place according to a specific signaling format, in particular according to an uplink signaling format. A signaling format can generally define and / or determine a message structure and / or a bit structure or pattern. Such a structure or pattern can comprise a plurality of substructures. A substructure can comprise a single or multiple bits. Different substructures can include different numbers of bits. In some variants, however, each acknowledgment substructure of a signaling format can comprise the same number of bits. A substructure can be uniquely associated with a data element and / or mapped uniquely on a data element. A multi-bit ( 2 or more) substructure can be used, for example, to provide the ability to indicate non-reception in addition to the ACK / NACK and / or error plugging and / or improved or more detailed ARQ / HARQ signaling. A substructure that carries information can comprise a single or multiple bits that represent or represent the information carried, for example ACK / NACK information.

Sending confirmation signaling may include coding and / or modulating, for example, the uplink signaling format and / or the substructures and / or the corresponding information or bits. The coding and / or modulation may include error detection coding and / or forward error correction coding and / or scrambling. An uplink format can represent a bit structure that comprises a plurality of bits that can be structured according to one or more substructures, for example confirmation substructures. A common coding and / or modulation can comprise that the jointly coded or demodulated information or bits are combined in the same coding, for example error coding (detection and / or error correction coding) and / or scrambling and / or modulation. Thus, jointly coded information can be protected by the same bits of error coding, or subjected to the same modulation and / or scrambling run.

A confirmation position indication can generally be considered to indicate a position of the depicted substructure in the uplink signaling format, for example a number and / or a range of bits and / or in relation to another substructure / other substructures. The information / bits in a substructure can generally indicate whether the receipt of the mapped / corresponding data element is acknowledged or not.

A resource can generally specify a time-frequency resource (or a range / ranges of time-frequency space), in particular a resource structure, for example a resource structure that comprises one or more resource elements. A resource can be part of a resource pool that includes one or a plurality of resources that can be configured (planned) for the uplink broadcast. Any resource can possibly be used for confirmation signaling. Different resources can be of different sizes, for example a range in frequency and / or spacetime. Different resources can be considered to affect or be planned for the same structure / TTI, for example for the same slot or mini slot or shortened slot. A resource pool can be configured for a variety of time structures / TTIs. The resource pool can be configured by the network node, or more generally by the RAN. A resource and / or a resource pool can be represented and / or configured according to a resource configuration, in particular an uplink control signaling configuration, which can in particular be a PUCCH configuration. A PUCCH configuration can represent resources for PUCCH signaling, in particular confirmation signaling on the PUCCH.

It can be considered that one or more different uplink signaling formats are or are associated with a resource and / or that different resources are associated with different uplink signaling formats. Different formats can differ with regard to the number of confirmation substructures and / or in the length (for example in bits) of the substructures. In some variations, an indication of a timing (in particular, a timing indicator indicating a time shift) can have or represent an integer value in a range that represents the number of different acknowledgment substructures in the uplink signaling format that affects them. If, for example, the format 3 Has confirmation substructures, the specification can represent values between 0 and 2 or between 1 and 3. A time shift can represent a shift in slots and can be referred to as a slot shift.

In general, the UE may select and / or set up a resource to send the acknowledgment signaling based on a configuration, for example an uplink control signaling resource configuration, particularly a PUCCH configuration. The network node can be set up to configure the configuration and / or configure the configuration. Such configuration can be done on the RRC layer, for example via RRC signaling, or can be considered static or semi-static (for example, it remains valid until it is changed by another RRC signaling, or a predefined one Plenty of time structures and / or ΠI covering), which can also be called permanent or semi-stable.

It can generally be considered that the acknowledgment signaling comprises a single uplink signaling format and / or a single message with such a format, and / or that the acknowledgment signaling or the format or the message or the bits in the Substructures for transmission, for example as part of the transmission, are coded and / or modulated together.

The sending of the confirmation signaling may include determining and / or based on confirmation information relating to the one or more data elements. Determining such information can be a Performing an ARQ and / or HARQ process and / or determining the correct receipt of the data elements (and / or mindful of a non-receipt). Alternatively or additionally, the sending of the confirmation signaling may include and / or be based on receiving the downlink data or the downlink data elements, for example based on a configuration which may be a downlink data configuration. Such a configuration can be configured by the network node. The configuration can (statistically and / or dynamically, for example partly both) be valid for one or more than one time structure or TTI. In some cases, however, the configuration can be dynamically adapted for each time structure or each TTI, for example as configured by a network node.

The confirmation signaling can be regarded as relating to the downlink data if it comprises confirmation information relating to the downlink data or its data element / data elements. The downlink data may represent general data sent on a downlink channel and may be the subject of one or more ARQ or HARQ operations, for example. A data element can in particular represent a (for example a single) data block (transport block) which is associated with a specific ARQ / HARQ process. In particular, different data elements can be associated with different HARQ / HARQ processes (which can run in parallel).

Data elements of the data can be sent by the network node and / or under the control or monitoring by the network node, which can be set up accordingly, and / or use its circuits accordingly and / or comprise a data transmission module therefor. In general, data elements can be associated with one or more different programs / transmitter events and / or messages, in particular programs at different times or different time structures or intervals, for example TTIs. The approaches described here enable flexible confirmation / HARQ feedback for the data elements that are received in different time structures / TTI. A UE can receive and / or set up the downlink data and / or the data elements, for example based on a configuration, and / or use their circuits for reception.

The confirmation signaling can be sent in or on a resource that is specified by the confirmation position specification, in particular a resource selection specification.

The PUCCH and / or a downlink control channel can be implemented as defined by a 3GPP standard, in particular according to LTE or NR according to the proposed change here.

A PUCCH can generally be a physical channel for sending uplink control signaling, for example UCI and / or HARQ signaling and / or measurement reports and / or planning requests.

A radio node can generally be viewed as a device or a node that is set up for wireless and / or radio (and / or microwave) frequency communication and / or for communication using an air interface, for example according to a communication standard.

A radio node can be a network node or a user device or a terminal. A network node can be any radio node of a wireless communication network, for example a base station and / or a gB node (gNB) and / or a forwarding node and / or a micro / nano / pico / femto node and / or other nodes, in particular for a RAN as described here.

The terms user device (UE) and terminal can be considered interchangeable in the context of this disclosure. A user device or a terminal can represent a device for communication using the wireless communication network and / or can be implemented as a user device according to a standard. Examples of user devices can be a telephone, such as a smartphone, a personal communication device, a mobile phone or terminal, a computer, such as in particular a laptop, a sensor or a machine with radio capability (and / or set up for the air interface), in particular for MTC (machine type communication , sometimes referred to as M2M, machine-to-machine) or a vehicle that is set up for wireless communication. A user device or a terminal can be mobile or stationary.

A radio node can generally comprise a processing circuit and / or a radio circuit. The circuit may include an integrated circuit. The processing circuit can include one or more processors and / or control devices (for example microcontrollers) and / or ASICs (application-specific integrated circuits) and / or FPGAs (field-programmable gate arrays) or the like. It can be considered that the Processing circuit comprises one or more memories or memory arrangements and / or is connected or can be connected to them (operable). A memory arrangement can comprise one or more memories. A memory can be set up to store digital information. Examples of memories include volatile and non-volatile memories, and / or random access memories (RAM) and / or read-only memories (ROM) and / or magnetic and / or optical memories and / or flash memories and / or hard disk memory and / or EPROM or EEPROM (erasable programmable ROM or electrically erasable programmable ROM). The radio circuit may include one or more transmitters and / or receivers and / or transceivers (which may operate as transmitters and receivers), and / or may include one or more amplifiers and / or oscillators and / or filters, and / or may include an antenna circuit and / or comprise one or more antennas and / or be connected or connectable to them.

Any or all of the modules disclosed herein can be implemented in software and / or firmware and / or hardware. Different modules can be associated with different components of a radio node, for example different circuits or different parts of a circuit. It can be considered that a module is distributed over different components and / or circuits.

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

list of figures

• 1 eine beispielhafte Abbildung der Signalisierung auf PUCCH-Ressourcen;
• 2 eine weitere beispielhafte Abbildung der Signalisierung auf PUCCH-Ressourcen;
• 3 eine weitere beispielhafte Abbildung der Signalisierung auf PUCCH-Ressourcen;
• 4 eine weitere beispielhafte Abbildung der Signalisierung auf PUCCH-Ressourcen;
• 5 ein beispielhaftes Endgerät oder eine beispielhafte UE;
• 6 einen beispielhaften Netzwerkknoten;
• 7 ein beispielhaftes, nicht beanspruchtes, die vorliegende Offenbarung erläuterndes Verfahren zum Betreiben eines Endgeräts oder einer UE;
• 8 ein beispielhaftes Endgerät oder eine beispielhafte UE;
• 9 ein beispielhaftes, nicht beanspruchtes, die vorliegende Offenbarung erläuterndes Verfahren zum Betreiben eines Netzwerkknotens; und
• 10 einen beispielhaften Netzwerkknoten.

The drawings are provided to illustrate the concepts and approaches described here and do not intend to limit their scope. Show it:

• 1 an exemplary mapping of the signaling on PUCCH resources;
• 2 another exemplary mapping of the signaling on PUCCH resources;
• 3 another exemplary mapping of the signaling on PUCCH resources;
• 4 another exemplary mapping of the signaling on PUCCH resources;
• 5 an exemplary terminal or an exemplary UE;
• 6 an exemplary network node;
• 7 an exemplary, non-claimed method for operating a terminal or a UE that explains the present disclosure;
• 8th an exemplary terminal or an exemplary UE;
• 9 an exemplary, non-claimed method of operating a network node illustrating the present disclosure; and
• 10 an exemplary network node.

Detailed description

Reference is made below to LTE technology for clarification and comparison. However, the approaches described here are not limited to this and can be applied to analog devices, structures and channels, for example in the context of the NR.

In 1 a DL program is shown in which a DL program is planned in slot n and the HARQ feedback is requested in slot n + 1. The UE may be configured accordingly, for example via the corresponding DCI, which may include a corresponding timing indicator.

In addition to the timing, the UE must also know the exact PUCCH resource to be used within slot n + 1. In LTE - depending on the PUCCH format - implicit and explicit signaling is used. For the PUCCH format 1a / 1b and 2 / 2a / 2 B implicit signaling is used, whereby the PUCCH resource is derived from the position of the planned PDCCH-CCE (in addition to the RRC-configured parameters). For other PUCCH formats, a pool of PUCCH resources is configured and an ACK / NACK resource indicator (ARI) is used to dynamically select one of the configured resources.

In view of the much higher flexibility of the PUCCH reporting system in the NR to be expected, it is questionable whether the main use of implicit signaling will not be very complicated and therefore possibly inefficient: if, for example, the HARQ feedback is used in two slots in different slots Slot reporting, they would use the same PUCCH resource if this is planned from the same PDCCH location (assuming a similar rule to LTE). To avoid such a collision, another PDCCH resource would have to be used, which is the Control channel planning limited. It can be considered to configure a pool of PUCCH resources, for example via RRC signaling, and to dynamically select which PUCCH resource to use. One possibility for this dynamic indication is the ACK / NACK resource indicator (ARI), which is included in the DCI.

In 2 Another planning example is shown in which a UE is planned in successive slots with DL broadcasts. Due to the lack of PUCCH opportunities (e.g. no UL opportunities), HARQ feedback is requested for all broadcasts shown in slot n + 3. 2 shows in particular a scenario in which a device (UE) is planned several times (for downlink data) and the HARQ feedback is to transmit for all transmissions in slot n + 3. The ACK / NACK timing indicator included in the DCIs points to slot n + 3 for all broadcasts. The ARIs included in the DCIs point to different PUCCH resources to avoid collisions.

While this works in principle, it may not be the most efficient solution. In the 2 In the example shown, the UE would have to send three independent PUCCH in the subframe n + 3, for example different messages. This is suboptimal in many ways: a single, 3-bit, jointly encoded broadcast (assuming that each HARQ feedback consists of a single bit) can be more efficient than 3 individual broadcasts; some of the NR-PUCCH formats will have a low PAPR that will be lost if multiple PUCCH are sent at the same time; depending on the frequency positions of the PUCCH resources, power reductions may be required due to intermodulation products.

It can be considered to allow HARQ feedback to be requested from DL broadcasts from different slots in a single PUCCH broadcast as in 3 is shown. All ARI in the received DCIs point to the same PUCCH resource (0 in this example). The PUCCH format must be able to carry several bits in different substructures. Accordingly, the HARQ feedback of multiple DL broadcasts is sent in a single PUCCH broadcast / message or is coded / modulated together (the PUCCH is broadcast entirely in slot n + 3).

If the UE misses a DL assignment (configuration), it is not aware that it should report the HARQ feedback and does not send ACK or NACK. Assume that the UE misses the assignment in slot n and receives the assignments in slots n + 1 and n + 3. The UE therefore only sends two feedback bits, one for slot n + 1 and one for slot n + 3. However, the gNB expects 3 bits (a single bit for each planned slot n, n + 1 and n + 3). If it only receives a single or 2 bits, then it does not know which DL transmissions the feedback corresponds to. The situation is only clear if a feedback with 3 bits or no feedback at all is received.

Thus, in one variation, the ACK / NACK timing indicators (T in the figures) included in the DCIs are used 1) to indicate in which slot the feedback is to be sent, and 2) to indicate one or as a pointer to a substructure within the PUCCH resource (or the associated uplink signaling format), which is specified by the ARI, with which subresource / substructure (for example bits in a bit map) the feedback is to be sent.

The error described above is thus avoided. Even if the UE misses some assignments (configurations or planned data), it is always clear which DL broadcast corresponds to a received HARQ feedback. This reduces the need for retransmissions and thereby improves throughput. Accordingly, the HARQ feedback message takes place according to the proposed solution (PUCCH resource 0 is sent completely in slot n + 3).

The ACK / NACK time indicator T indicates the slot in which the HARQ feedback of the corresponding DSL broadcast is to be sent. In the example, all DL programs are to be sent in slot n + 3. The T-value is different in the different slots because it is relative to the slot in which the DL data is received (in another variant it could be relative to the slot in which the DCI are received).

It is assumed here that the ACK / NACK timing indicator is received in the DCI and other possibilities can also be considered, for example the ACK / NACK timing indicator is derived from the slot or symbol number. Furthermore, in this example all DCI contain an ARI value of 0. From the ACK / NACK timing indicator T and the ARI, which the UE knows, it should use the PUCCH resource 0 in slot n + 3. The PUCCH resource indicated by the ARI must be a multi-bit resource, in the example shown the PUCCH resource 0 can carry four HARQ feedback bits (each in an associated bit field that represents a substructure).

From the ACK / NACK time specification indicator T, which the UE knows, it is intended to provide the HARQ feedback of the DSL broadcast received in slot n in bit field 3 should send the HARQ feedback of the DL broadcast received in slot n + 1 in bit field 2 and should send the HARQ feedback of the DL broadcast received in slot n + 3 in bit field 0. The unused bit position 1 would be set to a fixed value by the UE, for example a NACK. Even if the UE is scheduled but does not receive the schedule assignment (which the UE cannot distinguish from scheduling), it would set the corresponding bit positions to the same fixed value.

An extension would be that the UE does not set a bit position corresponding to a non-received transmission to NACK, but to DTX, which indicates that it received no assignment); in this way the gNB could distinguish between a received but incorrectly decoded broadcast and a broadcast that the UE did not even receive. In this case, however, the feedback is greater since each bit position can have the values ACK, NACK and DTX. In the simplest case, each "bit" position would be represented by 2 bits; in a preferred manner, however, the space of all 4 resources would be considered together: in the example described above, there can be 4 positions, and each position can take 3 values, a total of 3 ^ 4 = 81 combinations, which in total ceil * log2 (81 ) = 7 bits required.

In this example, the ACK / NACK timing indicator points directly to the bit in the bit field (or more generally to the PUCCH sub-resource within the PUCCH resource indicated by the ARI). More generally, the index to the PUCCH sub-resource is a function f (T) of the received ACK / NACK timing indicator.

In this example it is assumed that each DL broadcast is acknowledged with HARQ feedback of a single bit. However, this can easily be expanded if each DL program (data element) is acknowledged by a feedback with several bits (for example several bits for MIMO; if a DL program (transport block) is segmented into several code blocks and each code block or Group of code blocks can be individually recognized by one bit; a soft feedback if several bits indicate the degree to which the decoding was successful, in a range from ACK to almost ACK ... to NACK). Multiple bit feedback can be easily combined with the DTX specification described above.

At first glance, one might expect a power loss to occur because the PUCCH resource carries four bits, but only three-bit feedback is required in the example (since three shipments were planned / configured). However, the gNB knows which PUCCH sub-resources contain an ACK / NACK (or possibly DTX) (positions 0, 2, 3) and knows that a fixed value will be signaled at position 1. The gNB can take this into account in the decoding and may therefore only be able to decode in practice for 3 bits with little or no power loss.

In general, the ARI can be considered to choose from or between resources in a configured pool of PUCCH resources (for example, all PUCCH resources are of the same format or carry the same payload size). This concept can be expanded in such a way that the ARI can be a pointer to a selection between configured PUCCH resources of different formats or the payload: in the example in 4 the PUCCH resource 0 is able to carry 4 bits while the PUCCH resources 1 to 3 can only carry 1 bit at a time.

In the description, a separate ARI field and an indication of an ACK / NACK time specification are used to represent a confirmation position. However, it can be considered that the confirmation position indication is represented by a single indication, for example jointly coded information, so that, for example, both the ARI and the ACK / NACK timing indicator can be derived therefrom.

In general, it can be considered that the ACK / NACK timing indicator is reused to select a PUCCH sub-resource within the PUCCH resource pointed to by the ACK / NACK resource indicator (ARI). The concept of the ARI can be expanded so that the ARI can select configured PUCCH resources within a pool that are not the same (i.e. differ in either the format type or the supported payload).

5 schematically shows a terminal 10 that can be implemented as a UE (user device). The terminal 10 includes a processing circuit (which may also be referred to as a control circuit) 20 , which may include a controller connected to a memory. Any module of the terminal, for example a transmitter module or receiver module, can be in the processing circuit 20 be implemented and / or be executable by them, in particular as a module in the control device. The terminal 10 can also use a radio circuit 22 which provide functionality for receiving and transmitting or for transceiving (for example one or more transmitters and / or receivers and / or transceivers), the radio circuit 22 is connected or connectable to the control circuit. An antenna circuit 24 of the terminal 10 is with the radio circuit 22 connected or connectable to collect or transmit and / or amplify signals. The radio circuit 22 and the processing circuit 20 that it controls are configured for cell communication with a network, for example a RAN, as described here. The terminal 10 may be generally configured to perform any of the non-claimed methods of operating a terminal or UE disclosed herein that explains the present disclosure; in particular, it can comprise a corresponding circuit, for example a processing circuit and / or modules.

6 schematically shows a network node 100 , which in particular can be an eNB or a gNB or similar for the NR. The network node 100 includes a processing circuit (which may also be referred to as a control circuit) 120 , which can comprise a control device connected to a memory. Any module, for example a transmitter module and / or receiver module and / or a configuration module of the network node 100 can in the processing circuit 120 implemented and / or executable by this. The processing circuit 120 is connected, a radio circuit 122 of the radio node 100 to control, which in turn provides a transceiver and / or a transceiver functionality (for example, includes one or more transmitters and / or receivers and / or transceivers). An antenna circuit 124 can with the radio circuit 122 be connected or connectable for signal reception or transmission and / or amplification. The network node 100 may be configured to perform any of the non-claimed methods of operating a network node that are illustrative of the present disclosure described herein; in particular, it can comprise a corresponding circuit, for example a processing circuit and / or modules. The antenna circuit 124 can be connected to and / or comprise an antenna array. The network node 100 or its circuit can be set up to send configuration data and / or to configure a terminal as described here.

7 FIG. 12 shows a representation of an exemplary method for operating a terminal device or a user device that does not claim to explain the present disclosure. The procedure includes one measure TS10 for sending an acknowledgment signaling relating to downlink data, the downlink data comprising one or more downlink data elements; wherein the sending of the confirmation signaling is carried out as described here.

8th shows a schematic representation of an exemplary terminal or an exemplary user device. The user device can be a transmitter module TM10 to carry out the measure TS10 include.

9 FIG. 12 shows an illustration of an exemplary method for operating a network node that does not claim to explain the present disclosure. The procedure includes one measure NS10 for sending downlink control signaling that includes an acknowledgment position as described here.

10 shows a schematic representation of an exemplary network node. The network node can be a transmitter module NM10 to carry out the measure NS10 include.

In the context of this disclosure, HARQ-ACK / NACK (confirmation for a correctly received block of data, non-confirmation for an incorrectly received block of data) feedback may refer to feedback (for example, a corresponding transmitted signal that 1 or may include more bits) provided by a terminal (e.g. on the UL) e.g. on a network or a network node in response to data sent to it (e.g. on the DL). The HARQ-ACK / NACK information or feedback (or shorter HARQ-ACK information or feedback or HARQ information or feedback, or simply HARQ) may include sending a signal / bit indicating whether a transport block of data received by the terminal device has been correctly received or not. The HARQ and / or determining the HARQ may include decoding and / or error detection operations to determine correct reception. A number of HARQ processes can be defined with associated HARQ identifiers or numbers that can relate to individual data streams and / or associated data elements; a HARQ response or feedback from a terminal (e.g. a HARQ bit) can be associated with a single one of the HARQ events or identifiers. In a variant, the HARQ feedback can comprise a single bit per DL carrier; in another variant, the HARQ feedback can comprise two (or more than two) bits per carrier, for example depending on the rank used. In general, the HARQ Feedback is sent (and / or determined, for example based on received signals and / or transport blocks and / or data and / or HARQ process identifiers) by a terminal, and / or a terminal can be set up for and / or a HARQ module comprise for: determining (as described above, for example) and / or sending the HARQ feedback, in particular based on and / or using a configuration and / or a configured modulation, for example a modulation such as the one described here and / or determined is configured. The transmission of the HARQ can generally be carried out on a UL control channel, for example the PUCCH.

A non-claimed program product is generally contemplated that includes instructions that are configured to cause processing and / or control circuitry to perform and / or control any method described herein that is not claimed and that explains the present disclosure. especially when executed on the processing and / or control circuit. A non-claimed carrier medium arrangement is also considered, which carries and / or stores a program product described here.

A non-claimed carrier medium arrangement can comprise one or more carrier media. In general, a carrier medium can be accessible and / or readable and / or receivable by the control circuit. The storage of data and / or a program product and / or code can be viewed as part of carrying data and / or a program product and / or a code. A carrier medium can generally comprise a guidance / transport medium and / or a storage medium. A guidance / transport medium can be set up to carry and / or store signals, in particular electromagnetic signals and / or electrical signals and / or magnetic signals and / or optical signals. A carrier medium, in particular a guidance / transport medium, can be set up to carry such signals in order to carry them in turn. A carrier medium, in particular a guide / transport medium, can comprise an electromagnetic field, for example radio waves or microwaves, and / or optically conductive material, such as, for example, glass fiber, and / or a cable. A storage medium may include 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.

A wireless communication network can be and / or comprise a radio access network (RAN), which can be and / or comprise any type of cell and / or wireless radio network, which in turn is connected or connectable to a core network. The approaches described here are particularly suitable for a 5G network, for example LTE Evolution and / or NR (New Radio), or their successors. A RAN can include one or more network nodes. A network node can in particular be a radio node that is set up for radio and / or wireless and / or cell communication with one or more terminals. A terminal can be any device that is set up for radio and / or wireless and / or cell communication with or within a RAN, for example a user device (UE) or a mobile phone or a smartphone or a computer device or an in-vehicle communication device or a machine type communication (MTC) device, etc. A terminal may be mobile or, in some cases, stationary.

The transmission in the downlink can relate to a transmission from the network or network node to the terminal. Sending in the uplink can relate to the transmission from the terminal to the network or network node.

The signaling can generally comprise one or more signals and / or one or more symbols. The reference signaling can comprise one or more reference signals or symbols.

A resource element can generally describe a smallest individually usable and / or encodable and / or decodable and / or modulatable and / or demodulatable time-frequency resource, and / or can describe a time-frequency resource that has a symbol time length in time and a subcarrier in time Frequency covers. A signal can be allocated and / or allocated to a resource element. A subcarrier can be a subband of a carrier, as defined, for example, in a standard. A carrier can be a frequency and / or a frequency band for transmission and / or reception. In some variations, a signal (encoded / modulated together) can cover more than one resource element. A resource element can generally exist as defined by a corresponding standard, for example NR or LTE.

A sub-resource generally represents a time-frequency resource on which signaling according to a specific format can be transmitted and / or provided for transmission. The format may include one or more substructures that can be considered to represent a corresponding sub-resource (since they would be sent in part of the resources).

The expression transmission time interval (TTI) can be any time span ( T0 ), via which a physical channel can be coded and optionally nested to the broadcast. The physical channel can be used by the receiver over the same period of time ( T0 ) are decoded, via which it was encoded. Examples of the TTI include a short TTI (sTTI), a transmission time, a slot, a sub-slot, a mini-slot, a mini-subframe, etc. A TTI can include one or more symbol time intervals and / or one or two slot time intervals, for example 7 symbol time intervals one slot time interval can correspond. Time interval related expressions can be considered sufficient as the 3GPP nomenclature. A mini slot or shortened slot or short TTI may correspond to a variety of symbol time intervals, for example 2 or 3 or 4 or 5 or 6 or 7 symbol time intervals.

The configuration of a radio node, in particular a terminal or a user device, can relate to the fact that the radio node is set up or caused or set in order to be operated in accordance with the configuration. The configuration can be performed by another device, for example a network node (for example a radio node of the network if the base station or eB node) or network, in which case it can include sending configuration data to the radio node to be configured. Such configuration data can represent the configuration to be configured and / or comprise one or more instructions relating to a configuration, for example with regard to a freeze interval and / or a transmission time interval. A radio node can configure itself, for example based on configuration data received from a network or network node. A network node can use its circuitry / circuits for configuration and / or be set up for its use.

In general, the configuration may include determining configuration data representing the configuration and providing it to one or more other nodes (in parallel and / or sequentially), which it continues to the radio node (or another node, which can be repeated until) it can reach the wireless device). Alternatively or additionally, configuring a radio node, for example by a network node or other device, may include receiving configuration data and / or data relating to the configuration data, for example from another node, such as a network node, which is a higher level node Network, and / or sending received configuration data to the radio node. Accordingly, the determination of a configuration and the sending of the configuration data to the radio node can be carried out by different network nodes or functional units, which may be able to communicate via a suitable interface, for example an X2 interface in the case of LTE or a corresponding interface for NO. The configuration of a terminal can include planning of downlink and / or uplink transmissions for the terminal, for example downlink data and / or downlink control signaling and / or DCI and / or uplink signaling, in particular confirmation signaling, and / or configuring resources and / or a resource pool therefor.

In this disclosure, for purposes of description but not limitation, specific details (such as certain network functions, operations, and signaling steps) are set forth to ensure a thorough understanding of the technique described herein. It is obvious to the person skilled in the art that the present concepts and aspects can be implemented in other variants and variants deviating from these specific details.

For example, the concepts and variants are partially described in the context of long-term evolution (LTE) or LTE-Advanced (LTE-A) or Next Radio mobile or wireless communication technologies; however, this does not preclude the use of the present concepts and aspects in connection with additional or alternative mobile communication technologies, such as the global system for mobile communication (GSM). While the following variants are partially described in terms of certain technical specifications (TSs) of the third-generation partnership project (3GPP), it can be seen that the concepts and aspects available can also be implemented in connection with different performance management (PM) specifications.

It will also be apparent to those skilled in the art that the services, functions, and steps described herein can be implemented using software that runs in conjunction with a programmed microprocessor, or using an application specific integrated circuit (ASIC), one digital signal processor (DSP), a field programmable gate array (FPGA) or a general purpose computer. It is also evident that while the variants described here have been explained in the context of the methods and devices not claimed, the concepts and aspects described here can also be stored in a program product and in a system that includes the control circuit, for example a computer processor and a memory connected to the processor, the memory encoded with one or more programs or program products that perform the services, functions, and steps disclosed herein.

Having considered this description, the advantages of the aspects and variants described herein are fully apparent from the foregoing description, and it is apparent that various changes in the form, structures, and arrangement of the exemplary aspects of the description can be made without departing from the scope to deviate from the concepts and aspects described here or to abandon all their beneficial effects. The aspects described here can be varied in many ways.

Abkürzung

Erklärung

ACK

Bestätigung

ARI

ACK/NACK-Ressourcenindikator

CCE

Steuerkanalelement

DCI

Downlink-Steuerinformationen

DL

Downlink

DTX

diskontinuierliche Sendung

HARQ

hybride automatische Wiederholungsanforderung

MIMO

mehrfacher Eingang, mehrfacher Ausgang

NACK

negative Bestätigung

PAPR

Spitzen-zu-mittlere-Leistung-Verhältnis

PDCCH

physikalischer Downlink-Steuerkanal

PUCCH

physikalischer Uplink-Steuerkanal

RRC

Funkressourcensteuerung

UL

Uplink

Some useful abbreviations include:

abbreviation

Explanation

ACK

confirmation

ARI

ACK / NACK resource indicator

CCE

Control channel element

DCI

Downlink control information

DL

downlink

DTX

discontinuous broadcast

HARQ

hybrid automatic repeat request

MIMO

multiple entry, multiple exit

NACK

negative confirmation

PAPR

Peak mean to-performance ratio

PDCCH

physical downlink control channel

PUCCH

physical uplink control channel

RRC

Radio Resource Control

UL

uplink

Claims (10)

User equipment, UE, (10) for a New Radio, NR, radio access network, the UE comprising: a processing circuit (20), the UE configured to use the processing circuit to send a hybrid automatic retry request, HARQ, feedback relating to downlink data sent on a shared downlink physical channel, PDSCH , the downlink data comprising at least one downlink data element, the HARQ feedback having an uplink signaling format comprising at least one acknowledgment substructure, each of the substructures carrying confirmation information relating to a downlink data element, each the confirmation substructure is mapped to another one of the downlink data elements on the basis of at least one confirmation position indication, which is provided in a downlink control signaling received by the UE; wherein the acknowledgment position includes an indication of a timing, the indication of the timing comprises a timing bit pattern of more than one bit that explicitly indicates a slot for sending the HARQ feedback, the slot comprising at least 14 symbol time intervals; wherein the acknowledgment position indication further comprises a resource selection indication comprising a resource bit pattern, the resource bit pattern comprising more than one bit and explicitly indicating a physical uplink control channel, PUCCH, resource for sending the HARQ feedback, said resource Bit pattern is separate from the timing bit pattern; and wherein the PUCCH resource is a time-frequency resource and is selected by the resource selection specification from a pool of resources with which the UE is configured to be available for sending the HARQ feedback in the slot specified by the specification of the timing is specified. UE according to Claim 1 , the confirmation position indication selecting between two or more different uplink signaling formats. UE according to Claim 1 or 2 , wherein the downlink control signaling comprises at least one message, each message comprising at least one confirmation position indication. UE according to Claim 1 or 2 , wherein the downlink control signaling comprises at least one message, each message representing at least one of a group consisting of a planning assignment and a downlink control information, DCI, message. UE according to one of the Claims 1 to 4 , the downlink data elements comprising at least one from a group consisting of transport blocks and code block groups. A network node (100) for a New Radio, NR, radio network, the network node comprising a processing circuit (120) and configured to use the processing circuit (120) to: send downlink control signaling to a user device, UE, (10); send downlink data to the UE on a shared physical downlink channel, PDSCH, comprising at least one downlink data element; and receive a hybrid automatic retry request, HARQ, feedback from the UE relating to the downlink data, the HARQ feedback having an uplink signaling format comprising at least one acknowledgment substructure, each of the substructures carrying acknowledgment information that relate to a downlink data element, wherein each of the confirmation substructures is mapped to another one of the downlink data elements on the basis of at least one confirmation position indication that is provided in the downlink control signaling, the confirmation position indication an indication of a The timing includes a timing bit pattern of more than one bit that explicitly specifies a slot for sending the HARQ feedback, the slot comprising at least 14 symbol time intervals, the acknowledgment position also comprising a resource selection indication , the A Comprises resource bit pattern, the resource bit pattern comprising more than one bit explicitly indicating an uplink physical control channel, PUCCH, resource for sending the HARQ feedback, the resource bit pattern being separate from the timing bit pattern, and wherein the PUCCH resource is a time-frequency resource and is selected by the resource selection specification from a pool of resources with which the UE is configured to be available for sending the HARQ feedback in the slot specified by the specification of the timing is specified. Network node according to Claim 6 , the confirmation position indication selecting between two or more different uplink signal formats. Network node according to Claim 6 or 7 , wherein the downlink control signaling comprises one or more messages, each message comprising at least one confirmation position indication. Network node according to Claim 6 or 7 , wherein the downlink control signaling comprises at least one message, each message representing at least one of a group consisting of a planning assignment and a downlink control information, DCI, message. Network node according to one of the Claims 6 to 9 , the downlink data elements comprising at least one from a group consisting of transport blocks and code block groups.

Images