Enhanced multiplexing for single RLC entity

Description

TECHNICAL FIELD

[0001] The present invention relates generally to radio link control (RLC) protocols for wireless communication networks, and more particularly to methods and apparatuses for interrupting and resuming transmissions on an RLC data block basis for different priority packet flows within a single RLC entity.

BACKGROUND

[0002] RLC is a protocol used in wireless communication networks to convey user plane or control plane information between a mobile station and a radio access network. When conveying user plane information, the RLC protocol receives a protocol data unit (PDU) from a higher layer known as the logical link control (LLC) layer, where each LLC PDU is associated with a packet flow context (PFC) and is divided into smaller data packets, referred to herein as RLC data blocks for transmission over the wireless communication channel to a receiver. The receiver reassembles the LLC PDU from the received RLC data blocks.

[0003] In some scenarios, the RLC protocol entity operating at a transceiver and a receiver may support the transmission and reception of multiple packet data sessions in parallel, whereby multiple PFCs share a common RLC entity. Each PFC has its own packet data protocol (PDP) context, and therefore has its own quality of service (QoS) attributes from which a transmission priority may be derived. When a common RLC entity supports multiple PFCs, the transmitting RLC entity may receive LLC PDUs corresponding to these PFCs asynchronously and generally decides which PFC to service on a per LLC PDU basis, which requires the RLC entity to complete a transmission of an LLC PDU in progress before beginning the transmission of the next LLC PDU. A higher priority LLC PDU may therefore incur undesirable transmission
delays while the common RLC entity completes the transmission of a lower priority LLC PDU. Such delays may cause perceivable degradation of the service supported by the higher priority LLC PDU, especially when the lower priority LLC PDU has a significant length.

[0004] Background art of interest is disclosed in EP 1 411 690 A1, specifically a method for transferring the GPRS data packets from different PDP contexts according to their relative priority, wherein Logical Link Control (LLC) Packet Data Units (PDUs) are reordered when user data is transferred over the radio interface between a Mobile Station (MS) and a packet data network.

[0005] Furthermore, EP 0 582 537 A2 discloses a protocol defined for mixed data/voice/multimedia communications systems to transmit and receive high-priority, real-time traffic over low-speed digital communication links by embedding such high-priority traffic in low-priority, non-real-time traffic. High-priority, real-time packets are thus transmitted without delay by preempting low-priority packets. Low-priority, non-real-time packets are held during preemption, and low-priority transmission is automatically resumed after transmission of high-priority packets has been completed. A protocol is defined for communications systems to exchange information, at the time that a communication link is activated, defining their link capabilities for handling high-priority, real-time packets and to agree on how this high-priority traffic will be transmitted on the communication link.

[0006] The article titled "QoS Uplink Priority Based Scheduling for EMST" from Telefon AB LM Ericsson, 3GPP draft; GP-090879 EMST_MS_UL_SCHED, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre (650 Route des Lucioles , F-06921 Sophia-Antipolis Cedex, France), Vol. TSG GERAN No. Shenzten, (8 May 2009) discloses how multiple user plane flows, associated with distinct PDP Contexts, in the uplink as well as in the downlink direction, that may use distinct simultaneous RLC entities, can be multiplexed on the uplink direction, i.e. in the mobile station, in a QoS based prioritized way over the shared radio resources.

SUMMARY

[0007] The present invention provides a method as set out in appended Claim 1, a communication terminal as set out in Claim 4, a method as set out in Claim 8, and a communication terminal as set out in Claim 11. Optional features are set out in the remaining claims.

[0008] An embodiment of the present invention more efficiently bundles data segments associated with different higher layer packets during the transition from the interrupting higher layer packet back to the interrupted higher
layer packet. More particularly, a final data segment of a first higher layer packet associated with a higher priority first PFC is encapsulated in a final higher priority data block along with a data segment of a second higher layer packet associated with a lower priority second PFC to complete a transmission of the first higher layer packet and to resume a transmission of the second higher layer packet. The final higher priority data block further includes a transition indicator to indicate a transition within the final higher priority data block from the first higher layer packet back to the second higher layer packet.

[0009] The receiver receives the final higher priority data block comprising the final data segment of the first higher layer packet, a remaining data segment of the second higher layer packet, and the transition indicator. The receiver separates the remaining data segment for the second higher layer packet from the final higher priority data block based on the transition indicator to resume a previously interrupted reception of the second higher layer packet.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] 

Figure 1 shows one exemplary mobile communication system providing a connection to an external packet data network.

Figure 2 shows one exemplary protocol stack for a mobile communication system for transmitting data packets between a mobile terminal and an external packet data network.

Figure 3 shows one exemplary simplified block diagram of the relationship between the common RLC entity and the higher layer packets at the transmitter and the receiver.

Figure 4 shows one exemplary transmission method for interrupting and resuming higher layer packet transmissions within the context of a common RLC entity.

Figure 5 shows one exemplary reception method for interrupting and resuming higher layer packet receptions within the context of a common RLC entity.

Figure 6 shows one exemplary scenario for interrupting and resuming higher layer packet transmissions using a common RLC entity.

Figure 7 shows one exemplary method for encapsulating data segments from different higher layer packets for transmission via a single data block within the context of a common RLC entity.

Figure 8 shows one exemplary method for separating data segments from different higher layer packets received in a single data block within the context of a common RLC entity.

Figure 9 shows another exemplary scenario for interrupting and resuming packet transmission using a common RLC entity.

Figure 10 shows a block diagram of a transmitter and receiver according to one exemplary embodiment of the present invention.

DETAILED DESCRIPTION OF BACKGROUND EXAMPLES AND EMBODIMENTS

[0011] There is described in the following a method and apparatus which overcomes the priority-based problems associated with the use of a common RLC entity, by interrupting the transmission/reception of lower priority higher layer packets to transmit/receive higher priority higher layer packets within the context of a common RLC entity. An RLC entity views LLC PDUs as higher layer packets. It will be appreciated that the related techniques described herein apply to both the uplink and downlink of a wireless communication network.

[0012] According to one example of such apparatus described herein, lower priority data blocks (also referred to herein as RLC data blocks) containing data segments of a first higher layer packet associated with a lower priority first PFC experience ongoing transmission to a receiver. The transmission of the first higher layer packet is interrupted to transmit higher priority data blocks containing data segments of a second higher layer packet associated with a higher priority second PFC. After the transmission of a final data segment of the second higher layer packet, the transmission of the first higher layer packet is resumed. In one example, the lower priority data blocks are sequentially numbered before the interruption, and the sequential numbering continues without sequence number restart for the interrupting higher priority data blocks and the resuming lower priority data blocks.

[0013] The receiver receives the lower priority data blocks. Upon receipt of the first higher priority data block, the receiver detects an interruption of the first higher layer packet. The interruption of the first higher layer packet continues until a final higher priority data block containing a final data segment of the second higher layer packet is received, after which the reception of the first higher layer packet resumes.

