EP3414858A1 - Mécanismes de demande de répétition automatique - Google Patents

Mécanismes de demande de répétition automatique

Info

Publication number
EP3414858A1
EP3414858A1 EP17703448.5A EP17703448A EP3414858A1 EP 3414858 A1 EP3414858 A1 EP 3414858A1 EP 17703448 A EP17703448 A EP 17703448A EP 3414858 A1 EP3414858 A1 EP 3414858A1
Authority
EP
European Patent Office
Prior art keywords
logical channel
user data
channel
receiver
packet
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.)
Pending
Application number
EP17703448.5A
Other languages
German (de)
English (en)
Inventor
Martin Hans
Andreas Schmidt
Maik Bienas
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.)
Ipcom GmbH and Co KG
Original Assignee
Ipcom GmbH and Co KG
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 Ipcom GmbH and Co KG filed Critical Ipcom GmbH and Co KG
Publication of EP3414858A1 publication Critical patent/EP3414858A1/fr
Pending legal-status Critical Current

Links

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
    • H04L1/1642—Formats specially adapted for sequence numbers
    • 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/0015—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy
    • H04L1/0017—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the adaptation strategy where the mode-switching is based on Quality of Service requirement
    • 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/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
    • H04L1/0086—Unequal error protection
    • H04L1/0088—Unequal error protection in control part
    • 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
    • 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
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • 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
    • 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/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/0028—Formatting
    • H04L1/0031—Multiple signaling transmission
    • 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]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • 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

