EP3487099B1 - Mehrfachträgerbestätigungssignalisierung - Google Patents
Mehrfachträgerbestätigungssignalisierung Download PDFInfo
- Publication number
- EP3487099B1 EP3487099B1 EP18214563.1A EP18214563A EP3487099B1 EP 3487099 B1 EP3487099 B1 EP 3487099B1 EP 18214563 A EP18214563 A EP 18214563A EP 3487099 B1 EP3487099 B1 EP 3487099B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- nack
- ack
- carrier
- dtx
- codebook
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000011664 signaling Effects 0.000 title claims description 49
- 238000004891 communication Methods 0.000 claims description 48
- 239000000969 carrier Substances 0.000 claims description 26
- 238000000034 method Methods 0.000 claims description 25
- 230000015654 memory Effects 0.000 claims description 17
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 claims 54
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 claims 54
- 238000013507 mapping Methods 0.000 claims 2
- 238000010586 diagram Methods 0.000 description 28
- 230000009977 dual effect Effects 0.000 description 17
- 238000012790 confirmation Methods 0.000 description 11
- 230000004044 response Effects 0.000 description 11
- 238000000926 separation method Methods 0.000 description 10
- 230000008901 benefit Effects 0.000 description 9
- 230000005540 biological transmission Effects 0.000 description 6
- 230000007812 deficiency Effects 0.000 description 6
- 238000004458 analytical method Methods 0.000 description 5
- 238000013459 approach Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 230000007704 transition Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- VJYFKVYYMZPMAB-UHFFFAOYSA-N ethoprophos Chemical compound CCCSP(=O)(OCC)SCCC VJYFKVYYMZPMAB-UHFFFAOYSA-N 0.000 description 3
- 101100465000 Mus musculus Prag1 gene Proteins 0.000 description 2
- 230000003190 augmentative effect Effects 0.000 description 2
- 230000023402 cell communication Effects 0.000 description 2
- 238000007429 general method Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000001514 detection method Methods 0.000 description 1
- 230000005670 electromagnetic radiation Effects 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000000873 masking effect Effects 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/1607—Details of the supervisory signal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
- H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
- H04L1/0026—Transmission of channel quality indication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0056—Systems characterized by the type of code used
- H04L1/0057—Block codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
- H04L1/0072—Error control for data other than payload data, e.g. control data
- H04L1/0073—Special arrangements for feedback channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
- H04L27/2601—Multicarrier modulation systems
- H04L27/2626—Arrangements specific to the transmitter only
- H04L27/2646—Arrangements specific to the transmitter only using feedback from receiver for adjusting OFDM transmission parameters, e.g. transmission timing or guard interval length
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L5/00—Arrangements affording multiple use of the transmission path
- H04L5/003—Arrangements for allocating sub-channels of the transmission path
- H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
- H04L5/0055—Physical resource allocation for ACK/NACK
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L2001/125—Arrangements for preventing errors in the return channel
Definitions
- the present invention relates generally to the communications arts, and more specifically by way of example but not limitation, to acknowledgment signaling in a multiple carrier environment.
- Electronic communication forms the backbone of today's information-oriented society.
- Electronic communications are transmitted over wireless or wired channels using electromagnetic radiation, such as radio frequency (RF) transmissions, light waves, and so forth.
- RF radio frequency
- the accessibility and capacity of electronic communications is frequently limited by the bandwidth of a communications channel between a first (e.g., transmitting) device and a second (e.g., receiving) device.
- the available bandwidth of a communications channel may be increased by adopting any of a number of different schemes.
- One such example scheme is communicating over multiple carriers.
- Multiple carrier operations may include multiple cell operations.
- High speed packet access (HSPA), including high-speed downlink packet access (HSDPA), is currently being evolved to include multi-carrier and/or multi-cell operations.
- An initial step is to support dual-carrier and/or dual-cell (DC) HSDPA operations (DC-HSDPA).
- DC-HSDPA dual-cell
- a user can receive from two carriers "simultaneously.” This increases high-data-rate coverage.
- a first proposal entails signaling the two ACK/NACK indications (one per carrier) using separate High-Speed Dedicated Physical Control Channels (HS-DPCCHs).
- HS-DPCCHs High-Speed Dedicated Physical Control Channels
- the cubic metric is slightly larger than when the first HS-DPCCH is transmitted alone. This results in worse coverage when a mobile needs to ACK/NACK the second carrier alone, as compared to when it needs to ACK/NACK the first carrier alone.
- a second proposal generally entails signaling the two ACK/NACK indications using joint coding and one HS-DPCCH.
- the two ACK/NACK messages are jointly encode and transmitted using one HS-DPCCH.
- ERICSSON "Considerations on Dual-Cell HSDPA Operation", 3GPP DRAFT; R1-081545, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Shenzhen, China; 20080327, 27 March 2008 (2008-03-27), XP050109958, [retrieved on 2008-03-27 ]; discloses a discussion of Considerations on Dual-Cell HSDPA Operation.
- ERICSSON "Introduction of Dual-Cell HSDPA Operation on Adjacent Carriers", 3GPP DRAFT; Rl-083027 25212CR0267 INTRODUCTION OF DUAL-CELL HSDPA OPERATION ON ADJACENT CARRIERS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. Jeju; 20080812, 12 August 2008 (2008-08-12), XP050316480, [retrieved on 2008-08-12 ]; describes the characteristics of the Layer 1 multiplexing and channel coding in the FDD mode of UTRA.
- ERICSSON "On the HS-DPCCH Structure for Dual-Cell HSDPA Operation" 3GPP DRAFT; RI-083592 HS-DPCCH FOR DC-HSDPA, 3rd GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE; 650, ROUTE DES LUCIOLES; F-06921 SOPHIA-ANTIPOLIS CEDEX; FRANCE, (PUBLICATION 2008-09-24 ), describes that eight code words are needed to indicate ACK, NACK and DTX independently for dual cell transmission.
- This document suggests a codebook that includes the non-MIMO ACK/NACK codebook and has minimum Hamming distance of 3. does not include the non-MIMO ACK/NACK codebook and has a minimum Hamming distance equal to 5.
- An advantage of certain embodiments of the present invention is that an enhanced minimum Hamming distance may be achieved for a codebook having code words that jointly encode ACK/NACK signaling for multiple carriers. Another advantage of certain embodiments of the present invention is that PRE and POST operations may be supported. Yet another advantage of certain embodiments of the present invention is that codebook ambiguity may be avoided when there is a misunderstanding between a remote terminal and a wireless network node regarding whether a single carrier mode or a multiple carrier mode is active. Still yet another advantage of certain embodiments of the present invention is that a maximum possible code word separation may be achieved for messages having opposite acknowledgment meanings. Other advantages are noted herein below.
- Example additional embodiments include, by way of example but not limitation, arrangements, memories, devices, systems, and so forth. Additional aspects of the invention are set forth in part in the detailed description, drawings, and claims that follow, and in part may be derived from the detailed description and drawings, or can be learned by practice of the invention. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention as disclosed or as claimed.
- the first existing proposal would use two separate ACK/NACK indications. It would result in a severe coverage impact when both HS-DPCCHs are transmitted.
- the second existing proposal would reuse the existing eight (8) MIMO ACK/NACK/PRE/POST code words that are already specified in 3GPP.
- such a codebook formed from the existing eight MIMO code words has a minimum Hamming distance of only 3, which is far less than the optimal minimum Hamming distance for a codebook of length 10 and size 8.
- example codebook embodiments that are described herein below have superior minimum Hamming distances.
- Two different example multiple carrier codebook embodiments are set forth below.
- a first example multiple carrier codebook embodiment has a minimum Hamming distance of 5, and a second example multiple carrier codebook embodiment has a minimum Hamming distance of 4. Both example multiple carrier codebook embodiments are capable of being configured to support PRE and POST operations.
- the second example multiple carrier codebook embodiment may also include, as a sub-codebook or subset thereof, a single carrier ACK/NACK signaling codebook.
- the second example multiple carrier codebook embodiment may further ensure that code word pairs having code words with opposite meanings have a relatively large Hamming distance separation between them.
- the first and second example multiple carrier codebook embodiments may entail a codebook that supports ACK/NACK signaling using one HS-DPCCH for the DC-HSDPA operation in a WCDMA-based communications system.
- two CQIs may be signaled during DC-HSDPA operations.
- An analogous problem can arise with respect to CQI when an HS-SCCH order deactivating the DC-HSDPA operation is not detected by a remote terminal. This can create a CQI codebook ambiguity between a wireless network node and the remote terminal. Example embodiments addressing this problem are also described herein below.
- DC-HSDPA When a MIMO-style HS-DPCCH format is used for DC-HSDPA, integrating the DC-HSDPA feature and the MIMO HSDPA feature can be problematic.
- Example embodiment(s) enabling the DC-HSDPA feature and the MIMO HSDPA feature to be combined are also described herein below.
- FIG. 1 is a block diagram of an example communications system 100 including a wireless network node 102 and multiple remote terminals 104.
- communications system 100 includes at least one wireless network node 102 and one or more remote terminals 104a and 104b.
- wireless network node 102 may be in communication with fewer or more than two such remote terminals 104.
- each given remote terminal 104 may be in communication with multiple such wireless network nodes 102 (e.g., in a multiple-cell mode).
- wireless network node 102 may be a wired network node that communicates with remote terminal(s) 104 over a wireline connection.
- Communications from wireless network node 102 to a remote terminal 104 are usually termed downlink communications. Communications from a remote terminal 104 to wireless network node 102 are usually termed uplink communications. In an example embodiment, a downlink communication 106 is transmitted from wireless network node 102 to remote terminal 104a. Remote terminal 104a receives downlink communication 106 and processes it.
- uplink response message 108 In response to receiving downlink communication 106 and/or based on the processing thereof, remote terminal 104a formulates an uplink response message 108. As described herein below, uplink response message 108 may include at least one code word. Remote terminal 104a transmits uplink response message 108 to wireless network node 102. Wireless network node 102 may process uplink response message 108 appropriately, such as by decoding the included code word(s).
- uplink response message 108 indicates a reception condition with regard to one or more downlink communications 106.
- the reception condition may be indicated with one or more included code words.
- An indicated reception condition may be, for example, an affirmative acknowledgment, a negative acknowledgment, no reception, a preamble operation, a postamble operation, some combination thereof, and so forth.
- Different reception conditions are described further herein below with particular reference to FIG. 2 .
- Wireless network nodes 102 may comprise, for example, a base station, a base transceiver station, a radio base station, a Node B, an access point, some combination thereof, and so forth.
- Remote terminals 104 may comprise, for example, a mobile terminal, a mobile station, a user equipment, a subscriber station, a communication card or module, some combination thereof, and so forth.
- General example device implementations for wireless network nodes 102 and/or remote terminals 104 are described herein below with particular reference to FIG. 7 .
- remote terminals may be of any general type, and network nodes may be a part of the infrastructure of any general wireless (or wired) network.
- network nodes may be a part of the infrastructure of any general wireless (or wired) network.
- other air interface technologies e.g., that comport with a different wireless network standard
- Such other wireless network standards may or may not be directed to a cellular-type wireless network.
- FIG. 2 is an example state diagram 200 for extended ACK/NACK signaling that includes PRE and POST operations.
- state diagram 200 includes three states: a discontinuous transmission (DTX) state 202, a preamble (PRE) state 204, and an ACK/NACK state 206.
- DTX discontinuous transmission
- PRE preamble
- ACK/NACK state 206 ACK/NACK state 206.
- PRE and POST operations are introduced to improve ACK/NACK detection performance.
- a trellis structure is added to the ACK/NACK signaling channel.
- a remote terminal When a remote terminal detects the High-Speed Shared Control Channel (HS-SCCH) for subframe n, it sends a preamble "PRE" indication in the HS-DPCCH in subframe n -1 to transition from DTX state 202 to PRE state 204. If the remote terminal does not detect a High-Speed Downlink Shared Channel (HS-DSCH) in subframe n after receiving a HS-DSCH in subframe n -1, it sends a post-amble "POST" indication in subframe n to transition from ACK/NACK state 206 to DTX state 202.
- HS-SCCH High-Speed Shared Control Channel
- FIG. 3 is a block diagram 300 of example devices 302 that are configured to communicate using a multiple carrier codebook 312 in accordance with embodiments of the present invention.
- devices 302 include a transmitter 304, a receiver 306, a communication confirmation unit 308, a single carrier codebook 310, and a multiple carrier codebook 312.
- a first device 302a includes a transmitter 304a, a receiver 306a, a communication confirmation unit 308a, a single carrier codebook 310a, and a multiple carrier codebook 312a.
- a second device 302b includes a receiver 306b, a transmitter 304b, a communication confirmation unit 308b, a single carrier codebook 310b, and a multiple carrier codebook 312b.
- Each of devices 302a and 302b may include more or fewer components than those that are illustrated.
- first device 302a is functioning as a wireless network node 102 (of FIG. 1 ), and second device 302b is functioning as a remote terminal 104, such as remote terminal 104a.
- first device 302a uses transmitter 304a to transmit a downlink communication 106 to second device 302b, which is received with receiver 306b.
- Second device 302b uses transmitter 304b to transmit an uplink response message 108 to first device 302a, which is received with receiver 306a.
- Uplink response message 108 may include at least one ACK indication, at least one NACK indication, or at least one transitional operation indication for one or more carriers. If second device 302b miss detects the presence of downlink communication 106, it will not transmit an uplink response message 108. Such cases, for example, are referred to herein as DTX.
- these indications may be communicated using at least one code word from one or more codebooks.
- devices 302 When devices 302 are communicating over a single carrier, they may determine and decode/interpret code words using single carrier codebook 310. When devices 302 are communicating over multiple carriers, they may determine and decode/interpret code words using multiple carrier codebook 312.
- An example multiple carrier codebook 312 that pertains to at least two carriers/cells is described below with particular reference to FIG. 4 .
- the code word determination is performed by communication confirmation unit 308b of second device 302b, and the code word decoding is performed by communication confirmation unit 308a of first device 302a.
- FIG. 4 is a block diagram of an example multiple carrier codebook 312.
- multiple carrier codebook 312 comprises an example dual carrier codebook 312-2.
- dual carrier codebook 312-2 includes ten total code words 402. It includes eight "acknowledgment" code words 402a-h.
- Dual carrier codebook 312-2 may also include two "transitional operation" code words 402i and 402j.
- a dual carrier codebook 312-2 may alternatively include a different number of code words and/or a set of code words that have different meanings.
- Code word 402a indicates an "ACK/DTX" reception condition, which corresponds to an affirmative acknowledgment (e.g., for a transport block that is received) on a first carrier and no reception (e.g., of a transport block) on a second carrier.
- Code word 402b indicates a "NACK/DTX” reception condition, which corresponds to a negative acknowledgment (e.g., for a transport block that is not received correctly) on a first carrier and no reception on a second carrier.
- Code word 402c indicates a "DTX/ACK” reception condition, which corresponds to no reception on a first carrier and an affirmative acknowledgment on a second carrier.
- Code word 402d indicates a "DTX/NACK” reception condition, which corresponds to no reception on a first carrier and a negative acknowledgment on a second carrier.
- Code word 402e indicates a "NACK/ACK” reception condition, which corresponds to a negative acknowledgment on a first carrier and an affirmative acknowledgment on a second carrier.
- Code word 402f indicates an "ACK/NACK” reception condition, which corresponds to an affirmative acknowledgment on a first carrier and a negative acknowledgment on a second carrier.
- Code word 402g indicates an "ACK/ACK” reception condition, which corresponds to an affirmative acknowledgment on a first carrier and an affirmative acknowledgment on a second carrier.
- Code word 402h indicates a "NACK/NACK" reception condition, which corresponds to a negative acknowledgment on a first carrier and a negative acknowledgment on a second carrier.
- a multiple carrier codebook 312 such as dual carrier codebook 312-2 may also include code words for transitional operations.
- Code word 402i indicates a reception condition for a "PRE" operation, which corresponds to a preamble transition operation.
- Code word 402j indicates a reception condition for a "POST” operation, which corresponds to a postamble transition operation.
- Each code word in these two example codebook embodiments has a length of ten values (e.g., 10 bits), but code words may alternatively be of a different length.
- a multiple carrier codebook 312 is described that may be implemented using one HS-DPCCH for DC-HSDPA HARQ acknowledgement signaling.
- This codebook has a minimum Hamm
- This first example codebook embodiment two more code words that are identical to legacy PRE/POST code words may be added in order to also support PRE/POST functionality. Even with the addition of the legacy PRE/POST code words, the minimum Hamming distance can remain equal to 5. This first example codebook embodiment can achieve an appreciably better message error rate performance as compared to a codebook that is based on the existing 8 MIMO ACK/NACK/PRE/POST code words.
- the first example codebook embodiment for dual carrier ACK/NACK signaling implies that a remote terminal will fall back to Release-5 (single carrier) ACK/NACK signaling when an HS-SCCH order deactivating DC-HSDPA operation is received.
- problems may arise when a remote terminal misses such an HS-SCCH order and therefore keeps using a DC-HSDPA HARQ acknowledgement codebook, while the wireless network node starts decoding received code words using a (single carrier) Release-5 codebook.
- the acknowledgement signaling may be preceded by PRE and POST transitional operation indicators, as represented in state diagram 200 (of FIG. 2 ).
- a codebook for the MC-HSDPA HARQ acknowledgement signaling may contain the single-carrier codebook as a sub-codebook or subset thereof.
- a second example codebook embodiment, which is described below, includes a single carrier codebook as a sub-codebook or subset of a multiple carrier codebook.
- the Hamming distance between each of the code word pairs is also enhanced so as to achieve a minimum Hamming distance of 4. More specifically, for a second example codebook embodiment, a multiple carrier codebook 312 is described that may be implemented using one HS-DPCCH for DC-HSDPA HARQ acknowledgement signaling.
- the minimum Hamming distance of this example codebook is 4.
- this second example codebook embodiment may be augmented with the preamble (PRE) and postamble (POST) legacy code words as defined in Releases 5, 6, and 7.
- PRE preamble
- POST postamble
- a remote terminal when a remote terminal misses an order to cease multiple carrier operation (e.g., misses an HS-SCCH order) and remains in multiple carrier operation (e.g., remains in DC-HSDPA operation), it will signal an ACK/DTX code word indication or a NACK/DTX code word indication when it acknowledges receipt of HS-DSCH data. Because these two code words are the same as the ACK and NACK code words for single carrier (including single cell) signaling, there is no ambiguity problem at the wireless network node.
- messages having opposite meanings are assigned the largest (pair-wise) code word separation.
- messages DTX/ACK and DTX/NACK have opposite meaning.
- the messages ACK/DTX and NACK/DTX also have opposite meaning.
- the messages ACK/ACK and NACK/NACK have (double) opposite meaning.
- the messages ACK/NACK and NACK/ACK also have (double) opposite meaning. It can be seen that the proposed codebook has a Hamming distance of 10 for each pair of the above opposite-meaning cases.
- Code word remapping (e.g., changing the definition of a code word), bit permutation, bit-wise masking, combinations thereof, and so forth result in codebooks having the enumerated properties. Consequently, codebooks that can be obtained through one or more of these and/or similar or analogous operations (e.g., when starting from a codebook as described herein) comprise equivalent code books. Example implementations of these operations are provided below.
- This code word remapping does not, however, change the basic code properties, such as the minimum Hamming distance of 4, of the code book.
- the (pair-wise) maximum Hamming distance of 10 is preserved between code pairs having opposite meanings. In other words, the Hamming distance of 10 is preserved between code pairs DTX/ACK and DTX/NACK, between code pairs ACK/DTX and NACK/DTX, between code pairs ACK/NACK and NACK/ACK, and between code pairs ACK/ACK and NACK/NACK.
- This bit-permuted codebook preserves the minimum Hamming distance of 4 for the code book. Also, the Hamming distance of 10 is preserved between code pairs DTX/ACK and DTX/NACK, between code pairs ACK/DTX and NACK/DTX, between code pairs ACK/NACK and NACK/ACK, and between code pairs ACK/ACK and NACK/NACK.
- This code book resulting from application of a common mask preserves the minimum Hamming distance of 4 for the code book. Also, the Hamming distance of 10 is preserved between code pairs DTX/ACK and DTX/NACK, between code pairs ACK/DTX and NACK/DTX, between code pairs ACK/NACK and NACK/ACK, and between code pairs ACK/ACK and NACK/NACK.
- FIG. 5 is a flow diagram 500 of an example general method for multiple carrier acknowledgment signaling. As illustrated, flow diagram 500 includes eight blocks 502-516. Flow diagram 500 may be implemented by two communication devices, such as a first device 302a and a second device 302b (of FIG. 3 ). In an example embodiment, first device 302a implements steps 502, 504, 514, and 516 as a wireless network node 102. Second device 302b implements steps 506-512 as a remote terminal 104.
- processor-executable instructions may be embodied as hardware, firmware, software, fixed logic circuitry, combinations thereof, and so forth.
- Example operational implementations of processor-executable instructions include, but are not limited to, a memory coupled to a processor, an application-specific integrated circuit (ASIC), a digital signal processor and associated code, some combination thereof, and so forth.
- ASIC application-specific integrated circuit
- flow diagram 500 depicts a method for using a multiple carrier codebook 312 to implement acknowledgment signaling in a multiple carrier environment.
- an indication of carrier mode and a downlink schedule is transmitted.
- wireless network node 102 may transmit indication(s) of a carrier mode and a downlink schedule to remote terminal 104a using transmitter 304a.
- the carrier mode may be, for instance, a single-carrier mode or a multiple-carrier mode (e.g., a dual carrier mode).
- a downlink schedule typically informs the remote terminal of a bandwidth assignment block (e.g., frequencies and/or time slot(s)).
- downlink communication(s) are transmitted on one or more carriers.
- wireless network node 102 may transmit using transmitter 304a downlink communication(s) 106 on one or more carriers to remote terminal 104a in accordance with the indicated carrier mode and downlink schedule.
- Remote terminal 104a receives or at least attempts to receive downlink communications 106 from wireless network node 102 using receiver 306b. At step 506, it is determined if downlink communication(s) are received on expected carrier(s). For example, a communication confirmation unit 308b of remote terminal 104a may determine if downlink communication(s) 106 are received on the carrier(s) that are expected based on the indicated carrier mode and downlink schedule.
- a reception scenario is determined.
- communication confirmation unit 308b of remote terminal 104a may determine the reception scenario.
- the reception scenario corresponds to whether a communication was or was not correctly received on the expected carrier(s) and whether a communication was expected on the carrier(s).
- determining the reception scenario determines whether an ACK, NACK, DTX, etc. indication is appropriate for each of the assigned carrier(s). For a specific example, if a communication is expected on both a first and a second carrier, and if one is correctly received only on the first carrier, the reception scenario corresponds to an ACK for the first carrier and a NACK for the second carrier.
- a code word is determined that has a meaning corresponding to the determined reception scenario. For example, from a multiple carrier codebook 312 that is stored in a memory of remote terminal 104a, communication confirmation unit 308b of remote terminal 104a may determine a code word having a meaning corresponding to the determined reception scenario. Continuing with the specific example in a dual carrier context, remote terminal 104a determines the value of the code word 402f in dual carrier codebook 312-2 that corresponds to the ACK/NACK meaning.
- a message having the determined code word is transmitted.
- an uplink response message 108 having the determined code word 402 may be transmitted using transmitter 304b from remote terminal 104a to wireless network node 102.
- a message having the determined code word is received.
- uplink response message 108 having the determined code word 402 may be received from remote terminal 104a at wireless network node 102 using receiver 306a.
- the received code word is decoded.
- communication confirmation unit 308a of wireless network node 102 may decode the received code word 402. The decoding transforms or extracts the acknowledgment meaning from the value of the received code word 402.
- communication confirmation unit 308a of wireless network node 102 decodes the value of the received code word 402f to extract the intended ACK/NACK meaning that acknowledges the reception scenario on the first and second carriers.
- FIG. 6A is a block diagram 600A that depicts a Hamming distance analysis 602 that is performed on an example multiple carrier codebook 312.
- block diagram 600A includes multiple carrier codebook 312, Hamming distance analysis 602, and a minimum Hamming distance 604.
- a Hamming distance analysis 602 is applied to a multiple carrier codebook 312. The result of the analysis is a minimum Hamming distance 604.
- a multiple carrier codebook 312 in accordance with the first example codebook embodiment achieves a minimum Hamming distance 604 equal to five (5). Equivalent manipulations of this codebook likewise maintain the minimum Hamming distance of five.
- a multiple carrier codebook 312 in accordance with the second example codebook embodiment achieves a minimum Hamming distance 604 equal to four (4). Equivalent manipulations of this codebook likewise maintain the minimum Hamming distance of four.
- FIG. 6B is a block diagram 600B that depicts example code word pairs 606 having opposite meanings. As illustrated, block diagram 600B includes four code word pairs 606, eight code words 402, and a maximum code word separation indication 608. Each code word pair 606 includes two code words 402 that have opposite meanings.
- Code word pair 606ab includes code word 402a (ACK/DTX) and code word 402b (NACK/DTX).
- Code word pair 606cd includes code word 402c (DTX/ACK) and code word 402d (DTX/NACK).
- Code word pair 606ef includes code word 402e (NACK/ACK) and code word 402f (ACK/NACK).
- Code word pair 606gh includes code word 402g (ACK/ACK) and code word 402h (NACK/NACK).
- the code word separation is configured to be a maximum codeword separation 608 between any two code words 402 of a code word pair 606 in which the included code words have opposite meanings. For example, there is a maximum code word separation 608 between code words 402a and 402b. Similarly, there is a maximum code word separation 608 between code words 402e and 402f. For codebooks having code words 402 of length ten, the maximum code word separation 608 is ten.
- a remote terminal is enabled to signal MC-HSDPA HARQ affirmative acknowledgements (or negative acknowledgements) using a codebook that differs from a single carrier codebook for the same system.
- the multiple carrier (including multiple cell) codebook contains the codebook used for single carrier (including single cell) HARQ acknowledgement signaling as a sub-codebook thereof.
- the pair-wise Hamming distance of the new codebook is enhanced under the sub-codebook constraints. This approach can be extended to cover the case of MIMO extension to multiple carrier (or multiple cell) operations.
- a remote terminal is to use the DC-HSDPA HS-DPCCH format regardless of whether or not a HS-SCCH order deactivating the DC-HSDPA operation has been received.
- These superfluous bits in the second CQI field may be used in any of a number of different ways.
- Example uses of the superfluous bits of the second CQI field are described as follows.
- the CQI for the second carrier can be measured and reported even though the wireless network node will not currently schedule the remote terminal on the second carrier. These reported measurements may nevertheless be used by the wireless network node. For instance, a wireless network node may determine whether or not it is appropriate to reactivate the DC-HSDPA operation.
- the CQI for the first carrier may be reported twice in order to achieve a kind of repetition coding of the CQI. This repetition coding may improve the uplink coverage for the CQI information.
- an un-assigned/unused CQI value (e.g., currently the value 31 is not used) may be reported so as to indicate to the wireless network node that the remote terminal assumes that the DC-HSDPA operation is currently deactivated.
- two (10,5) codes may be used for coding the CQIs (i.e., one for each carrier/cell).
- Certain implementations may involve a combination of the DC-HSDPA feature and the MIMO HSDPA feature.
- a new format may be utilized.
- the information corresponding to the first MIMO stream may be mapped to a first HS-DPCCH code
- the information corresponding to the second MIMO stream may be mapped to a second HS-DPCCH code.
- the first HS-DPCCH code may be similar to the DC-HSDPA HS-DPCCH format described above.
- the second HS-DPCCH code may be transmitted in parallel with the first HS-DPCCH code.
- FIG. 7 is a block diagram 700 of example devices 702 that may be used to implement embodiments for multiple carrier acknowledgment signaling.
- block diagram 700 includes two devices 702a and 702b, human-device interface equipment 712, and one or more networks 716.
- each device 702 may include at least one processor 704, one or more memories 706, one or more input/output interfaces 708, and at least one interconnection 714.
- Memory 706 may include processor-executable instructions 710.
- Network(s) 716 may be, by way of example but not limitation, an internet, an intranet, an Ethernet, a public network, a private network, a cable network, a digital subscriber line (DSL) network, a telephone network, a wired network, a wireless network, some combination thereof, and so forth.
- Device 702a and device 702b may communicate over network(s) 716.
- device 702 may represent any processing-capable device.
- Processor 704 may be implemented using any applicable processing-capable technology, and one may be realized as a general-purpose or a special-purpose processor. Examples include, but are not limited to, a central processing unit (CPU), a digital signal processor (DSP), a microprocessor, some combination thereof, and so forth.
- Memory 706 may be any available memory that is included as part of and/or is accessible by device 702. It includes volatile and non-volatile memory, removable and non-removable memory, hard-coded logic, combinations thereof, and so forth.
- Interconnection 714 interconnects the components of device 702.
- Interconnection 714 may be realized as a bus or other connection mechanism and may directly or indirectly interconnect various components.
- I/O interfaces 708 may include (i) a network interface for monitoring and/or communicating across network 716, (ii) a display device interface for displaying information on a display screen, (iii) one or more human-device interfaces, and so forth.
- Example network interfaces include, but are not limited to, a radio or transceiver (e.g., a transmitter and/or a receiver), a modem, a network card, some combination thereof, and so forth.
- Human-device interface equipment 712 may be integrated with or discrete from device 702.
- processor 704 is capable of executing, performing, and/or otherwise effectuating processor-executable instructions, such as processor-executable instructions 710.
- Memory 706 is comprised of one or more processor-accessible memories.
- memory 706 may include processor-executable instructions 710 that are executable by processor 704 to effectuate the performance of functions by device 702.
- Processor-executable instructions 710 may be embodied as software, firmware, hardware, fixed logic circuitry, some combination thereof, and so forth.
- Processor 704 and processor-executable instructions 710 of memory 706 may be realized separately (e.g., as a DSP executing code) or integrated (e.g., as part of an application-specific integrated circuit (ASIC)).
- ASIC application-specific integrated circuit
- one device 702 may comprise a first device 302a (e.g., a wireless network node 102), and another device 702 may comprise a second device 302b (e.g., a remote terminal 104) (of FIGS. 1 and 3 ).
- Processor-executable instructions 710 may comprise, for example, the components and/or units of FIGS. 3 , 4 , 6A, and 6B (e.g., a communication confirmation unit 308, a multiple carrier codebook 312, etc.).
- processor-executable instructions 710 When processor-executable instructions 710 are executed by processor 704, the functions that are described herein may be effectuated.
- Example functions include, but are not limited to, those that are illustrated by flow diagram 500 (of FIG. 5 ) and those that are enabled by the example multiple carrier codebooks that are described herein above, as well as those that are embodied by the other features that are described herein.
- certain embodiments achieve an enhanced minimum Hamming distance for a codebook having code words that jointly encode ACK/NACK signaling for multiple carriers.
- Another advantage of certain embodiments is that PRE and POST operations may be supported (e.g., by including a preamble code word and a postamble code word that are compatible with one or more previous releases of a wireless standard). More specifically, for a first example codebook embodiment, a multiple carrier codebook having ten total code words achieves a minimum Hamming distance of five across the ten total code words, with five being the largest possible minimum Hamming distance for any codebook having 10 code words of length 10.
- a multiple carrier codebook having eight code words achieves a minimum Hamming distance of four between any two code word pairs (e.g., excluding preamble and postamble code words). Furthermore, another advantage of these embodiments is that codebook ambiguity may be avoided when a remote terminal fails to detect an HS-SCCH order because a multiple carrier codebook can be configured to include a single carrier codebook as a sub-codebook or subset thereof. Still yet another advantage of certain embodiments is that a largest code word separation for messages having opposite meanings may be achieved.
- FIGS. 1-7 The devices, features, functions, methods, steps, schemes, data structures, procedures, components, etc. of FIGS. 1-7 are illustrated in diagrams that are divided into multiple blocks and other elements. However, the order, interconnections, interrelationships, layout, etc. in which FIGS. 1-7 are described and/or shown are not intended to be construed as limiting, for any number of the blocks and/or other elements may be modified, combined, rearranged, augmented, omitted, etc. in any manner to implement one or more systems, methods, devices, memory, apparatuses, arrangements, etc. for multiple carrier acknowledgment signaling.
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Quality & Reliability (AREA)
- Mobile Radio Communication Systems (AREA)
- Detection And Prevention Of Errors In Transmission (AREA)
Claims (20)
- Verfahren in einem entfernten Terminal zur Bestätigung von Uplink-Signalisierung in einem Mehrträgermodus, wobei das Verfahren die folgenden Schritte umfasst:Bestimmen eines Codeworts, das Bestätigungssignalisierung für mindestens zwei Träger aus einem Mehrträgercodebuch, das mindestens acht Codewörter beinhaltet, die derart definiert sind, dass sie ein Einzelträgercodebuch als ein Untercodebuch des Mehrträgercodebuchs aufweisen, gemeinsam codiert; undÜbertragen einer Uplink-Signalisierungsnachricht, die das bestimmte Codewort beinhaltet, von dem entfernten Terminal zu einem drahtlosen Netzwerkknoten,dadurch gekennzeichnet, dass das Mehrträgercodebuch die folgenden Werte beinhaltet
ACK/DTX = [1 1 1 1 1 1 1 1 1 1] NACK/DTX = [0 0 0 0 0 0 0 0 0 0] DTX/ACK = [1 1 1 1 1 0 0 0 0 0] DTX/NACK = [0 0 0 0 0 1 1 1 1 1] NACK/ACK = [0 0 1 1 0 0 1 1 0 0] ACK/NACK = [1 1 0 0 1 1 0 0 1 1] ACK/ACK = [1 0 1 0 1 0 1 0 1 0] NACK/NACK = [0 1 0 1 0 1 0 1 0 1] - Verfahren nach Anspruch 1, wobei der Mehrträgermodus einen Dualträgermodus umfasst.
- Verfahren nach Anspruch 2, wobei die mindestens zwei Träger einen ersten Träger und einen zweiten Träger umfassen; und wobei das ACK/DTX einer zustimmenden Bestätigung für den ersten Träger und keinem Empfang für den zweiten Träger entspricht, das NACK/DTX einer negativen Bestätigung für den ersten Träger und keinem Empfang für den zweiten Träger entspricht, das DTX/ACK keinem Empfang für den ersten Träger und einer zustimmenden Bestätigung für den zweiten Träger entspricht, das DTX/NACK keinem Empfang für den ersten Träger und einer negativen Bestätigung für den zweiten Träger entspricht, das NACK/ACK einer negativen Bestätigung für den ersten Träger und einer zustimmenden Bestätigung für den zweiten Träger entspricht, das ACK/NACK einer zustimmenden Bestätigung für den ersten Träger und einer negativen Bestätigung für den zweiten Träger entspricht, das ACK/ACK einer zustimmenden Bestätigung für den ersten Träger und einer zustimmenden Bestätigung für den zweiten Träger entspricht, und das NACK/NACK einer negativen Bestätigung für den ersten Träger und einer negativen Bestätigung für den zweiten Träger entspricht.
- Verfahren nach einem der vorstehenden Ansprüche, wobei das Mehrträgercodebuch weiter ein Präambelcodewort und ein Postambelcodewort beinhaltet, die mit mindestens einer Vermächtniseinzelträgerversion von Präambel- und Postabelcodewörtern kompatibel sind.
- Verfahren nach einem der vorstehenden Ansprüche, wobei das Mehrträgercodebuch, welches das Einzelträgercodebuch als ein Untercodebuch davon aufweist, eine genaue Uplink-Signalisierung selbst dann ermöglicht, wenn ein die Uplink-Signalisierungsnachricht empfangendes Gerät und ein die Uplink-Signalisierungsnachricht übertragendes Gerät bezüglich des Einzelträgercodebuchs gegen das Mehrträgercodebuch fehlgepaart werden.
- Verfahren nach einem der vorstehenden Ansprüche, wobei der Schritt des Übertragens einer Uplink-Signalisierungsnachricht den Schritt des Übertragens der Uplink-Signalisierungsnachricht, die das bestimmte Codewort beinhaltet, auf einem High Speed Dedicated Physical Control Channel, HS-DPCCH, umfasst.
- Verfahren nach einem der vorstehenden Ansprüche, weiter den Schritt des Übertragens von mindestens einem ersten und einem zweiten Channel Quality Indicator, CQI, -Feld umfassend, wenn der Mehrträgermodus deaktiviert ist.
- Verfahren Anspruch 7, wobei das zweite CQI-Feld einen CQI für einen zweiten Träger umfasst.
- Verfahren Anspruch 7, wobei das erste CQI-Feld und das zweite CQI-Feld jeweils einen CQI für einen ersten Träger umfassen.
- Verfahren Anspruch 7, wobei das zweite CQI-Feld einen Wert zum Anzeigen, dass der Mehrträgermodus deaktiviert ist, umfasst.
- Verfahren nach einem der vorstehenden Ansprüche, weiter die folgenden Schritte umfassend:Mappen von Informationen, die einem ersten Multiple-Input Multiple-Output, MIMO, -Strom entsprechen, zu einem Codewort aus dem Mehrträgercodebuch für eine erste Codewortnachricht; undMappen von Informationen, die einem zweiten MIMO-Strom entsprechen, zu einem Codewort aus dem Mehrträgercodebuch für eine zweite Codewortnachricht,wobei der Schritt des Übertragens einer Uplink-Signalisierungsnachricht den Schritt des Übertragens der ersten Codewortnachricht parallel mit der zweiten Codewortnachricht umfasst.
- Verfahren nach einem der vorstehenden Ansprüche, wobei die Uplink-Signalisierung hybride Automatic Repeat Request, HARQ, Uplink-Signalisierung umfasst.
- Verfahren nach einem der vorstehenden Ansprüche, wobei der Mehrträgermodus einen Mehrzellenmodus umfasst, in welchem ein erster Träger der mindestens zwei Träger mit einer ersten Zelle assoziiert wird und ein zweiter Träger der mindestens zwei Träger mit einer zweiten Zelle assoziiert wird.
- Verfahren nach einem der vorstehenden Ansprüche, weiter die folgenden Schritte umfassend:Bestimmen, ob eine oder mehrere Downlink-Kommunikationen auf einem oder mehreren erwarteten Träger empfangen werden; undBestimmen eines Empfangsszenarios auf Grundlage der einen oder mehreren Downlink-Kommunikationen und der einen oder mehreren erwarteten Träger,wobei der Schritt des Bestimmens eines Codeworts den Schritt des Bestimmens desjenigen Codeworts aus dem Mehrträgercodebuch, das eine Bedeutung aufweist, die dem bestimmten Empfangsszenario entspricht, umfasst.
- Entferntes Terminal (104, 702), das angepasst ist, um Bestätigung von Uplink-Signalisierung in einem Mehrträgermodus auszuführen, wobei das entfernte Terminal umfasst:mindestens einen Speicher (706); undeinen oder mehrere Prozessoren (704), um:ein Codewort zu bestimmen, das Bestätigungssignalisierung für mindestens zwei Träger aus einem Mehrträgercodebuch, das mindestens acht Codewörter beinhaltet, die derart definiert sind, dass sie ein Einzelträgercodebuch als ein Untercodebuch des Mehrträgercodebuchs aufweisen, gemeinsam codiert; undeine Uplink-Signalisierungsnachricht, die das bestimmte Codewort beinhaltet, von dem entfernten Terminal zu einem drahtlosen Netzwerkknoten zu übertragen;dadurch gekennzeichnet, dass das Mehrträgercodebuch die folgenden Werte beinhaltet
ACK/DTX = [1 1 1 1 1 1 1 1 1 1] NACK/DTX = [0 0 0 0 0 0 0 0 0 0] DTX/ACK = [1 1 1 1 1 0 0 0 0 0] DTX/NACK = [0 0 0 0 0 1 1 1 1 1] NACK/ACK = [0 0 1 1 0 0 1 1 0 0] ACK/NACK = [1 1 0 0 1 1 0 0 1 1] ACK/ACK = [1 0 1 0 1 0 1 0 1 0] NACK/NACK = [0 1 0 1 0 1 0 1 0 1] - Entferntes Terminal nach Anspruch 15, wobei der Mehrträgermodus einen Dualträgermodus umfasst.
- Entferntes Terminal nach Anspruch 15 oder 16, wobei das Mehrträgercodebuch weiter ein Präambelcodewort und ein Postambelcodewort beinhaltet, die mit mindestens einer Vermächtniseinzelträgerversion von Präambel- und Postabelcodewörtern kompatibel sind.
- Entferntes Terminal nach einem der Ansprüche 15 bis 17, wobei der Mehrträgermodus einen Mehrzellenmodus umfasst, in welchem ein erster Träger der mindestens zwei Träger mit einer ersten Zelle assoziiert wird und ein zweiter Träger der mindestens zwei Träger mit einer zweiten Zelle assoziiert wird.
- Verfahren in einem drahtlosen Netzwerkknoten zur Bestätigung von Uplink-Signalisierung in einem Mehrträgermodus, wobei das Verfahren die folgenden Schritte umfasst:Empfangen einer Uplink-Signalisierungsnachricht, die ein Codewort beinhaltet, das Bestätigungssignalisierung für mindestens zwei Träger gemeinsam codiert, von einem entfernten Terminal an dem drahtlosen Netzwerkknoten; undDekodieren des Codeworts unter Verwendung eines Mehrträgercodebuchs, das mindestens acht Codewörter beinhaltet, die derart definiert sind, dass sie ein Einzelträgercodebuch als ein Untercodebuch des Mehrträgercodebuchs aufweisen,dadurch gekennzeichnet, dass das Mehrträgercodebuch die folgenden Werte beinhaltet
ACK/DTX = [1 1 1 1 1 1 1 1 1 1] NACK/DTX = [0 0 0 0 0 0 0 0 0 0] DTX/ACK = [1 1 1 1 1 0 0 0 0 0] DTX/NACK = [0 0 0 0 0 1 1 1 1 1] NACK/ACK = [0 0 1 1 0 0 1 1 0 0] ACK/NACK = [1 1 0 0 1 1 0 0 1 1] ACK/ACK = [1 0 1 0 1 0 1 0 1 0] NACK/NACK = [0 1 0 1 0 1 0 1 0 1] - Drahtloser Netzwerkknoten (102, 702), der angepasst ist, um Bestätigung von Uplink-Signalisierung in einem Mehrträgermodus auszuführen, wobei der drahtlose Netzwerkknoten umfasst:mindestens einen Speicher (706); undeinen oder mehrere Prozessoren (704), um:eine Uplink-Signalisierungsnachricht, die ein Codewort beinhaltet, das Bestätigungssignalisierung für mindestens zwei Träger gemeinsam codiert, von einem entfernten Terminal an dem drahtlosen Netzwerkknoten zu empfangen; unddas Codewort unter Verwendung eines Mehrträgercodebuchs zu dekodieren, das mindestens acht Codewörter beinhaltet, die derart definiert sind, dass sie ein Einzelträgercodebuch als ein Untercodebuch des Mehrträgercodebuchs aufweisen,dadurch gekennzeichnet, dass das Mehrträgercodebuch die folgenden Werte beinhaltet
ACK/DTX = [1111111111] NACK/DTX = [0 0 0 0 0 0 0 0 0 0] DTX/ACK = [1 1 1 1 1 0 0 0 0 0] DTX/NACK = [0 0 0 0 0 1 1 1 1 1] NACK/ACK = [0 0 1 1 0 0 1 1 0 0] ACK/NACK = [1 1 0 0 1 1 0 0 1 1] ACK/ACK = [1 0 1 0 1 0 1 0 1 0] NACK/NACK = [0 1 0 1 0 1 0 1 0 1]
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US9934108P | 2008-09-23 | 2008-09-23 | |
US10128808P | 2008-09-30 | 2008-09-30 | |
US12/502,506 US7924754B2 (en) | 2008-09-23 | 2009-07-14 | Multiple carrier acknowledgment signaling |
PCT/IB2009/006918 WO2010035103A1 (en) | 2008-09-23 | 2009-09-21 | Multiple carrier acknowledgment signaling |
EP09786270.0A EP2353243B1 (de) | 2008-09-23 | 2009-09-21 | Mehrträger-bestätigungssignalisierung |
EP11168917.0A EP2378693B1 (de) | 2008-09-23 | 2009-09-21 | Mehrfachträgerbestätigungssignalisierung |
Related Parent Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP11168917.0A Division EP2378693B1 (de) | 2008-09-23 | 2009-09-21 | Mehrfachträgerbestätigungssignalisierung |
EP09786270.0A Division EP2353243B1 (de) | 2008-09-23 | 2009-09-21 | Mehrträger-bestätigungssignalisierung |
Publications (2)
Publication Number | Publication Date |
---|---|
EP3487099A1 EP3487099A1 (de) | 2019-05-22 |
EP3487099B1 true EP3487099B1 (de) | 2019-12-18 |
Family
ID=42037581
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP09786270.0A Active EP2353243B1 (de) | 2008-09-23 | 2009-09-21 | Mehrträger-bestätigungssignalisierung |
EP11168917.0A Active EP2378693B1 (de) | 2008-09-23 | 2009-09-21 | Mehrfachträgerbestätigungssignalisierung |
EP18214563.1A Active EP3487099B1 (de) | 2008-09-23 | 2009-09-21 | Mehrfachträgerbestätigungssignalisierung |
EP11163660A Ceased EP2378692A1 (de) | 2008-09-23 | 2009-09-21 | Mehrfachträgerbestätigungssignalisierung |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP09786270.0A Active EP2353243B1 (de) | 2008-09-23 | 2009-09-21 | Mehrträger-bestätigungssignalisierung |
EP11168917.0A Active EP2378693B1 (de) | 2008-09-23 | 2009-09-21 | Mehrfachträgerbestätigungssignalisierung |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP11163660A Ceased EP2378692A1 (de) | 2008-09-23 | 2009-09-21 | Mehrfachträgerbestätigungssignalisierung |
Country Status (15)
Country | Link |
---|---|
US (1) | US7924754B2 (de) |
EP (4) | EP2353243B1 (de) |
JP (1) | JP5593319B2 (de) |
KR (1) | KR101617755B1 (de) |
CN (2) | CN107070594B (de) |
BR (1) | BRPI0919401B1 (de) |
CA (1) | CA2738125C (de) |
DK (3) | DK3487099T3 (de) |
ES (2) | ES2779983T3 (de) |
IL (1) | IL211817A (de) |
PL (1) | PL2378693T3 (de) |
PT (2) | PT2378693T (de) |
RU (1) | RU2504909C2 (de) |
SG (1) | SG2012079711A (de) |
WO (1) | WO2010035103A1 (de) |
Families Citing this family (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7843989B2 (en) * | 2007-06-26 | 2010-11-30 | Sharp Laboratories Of America, Inc. | Systems and methods for embedding a first signal in the coding of a second signal |
WO2010099653A1 (zh) | 2009-03-03 | 2010-09-10 | 深圳华为通信技术有限公司 | 信号编码方法及装置、联合反馈信号编码方法 |
KR101011988B1 (ko) * | 2009-03-13 | 2011-01-31 | 한국항공대학교산학협력단 | 다양한 개수의 안테나들을 구비하는 사용자 단말들을 포함하는 통신시스템에서 피드백 정보 송수신 방법 및 장치 |
EP2592774B1 (de) | 2009-03-17 | 2015-09-23 | Huawei Technologies Co., Ltd. | Verfahren und Vorrichtung zur Codierung eines Feedbacksignals |
US8345614B2 (en) * | 2009-03-17 | 2013-01-01 | Qualcomm Incorporated | Single channelization code HARQ feedback for DC-HSDPA +MIMO |
US9401779B2 (en) | 2009-03-29 | 2016-07-26 | Lg Electronics Inc. | Method for transmitting control information in wireless communication system and apparatus therefor |
CN104038323B (zh) | 2009-04-21 | 2018-01-05 | 光学无线技术有限责任公司 | 终端、基站及在其中使用的方法 |
PL2464048T3 (pl) * | 2009-08-07 | 2019-03-29 | Sun Patent Trust | Terminal i sposób sterowania ponownym przesyłaniem |
EP2487980A4 (de) * | 2009-10-06 | 2016-08-10 | Ntt Docomo Inc | Basisstation, vorrichtung und mobiles kommunikationsverfahren |
US9049618B2 (en) * | 2009-12-16 | 2015-06-02 | Innovative Sonic Corporation | Method and apparatus for channel measurement reports in a wireless communication system |
EP2524557B1 (de) * | 2010-01-15 | 2020-04-08 | Nokia Technologies Oy | Aktivierung von komponententrägern in einer trägeraggregation |
US8477672B2 (en) | 2010-02-10 | 2013-07-02 | Qualcomm Incorporated | 4C-HSDPA acknowledgment signaling |
EP2542006B1 (de) * | 2010-02-22 | 2018-11-21 | Sharp Kabushiki Kaisha | Mobilstationsvorrichtung und kommunikationsverfahren |
WO2011134522A1 (en) * | 2010-04-29 | 2011-11-03 | Telefonaktiebolaget L M Ericsson (Publ) | Efficient harq receiver for hsdpa |
KR101425630B1 (ko) * | 2010-04-30 | 2014-07-31 | 노키아 솔루션스 앤드 네트웍스 오와이 | 타이밍 불확실성 컴포넌트 캐리어 (재)구성/활성화/비활성화 기간 동안 캐리어 애그리케이션을 위한 ul ack/nack 피드백의 지원 |
EP2569890A4 (de) * | 2010-05-08 | 2017-09-06 | LG Electronics Inc. | Fehlerweiterleitungsschutz in nicht-binären mehrfach-ack/nacks |
CN101944985B (zh) * | 2010-09-20 | 2015-03-25 | 中兴通讯股份有限公司 | 一种信道状态信息反馈方法 |
US8675554B2 (en) * | 2010-11-08 | 2014-03-18 | Intel Corporation | Wireless communication device and method for performing neighbor cell analysis during continuous packet connectivity mode |
EP2661835A1 (de) * | 2011-01-07 | 2013-11-13 | InterDigital Patent Holdings, Inc. | Verfahren und vorrichtung zum senden von feedback für mehrzellige hsdpa-operationen |
US8923196B2 (en) * | 2012-03-16 | 2014-12-30 | Blackberry Limited | Uplink control channel resource collision resolution in carrier aggregation systems |
US9007963B2 (en) | 2012-03-16 | 2015-04-14 | Blackberry Limited | Uplink control channel resource mapping in carrier aggregation systems |
US8923255B2 (en) | 2012-03-16 | 2014-12-30 | Blackberry Limited | Uplink control channel resource collision avoidance in carrier aggregation systems |
WO2013141582A1 (ko) * | 2012-03-19 | 2013-09-26 | 엘지전자 주식회사 | Harq 수행 방법 및 무선기기 |
EP2915300A1 (de) | 2012-11-02 | 2015-09-09 | Telefonaktiebolaget L M Ericsson (Publ) | Netzwerkknoten, benutzerknoten und kanalmessverfahren |
US9439141B2 (en) | 2013-04-09 | 2016-09-06 | Telefonaktiebolaget L M Ericsson (Publ) | Decoding algorithm for the HS-DPCCH HARQ message exploiting the pre-and postambles |
US20140355703A1 (en) * | 2013-06-03 | 2014-12-04 | Broadcom Corporation | Codeword Structure For Multi-Structured Codebooks |
RU2658801C2 (ru) * | 2014-03-24 | 2018-06-22 | Телефонактиеболагет Лм Эрикссон (Пабл) | Способы управления прерываниями при множестве деактивированных scell |
US10355829B2 (en) | 2014-07-29 | 2019-07-16 | Panasonic Intellectual Property Corporation Of America | Conveying number of required HARQ repetitions for coverage enhancement |
WO2018230999A1 (ko) * | 2017-06-15 | 2018-12-20 | 엘지전자 주식회사 | 무선 통신 시스템에서 단말과 기지국 간 확인 응답 정보를 송수신하는 방법 및 이를 지원하는 장치 |
CN110741584B (zh) * | 2017-06-15 | 2022-06-07 | Lg 电子株式会社 | 在无线通信系统中用于发送和接收确认的方法及装置 |
JP6757860B2 (ja) * | 2017-06-28 | 2020-09-23 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | 構成無線ノードにより構成されたharqコードブックに基づくユーザ装置および受信無線ノードの動作 |
CN107682020B (zh) * | 2017-10-26 | 2020-09-04 | 北京邮电大学 | 一种基于Turbo码的编码、解码方法及装置 |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8208364B2 (en) * | 2002-10-25 | 2012-06-26 | Qualcomm Incorporated | MIMO system with multiple spatial multiplexing modes |
US7499474B2 (en) * | 2005-04-13 | 2009-03-03 | Nokia Corporation | Efficient HARQ control and channel quality feedback reporting for multicarrier systems |
US7944992B2 (en) * | 2005-06-17 | 2011-05-17 | Telefonaktiebolaget Lm Ericsson (Publ) | Multicarrier CDMA system |
DE102006004168A1 (de) * | 2005-08-04 | 2007-02-08 | Robert Bosch Gmbh | Überprüfung eines Adressdecoders |
US20070165738A1 (en) * | 2005-10-27 | 2007-07-19 | Barriac Gwendolyn D | Method and apparatus for pre-coding for a mimo system |
US7934137B2 (en) * | 2006-02-06 | 2011-04-26 | Qualcomm Incorporated | Message remapping and encoding |
CN101141756A (zh) * | 2006-09-08 | 2008-03-12 | 华为技术有限公司 | 数据传输模式设置和检测装置及方法 |
US8176376B2 (en) * | 2006-10-02 | 2012-05-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Optimal error protection coding for MIMO ACK/NACK/POST information |
WO2008041098A2 (en) * | 2006-10-02 | 2008-04-10 | Nokia Corporation | Apparatus, method and computer program product providing hybrid arq feedback for hsdpa mimo |
US20090141690A1 (en) * | 2007-10-01 | 2009-06-04 | Qualcomm Incorporated | Method and apparatus for uplink control signaling |
EP2213034B1 (de) * | 2007-10-02 | 2014-08-27 | Nokia Solutions and Networks Oy | Verbesserte ack-/nack-dtx-erkennung und signalisierung des nichtempfangs einer freigabenachricht für downlink-zuweisung |
US8477734B2 (en) * | 2008-03-25 | 2013-07-02 | Qualcomm Incorporated | Reporting of ACK and CQI information in a wireless communication system |
-
2009
- 2009-07-14 US US12/502,506 patent/US7924754B2/en active Active
- 2009-09-21 SG SG2012079711A patent/SG2012079711A/en unknown
- 2009-09-21 KR KR1020117009228A patent/KR101617755B1/ko active IP Right Grant
- 2009-09-21 PL PL11168917T patent/PL2378693T3/pl unknown
- 2009-09-21 BR BRPI0919401-0A patent/BRPI0919401B1/pt active IP Right Grant
- 2009-09-21 PT PT11168917T patent/PT2378693T/pt unknown
- 2009-09-21 EP EP09786270.0A patent/EP2353243B1/de active Active
- 2009-09-21 CN CN201710076360.3A patent/CN107070594B/zh active Active
- 2009-09-21 RU RU2011116064/08A patent/RU2504909C2/ru active
- 2009-09-21 DK DK18214563.1T patent/DK3487099T3/da active
- 2009-09-21 DK DK11168917.0T patent/DK2378693T3/en active
- 2009-09-21 ES ES18214563T patent/ES2779983T3/es active Active
- 2009-09-21 CN CN200980147778.2A patent/CN102308506B/zh active Active
- 2009-09-21 CA CA2738125A patent/CA2738125C/en active Active
- 2009-09-21 ES ES09786270.0T patent/ES2635192T3/es active Active
- 2009-09-21 DK DK09786270.0T patent/DK2353243T3/en active
- 2009-09-21 EP EP11168917.0A patent/EP2378693B1/de active Active
- 2009-09-21 EP EP18214563.1A patent/EP3487099B1/de active Active
- 2009-09-21 PT PT182145631T patent/PT3487099T/pt unknown
- 2009-09-21 WO PCT/IB2009/006918 patent/WO2010035103A1/en active Application Filing
- 2009-09-21 JP JP2011527421A patent/JP5593319B2/ja active Active
- 2009-09-21 EP EP11163660A patent/EP2378692A1/de not_active Ceased
-
2011
- 2011-03-20 IL IL211817A patent/IL211817A/en active IP Right Grant
Non-Patent Citations (1)
Title |
---|
None * |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3487099B1 (de) | Mehrfachträgerbestätigungssignalisierung | |
US9258096B2 (en) | Method and system for supporting multiple hybrid automatic repeat request processes per transmission time interval | |
US8582538B2 (en) | Scheduling grant information signaling in wireless communication system | |
US8239721B2 (en) | HARQ process utilization in multiple carrier wireless communications | |
EP2289196B1 (de) | Verfahren und vorrichtung in einem telekommunikationsnetzwerk | |
US20110032925A1 (en) | Method of transmitting group ack/nack in a communication system | |
US20090313516A1 (en) | Enhanced hybrid automatic repeat request for long term evolution | |
MX2010011779A (es) | Señalizacion de configuracion de antena multiple en sistema de comunicación inalambrica. | |
CN102754379B (zh) | 4c-hsdpa确认信令 | |
CN102238626B (zh) | 一种多载波系统的优化方法和系统 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED |
|
AC | Divisional application: reference to earlier application |
Ref document number: 2378693 Country of ref document: EP Kind code of ref document: P Ref document number: 2353243 Country of ref document: EP Kind code of ref document: P |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE |
|
17P | Request for examination filed |
Effective date: 20190603 |
|
RBV | Designated contracting states (corrected) |
Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: GRANT OF PATENT IS INTENDED |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04L 1/00 20060101AFI20190624BHEP Ipc: H04L 1/18 20060101ALI20190624BHEP Ipc: H04L 1/16 20060101ALI20190624BHEP |
|
INTG | Intention to grant announced |
Effective date: 20190712 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE PATENT HAS BEEN GRANTED |
|
AC | Divisional application: reference to earlier application |
Ref document number: 2378693 Country of ref document: EP Kind code of ref document: P Ref document number: 2353243 Country of ref document: EP Kind code of ref document: P |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602009060786 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 1215735 Country of ref document: AT Kind code of ref document: T Effective date: 20200115 |
|
REG | Reference to a national code |
Ref country code: SE Ref legal event code: TRGR |
|
REG | Reference to a national code |
Ref country code: DK Ref legal event code: T3 Effective date: 20200319 Ref country code: PT Ref legal event code: SC4A Ref document number: 3487099 Country of ref document: PT Date of ref document: 20200323 Kind code of ref document: T Free format text: AVAILABILITY OF NATIONAL TRANSLATION Effective date: 20200309 |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: FP |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200318 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200319 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D Ref country code: NO Ref legal event code: T2 Effective date: 20191218 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FG2A Ref document number: 2779983 Country of ref document: ES Kind code of ref document: T3 Effective date: 20200821 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20200418 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602009060786 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1215735 Country of ref document: AT Kind code of ref document: T Effective date: 20191218 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20200921 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20200930 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20200921 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20200930 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20200930 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20200930 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: TR Payment date: 20220902 Year of fee payment: 14 Ref country code: SE Payment date: 20220927 Year of fee payment: 14 Ref country code: PT Payment date: 20220906 Year of fee payment: 14 Ref country code: NO Payment date: 20220928 Year of fee payment: 14 Ref country code: IE Payment date: 20220927 Year of fee payment: 14 Ref country code: DK Payment date: 20220928 Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20220926 Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: IT Payment date: 20220926 Year of fee payment: 14 Ref country code: ES Payment date: 20221003 Year of fee payment: 14 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20191218 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: NL Payment date: 20230926 Year of fee payment: 15 Ref country code: GB Payment date: 20230927 Year of fee payment: 15 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20230927 Year of fee payment: 15 |
|
REG | Reference to a national code |
Ref country code: DK Ref legal event code: EBP Effective date: 20230930 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20240321 |
|
REG | Reference to a national code |
Ref country code: SE Ref legal event code: EUG |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230921 |