Retransmission in data communication systems

• US 20090086759A1
• Filed: 09/12/2008
• Published: 04/02/2009
• Est. Priority Date: 10/02/2007
• Status: Active Grant

• Current Assignee: Infineon Technologies AG
• Original Assignee: Infineon Technologies AG
• Inventors: HORVAT, Michael, SCHEDELBECK, Gert, SCHOPPMEIER, Dietmar, HEISE, Bernd
• Granted Patent: US 8,351,464 B2
• Time in Patent Office: Days
• US Class Current: 370/474
• CPC Class Codes: H04L 1/0007 by modifying the frame length
• CPC Class Codes: H04L 1/0085 Formatting with cells
• CPC Class Codes: H04L 1/1874 Buffer management
• CPC Class Codes: H04L 1/1887 Scheduling and prioritising arrangements
• CPC Class Codes: H04L 1/1896 ARQ related signaling
• CPC Class Codes: H04L 27/2601 Multicarrier modulation systems
• CPC Class Codes: H04L 5/003 Arrangements for allocating sub-channels of the transmission path

Abstract

Embodiments related to retransmission in data communication systems are described and depicted

Claims

1. A method comprising

receiving a data packet;

separating the data packet in a plurality of data fragments;

providing for each of the plurality of data fragments or for a group of the plurality of data fragments an identification;

transmitting the plurality of data fragments from a first transceiver unit to a second transceiver unit;

transmitting a request for retransmission from the second transceiver unit to the first transceiver unit, the request comprising one or more identifications;

processing the request for retransmission at the first transceiver unit to identify one or more data fragments based on the one or more identifications; and

retransmitting the one or more identified data fragments.

2. The method according to claim 1, further comprising processing each data fragment to provide 64/65 octet encapsulation.

3. The method according to claim 1, wherein the separating of the data packet and the providing of an identification is provided by a processing between a 64/65 octet encapsulation sublayer and a data link layer.

4. The method according to claim 1, further comprising:

distributing the data fragments to a plurality of subscriber lines based on the identification.

5. The method according to any of claims 1, further comprising dynamically changing the length of the data fragments.

6. The method according to claim 1, further comprising:

multiplexing a first data stream associated with a first service type, a second data stream associated with a second service type and a third data stream associated with retransmission data.

7. The method according to claim 1, further comprising:

providing information indicating whether a fragment of the plurality of fragments is to be protected by retransmission or providing information indicating whether a group of fragments is to be protected by retransmission.

8. The method according to claim 1, further comprising providing a rate decoupling functionality by transmitting idle fragments which are transparent to a TPS-TC layer of the first transceiver and the second transceiver or at least all TPS-TC sublayers hierarchically below the rate decoupling functionality.

9. The method according to claim 1, further comprising determining one or more repetitive noise parameters, the one or more repetitive noise parameters determining time periods during which no user data is transmitted.

10. The method according to claim 1, further comprising:

transmitting from the second transceiver to the first transceiver a request for retransmission, the request for retransmission including the identification of the last correctly received data fragment or the identification of the last correctly received group of data fragments.

11. A transmitter comprising:

a fragmentation entity to separate a packet into a plurality of data fragments;

an identification entity to provide for each data fragment or group of data fragments an identification;

a retransmission entity to receive a retransmission request including at least one of the identifications of the data fragments from a remote transceiver unit.

12. The transmitter according to claim 11, further comprising a TPS-TC entity to receive the data fragments with the identification and provide TPS-TC processing;

and

wherein the retransmission entity is configured to transfer to the TPS-TC entity one or more data fragments based on the at least one identifications received from the remote transceiver unit.

13. The transmitter according to claim 11, further comprising a bonding entity for bonding a plurality of subscriber lines wherein the bonding entity is configured to distribute the data fragments to the plurality of subscriber lines.

14. The transmitter according to claim 11, further comprising a rate decoupling entity, wherein the rate decoupling entity is configured to include idle fragments which are transparent to a TPS-TC layer or at least all TPS-TC sublayers hierarchically below the rate decoupling entity.

15. The transmitter according to claim 11, further comprising a multiplexer, the multiplexer configured to multiplex a first data stream of data fragments associated with a first service type, a second data stream of data fragments associated with a second service type and a third data stream of data fragments associated with retransmission data.

16. A receiver comprising

a retransmission entity to receive data fragments, wherein each of the data fragments or a group of data fragments comprises an identification, wherein the retransmission entity is configured to provide indication of at least one corrupt fragment;

and

a request generation entity to receive the indication and to generate a retransmission request based on the identification and the indication of at least one corrupt data fragment or at least one corrupt group of data fragments.

17. The receiver according to claim 16, wherein the retransmission entity is configured to receive the data fragments from a TPS-TC entity, the TPS-TC entity implementing at least one functionality of a TPS-TC sublayer for the received data fragments.

18. The receiver according to claim 16, further comprising a CRC entity, the CRC entity providing an error detection based on a packet start identifier provided in at least a first fragment of the data fragments and a packet end identifier provided in at least a second fragment of the plurality of fragments.

19. The receiver according to claim 16 wherein the receiver comprises a bonding entity, the bonding entity sharing at least one functionality with the retransmission entity.

20. A DSL transmission system comprising:

a first transceiver unit, the first transceiver unit comprising

a fragmentation entity to separate a packet into a plurality of data fragments;

a first identification entity to provide for each data fragment or a group of data fragments an identification;

a first transmission entity to transmit the plurality of data fragments; and

a first retransmission entity to receive retransmission requests and to identify at least one fragment based on the received retransmission request;

a second transceiver unit, the second transceiver unit comprising

a second retransmission entity to receive the plurality of data fragments and to provide indication of at least one corrupt data fragment;

a request generation entity to receive the indication and to generate a retransmission request based on the indication and the identification; and

a transmission entity to transmit the retransmission request to the first transceiver unit.

21. The system according to claim 20, wherein the first transceiver unit further comprises a CRC entity to provide a packet start identifier in at least a first one of the data fragments and a packet end identifier in at least a second one of the data fragments and wherein the second transceiver further comprises a CRC entity to provide error detection based on the packet start and packet end identifier.

22. The system according to claim 20, wherein the first retransmission entity is configured to transmit the data fragments to a first TPS-TC entity, the first TPS-TC entity implementing at least one functionality of a TPS-TC sublayer, and

wherein the second retransmission entity is configured to receive the data fragments from a second TPS-TC entity, the second TPS-TC entity implementing at least one functionality of a TPS-TC sublayer.

23. The system according to claim 20, wherein the first transceiver comprises a rate decoupling entity, wherein the rate decoupling entity is configured to include idle bytes in at least one of the TPS-TC encapsulation structures.

24. A protocol stack for a DSL transmission system, the protocol stack comprising a retransmission functionality, the retransmission functionality being provided between a sublayer of a TPS-TC layer and a data link layer, the retransmission functionality having a fragment of a packet or a group of fragments of a packet as basic retransmission unit.

25. The protocol stack according to claim 24, wherein the protocol stack is implementing a service specific retransmission functionality such that for a first class of services retransmission protection is provided and for a second class of services no retransmission protection is implemented.