ES2368342T3 - RADIO-LINK PROTOCOLS FOR MULTI-LINK COMMUNICATIONS SYSTEMS. - Google Patents

Abstract

A method (1200) for the transmission of data in a multilink communications system (100) comprising: the segmentation (1210) of a higher level packet into link level packets that are to be transmitted over a plurality of links of communication; the addition of a first sequence number (1220) to each link level packet; and adding a second sequence number (1230) to each link level packet that must be transmitted a first time, the second sequence number being in a sequence space associated with a particular communication link; and the reception of a negative confirmation message (NAK) from a receiver, the NAK message including a first loop of the first sequence number indicated by the first sequence numbers of two link level packets received consecutively presenting about second sequence numbers not contiguous.

Description

Radio link protocols for multi-link communication systems

Background

Countryside

The present disclosure refers, in general, to the field of wireless communication systems. More specifically, the embodiments disclosed herein refer to a new set of radio link protocols (RLPs) configured to enhance the effectiveness of wireless communication systems.

Background

Wireless communication systems have been widely implemented to provide various types of communication (eg voice, data, etc.) to multiple users. Such systems may be based on multiple code division (CDMA), time division multiple access (TDMA), multiple frequency division (FDMA) access techniques, or other multiple access techniques. A wireless communications system can be designed to implement one or more standards, such as IS-95, CDMA2000, IS-856, W-CDMA, TD-SCDMA, and other standards.

In response to the growing demand for multimedia and data services with a high transmission rate, multilink modulation has been proposed in wireless communications systems. The challenge of providing an efficient and robust multilink communications system persists. Special attention is requested with respect to document US 2002/172192 A1 which discloses a procedure and an apparatus for controlling the maximum number of retransmissions of an information package that can be attempted if the information package was not properly received. The number of message retransmissions is limited using maximum permissible retransmission values (MAR).

Another document, US-A-4 703 475 discloses a multi-link interprocessor communications protocol that makes it possible for a pair of processors to increase the speed of their communication through the use of multiple physical links in parallel. When a message is sent from one processor to another, the message is packaged in smaller segments and loaded onto the available physical links according to a simple algorithm. The individual packets are received at the other end, their precise transmission being verified and the received packets are regrouped in the relevant order.

Another document, US 2004/059978 A1 discloses a procedure and an apparatus to reduce latency for the recovery of communications errors and that includes the recognition that an incoming message is expected, and the request for retransmission if that message It has not been properly received. A message is transmitted in the form of two message potions, the first portion of the message transmitted at a first power level, and the second portion of the message, which is associated with the first portion of the message, transmitted at a second power level. .

Another document, US-B1-6 611 521 provides a procedure for communication between a plurality of stations within a communication network using a media access protocol, in which access to the medium is granted to the stations obtaining a Successful reservation of the medium and in which the verification of the data transmission is carried out by means of the existing protocol within the reservation.

Another document, US 2001/032325 A1 discloses a base station, a mobile station, and / or other terminal device includes a physical level protocol (level 1) and a link level protocol (level 2) which include some automatic retransmission request (ARQ) operations. A transmitter packages some packet units of link level data converting them into physical level frames and transmits the frames at physical level. A receiver responds to indicate the completion of a transmission either successfully or without success.

Summary

In accordance with the present invention there is provided a method for the transmission of data in a multilink communications system in accordance with that defined in claim 1, a method for the processing of data in a multilink communications system in accordance with what is defined in claim 7, an apparatus adapted for the transmission of data in a multilink communications system in accordance with the definition in claim 20, an apparatus adapted for the processing of data in a multilink communications system in accordance with what is defined in claim 23, a computer-readable medium according to what is defined in claim 26 and a computer-readable medium according to what is defined in claim 27. Embodiments of the invention are claimed in the dependent claims.

Brief description of the drawings

FIG. 1 illustrates an embodiment of a multi-link communications system;

FIG. 2 illustrates an embodiment of packets that reach a receiver through multiple communication links;

FIG. 3 illustrates an embodiment of a packet segmentation for the first transmitted packets;

FIG. 4 illustrates an embodiment of a packet segmentation for retransmitted packets;

FIG. 5 illustrates an embodiment of a protocol stack for a multi-link communication system;

FIG. 6 illustrates an embodiment of an architecture of a multi-link communications system;

FIG. 7 illustrates an embodiment of how packets are interspersed through multiple communication links;

FIG. 8 illustrates an embodiment of a packet transmission during a switching of service cells;

FIG. 9 illustrates an example of an octet-based segmentation and regrouping sequence number (SAR_seq);

FIG. 10 illustrates a scenario of a multi-link communications system;

FIG. 11 illustrates another scenario of a multi-link communications system;