[0014] A method and apparatus for interrupting the transmission/reception of a lower priority LLC PDU on a per RLC data block basis to transmit a higher priority LLC PDU within the context of a common RLC entity will be first be described. The transmission/reception of RLC data blocks containing data segments of a lower priority LLC PDU associated with a lower priority PFC is interrupted to transmit RLC data blocks containing data segments of a higher priority LLC PDU associated with a higher priority PFC. After the transmission/reception of a final data segment of the higher priority LLC PDU within an RLC data block, the transmission/reception of the lower priority LLC PDU resumes, either within the same RLC data block or within a subsequent RLC data block. The interrupting and resuming transitions described herein reduces undesirable transmission delays by using an RLC data block-based transmission granularity to ensure that the relative priorities of the PFCs are honored to the greatest extent possible when multiple PFCs share a common RLC entity. It will be appreciated that the RLC processes described herein may be used by a mobile station on the uplink and/or by a base station on the downlink.

[0015] To facilitate the description of the present invention, the following first describes an exemplary mobile communication system based on the Enhanced General Packet Radio Service (EGPRS) standard by the Third Generation Partnership Project (3GPP), and subsequently describes the present invention in the context of an EGPRS mobile communication system. It will be appreciated, however, that the present
invention applies to other communication protocols that use a common RLC entity to transmit multiple distinct packet data sessions in parallel. Further, it will be appreciated the present invention applies to both downlink and uplink communications.

[0016] Figure 1 shows an exemplary EGPRS network 10 comprising a GSM/EGPRS radio access network (GERAN) 12 and a core network 16. GERAN 12 typically comprises one or more base station subsystems (BSSs) 14. While not explicitly shown, each BSS 14 comprises a base station controller (BSC) and one or more base transceiver stations (BTSs), which may be co-located or in separate locations. The BTSs comprise the antennas, RF equipment, and baseband processing circuits needed to communicate with mobile terminals 100. The BSC manages the radio resources used for communication with the mobile terminal 100 and provides a connection to the core network 16.

[0017] Core network 16 includes one or more serving GPRS support nodes (SGSNs) 18 and one or more gateway GPRS support node (GGSN) 20. The SGSN 18 provides support for packet switched communications, handles session management and mobility management functions for the packet switched services, and provides a connection to a GGSN 20. The GGSN 20 serves as a gateway between the core network 16 network and external packet data networks 30, e.g., the Internet. For packet data communication, the mobile terminal 100 establishes a communication session with an SGSN 18, and the GGSN 20 connects the SGSN 18 with the external packet data networks 30. A more detailed description of the core network 16 is readily available in the relevant EGPRS standards.

[0018] Figure 2 provides a simplified illustration of an EGPRS protocol stack 50 used for transmission of packet data between the mobile terminal 100 and SGSN 18. Protocol stack 50 includes a plurality of protocol layers. The various layers of the protocol stack 50 represent a set of programs and protocols that may be implemented by software running on a host computing device including a processor and memory. Each layer encapsulates data received from a higher layer protocol to generate protocol data units (PDUs) that are passed down to the next lower layer. The term PDU as used herein is synonymous with the term packet.

[0019] The SGSN 18 receives IP packets from the GGSN 20. IP packets or other data packets may, for example, be transmitted to the SGSN 18 using the GPRS tunneling protocol (GTP). The protocol stack 50 implemented by the SGSN 18 and mobile terminal 100 includes a Sub Network Dependent Convergence Protocol (SNDCP) layer, Logical Link Control (LLC) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and a Physical layer (PL). The SNDCP layer converts the IP packets into a format compatible with the underlying GPRS network architecture. SNDCP PDUs are passed to the LLC layer, which provides a logical connection between the SGSN 18 and mobile terminals 100. The LLC layer encapsulates the SNDCP PDUs with an LLC header to generate LLC PDUs. The Base Station System GPRS Protocol (BSSGP) layer (not shown) routes the LLC PDU to the serving BSS 14 (e.g., over a frame relay PL). The BSSGP operates between the SGSN 18 and the BSS 14, e.g., the BSSGP does not extend over the air interface.

[0020] At the BSS 14, an LLC relay provides the LLC PDU to the RLC layer. An RLC entity establishes a reliable link (e.g., if required by the QoS of the corresponding packet switched service) between the BSS 14 and mobile terminal 100. The RLC entity also performs segmentation and reassembly of upper-layer PDUs (LLC PDUs in this example) into RLC packets, which are referred to herein as RLC data blocks. Each RLC data block includes a header and a data field. The header includes a temporary flow identity (TFI) that uniquely maps to a PFC, and the data field includes data segments from the LLC PDU associated with the PFC uniquely identified by the TFI in the corresponding header. The RLC data blocks are passed to the MAC layer which encapsulates the RLC data blocks with MAC headers. The MAC layer controls access signaling across the air interface, including the assignment of uplink and downlink radio blocks which are used to carry the RLC data blocks. The data is then transmitted to a mobile terminal 100 over the air interface via the PL. The PL is responsible for converting data received from the MAC layer into a bit stream suitable for transmission to the mobile terminal 100 over the radio interface.

[0021] The RLC layer of the BSS 14 and/or mobile terminal 100 may support the transmission and reception of multiple packet data sessions in parallel, whereby each packet session has a corresponding PFC and multiple PFCs share a common RLC entity. Each LLC PDU is uniquely associated with a distinct PFC, where each PFC has a particular transmission priority and QoS. For example, an LLC PDU associated with a lower priority PFC, e.g., LLC PDU_L, may share a common RLC entity with an LLC PDU associated with a higher priority PFC, e.g., LLC PDUH, as shown in Figure 3. Conventional systems operate using an LLC PDU-based transmission granularity, and therefore require the RLC entity to complete the transmission/reception of the RLC data blocks associated with a specific LLC PDU before beginning the transmission/reception of the RLC data blocks associated with a different LLC PDU. As a result, the transmission and reception of data for a higher priority LLC PDU may be undesirably delayed while the RLC entity completes the transmission/reception of data blocks for a lower priority LLC PDU.

[0022] This problem can be addressed by providing a method and apparatus for interrupting RLC data block transmissions for a lower priority PFC in favor of RLC data block transmission for a higher priority PFC within the context of a single RLC entity. Figure 4 shows one exemplary method 200 for interrupting and resuming lower priority transmissions. In general, the RLC entity transmits RLC data blocks containing data segments of an LLC PDU associated with the lower priority PFC (LLC PDU_L) (block 210), where the lower priority RLC data blocks are sequentially numbered. The RLC entity interrupts the transmission of LLC PDU_L by transmitting one or more RLC data blocks containing data segments of an LLC PDU associated with the higher priority PFC (LLC PDU_H) (block 220). The higher priority RLC data blocks are also sequentially numbered, where the sequential numbering is continued from the lower priority RLC data blocks without a sequence number restart. After transmitting a final data segment of LLC PDU_H within an RLC data block, the RLC entity resumes the transmission of data segments associated with LLC PDU_L, either within the same RLC data block or within a subsequent RLC data block (block 230). The resuming lower priority RLC data blocks are also sequentially numbered, where the sequential numbering is continued from the higher priority RLC data blocks without a sequence number restart.

