EP2507931B1 - Procédé et système d' identification de porteuse de données - Google Patents

Procédé et système d' identification de porteuse de données Download PDF

Info

Publication number
EP2507931B1
EP2507931B1 EP10816318.9A EP10816318A EP2507931B1 EP 2507931 B1 EP2507931 B1 EP 2507931B1 EP 10816318 A EP10816318 A EP 10816318A EP 2507931 B1 EP2507931 B1 EP 2507931B1
Authority
EP
European Patent Office
Prior art keywords
carriers
transmission control
carrier
control frame
list
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
Application number
EP10816318.9A
Other languages
German (de)
English (en)
Other versions
EP2507931A2 (fr
Inventor
Lijie Hu
Kan ZHENG
Lin Huang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Orange SA
Original Assignee
Orange SA
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Orange SA filed Critical Orange SA
Publication of EP2507931A2 publication Critical patent/EP2507931A2/fr
Application granted granted Critical
Publication of EP2507931B1 publication Critical patent/EP2507931B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1822—Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
    • 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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1893—Physical mapping arrangements
    • 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/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • 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/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • the present invention relates in general to telecommunication network functions and more specifically to telecommunication carrier identification.
  • 3GPP LTE Long Term Evolution
  • 3GPP Third Generation Partnership Project
  • Goals have included so far improving efficiency, lowering costs, improving services, making use of new spectrum opportunities, and better integration with open standards.
  • IMT International Mobile Telecommunication
  • IMT-Advanced has aimed at providing enhanced peak data rates to support advanced services and applications (100 Mbit/s for high and 1 Gbit/s for low mobility were established as targets for research). Altogether, future 3GPP LTE-Advanced systems will require wider system bandwidth, e.g. up to 100MHz, to achieve such high target peak data rates.
  • Carrier aggregation is a natural choice that could either meet the bandwidth extension requirement or ensure sufficient backward compatibility towards LTE Release-8.
  • Carrier Aggregation multiple Component Carriers (CCs) are aggregated according to the desired LTE-Advanced system bandwidth. These CCs are either LTE Release-8 compatible or designed specially to support new LTE Advanced features.
  • a LTE Release-8 user equipment may receive one of these component carriers, while an LTE-Advanced user equipment may simultaneously access multiple component carriers.
  • carrier aggregation does not require extensive changes of LTE physical layer structure, and can reuse the most of the existing implementations.
  • Hybrid Automatic Repeat Request is a variation of an Automatic Repeat Request (ARQ) error control method, which performs better ARQ, particularly over wireless channels.
  • ARQ Automatic Repeat Request
  • An example of HARQ also referred to as Type I HARQ, combines Forward Error Correction (FER) and ARQ by encoding a data block and error-detection information (such as Cyclic Redundancy Check (CRC)) with an error-correction code (such as e.g. Reed-Solomon code or Turbo code) prior to transmission.
  • FER Forward Error Correction
  • CRC Cyclic Redundancy Check
  • error-correction code such as e.g. Reed-Solomon code or Turbo code
  • the receiver may derive the correct data block. If the channel quality is good enough, all transmission errors should be correctable, and the receiver may derive the correct data block. If the channel quality is not good enough and not all transmission errors can be corrected, the receiver detects this situation using the error-detection code, then the received coded data block may be discarded or stored and a retransmission is requested by the receiver, similar to ARQ. In practice, incorrectly received coded data blocks (i.e. erroneous data blocks) are often stored at the receiver rather than discarded, and when the retransmitted block is received, the two blocks are combined (chase combining) before being fed to the decoder of the error-correction code. This can increase the probability of successful decoding.
  • Type II/III HARQ or incremental redundancy HARQ, where different (re)transmissions are coded differently rather than repeating the same coded bits as in chase combining. Performance is improved, since coding is effectively done across retransmissions.
  • the difference between type III HARQ and type II HARQ is that the retransmission packets in Type III HARQ can be decoded by themselves.
  • the HARQ method uses at least one HARQ process and some HARQ process entities, here under referred to, respectively, as set of transmission control frames and transmission control frames.
  • Each transmission control frame may comprise one or more header and one or more data blocks.
  • Each transmission control frames are transmitted between an emitter and a receiver in a telecommunication network. In other words, data blocks are transmitted using transmission control frames.
  • the plurality of carriers may be divided into time intervals or time slots, wherein each transmission control frame is transmitted on each carrier at each time interval (as described here under in reference to Figure 3 ).
  • CA Carrier Aggregation
  • UE User Equipment
  • CCs Component Carriers
  • re-transmission of data blocks may be allowed across CCs in order to better exploit frequency diversity.
  • errors detected in a data block transmitted in a first carrier are less likely to happen in retransmission of the same data block on another carrier at a different frequency.
  • HARQ process entities may be grouped into sets, each set being dedicated, for example, to a given user equipment or data stream.
  • Multiple stop-and-wait HARQ process entities may be transmitted in parallel on the same or different CC(s) so that while one HARQ process is waiting for an acknowledgement for a given HARQ process entity other HARQ process entities may use the carrier(s) to send additional packets.
  • HARQ process or transmission control frame process each comprising a plurality of HARQ process entities or transmission control frames.
  • the number of HARQ process entities should be in accordance with the roundtrip time between the emitter and the receiver to allow for continuous transmission, including the respective processing time of the data blocks, HARQ process entities and HARQ process.
  • the emitter and the receiver may be a user equipment (UE) and a eNodeB (station or radio controller element of the 3GPP LTE network) or vice-and-versa.
  • UE user equipment
  • eNodeB station or radio controller element of the 3GPP LTE network
  • the number of HARQ process entities may be configurable. For example, a set of eight HARQ process entities or transmission control frames may be used for a given component carrier or user equipment or data stream.
  • one HARQ process i.e. a set of HARQ process entities
  • the UE To perform operations such as soft combining (cohesion of data streams from multiple base stations or eNodeB that share a common time line and are operated according to it), in-sequence delivery and so on, the UE has to identify the HARQ process entities or transmission control frames of the carrier(s) it transmits on.
  • HARQ process sets may be flexibly mapped to carriers up-link and down-link. It allows retransmission across carriers, which may derive higher frequency diversity gain or flexible scheduling gain.
  • additional bits are needed in the header (here under called transmission control frame indication) of each transmission control frame are needed to identify the previous carrier the transmission control frame was transmitted onto. This seems to be a large signalling overhead, especially when using many carriers.
  • This indication may be used for instance by an emitter to inform a receiver of which HARQ process set has been used in a control channel (such as e.g. a Physical Downlink Shared Channel (PDSCH) or a Physical Uplink Shared Channel (PUSCH)).
  • PDSCH Physical Downlink Shared Channel
  • PUSCH Physical Uplink Shared Channel
  • the invention proposes a method of coding identification of carriers from a list of carriers in a telecommunication network according to claim 1.
  • the invention also proposes a method of identifying carriers from a list of carriers in a telecommunication network according to claim 4.
  • the invention also proposes an emitter according to claim 7.
  • the invention also proposes a receiver according to claim 10.
  • the invention also proposes a system according to claim 13.
  • the invention also proposes a readable computer program according to claim 14.
  • the invention also proposes a readable computer program according to claim 15.
  • the CCs are ordered in an ascending/descending way and numbered for identification. Then, several signalling bits are associated to each transmission control frame to transmit, indicating the previous carrier the transmission control frame was transmitted onto. Finally, the receiver determines the corresponding relationship according to the received signalling bits.
  • This invention allows reducing the transmission control frame identification bits when transmission control frames are flexibly mapped onto up-link or down-link carriers.
  • the number of bits in the transmission control frame indication may be reduced to [log 2 n]+ [log 2 (n-1)]+...+ [log 2 2] bits at each time interval.
  • the signalling bits may be transmitted together in a single transmission control frame indication or separately in each transmission control frame indication.
  • the method and system according to the invention involve an emitter and a receiver.
  • the exemplary embodiment will be described hereafter in its application to a eNodeB and a user equipment of a wireless telecommunication network. Both may be either receiver or emitter.
  • the number of transmission control frames may correspond to the number of data blocks that may be sent while waiting for receiving a feed-back or acknowledgement message for the first transmission control block associated with the first sent data block.
  • the feed-back message may be sent by the receiver to inform the emitter that a given data block in a given transmission control frame was received either successfully or unsuccessfully.
  • a receiver receives a transmission control frame, it analyses the data block(s) comprised in the transmission data block to detect any error that may have occurred during the transmission of the transmission control frame. Error detection may be performed for example using existing error-detection or error-correction codes. When no error is detected, the analyzed received data block may be used to reconstruct the data stream associated with it at the receiver.
  • the error in the received data block may be due to quality of the carrier used for transmitting the corresponding control frame.
  • the emitter needs therefore the reschedule the transmission of the erroneous data block to the receiver onto a different carrier, using the same transmission control frame.
  • the allocation of carriers is performed carrier by carrier. Firstly, each data block to retransmit from the emitter is assigned to the same transmission control frame than the one previously used (i.e. the last transmission control frame used for previously send the data block). A carrier, preferably a different carrier from the one previously used, is allocated for transmitting said transmission control frame. Then, remaining or non-allocated carriers may be allocated to transmission control frame for transmitting data blocks that have never been transmitted yet.
  • Figure 3b describes an illustrative embodiment of the method according to the invention performed by the receiver.
  • the method allows identifying carriers from a list of carriers in a telecommunication network 105.
  • Each of the carriers allows the transmission of a transmission control frame.
  • Each of said transmission control frame comprises:
  • Transmission control frame c 0 is transmitted over carrier (a) (in other words, carrier (a) is allocated to transmission control frame b 0 ) and comprises an indication that it was transmitted at time interval t 0 on carrier (c).
  • Figure 5 describes an illustrative embodiment of the method according to the invention at the emitter (respectively receiver), wherein the signalling bits of the indications of a plurality of transmission control frames at the same time interval are grouped into a single transmission control frame.
  • indications may, in an alternative embodiment, be inserted (respectively retrieved) in one, or a plurality of, different transmission control frame(s) rather than in each corresponding transmission control frame.
  • Each indication may be easily derived from the sequence(s) of binary bits as long as they remain ordered.
  • the indication inserted (respectively retrieved) in the first transmission control frame is '10011' and there are four carriers at the total. Consequently, two bits are needed to first code (respectively identify) a carrier used at the previous corresponding time slot among the four carriers. Bits '10' correspond thus to the indication in the transmission control frame on the first carrier.
  • the carrier coded (respectively identified) by '10' is carrier (c) which is removed from the list of carriers. Then, as three carriers remain in the list of carriers, 2 bits are still needed to code (respectively identify) a carrier.
  • '01' indicates that the second carrier of the sequence (00, 01, 10, 11) corresponding to the list of remaining carriers (a, b and d), namely carrier (b), will be used (respectively was used) to transmit the same transmission control frame on time interval t 0 .
  • carriers for transmission control frames for retransmitted block may be allocated first by the emitter for ensuring frequency diversity.
  • carriers (a) and (b) may thus be respectively allocated to transmission control frames d 0 and a 0 .
  • Table 1 shows an example of the number of signalling bits that may be saved using the method according to the invention. The greater number of carriers is used, the more signalling bits are saved. Table 1 HARQ process indication bits comparison Number of CC Bits needed with the invention Bits needed in prior art Number of bits saved Proportion of bits saved 1 3 3 0 0 2 7 8 1 12.5% 3 12 15 3 20% 4 17 20 3 15% 5 23 30 7 23.3% 6 29 36 7 19.4%

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Time-Division Multiplex Systems (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)

Claims (15)

  1. Procédé permettant de coder l'identification de porteuses à partir d'une liste ordonnée de porteuses dans un réseau de télécommunication, chacune desdites porteuses étant en cours d'allocation à une trame de contrôle de transmission afin d'autoriser sa transmission, chaque dite trame de contrôle de transmission comprenant :
    - un bloc de données correspondant à un flux de données, et
    - une indication de la porteuse qui a été allouée précédemment à un bloc de données précédent correspondant audit flux de données,
    ledit procédé étant caractérisé en ce qu'il comprend en outre, pour chacune des porteuses en cours d'allocation prises dans l'ordre de ladite liste de porteuses, les actions suivantes :
    - déterminer (210) le nombre de bits binaires requis pour identifier le nombre de porteuses dans la liste de porteuses,
    - coder (220) l'indication, dans la trame de contrôle de transmission à laquelle ladite porteuse est en cours d'allocation, sur la base du nombre déterminé de bits binaires,
    - supprimer (230) ladite porteuse en cours d'allocation de la liste de porteuses ; et
    - renuméroter (240) les porteuses restantes dans la liste de porteuses.
  2. Procédé selon la revendication 1, ledit procédé comprenant en outre l'action d'insérer l'indication dans chaque trame de contrôle de transmission correspondante.
  3. Procédé selon la revendication 1, ledit procédé comprenant en outre l'action d'insérer l'indication pour chaque trame de contrôle de transmission sur chaque porteuse à un intervalle de temps dans une ou une pluralité de différentes trames de contrôle de transmission.
  4. Procédé permettant d'identifier des porteuses à partir d'une liste ordonnée de porteuses dans un réseau de télécommunication, chacune desdites porteuses étant en cours d'allocation à une trame de contrôle de transmission afin d'autoriser sa transmission, chaque dite trame de contrôle de transmission comprenant :
    - un bloc de données correspondant à un flux de données, et
    - une indication de la porteuse qui a été allouée précédemment à un bloc de données précédent correspondant au dit flux de données,
    ledit procédé étant caractérisé en ce qu'il comprend, pour chacune des porteuses en cours d'allocation prises dans l'ordre de ladite liste de porteuses, les actions suivantes :
    - identifier (260), dans la liste de porteuses, la porteuse qui a été allouée précédemment à un bloc de données précédent correspondant au dit flux de données, en utilisant l'indication dans ladite trame de contrôle de transmission donnée,
    - supprimer (270) la porteuse identifiée de la liste de porteuses ; et
    - renuméroter (280) les porteuses restantes dans la liste de porteuses.
  5. Procédé selon la revendication 4, comprenant en outre l'action de récupérer l'indication dans chaque trame de contrôle de transmission correspondante.
  6. Procédé selon la revendication 4, comprenant en outre l'action de récupérer l'indication d'une pluralité de trames de contrôle de transmission dans une ou une pluralité de différentes trames de contrôle de transmission.
  7. Emetteur permettant de coder l'identification de porteuses à partir d'une liste ordonnée de porteuses dans un réseau de télécommunication, chacune desdites porteuses étant en cours d'allocation à une trame de contrôle de transmission afin d'autoriser sa transmission, chaque dite trame de contrôle de transmission comprenant :
    - un bloc de données correspondant à un flux de données, et
    - une indication de la porteuse qui a été allouée précédemment à un bloc de données précédent correspondant au dit flux de données,
    ledit émetteur étant caractérisé en ce qu'il comprend, pour chacune des porteuses en cours d'allocation prises dans l'ordre de ladite liste de porteuses :
    - des moyens destinés à déterminer le nombre de bits binaires requis pour identifier le nombre de porteuses dans la liste de porteuses,
    - des moyens destinés à coder l'indication, dans la trame de contrôle de transmission à laquelle ladite porteuse est en cours d'allocation, sur la base du nombre déterminé de bits binaires,
    - des moyens destinés à supprimer ladite porteuse en cours d'allocation de la liste de porteuses ; et
    - des moyens destinés à renuméroter les porteuses restantes dans la liste de porteuses.
  8. Emetteur selon la revendication 7, ledit émetteur comprenant en outre des moyens destinés à insérer l'indication dans chaque trame de contrôle de transmission correspondante.
  9. Emetteur selon la revendication 7, ledit émetteur comprenant en outre des moyens destinés à insérer l'indication pour chaque trame de contrôle de transmission sur chaque porteuse à un intervalle de temps dans une ou une pluralité de différentes trames de contrôle de transmission.
  10. Récepteur permettant d'identifier des porteuses à partir d'une liste ordonnée de porteuses dans un réseau de télécommunication, chacune desdites porteuses étant allouée à une trame de contrôle de transmission afin d'autoriser sa transmission, chaque dite trame de contrôle de transmission comprenant :
    - un bloc de données correspondant à un flux de données, et
    - une indication de la porteuse qui a été allouée précédemment à un bloc de données précédent correspondant au dit flux de données,
    ledit récepteur étant caractérisé en ce qu'il comprend, pour chacune des porteuses en cours d'allocation prises dans l'ordre de ladite liste de porteuses qui est attribuée à une trame de contrôle de transmission reçue donnée :
    - des moyens destinés à identifier, dans la liste de porteuses, une porteuse qui a été allouée précédemment à un bloc de données précédent du flux de données, en utilisant l'indication dans ladite trame de contrôle de transmission donnée,
    - des moyens destinés à supprimer la porteuse identifiée de la liste de porteuses, et
    - des moyens destinés à renuméroter les porteuses restantes dans la liste de porteuses.
  11. Récepteur selon la revendication 10, ledit récepteur comprenant en outre l'action de récupérer l'indication dans chaque trame de contrôle de transmission correspondante.
  12. Récepteur selon la revendication 10, ledit récepteur comprenant en outre des moyens destinés à récupérer l'indication d'une pluralité de trames de contrôle de transmission dans une ou une pluralité de différentes trames de contrôle de transmission.
  13. Système, ledit système comprenant :
    - un réseau de télécommunication,
    - un émetteur selon la revendication 7, ledit émetteur étant dans ledit réseau de télécommunication,
    - un récepteur selon la revendication 10, ledit récepteur étant dans ledit réseau de télécommunication.
  14. Support lisible par ordinateur stockant des instructions exécutables par ordinateur permettant à un système informatique de mettre en oeuvre le procédé de l'une quelconque des revendications 1 à 3.
  15. Support lisible par ordinateur stockant des instructions exécutables par ordinateur permettant à un système informatique de mettre en oeuvre le procédé de l'une quelconque des revendications 4 à 6.
EP10816318.9A 2009-11-30 2010-11-30 Procédé et système d' identification de porteuse de données Active EP2507931B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2009075218 2009-11-30
PCT/IB2010/003435 WO2011064676A2 (fr) 2009-11-30 2010-11-30 Procédé et système de transmission de données

Publications (2)

Publication Number Publication Date
EP2507931A2 EP2507931A2 (fr) 2012-10-10
EP2507931B1 true EP2507931B1 (fr) 2018-07-18

Family

ID=43857848

Family Applications (1)

Application Number Title Priority Date Filing Date
EP10816318.9A Active EP2507931B1 (fr) 2009-11-30 2010-11-30 Procédé et système d' identification de porteuse de données

Country Status (3)

Country Link
US (1) US9008016B2 (fr)
EP (1) EP2507931B1 (fr)
WO (1) WO2011064676A2 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016121809A1 (fr) * 2015-01-29 2016-08-04 株式会社Ｎｔｔドコモ Terminal et système de communication
EP3249844B1 (fr) * 2015-02-17 2020-06-24 Huawei Technologies Co., Ltd. Procédé et appareil de traitement de données

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070142046A1 (en) * 2005-12-15 2007-06-21 Welnick William E Method and system for acquiring a carrier system by a terminal device
EP2190159B1 (fr) * 2006-07-03 2012-10-31 ST-Ericsson SA Réduction du facteur de crête dans les systèmes multiporteuse
US8509695B2 (en) * 2007-07-10 2013-08-13 Belkin International, Inc. Method of selecting and broadcasting over a transmission frequency and device for the same
US8174959B2 (en) * 2008-03-11 2012-05-08 Nec Laboratories America, Inc. Auction based resource allocation in wireless systems
EP2200208A1 (fr) * 2008-12-19 2010-06-23 Panasonic Corporation Accusé de réception/accusé de réception négatif HARQ pour PDSCH dynamique
CN103906151B (zh) * 2009-03-12 2018-03-23 Lg电子株式会社 在无线通信系统中在用户设备及网络处操作载波的方法和操作载波的用户设备
US8934417B2 (en) * 2009-03-16 2015-01-13 Google Technology Holdings LLC Resource allocation in wireless communication systems
WO2010124238A2 (fr) * 2009-04-24 2010-10-28 Interdigital Patent Holdings, Inc. Procédé et dispositif pour envoyer un retour concernant une demande de répétition automatique hybride pour une agrégation de porteuse
WO2010127710A1 (fr) * 2009-05-08 2010-11-11 Nokia Siemens Networks Oy Rapport d'indication de qualité de voie dont la granularité dépend du nombre de meilleures porteuses de composantes
US9130698B2 (en) * 2009-05-21 2015-09-08 Qualcomm Incorporated Failure indication for one or more carriers in a multi-carrier communication environment
KR20110011517A (ko) * 2009-07-28 2011-02-08 엘지전자 주식회사 다중반송파 지원 광대역 무선 통신 시스템에서의 반송파 관리 절차 수행 방법 및 장치
US9351293B2 (en) * 2009-09-11 2016-05-24 Qualcomm Incorporated Multiple carrier indication and downlink control information interaction
CN102577523A (zh) * 2009-09-21 2012-07-11 Lg电子株式会社 在无线通信系统中发送探测参考信号的方法和装置
US8433251B2 (en) * 2009-09-28 2013-04-30 Qualcomm Incorporated Control information signaling
CN104618000B (zh) * 2009-11-09 2018-05-15 Lg电子株式会社 用于支持多天线传输技术的有效控制信息传输方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
WO2011064676A2 (fr) 2011-06-03
WO2011064676A3 (fr) 2011-08-04
US20120236815A1 (en) 2012-09-20
US9008016B2 (en) 2015-04-14
EP2507931A2 (fr) 2012-10-10

Similar Documents

Publication Publication Date Title
JP6923660B2 (ja) 方法、装置およびシステム
EP2474121B1 (fr) Schéma de retour d'informations pour la fourniture de retour d'informations sur des transmissions plurielles
EP2412118B1 (fr) Signalisation de mode de retransmission dans un système de communication sans fil
CN107888330B (zh) 一种数据传输的方法和装置
KR101323032B1 (ko) 피드백 정보를 구비한 멀티캐스팅을 위한 방법 및 장치
US10972228B2 (en) Base station device, user equipment, wireless communication system, and communication method
KR101749346B1 (ko) 다중 반송파 시스템에서 ｈａｒｑ 수행 장치 및 방법
KR101855502B1 (ko) Ack/nack 응답 메시지의 매핑 방법 및 단말
US8667357B2 (en) Method for conducting HARQ with a wireless communications system
US7539917B2 (en) Acknowledgement signaling for automatic repeat request mechanisms in wireless networks
KR101409733B1 (ko) 무선 통신 시스템에서, 그것의 제 1 네트워크 노드 및 제 2 네트워크 노드에서 데이터의 송신을 위한 방법
KR100678156B1 (ko) 무선 패킷 데이터 송신기 및 수신기와 송신 및 수신방법
CN108631960B (zh) 一种数据传输方法和相关设备
CN116405165A (zh) 发送harq-ack/nack的方法和设备及下行传输方法和设备
EP1211840A1 (fr) ARQ hybride avec transmission parallèle de paquets
US20080069055A1 (en) High rate packet data transmission system
RU2531264C2 (ru) Способ кодирования информации обратной связи harq с помощью двух отдельных кодовых слоев с неравной защитой от ошибок для dtх и ack/nack
WO2009157859A2 (fr) Commande d’erreur dans des systèmes sans fil à porteuses multiples
KR20090109042A (ko) 수신긍정확인 채널 할당방법
CN109155706A (zh) 数据传输方法、数据传输装置和通信系统
EP2507931B1 (fr) Procédé et système d' identification de porteuse de données
KR101140091B1 (ko) 무선통신 시스템에서 harq 수행 방법
Sachin et al. A review of Hybrid ARQ in 4G LTE
CN102714583B (zh) 数据载波标识方法和系统
CN111988118B (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

17P Request for examination filed

Effective date: 20120628

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL 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 RS SE SI SK SM TR

DAX Request for extension of the european patent (deleted)
RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: ORANGE

17Q First examination report despatched

Effective date: 20160621

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20180220

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL 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 RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

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: AT

Ref legal event code: REF

Ref document number: 1020485

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180815

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602010052058

Country of ref document: DE

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 9

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20180718

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1020485

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180718

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

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: 20180718

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20181019

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: 20181018

Ref country code: SE

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: 20180718

Ref country code: RS

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: 20180718

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: 20181118

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: 20180718

Ref country code: NO

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: 20181018

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: 20180718

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: 20180718

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: 20180718

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

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: 20180718

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: 20180718

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: 20180718

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602010052058

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

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: 20180718

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: 20180718

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: 20180718

Ref country code: IT

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: 20180718

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: 20180718

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

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20180718

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: 20180718

Ref country code: DK

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: 20180718

26N No opposition filed

Effective date: 20190423

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20180718

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181130

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20181130

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: 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: 20180718

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181130

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181130

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: 20181130

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: 20181130

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 NON-PAYMENT OF DUE FEES

Effective date: 20181130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

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: 20180718

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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180718

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20180718

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20101130

Ref country code: MK

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180718

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231019

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: 20231020

Year of fee payment: 14

Ref country code: DE

Payment date: 20231019

Year of fee payment: 14