FIG. 12 illustrates a flow chart of a process, which can be used in an embodiment to implement the transmission of data in a multi-link communications system;

FIG. 13 illustrates a flowchart of a process, which can be used in an embodiment to implement data processing of a multi-link communications system;

FIG. 14 illustrates a block diagram of an apparatus, in which some disclosed embodiments may be implemented; Y

FIG. 15 illustrates a block diagram of an apparatus, in which some disclosed embodiments can be implemented.

Detailed description

The embodiments disclosed herein refer to the provision of a new set of radio link protocols (RLPs) and associated procedures configured to maximize the efficiency of multi-link communication systems.

FIG. 1 illustrates an embodiment of a multi-link communication system (100). By way of example, various access terminals (ATs) 110, which include ATs 110a -110c, are dispersed throughout the system. Each AT 110 can communicate with an access network (AN) 120 by means of one or more channels at different frequencies on a direct link and / or a reverse link at a given time, as illustrated by the two-way arrows 130. For reasons of illustration and clarity, the two-way arrows 130 are shown for each AT 110. There may be an indeterminate number of channels (or frequencies) either on the direct link or the reverse link in a communications system. Likewise, the number of frequencies on the direct link need not be the same as the number of frequencies of the reverse link.

The AN 120 can also be in communication with a main network, such as a packet data network by means of a packet data service node (PDSN) 140. In one embodiment, the system 100 It can be configured to support one or more standards, for example the IS-95, the CDMA2000, the IS-856, the W-CDMA, the TD-SCDMA, other multi-link standards or a combination of these.

A base station transceiver system (BTS) disclosed herein may also be designated as and / or to implement the functions of an access network transceiver (ANT), an access point (AP), a base station (BS), a modem battery transceiver (MPT), a node B (for example, in a W-CDMA type system), etc. A cell may refer to a coverage area served by a BTS. A cell can also include one or more sectors. Likewise, a base station controller (BSC) may refer to the portion of a communications system configured to interface with a main network (for example a packet data network) and route the data packets between the ATs and the main network, perform various functions of radio access and link maintenance (such as a soft transfer), radio control transmitters and transceivers, etc. A BSC may also designate how and / or to implement the functions of an access network controller (ANC). A BSC and one or more BTSs may be part of an AN.

An AT disclosed herein may refer to various types of devices, including (but not limited to) a wireless phone, a cell phone, a laptop, a multimedia wireless device, a personal communication card (PC) for wireless communication , a personal digital assistant (PDA), an external or internal modem, etc. An AT can be any data device that communicates through a wireless channel and / or through a wired channel (for example, by means of optical fiber or coaxial cables). An AT may have several names, such as access unit, access node, subscriber unit, mobile station, mobile device, mobile unit, mobile phone, mobile, remote station, remote terminal, remote unit, user device, equipment of user, manual clamping device, etc. Different ATs can be incorporated into a system. ATs can be mobile or fixed, and can be scattered throughout a communications system. An AT may communicate with one or more BTSs about a direct link and / or a reverse link at a given time.

A "transmitter" disclosed herein may be a BTS, an AN, an AT, or any other means configured to transmit data packets through one or more communications links. A "receiver" disclosed herein may be an AT, a BTS, an AN, or any other means configured to receive data packets through one or more communications links. A communications link may include a radio frequency (RF) carrier, a fiber optic link, a coaxial cable, or other digital communications medium, or a combination thereof.

A multilink communications system disclosed herein may include a frequency division multiplexing system, an orthogonal frequency division multiplexing system, or other multilink modulation systems, in which each link corresponds to a range of frequencies

In some single link communications systems, a sender (for example, a BTS) segments a higher level packet (for example an Internet protocol (IP) packet) into a plurality of packets and adds a number of sequence, before the transmission of the packets to a receiver (for example, an AT) by means of a communications link (for example, an RF carrier). The receiver uses the sequence numbers of the received packets to rebuild the original higher level packet. If the receiver detects a gap (or hole) in the sequence numbers (for example, the sequence numbers of consecutive received packets that are not contiguous), then sends a negative confirmation message (NAK) to the sender, indicating the (the) missing package (s) (for example, deleted (s)). The sender then retransmits the missing packet (s).

In a communications system that employs multiple communications links (for example a plurality of RF carriers and / or other digital communications links), because the packets reach the receiver via various communications links, the sequence numbers of the received packages may not be contiguous, even if there are missing packages. In such situations, the above-mentioned packet transmission scheme may cause a large number of NAK messages (for example from the receiver) and spurious retransmitted packets (for example, from the sender) and, as a result, Slow down the data transmission process.

Therefore, there is a need for a new scheme that resolves the aforementioned drawbacks and provides efficient data transmission, within a multi-link communications system.