[0023] Figure 5 shows one exemplary interrupting and resuming method 250 from the perspective of the receiver. In general, the RLC entity receives RLC data blocks containing data segments for the LLC PDU_L (block 260), where the lower priority RLC data blocks are sequentially numbered. The RLC entity detects an interruption of the LLC PDU_L upon receiving an RLC data block containing a data segment for the LLC PDU_H (block 270). The higher priority RLC data blocks are also sequentially
numbered, where the sequential numbering is continued from the lower priority RLC data blocks without a sequence number restart. After receiving a final data segment of the LLC PDU_H within an RLC data block (block 280), the RLC entity resumes the reception of the data segments of the LLC PDU_L (block 290), which may be contained within the same RLC data block or within a subsequent RLC data block. The resuming lower priority RLC data blocks are also sequentially numbered, where the sequential numbering is continued from the higher priority RLC data blocks without a sequence number restart.

[0024] To successfully implement the interrupting and resuming transitions, the RLC entity signals the interrupting and/or resuming transitions. The RLC entity may signal the interrupting transition by changing the temporary flow identity (TFI) of the interrupting RLC data block. For example, the RLC entity may change the TFI in the header of the interrupting RLC data blocks from TFI_L, which is uniquely associated with the lower priority PFC, to TFI_H, which is uniquely associated with the higher priority PFC. Similarly, the RLC entity may signal the resuming transition by including TFI_L in the header of the resuming RLC data blocks. For example, the header of the of the initial and resuming lower priority RLC data blocks may each include TFI_L, while the header of the interrupting higher priority RLC data blocks may each include TFI_H. It will be appreciated that the data fields of the RLC data blocks contain data segments associated with the PFC identified by the header TFI.

[0025] In another background example, the RLC entity signals the interrupting transition by including TFI_H in the header of the higher priority RLC data blocks, and includes TFI_H along with a transition indicator in the data field of the first interrupting higher priority RLC data block. By including the transition indicator and TFI_H in the data field of the first interrupting higher priority RLC data block, the receiving RLC entity is able to detect the precise point of interruption within the sequence of received RLC data blocks, even if the receiver did not successfully receive the RLC data block immediately previous to the first interrupting higher priority RLC data block. The RLC entity signals the resuming transition by including TFI_L and a transition indicator in the data field of the first resuming RLC data block, and including TFI_L in the header of all resuming lower priority RLC data blocks. By including the transition indicator and TFI in the data field of the first resuming RLC data block, the RLC entity enables the
receiver to detect the transition, even if the receiver did not successfully receive the RLC data block immediately previous to the first resuming higher priority RLC data block. The interrupting transition indicator may be the same as or different from the resuming transition indicator. For example, a length indicator (LI) set to 124 or 125 may be used to indicate an interrupting and/or resuming transitions.

[0026] Figure 6 shows one example of multiplexed RLC data blocks 60 associated with different priority PFCs 70, 80 within the context of a single RLC entity. The RLC data blocks 60 of Figure 6 may represent transmission or reception data blocks.

[0027] Each RLC data block 60 includes a header and a data field, where each data field may carry up to X octets of data, and where a data segment from an LLC PDU uses one or more consecutive data field octets. In this example, the LLC PDU associated with the lower priority PFC 70 (LLC PDU_L) requires 3.5 RLC data blocks 60, while the LLC PDU associated with the higher priority PFC 80 (LLC PDU_H) requires 2.25 RLC data blocks 60, resulting in the RLC entity using seven RLC data blocks 60 sequentially numbered with block sequence numbers (BSNs) 1 to 7 for LLC PDU_L and LLC PDU_H. The transitions from the lower priority PFC 70 to the higher priority PFC 80 and back to the lower priority PFC 70 do not initiate a BSN sequence number restart. In other words, a single contiguous sequence of BSN values is present in the RLC data blocks 60, even when successive RLC data blocks 60 contain data segments from different PFCs.

[0028] The header of each RLC data block 60 includes a TFI that uniquely associates the data segments in the corresponding data field with a specific PFC. For example, TFIL in the header of BSN 1, BSN 2, BSN 6, and BSN 7 associates the data segments in the corresponding data fields with the lower priority PFC 70. To signal the interrupting transition of the lower priority PFC 70 by the higher priority PFC 80, the RLC entity changes the TFI in the header of the interrupting RLC data blocks 60 to TFI_H, and puts data segments for LLC PDU_H in the corresponding data fields. The data field of the first interrupting RLC data block 60, e.g., BSN 3, may also signal the interrupting transition by optionally including TFI_H and a transition length indicator
(LI) set to a predetermined transition value, e.g., 124 in the first two octets of the data field. As shown in Figure 6, when the data field includes a transition indicator, the data field has fewer octets available for payload data segments, e.g., two fewer octets in BSN 3 and three fewer octets in BSN 5.

[0029] To signal the resuming transition of the lower priority PFC 70, the RLC entity changes the TFI in the header of the resuming RLC data blocks 60 back to TFI_L, and puts the remaining data segments of the lower priority LLC PDU in the corresponding data fields. The data field of the first resuming RLC data block 60, e.g., BSN 6, may further signal the resuming transition by including TFI_L and a transition LI set to a predetermined transition value, e.g., 124, in the first two octets of the data field.

[0030] As shown in Figure 6, the data fields of some RLC data blocks 60, e.g., BSN 5 and BSN 7, may not be completely full with data. For example, the higher priority LLC PDU does not need all of the octets available in BSN 5 to complete the higher priority transmission/reception. In this case, an octet of the data field may identify the number of octets containing data for the last data segment of the higher priority LLC PDU by including an LI set to a value equal to the number of octets needed to complete the transmission/reception of LLC PDU_H, e.g., LI = 0.25X + 2. An octet of the data field may also optionally be used to include an LI set to a filler value, e.g., 127, to signal that the portion of the data field not filled with octets corresponding to the last data segment of the higher priority LLC PDU contains filler octets (e.g., dummy data).

[0031] The above discloses how the RLC entity may interrupt the lower priority PFCs in favor of higher priority PFCs, and therefore, to prevent any undesirable transmission/reception delays. When transitioning from the lower priority PFC to the higher priority PFC, the last RLC data block sent for the lower priority LLC PDU before the interruption will typically not contain the final data segment of the lower priority LLC PDU, and therefore the data field will be full. Thus, there is typically no inefficiency experienced during the transition from the lower priority PFC to the higher priority PFC. However, when transitioning from the higher priority PFC back to the lower priority PFC, the final higher priority RLC data block may not need all of the available payload space within the data field to complete the transmission/reception of the higher priority LLC PDU, as shown in Figure 6, which leads to inefficiencies at the RLC layer due to the unused payload space. The following describes how to improve RLC data block packing efficiency for both the uplink and downlink during transitions from higher priority PFCs back to lower priority PFCs within the context of a single RLC entity. More particularly, the following describes how data segments from LLC PDUs corresponding to different PFCs may be encapsulated into a single RLC data block during the transition from the higher priority PFC back to the lower priority PFC to avoid wasting available payload space.