Definitions

  • the present invention relates to a mechanism for sending repeat requests in a mobile communication network.
  • ARQ automatic repeat request
  • RLC radio link control
  • MAC media access control
  • HARQ hybrid ARQ
  • the MAC-HARQ mechanism is always used for packet data transmission, with one HARQ entity per transport channel, i.e. usually one per device.
  • the MAC-HARQ is configured per entity, i.e. per transport channel or one configuration per device.
  • the known RLC-ARQ is configurable depending on the required service, with one RLC- ARQ entity per logical channel, i.e. usually one per service (TCP-socket, application, or similar) and potentially multiple configurations per device.
  • the RLC-ARQ is configured individually per logical channel, for example a maximum number of repeated
  • a window size or timer (number of lost packets or time waited for before a newer packet is given to upper layers).
  • the HARQ uses an "n-channel- stop-and-wait" mechanism with the number n of channels (called “processes" in
  • UMTS/LTE chosen so that a fluent transmission is possible, and retransmissions may contain different redundancy versions of the original data, the versions being provided by the PHY layer as a coding result.
  • the RLC ARQ process is designed to allow for configuration of each RLC ARQ entity to match the logical channel delay and error rate requirements.
  • Feedback and retransmissions are sent asynchronously so that packet numbering is required for reference in ACK/NACK feedback packets and in retransmission packets.
  • Feedback is sent on request from the transmitter (poll) or autonomously by the receiver when it detects missing packets and packets (RLC PDUs) are transmitted and re-transmitted in their original version, as no redundancy versions are available in the RLC layer.
  • an ARQ mechanism In general there are two design options for an ARQ mechanism depending on which side decides if and how data needs to be retransmitted or new data should be sent and how. If the receiver has control it requests the transmitter to (re-) transmit either old or new data and decides on the transmission parameters. A test whether a maximum number of retransmissions is exceeded and the choice of transmission parameters including redundancy versions, modulation, coding and resources to be used is done in the receiver and the selected parameters are fed back to the transmitting side to react accordingly. Receiver-based control of HARQ is applied, for example, in the uplink of an LTE system where the UE can be explicitly requested and the base station has control.
  • the receiver needs to inform the transmitter about success of reception by sending feedback information in form of an ACK or NACK.
  • the decision if (re-) transmission of old or new data takes place is done in the transmitter based on the feedback, on maximum number of re-transmissions and other parameters.
  • the transmission parameters may be decided in the transmitter as well.
  • Transmitter-based control of HARQ is applied, for example in the downlink of an LTE system where the UE sends ACK NACK feedback to the base station and the base station has control.
  • Wireless transmission links are generally lossy to a certain degree. On a radio link that does not apply sequential delivery of packets in all cases, as is the case with multiple HARQ processes, in addition to loss, the order of packets can change, too.
  • Typical services are very sensitive to packet re-ordering, therefore in-sequence delivery is applied in the RLC layer. A mechanism that detects and corrects packet re-ordering is required.
  • the principle is based on sequence numbers and packet buffering. To avoid stalling the transmission in case packets are lost a maximum time to wait is predefined. After the time expires the received packets waiting are delivered in-sequence to the higher layer with gaps for the lost packets. A maximum wait time can be realized with a maximum number of packets received while waiting. The predefined maximum wait time is thus an important parameter that influences the packet loss rate and the delay. ARQ and HARQ is described in detail in telecommunication standards and related text books. In the patent literature, US 8,072,981 describes a method of transmitting packet sequence numbers in parallel to actual data. Packets are provided with sequence numbers which are transmitted over a separate channel, for example a control channel or a dedicated channel with the data being transmitted via a shared traffic channel.
  • US 2009/0268707 A1 describes a HARQ mechanism in which a counter is signalled from a transmitter to a receiver to indicate how often a specific packet has been transmitted.
  • US 2008/0123660 A1 describes a system in which at the network side on the S1 interface between the eNode-B and the access gateway each packet is tagged with a QoS tag.
  • the tag may be stripped off at the eNode-B and not transmitted to the UE.
  • the eNode-B uses the information in the QoS tag to control the transmission of packets including HARQ process selection.
  • the QoS tag is transmitted together with the packet in the same channel.
  • US 2007/0201369 A1 describes grouping logical flow channels by traffic priority to form an aggregate data flow which is then compared with a threshold value to obtain an indication value which is transmitted from a UE to a base station.
  • the present invention provides a method of performing an automatic repeat request mechanism in a mobile communication system, the method comprising sending user data from a first device to a second device over a logical channel and sending over a control channel an associated control message from a medium access control layer of the first device to a medium access control layer of the second device, the associated control message comprising a logical channel identifier for identifying the logical channel over which the user data is transmitted.
  • the invention also provides the corresponding transmitter and receiver devices.
  • the present invention is suitable as a design for a single ARQ entity for use in a next generation mobile communication system that replaces the currently used dual ARQ mechanisms "HARQ in MAC and "ARQ in RLC” i.e. to eliminate RLC-ARQ while introducing flexibility and service awareness into MAC-HARQ. This will increase the service reliability as the HARQ parameters could be adapted dynamically to the current needs of the service and reduce the transmission delay as the re-ordering process speeds up.
  • a logical channel ID is transmitted with a sequence number separated from related user data and with increased reception robustness.
  • the transmission of the logical channel ID allows to use service (QoS) specific HARQ- parameters.
  • QoS service
  • the separated transmission of the sequence number enables awareness for transmitted packets at the receiver even in case that the user data part of the transmission was not successfully received and therefore allows faster proceeding after a packet was discarded. There is no need for timer-based discard and the corresponding wait time that increases transmission delay.
  • the invention provides an ARQ mechanism in the MAC layer that replaces the currently used dual ARQ concept with an ARQ on RLC layer and a HARQ on MAC layer.
  • the ARQ mechanism provides flexible ARQ parameters per service (i.e. per logical channel) so that configuration of delay and reliability according to QoS demands is possible.
  • the logical channel associated with the data currently transmitted is indicated to the receiver. This indicated information is termed a logical channel identity (LogChID) that may have various physical appearances, discussed in more detail in the description of the preferred embodiments.
  • LogChID logical channel identity
  • a feature is that the MAC-layer executes the ARQ mechanism dependant on the logical channel of the data to be transmitted, in particular whether to retransmit packets and which redundancy version to use is decided dependant on the logical channel.
  • Parameters influencing this decision may be configured via configuration protocols, e.g. by the network to the UE.
  • QoS quality of service
  • logical channel may signal logical channels (e.g. in form of a channel ID), QoS settings (in various forms like an index to a list of settings) or a Service (in various forms like an IP- Address/Port-Number pair or alike).
  • logical channel is used because the model goes in-line with the current UMTS and LTE architecture and is easy to read, but there is no restriction related to that wording.
  • the LogChID has to be received successfully. For bad link conditions this means a more reliable transmission of the LogChID compared to data transmission is desirable.
  • the signalling of a LogChID is preferably done on a highly reliable control channel in parallel to the actual data transmission.
  • the LogChID transmission can use the same channel but different (preferably constant) coding that ensures the most reliable transport.
  • different coding used in parallel constitutes a different channel in the usual model.
  • the LogChID should be delivered on a control channel.
  • Alternative delivery mechanisms are not excluded but it is a feature of this invention to use highly reliable mechanisms different from those used for data transmission.
  • a grouping of logical channels into groups of channels that have the same or similar QoS demands may reduce the number of signalling bits.
  • a logical channel group and related logical channel group ID for signalling is already known from LTE for Buffer Status Reporting, e.g. the buffer status is reported once for the whole group of channels. The ID could be re-used or a new group ID can be used. In any case the grouping of logical channels would be configurable by the network with the knowledge of the QoS demand of logical channels.
  • the time to wait for lost packets is an important factor when the delay introduced by an ARQ mechanism should be reduced.
  • the knowledge about delivery success or failure of a packet is available in the receiver, yet it is unused for discarding packets. The reason is that for packets not successfully received the header information within that packets cannot be read either and thus the sequence number of a packet finally not transmitted is unknown to the receiver.
  • the receiver has to apply the abovementioned time to wait for the packet before discarding it and providing further packets to higher layer. It is thus a further aspect of this invention to deliver a packet identifier, e.g.
  • the NACK'ed packet is declared lost and the re-ordering entity is informed.
  • the transmitter To further reduce the delay on the link it is possible for the transmitter to mark a last transmission attempt of a packet on the control channel (e.g. as part of the sequence number information) so that the receiver can immediately declare the packet lost when the packet is not successfully received.
  • packet numbering is assumed per logical channel (as today in LTE and UMTS), therefore a sequence number received is only meaningful if the logical channel is known. Therefore, in conjunction with the sequence number signalling a signalling reduction of the LogChID into a logical channel group ID as proposed alternatively above is not feasible.
  • a full LogChID signalling together with a signalling of a sequence number is performed.
  • Control channels in general are a sparse resource; therefore, means to reduce signalling are beneficial.
  • the length of a sequence number has to be long enough to allow a wide enough value range to differentiate all packets that can be on the way from the transmitter to the receiver in parallel while taking worst-case assumptions into account.
  • a sequence number could be maintained on both sides (transmitter and receiver) without any explicit sequence number signalling simply by synchronously counting packets per logical channel including packets not successfully transmitted.
  • synchronization means is doomed to fail.
  • a shorter piece of information derived from the sequence number e.g. only a part of the sequence number is sent.
  • the n least significant bits with n in the range of 2 to 5 can be sent.
  • the receiver can derive the rest of the sequence number taking the history of received sequence numbers from the control channel into account assuming less that n consecutive transmission failures on a control channel.
  • a control channel for ARQ related information like LogChID and sequence numbers is used.
  • the control channel resources need to be unambiguously mapped to respective data channel (shared channel) resources.
  • the mapping can be explicit using additional signalling of the resource mapping or implicit with a fixed relation.
  • the amount of resources needed for the proposed HARQ control signalling depends on the number of packets transmitted; therefore they may vary from transmission to transmission.
  • Fig. 2 shows a prior art HARQ downlink architecture
  • Fig. 3 is a message sequence chart for a receiver controlled HARQ process
  • Fig. 4 is an alternative message sequence chart of a receiver controlled HARQ process
  • Fig. 5 is a message sequence chart of a transmitter controlled HARQ process
  • Fig. 6 is an alternative message sequence chart of a transmitter controlled HARQ process.
  • a mobile terminal also termed user equipment, UE
  • a base station BS
  • UE user equipment
  • BS base station
  • the layer 2 architecture model of both the UE and the BS are very similar to that depicted in the telecommunications standard 3GPP TS 36.300, figure 6-1 and the protocol stack is assumed to be as depicted in the same document, figure 4.3.1-1.
  • the data transmission takes place on a single downlink and uplink shared channel (DL- SCH and UL-SCH, resp.) and control channels are available for DL (Physical Downlink Control Channel, PDCCH) and UL (Physical Uplink Control Channel, PUCCH) as in the TS 36.300, figure 5.3.1-1 and 5.3.1-2.
  • PDCCH Physical Downlink Control Channel
  • PUCCH Physical Uplink Control Channel
  • Fig. 1 shows a current uplink (UL) architecture and is used to illustrate various
  • Data of multiple logical channels may be multiplexed by the MAC layer as described in state of the art taking logical channel priorities into account so that for example data of logical channels with higher priority is always transmitted before transmission of data of logical channels with lower priority takes place.
  • the multiplexing results in one or more data streams that are transmitted to the physical layer, so called transport channels.
  • Fig. 1 only shows one transport channel, the UL shared channel, but the invention is not so limited and may be used over multiple transport channels.
  • Fig. 1 also does not show a clear mapping of functions to either MAC or physical layer as this is not relevant to the invention and may vary in different architectural models.
  • the steps for implementing the invention take place in the MAC and/or the physical layer depending on implementation.
  • HARQ On the transport channel HARQ is applied which results in multiple HARQ processes, each running a stop-and-wait mechanism.
  • the processes are mapped to a physical channel representing the actual physical resource in a strict time relation, indicated in Fig. 1 with a circular arrow.
  • Fig. 1 four HARQ processes are assumed for better readability although in real deployments the number of processes will probably be higher.
  • Fig. 1 Also shown in Fig. 1 is a control channel (Physical Uplink Control Channel PUCCH) that can transmit HARQ control information in the UL in parallel to the shared channel.
  • Fig. 2 is very similar to Fig. 1 showing architecture with the same assumptions but for the downlink, DL. It is not described in further detail here.
  • Logical channel 2 contains voice data only which typically appears in small packets that can be delivered as a single packet over the physical resource.
  • Logical channel 1 contains browsing data that may consist of bigger packets that are segmented into packets of sizes that fit the available physical resources.
  • Fig. 3 shows a message sequence chart for a receiver-controlled HARQ process with two RLC entities for the two respective logical channels and a MAC layer for each entity (transmitter, receiver).
  • the MAC layer is detailed so that four HARQ processes are shown, HARQ-P1 to HARQ-P4.
  • Fig. 3 shows data for the lower priority logical channel to arrive at RLC1 and being segmented into multiple PDUs 1- 6; which are transmitted as transmit resources become available. Data for the higher priority logical channel 2 arrives during the timeline represented by Fig. 3 resulting in a single RLC PDU per data packet arrival without the need to segment the data.
  • the HARQ processes P1 to P4 are executed consecutively and each transmission on the physical channel PUSCH is either positively (ACK) or negatively (NACK) acknowledged depending on a decoding result at the receiver. For each packet successfully received a feedback is sent that acknowledges the reception and indicates new data to be transmitted next on the respective process.
  • ACK and the "new data indicator" may be transmitted together on the same channel or separate and they may be transmitted together with other information regarding the modulation and coding scheme and other transmit parameters to be used.
  • Fig. 3 only contains the information relevant for this invention.
  • Fig. 3 also shows the transmission of a LogChID on a PUCCH resource in parallel to a data transmission.
  • the LogChID is shown to be transmitted between the MAC entities (without specifying a process, just for readability and not restricting).
  • a LogChID is transmitted in parallel to every packet transmitted on the PUSCH and is shown in Fig. 3 as a dashed line between the MAC entities.
  • the receiver With the knowledge of the logical channel of each packet, whether successfully received (indicated by a transmission line ending with an arrow head) or not (indicated by a transmission line terminating with a cross), the receiver is in a position to make a decision.
  • Fig. 3 after unsuccessful reception of PDU 1 of logical channel 1, a decision is made to retransmit the packet with an incremented redundancy version rv 1 , the decision point denoted D11 (in the figures, a redundancy version 0 is not specifically indicated for readability, PDUs without rv number are rvO). Only with the new signalling of the logical channel the receiver can make that decision based on the configuration for the specific service that uses logical channel 1.
  • the difference in performing the HARQ is possible with signalling of the logical channel on a control channel.
  • Fig. 4 shows a similar example; yet with the signalling of PDU sequence numbers in addition to LogChID on a control channel.
  • the receiver can indicate the PDU 1 immediately as being finally lost after the logical channel dependant decision not to retransmit the packet again. This is possible as a result of the control channel signalling of logical channel and sequence number.
  • the RLC layer can deliver the resulting data without delaying it while waiting for PDU 1 to be received or a timer to expire.
  • the delay has been significantly reduced with the new signalling.
  • Figs. 5 and 6 show again a similar example with the difference that the HARQ mechanism is transmitter-controlled and only ACK or NACK are fed back from receiver to transmitter.
  • decision point D11 it is decided to retransmit PDU 1 of logical channel 1 and similar at D21 for logical channel 2. The decisions are made based on the knowledge of the logical channel and its configuration regarding the QoS demand of the respective service.
  • D12 again a decision is made to retransmit PDU 1 of logical channel 1 with a new redundancy version whereas at D22 it is decided not to retransmit PDU 1 of logical channel 2 due to delay constraints of that logical channel.
  • the LogChID and sequence number signalling on a control channel may be performed in addition to the known signalling of the same information in a AC-header that is added to each packet transmitted. In that case a redundant control information transmission could further increase transmission reliability for this information.
  • a redundant inclusion of the information in a MAC-header may be used by the receiver to verify calculated sequence numbers or received logical channel groups and detect errors.
  • the new signalling on the control channel can replace the signalling in the MAC-header, thereby reducing the data volume on the shared channel.
  • the sequence number may be reduced.
  • means for reduced or no signalling of sequence numbers may be applied to reduce signalling on the control channel. This may be implemented as follows.
  • the receiver maintains a variable that indicates the highest received sequence number, MAX-R-SN n , for each logical channel n that is initialized to zero.
  • the receiver maintains a variable that indicates the currently received sequence number, PRO-R-SN p , for each HARQ process p.
  • PRO-R-SN a When a packet is successfully received on process a, is PRO-R-SN a is considered the sequence number for that packet. When a packet transmission is detected to be finally unsuccessfully on process a, PRO-R-SN a is considered the sequence number of the lost packet and the re-ordering entity is informed correspondingly.
  • the final loss of the packet may be explicitly signalled as "last attempt", or explicit indication of new data on that process may indicate loss of the previous packet on that process, or the decision to discard the packet may be done in the receiver.
  • a part of the sequence number may be explicitly transmitted on the control channel or in the MAC-header or both. A comparison of the received part of the sequence number and the calculated sequence number takes place.
  • the transmitting and receiving side of the HARQ mechanism are considered in sync. If there is mismatch, the received sequence numbers are used to correct the calculation as follows: the MAC is reset on both side, a full transmission of sequence numbers is triggered, and the calculation is simply reset to the values received.
  • the size of the sequence number signalling may be variable: it can be increased (up to a max) for every detected loss of synchronization and it can be decreased (down to a miri) for a number of packets being in-sync.
  • the principles of the present invention have been described to work with a synchronous HARQ process in which ACK/NACK and other feedback is transmitted in a strict time relation to the original data and retransmissions are sent on the same process. This should not restrict the functionality of logical channel and/or sequence number signalling. The new functionality even provides packet identifications that could be re-used to change the HARQ mechanisms.
  • a selective-repeat HARQ could be used with MAC-HARQ by providing sequence numbers and LogChID with ACK/NACK. This would eliminate the necessity to maintain HARQ processes, a linear transmission of packets could be used. Asynchronous retransmission could be allowed, i.e. retransmission could occur on any HARQ process (only with explicit sequence number transmission). While the invention concerns the removal of ARQ functionality from the RLC layer, the RLC layer may still perform the functions of buffering, re-ordering, and segmentation and re-assembly.

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)