Embodiments disclosed herein refer to a new set of RLPs configured to provide efficient data transmission within a multilink communications system.

In one embodiment, a method for the transmission of data in a multi-link communication system comprises: the segmentation of a higher level packet into link level packets that must be transmitted over a plurality of communication links; the addition of a first sequence number to each link level packet (for example, according to a predetermined order); and the addition of a second sequence number to each link level packet that must be transmitted for the first time, the second sequence number being in a sequence state associated with a particular communication link. The second sequence number can be used for the detection of the missing packets, as described in more detail below.

In one embodiment, a method for processing data within a multi-link communication system comprises: examining two link level packets received consecutively through a particular communication link, each packet being level of communication. link identified by a first sequence number and a second sequence number, the second sequence number being associated with the particular communication link; and the transmission of a message to a sender to request the retransmission of one or more missing link level packets, if the second sequence numbers of the two data packets received consecutively are not contiguous.

In one embodiment, a multi-link RLP is provided, which includes a segmentation and regrouping part (SAR) and an automatic repeat request part (ARQ). The SAR portion of the RLP may be responsible for the segmentation of a higher level packet (for example an IP packet) into parts, referred to herein as "link level packets", and add a (first) number of sequence, designated herein "SAR_seq", for each link level packet. A receiver can use the SAR_seqs of the received packages to rebuild the higher level package. The ARQ portion of the RLP may add another (or second) sequence number designated herein "ARQ_seq", to each link level packet. The ARQ_seq can belong to a sequence space which is associated with a specific logical communication link, which allows the receiver to detect the missing packets by identifying any gaps in the ARQ_seqs of the packets received through the communication link . The ARQ_seqs can be long enough so that a line break does not occur during a burst of erasures over a communications link, but they do not need to be so long as to prevent a sequence line break during a transmission. In one embodiment, a logical communications link may include direct link pilots that extract packets from the same queue waiting for the BTS.

As an example, FIG. 2 illustrates an embodiment of two "streams" (or "pipelines") 210, 220 of packets arriving at a receiver through two communication links, for example, Link # 1 and Link # 2. For illustrative purposes, each packet is identified by a pair of sequence numbers: SAR_seq and ARQ_seq. If the receiver detects a loophole in the ARQ_seqs of the packets received within each link (for example, the sequence numbers of two packets received consecutively through the same link are noncontiguous according to a transmission scheme), the The receiver can send a message (for example a NAK message) to the sender, informing of the missing package (s). Note that the SAR_seqs within each communication link need not be in order. The receiver can use the SAR_seqs of the received packages (through several links) to reconstruct the original higher level package.