[0032] Figures 7 and 8 show an encapsulation method 300, 350 for the transmitter and receiver, respectively. At the transmitter, one or more data segments, including the final data segment of a higher priority LLC PDU, is encapsulated along with one or more remaining data segments of the lower priority LLC PDU associated with a previously interrupted lower priority PFC in the data field of a final higher priority RLC data block (block 310). The final higher priority RLC data block further includes a transition indicator to indicate the transition within the final higher priority RLC data block from the higher priority PFC back to the lower priority PFC (block 320). Upon receipt of the RLC data block containing data segments for both a higher priority PFC and a lower priority PFC (block 360), the RLC entity in the receiver separates the lower priority data segments from the data block based on the number of octets used for the last data segments of the higher priority PFC and a transition indicator included with the data block (block 370). In both the transmission and the reception embodiments, the transition indicator may comprise a transition LI set to a predetermined transition value (e.g., 124 or 125) in the data field of the final higher priority RLC data block. The transition indicator may further comprise a data field TFI that differs from the header TFI, where the header TFI signals the association of a first set of data segments in the data field to the higher priority PFC, and the data field TFI signals the association of a second set of data segments in the data field to the different lower priority PFC.

[0033] Figure 9 shows one example of multiplexed transmission or reception RLC data blocks associated with different priority PFCs within the context of a single RLC entity, where at least one of the RLC data blocks uses the encapsulation method described above to more efficiently transmit and receive data segments associated with different PFCs during the transition from the higher priority PFC 80 back to the lower priority PFC 70. As with Figure 6, the lower priority PFC 70 requires 3.5 RLC data blocks, while the higher priority PFC 80 requires 2.25 RLC data blocks. Because of the disclosed encapsulation method, however, the RLC entity for this embodiment only uses six RLC data blocks 60 sequentially numbered with block sequence numbers (BSNs) 1 to 6 for the same lower and higher priority LLC PDUs of Figure 6. In the example of Figure 9, RLC data blocks BSN 1 to BSN 4 are identical to that of Figure 5. Thus, the interruption details provided above are not repeated here.

[0034] To more efficiently make the transition from the higher priority PFC back to the lower priority PFC, the RLC entity generates a final higher priority RLC data block 60, e.g., BSN 5, that encapsulates both the final higher priority data segment and a remaining lower priority data segment in a single RLC data block 60. The header of BSN 5 includes TFI_H to signal that at least a portion of BSN 5 includes payload corresponding to the higher priority PFC. The data field of BSN 5 includes an LI set to a value equal to the number of octets needed to complete the transmission of the final data segment of LLC PDU_H, e.g., LI = 0.25X + 2, a transition LI set to a predetermined transition value, e.g., LI = 124, and TFI_L. The remainder of the data field includes the last 0.25X + 2 octets of LLC PDU_H, followed by the next 0.75X - 5 octets of LLC PDU_L. BSN 6 completes the transmission of LLC PDU_L.

[0035] As shown in Figure 9, the data field of some of the RLC data blocks 60, e.g., BSN 6, may not be completely full. For example, the LLC PDU_L does not need all of the octets available in BSN 6 to complete the lower priority transmission/reception. In this case, the data field of BSN 6 may optionally include an additional LI set to a filler value, e.g., LI = 127 to signal that the portion of the data field not filled with data corresponding to the last data segment of the lower priority LLC PDU contains filler octets (e.g., dummy data). It will further be appreciated that if BSN 5 includes more octets than needed to complete the transmission of the LLC PDU_H and LLC PDU_L, BSN 5 may also include additional LI values, e.g., an LI set to a value equal to the number of octets needed to complete the transmission of the LLC PDU_L, and an LI set to a filler value, e.g., LI = 127.

[0036] Figure 10 illustrates an exemplary communication terminal 400 for implementing the interrupting and resuming transitions within the context of a single RLC entity as described herein. Communication terminal 400 may represent a receiver or a transmitter, and may comprise a mobile terminal 100 or base station 14. The communication terminal 400 includes a transceiver 402 coupled to an antenna 404 for transmitting and receiving signals. Baseband processor 406 processes signals transmitted to, and received by, the communication terminal 400. Exemplary processing performed by baseband processor 406 includes modulation/demodulation, interleaving/de-interleaving, coding/decoding, etc. The baseband processor 406 includes an RLC processor 408 for implementing RLC protocols as described herein. As described above, RLC processor 408 performs the interrupting and resuming transitions of the lower and higher priority data within the context of a single RLC entity. When the RLC entity resumes lower priority transmissions, the RLC processor 408 may be configured to encapsulate the final higher priority data segment(s) along with one or more remaining lower priority data segments in a single RLC data block.

[0037] A single interruption of a lower priority PFC in favor of a higher priority PFC within the context of a common RLC entity has been described in the foregoing. It will be appreciated, however, that any number of interrupting transitions may occur. For example, the transmission/reception of a first lower priority PFC may be interrupted multiple times to enable the transmission/reception of LLC PDUs associated with multiple higher priority PFCs. Further, the interrupting transitions may be stacked such that two or more interrupting transitions occur before the transmission/reception of a lower priority LLC PDU is resumed. For example, the transmission/reception of a lower priority LLC PDU (PDU-A) may be interrupted to transmit/receive a higher priority LLC PDU (PDU-B). The transmission/reception of PDU-B may in turn be interrupted to transmit/receive an even higher priority LLC PDU (PDU-C). It will also be appreciated that a final higher priority RLC data block may include data segments from LLC PDUs associated with more than two PFCs. For example, a final higher priority RLC data block may include the final data segment(s) of PDU-C, the final data segment(s) of PDU-B, and one or more remaining data segments of PDU-A.

[0038] The present invention may, of course, be carried out in other ways than those specifically set forth herein without departing from essential characteristics of the invention. The present embodiments are to be considered in all respects as illustrative and not restrictive, and all changes coming within the meaning of the appended claims are intended to be embraced therein.

Claims

1. A method of generating, by a single radio link control entity, hereafter referred to as an RLC entity, lower layer blocks (60) using data segments from higher layer packets (70, 80) for transmission of the higher layer packets from a transmitter to a receiver, the method comprising:

encapsulating (310) a final data segment of a first higher layer packet (80) associated with a higher priority first packet flow context, hereafter abbreviated to PFC, together with a remaining data segment of a second higher layer packet (70) associated with a lower priority second PFC in a final higher priority data block wherein, when the final higher priority data block is transmitted from the transmitter to the receiver, transmission of the first higher layer packet (80) is completed and transmission of the second higher layer packet (70) is resumed; and

including (320) a transition indicator with the final higher priority data block to indicate a transition within the final higher priority data block from the first higher layer packet (80) to the second higher layer packet (70), wherein including the transition indicator comprises including:

a predetermined length indicator (LI) value indicating a number of octets in a data field of the final higher priority data block that are needed to complete the transmission of the final data segment of the first higher layer packet (80); and

a temporary flow identity, hereafter abbreviated to TFI, in the data field of the final higher priority data block, said TFI uniquely associated with the second PFC to which the second higher layer packet (70) belongs.

2. The method of claim 1, further comprising including a filler indicator with the final higher priority data block to indicate that an unused portion of the final higher priority data block contains filler data.

3. The method of claim 1, wherein the higher layer packets comprise protocol data units, hereafter referred to as PDUs, of a logical link control protocol, hereafter referred to as LLC protocol, that are associated with an LLC layer and formatted according to an LLC protocol, and wherein the final higher priority data block comprises an RLC data block associated with an RLC layer and formatted according to an RLC protocol.

4. A communication terminal (400) for generation of lower layer blocks for transmission to a receiver, the communication terminal (400) comprising:

a transceiver (402) configured to transmit data blocks to the receiver over a wireless communication channel; and

a processor (408) configured to generate, by a single radio link control entity, hereafter referred to as RLC entity, lower layer blocks using data segments from higher layer packets for transmission by the transceiver (402), wherein the processor (408) is configured to:

encapsulate a final data segment of a first higher layer packet (80) associated with a higher priority first packet flow context, hereafter abbreviated to PFC, together with a remaining data segment of a second higher layer packet (70) associated with a lower priority second PFC in a final higher priority data block wherein, when the final higher priority data block is transmitted from the transmitter to the receiver, transmission of the first higher layer packet (80) is completed and transmission of the second higher layer packet (70) is resumed; and

include a transition indicator with the final higher priority data block to indicate a transition within the final higher priority data block from the first higher layer packet (80) to the second higher layer packet (70), wherein the transition indicator comprises:

a predetermined length indicator (LI) value indicating a number of octets in a data field of the final higher priority data block that are needed to complete the transmission of the final data segment of the first higher layer packet (80); and

a temporary flow identity, hereafter abbreviated to TFI, in a data field of the final higher priority data block, said TFI uniquely associated with the second PFC to which the second higher layer packet (70) belongs.

5. The communication terminal (400) of claim 4, wherein the processor (408) is further configured to include a filler indicator with the final higher priority data block to indicate that an unused portion of the final higher priority data block contains filler data.

6. The communication terminal (400) of claim 4, wherein the higher layer packets comprise protocol data units, hereafter referred to as PDUs, of a logical link control protocol, hereafter referred to as LLC protocol, that are associated with an LLC layer and formatted according to an LLC protocol, and wherein the final higher priority data block comprises an RLC data block associated with an RLC layer and formatted according to an RLC protocol.

7. The communication terminal (400) of claim 4, wherein the communication terminal comprises a mobile device and the receiver comprises a base station.

8. A method of processing data generated by a single radio link control entity, hereafter referred to as RLC entity, and received from a transmitter, the method comprising:

receiving an encapsulated data block comprising:

a final data segment for a first higher layer packet (80) associated with a first packet flow context, hereafter abbreviated to PFC;

a remaining data segment for a second higher layer packet (70) associated with a second PFC; and

a transition indicator indicating a transition within the data block from the first higher layer packet (80) back to the second higher layer packet (70); and

separating the remaining data segment for the second higher layer packet (70) from the data block based on the transition indicator and resuming a previously interrupted reception of the second higher layer packet (70), wherein the transition indicator comprises:

a predetermined length indicator (LI) value indicating a number of octets in a data field of the final higher priority data block that are needed to complete the transmission of the final data segment of the first higher layer packet (80); and

a temporary flow identity, hereafter abbreviated to TFI, in a data field of the data block, said TFI uniquely associated with the second PFC to which the second higher layer packet (70) belongs.

9. The method of claim 8, wherein the received data block further comprises a filler indicator to indicate that an unused portion of the received data block contains filler data.

10. The method of claim 8, wherein the higher layer packets comprise protocol data units, hereafter referred to as PDUs, of a logical link control protocol, hereafter referred to as LLC protocol, that is associated with an LLC layer and formatted according to an LLC protocol, and wherein the data blocks comprise RLC data blocks associated with an RLC layer and formatted according to an RLC protocol.

11. A communication terminal (400) for processing data generated by a single radio link control entity, hereafter referred to as RLC entity, and received from a transmitter, the communication terminal (400) comprising:

a transceiver (402) configured to receive an encapsulated data block comprising:

a final data segment for a first higher layer packet (80) associated with a first packet flow context, hereafter abbreviated to PFC;

a remaining data segment for a second higher layer packet (70) associated with a second PFC; and

a transition indicator to indicate a transition within the data block from the first higher layer packet (80) back to the second higher layer packet (70); and

a processor (408) configured to separate the remaining data segment for the second higher layer packet (70) from the data block based on the transition indicator and to resume a previously interrupted reception of the second higher layer packet (70), wherein the transition indicator comprises:

a predetermined length indicator (LI) value indicating a number of octets in a data field of the final higher priority data block that are needed to complete the transmission of the final data segment of the first higher layer packet (80); and

a temporary flow identity, hereafter abbreviated to TFI, in a data field of the data block, said TFI uniquely associated with the second PFC to which the second higher layer packet (70) belongs.

12. The communication terminal (400) of claim 11, wherein the received data block further comprises a filler indicator to indicate that an unused portion of the received data block contains filler data.

13. The communication terminal (400) of claim 11, wherein the higher layer packets comprise protocol data units, hereafter referred to as PDUs, of a logical link control protocol, hereafter referred to as LLC protocol, that is associated with an LLC layer and formatted according to an LLC protocol, and wherein the data blocks comprise RLC data blocks associated with an RLC layer and formatted according to an RLC protocol.

14. The communication terminal (400) of claim 11, wherein the communication terminal comprises a base station and the transmitter comprises a mobile device.

Ansprüche

1. Ein Verfahren zum Erzeugen von Unterschicht-Blöcken (60) durch eine einzelne Funkverbindungssteuerungseinheit, nachfolgend als RLC-Einheit bezeichnet, unter Verwendung von Datensegmenten aus Oberschicht-Paketen (70, 80) zur Übertragung der Oberschicht-Pakete von einem Sender zu einem Empfänger, wobei das Verfahren umfasst:

