Source: https://patents.google.com/patent/US9379804
Timestamp: 2018-03-18 10:16:45
Document Index: 683516452

Matched Legal Cases: ['Application No. 2009325082', 'Application No. 2', 'Application No. 2', 'Application No. 200980149651', 'Application No. 200980156892', 'Application No. 200980149651', 'Application No. 200980149651', 'Application No. 200980156929', 'Application No. 09752588', 'Application No. 09789422', 'art 16', 'Application No. 2011', 'Application No. 2013']

US9379804B2 - System and method for hybrid automatic repeat request (HARQ) functionality in a relay node - Google Patents
US9379804B2
US9379804B2 US14465528 US201414465528A US9379804B2 US 9379804 B2 US9379804 B2 US 9379804B2 US 14465528 US14465528 US 14465528 US 201414465528 A US201414465528 A US 201414465528A US 9379804 B2 US9379804 B2 US 9379804B2
US14465528
US20140362755A1 (en )
Devices and methods related to relay nodes are provided. The relay node includes a first hybrid automatic repeat request (HARQ) entity providing a first HARQ functionality. The relay node further includes a second HARQ entity providing a second HARQ functionality.
This application is a continuation of U.S. patent application Ser. No. 13/842,584 filed Mar. 15, 2013 by Yi Yu, et al. entitled, “System and Method for Hybrid Automatic Repeat Request (HARQ) Functionality in a Relay Node”, which is a continuation of U.S. Pat. No. 8,402,334, issued on Mar. 19, 2013 entitled, “System and Method for Hybrid Automatic Repeat Request (HARQ) Functionality in a Relay Node”, both of which are incorporated by reference herein as if reproduced in their entirety.
FIG. 2 is a block diagram illustrating an end-to-end hybrid automatic repeat request (HARQ) communication system, according to an embodiment of the disclosure.
FIG. 3 is a block diagram illustrating an independent hybrid automatic repeat request (HARQ) communication system, according to an embodiment of the disclosure.
FIG. 4A is a flowchart of a method in a relay node on a downlink, according to an embodiment of the disclosure.
FIG. 4B is a flowchart of a method in a relay node on a downlink, according to an embodiment of the disclosure.
FIG. 5A is a flowchart of a method in a relay node on an uplink, according to an embodiment of the disclosure.
FIG. 5B is a flowchart of a method in a relay node on an uplink, according to an embodiment of the disclosure.
FIG. 6 illustrates a processor and related components suitable for implementing the several embodiments of the present disclosure.
FIG. 1 is a diagram illustrating a wireless communication system 100 using a relay node 102, according to an embodiment of the disclosure. Generally, the present disclosure relates to the use of relay nodes in wireless communications networks. Examples of a wireless communication network includes LTE or LTE-Advanced (LTE-A) networks, and all of the disclosed and claimed embodiments could be implemented in an LTE-A network. The relay node 102 can amplify or repeat a signal received from a UA 110 and cause the modified signal to be received at an access node 106. In some implementations of a relay node 102, the relay node 102 receives a signal with data from the UA 110 and then generates a new signal to transmit the data to the access node 106. The relay node 102 can also receive data from the access node 106 and deliver the data to the UA 110. The relay node 102 might be placed near the edges of a cell so that the UA 110 can communicate with the relay node 102 rather than communicating directly with the access node 106 for that cell.
In radio systems, a cell is a geographical area of reception and transmission coverage. Cells can overlap with each other. In the typical example, there is one access node associated with each cell. The size of a cell is determined by factors such as frequency band, peak transmission power levels, and channel conditions. Relay nodes, such as relay node 102, can be used to enhance coverage within or near a cell, or to extend the size of coverage of a cell. Additionally, the use of a relay node 102 can enhance throughput of a signal within a cell because the UA 110 can access the relay node 102 at a higher data rate or a lower power transmission than the UA 110 might use when communicating directly with the access node 106 for that cell. Transmission at a higher data rate within the same bandwidth creates higher spectrum efficiency, and lower power benefits the UA 110 by consuming less battery power.
Wireless communication systems may use error checking and correction systems to improve the quality of wireless communications. While error checking and correction systems have been implemented in user agents and/or access nodes that communicate directly with each other, introduction of relay nodes in wireless communications systems raise issues about implementing error checking and correction systems related to relay nodes.
The illustrative embodiments provide an error checking and correcting system in a wireless communication system that includes at least one relay node. In one illustrative embodiment, an error checking and correction system is implemented on the relay node. Implementing an error checking and correction system on a relay node can increase scheduling gain, and can have other benefits described further below.
In a specific illustrative embodiment, a relay node is in communication with an access node and a user agent. The relay node includes a hybrid automatic repeat request (HARQ) entity. HARQ is a variation of the “automatic repeat request” (ARQ) error control method. A HARQ entity is software and/or hardware that provides one or more HARQ functionalities. HARQ functionalities include, but are not limited to, retransmission combining techniques that enlist Chase combining or incremental redundancy, control of NACK/ACK transmissions, monitoring the number of retransmissions of MAC PDUs and ensuring that they do not exceed a maximum, and others as known in the art. The term “HARQ functionality,” as used herein, contemplates one or more of these HARQ functionalities.
In either HARQ or ARQ, data and error detection information bits are first transmitted. If a recipient of the transmission detects no errors, the recipient accepts the data. If the recipient detects errors, the recipient might request a retransmission of data and error detection information or other error correction information that will help in the successful reception of the data.
In another illustrative embodiment, an end-to-end HARQ system is created between the access node and the user agent without the involvement of the relay node related to this error detection and correction. Thus, this illustrative embodiment does not necessarily require implementing a HARQ entity on a relay node. This particular illustrative embodiment is described with respect to FIG. 2. The devices described with respect to FIG. 2 can be characterized as one or more processors configured to promote the actions described in the embodiments provided below.
FIG. 2 is a block diagram illustrating an end-to-end HARQ communication system 200, according to an embodiment of the disclosure. The system 200 includes the access node 106 in communication with the user agent 110 via the relay node 102. The access node 106 and the user agent 110 include peer Hybrid Automatic Repeat Request (HARQ) entities 202 and 204, respectfully.
When the access node 106 sends a medium access control (MAC) packet data unit (PDU) to the relay node 102, the relay node 102 will demodulate and decode the MAC PDU (transport block 1 (TB1)) without any cyclic redundancy check (CRC) (error detection) of TB1. Then, the relay node 102 will forward the transport block 1 (TB1) with a possible different modulation and coding scheme (MCS) to the user agent 110.
After the user agent 110 receives the transport block 1, the user agent 110 will perform the CRC and send a non-acknowledgement/acknowledgement (NACK/ACK) signal to the relay node 102, as shown by arrow 108. (Arrow 108 can also represent the access link.) In turn, the relay node 102 will forward the NACK/ACK to the access node 106, as shown by arrow 104. (Arrow 104 can also represent the relay link.) Based on the received NACK/ACK information, the access node 106 will perform the retransmission of the transport block 1 (the MAC PDU) or transmission of other error detection and correction information, if desired or necessary.
Similarly in the uplink, when the UA 110 sends a MAC PDU to the relay node 102, the relay node will demodulate and decode the MAC PDU without any CRC (error detection) of the transmitted transport block (TB). Then the relay node 102 will forward the TB with a possible different MCS to the access node 106. After the access node 106 receives the TB, the access node 106 will perform the CRC and send a NACK/ACK signal to the relay node 102 based on the result. Then the relay node 102 will forward the NACK/ACK to the UA 110. The UA 110 may perform the retransmission of the TB or transmission of other error detection and correction information if a NACK is received.
A major benefit of the illustrative embodiment shown in FIG. 2 is that the relay node 102 need not provide HARQ functionality. However, several disadvantages of this system may exist.
One disadvantage is that an error at the relay link 104 will be propagated to the access link access link 108. Error propagation can cause unnecessary battery drain for the user agent 110. Considering that a ten percent block error rate (BLER) may be common for the initial transmission, unnecessary battery drain in the user agent is likely.
Another disadvantage may be in the difficulty of controlling timing relationship between the packet transmission and the NACK/ACK feedback due to possible variable scheduling delays in the relay node when performing forwarding. Furthermore, additional complexity may exist on the resource link between the packet transmission and associated NACK/ACK (i.e., the resource to be used to transmit a NACK/ACK for a certain packet transmission), partially due to this possible variable delay.
Yet another disadvantage may be that radio link conditions differ between the relay link (arrow 104) and the access link (arrow 108). In the illustrative embodiment shown in FIG. 2, the size of TB1 (the MAC PDU) has to be the same on the relay link 104 and the access link 108. However, if the radio conditions change, keeping the same transport block size for the transmission limits the scheduling gain, and may also affect throughput.
Still another disadvantage may be that the NACK/ACK error ratio may be greater because two links (relay and access) are involved for the NACK/ACK feedback. However, these problems may be overcome by implementing a HARQ entity on the relay node 102 itself. This system is shown in FIG. 3.
FIG. 3 is a block diagram illustrating an independent HARQ communication system 300 according to an embodiment of the disclosure. The independent HARQ communication system 300 shown in FIG. 3 includes objects described with respect to FIG. 1 and FIG. 2. Thus, FIGS. 2 and 3 have some common reference numerals that refer to similar objects. The devices described with respect to FIG. 3 can be characterized as one or more processors configured to promote the actions described in the embodiments provided below.
However, in addition to the user agent 110 and the access node 106 having HARQ entities 202 and 204, respectfully, the relay node 102 includes its own HARQ entities 302 and 304. HARQ entities 302 and 304 handle decoding and encoding of error detection and correction bits on the relay node 102. HARQ entities 302 and 304 could be separate entities, but could also be characterized as a single HARQ entity. As with the description of FIG. 2, a HARQ entity can be implemented using software, firmware or hardware, or any combination that can implement HARQ functionality.
In the illustrative system 300 shown in FIG. 3, both the relay link 104 and the access link 108 operate with respect to their own independent HARQ entities, HARQ entity 302 and HARQ entity 304, respectively. HARQ entity 302 and HARQ entity 304 are stored on or are a part of relay node 102.
When the access node 106 sends a data packet and error detection information to the relay node 102, as shown by arrow 303A, the relay node 102 will demodulate and decode the data packet and perform cyclic redundancy check (CRC) (error detection). The relay node 102 will then send a NACK/ACK to the access node 106, as shown by arrow 303B. In turn, the access node 106 will perform a HARQ retransmission, if desired or necessary.
When the relay node 102 successfully receives the MAC PDU as determined by the HARQ entity 302, the relay node 102 will deliver the received MAC PDU to a higher layer. Then, the relay node 102 will further schedule and transmit the data to the user agent user agent 110, where the HARQ entity 304 handles HARQ processing for the relay node 102 of the data to be sent to the user agent 110. The relay node 102 may resegment the MAC PDU depending on the radio conditions, as shown by arrow 305A. After the user agent 110 receives the data, the user agent 110 will send a NACK/ACK to the relay node 102, as shown by arrow 305B. In turn, the relay node 102 will perform HARQ retransmission, if required or desired. No direct feedback to the access node is necessary from the user agent 110.
Similarly in the uplink, when the UA 110 sends a MAC PDU to the relay node 102, the relay node 102 will demodulate and decode the MAC PDU and perform a cyclic redundancy check (CRC). These functions are examples of HARQ functionalities, though fewer or more HARQ functionalities exist and could be used, as known in the art. The relay node 102 will then send a NACK/ACK to the UA 110 based on the results of the CRC. In turn, the UA 110 will perform HARQ retransmission, if desired or necessary. When the relay node 102 successfully receives the MAC PDU, the relay node 102 may deliver the data to the RLC layer and then the relay node may schedule and send the data to the access node 106. The relay node 102 may resegment or concatenate the data depending on the radio conditions. After the access node 106 receives the MAC PDU, it will perform a CRC. Based on the results of the CRC, the access node 106 will send a NACK/ACK to the relay node 102. In turn, the relay node 102 will perform a retransmission, if required or desired. No direct feedback to the UA 110 is necessary from the access node 106.
The illustrative embodiment shown in FIG. 3 may have several benefits. For example, the relay node 102 forwards the MAC PDU only when no errors are detected. This feature allows for more efficient use of resources of the access link 108.
Another benefit to the solution shown in FIG. 3 is that exploitation of the specific radio condition on each link is possible. For example, the MAC protocol, radio link control protocol or packet data converged protocol can segment or concatenate MAC PDUs, allowing for a different transport block size (TBS) on the access link 108 and higher scheduling gain. A further benefit to the solution shown in FIG. 3 is that the fixed timing between the packet transmission and the NACK/ACK transmission is maintained.
While the embodiments described with respect to FIG. 3 contemplate a relay node having two HARQ entities, other embodiments could also be implemented. For example, a single HARQ entity could be implemented in relay node 102, with the single HARQ entity performing both functions of the separate HARQ entities, HARQ entity 302 and HARQ entity 304.
Additionally, the embodiments contemplate multiple relay nodes between access node 106 and user agent 110. Each one of the additional relay nodes could have one HARQ entity, two HARQ entities, or no HARQ entities. In the latter case, the relay node would only relay a signal without performing some HARQ functionality.
Furthermore, if desired, more than two HARQ entities could be implemented on one or more relay nodes. Multiple HARQ entities could be assigned to handle different sets of UAs, different access nodes, or be used for other purposes.
FIG. 4A is a flowchart of a method in a relay node on a downlink, according to an embodiment of the disclosure. An example of a relay node and its operation are described above, and in particular with respect to FIGS. 1-3. The process can be implemented using software, hardware, firmware, or a combination thereof.
The process begins as the relay node receives a MAC PDU from an access node, wherein the MAC PDU is received at a relay node including a first hybrid automatic repeat request (HARQ) entity and a second HARQ entity (block 400A). The relay node then performs, using the first HARQ entity, a first HARQ functionality with respect to the MAC PDU (block 402A). This first HARQ functionality may terminate the HARQ process for the MAC PDU between the access node and relay node.
Next, the relay node may re-segment and re-encode the MAC PDU before the relay node schedules and transmits the MAC PDU to a user agent (block 404A). Thereafter, the relay node may receive a NACK/ACK from the UA with the second HARQ entity (block 406A). Finally, responsive to receiving the NACK/ACK, the relay node may perform a HARQ retransmission (block 408A). The process terminates thereafter.
As provided in block 404A, a possibility exists that the relay node changes the MAC PDU. For example, the relay node could resegment or concatenate the MAC PDUs, re-encode the MAC PDUs, or both resegment and re-encode the MAC PDU. In any of these three cases, the relay node schedules and transmits the MAC PDU.
In the embodiment provided in FIG. 4A, a single relay node with two HARQ entities is described. However, the embodiments also contemplate variations on this technique. For example, two or more relays could be used between the UA and the access node. For one or more of the relay nodes, as with the single relay node described in FIG. 4A, each relay node could have two HARQ entities. However, one or more relay nodes could instead have no HARQ entities, with the method proceeding as shown in FIG. 4A for those relay nodes that do have HARQ entities. Additionally, one or more relay nodes could instead have a single HARQ entity that performs the function of the two separate HARQ entities described above. Other modifications to these embodiments could also be implemented.
FIG. 4B is a flowchart of a method in a relay node on a downlink, according to an embodiment of the disclosure. An example of a relay node and its operation are described above, and in particular with respect to FIGS. 1-3. The process can be implemented using software, hardware, firmware or a combination thereof.
The process begins as the relay node receives a MAC PDU from an access node (block 400B). The relay node then demodulates the MAC PDU without performing a cyclic redundancy check (CRC) (block 402B). The relay node then forwards the MAC PDU to a user agent (block 404B). The modulation may be different, but the MAC PDU may not be re-segmented. The MAC PDU may or may not be re-encoded.
After receiving a non-acknowledgement/acknowledgement signal (NACK/ACK) from the user agent, the relay node forwards the NACK/ACK to the access node (block 406B). After forwarding the NACK/ACK to the access node, the relay node may receive a retransmission from the access node (block 408B). The relay node then forwards the retransmission to the user agent (block 410B). The relay node then either receives an ACK signal from the UA, or determines whether a maximum number of retransmissions has been completed (block 412B). If an ACK is received, or a maximum number of retransmissions has been completed, then the process terminates. If a maximum number of retransmissions has not been completed, then the process could return to step 406 and repeat until the maximum number of allowed retransmissions has been completed.
FIG. 5A is a flowchart of a method in a relay node on an uplink, according to an embodiment of the disclosure. An example of a relay node and its operation are described above, and in particular with respect to FIGS. 1-3. The process can be implemented using software, hardware, firmware or a combination thereof.
The process begins as the relay node receives a MAC PDU from a UA (block 500A). The relay node then demodulates the MAC PDU without any CRC of the transmitted transport block (bock 502A). The relay node forwards the transport block, possibly with a different MCS (modulation and coding scheme), to an access node (block 504A). Subsequently, the relay node receives a NACK/ACK signal from the access node (block 506A). In turn, the relay node forwards the NACK/ACK to the UA (block 508A). If desired or necessary, the relay node receives a retransmission of the MAC PDU from the UA (block 510A) and then forwards the retransmission of the MAC PDU to the access node (block 512A). The process terminates thereafter.
FIG. 5B is a flowchart of a method in a relay node on an uplink, according to an embodiment of the disclosure. An example of a relay node and its operation are described above, and in particular with respect to FIGS. 1-3. The process can be implemented using software, hardware, firmware or a combination thereof. In the embodiments of FIG. 5B, the various functions implemented in the relay node could be implemented by one or more HARQ entities, as provided with respect to FIG. 3.
The process begins as the relay node receives a MAC PDU from a user agent at a first HARQ entity (bock 500B). The relay node 102, using the first HARQ entity, demodulates the MAC PDU and may perform a cyclic redundancy check (CRC) (block 502B). These functions are examples of HARQ functionalities, though fewer or more HARQ functionalities exist and could be used, as known in the art.
The relay node 102 will then send, using the first HARQ entity, a NACK/ACK to the UA based on the results of the CRC (block 504B). Based on the results of the NACK/ACK, a determination is made if the relay node should receive a HARQ retransmission of the MAC PDU from the UA (block 506B). If a HARQ retransmission is desired or necessary, then the process returns to step 500B and repeats.
If HARQ retransmission is not desired or possibly is not necessary, then once the relay node receives the MAC PDU, the relay node will schedule and send the MAC PDU to the access node using a second HARQ entity (bock 508B). In an embodiment, the relay node's second HARQ entity may resegment or concatenate the MAC PDUs, depending on radio conditions. The relay node then waits to receive a signal from the access node, which itself may perform a CRC check. The relay node will receive a NACK/ACK from the access node at the second HARQ entity (block 510B). In turn, the relay node will perform a retransmission to the access node, if desired or required (block 512B). The process terminates thereafter. Note that no direct feedback to or from the UA is necessary between the UA and the access node.
In the embodiments provided in FIG. 5B, a single relay node with two HARQ entities is used to implement the above-described methods. However, the embodiments also contemplate variations on this technique. For example, two or more relays could be used between the UA and the access node. For one or more of the relay nodes, as with the single relay node described in FIG. 5B, each relay node could have two HARQ entities. However, one or more relay nodes could instead have no HARQ entities, with the method proceeding as shown in FIG. 5B for those relay nodes that do have HARQ entities. Additionally, one or more relay nodes could instead have a single HARQ entity that performs the function of the two separate HARQ entities described above. Other modifications to these embodiments could also be implemented.
The user agent 110 and other components described above might include a processing component that is capable of executing instructions related to the actions described above. FIG. 6 illustrates an example of a system 1300 that includes a processing component 1310 suitable for implementing one or more embodiments disclosed herein. In addition to the processor 1310 (which may be referred to as a central processor unit or CPU), the system 1300 might include network connectivity devices 1320, random access memory (RAM) 1330, read only memory (ROM) 1340, secondary storage 1350, and input/output (I/O) devices 1360. These components might communicate with one another via a bus 1370. In some cases, some of these components may not be present or may be combined in various combinations with one another or with other components not shown. These components might be located in a single physical entity or in more than one physical entity. Any actions described herein as being taken by the processor 1310 might be taken by the processor 1310 alone or by the processor 1310 in conjunction with one or more components shown or not shown in the drawing, such as a digital signal processor (DSP) 502. Although the DSP 502 is shown as a separate component, the DSP 502 might be incorporated into the processor 1310.
The following are incorporated herein by reference for all purposes: 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 36.300, 3GPP TS 36.321.
As described herein, the illustrative embodiments provide for a relay node. The relay node includes a first hybrid automatic repeat request (HARQ) entity providing a first HARQ functionality. The relay node further includes a second HARQ entity providing a second HARQ functionality.
The illustrative embodiments also provide for a relay node having a different configuration. In this different configuration, the relay node is configured to receive a medium access control packet data unit (MAC PDU) from an access node, demodulate and decode the MAC PDU without performing a cyclic redundancy check (CRC), forward the MAC PDU to a user agent, and, after receiving a non-acknowledgement/acknowledgement signal (NACK/ACK) from the user agent, forward the NACK/ACK to the access node.
The illustrative embodiments also provide for a method implemented in a relay node comprising a first hybrid automatic repeat request (HARQ) entity providing a first HARQ functionality and a second HARQ entity providing a second HARQ functionality. The method includes receiving a medium access control packet data unit (MAC PDU) from an access node, and performing, with the first HARQ entity, a first HARQ functionality with respect to the MAC PDU.
The illustrative embodiments also provide for a different method implemented in a relay node comprising a first hybrid automatic repeat request (HARQ) entity providing a first HARQ functionality and a second HARQ entity providing a second HARQ functionality. In this method, a medium access control packet data unit (MAC PDU) is received from an access node. Using the first HARQ entity, a first HARQ functionality is performed with respect to the MAC PDU.
1. A long term evolution (LTE) relay node configured to:
receive a first medium access control packet data unit (MAC PDU) from an LTE eNodeB, wherein a first hybrid automatic repeat request (HARQ) entity is configured to perform HARQ functionality with respect to the first MAC PDU; and
receive a second MAC PDU from an LTE user equipment (UE), wherein a second HARQ entity is configured to perform HARQ functionality with respect to the second MAC PDU.
2. The LTE relay node of claim 1, wherein the LTE relay node is configured to avoid transmitting the first MAC PDU to the LTE UE unless the first MAC PDU is free of errors when received from the LTE eNodeB.
3. The LTE relay node of claim 2, wherein the LTE relay node is configured to break apart the first MAC PDU to create different transport block sizes (TBS).
4. The LTE relay node of claim 3, wherein transport block size depends on radio conditions.
5. The LTE relay node of claim 1, wherein the LTE relay node is further configured to perform a cyclic redundant check (CRC) and to transmit a non-acknowledgement/acknowledgement (NACK/ACK) signal to the LTE eNodeB.
6. The LTE relay node of claim 5, wherein the LTE relay node is further configured to schedule and send the first MAC PDU to the LTE UE.
7. The LTE relay node of claim 6, wherein the LTE relay node is configured to receive a non-acknowledgement/acknowledgement (NACK/ACK) signal from the LTE UE.
8. The LTE relay node of claim 7, wherein the LTE relay node is further configured to maintain a fixed timing between transmission of the first MAC PDU and the NACK/ACK.
9. The LTE relay node of claim 1, wherein the LTE relay node is configured to break apart the second MAC PDU to create different transport block sizes (TBS).
10. The LTE relay node of claim 1, wherein transport block size depends on radio conditions.
11. A method implemented in a long term evolution (LTE) relay node, the method comprising:
receiving a first medium access control packet data unit (MAC PDU) from an LTE eNodeB, wherein a first hybrid automatic repeat request (HARQ) entity is configured to perform HARQ functionality with respect to the first MAC PDU; and
receiving a second MAC PDU from an LTE user equipment (UE), wherein a second HARQ entity is configured to perform HARQ functionality with respect to the second MAC PDU.
breaking apart the first MAC PDU to create different transport block sizes (TBS).
13. The method of claim 12, wherein transport block size depends on radio conditions.
scheduling the first MAC PDU; and
sending the first MAC PDU to the LTE UE.
receiving a non-acknowledgement/acknowledgement (NACK/ACK) signal.
responsive to receiving the non-acknowledgement signal (NACK), performing a hybrid automatic repeat request (HARQ) retransmission.
17. The method of claim 15, wherein a retransmission is avoided when an ACK is received.
maintaining a fixed timing between transmission of the first MAC PDU and the NACK/ACK.
19. The method of claim 11, wherein transmission of the first MAC PDU to the LTE UE is avoided unless the first MAC PDU is free of errors when received at the first HARQ entity.
20. The method of claim 11, wherein the LTE relay node is configured to perform a cyclic redundant check (CRC) and to transmit a non-acknowledgement/acknowledgement (NACK/ACK) signal to the LTE eNodeB.
US14465528 2008-12-17 2014-08-21 System and method for hybrid automatic repeat request (HARQ) functionality in a relay node Active US9379804B2 (en)
US12337229 US8402334B2 (en) 2008-12-17 2008-12-17 System and method for hybrid automatic repeat request (HARQ) functionality in a relay node
US13842584 US8856607B2 (en) 2008-12-17 2013-03-15 System and method for hybrid automatic repeat request (HARQ) functionality in a relay node
US14465528 US9379804B2 (en) 2008-12-17 2014-08-21 System and method for hybrid automatic repeat request (HARQ) functionality in a relay node
US13842584 Continuation US8856607B2 (en) 2008-12-17 2013-03-15 System and method for hybrid automatic repeat request (HARQ) functionality in a relay node
US20140362755A1 true US20140362755A1 (en) 2014-12-11
US9379804B2 true US9379804B2 (en) 2016-06-28
ID=41665076
US12337229 Active 2031-08-11 US8402334B2 (en) 2008-12-17 2008-12-17 System and method for hybrid automatic repeat request (HARQ) functionality in a relay node
US13842584 Active US8856607B2 (en) 2008-12-17 2013-03-15 System and method for hybrid automatic repeat request (HARQ) functionality in a relay node
US14465528 Active US9379804B2 (en) 2008-12-17 2014-08-21 System and method for hybrid automatic repeat request (HARQ) functionality in a relay node
US (3) US8402334B2 (en)
JP (1) JP2012512599A (en)
KR (2) KR101317292B1 (en)
CN (1) CN102318255B (en)
CA (1) CA2747339C (en)
EP (1) EP2377260B1 (en)
WO (1) WO2010077419A1 (en)
KR100966566B1 (en) * 2009-01-29 2010-06-29 엘지전자 주식회사 Signal transmission scheme for efficient management of common e-dch
KR20110127677A (en) * 2009-02-09 2011-11-25 인터디지탈 패튼 홀딩스, 인크 Apparatus and method for uplink power control for a wireless transmitter/receiver unit utilizing multiple carriers
EP2465225A4 (en) 2009-08-13 2017-07-05 Samsung Electronics Co Ltd Method and apparatus for transmitting reference signals in communication systems
WO2011041666A3 (en) * 2009-10-01 2011-12-08 Interdigital Patent Holdings, Inc. Power control methods and apparatus
KR101524209B1 (en) * 2014-05-02 2015-05-29 경상대학교산학협력단 Apparatus and method for determining trasmitting power of relay
US6014375A (en) * 1997-02-13 2000-01-11 Ericsson Inc. TDMA radio protocol with adaptive vocoder selection
US20030101274A1 (en) 2001-11-24 2003-05-29 Lg Electronics Inc. Packet transmission scheduling technique
US7054633B2 (en) * 2002-02-17 2006-05-30 Samsung Electronics Co., Ltd. Apparatus and method for transmitting and receiving uplink power offset information in a mobile communication system supporting HSDPA
WO2007048247A1 (en) 2005-10-27 2007-05-03 Nortel Networks Limited Methods and systems for a wireless routing architecture and protocol
US20070274250A1 (en) 2004-02-06 2007-11-29 Matsushita Electric Industrial Co.,Ltd Method and System for Detecting Network Connection in Ipv6 Radio Access Network
US20080089282A1 (en) 2006-08-23 2008-04-17 Malladi Durga P Acquisition in frequency division multiple access systems
EP1919234A2 (en) 2006-11-02 2008-05-07 Fujitsu Limited Determining transmitting stations in an OFDMA network
US20080107072A1 (en) 2006-11-02 2008-05-08 Fujitsu Limited Determining transmitting stations in an OFDMA network
WO2008103981A2 (en) 2007-02-23 2008-08-28 Texas Instruments Incorporated Secondary synchronization channel design for ofdma systems
US20080232493A1 (en) 2007-03-19 2008-09-25 Interdigital Technology Corporation Combined precoding vector switch and frequency switch transmit diversity for secondary synchronization channel in evolved utra
US20090010199A1 (en) 2007-07-03 2009-01-08 Tomoko Adachi Wireless communication apparatus and wireless communication method
US20090190522A1 (en) 2008-01-30 2009-07-30 Qualcomm Incorporated Management of wireless relay nodes using routing table
US20090196177A1 (en) 2008-02-01 2009-08-06 Nokia Siemens Networks Oy Method, apparatus and computer program for uplink scheduling in a network that employs relay nodes
US7602843B2 (en) * 2005-01-05 2009-10-13 Samsung Electronics Co., Ltd Apparatus and method for transmitting/receiving channel quality information in a communication system
US7673211B2 (en) * 2005-05-23 2010-03-02 Telefonaktiebolaget L M Ericsson (Publ) Automatic repeat request (ARQ) protocol having multiple complementary feedback mechanisms
US7830837B2 (en) * 2008-03-21 2010-11-09 Lg Electronics Inc. Method of data communication in a wireless communication system
US20100296431A1 (en) * 2008-08-11 2010-11-25 Interdigital Patent Holdings, Inc. Method and apparatus for using a relay to provide physical and hybrid automatic repeat request functionalities
US7873002B2 (en) * 2006-09-19 2011-01-18 Zte (Usa) Inc. Frame structure for multi-hop relay in wireless communication systems
US20110317648A1 (en) 2005-11-01 2011-12-29 Young Dae Lee Method of transmitting and receiving wireless resource information
US8121552B2 (en) * 2006-09-05 2012-02-21 Motorola Mobility, Inc. Method and apparatus for providing channel quality feedback in a wireless communication system
US20120057560A1 (en) * 2009-05-11 2012-03-08 Sung Jun Park Method and apparatus for transmitting and receiving duplicate data in a multicarrier wireless communication system
US20150163821A1 (en) * 2013-12-06 2015-06-11 Htc Corporation Method of Handling Device-to-Device Communication and Communication Device Thereof
US20070097945A1 (en) 2005-10-27 2007-05-03 Wang Guo Q Methods and systems for a wireless routing architecture and protocol
US8576882B2 (en) 2006-05-11 2013-11-05 Blackberry Limited Media access control protocol for multi-hop network systems and method therefore
US20080107078A1 (en) 2006-11-02 2008-05-08 Fujitsu Limited Determining transmitting stations in an OFDMA network
US20130094431A1 (en) * 2008-08-11 2013-04-18 Interdigital Patent Holdings, Inc. Method and apparatus for using a relay to provide physical and hybrid automatic repeat request functionalities
US8175014B2 (en) * 2008-08-11 2012-05-08 Interdigital Patent Holdings, Inc. Method and apparatus for using a relay to provide physical and hybrid automatic repeat request functionalities
US8605674B2 (en) * 2009-05-11 2013-12-10 Lg Electronics Inc. Method and apparatus for transmitting and receiving duplicate data in a multicarrier wireless communication system
3GPP TR 36.814v0.4.1; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Further Advancements for E-UTRA Physical Layer Aspects; Release 9; Feb. 2009; 31 pages.
3GPP TR 36.913 v1.0.0; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Requirements for Further Advancements for E-UTRA (LTE-Advanced) Release 8; May 2008; 13 pages.
3GPP TS 36.212 v8.4.0; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and Channel Coding; Release 8; Sep. 2008; 56 pages.
3GPP TS 36.300 V8.6.0; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall Description; Stage 2; Release 8; Sep. 2008; 137 pages.
3GPP TS 36.304 v8.3.0; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) Procedures in Idle Mode; Release 8; Sep. 2008; 28 pages.
3GPP TS 36.321 V8.1.0; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) Protocol Specification; Release 8; Mar. 2008; 30 pages.
3GPP TS 36.321 v8.3.0; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Medium Access Control (MAC) Protocol Specification; Release 8; Sep. 2008; 36 pages.
3GPP TS 36.331 v8.3.0; 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) Radio Resource Control (RRC); Protocol Specification; Release 8; Sep. 2008; 178 pages.
3GPP TSG RAN WG1 #54bis; "Decode and Forward Relays for E-UTRA Enhancements"; R1-083533; Prague, Czech Republic; Sep. 29-Oct. 3, 2008; 5 pages.
3GPP TSG RAN WG1 Meeting #54; "Discussion on the Various Types of Relays"; R1-082397; Warsaw, Poland; Jun. 30-Jul. 4, 2008; 6 pages.
3GPP TSG RAN WG1 Meeting #55; "L2 Relay Interference Mitigation"; R1-084102; Prague, Czech Republic; Nov. 10-14, 2008; 6 pages.
3GPP TSG RAN WG1 Meeting #55-bis; "Relay Control Signalling Resource Coordination"; R1-090027; Ljubljana, Slovenia; Jan. 12-16, 2009; 3 pages.
Advisory Action dated Jun. 12, 2015; U.S. Appl. No. 13/865,810, filed Apr. 18, 2013; 3 pages.
Advisory Action dated Sep. 16, 2014; U.S. Appl. No. 13/221,583, filed Aug. 30, 2011; 18 pages.
Australian Examination Report; Application No. 2009325082; Jul. 11, 2011; 2 pages.
Cai, Zhijun, et al., U.S. Appl. No. 12/337,214, filed Dec. 17, 2008; Title: System and Method for Autonomous Combining.
Cai, Zhijun, et al.; U.S. Appl. No. 12/340,412, filed Dec. 19, 2008; Title: System and Method for Resource Allocation.
Cai, Zhijun, et al.; U.S. Appl. No. 13/221,583, filed Aug. 30, 2011; Title: System and Method for Autonomous Combining.
Canadian Office Action; Application No. 2,746,635; Jan. 22, 2015; 4 pages.
Canadian Office Action; Application No. 2,747,593; Mar. 26, 2015; 3 pages.
China Mobile, Vodafone, Huawei; TSG-RAN WG1 #54; Title: Application Scenarios for LTE-Advanced Relay; R1-082975; Jeju, Korea; Aug. 18-22, 2008; 7 pages.
Chinese Office Action as Received in Co-pending Application No. 200980149651.4 on May 6, 2014; 3 pages. (No English translation available).
Chinese Office Action as Recieved in Co-pending Application No. 200980156892.1 on Feb, 15, 2015; 6 pages. (No English translation avaliable).
Chinese Office Action; Application No. 200980149651.4; Jun. 5, 2015; 13 pages.
Chinese Office Action; Application No. 200980149651.4; Nov. 24, 2014; 12 pages.
Chinese Office Action; Application No. 200980156929.0; Sep. 2, 2014; 7 pages.
Doppler, Klaus, et al.; "Assessment of Relay Based Deployment Concepts and Detailed Description of Multi-hop Capable RAN Protocols as Input for the Concept Group Work"; IST-4-027756 Winner II; D3.5.2 v1.0; Jun. 30, 2007; 24 pages.
Ericsson; TSG-RAN WG1 #53; Title: A Discussion on Some Technology Components for LTE-Advanced; R1-082024; Kansas City, Missouri; May 5-9, 2008; 11 pages.
European Examination Report; Application No. 09752588.5; Aug. 28, 2015; 7 pages.
European Examination Report; Application No. 09789422.4; May 2, 2016; 7 pages.
Final Office Action dated Apr. 19, 2012; U.S. Appl. No. 13/216,819, filed Aug. 24, 2011; 39 pages.
Final Office Action dated Dec. 16, 2011; U.S. Appl. No. 12/337,207, filed Dec. 17, 2008; 37 pages.
Final Office Action dated Dec. 9, 2011; U.S. Appl. No. 12/331,992, filed Dec. 10, 2008; 24 pages.
Final Office Action dated Jan. 24, 2013; U.S. Appl. No. 13/548,817, filed Jul. 13, 2012; 33 pages.
Final Office Action dated Jan. 5, 2012; U.S. Appl. No. 12/340,418, filed Dec. 19, 2008; 22 pages.
Final Office Action dated Jan. 9, 2012; U.S. Appl. No. 12/337,235, filed Dec. 17, 2008; 26 pages.
Final Office Action dated Jun. 7, 2012; U.S. Appl. No. 12/337,222, filed Dec. 17, 2008; 16 pages.
Final Office Action dated Mar. 23, 2012; U.S. Appl. No. 12/340,432, filed Dec. 19, 2008; 28 pages.
Final Office Action dated Mar. 23, 2015; U.S. Appl. No. 13/865,810, filed Apr. 18, 2013; 43 pages.
Final Office Action dated Mar. 24, 2016; U.S. Appl. No. 14/298,629, filed Jun. 6, 2014; 18 pages.
Final Office Action dated Nov. 20, 2013; U.S. Appl. No. 12/337,222, filed Dec. 17, 2008; 28 pages.
Final Office Action dated Nov. 8, 2011; U.S. Appl. No. 12/340,412, filed Dec. 19, 2008; 19 pages.
Final Office Action dated Oct. 2, 2012; U.S. Appl. No. 12/340,418, filed Dec. 19, 2008; 29 pages.
Final Office Action dated Sep. 17, 2014; U.S. Appl. No. 13/865,810, filed Apr. 18, 2013; 42 pages.
IEEE P802.16j/D9; Part 16: Air Interface for Fixed and Mobile Broadband Wireless Access Systems-Multihop Relay Specification; Draft Amendment to IEEE Standard for Local and Metropolitan Area Networks; Feb. 4, 2009; 314 pages.
Japanese Office Action as Received in Co-pending Application No. 2011-540716 on Aug. 22, 2014; 2 pages. (No English translation available).
Japanese Office Action as Received in Co-pending Application No. 2013-066527 on Jan. 23, 2014; 2 pages. (No English translation available).
Masato, Okuda, et al.; "MAC-PDU Reconstruction at RS"; IEEE C802.16j-07/022; Jan. 8, 2007; 3 pages.
Mitsubishi Electric; 3GPP TSG RAN WG1 #54 Meeting; Title: Basic Structure of Relaying under Multi-Antenna eNB; R1-082775; Jeju Island, Korea; Aug. 18-22, 2008; 4 pages.
Motorola; Title: Classification of Relays; TSG-RAN WG1 #54; R1-083223; Jeju, South Korea; Aug. 18-22, 2008; 3 pages.
Notice of Allowance dated Aug. 10, 2012; U.S. Appl. No. 12/340,412, filed Dec. 19, 2008; 17 pages.
Notice of Allowance dated Aug. 11, 2014; U.S. Appl. No. 13/842,584, filed Mar. 15, 2013; 30 pages.
Notice of Allowance dated Jan. 17, 2013; U.S. Appl. No. 12/340,418, filed Dec. 19, 2008; 25 pages.
Notice of Allowance dated Jul. 24, 2015; U.S. Appl. No. 13/865,810, filed Apr. 18, 2013; 14 pages.
Notice of Allowance dated Jun. 24, 2014; U.S. Appl. No. 12/331,992, filed Dec. 10, 2008; 10 pages.
Notice of Allowance dated May 27, 2011; U.S. Appl. No. 12/337,214, filed Dec. 17, 2008; 10 pages.
Office Action dated Apr. 18, 2013; U.S. Appl. No. 13/216,819, filed Aug. 24, 2011; 37 pages.
Office Action dated Aug. 19, 2011; U.S. Appl. No. 12/331,992, filed Dec. 10, 2008; 52 pages.
Office Action dated Dec. 3, 2012; U.S. Appl. No. 12/337,222, filed Dec. 17, 2008; 24 pages.
Office Action dated Feb. 1, 2012; U.S. Appl. No. 12/337,222, filed Dec. 17, 2008; 20 pages.
Office Action dated Feb. 14, 2014; U.S. Appl. No. 12/331,992, filed Dec. 10, 2008; 81 pages.
Office Action dated Feb. 17, 2012; U.S. Appl. No. 12/340,412, filed Dec. 19, 2008; 19 pages.
Office Action dated Jan. 31, 2013; U.S. Appl. No. 13/221,583, filed Aug. 30, 2011; 69 pages.
Office Action dated Jul. 13, 2011; U.S. Appl. No. 12/337,207, filed Dec. 17, 2008; 34 pages.
Office Action dated Jul. 18, 2011; U.S. Appl. No. 12/340,432, filed Dec. 19, 2008; 6 pages.
Office Action dated Jul. 21, 2011; U.S. Appl. No. 12/340,418, filed Dec. 19, 2008; 34 pages.
Office Action dated Jul. 22, 2011; U.S. Appl. No. 12/337,235, filed Dec. 17, 2008; 36 pages.
Office Action dated Jun. 16, 2011; U.S. Appl. No. 12/340,412, filed Dec. 19, 2008; 33 pages.
Office Action dated Mar. 2, 2016; U.S. Appl. No. 12/916,214, filed Oct. 29, 2010; 55 pages.
Office Action dated May 10, 2013; U.S. Appl. No. 13/221,583, filed Aug. 30, 2011; 21 pages.
Office Action dated May 26, 2010, 9 pages, U.S. Appl. No. 12/337,214, filed Dec. 17, 2008.
Office Action dated May 29, 2013; U.S. Appl. No. 12/337,222, filed Dec. 17, 2008; 26 pages.
Office Action dated Nov. 10, 2011; U.S. Appl. No. 13/216,819, filed Aug. 24, 2011; 19 pages.
Office Action dated Oct. 12, 2012; U.S. Appl. No. 13/548,817, filed Jul. 13, 2012; 53 pages.
Office Action dated Oct. 16, 2014; U.S. Appl. No. 13/865,810, filed Apr. 18, 2013; 38 pages.
Office Action dated Oct. 19, 2015; U.S. Appl. No. 14/298,629, filed Jun. 6, 2014; 89 pages.
Office Action dated Sep. 16, 2011; U.S. Appl. No. 12/340,432, filed Dec. 19, 2008; 33 pages.
Panasonic; 3GPP TSG RAN WG1 Meeting #54bis; Title: Discussion on the TD Relay and FD Relay for FDD System; R1-083676; Prague, Czech Republic; Sep. 29-Oct. 3, 2008; 5 pages.
Parkvall, Stefan, et al.; "The Evolution of WCDMA Towards Higher Speed Downlink Packet Data Access"; IEEE VTC; May 6, 2001; 5 pages
PCT International Preliminary Report on Patentability; PCT Application No. PCT/US2009/062571; Mar. 10, 2011; 8 pages.
PCT International Search Report; PCT Application No. PCT/US2009/030967; Sep. 8, 2009; 5 pages.
PCT International Search Report; PCT Application No. PCT/US2009/062551; Jan. 28, 2010; 4 pages.
PCT International Search Report; PCT Application No. PCT/US2009/062554; May 12, 2010; 6 pages.
PCT International Search Report; PCT Application No. PCT/US2009/062557; Feb. 10, 2010; 4 pages.
PCT International Search Report; PCT Application No. PCT/US2009/062560; Mar. 1, 2010; 4 pages.
PCT International Search Report; PCT Application No. PCT/US2009/062570; Feb. 22, 2010; 4 pages.
PCT International Search Report; PCT Application No. PCT/US2009/062571; Apr. 19, 2010; 6 pages.
PCT International Search Report; PCT Application No. PCT/US2009/062574; Jul. 19, 2010; 6 pages.
PCT International Search Report; PCT Application No. PCT/US2009/064398; Mar. 18, 2010; 5 pages.
PCT Written Opinion of the International Searching Authority; PCT Application No. PCT/US2009/030967; Sep. 8, 2009; 9 pages.
PCT Written Opinion of the International Searching Authority; PCT Application No. PCT/US2009/062551; Jan. 28, 2010; 5 pages.
PCT Written Opinion of the International Searching Authority; PCT Application No. PCT/US2009/062554; May 12, 2010; 7 pages.
PCT Written Opinion of the International Searching Authority; PCT Application No. PCT/US2009/062557; Feb. 10, 2010; 7 pages.
PCT Written Opinion of the International Searching Authority; PCT Application No. PCT/US2009/062560; Mar. 1, 2010; 7 pages.
PCT Written Opinion of the International Searching Authority; PCT Application No. PCT/US2009/062570; Feb. 22, 2010; 8 pages.
PCT Written Opinion of the International Searching Authority; PCT Application No. PCT/US2009/062571; Apr. 19, 2010; 6 pages.
PCT Written Opinion of the International Searching Authority; PCT Application No. PCT/US2009/062574; Jul. 19, 2010; 9 pages.
PCT Written Opinion of the International Searching Authority; PCT Application No. PCT/US2009/064398; Mar. 18, 2010; 9 pages.
Qualcomm Europe; 3GPP TSG-RAN WG1 #54; Title: Operation of Relays in LTE-A; R1-083191; Jeju, S. Korea; Aug. 18-22, 2008; 5 pages.
Samsung; 3GPP TSG RAN WG1 Meeting #53bis; Title: Application of Network Coding in LTE-Advanced Relay; R1-082327; Warsaw, Poland; Jun. 30-Jul. 4, 2008; 4 pages.
Sendonaris, Andrew, et al.; "User Cooperation Diversity-Part I: System Description"; IEEE Transactions on Communications; vol. 51, No. 11; Nov. 2003; 12 pages.
Sendonaris, Andrew, et al.; "User Cooperation Diversity-Part II: Implementation Aspects and Performance Analysis"; IEEE Transactions on Communications; vol. 51, No. 11; Nov. 2003; 10 pages.
Tao, Jeffrey Z., et al.; "Aggregation in 802.16j-Enhanced Concatenation and MPDU Construction"; IEEE C802.16j-06/178r2; Nov. 7, 2006; 18 pages.
Womack, James Earl, et al.; U.S. Appl. No. 12/331,992, filed Dec. 10, 2008; Title: Method and Apparatus for Discovery of Relay Nodes.
Womack, James Earl, et al.; U.S. Appl. No. 14/878,613, filed Oct. 8, 2015; Title: System and Method for Relay Node Selection; 27 pages.
Yu, Yi, et al.; U.S. Appl. No. 12/337,207, filed Dec. 17, 2008; Title: System and Method for Multi-User Multiplexing.
Yu, Yi, et al.; U.S. Appl. No. 14/298,629, filed Jun. 6, 2014; Title: System and Method for Multi-User Multiplexing; 37 pages.
CA2747339A1 (en) 2010-07-08 application
US8856607B2 (en) 2014-10-07 grant
JP2012512599A (en) 2012-05-31 application
US20130223326A1 (en) 2013-08-29 application
EP2377260A1 (en) 2011-10-19 application
KR20120108065A (en) 2012-10-04 application
KR101223377B1 (en) 2013-01-16 grant
EP2377260B1 (en) 2017-09-27 grant
WO2010077419A1 (en) 2010-07-08 application
KR101317292B1 (en) 2013-10-14 grant
US8402334B2 (en) 2013-03-19 grant
CN102318255A (en) 2012-01-11 application
KR20110095960A (en) 2011-08-25 application
US20100153806A1 (en) 2010-06-17 application
CN102318255B (en) 2015-02-04 grant
CA2747339C (en) 2016-03-29 grant
US20140362755A1 (en) 2014-12-11 application
US20120176887A1 (en) 2012-07-12 Method and system for hybrid automatic repeat request operation for uplink coordinated multi-point signaling
US20100322194A1 (en) 2010-12-23 Mechanisms for Data Handling During a Relay Handover with S1 Termination at Evolved Universal Terrestrial Radio Access Network Access Node
US20110317637A1 (en) 2011-12-29 Method for processing and transmitting data packet
US20100322193A1 (en) 2010-12-23 Mechanisms for Data Handling During a Relay Handover with S1 Termination at Relay
US20100150173A1 (en) 2010-06-17 System and Method for Multi-User Multiplexing
US20120057451A1 (en) 2012-03-08 Method of retransmission for supporting mimo in synchronous harq
US20090307559A1 (en) 2009-12-10 Transmitter, receiver, transmission method, and reception method
US20110300854A1 (en) 2011-12-08 Method of control indication in multi-input multi-output communication systems
US20120120927A1 (en) 2012-05-17 Introducing a delay in the transmission of a nack for a packet received employing coordinated multi-point transmission
US20100195605A1 (en) 2010-08-05 Discontinuous Reception Start Offset Coordinated with Semi-Persistent Scheduling System and Method
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:YU, YI;WOMACK, JAMES EARL;CAI, ZHIJUN;SIGNING DATES FROM20090113 TO 20090122;REEL/FRAME:033709/0804
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RESEARCH IN MOTION CORPORATION;REEL/FRAME:033709/0887