FIG. 3 illustrates an embodiment of a packet segmentation for the first transmitted packets. A higher level packet (for example an IP packet) can be segmented into a plurality of link level packets. Each link level packet may include a sequence number (for example, the least significant bit (s) of the SAR_seq (SAR_seq LSB); a second sequence number, for example an ARQ_seq; other fields of the RLP associated with a given link; and an F / R flag. The F / R flag can be implemented to indicate whether a packet is one transmitted for the first time (for which the F / R flag has been established to be “F ", As shown in FIG. 3), or a retransmitted one, for which the F / R flag is set to be" R ", as shown in FIG. 4). Note that in the embodiment shown, the RLP -ARQ no longer segments an RLP -SAR package, since the RLP -ARQ can request that the RLP -SAR segment the upper level package so that it fits into the payload of the physical level

FIG. 4 illustrates an embodiment of a packet segmentation for retransmitted packets. In this case, the ARQ_seq does not need to be included in a retransmitted packet (since the packet has already been identified as "missing" by the receiver). The F / R flag is set to "R". Note that the length of the SAR_seq field included in a retransmitted RLP -SAR packet may be greater than that of a packet transmitted for the first time (for example SAR_seq vs. SAR_seq LSB). This allows the length of the SAR_seq for the packets transmitted for the first time (which make up the majority of the packets sent) to be small, without causing the RLP -SAR retransmitted packets to skip the line. For example, the length of the SAR_seq of an RLP -SAR packet transmitted for the first time, needs to be long enough so that it does not go out of line during a burst of errors.

In some embodiments, when the RLP packet is retransmitted using a delayed ARQ, designated herein as "D-ARQ", the format shown in FIG. 4. This avoids the possibility of the line break of the small ARQ_seq (as shown in FIG. 3) between the first time the packet was transmitted and the time the packet with the D-ARQ is sent .

FIG. 5 illustrates an embodiment of a protocol stack, for example showing the relationship between the cases of the higher level protocol, the RLP -SAR and RLP -ARQ on each link flow. For illustrative and clarity reasons, two communication links are explicitly shown. The embodiment of FIG. 5 can be extended to a system that employs more than two communication links.

FIG. 6 illustrates an embodiment of an architecture in a multilink communications system, where a BSC 610 is in communication with a service sector that employs two communication links 620, 630. Similar to the single link assumption, the headers of the RLP can be added by the sector to enable just-in-time packaging of RLP packages.

In the embodiment of FIG. 6, associated with each packet in the BSC queue may be metadata indicating the SAR_seq associated with the octets of the packet. The flow control between the BTS and the BSC can be executed using frame identifiers (or "FrameIDs") that are independent of the space of the SAR_seq. Thus, the fact that the higher level packets of each BSC queue can be non-sequential does not influence the interface between BTS -BSC. In some embodiments, the BSC can segment the higher level packets through the BTSs associated with different links. Frame misalignment can be performed on the receiver after the RLP frames are put back together in the order of SAR_seq. If the frame alignment of the higher level packets must be carried out by the RLP, then an RLP packet may not contain octets from more than one higher level packet. If a high-level data link control (HDLC) frame alignment is used, then the RLP payload may contain octets from more than one higher level packet, provided the octets from the higher level packets Be contiguous.

FIG. 7 illustrates an embodiment of how packets are interspersed across multiple links. For example, the RLP packet with SAR_seq = 81 on link # 2 can also include octets 91 -100.

After cell switching, each service BTS can indicate to the BSC a couple of parameters, for example, <FrameID, octet_offset>, associated with the last frame that has served. Based on this information, the BSC can determine which octets should still be served and send only those octets to the new service sector. Unlike the case of the single link, the octets supplied to the new service sector need not be contiguous, as illustrated in FIG. 8.

In one embodiment, upon detection of a gap in the ARQ_seq over any of the communication links, a receiver can send a status information message, which may include the following: a pair of SAR_seq from the beginning and the end of a SAR sequence gap associated with the communication link at the point where the ARQ_seq lagoon has been observed. The recipient may, alternatively, send a NAK message to the sender, which may include such information as the missing SAR_seqs and / or the last SAR_seq received on a communication link.

In one embodiment, the sender can maintain a list of SAR_seqs sent over each communication link. The sender can use this correspondence establishment to determine if a missing SAR packet whose SAR_seq is included in the status report message needs to be retransmitted or not (in the light that it may still be on board). In one embodiment, upon receipt of a status message, the issuer may perform the following associated with each SAR gap reported in the status report message: a) determine the communication link with which the loophole SAR is associated; b) retransmit the RLP data units that are associated with the SAR gap notified in the status report message: determine the communication link with which the SAR gap is associated; b) retransmit the RLP data units that are associated with the SAR gap notified in the status report message and sent over the communication link where the SAR gap is notified.

There may be situations in which a receiver (for example an AT) is re-pointing (or switching) from one cell to another, while receiving packets of multiple communication links. In one embodiment, the sequence space of ARQ_seq can be configured on a per-cell and frequency basis. For example, the ARQ_seq can be initialized when a cell is added to the active set. The ARQ_seq may not be initialized after the cell reboots. Sectors that are in softer transfer can share the same ARQ_seq. In some embodiments, the sender (for example an AN) can specify the sectors that explicitly share the space of the same ARQ_seq, for example, by means of a message that it sends to a receiver (for example an AT). This allows the TA to discover any gap at the beginning of being served from a sector.

In some embodiments, it may be convenient to be able to detect the missing RLP packets at the end of the transmission from a pilot. Consider the following scenarios:

•

A pilot is deleted from the active set and the last few RLP packets sent from that pilot are missing (for example, deleted). Because the receiver can rely on the receipt of a next successful RLP packet to detect a gap in the ARQ_seq, it may not be able to detect such missing RLP packets, and the status report message may not be triggered.

•

An AT reprints its data source channel (DSC) from sector A to sector B (belonging sector A and sector B to different cells) and the last few RLP packets from sector A are deleted. As a result, the AT may not be able to discover such gaps in the ARQ_seqs of the received RLP packets, and the status report message may not be triggered.

In one embodiment, the procedure described as follows can be used to detect deleted RLP packets at the end of a transmission from a pilot. Following the rebound of the DSC or the withdrawal of an active pilot, an AT sends a message to an AN which can include at least the SAR_seq from the pilot (s) that is no longer in the service sector . In some situations, to avoid sending too many NAK messages in the event that an AT establishes a forwarding communication between two cells, the AT may send this report only if a predetermined period of time has elapsed (for example, T ms ) and the AT has not re-targeted its DSC in the original cell). In the case of the DSC rebound, the message may include the SAR_seq from the pilots of the old service sector. In the case of the withdrawal of the active set of a pilot, the message may include the last SAR_seq from the pilot that was removed from the service sector. Upon receipt of the message from the AT, the AN can determine if the AT has lost any packet from the RLP.