Abstract

La présente invention concerne un procédé de réalisation d'un mécanisme de demande de répétition automatique dans un système de communication mobile, le procédé consistant à envoyer des données utilisateur d'un premier dispositif à un second dispositif sur un canal logique et envoyer sur un canal de commande un message de commande associé depuis une couche de contrôle d'accès au support du premier dispositif à une couche de contrôle d'accès au support du second dispositif, le message de commande associé comprenant un identifiant de canal logique destiné à identifier le canal logique sur lequel les données utilisateur sont transmises.
EP17703448.5A 2016-02-10 2017-02-10 Mécanismes de demande de répétition automatique Pending EP3414858A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP16154985 2016-02-10
PCT/EP2017/053011 WO2017137564A1 (fr) 2016-02-10 2017-02-10 Mécanismes de demande de répétition automatique

Publications (1)

Publication Number Publication Date
EP3414858A1 true EP3414858A1 (fr) 2018-12-19

Family

ID=55353055

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17703448.5A Pending EP3414858A1 (fr) 2016-02-10 2017-02-10 Mécanismes de demande de répétition automatique

Country Status (3)

Country Link
EP (1) EP3414858A1 (fr)
RU (1) RU2761016C2 (fr)
WO (1) WO2017137564A1 (fr)

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE60005150T2 (de) 2000-05-17 2004-04-01 Matsushita Electric Industrial Co., Ltd., Kadoma Hybrides ARQ Verfahren zur Datenpaketübertragung
CN1254998C (zh) * 2001-11-08 2006-05-03 三菱电机株式会社 无线通信方法及用于其中的移动体终端
CN101406097A (zh) 2006-02-03 2009-04-08 诺基亚公司 从用户设备向无线网络提供基于阈值的缓冲器状态报告的装置、方法和计算机程序产品
WO2008021182A2 (fr) * 2006-08-09 2008-02-21 Interdigital Technology Corporation procédé et appareil pour obtenir une qualité de service différenciée pour des paquets dans un flux particulier
WO2009132169A1 (fr) 2008-04-25 2009-10-29 Interdigital Patent Holdings, Inc. Procédés de mise en œuvre de groupage d’intervalle de temps de transmission
EP2306665A1 (fr) * 2009-10-02 2011-04-06 Panasonic Corporation Protocole HARQ en liaison montante de retour de relais
US8341134B2 (en) * 2010-12-10 2012-12-25 International Business Machines Corporation Asynchronous deletion of a range of messages processed by a parallel database replication apply process
CA2882876C (fr) * 2012-08-23 2021-01-26 Interdigital Patent Holdings, Inc. Fourniture de ressources de couches physiques a des sites de services differents
US8868026B2 (en) * 2012-08-30 2014-10-21 Nokia Solutions And Networks Oy Sending BCCH modification info/ETWS information to UEs in enhanced cell PCH in one DRX cycle