Verkapseln (310) eines Enddatensegments eines ersten Oberschicht-Pakets (80), das einem ersten Paketflusskontext, nachfolgend abgekürzt als PFC, von höherer Priorität zugeordnet ist, zusammen mit einem verbleibenden Datensegment eines zweiten Oberschicht-Pakets (70), das einem zweiten PFC von niedrigerer Priorität zugeordnet ist, in einem Enddatenblock von höherer Priorität, wobei, wenn der Enddatenblock von höherer Priorität vom Sender zum Empfänger übertragen wird, die Übertragung des ersten Oberschichts-Pakets (80) abgeschlossen ist und die Übertragung des zweiten Oberschicht-Pakets (70) wieder aufgenommen wird; und

beinhaltend (320) einen Übergangsindikator mit dem Enddatenblock von höherer Priorität, um einen Übergang innerhalb des Enddatenblocks von höherer Priorität von dem ersten Oberschicht-Paket (80) zu dem zweiten Oberschicht-Paket (70) anzuzeigen, wobei das Beinhalten des Übergangsindikators das Beinhalten von folgendem umfasst:

einen vorbestimmten Längenindikator-(LI)-Wert, der eine Anzahl von Oktetts in einem Datenfeld des Enddatenblocks von höherer Priorität angibt, die benötigt werden, um die Übertragung des Enddatensegments des ersten Oberschicht-Pakets (80) Schicht abzuschließen; und

eine temporäre Flussidentität, nachfolgend als TFI abgekürzt, im Datenfeld des Enddatenblocks von höherer Priorität, wobei die TFI eindeutig der zweiten PFC zugeordnet ist, zu der das zweite Oberschicht-Paket (70) gehört.

2. Verfahren nach Anspruch 1, ferner umfassend das Beinhalten eines Füllindikators mit dem Enddatenblock von höherer Priorität, um anzuzeigen, dass ein nicht verwendeter Abschnitt des Enddatenblocks von höherer Priorität Fülldaten enthält.

3. Das Verfahren nach Anspruch 1, wobei die Oberschicht-Pakete Protokolldateneinheiten, nachfolgend als PDUs bezeichnet, eines logischen Verbindungssteuerungsprotokolls, nachfolgend als LLC-Protokoll bezeichnet, umfassen, die einer LLC-Schicht zugeordnet und gemäß einem LLC-Protokoll formatiert sind, und wobei der Enddatenblock von höherer Priorität einen RLC-Datenblock umfasst, der einer RLC-Schicht zugeordnet und gemäß einem RLC-Protokoll formatiert ist.

4. Ein Kommunikationsendgerät (400) zum Erzeugen von Unterschicht-Blöcken zur Übertragung an einen Empfänger, wobei das Kommunikationsendgerät (400) umfasst:

einen Sender-Empfänger (402), der konfiguriert ist, Datenblöcke über einen drahtlosen Kommunikationskanal an den Empfänger zu übertragen; und

einen Prozessor (408), der konfiguriert ist, durch eine einzelne Funkverbindungssteuerungseinheit, im Folgenden als RLC-Einheit bezeichnet, Unterschicht-Blöcke zu erzeugen, die Datensegmente aus Oberschicht-Paketen zur Übertragung durch den Sender-Empfänger (402) verwenden, wobei der Prozessor (408) konfiguriert ist:

Verkapseln eines Enddatensegments eines ersten Oberschicht-Pakets (80), das einem ersten Paketflusskontext, nachfolgend als PFC abgekürzt, von höherer Priorität zugeordnet ist, zusammen mit einem verbleibenden Datensegment eines zweiten Oberschicht-Pakets (70), das einem zweiten PFC mit niedrigerer Priorität zugeordnet ist, in einem Enddatenblock mit höherer Priorität, wobei, wenn der Enddatenblock von höherer Priorität vom Sender zum Empfänger übertragen wird, die Übertragung des ersten Oberschicht-Pakets (80) abgeschlossen ist und die Übertragung des zweiten Oberschicht-Pakets (70) wieder aufgenommen wird; und

einen Übergangsindikator mit dem Enddatenblock von höherer Priorität zu beinhalten, um einen Übergang innerhalb des Enddatenblocks von höherer Priorität von dem ersten Oberschicht-Paket (80) zu dem zweiten Oberschicht-Paket (70) anzuzeigen, wobei der Übergangsindikator umfasst:

einen vorbestimmten Längenindikator-(LI)-Wert, der eine Anzahl von Oktetts in einem Datenfeld des Enddatenblocks mit höherer Priorität angibt, die benötigt werden, um die Übertragung des Enddatensegments des ersten Oberschicht-Pakets (80) abzuschließen; und

eine temporäre Flussidentität, nachfolgend als TFI abgekürzt, in einem Datenfeld des Enddatenblocks von höherer Priorität, wobei die TFI eindeutig der zweiten PFC zugeordnet ist, zu der das zweite Oberschicht-Paket (70) gehört.

5. Das Kommunikationsendgerät (400) nach Anspruch 4, wobei der Prozessor (408) ferner konfiguriert ist, einen Füllindikator mit dem Enddatenblock von höherer Priorität zu beinhalten, um anzuzeigen, dass ein nicht verwendeter Abschnitt des Enddatenblocks von höherer Priorität Fülldaten enthält.

6. Das Kommunikationsendgerät (400) nach Anspruch 4, wobei die Oberschicht-Pakete Protokolldateneinheiten, nachfolgend als PDUs bezeichnet, eines logischen Verbindungssteuerungsprotokolls, nachfolgend als LLC-Protokoll bezeichnet, umfassen, die einer LLC-Schicht zugeordnet und gemäß einem LLC-Protokoll formatiert sind, und wobei der Enddatenblock von höherer Priorität einen RLC-Datenblock umfasst, der einer RLC-Schicht zugeordnet und gemäß einem RLC-Protokoll formatiert ist.

7. Das Kommunikationsendgerät (400) nach Anspruch 4, wobei das Kommunikationsendgerät eine mobile Vorrichtung umfasst und der Empfänger eine Basisstation umfasst.

8. Ein Verfahren zum Verarbeiten von Daten, die von einer einzelnen Funkverbindungssteuerungseinheit, nachstehend als RLC-Einheit bezeichnet, erzeugt und von einem Sender empfangen werden, wobei das Verfahren umfasst:
Empfangen eines verkapselten Datenblocks, umfassend:

ein Enddatensegment für ein erstes Oberschicht-Paket (80), das einem ersten Paketflusskontext, nachfolgend abgekürzt als PFC, zugeordnet ist;

ein verbleibendes Datensegment für ein zweites Oberschicht-Paket (70), das einem zweiten PFC zugeordnet ist; und

einen Übergangsindikator, der einen Übergang innerhalb des Datenblocks von dem ersten Oberschicht-Paket (80) zurück zu dem zweiten Oberschicht-Paket (70) anzeigt; und

Trennen des verbleibenden Datensegments für das zweite Oberschicht-Paket (70) vom Datenblock basierend auf dem Übergangsindikator und Wiederaufnehmen eines zuvor unterbrochenen Empfangs des zweiten Oberschicht-Pakets (70), wobei der Übergangsindikator umfasst:

