Handover failure handling

(54) Title: RADIO LINK FAILURE TO HANDLE AND (57) Summary: DELIVERY.

(30) Unionist priority: 23/04/2007 us 60 / 913,316,

06/18/2007 US 60 / 944,542, 06/18/2007 US 60 / 944,542, 04/23/2007

US 60 / 913,316 (73) Holder (s): interdigital Technology Corporation (72) Inventor (s): JAMES M. MILLER, Mohammed Sammour, SHANKAR SOMASUNDARAM, Slephen E. Terry (74) Attorney (s): ADVOCACIA PIETRO ARIBONI S / C (86) International Order: pct USO8O612O8 of 23/04/2008 (87) International Publication: wo 2oos / i3i4oide 10/30/2008

<img file="BRPI0809739A2_D0001.tif" />

500

501

502

503

1/15

Handling of delivery failures and radio links.

FIELD OF THE INVENTION

This application relates to wireless communication systems.

BACKGROUND

In Step 2 of the evolved universal terrestrial radio access network (E-UTRAN), the cases in which the wireless transmission and reception unit (WTRU) selects a cell that belongs to the same eNode B after a radio link failure ( RL) are listed for further study (FFS). It was proposed that if the WTRU selects a cell other than the same eNode B, the activity cannot be resumed without interaction between the WTRU and eNode B. Currently, the radio access network 2 (RAN2) specifies that, if the WTRU selects a cell from a different eNode B, it needs to go to rest through radio resource control (RRC).

Currently, RAN2 decisions about RL failure are determined based on two phases. The two phases govern the behavior associated with RL failures and are shown in Figure 1.