Also Published As

Publication number Publication date
WO2017137564A1 (fr) 2017-08-17
RU2761016C2 (ru) 2021-12-02
RU2019124262A (ru) 2021-02-01
RU2019124262A3 (fr) 2021-02-01

Similar Documents

Publication Publication Date Title
AU2009209739B2 (en) Method for sending status information in mobile telecommunications system and receiver of mobile telecommunications
EP1770897B1 (fr) Procédé, dispositif et système de communication mobile pour la retransmission de paquets
US8325656B2 (en) Arrangement and method for extended control plane signalling in a high speed packet data communication
US8824376B2 (en) Method for sending status information in mobile telecommunications system and receiver of mobile telecommunications
CN113748629B (zh) 通信装置、基础设施设备以及方法
EP2290866B1 (fr) Procédé pour le déplacement d'une fenêtre de réception dans un réseau d'accès radio
US7761767B2 (en) Method and apparatus for retransmission management for reliable hybrid ARQ process
US9025564B2 (en) Method and apparatus for handover in a mobile communication system
US8413002B2 (en) Method of performing ARQ procedure for transmitting high rate data
EP2094049B1 (fr) Procédé et dispositif d'envoi de RLC PDU dans un système de communications mobile
US20080043619A1 (en) Method and apparatus for controlling arq and harq transmissions and retransmissions in a wireless communication system
US20090319850A1 (en) Local drop control for a transmit buffer in a repeat transmission protocol device
KR20080047960A (ko) 이동통신 시스템에서 타이머에 의한 라디오 링크 제어계층의 데이터 전송 방법 및 장치
Susitaival et al. LTE coverage improvement by TTI bundling
EP1364482B1 (fr) Procede et dispositif permettant d'eviter les retransmissions inutiles dans un systeme cellulaire
EP3890431B1 (fr) Optimisation de latence d'accusé de réception tcp
JP5648631B2 (ja) 受信装置、受信方法およびプログラム
WO2024028277A1 (fr) Équipement, dispositifs et procédés de communication d'infrastructure
WO2019128937A1 (fr) Procédé de planification de données de liaison montante et dispositif correspondant
KR101617044B1 (ko) 피어 엔티티의 전송 상태 정보를 이용한 데이터 유닛 재전송 방법
EP3414858A1 (fr) Mécanismes de demande de répétition automatique
KR101201046B1 (ko) 이동통신 시스템에서 제어 메시지를 재전송하는 방법 및장치
KR20120023374A (ko) 무선링크제어계층에서의 데이터 전송 장치 및 방법

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

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: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20180903

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Extension state: BA ME

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20210604

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS