Wireless communication method and apparatus for supporting reconfiguration of radio link control parameters
10 claims: 2 independent, 8 dependent
- 1Reivindicações 1. Método de reconfiguração de uma unidade de controle de links de rádio (RLC) em uma unidade de transmissão e recepção sem fio (WTRU), caracterizado por compreender:- recebimento de uma mensagem de reconfiguração de controle de recursos de rádio (RRC), em que a mensagem de reconfiguração de RRC inclui um elemento de informação (IE) “tamanho de PDU de RLC DL”, que indica que a unidade de RLC deverá ser reconfigurada de recebimento de unidades de dados de protocolo (PDUs) de RLC com tamanho fixo para recebimento de PDUs de RLC com tamanho flexível, em que a unidade de RLC compreende um subconjunto do lado de transmissão e um subconjunto do lado de recepção;- determinação se um IE “restabelecimento de RLC em um lado” está presente na mensagem de reconfiguração de RRC;- restabelecimento somente do subconjunto do lado de recepção caso a determinação seja positiva;e - restabelecimento do subconjunto do lado de recepção e do subconjunto do lado de transmissão caso a determinação seja negativa.
- 2Método conforme a reivindicação 1, caracterizado pelo fato de que compreende adicionalmente a configuração da unidade de RLC para receber PDUs de RLC com tamanho fixo caso o IE “tamanho de PDU de RLC DL” seja definido como “tamanho fixo, em que o tamanho das PDUs de RLC é indicado na mensagem de reconfiguração de RRC.
- 3Método conforme a reivindicação 1, caracterizado pelo fato de que compreende adicionalmente a configuração da unidade de RLC para receber PDUs de RLC com tamanho flexível caso o IE “tamanho de PDU de RLC DL” seja definido como “tamanho flexível”, em que o tamanho das PDUs de RLC é indicado na mensagem de reconfiguração de RRC.
- 4Método conforme a reivindicação 1, caracterizado pelo fato de que o critério de restabelecimento de RLC é avaliado quando um elemento de informação (IE) “informação de RLC” está presente na mensagem de reconfiguração de RRC.
- 5Método conforme a reivindicação 1, caracterizado pelo fato de que a mensagem de reconfiguração de RRC inclui um IE “modo de RLC de link inferior” definido como “RLC AM”.
- 6Unidade de transmissão e recepção sem fio (WTRU) caracterizada por compreender:- uma unidade de controle de links de rádio (RLC) que inclui um lado de transmissão e um lado de recepção;2/2 em que a unidade de RLC é configurada para receber uma mensagem de reconfiguração de controle de recursos de rádio (RRC) que inclui um elemento de informação (IE) “tamanho de PDU de RLC DL”, em que o IE “tamanho de PDU de RLC DL” indica para a WTRU que uma unidade de controle de links de rádio (RLC) deverá ser reconfigurada de recebimento de unidades de dados de protocolo (PDUs) de RLC com tamanho fixo para o recebimento de PDUs de RLC com tamanho flexível;em que a unidade de RLC é adicionalmente configurada para restabelecer apenas o subconjunto do lado de recepção caso um IE “restabelecimento de RLC de um lado” esteja presente na mensagem de reconfiguração de RRC e definido como verdadeiro;e em que a unidade de RLC é adicionalmente configurada para restabelecer o subconjunto do lado de recepção e o subconjunto do lado de transmissão caso um IE “restabelecimento de RLC de um lado” esteja presente na mensagem de reconfiguração de RRC e não definido como verdadeiro.
- 7WTRU conforme a reivindicação 6, caracterizada pelo fato de que a unidade de RLC é adicionalmente configurada para receber PDUs de RLC com tamanho fixo caso o IE “tamanho de PDU de RLC DL” seja definido como “tamanho fixo, em que o tamanho das PDUs de RLC é indicado na mensagem de reconfiguração de RRC.
- 8WTRU conforme a reivindicação 6, caracterizada pelo fato de que a unidade de RLC é adicionalmente configurada para receber PDUs de RLC com tamanho flexível caso o IE “tamanho de PDU de RLC DL” seja definido como “tamanho flexível”, em que o tamanho das PDUs de RLC é indicado na mensagem de reconfiguração de RRC.
- 9WTRU conforme a reivindicação 6, caracterizada pelo fato de que é adicionalmente configurada para avaliar critérios de restabelecimento de RLC quando um elemento de informação (IE) “informações de RLC” estiver presente na mensagem de reconfiguração de RRC.
- 10WTRU conforme a reivindicação 6, caracterizada pelo fato de que a mensagem de reconfiguração de RRC inclui um IE “modo de RLC de link inferior” definido como “RLC AM”. 1/1 WTRU 100 110:rSubcõhjúríto dõj [lado de trasmis-1 sao Subconjunto do lado de recepção Mensagem de reconfiguração de RRC 105 140 Buffer de transmissão 115 125 Unidade de controle de recursos de rádio |<(RRC) ZY Unidade de controle de -> acesso a meios (MAC) Unidade de camada 1 (L1) física (PHY) -135
Independent claims10
395 paragraphs in 1 section, as filed
(54) Title: METHOD AND APPARATUS OF (57) Summary:
WIRELESS COMMUNICATION TO SUPPORT RADIO LINK CONTROL PARAMETER RECONFIGURATION.
(30) Unionist Priority: 03/16/2007 us 60 / 895,338,
26/03/2007 US 60 / 908,076, 26/04/2007 US 60 / 914,189 (73) Holder (s): interdigital Technology Corporation (72) Inventor (s): christopher r. cave, diana pani, paul MARINIER, STEPHEN E. TERRY (74) Attorney (s): ADVOCACIA PIETRO ARIBONI S / C (86) International Request: pct us2oosoo3336 of 13/03/2008 (87) International Publication: wo 2008 / 115392de 09/25/2008
WTRU
100·
110rSuficõnJülo dóJ ally of trasmis-i Jsão
Subset t on the [receiving,
RRC reset message
105
Z-Rr buffer + 140 L transmission<sup>1</sup>___—
Radio resource control unit * (RRC)
115 - Media access control (MAC) unit
135
Physical layer 1 (L1) unit (PHY)
1251201/37
Wireless communication method and apparatus to support reconfiguration of radio link control parameters.
Field of the Invention
The present invention relates to wireless communications.
Background
Some of the main goals of the evolution of high-speed packet access (HSPA) include higher data speeds, higher capacity and system coverage, expanded support for packet services, reduced latency, reduced operator costs and backward compatibility. Meeting these objectives requires evolutions to the radio interface protocol and network architecture. More specifically, meeting these objectives required a set of improvements and architectural changes to the layer 2 (L2) functionalities (that is, radio link control (RLC) and media access control (MAC)).
Some of the L2 enhancements include flexible-sized RLC protocol data units (PDUs) (ie, RLC PDUs that have flexible sizes), high-speed MAC segmentation / concatenation (MAC-hs) and multiplexing. In Version 6 (R6) of access via universal terrestrial radio (UTRA), RLC entities with recognized mode (AM) can only use fixed size RLC PDUs (ie RLC PDUs that have a fixed size). In addition, the MAC-hs sublayer on Node B can support only the concatenation of dedicated MAC PDUs (MAC-d). UTRA Version 7 (R7) L2 enhancements result in significant RLC / MAC changes to R6 characteristics.
Currently, when radio bearers (RB) are established or reconfigured using radio resource control (RRC) signaling, the information element (IE) “RB mapping information is present. The “RB mapping information” contains information about the RLC instance and transport channels corresponding to the RB.
The configuration of MAC-hs needs to be the same across all RBs mapped to a shared high-speed lower link channel (HS-DSCH), otherwise an invalid configuration will result.
In HSPA, high-speed shared channels are monitored by a wireless transmission and reception unit (WTRU) in a single cell (ie the HS-DSCH cell in service). Due to mobility, when the WTRU is moving from one cell to another, the WTRU needs to make a cell change in service by switching to a new HS-DSCH cell in service and ending communication with the old HS-DSCH cell in service . In a Node repositioning procedure, a delivery between Nodes B takes place from a Node
2/37
Old B (that is, a source Node B) to a new Node B (that is, a target Node B).
At the time of a change of Node B in service, the target Node B needs to start data transmission along the new configuration. Delivery can take place between evolved HSPA B Nodes that support L2 enhancements or to / for cells with or without L2 enhancements. In both cases, the WTRU must be able to deliver, adjust to the new settings and minimize data loss.
With the introduction of new L2 enhancements, new procedures need to be defined in order to optimize and minimize data loss during delivery between R7 cells or between an R7 cell and an R6 cell. Specifically, procedures that deal with restarting the MAC-hs entity need to be modified in order to compensate for the new L2 enhancements.
In addition, it cannot be considered that all Nodes B of R6 will be updated at the same time as Nodes B of R7. Deliveries between cells R6 and R7 can therefore occur frequently. Due to the functional changes of RLC and MAC, delivery methods need to be defined with minimal loss of quality and data between these cells. Specifically, on the WTRU side, MAC-hs and RLC need to make functional changes during deliveries.
Summary of the Invention
Various wireless communication methods and devices are described to support the reconfiguration of RLC parameters. An RRC reconfiguration message is generated that indicates that an RLC unit in a WTRU or a universal terrestrial radio access network (UTRAN) must be reconfigured to support flexible-sized RLC PDUs to support fixed-size RLC PDUs or vice versa. If an IE “RLC reset on one side is present in the RRC reset message, only a subset of the receiving side or transmission side on the RLC unit is reset. Otherwise, the subset of the receiving side and a subset of the transmission side in the RLC unit are both reset. Flexible size RLC PDUs can be discarded and a message indicating the discarded flexible size RLC PDUs can be transmitted. Flexible size RLC PDUs can be modified to match a set of previously defined sizes.
Brief Description of the Figures
A more detailed understanding can be obtained from the following description together with the attached figures, in which:
-a Figure 1 is an example of a block diagram of a WTRU that moves between cells R6 and R7 and is configured to operate with the new MAC-hs and RLC sublayers
3/37 when a delivery message is received during an in-service cell change procedure; and
- Figure 2 is an example of a block diagram of a UTRAN that sends an RRC reconfiguration message to the WTRU of Figure 1.
Detailed Description
When indicated below, the terminology “wireless transmission and reception unit (WTRU)” includes, but is not limited to, user equipment (UE), mobile station, fixed or mobile subscriber unit, pager, cell phone, personal digital assistant (PDA), computer or any other type of user device capable of operating in a wireless environment. When indicated below, the terminology “base station includes, but is not limited to, a Node B, location controller, access point (AP) or any other type of interface device capable of operating in a wireless environment.
Various wireless communication methods that optimize delivery scenarios, reset procedures and reconfiguration procedures for an RLC entity are described in the present. In addition, several wireless communication methods for deliveries between cells are described where one or both cells support L2 enhancements. Upper link (UL) and lower link (DL) are both applicable to these wireless communication methods.
The following expressions are used throughout the description below and are defined briefly. An enhanced MAC-hs payload unit (MAC-ehs) is a MAC-ehs service data unit (SDU) or a segment of a MAC-ehs SDU contained in a MAC-ehs PDU. A MAC-ehs reordering PDU is a set of MAC-ehs payload units in a MAC-ehs PDU that belongs to the same priority queue. An enhanced cell is a cell that supports L2 enhancements, that is, flexible-sized RLC PDUs. An unenhanced cell is a cell that does not support L2 enhancements, that is, fixed-size RLC PDUs.
When indicated below, R6 includes, but is not limited to, a cell, Node B or radio network controller (RNC) that does not support flexible-sized RLC PDUs (that is, fixed-size RLC PDUs are supported) . When indicated below, R7 includes, but is not limited to, a cell, Node B or RNC that supports flexible-sized RLC PDUs.
When indicated below, UTRAN includes, but is not limited to, a cell, Node B, RNC or network node.
Figure 1 is an example of a block diagram of a WTRU 100 that moves between non-enhanced cells and enhanced cells and is configured for operation with the new RLC and MAC-ehs sublayers when a
4/37 delivery message is received during an in-service cell change procedure. As shown in Figure 1, the WTRU 100 includes an RRC 105 unit, an RLC 110 unit, a MAC 115 unit and a physical layer 1 (L1) unit (PHY) 120. The initiation of an in-service cell change can occur in response to the receipt of an RRC 125 reconfiguration message, such as an RRC RB reconfiguration message, a transport channel RRC reconfiguration message, or a reconfiguration message. Physical channel RRC. The RLC unit 110 includes a subset of the transmission side 130 and a subset of the receiving side 135. The subset of the transmission side 130 includes a transmission buffer 140.
The RRC 125 reconfiguration message can be generated by a UTRAN. Figure 2 is a block diagram illustrating an example of configuring a protocol stack on the UTRAN 200. The UTRAN 200 can include an RRC 205 unit, an RLC 210 unit, a MAC 115 unit and an L1 unit. PHY 220. The RLC unit 210 includes a subset of the transmission side 230 and a subset of the receiving side 235. The subset of the transmission side 230 includes a transmission buffer 240. The RRC 205 unit generates the RRC 125 reconfiguration message to initiate a change of cells in service.
The UTRAN 200 may also include a target Node B, a source Node B, a control RNC (CRNC) and an in-service RNC (SRNC) (not shown). The RNC can include an RLC unit and an RRC unit (not shown). Alternatively, the RNC functionalities are included in Node B and, therefore, no control RNC or RNC in service is present.
RLC instances do not need to have the same RLC configuration for all RBs mapped to an HS-DSCH. A WTRU connected to an enhanced cell can simultaneously support, for example, one or more RLC instances configured with fixed size RLC PDUs and / or flexible size RLC PDUs. The enhanced MAC-ehs is capable of supporting the reception of fixed size RLC PDUs and flexible size RLC PDUs.
A WTRU that operates in an unenhanced cell cannot, however, support RLC instances with flexible RLC PDUs. All RLC entities mapped to a normal HS-DSCH (ie, a MAC-hs) need to be configured with fixed-size RLC PDU operation. This is due to the fact that the normal MAC-hs configuration does not support the reception and signaling of flexible RLC PDUs. Consequently, an RLC that supports fixed size RLC PDUs can designate an RLC AM instance or an RLC instance in unrecognized mode (UM).
5/37
To avoid restores, the logical channels corresponding to an RLC instance do not need to change its configuration when moving from an unenhanced cell to an enhanced cell. When a WTRU moves from a cell with normal MAC-hs configuration to a cell with enhanced MAC-ehs configuration, for example, RLC instances configured to support fixed-size RLC PDUs do not need to be reconfigured to support PDUs of RLC with flexible size.
The RB that supports fixed-size RLC PDUs in an enhanced cell can maintain the fixed-size RLC PDU configuration or can be reconfigured to support flexible-sized RLC PDUs at the time of delivery or later, in which case a RB reconfiguration will be triggered and the RRC will perform the necessary steps. This allows signaling RBs to maintain their existing RLC configuration and prevent the re-establishment of the RLC entity. If deliveries between enhanced and enhanced cells often occur on a network, this method avoids reinstating non-enhanced AM RLC instances if the WTRU moves frequently between enhanced and non-enhanced cells. This method also allows for optimizations for RLC UM instances. If RLC UM instances are not extended to support RLC PDUs with flexible size at R7, RLC UM instances do not need to be reinstated or reconfigured when moving from unenhanced cells to enhanced cells and vice versa. In case flexible size PDUs are introduced for RLC UM instances, the same methods described for RLC AM apply.
Restoring RLC behavior by RB during movement between enhanced cells and non-enhanced cells:
When the WTRU changes cells in service during delivery that support different versions (ie, R6 and R7), the WTRU has the option of maintaining an existing RLC instance without changing its configuration (ie, supporting RLC PDUs with size fixed over an enhanced MAC configuration) or the existing RLC instance can be reconfigured. An RLC instance that supports flexible-sized RLC PDUs in an enhanced L2 cell cannot maintain its configuration, however, when moving to an unenhanced L2 cell because normal MAC-hs cannot support receiving PDUs from Flexible size RLC. Therefore, an RLC reset or a new procedure that handles changing the RLC configuration is needed to minimize data loss. The reconfiguration change to the RLC unit may also occur due to the repositioning of SRNS, which involves moving an SRNC that supports flexible-sized RLC PDUs to an SRNC that does not support
6/37
Flexible size RLC.
Methods of carrying out and assessing the need to restore RLC are required on a RB basis. When a WTRU moves between enhanced and non-enhanced L2 cells or when the RLC changes its configuration, no RLC reconfiguration occurs and therefore no RLC reset is performed and / or an RLC configuration change occurs for RLC PDUs with fixed size for flexible size RLC PDUs. In this case, an RLC reconfiguration procedure can be triggered. The restoration of the RLC entity in this case is not always necessary, but it can be optionally carried out.
The reconfiguration procedure configures only the RLC entity to begin supporting flexible-sized RLC PDUs. No data loss occurs, as fixed-size RLC PDUs can be transmitted and be transparent to the WTRU and MAC-ehs. The reconfiguration procedure configures only the RLC entity to start supporting flexible-sized RLC PDUs. No data loss occurs, as fixed-size RLC PDUs can be transmitted to the WTRU and MAC-ehs. When a change in the RLC configuration occurs from RLC PDUs with flexible size to RLC PDUs with fixed size, an RLC reset is required or, optionally, a new procedure can be performed to deal with the change and try to minimize the loss of Dice. The WTRU is configured to always remain on RLC R7 and support flexible size RLC PDUs. The UTRAN can change the RLC settings without explicitly indicating to the WTRU that a change from R6 to R7 or vice versa has occurred.
Evaluation criteria for performing an RLC reset or reset:
When the RLC changes its configuration, a RB reconfiguration procedure will be triggered. RB RRC reconfiguration procedures and information elements are used to assess and indicate the need to re-establish RLC.
The need for RLC reset for signaled RB can be determined by explicit RRC signaling that adds a new field to an existing RB information element (IE) or signaling RB (SRB) that indicates RLC reset. Explicit RRC signaling can indicate a one-sided or full recovery. RRC procedures corresponding to the RRB reconfiguration procedure can be modified to perform condition checks on the new configuration parameters provided (ie, RLC PDU size, flexible or fixed) and the old configuration parameters of the reconfigured RLC entity (i.e., RLC PDU size, flexible or fixed) and
7/37 to assess the need to restore RLC.
The assessment of restoration criteria can be performed in the description of generic actions by receiving IE RB mapping information, in the description of generic actions by receiving IE “RLC information” and / or by adding a new one. section that describes generic actions upon receipt of the lower link (DL) or upper link (UL) RLC configuration IE.
The following sections describe the different possibilities for evaluating and implementing RLC restoration criteria and apply to DL RLC, UL RLC and, optionally, UM entities.
Option 1:
For this option, the RLC restoration assessment is carried out within the IE actions "RB mapping information" or in a new section that deals with actions upon receipt of the IE "RLC configuration. Note that the RLC configuration (ie, whether the choice of RLC is fixed or flexible) is provided in IE “RB mapping information” for this option. The IE “RLC configuration” can be provided, however, in other information elements. The “RLC configuration” IE can provide the WTRU with information regarding whether the RLC instance is configured to support fixed size RLC PDUs or flexible size RLC PDUs.
If the IE “RLC configuration” is set to the “enhanced” value and the previously stored value is set to “normal” (or if the value is different from the one currently set), an RLC entity (or layer) is reconfigured according to IE DL RLC configuration Optionally, if restoration is necessary, the RLC entity is restored. Otherwise, if the IE “RLC configuration is set to the“ normal ”value and the previously stored value is set to“ enhanced ”(or if the value is different from the one currently set). The RLC entity is reestablished by performing one-sided or total re-establishment.
Upon receipt of an RRC message that results in the reconfiguration of the RB, the WTRU performs a set of actions related to RB mapping. For UL RLC operation, the reset condition can optionally be performed at present. More specifically, if that RB is using AM and the RLC PDU configuration (that is, RLC PDU size selection) applicable to the UL logical channel is changed from a configuration that supports flexible-sized RLC PDUs to RLC PDUs fixed size and if the IE “one-sided RLC restoration” is included in that RRC message and set to TRUE, the WTRU restores the entity's transmission side
8/37
Corresponding RLC. Otherwise, the WTRU restores the corresponding RLC entity.
When the configuration that supports fixed-size RLC PDUs is changed to a configuration that supports flexible-sized RLC PDUs, RLC reset is optional and can be performed when the length indicator indicated in a length indicator field for the PDUs of RLC is changed between seven and fifteen bits. As described above, only the transmission side subset 130 and 230 (if the IE “one side RLC establishment” is included) or the complete RLC unit 110 and 210 (that is, the transmission side subset 130 and 230 and the receiving side subset 135 and 235) can be reset.
Option 2:
The RLC reinstatement criterion is assessed in the actions upon receipt of the IE “RLC information”. When the actions corresponding to the IE “RLC information” are performed, the procedure needs to be aware of the configuration of the RLC entity (ie, RLC PDU with flexible size or RLC PDU with fixed size). This can be accomplished by adding a new IE to the IE “RLC information” that indicates the RLC configuration. The new IE indicates whether a fixed or flexible RLC PDU size can be used. The new IE also indicates whether normal or amplified RLC is used.
The RLC DL PDU size IE value set can be extended to contain a reserved value that explicitly indicates that the RLC supports flexible-sized RLC PDUs. For example, a value of 0 or 8 or “all 1” can be used in binary and the like. The IE “RB mapping information” and the IE “RLC DL configuration” that specifies the version of the RLC configuration used are examined. Information about the RLC configuration is obtained from any other IE that contains this information. If the new IE is not included in IE “RLC information”, the reset procedure is then based on information from other elements or the reset procedure occurs in IE RB mapping information.
If a new RB supports (that is, is configured to start operating with) fixed size RLC PDUs and an old RB supports (that is, it is configured to operate with flexible RLC PDUs), the RLC entity is reinstated. The restoration can be a restoration on the one hand. For RLC DL, for example, only the receiving side can be reset and, for RLC UL, only the transmission side can be reset. To perform a reset on one side, you can use the existing IE “reset on one side” in IE “RLC information”. Optionally, the RRC procedure indicates
9/37 specifically the restoration of the receiving or transmitting entity without using the IE restoration on one side ”.
If a new RB supports flexible-sized RLC PDUs and an old RB supports fixed-size RLC PDUs and the RLC unit 110 and 210 is reconfigured, reset can be optional.
A description of the RRC procedure is included below. The RRC procedure has been modified to correspond to the IE “RLC information”. For the purposes of this specification, a new information element “DLRLC size indicator” is added to the IE “RLC information” or UL, “UL RLC size indicator”, which has a normal or fixed RLC value . An example of the new IE is shown in Table 1.
The RRC procedure corresponding to the actions performed in the presence of IE “RLC information” is modified to compensate for changes in the configuration of RLC instances. The IE “RLC size indicator” is used as an example in the procedure described below. Generally, however, the IE “RLC size indicator” represents an indication of the RLC configuration, can be called differently and have a different enumeration such as enhanced / normal or values.
The modified RRC procedure can be performed as follows:
Upon receipt of the IE “RLC information”, the
WTRU shall:
1> if the IE “lower link RLC mode '' is present and defined in“ RLC AM '';
2> if the IE “RLC DL size indicator” is present and set to the “fixed” value;
3> if the value is different from the one currently defined in the RLC entity;
4> if the IE “RLC establishment on one side” is set to TRUE;
<td></td><td> 5></td><td>restore the</td><td>side of</td>
<td>receiving the corresponding RLC entity;</td><td></td><td></td><td></td>
<td></td><td>4> case</td><td>contrary:</td><td></td>
<td></td><td> 5></td><td>restore</td><td>entity</td>
<td>Corresponding RLC;</td><td></td><td></td><td></td>
<td> 3></td><td>to set up</td><td>the entity</td><td>RLC</td>
corresponding according to the new RLC PDU size indicator;
2> otherwise, if the “size indicator
10/37
RLC DL ”is present and defined as“ flexible ”:
3> if the value is different from the one currently defined in the RLC;
4> reconfigure the RLC entity (optionally, reset RLC if the RRC is configured to reset when moving from an unenhanced cell to an enhanced cell);
2> otherwise (after the statement “otherwise, there are the procedures that deal with the fixed RLC PDU size instances or the case where the RLC DL size indicator is not present; the steps after this statement “otherwise they correspond to the steps in R6);
3> if the IE “RLC PDU size
DL ”is not present;
4> the determination of the lower link RLC PDU size will be handled at the RLC level, without any RRC configuration.
Note: the case in which this mandatory IE is not present is intended to handle interaction with a network using an earlier version of the specification.
3> otherwise, if the IE RLC PDU size DL ”is present and no lower link RLC PDU size is currently defined in the RLC entity:
4> configure the corresponding RLC entity with the lower link RLC PDU size;
3> otherwise, if the IE “RLC DL PDU size” is present and its value is different from that currently defined in the RLC entity;
Note: The lower link RLC PDU size defined in the RLC entity can be configured explicitly or, if no explicit configuration is provided, derived by the first RLC PDU received.
4> if the IE “restoration of RLC on one side” is set to TRUE;
5> restore the receiving side of the corresponding RLC entity;
4> otherwise:
5> reestablish the entity
Corresponding RLC.
4> configure the RLC entity
Corresponding 11/37 with the new lower link RLC size.
The verification of conditions for restoration of RLC is not restricted to the order specified in the two options above and, therefore, can be performed in any order. In addition, the name of the new lEs, such as RLC DL configuration IE and RLC DL size indicator IE, is subject to change. The procedure corresponding to this IE remains unchanged, regardless of the names of the LE.
For Option 2, an example of the functional definition of IE “RLC information” is provided in Table 1 below.
io Table 1
IE “RLC Information” Modified
<td>Name of group / element of information</td><td>Need</td><td>Multi</td><td>Type and reference</td><td>description semantics</td><td>Version</td>
<td>Choose mode link RLC higher</td><td>OP</td><td></td><td></td><td>Indicates whether be used RLC in mode recognized, not recognized or transparent</td><td></td>
<td>> RLC AM</td><td></td><td></td><td></td><td></td><td></td>
<td>»Disposal of RLC of streaming</td><td>MP</td><td></td><td>Disposal of RLC of streaming 10.3.4.25</td><td></td><td></td>
<td>»Size of window of streaming</td><td>MP</td><td></td><td>Number integer (1.8, 16, 32, 64, 128, 256, 512, 768, 1024, 1536, 2047, 2560, 3072, 3584, 4095)</td><td>Maximum number of PDUs from RLC sent without recognition . This one parameter is necessary if use mode recognized. THE WTRU should</td><td></td>
12/37
<td></td><td></td><td></td><td></td><td>also consider that the window of receiver of UTRAN is equal to this value.</td><td></td>
<td>»RST of timer</td><td>MP</td><td></td><td>Number integer (50, 100, 150, 200, 250, 300, 350, 400, 450, 500, 550, 600, 700, 800, 900, 1000)</td><td>Time elapsed in milliseconds. It is used to trigger the retransmission to RESTART PDU.</td><td></td>
<td>»Maximum RST</td><td>MP</td><td></td><td>Number integer (1, 4, 6, 8, 12, 16, 24, 32)</td><td></td><td></td>
<td>»Information meeting</td><td>OP</td><td></td><td>Information meeting 10.3.4.4</td><td></td><td></td>
<td>> RLC ONE</td><td></td><td></td><td></td><td></td><td></td>
<td>>> Disposal of RLC of streaming</td><td>OP</td><td></td><td>Disposal of RLC of streaming 10.3.4.25</td><td></td><td></td>
<td>> RLC TM</td><td></td><td></td><td></td><td></td><td></td>
<td>>> Disposal of RLC of streaming</td><td>OP</td><td></td><td>Disposal of RLC of streaming 10.3.4.25</td><td></td><td></td>
<td>»Segmentation indication</td><td>MP</td><td></td><td>Boolean</td><td>TRUE indicates that it is performed the segmentation</td><td></td>
13/37
<td>Choose mode link RLC bottom</td><td>OP</td><td></td><td></td><td>Indicates whether be used RLC in mode recognized, not recognized or transparent</td><td></td>
<td>> RLC AM</td><td></td><td></td><td></td><td></td><td></td>
<td>> Indicator of PDU size DL RLC</td><td>MP</td><td></td><td>Listed (fixed, flexible)</td><td>Indicates whether must be used sizes of RLC PDU fixed or flexible</td><td>REL-7</td>
<td>»Size of DL RLC PDU</td><td>MP</td><td></td><td>Number all (16.5000 in breaks of 8)</td><td>The unit is the bit</td><td>REL-5</td>
<td>»Supply in sequence</td><td>MP</td><td></td><td>Boolean</td><td>TRUE indicates that the RLC should preserve the order of PDUs on each superior when these are provided. FALSE indicates that the entity Receiving RLC may allow the supply of SDUs for layer superior in</td><td></td>
14/37
<td></td><td></td><td></td><td></td><td>different order of submitted to sublayer RLC on the side transmitter.</td><td></td>
<td>»Size of window of reception</td><td>MP</td><td></td><td>Number integer (1, 8, 16, 32, 64, 128, 256, 512, 768, 1024, 1536, 2047, 2560, 3072, 3584, 4095)</td><td>Maximum number of PDUs from RLC with receivement allowed. This parameter is necessary if use mode recognized. THE WTRU should also consider that the window of transmitter UTRAN is equal to this value.</td><td></td>
<td>>> Information situation Link RLC bottom</td><td>MP</td><td></td><td>Contact Information of situation of RLC's bottom link 10.3.4.1</td><td></td><td></td>
<td>> RLC ONE</td><td></td><td></td><td></td><td></td><td></td>
<td>»Size of LI RLC A DL</td><td>MP</td><td></td><td>Number integer (7, 15)</td><td>Size in bits for use for 0 LI ONE Link RLC bottom</td><td>REL-6</td>
<td>»Size of DL reception window</td><td>qCV-Not- SIB16O</td><td></td><td>Number integer (32, 48, 64, 80, 96, 112)</td><td></td><td>REL-6</td>
<td>> RLC TM</td><td></td><td></td><td></td><td></td><td></td>
15/37
<td>»Indication of segmentation</td><td>MP</td><td></td><td>Boolean</td><td>TRUE indicates the targeting</td><td></td>
<td>Restoration the RLC of a side</td><td>MP</td><td></td><td>Boolean</td><td>TRUE indicates that just one side of the entity RLC AM is reestablished</td><td>REL-5</td>
<td>Interpretation of bits AND alternative</td><td>CV-Not- SIB16o</td><td></td><td>Listed (true)</td><td>The absence of this IE indicates: "interpretation bit E normal"</td><td>REL-6</td>
If the restoration of RLC for different RLC configurations is not evaluated in IE “RLC information”, condition checks of the PDU size of RLC DL in IE “RLC information” should only be carried out if the RLC AM instance sustains fixed RLC PDU sizes.
Otherwise, if a. condition verification is performed and the RLC DL PDU size is present for flexible RLC configurations, unnecessary restores may result.
With reference to Figures 1 and 2, an alternative method of adjusting the new RLC configuration on WTRU 100 and UTRAN will now be described
200. This alternative method is applicable when the subset of the receiving side 135 and
235 explicitly signal the RLC configuration via the RRC RB reconfiguration messages and is configured to support flexible-sized RLC PDUs. When the subset of the receiving side 135 and 235 is configured to support flexible-sized RLC PDUs, the subset of the receiving side 135 and 235 can receive an indication of the RLC PDU size that the subset of the transmitting side 130 and 230 is using ( when configured to support fixed-size RLC PDUs) from the top layers. This method is also applicable to the case where the RLC unit 110 and 220 changes the size of the RLC PDU length indicator field from 7 to 15.
When changing from an RLC configuration that supports flexible RLC PDU to an RLC configuration that supports fixed RLC PDU sizes, the transmission side subset 130 and 230 and the receiving side subset 135 and 235 need to discard Flexible size RLC PDUs.
16/37
More specifically, at a given activation time, the transmission side subset 130 and 230 discards flexible size RLC PDUs (or RLC PDUs with a different size than the fixed recognized data (AMD) size PDU) that have been transmitted once and have not yet been recognized. An example of activation time can be the moment when Node B starts using normal MAC-hs in the case of DL or MAC-i / is in the case of UL. The transmission side subset 130 and 230 can dispose of the RLC PDUs according to one or a combination of any of the following rules;
1. any RLC PDU with a size other than the length of the fixed RLC PDU (applies to flexible size RLC PDUs that have been created but have not necessarily been transmitted yet);
2. any RLC PDU with a size different from the length of fixed RLC PDUs that have already been transmitted at least once (applies only to RLC PDUs that have been transmitted or submitted to lower layers, whereby RLC PDUs that have been created but have not yet been transmitted are not discarded);
3. all RLC PDUs with a sequence number (SN) up to the last RLC PDUs with a flexible RLC PDU size (or a size other than the fixed PDU length), inclusive;
4. all RLC PDUs with SN up to the last RLC PDU with a flexible RLC PDU size (or a size different from the fixed PDU length) that has been transmitted at least once, inclusive;
5. all RLC SDUs up to the last SDU contained in the last RLC PDU with a flexible RLC PDU size (or a size other than the configured fixed PDU length);
6. all RLC SDUs up to the last SDU contained in the last RLC PDU with a flexible PDU size (or a size other than the configured fixed PDU length);
7. all RLC SDUs for which at least one segment was contained in a PDU with a different size than the configured fixed PDU size that was transmitted at least once; and / or
8. all RLC PDUs in a retransmission buffer that has been transmitted to lower layers and that have an assigned SN.
If the last discarded RLC PDU contains an RLC SDU segment, that RLC SDU can optionally be reconstructed using the new configuration (ie, a new fixed RLC PDU size).
The transmission side subset 130 and 230 does not reset status parameters and sequence numbers. Then, the subset of the
17/37 transmission side 130 and 240 proceeds to indicate to the receiving side subset 135 and 235 which RLC PDUs or RLC SDUs have been discarded.
A move receipt window control (SUFI) superfield (SUFI) can be used to indicate discarded RLC PDUs or RLC SDUs. If “send MRW” is not configured, the MRW SUFI is assembled with the disposal information. More specifically, it must indicate the last RLC PDU SN or RLC SDU discarded (SN_MRW = last RLC PDU SN discarded + 1). The subset of the receiving side 135 and 235 then discards all RLC PDUs with SN <SN_MRW and moves the receiving window proportionally.
If “send MRW is not configured, information from only fifteen discarded SDUs can be indicated. This may not be sufficient to indicate all RLC SDUs to be discarded, especially if a large number of SDUs are discarded. More than one MRW SUFI may therefore need to be sent.
A field with length N can always be set to zero or can be optionally set to indicate the length of the last SDU belonging to the PDU.
A new MRW SUFI has now been introduced and is only used for delivery purposes. The new MRW SUFI can include an SN_MRW field to indicate the sequence number of the last PDU or SDU to be discarded. The reception window is proportionally updated and all RLC PDUs with SN up to and including the SN_MRW field are discarded. Optionally, prior to the disposal of all RLC PDUs, the receiving side subset 135 and 235 can combine all RLC PDUs into RLC SDUs and deliver them to the upper layers. The receiving side subset 135 and 235 can then discard all RLC PDUs up to and including SN_MRW, which cannot be merged into RLC SDUs.
You can avoid restoring RLC by using the SDU discard function to discard SDUs that have been created with flexible RLC PDUs when the cell in service is changed to an inherited Node B or when an inherited Node B is added to the enhanced dedicated channel active set (E-DCH) for the UL case. The RLC then uses the MRW SUFI to instruct the WTRU to move the reception window and discard the same RLC PDUs.
This method results in the same amount of data loss as the RLC reset if the reconfiguration takes place at the time of activation. Data loss can be minimized, however, if the transmission side subset 130 and 230 starts generating fixed RLC PDUs when the
18/37 delivery is made or when the transmission side subset 130 and 230 becomes aware of the delivery. The moment the delivery takes place (that is, at the given activation time), the discard function starts. This will allow the RLC 110 unit to attempt to release some flexible size RLC PDUs until the end of the activation time. When data is transmitted over the target cell radio link (ie, a delivery is made), all RLC PDUs with flexible size not recognized in the retransmission buffer 140 and 240 must be discarded using the discard function. SDU, as they are not supported by the target Node B.
This can present a disadvantage, since the transmission side subset 130 and 230 can only update its transmission parameters and status variables after receiving an MRW_ACK from the WTRU, which can temporarily paralyze the transmission window. An advantage of this method, however, is that data loss can be minimized.
The start of the procedure can be indicated by one or a combination of the following options:
1. The procedure can be indicated by means of explicit signaling from upper layers (ie, initiate the disposal of SDU for delivery purposes).
2. The procedure can be triggered internally by the RLC when a PDU size change is detected from flexible to fixed RLC (that is, when a reconfiguration from flexible to fixed is indicated in RRC messages).
3. The procedure initiated at a given activation time for delivery purposes if a synchronized change is requested.
SDU disposal function for recognized, unrecognized and transparent mode:
Disposal for RLC reconfiguration purposes:
This alternative is only applicable for RLC recognition mode entities. It is triggered when the RLC configuration is changed from PDU size from flexible to fixed RLC. Optionally, this procedure can also be triggered if the RLC configuration is changed from a fixed size RLC PDU configuration to a flexible size RLC PDU configuration and / or if the size of the length indicator changes.
If the RLC configuration is changed from a flexible-sized RLC PDU configuration to a fixed-size RLC PDU configuration, all SDUs that contain segments or “length indicators” that indicate the end of the SDUs on AMD PDUs that have been passed down to lower layers are discarded (optionally, up to and including the latest AMD PDU), with a different size from the new AMD PDU size configured and explicit signaling is used to inform the subset of the receiving side
19/37
135 and 235.
Transmitting RLC behavior to minimize data loss:
Optionally, the behavior of the transmission side subset 130 and 230 can be modified to minimize data loss when switching from flexible PDU sizes to fixed PDU sizes. When the transmission side subset 130 and 230 is aware of switching to fixed PDU sizes, the transmission side subset 130 and 230 should start generating fixed size RLC PDUs before the activation time specified by upper layers (or that is, when switching will take place). These fixed size RLC PDUs can include all PDUs already created that have not yet been transmitted (that is, they must be regenerated according to the fixed size) and all new PDUs created from newly arrived or buffered SDUs. Alternatively, the transmission side subset 130 and 230 can continue to generate RLC PDUs with a flexible size, but change the maximum configured RLC PDU size to match the fixed RLC PDU size that will be configured when it takes place the delivery.
At the time of activation, if all PDUs in the transmission side subset 130 and 230 (including the PDUs in the retransmission buffer 140 and 240) are equal in size to the configured fixed size RLC PDUs, the transmission side subset 130 and 230 should proceed with normal operation with fixed size RLC PDUs, without discarding any PDUs. Otherwise, the transmission side subset 130 and 230 should only discard RLC PDUs that are not the same size as the configured fixed length, including the RLC PDUs that have already been transmitted.
When performing an RLC reset procedure, the procedure must be modified to consider that not all PDUs are discarded at the time of activation. When the transmission side subset 130 and 230 indicates for the receiving side subset 135 and 235 to move its receiving window (MRW indication), the PDU disposal procedure described above can be used to indicate which PDUs have been discarded.
Optionally, the procedure can be modified in such a way that the MRW indication is sent previously and the subset of the receiving side 135 and 235 just adjust its reception window at the time of activation. The time when the subset of the receiving side 135 and 235 needs to adjust its reception window can be explicitly indicated in the MRW indication or the subset of the receiving side 135 and 235 can adjust its reception window in the activation time when the transport channel must be reconfigured.
20/37
The transmission side subset 130 and 230 should be informed of the change in size from flexible PDU to fixed as soon as possible after decision making in upper layers, instead of waiting until the activation time. This allows more time before activation time to successfully transmit the remaining flexible size PDUs and limits the number of flexible size PDUs that will be discarded at the time of activation.
Method to avoid restoring RLC and minimize data loss:
This method can be used alone or in combination with one of the methods described above.
In order to minimize data loss, when changing from flexible size RLC PDUs to fixed size RLC PDUs, the transmission side subset 130 and 230 does not discard any of the flexible RLC PDUs created and transmitted. Since the normal MAC-hs or MAC-e / es will only support receipt of RLC PDUs with fixed sizes corresponding to one of a size index identifier (SID) for the DL or a data description identifier (DDI) for the UL configured for each priority row or logical channel, however, the RLC PDUs retransmitted on the normal MAC-hs or MAC-e / es need to match one of these previously defined sizes.
The padding can be used to ensure that the RLC PDUs have a valid size. At the time of changing the RLC configuration, at the time of making the delivery decision or at the given time of activation, the transmission side subset 130 and 230 can use padding to change the size of all flexible RLC PDUs (ie , with a different size from the fixed one) to be retransmitted, in such a way that they coincide with one or a combination of the following sizes:
1. a configured fixed RLC PDU size, if the flexible RLC PDU size is smaller than the fixed RLC PDU size;
2. the maximum size of the flexible RLC PDU configured before reconfiguration; the RNC must ensure that MAC-hs and / or MAC-e / es are also configured at the maximum RLC PDU size;
3. the maximum RLC PDU size present in the retransmission buffer; the RNC must ensure that MAC-hs or MAC-e / es are also configured to support receipts of this size (that is, one of the SIDs must correspond to that maximum RLC PDU size);
4. for each flexible RLC PDU, match the size with the next largest SID or DDI size configured for the MAC-hs queue to which the logical channel (MAC-d flow) also corresponds.
21/37
If the size of the RLC PDU is larger than any of the matching sizes as listed above, padding cannot be used. The WTRU may, however, dispose of them using the SDU disposal procedure as described above.
Alternatively, RLC PDUs can be segmented again to match the new fixed RLC PDU size and, if the last remaining segment is smaller than the fixed RLC PDU size (or less than the configured size to match), it can use fill.
The change from flexible size to fixed size can be flagged for the subset of the receiving side 135 and 235 or, optionally, it can be transparent for the subset of the receiving side 135 and 235 (that is, the subset of the receiving side 135 and 235 235 always operates on flexible RLC).
When adding padding, the RLC PDU length indicator field (s) may need updating to reflect changes and indicate where padding begins.
Achievements
1. Wireless communication method for reconfiguring a radio link control unit (RLC) into a wireless transmission and reception unit (WTRU), in which the method comprises:
- receiving a radio resource control (RRC) reconfiguration message that indicates that the RLC unit should be reconfigured from receiving flexible-sized RLC protocol data units (PDUs) through a lower link channel for receiving fixed-size RLC PDUs through the lower link channel, where the RLC unit comprises a subset of the transmission side and a subset of the receiving side; and
- restoration of at least the subset of the receiving side.
2. Method according to realization 1, which additionally comprises:
- if an information element (IE) “RLC reset on one side” is present in the RRC reconfiguration message, reset only on the receiving side subset; and
- if an IE “RLC reset on one side” is not present in the RRC reconfiguration message, reset of the receiving side subset and the transmission side subset.
3. Method according to any of the realizations 1 or 2, in which the subset of the receiving side is reconfigured from receiving flexible-sized RLC PDUs to receiving fixed-size RLC PDUs when the WTRU moves from a first holding cell enhanced high-speed media access control (MAC-ehs) for a second cell that does not support enhanced MAC-ehs.
22/37
4. Method according to any of the realizations 1 to 3, in which the subset of the receiving side is reconfigured from receiving flexible-sized RLC PDUs to receiving fixed-size RLC PDUs when the WTRU moves from a first holding cell Flexible-sized RLC PDUs for a second cell that does not support flexible-sized RLC PDUs.
5. Method according to any of the realizations 1 to 4, in which the subset of the receiving side is reconfigured from receiving flexible-sized RLC PDUs to receiving fixed-size RLC PDUs when an RRC connection is repositioned from a network controller in service radio (SRNC) that supports flexible-sized RLC PDUs for an SRNC that does not support flexible-sized RLC PDUs.
6. Method according to any of the realizations 1 to 5, in which the RLC reset criterion is evaluated when an information element (IE) “RLC information” is present in the RRC reconfiguration message.
7. Method according to realization 6, in which the RLC restoration criterion is evaluated on a radio carrier (RB) basis.
8. Wireless transmission and reception unit (WTRU) comprising:
- a radio link control unit (RLC) that includes a subset of the transmitting side and a subset of the receiving side: and
- a radio resource control unit (RRC) configured to receive an RRC reconfiguration message that indicates that the RLC unit should be reconfigured from receiving flexible-sized RLC protocol data units (PDUs) via a lower link channel for receiving fixed size RLC PDUs via the lower link channel, where at least the subset of the receiving side is re-established.
9. WTRU according to realization 8, in which, if an information element (IE) “RLC reset on one side” is present in the RRC reconfiguration message, only the subset of the receiving side is reset and, if an IE “reset sided RLC ”is not present in the RRC reconfiguration message, the receiving side subset and the transmission side subset are reset.
10. WTRU according to any of the realizations 8 and 9, in which the subset of the receiving side is reconfigured from receiving flexible-sized RLC PDUs to receiving fixed-size RLC PDUs when the WTRU moves from a first cell that supports control access to enhanced high-speed media (MAC-ehs) for a second cell that does not support improved MAC-ehs.
11. WTRU according to any of the realizations 8 to 10, in which the subset of the receiving side is reconfigured for receiving flexible-sized RLC PDUs for
23/37 receiving fixed-size RLC PDUs when the WTRU moves from a first cell that supports flexible-sized RLC PDUs to a second cell that does not support flexible-sized RLC PDUs.
12. WTRU according to any of the realizations 8 to 11, in which the subset of the receiving side is reconfigured from receiving flexible-sized RLC PDUs to receiving fixed-size RLC PDUs when an RRC connection is repositioned from a network controller radio in service (SRNC) that supports flexible-sized RLC PDUs for an SRNC that does not support flexible-sized RLC PDUs.
13. WTRU according to any of the realizations 8 to 12, in which the RLC reset criterion is evaluated when an information element (IE) “RLC information” is present in the RRC reconfiguration message.
14. WTRU according to realization 13, in which the RLC restoration criterion is evaluated on a radio carrier (RB) basis.
15. Wireless communication method for reconfiguring a radio link control unit (RLC) into a wireless transmission and reception unit (WTRU), in which the method comprises:
- receipt of a radio resource control (RRC) reset message indicating that the RLC unit should be configured to receive fixed size RLC protocol data units (PDUs) through a lower link channel for receiving flexible-sized RLC PDUs through the lower link channel, where the RLC unit comprises a subset of the transmission side and a subset of the receiving side; and
- determination of whether it is necessary to restore at least the subset of the receiving side.
16. Method according to realization 15, in which, if it is determined that restoration is necessary, the method additionally comprises:
- if an information element (IE) “RLC reset on one side” is present in the RRC reset message, reset only on the receiving side subset; and
- if an IE “RLC reset on one side is not present in the RRC reset message, reset the receiving side subset and the transmission side subset.
17. Method according to any of the realizations 15 and 16, in which the subset of the receiving side is reconfigured from receiving fixed-size RLC PDUs to receiving flexible-sized RLC PDUs when the WTRU moves from a first cell that does not support enhanced high-speed media access control (MAC-ehs) for a second cell that supports enhanced MAC-ehs.
24/37
18. Method according to any of the realizations 15 to 17, in which the subset of the receiving side is reconfigured from receiving fixed-size RLC PDUs to receiving flexible-sized RLC PDUs when the WTRU moves from a first cell that does not support Flexible-sized RLC PDUs for a second cell that supports flexible-sized RLC PDUs.
19. Method according to any of the realizations 15 to 18, in which the subset of the receiving side is reconfigured from receiving fixed-size RLC PDUs to receiving flexible-sized RLC PDUs when an RRC connection is repositioned from a network controller. radio in service (SRNC) that does not support flexible RLC PDUs for an SRNC that supports flexible RLC PDUs.
20. Method according to any of the achievements 15 to 19, in which RLC reset criteria are evaluated when an information element (IE) “RLC information” is present in the RRC reconfiguration message.
21. Method according to realization 20, in which the RLC restoration criterion is evaluated on a radio carrier (RB) basis.
22. Wireless transmission and reception unit (WTRU) comprising:
- a radio link control unit (RLC) that includes a subset of the transmitting side and a subset of the receiving side; and
- a radio resource control unit (RRC) configured to receive an RRC reconfiguration message that indicates that the RLC unit should be reconfigured from receiving fixed size RLC protocol data units (PDUs) via a lower link channel for receiving flexible-sized RLC PDUs through the lower link channel, in which a determination is made whether it is necessary to re-establish at least the subset of the receiving side.
23. WTRU according to realization 22, in which, if the need to reset is determined, only the subset of the receiving side is reset if an information element (IE) “RLC reset with one side” is present in the RRC reset message and the subset of the receiving side and the subset of the transmission side are reset if an IE “RLC reset on one side” is not present in the RRC reset message.
24. WTRU according to any of the realizations 22 and 23, in which the subset of the receiving side is reconfigured from receiving fixed-size RLC PDUs to receiving flexible-sized RLC PDUs when the WTRU moves from a first unsupported cell enhanced high-speed media access control (MAC-ehs) for a second cell that supports enhanced MAC-ehs.
25. WTRU according to any of the realizations 23 or 24, in which the subset of the side
Reception 25/37 is reconfigured from receiving fixed size RLC PDUs to receiving flexible size RLC PDUs when the WTRU moves from a first cell that does not support flexible size RLC PDUs to a second cell that supports Flexible size RLC PDUs.
26. WTRU according to any of the realizations 22 to 25, in which the subset of the receiving side is reconfigured from receiving fixed-size RLC PDUs to receiving flexible-sized RLC PDUs when an RRC connection is repositioned from a network controller radio in service (SRNC) that does not support flexible RLC PDUs for an SRNC that supports flexible RLC PDUs.
27. WTRU according to any of the realizations 22 to 26, in which the RLC reset criterion is evaluated when an information element (IE) “RLC information is present in the RRC reconfiguration message.
28. WTRU according to realization 27, in which the RLC restoration criterion is evaluated on a radio carrier (RB) basis.
29. Wireless communication method of performing a reconfiguration of a radio link control unit (RLC) in a wireless transmission and reception unit (WTRU), in which the method comprises:
- receipt of a radio resource control (RRC) reconfiguration message indicating that the RLC unit should be reconfigured for transmitting flexible size RLC protocol data units (PDUs) through an upper link channel for transmitting fixed size RLC PDUs through the upper link channel, wherein the RLC unit comprises a subset of the transmission side and a subset of the receiving side; and
- restoration of at least the transmission side subassembly.
30. Method according to realization 29, which additionally comprises:
- if an information element (IE) “RLC reset on one side” is present in the RRC reset message, reset only on the transmission side subset; and
- if an IE “RLC reset on one side” is not present in the RRC reset message, reset of the receiving side subset and the transmission side subset.
31. Method according to any of the embodiments 29 and 30, in which the transmission side subset is reconfigured from transmission of RLC PDUs with flexible size to transmission of RLC PDUs with fixed size when the WTRU moves from a first cell that holds PDUs flexible size RLC for a second cell that does not support flexible size RLC PDUs.
32. Method according to any of the achievements 29 to 31, in which the subset of the side
26/37 transmission is reconfigured from transmitting flexible-sized RLC PDUs to transmitting fixed-size RLC PDUs by adding a new cell that does not support flexible-sized RLC PDUs to an active set containing only cells that support flexible-sized RLC PDUs.
33. Method according to any of the realizations 29 to 32, in which the subset of the transmission side is reconfigured from the transmission of RLC PDUs with flexible size to transmission of RLC PDUs with fixed size when an RRC connection is repositioned from a network controller. radio in service (SRNC) that supports flexible-sized RLC PDUs for an SRNC that does not support flexible-sized RLC PDUs.
34. Method according to any of the achievements 29 to 33, in which the RLC restoration criterion is evaluated based on actions related to the mapping of radio bearers (RB).
35. Method according to performance 34, in which the RLC restoration criterion is evaluated on a radio carrier (RB) basis.
36. Wireless transmission and reception unit (WTRU) comprising:
- a radio link control unit (RLC) that includes a subset of the transmitting side and a subset of the receiving side; and
- a radio resource control unit (RRC) configured to receive an RRC reconfiguration message that indicates that the RLC unit should be reconfigured for transmitting RLC protocol data units (PDUs) with flexible size through an upper link channel for transmitting fixed size RLC PDUs through the upper link channel, where at least the subset of the transmission side is re-established.
37. WTRU according to any realization 36, in which, if an information element (IE) RLC reset on one side ”is present in the RRC reset message, only the subset of the transmission side is reset and, if an IE“ reset sided RLC ”is not present in the RRC reconfiguration message, the receiving side subset and the transmission side subset are reset.
38. WTRU according to any of the realizations 36 or 37, in which the transmission side subset is reconfigured from transmission of RLC PDUs with flexible size to transmission of RLC PDUs with fixed size when the WTRU moves from a first cell that holds PDUs flexible size RLC for a second cell that does not support flexible size RLC PDUs.
39. WTRU according to any of the realizations 36 to 38, in which the transmission side subset is reconfigured from the transmission of RLC PDUs with flexible size to transmission of RLC PDUs with fixed size when adding a new cell that
27/37 does not support flexible-sized RLC PDUs to an active set that contains only cells that support flexible-sized RLC PDUs.
40. WTRU according to any of the realizations 36 to 39, in which the transmission side subset is reconfigured from the transmission of RLC PDUs with flexible size to transmission of RLC PDUs with fixed size when an RRC connection is repositioned from a network controller of radio in service (SRNC) that supports flexible-sized RLC PDUs for an SRNC that does not support flexible-sized RLC PDUs.
41. WTRU according to any of the achievements 36 to 40, in which the RLC restoration criterion is evaluated based on actions related to the mapping of radio bearers (RB).
42. WTRU according to realization 41, in which the RLC restoration criterion is evaluated on a radio carrier (RB) basis.
43. Wireless communication method to perform a reconfiguration of a radio link control unit (RLC) in a wireless transmission and reception unit (WTRU), in which the method comprises:
- receipt of a radio resource control (RRC) reconfiguration message indicating that the RLC unit should be reconfigured for transmitting fixed size RLC protocol data units (PDUs) through an upper link channel for transmitting flexible-sized RLC PDUs through the upper link channel, wherein the RLC unit comprises a subset of the transmitting side and a subset of the receiving side; and
- determining whether a restoration of at least the transmission side subassembly is necessary.
44. Method according to realization 43, in which the restoration is necessary if an RLC protocol header format of headers in the RLC PDUs is changed.
45. Method according to realization 44, in which the change in the RLC protocol header format corresponds to a change in the size of a length indicator field in the headers.
46. Method according to any of the realizations 43 to 45, in which, if it is determined that a restoration is necessary, the method additionally comprises:
- if an information element (IE) “RLC reset on one side” is present in the RRC reset message, reset only on the transmission side subset; and
- if an IE “RLC reset on one side” is not present in the RRC reset message, reset of the receiving side subset and the transmission side subset.
47. Method according to any of the realizations 43 to 46, in which the subset of the side
28/37 transmission is reconfigured from transmission of fixed size RLC PDUs to transmission of flexible size RLC PDUs by adding a new cell that supports flexible size RLC PDUs to an active set and removing a cell which does not support flexible RLC PDUs from the active pool, where the final active pool contains only cells that support flexible RLC PDUs in size.
48. Method according to any of the embodiments 43 to 47, in which the transmission side subset is reconfigured from transmission of fixed size RLC PDUs to transmission of flexible size RLC PDUs when an RRC connection is repositioned from a network controller in service radio (SRNC) that does not support flexible size RLC PDUs for an SRNC that supports flexible size RLC PDUs.
49. Method according to any of the embodiments 43 to 48, in which the subset of the transmission side is reconfigured from the transmission of RLC PDUs with fixed size to the transmission of RLC PDUs with flexible size when a path over which the RLC PDUs are transmitted is changed from the inclusion of a first cell that does not support flexible RLC PDUs to the inclusion of a second cell that supports flexible RLC PDUs.
50. Method according to any of the realizations 43 to 49, in which the RLC reset criterion is evaluated when an information element (IE) “RLC information” is present in the RRC reconfiguration message.
51. Method according to realization 50, in which the RLC restoration criterion is evaluated on a radio carrier (RB) basis.
52. Wireless transmission and reception unit (WTRU) comprising:
- a radio link control unit (RLC) that includes a subset of the transmitting side and a subset of the receiving side; and
- a radio resource control unit (RRC) configured to receive an RRC reconfiguration message that indicates that the RLC unit should be reconfigured for transmitting fixed size RLC protocol data units (PDUs) via an upper link channel for transmitting flexible RLC PDUs through the upper link channel, where a determination is made as to whether a restoration of at least the subassembly of the transmission side is necessary.
53. WTRU according to realization 52, in which the restoration is necessary if an RLC protocol header format of headers in the RLC PDUs is changed.
54. WTRU according to realization 53, in which the change in the RLC protocol header format corresponds to a change in the size of a length indicator field in the headers.
29/37
55. WTRU according to any of the achievements 52 to 54, in which, if it is determined that a restoration is necessary, only the transmission side subset is reestablished if an information element (IE) “one side RLC reset” is present in the RRC reconfiguration message and the reception side subset and the transmission side subset are both reinstated if an IE “RLC reset on one side is not present in the RRC reconfiguration message.
56. WTRU according to any of the realizations 52 to 55, in which the subset of the transmission side is reconfigured from transmission of RLC PDUs with fixed size for transmission of RLC PDUs with flexible size when adding a new cell that supports RLC PDUs with flexible size to an active pool and removing a cell that does not support flexible RLC PDUs from the active pool, where the final active pool contains only cells that support flexible RLC PDUs.
57. WTRU according to any of the realizations 52 to 56, in which the transmission side subset is reconfigured from transmission of fixed size RLC PDUs to transmission of flexible size RLC PDUs when an RRC connection is repositioned from a radio network controller in service (SRNC) that does not support flexible-sized RLC PDUs for an SRNC that supports flexible-sized RLC PDUs.
58. WTRU according to any of the realizations 52 to 57, in which the transmission side subset is reconfigured from the transmission of RLC PDUs with fixed size to transmission of RLC PDUs with flexible size when a path over which the RLC PDUs are transmitted is changed from the inclusion of a first cell that does not support flexible RLC PDUs to the inclusion of a second cell that supports flexible RLC PDUs.
59. WTRU according to any of the realizations 52 to 58, in which the RLC reset criterion is evaluated when an information element (IE) “RLC information” is present in the RRC reconfiguration message.
60. WTRU according to realization 59, in which the RLC restoration criterion is evaluated on a radio carrier (RB) basis.
61. Wireless communication method of reconfiguring a radio link control unit (RLC) in a universal terrestrial radio access network (UTRAN), in which the method comprises:
- determination of the need to reconfigure the RLC unit;
- reconfiguring the RLC unit from fixed RLC protocol data unit (PDU) sizes to flexible RLC PDU sizes, wherein the RLC unit comprises a subset of the transmitting side and a subset of the receiving side; and
30/37
- restoration of at least one of the transmission side subset and the receiving side subset.
62. Method according to realization 61, in which the subset of the transmission side is reconfigured from the transmission of fixed-size RLC PDUs to the transmission of flexible-sized RLC PDUs when a path over which the RLC PDUs are transmitted is changed from the inclusion from a first cell that does not support enhanced high-speed media access control (MAC-ehs) to the inclusion of a second cell that supports enhanced MAC-ehs.
63. Method according to any of the realizations 61 and 62, in which the subset of the receiving side is reconfigured from receiving fixed-size RLC PDUs to receiving flexible-sized RLC PDUs when a path over which the RLC PDUs are received is changed from the inclusion of a first cell that does not support flexible RLC PDUs to a second cell that supports flexible RLC PDUs.
64. Method according to any of the realizations 61 to 63, which additionally comprises the transmission of a radio resource control (RRC) reconfiguration message to a wireless transmission and reception unit (WTRU) indicating that the WTRU must be reconfigured for receipt of fixed size RLC PDUs for receiving flexible size RLC PDUs.
65. Method according to realization 64, in which the RRC configuration message includes an information element (IE) “RLC reset with one side” if it is determined that a RLC reset of the receiving side subset is required by the WTRU.
66. Method according to any of the realizations 61 to 63, which additionally comprises the transmission of a radio resource control (RRC) reconfiguration message to a wireless transmission and reception unit (WTRU) indicating that the WTRU must be reconfigured for transmission of fixed size RLC PDUs for transmitting flexible size RLC PDUs.
67. Method according to realization 66, in which the RRC reconfiguration message includes an information element (IE) “RLC reset on one side” if it is determined that a RLC reset of the transmission side subset is required by the WTRU.
68. Universal terrestrial radio access network (UTRAN) comprising:
- a radio link control unit (RLC) that includes a subset of the transmitting side and a subset of the receiving side; and
- a radio resource control unit (RRC) configured to determine that reconfiguration of the RLC unit is required, reconfiguring the RLC unit from fixed RLC protocol data unit (PDU) sizes to PDU sizes
31/37 flexible RLC and restore at least one of the transmission side subset and the receiving side subset.
69. UTRAN as per realization 68, in which the subset of the transmission side is reconfigured from the transmission of RLC PDUs with fixed size to the transmission of RLC PDUs with flexible size when a path over which the RLC PDUs are transmitted is changed from the inclusion of a first cell that does not support enhanced high-speed media access control (MAC-ehs) to include a second cell that supports enhanced MAC-ehs.
70. UTRAN according to any of the realizations 68 or 69, in which the subset of the receiving side is reconfigured from receiving fixed-size RLC PDUs to receiving flexible-sized RLC PDUs when a path over which the RLC PDUs are received is changed from the inclusion of a first cell that does not support flexible RLC PDUs to a second cell that supports flexible RLC PDUs.
71. UTRAN according to any of the realizations 68 to 70, which additionally comprises a transmitter configured to send a radio resource control (RRC) reconfiguration message to a wireless transmission and reception unit (WTRU) indicating that the WTRU must be reconfigured receiving fixed-size RLC PDUs for receiving flexible-sized RLC PDUs.
72. UTRAN according to realization 71, in which the RRC reconfiguration message includes an information element (IE) "one-sided RLC reset" if it is determined that an RLC reset of the receiving side subset is required by the WTRU.
73. UTRAN according to any of the realizations 68 to 70, which additionally comprises a transmitter configured to transmit a radio resource control (RRC) reconfiguration message to a wireless transmission and reception unit (WTRU) indicating that the WTRU must be reconfigured transmission of fixed size RLC PDUs for transmission of flexible size RLC PDUs.
74. UTRAN according to realization 73, in which the RRC reconfiguration message includes an information element (IE) "RLC reset on one side" if it is determined that a RLC reset of the transmission side subset is required by the WTRU.
75. Wireless communication method to perform a reconfiguration of a radio link control unit (RLC) in a terrestrial radio access network (UTRAN), in which the method comprises:
- determination of the need to reconfigure the RLC unit;
- reconfiguration of the RLC unit from flexible RLC protocol data unit (PDU) sizes to fixed RLC PDU sizes, where the RLC unit
32/37 comprises a subset of the transmission side and a subset of the receiving side; and
- restoration of at least one of the transmission side subset and the receiving side subset.
76. Method according to realization 75, in which the RLC unit is reconfigured from the transmission of RLC PDUs with flexible size to transmission of RLC PDUs with fixed size when a path over which the RLC PDUs are transmitted is changed from the inclusion of a first cell that supports enhanced high-speed media access control (MAC-ehs) for the inclusion of a second cell that does not support enhanced MAC-ehs.
77. Method according to any of the 75 or 76 embodiments, in which the RLC unit is reconfigured from flexible-sized RLC PDUs to fixed-size RLC PDUs when the WTRU moves from a first cell holding flexible-sized RLC PDUs to a second cell that does not support flexible-sized RLC PDUs.
78. Method according to any of the realizations 75 to 77, in which the RLC unit is reconfigured from RLC PDUs with flexible size to RLC PDUs with fixed size when an RRC connection is repositioned from an in-service radio network controller (SRNC) which supports flexible-sized RLC PDUs for an SRNC that does not support flexible-sized RLC PDUs.
79. Method according to any of the achievements 75 to 78, which additionally comprises the transmission of a radio resource control (RRC) reconfiguration message to a wireless transmission and reception unit (WTRU) indicating that the WTRU must be reconfigured for receipt of flexible-sized RLC PDUs for receiving fixed-size RLC PDUs.
80. Method according to realization 79, in which the RRC reconfiguration message includes an information element (IE) “RLC restoration with one side”.
81. Method according to any of the realizations 75 to 78, which additionally comprises the transmission of a radio resource control (RRC) reconfiguration message to a wireless transmission and reception unit (WTRU) indicating that the WTRU must be reconfigured for transmission of flexible-sized RLC PDUs for transmitting fixed-size RLC PDUs.
82. Method according to realization 81, in which the RRC reconfiguration message includes an information element (IE) “RLC restoration on one side”.
83. Universal terrestrial radio access network (UTRAN) comprising:
- a radio link control unit (RLC) that includes a subset of the transmitting side and a subset of the receiving side; and
- a radio resource control unit (RRC) configured to determine that it is
33/37 reconfiguration of the RLC unit, reconfiguring the RLC unit from flexible RLC protocol data unit (PDU) sizes to fixed RLC PDU sizes and re-establishing at least one of the transmission side subset and the subset of the receiving side.
84. UTRAN according to realization 83, in which the RLC unit is reconfigured from the transmission of RLC PDUs with flexible size to transmission of RLC PDUs with fixed size when a path over which the RLC PDUs are transmitted is changed to include a first cell that supports enhanced high-speed media access control (MAC-ehs) for inclusion of a second cell that does not support enhanced MAC-ehs.
85. UTRAN according to any of the 83 or 84 realizations, in which the RLC unit is reconfigured from flexible-sized RLC PDUs to fixed-size RLC PDUs when the WTRU moves from a first cell that supports flexible-sized RLC PDUs to a second cell that does not support flexible-sized RLC PDUs.
86. UTRAN according to any of the realizations 83 to 85, in which the RLC unit is reconfigured from flexible-sized RLC PDUs to fixed-size RLC PDUs when an RRC connection is repositioned from an in-service radio network controller (SRNC) which supports flexible-sized RLC PDUs for an SRNC that does not support flexible-sized RLC PDUs.
87. UTRAN according to any of the realizations 83 to 86, which additionally comprises a transmitter configured to send a radio resource control (RRC) reconfiguration message to a wireless transmission and reception unit (WTRU) indicating that the WTRU must be reconfigured receiving flexible-sized RLC PDUs for receiving fixed-size RLC PDUs.
88. UTRAN according to realization 87, in which the RRC reconfiguration message includes an information element (IE) “RLC restoration on one side”.
89. UTRAN according to any of the realizations 83 to 86, which additionally comprises a transmitter configured to send a radio resource control (RRC) reconfiguration message to a wireless transmission and reception unit (WTRU) indicating that the WTRU must be reconfigured transmission of flexible-sized RLC PDUs for transmission of fixed-size RLC PDUs.
90. UTRAN according to realization 89, in which the RRC reconfiguration message includes an information element (IE) “RLC restoration on one side.
91. Wireless communication method to perform a reconfiguration of a radio link control unit (RLC) in a wireless transmission and reception unit (WTRU), in which the method comprises:
- RLC unit reconfiguration of protocol data unit sizes
34/37 flexible RLC (PDU) for fixed RLC PDU sizes, wherein the RLC unit comprises a subset of the transmitting side and a subset of the receiving side; and
- dispose by the transmission side subset of flexible-sized RLC PDUs.
92. Method according to realization 91, which additionally comprises the transmission of a message indicating the discarded flexible RLC PDUs.
93. Method according to realization 92, in which the message additionally indicates RLC service data units (SDUs) corresponding to the discarded flexible size RLC PDUs.
94. Method according to any of the realizations 92 or 93, in which the message includes a super field (SUFI) of motion reception window (MRW) to indicate the discarded RLC PDUs.
95. Method according to realization 94, in which the MRW SUFI indicates the sequence number (SN) of a last RLC PDU or RLC SDU that is discarded.
96. Method according to any of the realizations 91 to 95, in which any RLC PDU with a size different from the length of the fixed size RLC PDUs is discarded.
97. Method according to any of the realizations 91 to 95, in which any RLC PDU with a size different from the length of fixed size RLC PDUs that have already been transmitted at least once is discarded.
98. Method according to any of the realizations 91 to 95, in which all RLC PDUs with a sequence number (SN) up to the last RLC PDU with flexible RLC PDU size, or an RLC PDU size different from the length of one Fixed RLC PDUs are even discarded.
99. Method according to any of the realizations 91 to 95, in which all RLC PDUs with a sequence number (SN) until the last RLC PDU with a flexible RLC PDU size, or an RLC PDU size different from the length of a fixed RLC PDU that has been transmitted at least once, are discarded.
100. Method according to any of the realizations 91 to 95, in which all RLC service data units (SDUs) up to the last SDU contained in the last RLC PDU with a flexible RLC PDU size, or a different RLC PDU size of the fixed RLC PDU length, are discarded.
101. Method according to any of the realizations 91 to 95, in which all RLC SDUs for which at least one segment was contained in an RLC PDU with a different size than a fixed size RLC PDU that was transmitted at least once are discarded .
102. Method according to any of the realizations 91 to 95, in which all RLC PDUs
35/37 in a retransmission buffer that were transmitted to lower layers and given an assigned sequence number (SN) are discarded.
103. Method according to any of the realizations 91 to 102, in which data loss is minimized through the creation and transmission of fixed-size RLC PDUs when making a delivery decision.
104. Method according to any of the realizations 91 to 103, in which the subset of the transmission side discards flexible-sized RLC PDUs in response to the explicit signaling of upper layers.
105. Wireless communication method to perform a reconfiguration of a radio link control unit (RLC) in a wireless transmission and reception unit (WTRU), in which the method comprises:
- receipt of a message from upper layers indicating an activation time; and
- before the activation time, reconfiguration of the RLC unit for generation of flexible size RLC protocol data units (PDUs) for generation of fixed size RLC PDUs.
106. Method according to realization 105, which additionally includes the regeneration, according to a fixed size, of all PDUs that have been created, but that have not yet been transmitted.
107. Method according to realization 105, which additionally comprises the regeneration, according to a fixed size, of all new PDUs that have been created from buffered or newly arrived service data units (SDUs).
108. Method according to any of the embodiments 105 to 107, in which a delivery takes place during the activation time.
109. Method according to realization 106, in which the remaining RLC PDUs with flexible size are discarded.
110. Wireless communication method to perform a reconfiguration of a radio link control unit (RLC) in a wireless transmission and reception unit (WTRU), in which the method comprises:
- generation by the RLC unit of RLC protocol data units (PDUs) with flexible size;
- receiving a message from upper layers indicating an activation time;
- before the activation time, changing a maximum configured RLC PDU size associated with flexible RLC PDUs to match a fixed RLC PDU size; and
- at activation time, reconfiguration of the RLC unit for generation of RLC protocol data units (PDUs) with flexible size for generation of RLC PDUs
36/37 with fixed size.
111. Method according to realization 110, in which a delivery takes place at the time of activation.
112. Wireless communication method to perform a reconfiguration of a radio link control unit (RLC) in a wireless transmission and reception unit (WTRU), in which the method comprises:
- reconfiguration of the RLC unit of transmission of RLC PDUs with flexible size for transmission of RLC PDUs that have a size selected from a previously defined set of RLC PDU sizes; and
- changing the size of RLC PDUs with flexible size for retransmission to match a specific size in the previously defined set of RLC PDU sizes.
113. Method according to realization 112, in which the filling of the RLC PDUs with flexible size is carried out to match the specific size.
114. Method according to realization 113, in which the flexible RLC PDUs are filled to the next highest available size in the previously defined set.
115. Method according to realization 114, in which a flexible RLC PDU with a size higher than the maximum size of the RLC PDU sizes in the previously defined set is discarded.
116. Method according to realization 112, in which all RLC PDUs with flexible sizes that have not been transmitted or presented to lower layers are regenerated for framing in RLC PDUs with fixed size.
117. Wireless communication method to perform a reconfiguration of a radio link control unit (RLC) in a universal terrestrial radio access network (UTRAN), in which the method comprises:
- reconfiguration of the RLC unit of transmission of RLC PDUs with flexible size for transmission of RLC PDUs that have a size selected from a previously defined set of RLC PDU sizes; and
- changing the size of RLC PDUs with flexible size to be retransmitted to match a specific size in the previously defined set of RLC PDU sizes.
118. Method according to realization 117, in which the filling of the RLC PDUs with flexible size is carried out in order to match the specific size.
119. Method according to realization 118, in which the flexible RLC PDUs are filled to the next highest size available in the previously defined set.
120. Method according to realization 119, in which a flexible size RLC PDU
37/37 with size higher than the maximum size among the RLC PDU sizes in the previously defined set is discarded.
121. Method according to realization 117, in which all flexible size RLC PDUs that have not been transmitted or submitted to lower layers are regenerated to fit fixed size RLC PDUs.
Although the characteristics and elements are described in specific combinations, each characteristic or element can be used alone, without the other characteristics and elements or in various combinations with or without the other characteristics and elements. The methods or flowcharts provided herein may be implemented in a computer program, software or firmware tangibly incorporated into a computer-readable storage medium for execution by a general purpose computer or processor. Examples of computer-readable storage media include read-only memory (ROM), random access memory (RAM), registry, cache memory, semiconductor memory devices, magnetic media such as internal hard drives and removable disks, magnetic media optical and optical media such as CDROM discs and digital versatile discs (DVDs).
Suitable processors include, for example, a general purpose processor, special purpose processor, conventional processor, digital signal processor (DSP), a series of microprocessors, one or more microprocessors in association with a DSP core, controller, microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Portal Sets (FPGAs), any other type of integrated circuit (IC) and / or state machine.
A processor in association with software can be used to implement a radio frequency transceiver for use in a wireless transmission and reception unit (WTRU), user equipment (UE), terminal, base station, radio network controller (RNC) ) or any host computer. The WTRU can be used in conjunction with modules, implemented in hardware and / or software, such as a camera, video camera module, videophone, headset, vibrating device, speaker, microphone, television transceiver, headset handsfree headset, keyboard, Bluetooth® module, frequency modulated radio (FM) unit, liquid crystal display (LCD) unit, organic light-emitting diode (OLED) unit, digital music device, media player, video game module, Internet browser and / or any wireless local area network (WLAN) module.
1/2
1 sheet
Sheet 1
120 members in 18 offices
Priority claims7
| Document | Office | Kind | Date |
|---|---|---|---|
| 60895338 | United States of America | – | |
| 89533807 | United States of America | P | |
| 60908076 | United States of America | – | |
| 90807607 | United States of America | P | |
| 60914189 | United States of America | – | |
| 91418907 | United States of America | P | |
| 2008003336 | United States of America | W |
Members120
| Document | Office | Kind | |
|---|---|---|---|
| TWM335886U | Taiwan Province of China | U | |
| US2008188224A1 | United States of America | A1 | |
| AU2008214411A1 | Australia | A1 | |
| CA2677223A1 | Canada | A1 | |
| WO2008097486A2 | World Intellectual Property Organization (WIPO) | A2 | |
| TW200836538A | Taiwan Province of China | A | |
| TWM339861U | Taiwan Province of China | U | |
| US2008227442A1 | United States of America | A1 | |
| AU2008227111A1 | Australia | A1 | |
| CA2681020A1 | Canada | A1 | |
| WO2008115392A2 | World Intellectual Property Organization (WIPO) | A2 | |
| TW200841758A | Taiwan Province of China | A | |
| WO2008115392A3 | World Intellectual Property Organization (WIPO) | A3 | |
| CN201204594Y | China | Y | |
| CN201219297Y | China | Y | |
| WO2008097486A3 | World Intellectual Property Organization (WIPO) | A3 | |
| AR065161A1 | Argentina | A1 | |
| MX2009008193A | Mexico | A | |
| AR067209A1 | Argentina | A1 | |
| KR20090115194A | Republic of Korea | A | |
| KR20090118070A | Republic of Korea | A | |
| MX2009009893A | Mexico | A | |
| EP2127403A2 | European Patent Office (EPO) | A2 | |
| KR20090130378A | Republic of Korea | A | |
| EP2140632A2 | European Patent Office (EPO) | A2 | |
| CN101641914A | China | A | |
| KR20100015833A | Republic of Korea | A | |
| CN101675683A | China | A | |
| IL200185A0 | Israel | A0 | |
| IL200185D0 | Israel | D0 | |
| IL200979A0 | Israel | A0 | |
| IL200979D0 | Israel | D0 | |
| JP2010518695A | Japan | A | |
| JP2010521920A | Japan | A | |
| HK1139258A | Hong Kong, China | A | |
| HK1139258A1 | Hong Kong, China | A1 | |
| RU2009132930A | Russian Federation | A | |
| RU2009138222A | Russian Federation | A | |
| AU2008227111B2 | Australia | B2 | |
| BRPI0806351A2 | Brazil | A2 | |
| AU2008214411B2 | Australia | B2 | |
| KR101115107B1 | Republic of Korea | B1 | |
| US2012051325A1 | United States of America | A1 | |
| US8130706B2 | United States of America | B2 | |
| TW201212607A | Taiwan Province of China | A | |
| JP4903273B2 | Japan | B2 | |
| RU2447595C2 | Russian Federation | C2 | |
| RU2448437C2 | Russian Federation | C2 | |
| JP2012105329A | Japan | A | |
| US2012147835A1 | United States of America | A1 | |
| JP4997294B2 | Japan | B2 | |
| KR101172129B1 | Republic of Korea | B1 | |
| KR20120093291A | Republic of Korea | A | |
| JP2012199954A | Japan | A | |
| TW201244522A | Taiwan Province of China | A | |
| US8320327B2 | United States of America | B2 | |
| CN101641914B | China | B | |
| IL200185A | Israel | A | |
| CN103024833A | China | A | |
| CN101675683B | China | B | |
| KR20130044358A | Republic of Korea | A | |
| CN103220733A | China | A | |
| MY149326A | Malaysia | A | |
| JP5302442B2 | Japan | B2 | |
| JP2013214998A | Japan | A | |
| KR20130122805A | Republic of Korea | A | |
| HK1184008A | Hong Kong, China | A | |
| HK1184008A1 | Hong Kong, China | A1 | |
| KR20140007978A | Republic of Korea | A | |
| KR20140046075A | Republic of Korea | A | |
| US8705406B2 | United States of America | B2 | |
| US8705489B2 | United States of America | B2 | |
| US2014177593A1 | United States of America | A1 | |
| US2014185583A1 | United States of America | A1 | |
| BRPI0808321A2This record | Brazil | A2 | |
| KR101421200B1 | Republic of Korea | B1 | |
| JP5555360B2 | Japan | B2 | |
| JP5559820B2 | Japan | B2 | |
| KR101420895B1 | Republic of Korea | B1 | |
| KR20140094033A | Republic of Korea | A | |
| JP2014180045A | Japan | A | |
| KR20140114906A | Republic of Korea | A | |
| TW201438506A | Taiwan Province of China | A | |
| JP2014197880A | Japan | A | |
| TWI459838B | Taiwan Province of China | B | |
| KR101461293B1 | Republic of Korea | B1 | |
| TWI462626B | Taiwan Province of China | B | |
| IL200979A | Israel | A | |
| TWI467994B | Taiwan Province of China | B | |
| KR20150005722A | Republic of Korea | A | |
| KR101483258B1 | Republic of Korea | B1 | |
| TW201507420A | Taiwan Province of China | A | |
| KR101494727B1 | Republic of Korea | B1 | |
| KR20150020733A | Republic of Korea | A | |
| JP5702488B2 | Japan | B2 | |
| CA2681020C | Canada | C | |
| JP2015119506A | Japan | A | |
| TWI493947B | Taiwan Province of China | B | |
| US9167489B2 | United States of America | B2 | |
| CN103024833B | China | B |
6 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]GrantedPRAZO DE VALIDADE: 10 (DEZ) ANOS CONTADOS A PARTIR DE 13/10/2020, OBSERVADAS AS CONDICOES LEGAIS.B16A | B16A | |
| Decision: intention to grant [chapter 9.1 patent gazette]B09A | B09A | |
| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]B06U | B06U | |
| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]B06F | B06F | |
| Others concerning applications: alteration of classificationB15K | B15K | |
| Requested change of headquarter approvedB25G | B25G |
Numbers
- Publication
- PI0808321
- Application
- 8083215
Titles2
- Portuguese
- MÉTODO E APARELHO DE COMUNICAÇÃO SEM FIO PARA SUUSTENTAR RECONFIGURAÇÃO DE PARÂMETROS DE CONTROLE DE LINKS DE RADIO.
- English
- WIRELESS COMMUNICATION METHOD AND APPARATUS TO SUPPORT RADIO LINK CONTROL PARAMETER RECONFIGURATION.
Classification
- CPC, 10
- H04L1/1877
- H04W36/0055
- H04L1/0007
- H04L47/365
- H04L47/70
- H04W76/19
- H04W72/12
- H04W36/249
- H04W76/22
- H04L1/1874
- IPC, 6
- H04L12 56
- H04L47 36
- H04L47 70
- H04W36 10
- H04W36 14
- H04W72 12