There may be situations in which a receiver drops RLP packets that are sent by a sender at the end of a burst of data from one of the communication links. To detect such lost packets, in one embodiment, a receiver may initiate a timer (for example a "trapped" timer) when it detects a gap in a SAR_seq. The timer can be reset if the gap is filled, or if the receiver sends a NAK message that includes the gap (due to other triggers). When the timer expires, the receiver can send a NAK message for this gap. The NAK message may include the last SAR_seq received from all service pilots.

5 In one embodiment, the following can be applied when sending a status report / NAK message:

• If any of the following episodes occur, a receiver (for example, an AT) sends a status report / NAK message:

1. The service cell changes or the service pilot is removed from the active set, and there is a gap in the SAR_seq.

10 2. The AT detects a loophole in the ARQ_seq from a cell.

• If a predetermined period of time (for example T ms) has elapsed from the moment the AT detected a loophole in the SAR_seq, a NAK message including the missing SAR_seqs has not been sent.

• In the case of the withdrawal of the active set of a pilot, the status report message from AT 15 may include at least the SAR_seq from the pilot that has been removed from the service sector.

•

In the case of the DSC rebound, the status report message from the AT may include the last SAR_seq from the pilots of the active service sector.

•

The status report message may include the last SAR_seq from all communication links in the service sector.

20 • Upon receipt of a status report message from the AT, the AN may terminate if the AT has dropped a packet from the RLP.

• Upon receipt of a NAK message from the AT, the AN can transmit the SAR_seq octets of the NAK message that have not been retransmitted.

There may also be situations in which a receiver loses packets from the RLP that are sent by the sender at the end of a burst of data (not precisely from one of the communication links). In one embodiment, the following can be used to detect said missing packages:

• After sending an RLP packet to the sectors, the BSC can start a timer (or a “empty timer”)

•

The timer must be reset whenever the BSC sends a new RLP packet to any of the 30 sectors.

• When the timer expires, the BSC can send an empty message.

one.

The message can indicate to a receiver (for example an AT) that this is the end of the data burst.

2.

This message may include the last RLP package.

•

Upon receipt of the emptying message, if the AT detects that there is a gap in the SAR_seq that has not been previously reported, the AT sends a NAK message.

The examples described below illustrate in greater detail various embodiments disclosed herein.

In an example of removing a pilot from the service sector, consider a scenario in which the pilot belonging to link # 2 is removed from the service sector after the <3, 10> package has been served.

Link # 1 Link # 2 (which is removed)

<ARQ_seq, SAR_seq> <ARQ_seq, SAR_seq> <1, 5> <2, 7> <1, 6> <3, 9> <2, 8> deleted

<3, 10> deleted Upon receipt of a traffic channel assignment message that the pilot removes from the active channel, an AT may send a message to an AN that includes the following information:

AT Status_Report_Message {pilot x link_2: last_SAAR_seq = 6}

The AN then forwards the packets with a SAR_seq = 8, 10, respectively, on any of the 5 remaining pilots in the service sector.

In an example of cell switching, consider a scenario in which the service cell changes and the following packets are served from the old service cell:

Link # 1 Link # 2

<ARQ_seq, SAR_seq> <ARQ_seq, SAR_seq> <1, 5> <2, 7> <1, 6> <3, 9> deleted <2, 8> deleted

<3, 10> deleted

After switching, the AT may send a message to the AN that includes the following information: 10 AT Status_Report_Message {pilot x link_2; last_SAAR_seq = 6 pilot and link_1: last_SAAR_seq = 7}

The AN sends the packets again with the SAR_seq = 8, 9, 10 respectively on any pilot in the service sector.

15 The following illustrates a segment based on an example of SAR_seq:

Link # 1 Link # 2

<ARQ_seq, SAR_seq> <ARQ_seq, SAR_seq> <1, 5> <2, 7> deleted <1, 6> <3, 9> <2, 8> deleted

<3, 10>

When the package <3, 9> is received on link # 1, a receiver can send:

Satuts_Report_message {SAR_missing_boundary = 5, 9}

When the sender receives the previous status report message, he can retransmit only the packet with the

20 SAR_seq = 7, because the status report message indicates to sender a) an erasure has occurred on link # 1 (where packets with SAR_seq = 5, 9 have been sent) and b) the RLP data units which are sent on link # 1 and with the SAR_seq between 5 and 9 are missing. When the sender retransmits the packet with SAR_seq = 7, you can send it over link # 1 or link # 2. The packet retransmitted with SAR_seq = 7, can be sent without ARQ_seq.

