Adaptive transport format uplink signaling for data-non-associated feedback control signals
12 claims: 4 independent, 8 dependent
- 1User equipment for long term evolution operation, comprising:a decoder (426), responsive to a dynamic transport format control signal from a base station indicative of a dynamically selected transport format, for decoding said control signal for providing a decoded signal indicative of said dynamically selected transport format for use in data-non-associated uplink feedback control signaling (104);and an encoder (436), responsive to said decoded signal, for encoding data-non-associated uplink feedback information according to said dynamically selected transport format for transmission to the base station using the selected transport format (106).
- 4A base station for long term evolution operation, comprising:an encoder (420), responsive to dynamically selected transport format component signals and to a data signal, for encoding said transport format component data-non-associated signals and said data signal for providing a dynamic transport format control signal for transmission from said base station to user equipment, said control signal indicative of a dynamically selected transport format for data-non-associated uplink signaling used by said user equipment;and a decoder (456), responsive to said data-non-associated uplink signaling, for decoding feedback information according to said dynamically selected transport format.
- 7A method for use in long term evolution operation comprising:decoding (426), responsive to a dynamic transport format control signal from a base station indicative of a dynamically selected transport format, said control signal for providing a decoded signal indicative of said dynamically selected transport format for use in data-non-associated uplink feedback control signaling (104);and encoding (436), responsive to said decoded signal, data-non-associated uplink feedback information according to said dynamically selected transport format for transmission to the base station using the selected transport format (106).
- 10A method for use in long term evolution operation comprising:encoding (420), responsive to dynamically selected transport format component data-non-associated signals and to a data signal, said transport format component signals and said data signal for providing a dynamic transport format control signal for transmission to user equipment, said control signal indicative of a dynamically selected transport format for data-non-associated uplink signaling used by said user equipment;and decoding (456), responsive to said data-non-associated uplink signaling, feedback information according to said dynamically selected transport format.
Independent claims4
62 paragraphs in 4 sections, as filed
BACKGROUND OF THE INVENTION
1.Technical Field
0001The invention relates to improving uplink feedback signaling.
2. Discussion of Related Art
Abbreviations
0002<dl id="dl0001" compact="compact"><dt>3GPP</dt><dd>Third generation partnership program</dd><dt>A/N</dt><dd>ACK/NACK</dd><dt>ACK</dt><dd>Acknowledgement</dd><dt>BER</dt><dd>Bit Error Ratio</dd><dt>BLER</dt><dd>Block Error Ratio</dd><dt>BPSK</dt><dd>Binary Phase Shift Keying</dd><dt>CM</dt><dd>Cubic Metric</dd><dt>DL</dt><dd>Downlink</dd><dt>CQI</dt><dd>Channel Quality Indicator</dd><dt>CRC</dt><dd>Cyclic Redundancy Check</dd><dt>ECR</dt><dd>Effective Coding Rate</dd><dt>EDCH</dt><dd>Enhanced Dedicated Channel</dd><dt>ENSR</dt><dd>Estimated Signal to Noise Ratio</dd><dt>FB</dt><dd>Feedback</dd><dt>HARQ</dt><dd>Hybrid Automatic Repeat Request</dd><dt>LTE</dt><dd>Long Term Evolution</dd><dt>MCS</dt><dd>Modulation and Coding Scheme</dd><dt>MIMO</dt><dd>Multiple-Input Multiple-Output</dd><dt>NACK</dt><dd>Negative ACK</dd><dt>PAPR</dt><dd>Peak to Average Power Ratio</dd><dt>PAR</dt><dd>Peak-to-average ratio</dd><dt>PUSCH</dt><dd>Physical Uplink Shared Channel</dd><dt>QAM</dt><dd>Quadrative Amplitude Modulation</dd><dt>QoS</dt><dd>Quality of Service</dd><dt>QPSK</dt><dd>Quadrative Phase-Shift Keying</dd><dt>RRC</dt><dd>Radio Resource Control</dd><dt>RU</dt><dd>Resource Unit</dd><dt>SDMA</dt><dd>Space Division Multiple Access</dd><dt>SIMO</dt><dd>Single-Input Multiple-Output</dd><dt>SINR</dt><dd>Signal-to-Interference and Noise Ratio</dd><dt>SNR</dt><dd>Signal-to-Noise Ratio</dd><dt>TDM</dt><dd>Time Division Multiplexing</dd><dt>TFCI</dt><dd>Transport Format Combination Indicator</dd><dt>TFC</dt><dd>Transport Format Combination</dd><dt>TTI</dt><dd>Transmission Time Interval</dd><dt>UL</dt><dd>Uplink</dd><dt>UTRAN</dt><dd>Universal Terrestrial Radio Access Network</dd><dt>VoIP</dt><dd>Voice over Internet Protocol</dd></dl>
0003This invention arose in the context of developments underway in the UL part of UTRAN long term evolution (LTE) often referred as 3.9G but is not limited to that context.
0004For UMTS, multicodes are used for both the control and data channels and such is not available in LTE due to bad PAPR. The signaling has to be transmitted as inband signaling with the data transmission.
0005MOTOROLA: "Multiplexing of Uplink Control Signaling with Data", 3GPP DRAFT; RI-070777 discusses about puncturing of the data to accommodate control signaling. This document teaches that the repetition and modulation selection are performed according to information about the channel. This selection can be tied to the modulation and coding scheme (MSC) of the data block. The block error ratio (BLER) target of the UL data channel may vary quite a lot, depending on many issues and parameters: Different services will have different QoS requirements (e.g., delay performance, BLER). Therefore, it is difficult to provide sufficient quality for control signals if the transport format of data-non-associated control is tied only to the modulation and coding scheme (MCS) used by UL data.
0006D2 NOKIA: "One TFC for signalling on HR channels", 3GPP DRAFT; GP-040944 discusses about use of transport channels when only one signalling TFC is used.
0007More particularly, the invention arose during consideration of resource allocation for non-data-associated control signals transmitted with UL data on the PUSCH (Physical Uplink Shared Channel). These control signals include ACK/NACK due to the DL transmission and CQI reporting which can be either periodic or scheduled.
0008In RAN1#46bis, it has been agreed that data non-associated uplink control signaling is to be multiplexed with UL data with time division multiplexing (TDM). Detailed operations have not been discussed yet in 3GPP.
0009As suggested above, although the invention is not limited to the specific context in which it arose, it proceeds from consideration of the basic problem of how to divide the available physical resources (i.e., symbol space and transmission power) between data-non-associated control and data channels in LTE UL system. Information about the symbol space division must be pre-known at both ends of the radio link in order to perform correct rate matching/de-matching and encoding/decoding operations for different channels. Although not limited to such a scenario, it is noted that in the LTE UL system, the eNode-B (base station) has to be in charge of the resource split between the control and data parts and signaling this information to the UE. This is mainly due to the following things: <ul id="ul0001" list-style="bullet" compact="compact"><li>Data-associated control signaling is not supported in LTE UL. Therefore UE cannot signal transport format indication to the eNode B.</li><li>Blind detection is not feasible in UL, not only from the receiver complexity point of view but also taking into account the fact that CRC may not be available so there is no handy criterion on which to base the decision which of multiple possible formats was actually transmitted.</li></ul>
0010A second problem is how to optimize the performance of data-non-associated control signaling. It is noted that power control will set the SINR target of PUSCH according to the data channel. Therefore, the control channel has to adapt to the SINR operation point set for data. Control signals have typically much tighter delay requirements. Furthermore, control signaling benefits neither from the fast link adaptation nor the HARQ. Therefore the coding for data-non-associated control signaling needs to be done with somewhat more margin.
0011A third problem is relates to different performance requirements of UL data and control signals. <ul id="ul0002" list-style="bullet" compact="compact"><li>ACK/NACK BER should be about 0.1% (no HARQ)</li><li>CQI BLER should typically be less than 10% (no HARQ)</li><li>BLER of UL data channel(s) varies usually between 10% and 30% (depending on the HARQ operation point).</li></ul>
0012One way to adjust the available resources between control and data parts is to apply different power offset values for them. There are two main disadvantages regarding this power offset method: <ul id="ul0003" list-style="bullet" compact="compact"><li>PAR problem: It has been shown in [R1-072224] that PAR and CM are increased when higher power is configured for control rather than for data. [R1-072224] recommends that the control power should be limited not to exceed the data power. Furthermore, it is not possible to increase the Tx power of control signaling, when the UE is transmitting with full power (i.e., located at the cell edge). So power increase is inefficient in providing adequate quality in several cases in practice.</li><li>It is also noted that from resource utilization point of view, power reduction is not too economic since all the available power resources won't be utilized any more. This is equivalent to a waste of capacity.</li></ul>
0013Rl-071000 presents another prior art technique, where the symbol space of data-non-associated control channels is tied to the data modulation used by UL data channel. This is simply a consequence of the fact that the number of bits that is conveyed with a symbol depends on the data modulation: QPSK, 16QAM and 64 QAM carry 2, 4 and 6 bits respectively, therefore the number of symbols needed to carry a given number of bits from coding of data-non-associated control signaling depends on the modulation used. The applied symbol space corresponding to different data modulations is signalled to the UE by means of higher layer signalling (RRC signalling).
0014A problem related to this technique is that it is unable to guarantee the QoS of the data-non-associated control signaling. It is noted that the BLER target of the UL data channel may vary quite a lot, depending on many issues and parameters: <ul id="ul0004" list-style="bullet" compact="compact"><li>Different services will have different QoS requirements anyway (e.g., delay performance, BLER). Therefore, it is problematic to tie the symbol space of data-non-associated control channel only for the MCS used by UL data.</li><li>Performance of data-non-associated control signalling depends not only on the SINR but also the number of RUs allocated for UL data. For that reason, the symbol space allocated for the control channel should vary also according to the bandwidth.</li></ul><ul id="ul0005" list-style="bullet" compact="compact"><li>Propagation environment may change quite rapidly. RRC signaling may not be able to track these changes fast enough.</li><li>Feasibility of this method depends also on the UL HARQ scheme (adaptive vs. non-adaptive)</li></ul> Therefore, it is difficult to provide sufficient quality for control signals if the symbol space of data-non-associated control is tied only to the modulation and coding scheme (MCS) used by UL data. The disclosure that follows deals with transport format selection of data-non-associated control signals transmitted with UL data. Also disclosed are some special, non-limiting cases of transport format selection for UL data transmission.
SUMMARY OF THE INVENTION
0015The scope of the invention is defined by the appended claims.
0016According to a first aspect of the present invention, a method for use in long term evolution operation is provided comprising dynamically selecting a symbol space for data-non-associated uplink feedback control signaling, and sending the selected uplink feedback control signaling using the selected symbol space. According to a second aspect of the present invention, user equipment for long term evolution operation is provided, comprising a decoder, responsive to a dynamic transport format control signal from a base station indicative of a dynamically selected transport format, for decoding said command signal for providing a decoded signal indicative of said dynamically selected transport format for use in data-non-associated uplink feedback control signaling, and an encoder, responsive to said decoded signal, for encoding feedback information according to said dynamically selected transport format for transmission to the base station using the selected transport format.
0017According to the third aspect of the present invention, a base station for long term evolution operation is provided, comprising an encoder, responsive to dynamically selected transport format component signals and to a data signal, for encoding said transport format component signals and said data signal for providing a dynamic transport format control signal for transmission from said base station to user equipment, said control signal indicative of a dynamically selected transport format for data-non-associated uplink signaling used by said user equipment, and a decoder, responsive to said data-non-associated uplink signaling, for decoding feedback information according to said dynamically selected transport format.
0018According to a fourth aspect of the present invention, a system is provided comprising user equipment according to the second aspect of the invention and a base station according to the third aspect of the invention.
0019According to a fifth aspect of the present invention, a computer program product is provided in which a program code is stored in a computer readable medium, said program code realizing the following when executed by a processor (a) dynamically selecting a symbol space for data-non-associated uplink feedback control signaling, and (b) sending the selected uplink feedback control signaling using the selected symbol space.
0020According to a sixth aspect of the present invention, apparatus is provided comprising means for dynamically selecting a symbol space for data-non-associated uplink feedback control signaling, and means for sending the selected uplink feedback control signaling using the selected symbol space.
0021The present invention provides a method for selecting the transport format combination (TFC) of control signals transmitted with UL data (PUSCH). It also provides a signaling scheme to support the current transport format selection method. It also provides some methods to control the transport format used by a shared data channel.
0022The invention teaches to select the coding and in particular the amount of symbols used for coding of the inband control information on, e.g., a PUSCH to achieve a targeted BLER for signaling and data which are typically different. By means of the invention signaling is reduced to a minimum level.
0023It is to be understood that all presented exemplary embodiments may also be used in any suitable combination.
Advantages:
0024The main advantage of this invention is that physical UL resources can be utilized in a more efficient way. This is due to the fact that if only semi-static control is available overhead caused by data-non-associated control signalling cannot be optimized too accurately. Instead of that, the control channel resources are configured in such a way to be on the safe side, in terms of QoS of control signalling (this leads to higher overhead). Using the scheme disclosed in detail below, the QoS of data-non-associated control signalling transmitted with UL data can be adjusted and optimized in a flexible, fast and efficient way.
0025It is noted that in different scenarios, there are also other reasons than just the QoS aspect to change the format of data-non-associated control signalling dynamically. TFCI bit(s) can be used in many ways: <ul id="ul0006" list-style="bullet" compact="compact"><li>They can be used to select between optimized SIMO and MIMO configurations</li><li>They can be used to select some kind of "air-bag" configuration for data-non-associated control signalling (which has the best possible quality). Such a configuration can be selected e.g. by the base station, if there is risk that crucial control information is getting lost in UL and that would compromise DL performance e.g. due to insufficient knowledge of the UL channel quality. Such cases may occur for data bursts after some time of inactivity, if no dummy data exchange is done during the time of inactivity in order to save power. Due to the missing data exchange, the base station has neither up to date knowledge any more about the DL nor the UL channel quality. Once new data arrive e.g. for DL. it is essential to quickly get reliable CQI to be able to schedule these data efficiently. However, because the UL channel quality is not known as well, it is desirable to select a configuration for the UL control information that is on the safe side. This may waste some UL capacity, but allows to achieve a better DL capacity and quality of service.</li><li>They can be used to dynamically select between different CQI sizes (pre-allocated for certain CQI reporting scheme), e.g., based rapid changes in propagation environment</li></ul>
0026These advantages are not exhaustive of the possible advantages of the present invention.
0027Disadvantages: <ul id="ul0007" list-style="bullet" compact="compact"><li>Additional signalling burden (1-3 bits) related to UL allocation grant signalling</li></ul>
0028Other objects and features of the present invention will become apparent from the following detailed description considered in conjunction with the accompanying drawings. It is to be understood, however, that the drawings are designed solely for purposes of illustration and not as a definition of the limits of the invention, for which reference should be made to the appended claims. It should be further understood that the drawings are not drawn to scale and that they are merely intended to conceptually illustrate the structures and procedures described herein.
BRIEF DESCRIPTION OF THE FIGURES
0029<dl id="dl0002" compact="compact"><dt>Fig. 1</dt><dd>is a flowchart illustrating a process that may be carried out in user equipment, according to the present invention;</dd><dt>Fig. 2</dt><dd>is a flowchart illustrating a process that may be carried out in a base station, according to the present invention.</dd><dt>Fig. 3</dt><dd>illustrates a general purpose signal processor which may be used in the user equipment to carry out the process of <figref idref="f0001">Fig. 1</figref> or in the base station to carry out the process of <figref idref="f0001">Fig. 2</figref>, or both.</dd><dt>Fig. 4</dt><dd>shows an example of a scenario in which the present invention may be employed where a base station dynamically decides the symbol space to be used by user equipment in its feedback signaling included in an uplink that also includes uplink data.</dd></dl>
DETAILED DESCRIPTION OF THE INVENTION
0030<figref idref="f0001">Figure 1</figref> is a flowchart illustrating a process that may be carried out in user equipment, according to the present invention. The process may be carried out by any kind of signal processing. After entering in a step 100, a step 104 is executed to dynamically select symbol space to be used for uplink signaling such as for data-non-associated uplink feedback control signaling. In a step 106, the process 100 then causes the user equipment to send the uplink feedback control signaling using the selected symbol space. The process then returns in a step 108.
0031<figref idref="f0001">Fig. 2</figref> shows a process 200 that may be carried out in a base station, according to the present invention. After entering in a step 202, a step 204 is executed to dynamically select a symbol space to be used for uplink signaling such as for data-non-associated uplink feedback control signaling. In a step 210, the process 200 then causes the base station to send the uplink feedback control signaling to the user equipment in a downlink to command it to use the selected symbol space. Not shown is a step where the base station may store the selected symbol space for future reference when receiving the uplink signaling from the user equipment. The process then returns in a step 220.
0032Thus, although the step 104 of <figref idref="f0001">Fig. 1</figref> could be decided by the user equipment on its own, <figref idref="f0001">Fig. 2</figref> shows that the symbol space selection may actually be commanded to the user equipment in a preceding signaling step 210 by the base station. In that case, the step 104 of <figref idref="f0001">Fig. 1</figref> represents the UE selecting the symbol space in response to the control signaling sent in the preceding step 210 of <figref idref="f0001">Fig. 2</figref>.
0033<figref idref="f0001">Fig. 3</figref> illustrates a general purpose signal processor which may be used in the user equipment to carry out the process 100 of <figref idref="f0001">Fig. 1</figref>. Such a processor includes a CPU, RAM, ROM, an input/output port, a clock, and miscellaneous other components all interconnected by data, address and control lines and may also be used in the base station to carry out the process 200 of <figref idref="f0001">Fig. 2</figref>. If software is used to carry out the process 100 or the process 200, it may be in the form of coded instructions embodied in a computer readable medium. It should be understood however that either or both of these processes 100, 200 may instead be carried out by other kinds of processors including but not limited to dedicated hardware such as an integrated circuit.
0034<figref idref="f0002">Fig. 4</figref> shows a non-limiting example of a scenario in which the present invention may be employed where a base station 402 dynamically selects the symbol space to be used by user equipment 404 in its feedback signaling included in an uplink 406 that also includes uplink data. Such signaling is carried on a so-called data-non-associated control or signaling channel of the uplink 406. A selector (not shown but that may take the form of the processor of <figref idref="f0001">Fig. 3</figref>) in the base station dynamically selects the symbol space (according to step 204 of <figref idref="f0001">Fig. 2</figref>) to be used along with some related parameters to be commanded to the user equipment for the user equipment to use in connection with the uplink signaling channel on the uplink 406. Such might include for instance an input size signal on a line 410, an encoding scheme signal on a line 412, as well as a symbol space signal on a line 414. Such signals are provided as shown generally on a line 416 to an encoder along with data on a line 418 to an encoder 420. In carrying out step 220 of <figref idref="f0001">Fig. 2</figref>, the encoder provides an output signal on a line 421 in which the data is combined with the signaling 410, 412, 414 for transmission via an antenna on a downlink 422 to the user equipment 404. Upon reception by an antenna 423 in the user equipment, a received downlink signal on a line 424 is provided to a decoder 426 in the UE 404. It decodes the data previously encoded on the line 418 and provides a decoded data signal on a line 428 for use in the UE 404. The decoder also provides a sensed signal on a line 430 indicative of the quality of the downlink. A measurement thereof may be made in a measurement component 432 that then provides a channel quality indicator (feedback) signal on a line 434 to an encoder 436. The decoder 426 also provides a command signal on a line 438 to the encoder 436 having information contained therein at least indicative of the symbol space information sent from the base station and possibly also the other information contained on the line 416. The encoder then carries out steps 104, 106 of <figref idref="f0001">Fig. 1</figref> to dynamically select and use the symbol space for data-non-associated uplink signaling. If the decoded data on the line 428 is received correctly, an ACK signal is sent to the encoder 436 on the line 440. Otherwise, a NACK may be sent. Signal data intended for the uplink is provided on a line 442 to the encoder 436 and combined with the CQI and ARQ information for output on a line 450 from the encoder 436 to an antenna for transmission on the uplink 406 to the base station. A decoder 456 in the base station uses the uplink CQI signal 434 to help carry out step 204 for the next dynamic selection of the symbol space for the data-non-associated uplink feedback control signaling to be used on the uplink 406.
Transport format selection scheme
0035In the illustrated embodiment, the transport format configuration of data-non-associated control channels 434, 440 transmitted with UL data 442 is divided into two parts, (1) a semi-static part and (2) a dynamic part.
Semi-static part
0036The semi-static part is used to configure possible transport formats for data-non-associated control channels. It is possible to configure TFCs in such a way that different control signals (e.g., CQI) have <ul id="ul0008" list-style="bullet"><li>different symbol space allocation (i.e. number of output bits of encoder 436) with different TFCs</li><li>different number of input bits (i.e., CQI encoding scheme) with different TFCs. It is also possible to configure such a TFC in which the CQI message is not transmitted at all (zero CQI bits) .</li></ul>
Dynamic control part
0037Dynamic parameters are used to select one of several predefined transport format combinations for each MCS for data-non-associated control signals transmitted with UL data.
Transport format selection
0038In the illustrated embodiment, eNode-B selector selects the actual transport format combination based on <ul id="ul0009" list-style="bullet" compact="compact"><li>Service requirements related to UL data channel (e.g., BLER operation point)</li><li>Bandwidth allocation of UL data channel (i.e., how many resource units)</li><li>Measured UL QoS (SINR, BLER, data channel performance)</li><li>Possible MIMO mode (UL/DL) <ul id="ul0010" list-style="none" compact="compact"><li>∘ Virtual-MIMO in UL: Transport format combinations can be optimized separately for use in SIMO and virtual MIMO modes (the selected mode changes dynamically according to UL scheduler decisions). Virtual MIMO would benefit from block spreading applied for multiple control streams whereas in case of SIMO the signaling is optimized when spreading is not applied.</li><li>∘ DL SIMO/MIMO transmission: Number of feedback (FB) bits varies between SIMO and different MIMO modes. Transport format combination can be optimized separately for use in SIMO and different MIMO modes.</li></ul></li></ul>
0039Rate matching operation of UL data channel(s) is based on the transport format combination selected for the data-non-associated control channels. For example, Rate matching can be used for the UL data channel(s) to fit the data to use those symbols available for transmissions that have not been assigned for data-non-associated control signals.
Transport format signaling scheme
0040Higher layer signaling is used to configure the applied transport format combinations for data-non-associated control signals transmitted with UL data. <ul id="ul0011" list-style="bullet" compact="compact"><li>Number of TFCs configured by a higher layer should be limited to a relatively small number to avoid excessive signaling burden, in particular to limit the number of bits necessary to signal the TFC to be used in a particular TTI.</li><li>It seems that four quantization levels would be enough in practice.</li><li>The exact relation between the TFCI bits and the content of TFC is configurable (RRC signaling). TFCI signaling can be further optimized by reconfiguring the TFC set on the fly while the UE moves e.g., from cell center to cell edge.</li></ul> As suggested above, dynamic control signaling may be used to select the actual transport format used for data-non-associated control signaling. Such signaling may be transmitted on the downlink 422 in/with UL allocation grant signaling. 2(1) bits might for instance be needed to configure 4(2) different transport format combinations for data-non-associated controls signaling. Such additional dynamic signaling bits may be viewed as "Dynamic TFCI".
0041If it is already contemplated to include a signaling bit into the UL allocation grant signaling to inform whether the corresponding DL allocation grant was transmitted or not (and consequently an ACK/NACK needs to be transmitted as data-non-associated controls signaling), such could be adapted for purposes of the present invention as well. It is noted that having 2 bits reserved for this indication combined with Dynamic TFCI, would make it possible to utilize these bits in such a way that one signaling word (e.g., "00") corresponds to the case where ACK/NACK does not exist whereas the remaining signaling words ('01', '10' and '11') can represent the size of ACK/NACK resource when ACK/NACK is present. With this optimization only one additional bit on top of the bit which is used to indicate presence of the ACK/NACK signal in the prior art is needed to be able to signal 3 different TFCIs to be used for this ACK/NACK signal. If this information was used individually, one additional bit could only indicate two different TFCIs, causing a significantly coarser quantization.
0042Explicit segmentation indicator "Explicit segmentation indicator" transmitted with dynamic resource allocation signalling can be seen as an additional example of this invention. This indicator could be used e.g., in a VoIP application. <ul id="ul0012" list-style="bullet" compact="compact"><li>At the cell edge it may not be possible to transmit a data packet (say VoIP packet) in a single TTI. Then the packet can be transmitted using two HARQ transmissions, also called nominal mode, where the first transmission fails with a high probability, and the desired Block Error Rate is achieved after the second one. Of course, as an alternative, one can always subdivide the VoIP packet into two packets, but this will decrease the coding gain significantly because each of the packets is shorter and the coding gain of turbo codes decreases significantly for sort packets (VoIP packets are not particularly big anyhow). It is also possible to use a higher code rate for initial transmission and always rely on retransmission(s) but then the standard rate matching approach would first send all the systematic bits and then only parity bits. This is undesirable as well as it represents a bad interleaver. In case of explicit segmentation, i.e. if an information that segmentation is to be used is included (e.g. via a signalling bit or other means) this information can be used to optimize the definition of redundancy versions that are specifically optimized for this case. Then a redundancy version can be defined e.g., in such a way, that odd and even bits are transmitted on odd and even frame numbers. If the first transmission happens to be on a odd frame number (or TTI number or subframe number, or another suitable identification number of a specific packet) then only the odd bits are transmitted. More specifically, among those bits that would be transmitted if twice as many bits were available for transmission, only the odd bits are selected. This gives exactly the number of bits available for transmission. For the next packet, which will be on an even frame number (or respective number) the even bits are selected. Thus after reception of both packets, the receiver has available exactly those bits, that would have been available for a hypothetical transmission that would have allowed transmission of twice as many bits as actually possible. The rate matching is designed to provide an optimal selection (within practical limits, e.g. complexity) for a given number of bits. Therefore the proposed algorithm will achieve a (practically) optimal selection of bits when combining two transmissions. According to the state of the art, the Rate matching algorithm would select a redundancy version that was optimal for the first transmission, however this is pointless as the first transmission is practically deemed to fail anyhow due to insufficient available transmission power, or because the coding rate is even above 1. According to the prior art, the combined first and second transmission would not be ideal. In particular, due to the prior art, the first transmission would contain exclusively or predominantly systematic bits, while the second one would contain predominantly or exclusively parity bits. Obviously, this is not a good distribution of these two kinds of bits on the two TTIs.</li><li>One approach to save one signalling bit in case of segmentation is to not to reserve ACK/NACK resource corresponding to the first TTI (the first transmission contains almost always an error in such case, so there is little use (little information) in almost always sending the NACK following the first transmission)</li><li>If such a segmentation bit is present, then, according to the present invention, the meaning of the TFCI signalling for data-non-associated control signaling is redefined, because it is an indication that there is a comparatively poor UL channel quality (at least too poor to transmit a packet in a single shot). In general more robust TFCIs will be associated, compared to the case where the segmentation (or nominal mode) is not indicated.</li></ul>
0043Another use case for the dynamic indicator is controlling of the transmission power used in HARQ retransmissions. An HARQ retransmission is used, if the first transmission was not successful. For HARQ, the receiver makes use of both the first reception (that had failed when decoded individually) and the second one, while conventional ARQ would only make use of the second one. Therefore for HARQ typically the retransmission can be sent with lower power respectively lower SNR. Consequently more symbols have to be used for data-non-associated control signaling for retransmissions compared to initial transmissions if otherwise the same parameters are used. The fact that a transmission is a retransmission can be derived from information on the used redundancy information, retransmission number a new data indicator that indicates transmission of a new packet or similar information.
0044Dynamic indicator could also be used to indicate the situation that there is a need to puncture more bits for control than in a non-nominal mode. Actually it may be less than one bit if all bits are collected into one comprehensive redundancy version table such as done for EDCH. In this case there are not individual bits for segmentation indicator and dynamic indicator, but instead all the bits are pooled together to define an indicator into a comprehensive table, that includes both the segmentation indicator and the dynamic indicator or the segmentation indicator and the TFC. This table can be predefined or signalled similar to the table that was already described for associating the dynamic indicator with a TFC.
0045Tables 1-4 show examples of signaling schemes according to the invention. Table 1 presents a signaling format with one-bit TFCI signaling. Table 2 shows another signaling example with one-bit TFCI signaling. In Table 2 the size of the MCS domain is reduced from 5 to 3 (as compared to Table 1). Table 3 shows an example where the signaling is based only on dynamic TFCI signaling with two bits. Table 4 shows an example where the dynamic signaling is used to configure the number input bits of CQI signaling. <tables id="tabl0001" num="0001"><table frame="all"><title><b>Table 1. An example of a signalling format according to the invention</b></title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="92mm" /><colspec colnum="2" colname="col2" colwidth="18mm" /><colspec colnum="3" colname="col3" colwidth="14mm" /><colspec colnum="4" colname="col4" colwidth="15mm" /><colspec colnum="5" colname="col5" colwidth="14mm" /><colspec colnum="6" colname="col6" colwidth="15mm" /><thead><row><entry namest="col1" nameend="col2" align="left" valign="top">Control type</entry><entry align="center" valign="top">A/N</entry><entry align="center" valign="top">CQI</entry><entry align="center" valign="top">A/N</entry><entry align="center" valign="top">CQI</entry></row></thead><tbody><row><entry namest="col1" nameend="col2" align="left">Control size (# of input bits)</entry><entry align="center">1 bits</entry><entry align="center">bits</entry><entry align="center">1 bits</entry><entry align="center">10 bits</entry></row><row><entry namest="col1" nameend="col2" align="left">Dynamic TFI</entry><entry namest="col3" nameend="col4" align="center">0</entry><entry namest="col5" nameend="col6" align="center">1</entry></row><row><entry morerows="4">Symbol space of control channel as a function data channel MCS</entry><entry>MCS1</entry><entry align="center">1</entry><entry align="center">5</entry><entry align="center">2</entry><entry align="center">8</entry></row><row><entry>MCS2</entry><entry align="center">4</entry><entry align="center">8</entry><entry align="center">8</entry><entry align="center">12</entry></row><row><entry>MCS3</entry><entry align="center">8</entry><entry align="center">16</entry><entry align="center">16</entry><entry align="center">24</entry></row><row><entry>MCS4</entry><entry align="center">12</entry><entry align="center">24</entry><entry align="center">24</entry><entry align="center">36</entry></row><row><entry>MCS5</entry><entry align="center">24</entry><entry align="center">48</entry><entry align="center">48</entry><entry align="center">72</entry></row></tbody></tgroup></table></tables><tables id="tabl0002" num="0002"><table frame="all"><title><b>Table 2. Another example of a signalling format according to the invention</b></title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="84mm" /><colspec colnum="2" colname="col2" colwidth="17mm" /><colspec colnum="3" colname="col3" colwidth="17mm" /><colspec colnum="4" colname="col4" colwidth="17mm" /><colspec colnum="5" colname="col5" colwidth="17mm" /><colspec colnum="6" colname="col6" colwidth="17mm" /><thead><row><entry namest="col1" nameend="col2" align="left" valign="top">Control type</entry><entry align="center" valign="top">A/N</entry><entry align="center" valign="top">CQI</entry><entry align="center" valign="top">A/N</entry><entry align="center" valign="top">CQI</entry></row></thead><tbody><row><entry namest="col1" nameend="col2" align="left">Control size (# of input bits)</entry><entry align="center">1 bits</entry><entry align="center">110 bits</entry><entry align="center">1 bits</entry><entry align="center">110 bits</entry></row><row><entry namest="col1" nameend="col2" align="left">Dynamic</entry><entry namest="col3" nameend="col4" align="center">0</entry><entry namest="col5" nameend="col6" align="center">1</entry></row><row><entry morerows="2">Symbol space of control channel as a function data channel MCS</entry><entry>MCS1</entry><entry align="center">2</entry><entry align="center">5</entry><entry align="center">12</entry><entry align="center">24</entry></row><row><entry>MCS2</entry><entry align="center">4</entry><entry align="center">8</entry><entry align="center">16</entry><entry align="center">36</entry></row><row><entry>MCS3</entry><entry align="center">8</entry><entry align="center">16</entry><entry align="center">24</entry><entry align="center">48</entry></row></tbody></tgroup></table></tables><tables id="tabl0003" num="0003"><table frame="all"><title><b>Table 3. Yet another example of signalling format according to invention</b></title><tgroup cols="10"><colspec colnum="1" colname="col1" colwidth="44mm" /><colspec colnum="2" colname="col2" colwidth="19mm" /><colspec colnum="3" colname="col3" colwidth="13mm" /><colspec colnum="4" colname="col4" colwidth="14mm" /><colspec colnum="5" colname="col5" colwidth="13mm" /><colspec colnum="6" colname="col6" colwidth="14mm" /><colspec colnum="7" colname="col7" colwidth="13mm" /><colspec colnum="8" colname="col8" colwidth="14mm" /><colspec colnum="9" colname="col9" colwidth="13mm" /><colspec colnum="10" colname="col10" colwidth="14mm" /><thead><row><entry namest="col1" nameend="col2" align="left" valign="top">Control type</entry><entry align="center" valign="top">A/N</entry><entry align="center" valign="top">CQI</entry><entry align="center" valign="top">A/N</entry><entry align="center" valign="top">CQI</entry><entry align="center" valign="top">A/N</entry><entry align="center" valign="top">CQI</entry><entry align="center" valign="top">A/N</entry><entry align="center" valign="top">CQI</entry></row></thead><tbody><row><entry namest="col1" nameend="col2" align="left">Control size (# of input bits)</entry><entry align="center">1 bits</entry><entry align="center">10 bits</entry><entry align="center">1 bits</entry><entry align="center">10 bits</entry><entry align="center">1 bits</entry><entry align="center">10 bits</entry><entry align="center">1 bits</entry><entry align="center">10 bits</entry></row><row><entry namest="col1" nameend="col2" align="left">Dynamic</entry><entry namest="col3" nameend="col4" align="center">0</entry><entry namest="col5" nameend="col6" align="center">1</entry><entry namest="col7" nameend="col8" align="center">2</entry><entry namest="col9" nameend="col10" align="center">3</entry></row><row><entry morerows="1">Symbol space of control channel as a function data channel MCS</entry><entry>MCS1</entry><entry align="center">1</entry><entry align="center">5</entry><entry align="center">2</entry><entry align="center">10</entry><entry align="center">4</entry><entry align="center">15</entry><entry align="center">8</entry><entry align="center">20</entry></row><row><entry>MCS2</entry><entry align="center">12</entry><entry align="center">24</entry><entry align="center">16</entry><entry align="center">32</entry><entry align="center">20</entry><entry align="center">40</entry><entry align="center">24</entry><entry align="center">48</entry></row></tbody></tgroup></table></tables><tables id="tabl0004" num="0004"><table frame="all"><title><b>Table 4. Still another example of a signalling format according to the invention</b></title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="78mm" /><colspec colnum="2" colname="col2" colwidth="17mm" /><colspec colnum="3" colname="col3" colwidth="18mm" /><colspec colnum="4" colname="col4" colwidth="19mm" /><colspec colnum="5" colname="col5" colwidth="18mm" /><colspec colnum="6" colname="col6" colwidth="19mm" /><thead><row><entry namest="col1" nameend="col2" align="left" valign="top">Control type</entry><entry align="center" valign="top">A/N</entry><entry align="center" valign="top">CQI</entry><entry align="center" valign="top">A/N</entry><entry align="center" valign="top">CQI</entry></row></thead><tbody><row><entry namest="col1" nameend="col2" align="left">Control size (# of input bits)</entry><entry align="center">1 bits</entry><entry align="center">10 bits</entry><entry align="center">1 bits</entry><entry align="center">40 bits</entry></row><row><entry namest="col1" nameend="col2" align="left">Dynamic</entry><entry namest="col3" nameend="col4" align="center">0</entry><entry namest="col5" nameend="col6" align="center">1</entry></row><row><entry morerows="2">Symbol space of control channel as a function data channel MCS</entry><entry>MCS1</entry><entry align="center">2</entry><entry align="center">5</entry><entry align="center">12</entry><entry align="center">20</entry></row><row><entry>MCS2</entry><entry align="center">4</entry><entry align="center">8</entry><entry align="center">16</entry><entry align="center">32</entry></row><row><entry>MCS3</entry><entry align="center">8</entry><entry align="center">16</entry><entry align="center">24</entry><entry align="center">64</entry></row></tbody></tgroup></table></tables>
0046In the proposed signaling scheme configurable parameters are <ul id="ul0013" list-style="bullet"><li>CQI (number of input bits of encoder) and ACK/NACK sizes</li><li>Number of output bits of encoder (encoding scheme for CQI)</li><li>Encoding scheme</li><li>Symbol space for data-non-associated control signaling <ul id="ul0014" list-style="none" compact="compact"><li>∘ separately for different modulation and coding schemes used by UL data channel</li><li>∘ separately for different transport formats of data-non-associated control channel</li></ul></li></ul>
0047It is noted that the modulation and coding scheme applied for the UL data channel can be mapped into different transport formats in different ways <ul id="ul0015" list-style="bullet" compact="compact"><li>Modulation -specific approach <ul id="ul0016" list-style="none" compact="compact"><li>∘ MCS1 --- 64 QAM</li><li>∘ MCS2 --- 16QAM</li><li>∘ MCS3 --- QPSK</li></ul></li><li>Modulation and coding scheme - specific approach <ul id="ul0017" list-style="none" compact="compact"><li>∘ MCS1 --- 16QAM, ECR> 2/3</li><li>∘ MCS2 --- 16QAM, ECR< 2/3</li><li>∘ MCS3 --- QPSK, ECR> 2/3</li><li>∘ MCS4 --- QPSK, ECR< 2/3</li></ul></li></ul>
0048In a further embodiment of the present invention, the TFC to be used can be defined using algorithmic representations. In this approach, each MCS is associated to an Estimated Signal to Noise Ratio(ESNR). The ESNR can be computed in dependence of the coding rate and modulation rate of the selected MCS. Coding rate is the relation between the number of data bits and bits after coding and rate matching. In a second step, the TFC of the control signalling can then be derived in dependence of the ESNR. At first sight, it may be considered to be equivalent to define a direct association between MCS and TFC or an indirect association between ESNR and TFC. However, the latter approach lends itself easier to be put into formulas. For example, for the derivation of the number of symbols to be used for ACK/NACK signalling, the known formula for BPSK Bit error rate performance can be used to determine the required energy and consequently number of symbols to be used to reach a desired bit error rate. Also the relation between MCS and ESNR can be derived using a few explicit definitions for some MCS and appropriate interpolation between these for other ones or suitable approximations.
0049Note that the segmentation indicator can also be taken into account for this derivation: Because the target error rate is only achieved after the second transmission, the coding rate to be used in the calculation can be set to half the actual coding rate.
0050Also further transmission parameters can be taken into account in a similar way as the segmentation indicator: Depending on specific transmission parameters, the rule to derive the ESNR from the MCS can be changed. Either an offset to the MCS can be defined (in a similar way as for the segmentation indicator) or an offset can be applied to the ESNR directly. For example, some information may be available about the intended QoS (Quality of service) of a packet (or more precisely the service to which the data that are carried by that packet belongs). This QoS will determine the optimum BLER (Block Error Ratio) of the packet and this will affect the required SNR. So consequently this information can be also used to get an optimized setting of the ESNR. Further such parameters include but are not limited to usage of SIMO or MIMO for transmission. For MIMO, even for so called virtual MIMO, also called SDMA (Space Division Multiple Access) two streams are transmitted, this will typically cause some inter stream interference. This inter stream interference can be removed by interference cancellation techniques including successive interference cancellation, that performs multiple decoding runs of the data. However, for data-non-associated control signaling, there may be no coding (ACK/NACK) and then this interference cancellation may be less effective, meaning that more resources have to be spent than for the single stream case.
0051In a further refinement of the above embodiment, the number of bits that are used for data-non-associated control signaling instead of data transmission are taken into account. In other words, the above mentioned coding rate is calculated taking the number of symbols into account, which are used for the transmission of data-non-associated controls signaling. Note that this number is only derived as an output of the calculation, so in practice it is not known as an input parameter for the calculation. It can however be taken into account by an iterative solution, or by solving directly the corresponding system of equations. For practical implementations, the exact way of calculation e.g. the number of iterations to be performed and the starting value to be used must be pre known at both base station and mobile station in order to ensure that both calculate exactly the same result because otherwise decoding of both the data-non-associated control signaling and the data can fail.
0052In a further refinement, not only the modulation scheme and the code rate are taken into account, but also the size of the packet, e.g. the number of payload bits or the number of bits after encoding or the number of bits after rate matching or the number of symbols available for transmission or the number of allocated resource units. Basically each of these quantities is equivalent as one can be derived from another if code rate and/or modulation scheme are known as well. The reason for including this information as well is the fact that the coding gain for turbo codes increases with increasing block size. So if a larger block is encoded, a somewhat lower SNR is sufficient for a desired error rate. Consequently somewhat more symbols have to be used for data-non-associated control signaling.
0053The invention has been described primarily for the case that each UL packet is scheduled individually. It is however also applicable to the case, that several packets are scheduled with a single scheduling command, also sometimes called persistent scheduling. For example in the case of VoIP, a packet may be scheduled every 20ms, because the voice encoder does deliver a coded voice packet every 20ms. This approach reduces the scheduling overhead. Also for persistently scheduled packets, it may be necessary to include some data-non-associated control signaling and then the number of symbols to be set aside for this purpose must also be determined. One approach may be to substitute the persistent scheduling by explicit scheduling and apply the invention directly. Another approach can be to provide the necessary information already in the persistent scheduling command in a similar way as set out in this invention. Of course, it is also possible to combine these two approaches or to use slightly different parameters in those two cases.
Contents4
2 sheets
Sheet 1 Sheet 2
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| EP1748593A1 | Cites | European Patent Office (EPO) | Filed by opponent |
| EP1914948A1 | Cites | European Patent Office (EPO) | Filed by opponent |
| EP1931096A1 | Cites | European Patent Office (EPO) | Filed by opponent |
| WO2007037412A1 | Cites | World Intellectual Property Organization (WIPO) | Filed by opponent |
| WO2007043105A1 | Cites | World Intellectual Property Organization (WIPO) | Filed by opponent |
| WO2008115649A1 | Cites | World Intellectual Property Organization (WIPO) | Filed by opponent |
| EP2019559A1 | Cites | European Patent Office (EPO) | Filed by opponent |
| EP2827520A2 | Cites | European Patent Office (EPO) | Filed by opponent |
| MOTOROLA: "Multiplexing of Uplink Control Signaling with Data", 3GPP DRAFT; R1-070777_ UL_CONTROLDATA_MUX, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. St. Louis, USA; 20070206, 6 February 2007 (2007-02-06), XP050104805, | Non-patent | – | – |
| NOKIA: "One TFC for signalling on HR channels", 3GPP DRAFT; GP-040944 44160 FLO HR SIGNALLING CR, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. TSG GERAN, no. Cancun; 20040415, 15 April 2004 (2004-04-15), XP050010946, | Non-patent | – | – |
| NEC GROUP ET AL.: "Multiplexing of uplink data-non-associated control signal with data", 3GPP DRAFT; R1-072121, 2 May 2007 (2007-05-02), pages 1 - 4, XP050105870 | Non-patent | – | Filed by opponent |
46 members in 17 offices
Members46
| Document | Office | Kind | |
|---|---|---|---|
| AU2008265134A1 | Australia | A1 | |
| CA2690672A1 | Canada | A1 | |
| CA2829696A1 | Canada | A1 | |
| WO2008155370A2 | World Intellectual Property Organization (WIPO) | A2 | |
| US2009033524A1 | United States of America | A1 | |
| WO2008155370A3 | World Intellectual Property Organization (WIPO) | A3 | |
| MX2009013860A | Mexico | A | |
| EP2168285A2 | European Patent Office (EPO) | A2 | |
| KR20100039344A | Republic of Korea | A | |
| CN101785230A | China | A | |
| ZA200908947B | South Africa | B | |
| RU2010101325A | Russian Federation | A | |
| US8014352B2 | United States of America | B2 | |
| KR20130064148A | Republic of Korea | A | |
| RU2485696C2 | Russian Federation | C2 | |
| UA102227C2 | Ukraine | C2 | |
| CN103427954A | China | A | |
| CA2690672C | Canada | C | |
| RU2012145206A | Russian Federation | A | |
| KR101391208B1 | Republic of Korea | B1 | |
| KR101391209B1 | Republic of Korea | B1 | |
| AU2008265134B2 | Australia | B2 | |
| AU2008265134C1 | Australia | C1 | |
| AU2014233624A1 | Australia | A1 | |
| RU2532710C2 | Russian Federation | C2 | |
| BRPI0813259A2 | Brazil | A2 | |
| EP2827520A2 | European Patent Office (EPO) | A2 | |
| EP2168285B1 | European Patent Office (EPO) | B1 | |
| EP2827520A3 | European Patent Office (EPO) | A3 | |
| AU2014233624B2 | Australia | B2 | |
| CA2829696C | Canada | C | |
| CN103427954B | China | B | |
| EP2827520B1This record | European Patent Office (EPO) | B1 | |
| DK2827520T3 | Denmark | T3 | |
| EP2827520B9 | European Patent Office (EPO) | B9 | |
| ES2703144T3 | Spain | T3 | |
| PL2827520T3 | Poland | T3 | |
| ES2703144T9 | Spain | T9 | |
| HUE042267T2 | Hungary | T2 | |
| DK2827520T5 | Denmark | T5 | |
| BRPI0813259B1 | Brazil | B1 | |
| EP2827520B2 | European Patent Office (EPO) | B2 | |
| DK2827520T4 | Denmark | T4 | |
| FI2827520T4 | Finland | T4 | |
| ES2703144T5 | Spain | T5 | |
| PL2827520T5 | Poland | T5 |
115 legal events, as 15 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapse because of not paying annual feesLapsedMM01 | MM01 | AT | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| Ep patent lapsedLapsedEBP | EBP | DK | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Change of representativeR082 | R082 | DE | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Publication of translation of european patent specificationUEP | UEP | AT | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Opt-out of the competence of the unified patent court (upc) changedP02 | P02 | EP | |
| Opt-out of the competence of the unified patent court (upc) registeredP01 | P01 | EP | |
| Ep patent validated in greeceEP | EP | GR | |
| Amendment of european patent (b2) valid in norwayTB2 | TB2 | NO | |
| Patent modifiedDC2A | DC2A | ES | |
| Translation for ep filed (entry of ep into country)FP | FP | NL | |
| Ep patent has been republished in amended form after opposition at epoOppositionRPEO | RPEO | SE | |
| Amended ep patent with danish claimsT4 | T4 | DK | |
| Patent maintained in amended form27A | 27A | EP | |
| Designated contracting statesAK | AK | EP | |
| Epo decision maintaining patent in amended form now finalR102 | R102 | DE | |
| Patent maintained in amended formORIGINAL CODE: 0009272PUAH | PUAH | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: PATENT MAINTAINED AS AMENDEDSTAA | STAA | EP | |
| Opposition withdrawnWithdrawnORIGINAL CODE: 0009264PLBP | PLBP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Publication of translation of european patent specificationUEP | UEP | AT | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Reply of patent proprietor to notice(s) of opposition receivedOppositionORIGINAL CODE: EPIDOSNOBS3PLBB | PLBB | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Opposition filedOpposition26 | 26 | EP | |
| Notice of opposition and request to file observation + time limit sentOppositionORIGINAL CODE: EPIDOSNOBS2PLAX | PLAX | EP | |
| Corrected translation of ep patentT5 | T5 | DK | |
| Filing of the translation of the text of european patentsAG4A | AG4A | HU | |
| Opposition filedOppositionORIGINAL CODE: 0009260PLBI | PLBI | EP | |
| Opposition filed against patentOppositionR026 | R026 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Ep patent validated in greeceEP | EP | GR | |
| Change of the address of the representativeNEW ADDRESS: RUE DES NOYERS 11, 2000 NEUCHATEL (CH)PCAR | PCAR | CH | |
| Definitive protectionFG2A | FG2A | ES | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| CorrectionBERICHTIGUNG B9PK | PK | CH | |
| Invalidated european patentMG4D | MG4D | LT | |
| Entry of ep patent into national phase of norway [publ. of translation]T2 | T2 | NO | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Translation of granted ep patentGrantedTRGR | TRGR | SE | |
| Translation for ep filed (entry of ep into country)FP | FP | NL | |
| Ep patent with danish claimsT3 | T3 | DK | |
| New agentNV | NV | CH | |
| Ep patent valid in romaniaEPE | EPE | RO | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| European patents granted designating irelandGrantedFG4D | FG4D | IE | |
| Reference to at number (ep patent validated in austria)REF | REF | AT | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Divisional application: reference to earlier applicationAC | AC | EP | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: THE PATENT HAS BEEN GRANTEDSTAA | STAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Party data changed (applicant data changed or rights of an application transferred)RAP1 | RAP1 | EP | |
| Intention to grant announcedINTG | INTG | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: GRANT OF PATENT IS INTENDEDSTAA | STAA | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: EXAMINATION IS IN PROGRESSSTAA | STAA | EP |
Numbers
- Publication
- 2827520
- Application
- 141845651
Titles3
- German
- Adaptive Transport Format Uplink Signalisierung für nicht-daten-bezogene Rückkopplungs-Kontrollsignale
- English
- Adaptive transport format uplink signaling for data-non-associated feedback control signals
- French
- Signalisation en liaison montante à format de transport adaptatif pour des signaux de commande de rétroaction non associés à des données
Classification
- CPC, 8
- H04L1/1819
- H04L1/1671
- H04W48/08
- H04L1/003
- H04L1/0039
- H04L1/0025
- H04L1/0026
- H04L1/18
- IPC, 3
- H04L1 00
- H04L1 16
- H04L1 18
Designated states34
- Contracting states, 34
- Austria
- Belgium
- Bulgaria
- Switzerland
- Cyprus
- Czechia
- Germany
- Denmark
- Estonia
- Spain
- Finland
- France
- United Kingdom
- Greece
- Croatia
- Hungary
- Ireland
- Iceland
- Italy
- Liechtenstein
- Lithuania
- Luxembourg
- Latvia
- Monaco
and 10 moreShow fewer
- Malta
- Netherlands (Kingdom of the)
- Norway
- Poland
- Portugal
- Romania
- Sweden
- Slovenia
- Slovakia
- Türkiye