A first phase starts when a radio problem is detected, which generates an RL failure detection. As a result, there is no mobility based on WTRU based on a timer or other criteria (such as counting) (T ^.

A second phase begins when a radio link failure is detected, which generates RRC_ldle. WTRU-based mobility is still available, which is timer-based (T₂).

Table 1 below describes how mobility is currently handled with respect to an RL failure.

Table 1

Mobility and Failure of Radio Links

<td>Cases</td><td>First phase</td><td>Second level</td><td>T2 expired</td>

<td>EU returns to the same cell</td><td>Proceed as if did not occur no problem radio</td><td>The activity does not can be resumed no interaction between the UE and the eNode B. The procedure to be used is FFS, not usually via RRCJDLE</td><td>Go via RRCJDLE</td>

<td>EU selects one cell other than</td><td>AT</td><td>FFS</td><td>Go via RRCJDLE</td>

2/15

<td>same eNode B</td><td></td><td></td><td></td>

<td>EU selects one cell of an eNode B different</td><td>AT</td><td>Go via RRCJDLE</td><td>Go via RRCJDLE</td>

A recent proposal divides delivery into 2 (two) phases similar to RL failure and suggests a procedure for handling delivery failure.

In the first phase, the WTRU tries to synchronize and access the target cell, such as during a T1 timer. In the second phase, the WTRU aborted the delivery, as it failed, and tries to reestablish the lost connection to the network, such as during a T2 timer. After the second phase, the UE enters RRC_IDLE.

Figure 2 shows the two phases that govern the behavior associated with delivery failure during mobility controlled by the network according to the current proposal.

The first phase begins with a first attempt to synchronize to a target cell; and generates a non-delivery detection. During this period, there is no mobility based on WTRU, which is based on a timer or other criterion (such as counting) (Ti).

The second phase begins with detection of delivery failure, which generates RRC_IDLE. WTRU-based mobility is still available based on the Timer (T₂).

Table 2 describes how mobility is handled with respect to a delivery failure.

Table 2

<td colspan="4">Delivery and Mobility Failure</td>

<td>Cases</td><td>First phase</td><td>Second level</td><td>T2 expired</td>

<td>EU enters the cell target</td><td>It continues as if did not occur radio problems</td><td>The activity can be resumed without interaction between the EU and eNode Β, the EU performs procedure random access according to 10.1.5.</td><td>Go via RRCJDLE</td>

<td>UE returns to cell source</td><td>AT</td><td>The activity does not can be resumed no interaction between the UE and the eNode Β, the</td><td>Go via RRCJDLE</td>

3/15

<td></td><td></td><td>EU carries out the Procedure Random Access according to 10.1.5</td><td></td>

<td>EU selects one cell other than target cell or source</td><td>AT</td><td>Go via RRCJDLE</td><td>Go via RRCJDLE</td>

In addition, it is currently allowed to use random access not based on contention during delivery. In this way, the random access procedure not based on current contention, shown in Figure 3, includes the assignment of a Preamble of Random Access through dedicated signaling on the lower link (DL), in which eNode B assigns a WTRU a Preamble of Random Access without contention with 6 (six) bits (that is, a Preamble of Random Access that is not within the set transmitted in BCH). The preamble is signaled by means of a delivery command (HO) generated by a target eNode B and sent by the source eNode B for delivery, using media access control (MAC) signaling (such as layer 1 control channel ( L1) / layer 2 (L2) or MAC control packet data unit (PDU)) in case of DL data arrival.

The WTRU then transmits the Preamble of Random Access without contention assigned in the RACH on the upper link. An eNB Random Access Response is sent over DL-SCH. The response is almost synchronous (in a flexible window whose size is one or more transmission time intervals (TTI)) with message 1 and is addressed to C-RNTI or RA-RNTI (FFS) in control channel L1 / L2 .

The WTRU then transmits the Preamble of Random Access without contention assigned in the RACH at the top link. An eNB Random Access Response is sent on the DL-SCH. The response is almost synchronous (within a flexible window whose size is one or more transmission time intervals (TTI)) with message 1 and is addressed to C-RNTI or RA-RNTI (FFS) on the control channel L1 / L2.

The Random Access Response includes at least time alignment information, an initial UL grant for delivery, and time alignment information for arrival of DL data. In addition, the RA preamble identifier is addressed to the temporary routing area radio network identifier (RA-RNTI) on the L1 / L2 control channel.

The response is intended for only one WTRU in a lower link shared channel message (DL-SCH) if it is addressed to the cell's RNTI (C-RNTI) on the L1 / L2 control channel or one or more WTRUs on a

4/15 DL-SCH message if RA-RNTI is addressed on the L1 / L2 control channel.

There is a need for an improved method and apparatus for handling delivery failures and radio links.

SUMMARY OF THE INVENTION

The method and apparatus described are used to handle RL and delivery failures based on details of context transfer and RACH procedures that improve failure delivery procedures. After an RL failure, a wireless transmission and reception unit (WTRU) includes the identity of an evolved Node B (eNB) and / or cell as an information element (IE) in an RRC connection request and / or a cell update message or any other RRC message along with a WTRU identity.

BRIEF DESCRIPTION OF THE FIGURES

A more detailed understanding can be obtained from the following description, provided as an example in conjunction with the attached figures, in which;

- Figure 1 shows a conventional radio link failure;

- Figure 2 shows a conventional delivery failure;

- Figure 3 shows a random access procedure not based on conventional containment;

Figure 4 is a diagram of a wireless communication system; and

- Figure 5 shows a flow chart of a described method of handling a radio link failure.

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, assistant personal digital device (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.

Referring to Figure 4, an LTE wireless communication network (NW), for example, comprises one or more WTRUs 20, each of which includes a processor 21, one or more B 30 Nodes, each of which includes a processor 31, and one or more cells 40. Each cell 40 comprises one or more B Nodes (NB or eNB) 30. Each of processors 21 and 31 is configured to implement a described method of handling a delivery failure and radio link (RL).

Throughout the method described, information about

5/15 context designates any one of the Radio Resource Control (RRC) context, security context, Packet Data Convergence Protocol (PDCP) context or any layer context that may proceed during mobility. For the sake of brevity, however, the expression context or context of RRC can be used for each of the types of context described above.

When an RL failure is detected by the WTRU 20, the WTRU 20 initiates mobility procedures (ie, new cell selection). In the normal cell selection procedure, the WTRU 20 reselects any available cell after the RL failure and, by means of a cell update or radio resource control (RRC) connection request, the WTRU 20 sends its identity of WTRU to an eNode B (eNB) 30. ENB 30, using the received WTRU identity, detects whether WTRU 20 was under the control of that eNB 30 before the radio link failure occurred.

A method and apparatus are described in which, after a delivery failure (HO) or radio link (RL), the WTRU 20 includes its WTRU identity (such as TMSI / IMSI / IMEI or any other EU identity) and the eNB identity and / or cell identity as an information element (IE) in the RRC connection request, the cell update message or any other RRC message.

After the WTRU 20 takes shelter over an eNB (ie target eNB) after the new cell selection, the information included in the IE is transmitted to the target eNB. If the target eNB in ​​which the WTRU 20 is housed is different from the eNB for which the WTRU 20 was housed before the RL failure (ie source eNB), the target eNB contacts the source eNB, using the eNB identity and / or cell ID included in the IE, to inform the source eNB of the identity of the WTRU 20. The target eNB then requests the source eNB to transmit context parameters from the WTRU 20. Alternatively, the target eNB can also inform the source eNB of the cell identity.

If the source eNB finds context information that matches the identity of the WTRU 20, the source eNB transmits the context information to the target eNB. The target eNB can then send a response to the cellular update of the WTRU 20, the RRC connection request or any other RRC procedure initiated by WTRU, which indicates that the WTRU 20 can reuse the previous context.

If the context is not found by the source eNB, the target eNB performs procedures for cell update / establishment of RRC connections or any other RRC procedure. In this case, when the target eNB receives a request to reestablish an RRC connection via WTRU 20, it signals all the parameters of Layer 1 and / or Layer 2/3 that would have signaled for a new RRC connection. The WTRU 20 can then delete any context information

6/15 stored that was applicable to the old cell. Alternatively, if the context is not found, WTRU 20 can enter RRC Idle without waiting for timer T2 to end and resume procedures or wait for timer t2 to end in RRC Idle.

Descrito described IE, which comprises information about the eNB in ​​which the WTRU 20 last housed can be included by the WTRU 20. According to this alternative, processor 21 includes the eNB identity and / or cellular identity in the IE only upon detection of a delivery failure.

If the target eNB, in which the WTRU 20 is housed, is the same source eNB before the failure and if the eNB finds a context for the WTRU 20 (eNB finds out by checking that it has a context that matches the identity of the WTRU 20), eNB, upon receipt of a WTRU 20 RRC CONNECTION REQUEST (or upon receipt of any other RRC procedure initiated by WTRU), you can tell WTRU 20 to use the same context information you had before the failure occurred. Otherwise, eNB will be able to signal all Layer 1 and Layer 2/3 parameters to WTRU 20 that eNB would signal for a new RRC connection. The WTRU 20 can then delete any stored context information.

A flow chart of the described method used by processor 21 of WTRU 20 to handle an RL failure is described below. Upon detection of an RL failure (step 500), WTRU 20 conducts an initial access procedure to obtain access to a selected target eNB (step 501). The WTRU 20 then transmits an IE to the target eNB that includes at least the eNB ID for a source eNB on which the WTRU 20 housed previously (step 502). The WTRU 20 then receives the RRC context of the target eNB (step 503) after obtaining the context by the target eNB, such as from the source eNB.

According to the method described, the length of the period in which the target eNB maintains the context of radio access control (RAC) is preferably determined based on implementation. This is also the case in determining whether the transfer of context information between the target eNB and the source eNB occurs only on a radio link failure.

If the target eNB in ​​which the WTRU 20 takes shelter is the same source eNB in ​​which the WTRU 20 had taken shelter before delivery, upon receipt of a WTRU 20 RRC CONNECTION REQUEST or receipt of any other RRC initiated by WTRU, may indicate to WTRU 20 that it uses the same context information that it had before the failure occurred.

7/15

As experts in the field will understand, the shelter of WTRU 20 in the same cell or the same eNB in ​​which it housed itself before the RL failure helps to save network resources. Thus, the described method may alternatively include that the WTRU 20 during the cell selection procedure after the RL failure considers the identity of the source eNB, in order to prefer cells from the source eNB over cells of a different eNB. According to this alternative, it may be preferable for WTRU 20 to give priority to an eNB detected in the following order: the last cell in which it was previously housed; a cell of the same eNode B in which it was previously housed; and the cell of any other eNode B.

The other parameters of new cell selection may or may not be considered by the WTRU 20 during a radio link failure situation, as the quick shelter and start of the call are the main criteria after the failure; having only the eNB identity (or cell identity), together with the cell's signal strength, is sufficient to conduct cell selection through radio link failure. According to this method, the identities (eNB and cell) can be transmitted in the system information messages together with the cell ID.

For a delivery failure, a method is described in which, when the WTRU 20 moves to a different cell and the different cell belongs to the same eNB, based on the identity of the WTRU 20, the eNB to which the WTRU 20 moved -if it identifies if it has the context of WTRU 20. If eNB has the context, eNB signals to WTRU 20 that it uses the same context as above. The WTRU 20 is capable of using the same context, as the context is stored with respect to eNB and not with respect to the cell. Under this method, the same cell selection priority described above for an RL failure described above applies to eNB delivery failures, as an alternative method.

When the WTRU 20 moves to a cell of a different eNB, a procedure similar to that described above can be used for a radio link failure. It should be noted that, during this delivery procedure, the last eNB identity that the WTRU 20 may have stored may be the source eNB or the target eNB, depending on which stage of the procedure the delivery has failed. According to this described method, it is preferable that the WTRU 20 stores the source eNB as the last eNB in ​​which it was housed until the successful completion of delivery. In addition, the procedure itself would not be affected, regardless of whether the WTRU sends the identity of the source eNB or target eNB to the final eNB in ​​which it is housed.

An important aspect of being able to recover the context is that the WTRU is housed in a cell and sends message 1 (ie the Preamble of Random Access) in the RACH procedure as soon as possible. If there is a delay in this process, eNB may have excluded the context, in order to render the

8/15 context recovery procedure. Consequently, a method of improving the Random Access Channel (RACH) procedure for delivery and RL failures is described. According to this method, a dedicated subscription is allocated to WTRU 20 during the delivery procedure. The allocated dedicated signature is then used to access the source cell after RL or delivery failure. The HO command, for example (or any signaling message), assigns WTRU 20 two dedicated signatures, one to be used by WTRU 20 to access the target cell and the other to be used by WTRU 20 to access the source cell (or any other cell) in case of failure (such as if WTRU 20 does not manage access to the target cell).

If the delivery is successfully terminated, WTRU 20 may (implicitly or explicitly) release the subscription back to the network in the delivery confirmation message. In the event of a failure during the delivery procedure, WTRU 20 can use this second dedicated subscription and try to access the network as soon as possible. As the WTRU 20 uses a dedicated signature, it is able to recover more quickly from a failure.

Alternatively, a set of dedicated signatures is transmitted on the broadcast channel (BCH) defined exclusively for RL failure, which is used by WTRU 20 in the event of a delivery failure or RL. In another alternative, a set of dedicated universal signatures, valid across all cells, can be used for RL failures. This set of universal dedicated signatures can be sent in the delivery message or transmitted in the system information messages. The WTRU can then use that universal dedicated signature after the failure to access any cell.

An alternative RACH procedure is described in which, instead of assigning a dedicated signature to the WTRU 20, which is used in the event of failure, at least one of the signatures (such as Preamble of Random Access) in the current set transmitted in the BCH can be identified / reserved for access to the cell after the failure. According to this alternative, the WTRU 20 obtains the reserved subscriptions from the BCH (or the Delivery Command (HO) can inform the WTRU 20 the reserved subscriptions to be used in case of failure). After the WTRU 20 learns the reserved subscriptions, the WTRU 20 uses this reserved subscription if it experiences a delivery failure or RL.

Another alternative is described in which higher access classes are used to handle RL failures. According to this alternative, WTRU 20 associates the handling of RL failures with a higher access class service and, in this way, would end up selecting again for the network with a lower setback and higher priority. In this scenario, when WTRU 20 tries to access a cell after an RL failure, as WTRU 20 would have a service

9/15 higher access class and therefore would attempt to access network 10 with less or no backslide between its different RACH attempts. In this way, WTRU 20 after an RL failure may have a higher probability of accessing the network compared to other WTRUs with lower service and access class, which would generate longer backward intervals.

In another alternative method of accessing RACH, the

WTRU 20 raises its power more quickly so that the network has a higher possibility of detection and, therefore, prioritize the given WTRU 20. Table 3 describes the mobility of WTRU 20 during an RL failure according to this described method.

Table 3

Mobility and Failure of Radio Links

<td>Cases</td><td>First phase</td><td>Second level</td><td>T2 expired</td><td>Priority cell selection</td>

<td>EU returns for the same cell</td><td>Continue as if no there were occurred problems of radio</td><td>The activity does not Can be resumed without interaction between the WTRU and the eNode B, the procedure to be used is FFS, normally not through RRCJDLE</td><td>Go via RRCJDLE</td><td> 1</td>

<td>EU selects a cell different from same eNode B</td><td>AT</td><td>The activity does not Can be resumed without interaction between the WTRU and the eNode B.</td><td>Go via RRCJDLE</td><td> 2</td>

<td>EU selects a cell of an eNode B different</td><td>AT</td><td>The activity does not Can be resumed without interaction between the WTRU and the</td><td>Go via RRCJDLE</td><td> 3</td>

10/15

<td></td><td></td><td>eNode Β, the procedure to be used is FFS, normally didn't see RRCJDLE</td><td></td><td></td>

For the second phase, in order to resume activity when WTRU 20 returns to the same cell, or when WTRU 20 selects a different cell from the same eNode B or a different eNB, a method in which WTRU 20 has access is described to the cell via the random access procedure. The non-access layer identity (NAS) used in the random access process is also used by eNB to determine whether eNB has a stored RRC context for that WTRU 20. If eNB finds a RRC context that matches the identity of the WTRU 20, eNB sends, in response to the RRC CONNECTION REQUEST, a message (such as RRC CONNECTION RESPONSE) or any other RC procedure initiated by WTRU , which tells WTRU 20 to reuse the RRC context it has stored.

If the eNB does not find a RRC context that matches the identity of the WTRU 20, the new eNB comes into direct contact with the previously housed eNB using the eNB identity transmitted by the WTRU 20. As described above, eNB may alternatively derive the WTRU identity or the WTRU context of the Mobile Administration Entity (MME).

If a context is found and transferred in the old eNB, it sends, in response to the RRC CONNECTION REQUEST, a message (such as RRC CONNECTION RESPONSE) or any other RRC procedure initiated by WTRU that indicates to WTRU 20 that reuse the RRC context you have stored. If the context is not found in the new or old eNB, an RRC connection establishment procedure occurs and the WTRU 20 discards the RRC contexts it has stored. In this case, when the network sends a response to the RRC procedure initiated by the WTRU, network 20 indicates whether WTRU 20 can establish the stack using the old context information it had before the failure or network 10 transmits new parameters in the message. response for the WTRU 20 to configure your battery. After the WTRU 20 receives the reply message from the network 10 and processes it, the WTRU 20 transmits a complete message to the network 10 which indicates to the network 10 that it has finished the configuration on its side.

Table 4 below describes the mobility of the WTRU 20

11/15 during a delivery failure according to the method described.

Table 4

Delivery and Mobility Failure

<td>Cases</td><td>First phase</td><td>Second level</td><td>T2 expired</td><td>Priority cell selection</td>

<td>EU enters the target cell</td><td>Continue as if no there were occurred problems of radio</td><td>The activity does not Can be resumed without interaction between UE and eNode B</td><td>Go via RRCJDLE</td><td> 1</td>

<td>EU returns to the cell source</td><td>AT</td><td>The activity does not Can be resumed without interaction between EU and eNode B</td><td>Go via RRCJDLE</td><td> 2</td>

<td>EU selects a cell different from same eNode B</td><td>AT</td><td>The activity does not Can be summed up without interaction between the UE and the eNode B, o procedure to be used is FFS, normally didn't see RRCJDLE</td><td>Go via RRCJDLE</td><td> 3</td>

<td>EU selects a cell of an eNode B different</td><td>AT</td><td>The activity does not Can be resumed without interaction between the UE and the eNode b, o procedure to be used is FFS,</td><td>go via RRCJDLE</td><td> 4</td>

12/15

<td></td><td></td><td>normally didn't see RRCJDLE</td><td></td><td></td>

For the second phase, in order to resume activity when WTRU 20 returns to the same cell or when WTRU 20 selects a different cell from the same eNB or a different eNB, a method is described in which WTRU 20 has access to the cell through the random access procedure. The non-access layer identity (NAS) used in the random access procedure is also used by eNB to determine whether eNB has a stored RRC context for WTRU 20. If eNB finds a stored RRC context for WTRU 20. If eNB finds a RRC context that matches the identity of WTRU 20, eNB sends a message in response to the RRC CONNECTION REQUEST (such as CONNECTION RESPONSE RRC) or any other RRC procedure initiated by WTRU that tells WTRU 20 to reuse the RRC context it has stored.

If the eNB does not find a RRC context that matches the identity of the WTRU 20, the new eNB comes into direct contact with the previously housed eNB using the eNB identity transmitted by the WTRU 20. As described above, eNB may alternatively derive the WTRU identity or the MME WTRU context.

If a context is found and transferred in the old eNB, it sends in response to the RRC CONNECTION REQUEST a message (such as RRC CONNECTION RESPONSE) or any other RRC procedure initiated by the WTRU, which indicates to the WTRU 20 to reuse the RRC context it stored. If the context is not found in the new or old eNB, a procedure for establishing a standard RRC connection occurs! and WTRU 20 preferably discards the RRC contexts it has stored. It should be noted that the use of the cell selection priority column in Tables 3 and 4 is an alternative method and that, regardless of the priority, the procedure described is still applicable if other selection and new selection priorities are used. ACHIEVEMENTS

1. Wireless communication method implemented in a wireless transmission and reception unit (WTRU) comprising:

- detection of a failure that includes at least one of the radio link (RL) and delivery (HO) failures;

- transmission of a wireless transmission and reception unit identity (WTRU) and an information element (IE) that includes at least one of a source Node identity and source cell identity for access to a target Node; and

13/15

- receiving context information from target Node B based, at least in part, on IE.

2. Method according to realization 1, which additionally includes conducting the new cell selection to select an available target Node B.

3. Method according to any of the previous accomplishments, in which the source Node B identity is considered in the selection of an available target Node B.

4. Method according to any of the previous accomplishments, in which the new selection comprises:

- attempt, first, to select the source Node B again; and

- attempt to reselect to a source cell associated with the source cell identity when the source Node B is not available.

5. Method according to realization 4, in which the target Node B and the target cell are different from the source Node B and the source cell.

6. Method according to any of the previous realizations, which additionally includes the storage of context information before the detected failure.

7. Method according to any of the realizations 1 to 6, in which the context information includes an indication of the use of the stored context information.

8. Method according to any of the realizations 1 to 6, in which the context information includes context information different from the stored context information.

9. Method according to any of the previous achievements, which additionally comprises the access of a network that uses at least one among the use of a smaller retrograde or higher power increase.

10. Method according to any of the previous accomplishments, which additionally comprises the receipt of at least one dedicated subscription allocated during delivery, whereby the dedicated signature is used to access a source cell after an RL or delivery failure.

11. Method according to realization 10, in which at least one dedicated signature is received on a delivery command.

12. Method according to realization 10, which additionally comprises the receipt of the delivery command that includes two dedicated signatures assigned, in which one of the dedicated signatures is used to access a target Node B and the other is used to access a source Node B if an RL or delivery failure occurs.

13. Method according to realization 12, which additionally includes the release of the two dedicated signatures when the delivery has ended.

14. Method according to any of the previous accomplishments, in which at least one dedicated subscription among a set of subscriptions is reserved on a broadcast channel for access to any cell of any Node B after an RL or

14/15 delivery.

15. Method according to realization 14, in which the set of signatures reserved for dedicated access is received in a delivery command.

16. Wireless transmission and reception unit that comprises a processor configured to implement a method according to any of the previous embodiments.

17. Node B that comprises a processor configured to implement a method according to any of the previous realizations.

18. Processor configured to implement a method according to any of the previous achievements.

Although the characteristics and elements are described above 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 embedded in 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 CD-ROM 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,

15/15 Internet browser and / or any wireless local area network (WLAN) or Ultra Wide Band (UWB) module.

1/2