25 When the packet <3, 10> is received over link # 2, the receiver can send (assuming that the packet retransmitted with SAR_seq = 7 is going to be already received):

Status_Report_message {SAR_missing_boundary = 6, 10}

When the sender receives the previous status report message, he can retransmit the message with the SAR_seq =

8.

FIG. 9 illustrates an example of an octet-based SAR_seq, which is similar to the segment-based example illustrated above, with the difference that the SAR_seq is an octet-based sequence number. In this case, a receiver can send a status report message after receipt of the RLP packet containing "Octets 81 to 90". The status report is generated because the receiver detects a loophole in the ARQ_seq on link # 1. The status report message may indicate:

• missing_interval: octets with SAR_seq = 51 to 80 are missing in link # 1.

The sender can do the following after receiving the status report message:

For each missing_interval notified, the sender determines the communication link over which the RLP data units have been transmitted, and retransmits the missing data units notified by the receiver that belong to the missing_interval and have been sent over that link. At the time of retransmission, it may not matter which communication link in the service sector is selected to send the missing octets.

FIG. 10 illustrates an example in which a receiver sends a status report message as a result of the detection of a gap in the ARQ_seq. In this case, the communication link (for example, Link # 1) on which the package "1" must be sent may be obstructed and, consequently, unavailable; the package "2" can be deleted during transmission. After the “trapped” timer expires, the receiver sends a status report message requesting the retransmission of packets that are sent over link # 1 and with the SAR_seq between 0 and 2.

FIG. 11 illustrates an example similar to that shown in FIG. 10, with the difference that the status report message is deleted. As a result, the sender resends both "1" and "2" packets upon receipt of the NAK message.

FIG. 12 illustrates a flow chart of a process 1200, which can be used in one embodiment to implement the transmission of data in a multi-link communications system. Step 1210 segments a higher level packet into link level packets so that they are transmitted on a plurality of communication links. Step 1220 adds a first sequence number (for example a SAR_seq LSB or a SAR_seq) for each link level packet. Step 1230 adds a second sequence number (for example an ARQ_seq) for each link level packet to be transmitted during a first time, the second sequence number being in a sequence space associated with a particular communication link.

FIG. 13 illustrates a flowchart of a process 1300, which can be used in an embodiment to implement the data processing of a multilink communications system. Step 1310 examines two link level packets received consecutively through a particular communication link, each link level packet being defined by a first sequence number and a second sequence number, the second sequence number being associated with the specific communication link. Step 1320 transmits a message to a sender to request the transmission of one or more missing link level packets, if the second sequence numbers of the two data packets received consecutively are not contiguous.

FIG. 14 illustrates a block diagram of an apparatus 1400, which can be used to implement some of the disclosed embodiments (such as those described above). By way of example, the apparatus 1400 may include a segmentation unit (or module) 1410 configured to segment a higher level packet into link level packets to be transmitted in a plurality of communication links; and a sequence number addition unit 1420 configured to add a first sequence number to each link level packet (as described above). The sequence number addition unit 1420 can also be configured to add a second sequence number to each link level packet to be transmitted for the first time (as described above). The apparatus 1400 may also include a reception unit 1430 configured to receive a message (such as a status report or NAK message described above) from a receiver, for example, to report missing one or more packages; and a transmission unit 1440 configured to transmit data packets to the receiver.

In the apparatus 1400, the segmentation unit 1410, the sequence number addition unit 1420, the reception unit 1430 and the transmission unit 1440 can be coupled to a communication bus 1450. A processing unit 1460 and a unit of memory 1470 can also be coupled to the communication bus 1450. The processing unit 1460 can be configured to control and / or coordinate the operations of various units. The memory unit 1470 may incorporate instructions that are executed by the processing unit 1460.

FIG. 15 illustrates a block diagram of an apparatus 1500, which can be used to implement some of the disclosed embodiments (such as those described above). By way of example, the apparatus 1500 may include an examination unit (or module) 1510 configured to examine two link level packets received consecutively through a particular communication link, each link level packet being identified by a first sequence number and for a second sequence number; and a transmission unit 1520 configured to transmit a message to a sender, for example if the second sequence numbers of the two data packets received consecutively are noncontiguous, or upon detection of other missing packets (according to as described above). The apparatus 1500 may also include a receiving unit 1530, for example configured to receive data packets and messages from the sender.

In the apparatus 1500, the examination unit 1510, the transmission unit 1520 and the reception unit 1530 can be coupled to a communication bus 1540. The processing unit 1550 and a memory unit 1560 can also be coupled to the communication bus 1540. The processing unit 1550 can be configured to control and / or coordinate the operations of various units. The memory unit 1560 may incorporate instructions that are executed by the processing unit 1550. (In some embodiments, the memory unit 1560 may also store an active set of AT, as described above) .

Various units / modules of FIGS. 14-15 and other embodiments may be implemented in hardware, software, firmware or a combination thereof. Various units / modules described herein may be implemented in hardware, software, firmware or a combination thereof. In a hardware implementation, various units can be implemented within one or more application specific integrated circuits (ASICs), in digital signal processors (DPS), digital signal processing devices (DSPDs), in programmable door arrays on the field (FPGA), in processors, microprocessors, controllers, microcontrollers, programmable logic devices (PLD) other electronic units or any combination of these. In a software implementation, various units can be implemented with modules (procedures, functions, etc.) that carry out the functions described herein. Software codes can be stored in a memory unit and executed in a processor (or a processing unit). The memory unit can be implemented inside the processor or outside the processor, in which case it can be communicatively coupled with the processor through various means known in the art.

Embodiments disclosed herein provide some embodiments of the RLPs and their implementation for multilink communications systems. There are other embodiments and implementations. Various disclosed embodiments can be implemented in a BTS, in a BSC, in an AT, and other transmitters and receivers configured for communications system.

Those skilled in the art will undoubtedly understand that the information and signals can be represented using any of the plurality of different techniques and methods. For example, the data, instructions, commands, information, signals, bits, symbols and chips that may have been referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, fields or magnetic particles, optical fields or particles, or any combination of these.

Experts should also appreciate that the various illustrative logic blocks, modules, circuits and algorithmic stages described in connection with the embodiments disclosed herein, can be implemented as electronic hardware, computer software or as a combination of both. To clearly illustrate this interchangeable nature of hardware and software, various illustrative components, block, modules and stages have been previously described in general terms of their functionality. Whether such functionality is implemented as hardware or as software depends on the specific application and design constraints imposed on the global system. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions should not be interpreted as determining a deviation from the scope of the present invention.

The various illustrative logic blocks, modules, circuits described in connection with the embodiments disclosed herein may be implemented or carried out with a general purpose processor, a digital signal processor (DSP), an application integrated circuit. specific (ASIC), a field programmable door array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described herein memory. A general purpose processor can be a microprocessor but, alternatively, the microprocessor can be any professional processor, controller, microcontroller or state machine. A processor can also be implemented as a combination of computing devices, for example as a combination of a DSP core or any other configuration of the type indicated.

The steps of the procedure or algorithm described in combination with the embodiments disclosed herein may be disclosed directly in hardware, in a software module executed by a processor or in a combination of the two. The software module can reside in a random access memory (RAM), in a flash memory, in a read-only memory (ROM), in an electrically programmable ROM (EPROM), in an electrically programmable programmable ROM (EEPROM), on records, hard drive, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor such that the processor can read the information coming from and write the information to the storage medium. Alternatively, the storage medium can form a body with the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in an AT. Alternatively, the processor and the storage medium may reside as discrete components in an AT.

Claims (27)

1. A method (1200) for the transmission of data in a multi-link communication system (100) comprising: the segmentation (1210) of a higher level packet into link level packets that are to be transmitted over a plurality of communication links; the addition of a first sequence number (1220) to each link level packet; Y the addition of a second sequence number (1230) to each link level packet that must be transmitted a first time, the second sequence number being in a sequence space associated with a particular communication link; Y the reception of a negative confirmation message (NAK) from a receiver, including the NAK message a first loop of the first sequence number indicated by the first sequence numbers of two link level packets received consecutively having a few seconds sequence numbers not contiguous. 2. The method of claim 1, wherein the first sequence number comprises the least significant bits of a segmentation and regrouping sequence number (SAR_seq LSB) and the second sequence number comprises a request sequence number of Auto repeat (ARQ_seq), for each link level packet that must be transmitted a first time. 3. The method of claim 1, wherein the first sequence number comprises a segmentation and regrouping sequence number (SAR_seq), for each link level packet that must be retransmitted. 4. The method of claim 1, further comprising adding a status flag for each link level packet, indicating the status flag if each link level packet is a packet transmitted for the first time or a retransmitted packet 5. The method of claim 1, which also comprises determining a communication link with which the loop of the first sequence number is associated. 6. The method of claim 5, which also comprises the retransmission of one or more link level packets having first sequence numbers that fill the gap of the first sequence number and transmitted over the determined communication link. 7.-A procedure for data processing for a multi-link communication system (100) comprising: the examination of two link level packets (1310) consecutively through a particular communication link, each link level packet being identified by a first sequence number and a second sequence number, the second sequence number being associated with the specific communication link; Y the transmission of a first NAK message (1320) to a sender to request the transmission of one or more missing link level packets, if the second sequence numbers of the two link packets received consecutively are not contiguous. 8. The method of claim 7, wherein the first sequence number comprises the least significant bits of a segmentation and regrouping sequence number (SAR_seq LSB) and the second sequence number comprises a request sequence number of auto repeat (ARQ_seq). 9. The method of claim 7, wherein the first NAK message includes first sequence numbers of two data packets received consecutively. 10. The method of claim 7, which also comprises: receiving an indication of the withdrawal of a pilot from an active set; Y the transmission of a second NAK message to the sender, including the second NAK message the first sequence number of a last link level packet received from the pilot before being removed from the active set. 11. The method of claim 10, wherein the second NAK message is transmitted after a predetermined period of time after receipt of the indication. 12. The method of claim 7, which also comprises: switching a service cell from a first cell to a second cell; Y the transmission of a second NAK message to the sender, including the second NAK message, the first sequence number of a last link level packet from each pilot associated with the first cell. 13. The method of claim 12, wherein the second NAK message is transmitted after a predetermined period of time after receipt of the indication. 14. The method of claim 7, which also comprises: the reception of an emptying message from a sender, the emptying message indicating the end of a burst of data and including a last transmitted link level packet; Y Sending a NAK message to the sender, if a loophole is detected in the sequence numbers of the link level packets received. 15. The method of claim 14, wherein each sequence number comprises a segmentation and regrouping sequence number (SAR_seq). 16. The method of claim 7, which also comprises: the start of a timer after the detection of a gap in the second sequence numbers of the received link level packets; Y the transmission of a NAK message to a sender after the expiration of the timer, including the NAK message the gap and the sequence number of a last data packet received from each service pilot. 17. The method of claim 16, which also comprises resetting the timer, upon receipt of one or more data packets that have sequence numbers that fill the first gap. 18. The method of claim 16, which also comprises resetting the timer, after the transmission of the NAK message to the sender. 19. The method of claim 16, wherein the sequence number comprises a segmentation and regrouping sequence number (SAR_seq). 20.-An apparatus (1400) adapted for the transmission of data in a multi-link communication system (100), comprising: means for the segmentation (1410) of a higher level packet into link level packets that must be transmitted over a plurality of communication links; means for adding a first sequence number (1420) to each link level packet; Y means for adding a second sequence number (1430) to each link level packet that must be transmitted a first time, the second sequence number being in a sequence space associated with a particular communication link, and means for receiving a negative confirmation message (NAK) from a receiver, including the NAK message a loop of first sequence number indicated by the first sequence numbers of two link level packets received consecutively presenting a few seconds sequence numbers not contiguous. 21. The apparatus of claim 20, wherein the first sequence number comprises the least significant bits of a segmentation and regrouping sequence number (SAR_seq LSB) and the second sequence number comprises a request sequence number of Auto repeat (ARQ_seq) for each link level packet that must be transmitted a first time. 22. The apparatus of claim 20, wherein the first sequence number comprises a segmentation and regrouping sequence number (SAR_seq) for each link level packet to be retransmitted. 23.-An apparatus (1500) adapted for data processing in a multi-link communication system (100), comprising: means for the examination (1510) of two link level packets received consecutively through a specific communication link (1540), each link level packet being characterized by a first sequence number and a second number sequence, the second sequence number being associated with the specific communication link (1540); Y means for the transmission (1520) of a NAK message to a sender to request a retransmission of one or more missing link level packets, if the second sequence numbers of the two consecutive data packets received are not contiguous. 24. The apparatus of claim 23, wherein the first sequence number comprises the least significant bits of a segmentation and regrouping sequence number (SAR_seq LSB) and the second sequence number comprises a request sequence number of auto repeat (ARQ_seq). 25. The apparatus of claim 23, wherein the NAK message includes the first sequence numbers of the two data packets received consecutively. 26.-A computer-readable medium that incorporates instructions executable by a processor to: segmenting a higher level packet into link level packets that must be transmitted over a plurality of communication links (1540); add a first sequence number to each link level packet; Y adding a second sequence number to each link level packet that must be transmitted a first time, the second sequence number being in a sequence space associated with a particular communication link (1540); Y receive a negative confirmation message (NAK) from a receiver, including the NAK message a loop of first sequence number indicated by the first sequence numbers of two link level packets received consecutively having a second sequence number not contiguous 27.-A computer-readable medium that incorporates instructions executable by a processor to: examine two link level packets received consecutively through a particular communication link (1540), each link level packet being defined by a first sequence number and a second sequence number, the second number being sequence associated with the specific communication link (1540); Y transmit a NAK message to a sender to request the retransmission of one or more missing link level packets, if the second sequence numbers of two consecutive data packets received are not contiguous.