einen vorbestimmten Längenindikator-(LI)-Wert, der eine Anzahl von Oktetts in einem Datenfeld des Enddatenblocks von höherer Priorität angibt, die benötigt werden, um die Übertragung des Enddatensegments des ersten Oberschicht-Pakets (80) abzuschließen; und

eine temporäre Flussidentität, im Folgenden als TFI abgekürzt, in einem Datenfeld des Datenblocks, wobei die TFI eindeutig der zweiten PFC zugeordnet ist, zu der das zweite Oberschicht-Paket (70) gehört.

9. Das Verfahren nach Anspruch 8, wobei der empfangene Datenblock ferner einen Füllindikator umfasst, um anzuzeigen, dass ein unbenutzter Abschnitt des empfangenen Datenblocks Fülldaten enthält.

10. Das Verfahren nach Anspruch 8, wobei die Oberschicht-Pakete Protokolldateneinheiten, nachfolgend als PDUs bezeichnet, eines logischen Verbindungssteuerungsprotokolls, nachfolgend als LLC-Protokoll bezeichnet, das einer LLC-Schicht zugeordnet und gemäß einem LLC-Protokoll formatiert ist, umfassen, und wobei die Datenblöcke RLC-Datenblöcke umfassen, die einer RLC-Schicht zugeordnet und gemäß einem RLC-Protokoll formatiert sind.

11. Ein Kommunikationsendgerät (400) zum Verarbeiten von Daten, die von einer einzelnen Funkverbindungssteuerungseinheit, nachstehend als RLC-Einheit bezeichnet, erzeugt und von einem Sender empfangen werden, wobei das Kommunikationsendgerät (400) umfasst:
einen Sender-Empfänger (402), der konfiguriert ist, einen verkapselten Datenblock zu empfangen, der umfasst:

ein Enddatensegment für ein erstes Oberschicht-Paket (80), das einem ersten Paketflusskontext, nachfolgend abgekürzt als PFC, zugeordnet ist;

ein verbleibendes Datensegment für ein zweites Oberschicht-Paket (70), das einem zweiten PFC zugeordnet ist; und

einen Übergangsindikator, um einen Übergang innerhalb des Datenblocks von dem ersten Oberschicht-Paket (80) zurück zu dem zweiten Oberschicht-Paket (70) anzuzeigen; und

einen Prozessor (408), der konfiguriert ist, das verbleibende Datensegment für das zweite Oberschicht-Paket (70) vom Datenblock basierend auf dem Übergangsindikator zu trennen und einen zuvor unterbrochenen Empfang des zweiten Oberschicht-Pakets (70) wieder aufzunehmen,

wobei der Übergangsindikator umfasst:

einen vorbestimmten Längenindikator-(LI)-Wert, der eine Anzahl von Oktetts in einem Datenfeld des Enddatenblocks von höherer Priorität angibt, die benötigt werden, um die Übertragung des Enddatensegments des ersten Oberschicht-Pakets (80) abzuschließen; und

eine temporäre Flussidentität, im Folgenden als TFI abgekürzt, in einem Datenfeld des Datenblocks, wobei die TFI eindeutig mit der zweiten PFC verbunden ist, zu der das zweite Oberschicht-Paket (70) gehört.

12. Das Kommunikationsendgerät (400) nach Anspruch 11, wobei der empfangene Datenblock ferner einen Füllindikator umfasst, um anzuzeigen, dass ein nicht verwendeter Abschnitt des empfangenen Datenblocks Fülldaten enthält.

13. Das Kommunikationsendgerät (400) nach Anspruch 11, wobei die Oberschicht-Pakete Protokolldateneinheiten, nachfolgend als PDUs bezeichnet, eines logischen Verbindungssteuerungsprotokolls, nachfolgend als LLC-Protokoll bezeichnet, das einer LLC-Schicht zugeordnet und gemäß einem LLC-Protokoll formatiert ist, umfassen, und wobei die Datenblöcke RLC-Datenblöcke umfassen, die einer RLC-Schicht zugeordnet und gemäß einem RLC-Protokoll formatiert sind.

14. Das Kommunikationsendgerät (400) nach Anspruch 11, wobei das Kommunikationsendgerät eine Basisstation umfasst und der Sender eine mobile Vorrichtung umfasst.

Revendications

1. Procédé de génération, par une entité de commande de liaison de radio unique, ci-après désignée sous le nom d'entité RLC, de blocs de couche inférieure (60) à l'aide de segments de données de paquets de couche supérieure (70, 80) pour la transmission de paquets de couche supérieure d'un émetteur à un récepteur, le procédé comprenant les étapes consistant en :

l'encapsulation (310) d'un segment de données final d'un premier paquet de couche supérieure (80) associé à un premier contexte de flux de paquets de priorité supérieure, ci-après abrégé en PFC, conjointement avec un segment de données restant d'un deuxième paquet de couche supérieure (70) associé à un deuxième PFC de priorité inférieure dans un bloc de données de priorité supérieure final, où, lorsque le bloc de données de priorité supérieure final est transmis de l'émetteur au récepteur, la transmission du premier paquet de couche supérieure (80) est achevée et la transmission du deuxième paquet de couche supérieure (70) est reprise ; et

l'inclusion (320) d'un indicateur de transition au bloc de données de priorité supérieure final de façon à indiquer une transition, à l'intérieur du bloc de données de priorité supérieure final, du premier paquet de couche supérieure (80) au deuxième paquet de couche supérieure (70), l'inclusion de l'indicateur de transition comprenant l'inclusion :

d'une valeur prédéterminée d'un indicateur de longueur (LI) indiquant un nombre d'octets, dans un champ de données du bloc de données de priorité supérieure final, qui sont nécessaires pour achever la transmission du segment de données final du premier paquet de couche supérieure (80) ; et

d'une identité de flux temporaire, ci-après abrégée en TFI, dans le champ de données du bloc de données de priorité supérieure final, ladite TFI étant associée de façon unique au deuxième PFC auquel appartient le deuxième paquet de couche supérieure (70).

2. Procédé selon la revendication 1, comprenant de plus l'inclusion d'un indicateur de remplissage au bloc de données de priorité supérieure final de façon à indiquer qu'une partie inutilisée du bloc de données de priorité supérieure final contient des données de remplissage.

3. Procédé selon la revendication 1, dans lequel les paquets de couche supérieure comprennent des unités de données de protocole, ci-après désignées sous le nom de PDU, d'un protocole de commande de liaison logique, ci-après désigné sous le nom de protocole LLC, qui sont associées à une couche LLC et formatées selon un protocole LLC, et dans lequel le bloc de données de priorité supérieure final comprend un bloc de données RLC associé à une couche RLC et formaté selon un protocole RLC.

4. Terminal de communication (400) pour la génération de blocs de couche inférieure pour la transmission à un récepteur, le terminal de communication (400) comprenant :

un émetteur/récepteur (402) configuré pour transmettre des blocs de données au récepteur sur un canal de communication sans fil ; et

un processeur (408) configuré pour générer, par une entité de commande de liaison de radio unique, ci-après désignée sous le nom d'entité RLC, de blocs de couche inférieure à l'aide de segments de données de paquets de couche supérieure pour la transmission par l'émetteur/récepteur (402), le processeur (408) étant configuré pour :

encapsuler un segment de données final d'un premier paquet de couche supérieure (80) associé à un premier contexte de flux de paquets de priorité supérieure, ci-après abrégé en PFC, conjointement avec un segment de données restant d'un deuxième paquet de couche supérieure (70) associé à un deuxième PFC de priorité inférieure dans un bloc de données de priorité supérieure final, où, lorsque le bloc de données de priorité supérieure final est transmis de l'émetteur au récepteur, la transmission du premier paquet de couche supérieure (80) est achevée et la transmission du deuxième paquet de couche supérieure (70) est reprise ; et

inclure un indicateur de transition au bloc de données de priorité supérieure final de façon à indiquer une transition, à l'intérieur du bloc de données de priorité supérieure final, du premier paquet de couche supérieure (80) au deuxième paquet de couche supérieure (70), l'indicateur de transition comprenant :

une valeur prédéterminée d'un indicateur de longueur (LI) indiquant un nombre d'octets, dans un champ de données du bloc de données de priorité supérieure final, qui sont nécessaires pour achever la transmission du segment de données final du premier paquet de couche supérieure (80) ; et

une identité de flux temporaire, ci-après abrégée en TFI, dans un champ de données du bloc de données de priorité supérieure final, ladite TFI étant associée de façon unique au deuxième PFC auquel appartient le deuxième paquet de couche supérieure (70).

5. Terminal de communication (400) selon la revendication 4, dans lequel le processeur (408) est de plus configuré pour inclure un indicateur de remplissage au bloc de données de priorité supérieure final de façon à indiquer qu'une partie inutilisée du bloc de données de priorité supérieure final contient des données de remplissage.

6. Terminal de communication (400) selon la revendication 4, dans lequel les paquets de couche supérieure comprennent des unités de données de protocole, ci-après désignées sous le nom de PDU, d'un protocole de commande de liaison logique, ci-après désigné sous le nom de protocole LLC, qui sont associées à une couche LLC et formatées selon un protocole LLC, et dans lequel le bloc de données de priorité supérieure final comprend un bloc de données RLC associé à une couche RLC et formaté selon un protocole RLC.

7. Terminal de communication (400) selon la revendication 4, où le terminal de communication comprend un dispositif mobile et le récepteur comprend une station de base.

8. Procédé de traitement de données générées par une entité de commande de liaison de radio unique, ci-après désignée sous le nom d'entité RLC, et reçues à partir d'un émetteur, le procédé comprenant les étapes consistant en :

la réception d'un bloc de données encapsulé, comprenant :

un segment de données final pour un premier paquet de couche supérieure (80) associé à un premier contexte de flux de paquets, ci-après abrégé en PFC ;

un segment de données restant d'un deuxième paquet de couche supérieure (70) associé à un deuxième PFC ; et

un indicateur de transition indiquant une transition, à l'intérieur du bloc de données, à partir du premier paquet de couche supérieure (80), de retour vers le deuxième paquet de couche supérieure (70) ; et

la séparation du segment de données restant pour le deuxième paquet de couche supérieure (70) à partir du bloc de données en fonction de l'indicateur de transition et la reprise d'une réception interrompue précédemment du deuxième paquet de couche supérieure (70), l'indicateur de transition comprenant :

une valeur prédéterminée d'un indicateur de longueur (LI) indiquant un nombre d'octets, dans un champ de données du bloc de données de priorité supérieure final, qui sont nécessaires pour achever la transmission du segment de données final du premier paquet de couche supérieure (80) ; et

une identité de flux temporaire, ci-après abrégée en TFI, dans un champ de données du bloc de données, ladite TFI étant associée de façon unique au deuxième PFC auquel appartient le deuxième paquet de couche supérieure (70).

9. Procédé selon la revendication 8, dans lequel le bloc de données reçu comprend de plus un indicateur de remplissage afin d'indiquer qu'une partie inutilisée du bloc de données reçu contient des données de remplissage.

10. Procédé selon la revendication 8, dans lequel les paquets de couche supérieure comprennent des unités de données de protocole, ci-après désignées sous le nom de PDU, d'un protocole de commande de liaison logique, ci-après désigné sous le nom de protocole LLC, qui est associé à une couche LLC et formaté selon un protocole LLC, et dans lequel les blocs de données comprend des blocs de données RLC associés à une couche RLC et formatés selon un protocole RLC.

11. Terminal de communication (400) pour traiter des données générées par une entité de commande de liaison de radio unique, ci-après désignée sous le nom d'entité RLC, et reçues à partir d'un émetteur, le terminal de communication (400) comprenant :

un émetteur/récepteur (402) configuré pour recevoir un bloc de données encapsulé, comprenant :

un segment de données final pour un premier paquet de couche supérieure (80) associé à un premier contexte de flux de paquets, ci-après abrégé en PFC ;

un segment de données restant pour un deuxième paquet de couche supérieure (70) associé à un deuxième PFC ; et

un indicateur de transition pour indiquer une transition, à l'intérieur du bloc de données, à partir du premier paquet de couche supérieure (80), de retour vers le deuxième paquet de couche supérieure (70) ; et

un processeur (408) configuré pour séparer le segment de données restant pour le deuxième paquet de couche supérieure (70) à partir du bloc de données en fonction de l'indicateur de transition et à reprendre une réception interrompue précédemment du deuxième paquet de couche supérieure (70), l'indicateur de transition comprenant :

une valeur prédéterminée d'un indicateur de longueur (LI) indiquant un nombre d'octets, dans un champ de données du bloc de données de priorité supérieure final, qui sont nécessaires pour achever la transmission du segment de données final du premier paquet de couche supérieure (80) ; et

une identité de flux temporaire, ci-après abrégée en TFI, dans un champ de données du bloc de données, ladite TFI étant associée de façon unique au deuxième PFC auquel appartient le deuxième paquet de couche supérieure (70).

12. Terminal de communication (400) selon la revendication 11, dans lequel le bloc de données reçu comprend de plus un indicateur de remplissage afin d'indiquer qu'une partie inutilisée du bloc de données reçu contient des données de remplissage.

13. Terminal de communication (400) selon la revendication 11, dans lequel les paquets de couche supérieure comprennent des unités de données de protocole, ci-après désignées sous le nom de PDU, d'un protocole de commande de liaison logique, ci-après désigné sous le nom de protocole LLC, qui est associé à une couche LLC et formaté selon un protocole LLC, et dans lequel les blocs de données comprend des blocs de données RLC associés à une couche RLC et formatés selon un protocole RLC.

14. Terminal de communication (400) selon la revendication 11, où le terminal de communication comprend une station de base et l'émetteur comprend un dispositif mobile.

Drawing