Mobile terminal, base station and methods therein

TECHNICAL FIELD

The present embodiments relate to a mobile terminal, a mobile station, and methods therein. In particular, these embodiments relate to on-demand access to a wireless communication system.

BACKGROUND

In today's wireless communication systems, many different technologies are used, such as Long-Term Evolution (LTE), LTE-Advanced, Broadband Multiple Code-Split Access (WCDMA), Worldwide Wireless Communication System / Increased Data Transmission Rates over GSM networks (GSM / EDGE) ), Global Microoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations. The wireless communication system includes base stations providing radio coverage in at least one relevant geographical area forming the cell. The cell definition may also contain the frequency bands used for transmission, which means that two different cells may cover the same geographical area but using different frequency bands. Mobile terminals are served in the cells by the appropriate base station and communicate with the corresponding base station. Mobile terminals transmit data on an air or radio interface to base stations in uplink (UL) transmissions and base stations transmit data on an air or radio interface to mobile terminals in downlink (DL) transmissions.

Version 6 of the third generation partnership project standards (3GPP) introduced Enhanced

Uplink (E-UL), also known as High Speed ​​Uplink Packet Access (HSUPA). Compared to previous versions, E-UL has improved uplink communication performance - those from the mobile terminal, i.e., User Equipment, UE, to the base station - using higher data speeds, reduced latency, and improved system bandwidth. These improvements were implemented through a new transport channel called the Reinforced Dedicated Channel (E-DCH). In Version 6, and continuing to Version 7, however, the mobile terminal can only use E-DCH in limited circumstances.

Specifically, at the Radio Resource Control (RRC) level, the mobile terminal can be in two basic modes of operation, called Idle mode and CONNECTED mode. In Idle mode, the mobile terminal requests an RRC connection before sending any uplink data or responding to a call. In CONNECTED mode, on the contrary, the mobile terminal has an RRC connection, and can be in one of several device states: Universal Mobile Telecommunications System (UMTS), Radio Access Paging Channel (URA_PCH), Cell Paging Channel (CELL_PCH), Access Channel State Cell Front (CELL_FACH), and the status of the Dedicated Cell Channel (CELL_DCH). The URA_PCH and CELL_PCH states are paging states in which the mobile terminal sleeps and only occasionally wakes up and checks the paging. To send uplink data, the mobile terminal moves to the CELL_FACH or CELL_DCH state. When shifting to the CELL_FACH state in Versions 6 and 7, the mobile terminal can send a relatively small amount of uplink data in a transport channel based on the competition called the Free Access Channel (RACH), but not in E-DCH; to send data in E-DCH, the mobile terminal had to be moved to the CELL_DCH state, which introduces a delay.

To reduce the delay caused by the transition, Version 8 of 3GPP standards allocates some E-DCH resources as common resources, also called common E-DCH resources, which can be used on a competitive basis by mobile terminals in the CELL_FACH state. Accordingly, mobile terminals in the CELL_FACH state with a relatively large amount of uplink data can send this data in E-DCH using common E-DCH resources rather than having to make multiple accesses in RACH or switch to the CELL_DCH state.

However, this happens at the expense of increased downlink control signaling. In fact, the base station now broadcasts system information to mobile terminals that inform them which access request preambles can be used for E-DCH access request, and which E-DCH resources are available as common E-DCH resources. Among other disadvantages, this increased DL control signaling may delay base station signaling of more key system information.

For example, the base station often transmits system information in a series of so-called System Information Blocks (SIBs). Different types of system information are transmitted in different types of SIB, one after the other in a time-separated manner. This process is repeated to continuously provide system information to mobile terminals as needed. Accordingly, any given large SIB delays the transmission of the entire SIB series, which in turn increases the time between which any given SIB is repeated, i.e., the SIB repeat factor. If the SIB repetition factor is excessively large for SIBs with key system information, there may be long periods of time in which the mobile terminal cannot be recalled, send uplink data, perform cell updates, or perform lower renegotiation to a switched circuit network, also called renegotiation lower CS. This type of delay can be caused by the increased DL control signaling associated with Version 8 of 3GPP standards resulting in reduced performance of the wireless communication system.

WO2007052971 discloses a prior art system that transmits contention-based channel information to the UE.

WO2009057032 discloses a method of communication between a primary station and a secondary station comprising the step of signaling two different random access channels based on a resource difference for the two random access channels.

SUMMARY

The purpose of these embodiments is to improve the efficiency of the wireless communication system.

According to an aspect of the present embodiments, the goal is achieved by a method in a mobile terminal for requesting access to a wireless communication system. The mobile terminal receives broadcast system information which indicates the first available channel resource on the basis of competition. The mobile terminal outputs the second available channel resource on the basis of competition based on the first available channel resource on the basis of competition. The mobile terminal also transmits a mapped preamble to request access to a second available resource for access to the wireless communication system.

In accordance with another aspect of the present embodiments, the objective is achieved by a base station method for managing access to a wireless communication network. The base station encodes system information indicating the second available contention-based channel resource relative to the first available contention-based channel resource. The base station transmits coded system information.

In accordance with yet another aspect of the present embodiments, the purpose is achieved by a mobile terminal for requesting access to a wireless communication system. The mobile terminal includes a receiving circuit configured to receive broadcast system information that indicates the first available contention based channel resource. The mobile terminal also includes a processing circuit configured to output the second available contention-based channel resource based on the first available contention-based channel resource, and to transmit a mapped preamble to request access to the second available resource.

In accordance with yet another aspect of the present embodiments, the goal is achieved by a base station for managing access to a wireless communication network. The base station includes a processing circuit configured to encode system information indicating a second available contention-based channel resource relative to the first available contention-based channel resource. Further, the base station includes a transmitting circuit configured for transmitting system information.

By indicating available channel resources based on competition with other available channel resources, the amount of data signaled in system information is reduced. Thus, the delay for transmitting system information is reduced and the operation of the wireless communication system is improved.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of embodiments will now be described in more detail with reference to the attached drawings, in which:

Fig. 1 is a schematic block diagram showing a wireless communication system,

Fig. 2 is a combined process diagram and signaling diagram illustrating the present embodiments,

Fig. 3 is a flow diagram showing embodiments of a method at a base station,

Fig. 4 is a block diagram illustrating embodiments of the base station,

Fig. 5 is a flow chart showing embodiments of the method in a mobile terminal, and

Fig. 6 is a block diagram illustrating embodiments of the mobile terminal.

DETAILED DESCRIPTION

Fig. 1 is a schematic overview depicting a wireless communication system, also referred to as a radio communication network. In today's wireless communication systems, several different technologies are used, such as LTE, LTE-Advanced, WCDMA, GSM / EDGE, WiMax, or UMB, to mention just a few possible implementations. A wireless communication system that includes base station 12 and one or more other units 14. Base station 12 provides a communication channel in uplink 16 for receiving uplink data from individual mobile terminals 10, 10-1, 10-2 ... 10-N in a group of 20 with N mobile terminals, also conveniently referred to as "users" or "equipment user". Base station 12 also provides a communication channel in the downlink 22 for sending transmission to mobile terminals 10 - 10-N in group 20, including control signaling.

The specialist should understand that "mobile terminal" is a non-limiting term that means any user equipment, wireless terminal, device or node, e.g. Personal Digital Assistant (PDA), laptop, cell phone, sensor, relay, mobile tablets or even a small base station communicating at a cell served by base station 12.

Base station 12 may also be referred to as e.g. NodeB, evolved Node B (eNB, eNode B), radio base station, transceiver base station, Access Point Base Station, base station router, base station controller, radio network controller, or any other network entity capable of communicating with 10 - 10-N mobile terminals in a cell served by base station 12 depending on e.g. the radio access technology and terminology used.

Base station 12 can support two different Competitive Base (CB) channels of the uplink 16 communication channel, one legacy CB channel, e.g., offering low data rates such as RACH, and one non-legacy CB channel, e.g., offering high speeds data such as E-DCH. Some 10-1 - 10-N mobile terminals, referred to as legacy mobile terminals, only support the legacy CB channel, while others support both CB channels. If the mobile terminal 10 supports both channels, the mobile terminal 10 may preferentially select a non-legacy CB channel for sending uplink data. To manage access to both CB channels, base station 12 transmits system information for both CB channels on the downlink communication channel control channel 22. Contest based channel means a channel that can be used by many mobile terminals without prior coordination. Thus, for a contention-based channel, base station 12 broadcasts preamble access requests that mobile terminal 10 randomly selects. On a non-competitive channel, base station 12 first maps the preamble to access mobile terminal 10 and then transmits the mapped preamble to access to mobile terminal 10 for use by mobile terminal 10. Base station 12 transmits system information that indicates which CB channel resources are available. As a point of benefit, base station 12 intelligently transmits system information for CB channels, to reduce the amount of control signaling in the downlink. In accordance with the present embodiments, instead of transmitting system information to 10-10-N mobile terminals that independently indicates available resources, base station 12 encodes system information that indicates available CB channel resources relative to other available channel resources, e.g. relative to the position where other available resources are indicated in the system information. In some embodiments, for example, available resources are indicated in an ordered list, and base station 12 indicates available resources as a function of their position in the list relative to other resources. Base station 12 transmits this system information to 10-10 N mobile terminals.

Accordingly, the mobile terminal 10 is configured to receive system information that indicates the first available CB channel resource. The mobile terminal 10 is configured to output information for the second available CB channel resource on a base basis or as a function of the first available resource. This may result, for example, in outputting information for the second available resource according to a predetermined rule that defines the second resource as a function of the first available resource, e.g., as a function of the position of the first available resource in an ordered list describing the resources. In various embodiments, the second available CB channel resource is mapped to the access request preamble randomly selected by the mobile terminal. In such embodiments, the mobile terminal 10 is configured to output information for a second available resource in response to receiving a positive acknowledgment corresponding to the selected preamble, and then to transmit uplink data on the CB channel using the second available resource. The embodiments described herein can advantageously reduce the signaling required in System Information Blocks (SIB), especially Type 5 System Information Block (SIB5) when information from preambles is signaled there, to broadcast the entire amount of common E-DCH resources about 70% compared to current signaling.

Fig. 2 is a schematic combined process diagram and signaling diagram illustrating some of the present embodiments.

Step 201. Base station 12 encodes system information for transmission to mobile terminals in an area covered by base station 12. System information indicates available contention-based channel resources, e.g., a second contention-based channel. The competitive channel can be represented by the Free Access Channel (RACH) or the Enhanced Dedicated Channel (E-DCH). The encoded system information indicates the uplink channel resources available on a competitive basis relative to other available resources of the uplink channel based on competition.

Step 202. Base station 12 transmits system information to one or more of the 10-10-N mobile terminals.

Base station 12 may further transmit control channel system information that indicates which first access request preambles and second access request preambles can be used for access request using the corresponding CB channels. Each access request preamble can be mapped to specific CB channel resources. In this regard, CB channels share the "request" space of the access request preamble.

As a benefit point, base station 12 can intelligently transmit system information for CB channels to limit the amount of control signaling in the downlink. Instead of transmitting system information to 10-10-N mobile terminals, which independently indicates access request preambles for respective CB channels, base station 12 can transmit system information indirectly indicating access request preambles for one channel, e.g., non-CB channel, based on , e.g. as a function of access request preambles for another channel, e.g., legacy CB channel. Indirectly means here that the second access request preambles can be derived from the first access request preambles, e.g. as a function of the indicated first access request preambles. Accordingly, mobile terminal 10 may receive system information directly indicating access request preambles for one channel, e.g., legacy CB channel, and may output access request preambles for another channel, e.g., non-legacy CB channel, as a function of directly indicated request preambles. access. The mobile terminal 10 may then randomly select one of the derived access request preambles and transmit the selected access request preamble to base station 12 to request access to the associated CB channel, i.e., non-legacy channel or legacy channel.

Step 203. The mobile terminal 10, which has received broadcast system information indicating the first available resource, derives the second available resource from the system information as well as the CB channel preamble request. This could be the case when the first available resource generated an unconfirmed access request.

Step 204. At some point after receiving this system information, the mobile terminal 10 requests access to a supported or preferred CB channel, the first or second competitive channel, e.g. by randomly selecting one of the first or second access request preambles associated with it. channel, and by transmitting the selected preamble to base station 12 using the second available resource.

Step 205. The base station 12, which received the transmitted access request preamble, performs contention management for the associated CB channel.

Step 206. Base station 12 transmits or signals on the downlink communication channel 22 whether base station 12 acknowledges or refuses to request the mobile terminal to access that channel using the second available resource.

Step 207. If the mobile terminal 10 receives a positive acknowledgment, the mobile terminal 10 continues by sending uplink data on any available resource, e.g. a second resource as shown, of the associated CB channel which is mapped to the selected and confirmed access request preamble.

The embodiments described herein advantageously reduce the signaling required in SIB5 to transmit the entire amount of common E-DCH resources by about 70% compared to current signaling. In particular, after Rel-8, SIB5 can be substantially enlarged due to the configuration of the common EDCH. A total of 32 common E-DCH resources can be configured in the cell. If all these resources are included in SIB5, the size of SIB5 will increase by 8 segments, where the segment consists of a header and a data field, e.g. the data field houses elements of the encoded system information. This means that SIB5 can have more than 12 segments, and in turn means that the Main Information Block up to 16 segments, SIB11 up to 16 segments, and SIB5 will have more than 50% of the 64 segments available in the 1.280 second scheduling window frame. As a result, SIB5 cannot be transmitted in less than 640 ms, which means that the repetition rate will have to be increased. However, according to the above embodiments, the number of segments for SIB5 transmission can be reduced to less than 3 segments. This means that the SIB5 repetition rate can be reduced. Hence, the transmission delay URA / CELL updates the Radio Carrier (RB) reconfiguration when appropriate, or the delay introduced in the CS switching mechanism will be minimized. More specifically, the SIBs are read by the mobile terminal 10 at various stages. For example, when the mobile terminal 10 is turned on, or when the mobile terminal 10 moves from the CELL_DCH state to the CELL_FACH state, the mobile terminal 10 must re-acquire SIB. Similarly, when mobile terminal 10 moves to another cell, new SIBs must be read.

Updating the cell will be the procedure that will have the greatest impact. The cell update is performed when moving from the CELL_DCH state to the CELL_FACH state if the IDs are not included or the mobile terminal 10 selects a different cell than the one indicated in the RB reconfiguration. The Cell Update is also performed when the mobile terminal 10 changes the cell. For E-DCH in mobile terminals in CELL_FACH state and CELL_DCH state, Cell Update is also required after a Radio Link (RL) failure. There are other cases where a cell update is required.

Next, Version 10 of 3GPP standards also known as the 4th Generation, introduced CS switching from LTE. This feature may require the mobile terminal 10 to read the SIB before starting the procedure.

Specialists will appreciate that when the above examples were described in the context of 3GPP standards, these teachings can be applied to a wide range of system types, communication sewer schemes, etc.

Fig. 3 is a flow diagram illustrating a method in base station 12 for managing access to a wireless communication network in accordance with the present embodiments.

Step 301. Base station 12 encodes system information indicating a second contention-based channel resource available relative to the first contention-based channel resource available. The contention-based channel may in some embodiments correspond to a random access channel, RACH, or a joint Reinforced Dedicated Channel, E-DCH. System information can be contained in System Information Block type 5, SIB5. In addition, a second available resource may be indicated in the ordered resource list as a function of the position of the first available resource in the ordered list. An ordered list in certain embodiments defines the resources of the joint Dedicated Reinforced Channel, E-DCH. Each E-DCH Resource is defined by the Soffset information element, Fractional Dedicated Physical Control Channel, FDPCH, information element code number, and information element info Hybrid Channel Confirmation Indicator Indicator, Automatic Confirmation Request E-DCH, E-HICH, for common EDCH. The position of the second available resource in the ordered list is in some embodiments defined by the default value in the Soffset information element. The default value can e.g. be a function of the position of the second available resource in the ordered list, a function of the "Soffset" value of the previous first available resource, or a function of the position of the second available resource and the offset value. In these embodiments, the offset value is the Soffset value of the first available resource. The information element F-DPCH code number is in some embodiments the same for up to ten common E-DCH resources. The Info E-HICH information element for the common E-DCH can be defined by the sewer code and the signature sequence. The default signature sequence value may be, e.g., a function of the position of the second available resource in an ordered list, a function of the value of "Signature Sequence" of the previous first available resource, or a function of the position of the second available resource and the value of "Signature Sequence" of the previous first available resource. The sewage code of the second available resource is in some embodiments equal to the sewage code of the first available resource.

The second available resource can be defined by the value in the information element scrambling code of the Dedicated Physical Control Channel in the uplink. The value can be e.g. the function of the position of the second available resource in the ordered list of common E-DCH resources, the function of the value in the information element the scrambling code of the Dedicated Physical Control Channel in the uplink of the previous first available resource, or the function of the position of the second available resource and the value of the "info of the DPCH code of the Uplink for the Common E-DCH "in the information element, the scrambling code of the Dedicated Physical Control Channel in the uplink of the previous first available resource.

Step 302. Base station 12 transmits coded system information. Thus, base station 12 manages access by broadcasting system information indicating available resources to be used for accessing the wireless communication network.

The present embodiments preferably reduce downlink control signaling associated with contention-based uplink access to the wireless communication system.

The present embodiments further reduce downlink control signaling by the fact that instead of transmitting system information to mobile terminals that independently indicates access request preambles for each of two different contention based (CB) channels in the uplink, base station 12 in accordance with some embodiments can transmit system information, which indirectly indicates the access request preambles for one channel based or as a function of the preambles for another channel. Accordingly, the mobile terminal 10 receives system information that directly indicates the access request preambles for one CB channel and outputs the access request preambles for another CB channel as a function of the directly indicated preambles.

As a specific example in the context of 3GPP specifications, base station 12 may support CB channels that correspond to a Free Access Channel (RACH) and a common Reinforced Dedicated Channel (E-DCH). Accordingly, base station 12 transmits system information for these channels in the System Information Block (SIB), namely SIB Type 5. System information for RACH is broadcast in SIB5 using the "PRACH System Information List" Information Element (IE), while system information for the common E-DCH is transmitted in SIB5 using the IE "Common E-DCH System Information". The access request preamble as used above corresponds to the PRACH preamble, which has a signature sequence, scrambling code, and sub-channel.

More specifically, the present embodiments reduce the number of segments used in SIB5 to broadcast IE "Common E-DCH System Info" that define common E-DCH resource parameters. To this end, new coding for IE included in IE "Common System Info E-DCH" in SIB5 is proposed. IE "Common System Info E-DCH" is an optional IE included in SIB5. The table below shows the current encoding for Duplex Frequency Division (FDD) for IE "Common E-DCH System Info". For definitions of different IE, reference is made to the Technical Specification (TS) 3GPP 25.331 section 10 version 10.0.0.

<td>Name information Element / Group</td><td>Needed</td><td>Multi</td><td>Type i Reference</td><td>Semantic description</td><td>Version</td>

<td>UL interference for joint EDCH</td><td>OP</td><td></td><td>UL interference 10.3.6.87</td><td></td><td>REL-8</td>

<td>Common EDCH MACd flows</td><td>MP</td><td></td><td>Common MACd flows E-DCH 10.3.5.3b</td><td></td><td>REL-8</td>

<td>SELECTION mode</td><td>MP</td><td></td><td></td><td></td><td>REL-8</td>

<td>&gt; FDD</td><td></td><td></td><td></td><td></td><td>REL-8</td>

<td>&gt;&gt; Preamble control parameters PRACH (for reinforced uplink)</td><td>MP</td><td></td><td>parameters control preamble PRACH (for the Fortified uplink) 10.3.6.54a</td><td>Control parameters of the physical signal</td><td>REL-8</td>

<td>&gt;&gt; value allocation initial service</td><td>MP</td><td></td><td>Integer (0..37)</td><td>(0..37) indicates E-DCH service assignment index as defined [15].</td><td>REL-8</td>

<td>&gt;&gt; Price E-DCH Transmission Time</td><td>MP</td><td></td><td>Integer (2.10)</td><td>The unit is ms.</td><td>REL-8</td>

<td>&gt;&gt; E-AGCH Info</td><td>MP</td><td></td><td>E-AGCH Info 10.3.6.100</td><td></td><td>REL-8</td>

<td>&gt;&gt; HARQ info for E-DCH</td><td>MP</td><td></td><td>HARQ info for E-DCH 10.3.5.7d</td><td></td><td>REL-8</td>

<td>&gt;&gt; info controlling DPCH power in Uplink</td><td>MP</td><td></td><td>info controlling DPCH power in Uplink for Joint EDCH 10.3.6.91a</td><td></td><td>REL-8</td>

<td>&gt;&gt; E-DPCCH info</td><td>MP</td><td></td><td>E-DPCCH Info 10.3.6.98</td><td></td><td>REL-8</td>

<td>&gt;&gt; E-DPDCH info</td><td>MP</td><td></td><td>E-DPDCH info 10.3.6.99</td><td></td><td>REL-8</td>

<td>&gt;&gt; purpose of F-DPCH TPC degree false commands</td><td>MP</td><td></td><td>Real (0.01..0.1 step 0.01).</td><td>Information F-DPCH in Downlinek. Actual value of dl-FDPCHTPCcommandErrorRate = IE value * 0.01</td><td>REL-8</td>

<td>&gt;&gt; suspension additional E-DCH transmission</td><td>MP</td><td></td><td>integer (0.15)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>&gt;&gt; Maximum allocation of E-DCH resources for CCCH</td><td>MP</td><td></td><td>numbered (8, 12, 16, 24, 32, 40, 80, 120)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>&gt;&gt; Maximum period for the solution phase collision</td><td>MP</td><td></td><td>Integer (8..24)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>&gt;&gt; suspension of continuing E-DCH transmission</td><td>MP</td><td></td><td>Numbered (0, 8, 16, 24, 40, 80, 120, infinity)</td><td>In terms of TTI. If set to "infinity" is off default version of EDCH common resources.</td><td>REL-8</td>

<td>&gt;&gt; ACK / NACK service on HSDPCCH</td><td>MP</td><td></td><td>boolean</td><td>TRUE indicates that HS-DPCCH should be used when the E-DCH common resource is allocated to UE for DTCH / DCCH transmission after collision resolution. FALSE indicates that HSDPCCH is not to be used.</td><td>REL-8</td>

<td>&gt;&gt; Feedback Measurement</td><td>OP</td><td></td><td>Feedback measurement 10.3.6.40a</td><td></td><td>REL-8</td>

<td>list &gt;&gt; information configuration resources Joint E-DCH</td><td>MP</td><td>1 to &lt;MaksEDCH&gt;</td><td></td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt; Soffset</td><td>MP</td><td></td><td>Integer (0..9)</td><td>(0..9) indicates the symbol offset as defined in [26]</td><td>REL-8</td>

<td>&gt;&gt;&gt; F-DPCH code number</td><td>MP</td><td></td><td>integer (0..255)</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt; E-RGCH information</td><td>OP</td><td></td><td>E-RGCH Info 10.3.6.102</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt; E-HICH info</td><td>MP</td><td></td><td>E-HICH info 10.3.6.101</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt; DPCH code info in uplink</td><td>MP</td><td></td><td>DPCH code info in uplink for joint E-DCH 10.3.6.87b</td><td></td><td>REL-8</td>

MP means Mandatory Present and OP means Optional. IE that is Mandatory Present must always be included and have value, while the value of optional IE may or may not be present. MD means Mandatory Default. When IE is set as a mandatory default, a value for this IE is always needed, and a specific default value is mentioned.

The present embodiments propose modifications to certain IEs as detailed below.

&gt;&gt; E-DCH Common Resource Configuration Information list

This IE is a list that contains all defined common E-DCH resources. A maximum of 32 shared E-DCH resources can be included in this list. For each defined E-DCH common resource, the following IE are defined:

&gt;&gt;&gt; Soffset

This IE is MP IE, whose value is between 0 and 9. This value indicates the specific slot in the F-DPCH that contains the power control commands for the specific F-DPCH.

Instead of being MP, this IE in various embodiments is set to MD. If IE is not present, "Soffset" defaults. The default value is a function of the E-DCH common resource entry in the list, a function of the "Soffset" value of the previous EDCH common resource case, or a function of E-DCH common resource entry and the "Soffset" value of the previous E-DCH common resource case. The first defined E-DCH common resource will occupy position 0 (or 1). The second defined E-DCH common resource will occupy position 1 (or 2). Similar reasoning will apply to other defined resources.

A specific implementation will be, for example, if the "Soffset" value for the first E-DCH common resource case defaults and the rest of the E-DCH common resource takes the last case value.

For example, a simple formula is shown below for setting default values ​​for each defined E-DCH resource.

Soffet = (offset + item in the E-DCH common resource list) mod 10 where "offset" is the value of the last IE case "Soffset". If IE "Soffset" was not present in the first case, "offset" is zero.

"E-DCH Common Resource List Item" indicates the number of the E-DCH Common Resource Configuration Information in order of appearance. The value of the "E-DCH Common Resource List Item" can be zero (or one) for the first case.

If IE is present, the signaled value overrides the default value.

&gt;&gt;&gt; F-DPCH code number

This IE indicates the code to use for F-DPCH.

Instead of being MP, this IE is optional, depending on the value.

If the coding presented for Soffset is potentially used, only three cases of the F-DPCH code number are needed, once for every 10 E-DCH common resources. Hence, in the best configuration, only three cases will have to be present.

Thus, this IE in various embodiments is set to be conditioned by the value (CV) so that this IE is mandatory for the first occurrence. Alternatively, it may be mandatory for the first occurrence or if the default value is zero. Otherwise, this IE is optional. Additionally, if this IE is not present, the value is equal to the last instance of this IE.

If IE is present, the signaled value overrides the default value.

&gt;&gt;&gt;&gt; E-HICH info

E-HICH info contains two additional IE. Changes in this IE will cause impacts on Version 6 and Version 7 3GPP standards. To avoid affecting earlier versions, a new IE can be used instead: "E-HICH info for common E-DCH". Only two IE will be needed as this feature only applies to FDD.

&gt;&gt;&gt; E-HICH info for joint E-DCH

Sewer code

This IE can be set to be conditional on the value (CV) of IE, so that IE is only mandatory for the first case and optional for others. If this IE does not exist, the value is equal to the last occurrence of this IE.

If IE is present, the signaled value overrides the default value.

Signature sequence

The value of this IE is a number between 0 and 39. This IE in various embodiments is set to MD. If IE is not present, "signature sequence" defaults.

The default value is a function of the E-DCH common resource entry in the list, a function of the "Signature sequence" value of the previous E-DCH common resource case, or a function of E-DCH common resource entry and the "Signature sequence" value of the previous E-DCH common resource case. The first defined E-DCH common resource will occupy position 0 (or 1). The second defined E-DCH common resource will occupy position 1 (or 2). Similar reasoning will apply to other resources. A specific implementation may be, for example, if the "Signature sequence" for the first E-DCH common resource case defaults and the remaining E-DCH common resource takes the function of the value of the last IE case.

For example, a simple formula is shown below for setting default values ​​for any defined E-DCH common resource that does not have IE.

Signature Sequence = (offset + position in the E-DCH common resource list) mod 40 where "offset" is the value of the last IE instance "Signature Sequence". If "Signature Sequence" was not present in the first case, "offset" is zero.

"E-DCH Common Resource List Item" indicates the number of the E-DCH Common Resource Configuration Information in order of appearance. The value of the "E-DCH Common Resource List Item" is zero (or one) for the first case.

If IE is present, the signaled value overrides the default value.

&gt;&gt;&gt; DPCH code info in the uplink for the Common E-DCH

The scrambling code number is the current MP value. This IE accepts a relatively large number of bits for each E-DCH common resource. This IE in some embodiments is changed to value-based (CV) instead, avoiding including such a large number of bits on the configured E-DCH common resource.

Value-based means that this IE is mandatory for the first occurrence. Otherwise, this IE is optional. Additionally, if this IE is not present, the IE value is a function of the last case. For example, it can be a function of the E-DCH common resource item in the E-DCH common resource list, a function of the "DPCH code info in the uplink for Common E-DCH" previous case of an E-DCH common resource, or a function of an E-DCH common resource item and "DPCH code info in uplink for Common E-DCH" values ​​of the previous E-DCH common resource case. The following formula illustrates how default values ​​can be set when IE is not included:

Scrambling code number = offset + item in the E-DCH common resource list where "offset" is the value of the last IE instance "scrambling code number". If "offset" was not present in the first case or occurrence, "offset" is equal.

"E-DCH Common Resource List Item" indicates the number of the E-DCH Common Resource Configuration Information in order of appearance. "E-DCH Common Resource List Value"

is zero (or 1) for the first case.

If IE is present, the signaled value overrides the default value.

&gt;&gt; E-DPDCH info

E-DCH E-TFCI minimum setting

This IE is mandatory by default. If this IE is missing, then there is no minimum E-TFCI setting.

For E-DCH in CELL_FACH and Idle Mode, the UE will always send its message, especially CCCH messages. Otherwise, the UE will be blocked and, potentially, the UE will be abandoned. It seems obvious that for E-DCH in CELL_FACH and Idle Mode, the E-DCH minimum E-TFCI setting will always be included and must necessarily be a number above zero (E-TFCI index 0 will only allow UE to send Serial Information).

Thus, the semantic description can be modified so that for CELL_FACH and Idle Mode (or for Enhanced Uplink in CELL_FACH and Idle Mode), if IE is not included, the E-DCH minimum E-TFCI setting is set to a defined value. The only limitation for this value is that the value belongs to the set of values ​​defined in the E-TFCI table. The specific table to be used is indicated in IE "E-TFCI index table" also included in IE "E-DPDCH info". As previously mentioned, the zero value of E-TFCI only allows the UE to transmit the Scheduling Information. Thus, the minimum reasonable E-TFCI value that the UE may transmit user data or higher layer control data is an E-TFCI value of 1.

If IE is present, the signaled values ​​override the default value.

&gt;&gt; PRACH preamble control parameters for Reinforced Uplink

This IE is characterized by available signatures, preamble scrambling code numbers, and available Subchannel numbers.

Available Signatures

This is IE of a series of bits and each bit indicates whether the signature is used or not. Signatures configured for RACH and included in IE "Available Signatures" are presented in IE "PRACH info (for RACH)". These signatures cannot be used for Reinforced Uplink in CELL_FACH and Idle Mode. IE "PRACH info (for RACH)" is included in the IE "PRACH System Information List", which is located in SIB5. "PRACH System Information List", "PRACH info (for RACH)" and "Available Signatures" are mandatory in IE. Hence, they will always be included in SIB5.

IE "Available Signatures" contained in IE "PRACH preamble control parameters for

Reinforced Uplink "is also a mandatory current value; however, in these embodiments this IE is optional and takes the default value. This default value is the same or a function of another IE, e.g.," Available Signatures "present in IE" PRACH info ( for RACH) ".

As an example, the default value in various embodiments is the operation of the "NO" or "REVERSE" function of the value of a series of bits contained in the "Available Signatures" present in IE "PRACH info (for RACH)".

An illustrative example is given to explain the concept. If the value of IE "Available Signatures" contained in IE "PRACH info (for RACH)" is: 1111111100000000, then the default value of IE "Available Signatures" contained in IE "Common System Info E-DCH" will be the reverse bit operation of (1111111100000000), which is equal to 0000000011111111. Thus, IE "available signatures" is set to mandatory default (MD) and the description semantics would say that the default value is the inverse bit series indicated in IE "Available Signatures" in IE "PRACH Info (for RACH)". In other words, the available signatures for Reinforced Uplink in CELL_FACH are those signatures that are not used for RACH, unless IE is present.

By doing so, base station 12 inhibits the incorporation of this IE into IE "PRACH Preamble Control Parameters for Reinforced Uplink" and thereby reduces downlink control signaling. A mobile terminal 18 that does not receive such IE nevertheless sets IE to the default value described above. If IE is present, the signaled values ​​override the default value.

Preamble scrambling code number

This IE is also included in IE "PRACH info (for RACH)". The present embodiments teach that the scrambling code for common E-DCH is the same as this code for RACH, at least by default. If it were different, the new preamble scrambling code number in various embodiments is a function of the preamble scrambling code number present in IE "PRACH info (for RACH)". Hence, this IE in some embodiments is MD and by default equal to IE "preamble scramblign code number" indicated in IE "PRACH info (for RACH)", and is otherwise the IE function "preamble scrambling code number" indicated in IE "PRACH info (for RACH) ".

As in the previous case, base station 12 refrains from incorporating this IE into IE "PRACH preamble control parameters for Reinforced Uplink" and thereby reduces control signaling in the downlink. A mobile terminal 18 that does not receive such an IE nevertheless sets IE to the default value described above. If IE is present, the signaled values ​​override the default value.

Number of Subchannels Available

This IE is a series of bits. Each bit indicates availability for the subchannel, where the subchannels are numbered from "subchannel 0" to "subchannel 11". A value of 1 bit indicates that the corresponding subchannel is available and a value of zero indicates that it is not available.

This IE is also included in IE "PRACH info (for RACH)". This IE in some embodiments is also set to MD. The mandatory default value is the IE function "PRACH info (for RACH)".

For example, this IE can be set equal to IE "Available Subchannel Number" indicated in IE "PRACH info (for RACH)". In another approach, the default value may be the INverse (or NOT) function IE "Available Subchannel Number" indicated in IE "PRACH info (for RACH)"

As in the previous case, base station 12 refrains from incorporating this IE into IE "PRACH preamble control parameters for Reinforced Uplink" and thereby reduces control signaling in the downlink. A mobile terminal 18 that does not receive such an IE nevertheless sets IE to the default value described above. If IE is present, the signaled values ​​override the default.

The use of the coding suggested above, the IE structure "PRACH Preamble Control Parameters for Reinforced Uplink" and other IE involved will result in the following, affected IEs are indicated by underlined text, and intact IEs are defined in relation to 3GPP Technical Specification (TS) 25.331 section 10 version 10.0 .0:

Common E-DCH system info are defined by IE in the following table.

<td>Name information Element / Group</td><td>Needed</td><td>Multi</td><td>Type and reference</td><td>Semantic description</td><td>Version</td>

<td>UL interference for common E-DCH</td><td>OP</td><td></td><td>UL interference 10.3.6.87</td><td></td><td>REL-8</td>

<td>Common EDCH MACd flows</td><td>MP</td><td></td><td>Common MAC-d flows E-DCH 10.3.5.3b</td><td></td><td>REL-8</td>

<td>SELECTION mode</td><td>MP</td><td></td><td></td><td></td><td>REL-8</td>

<td>&gt; FDD</td><td></td><td></td><td></td><td></td><td>REL-8</td>

<td rowspan="5">parameters &gt;&gt; control preamble PRACH (for reinforced uplink)</td><td rowspan="5">MP</td><td rowspan="5"></td><td>control parameters</td><td rowspan="5">Control Parameters physical signals</td><td rowspan="5">REL-8</td>

<td>PRACH preamble (for</td>

<td>reinforced</td>

<td>Uplink) 10.3.6.54a</td>

<td></td>

<td>&gt;&gt; the value of the Initial Service allocation</td><td>MP</td><td></td><td>Integer (0..37)</td><td>(0..37) indicates E-DCH service assignment index as defined [15].</td><td>REL-8</td>

<td>&gt;&gt; Price E-DCH Transmission Time</td><td>MP</td><td></td><td>Integer (2.10)</td><td>The unit is ms.</td><td>REL-8</td>

<td>&gt;&gt; E-AGCH Info</td><td>MP</td><td></td><td>E-AGCH Info 10.3.6.100</td><td></td><td>REL-8</td>

<td>&gt;&gt; HARQ info for E-DCH</td><td>MP</td><td></td><td>HARQ info for E-DCH 10.3.5.7d</td><td></td><td>REL-8</td>

<td>&gt;&gt; info controlling DPCH power in uplink</td><td>MP</td><td></td><td>info controlling DPCH power for Common E-DCH 10.3.6.91a</td><td></td><td>REL-8</td>

<td>&gt;&gt; E-DPCCH info</td><td>MP</td><td></td><td>E-DPCCH Info 10.3.6.98</td><td></td><td>REL-8</td>

<td rowspan="2">&gt;&gt; E-DPDCH info</td><td rowspan="2">MP</td><td rowspan="2"></td><td>E-DPDCH info</td><td rowspan="2"></td><td rowspan="2">REL-8</td>

<td> 10.3.6.99</td>

<td>&gt;&gt; purpose of F-DPCH TPC degree false commands</td><td>MP</td><td></td><td>Real (0.01..0.1 step 0.01).</td><td>Information F-DPCH in Downlinek. Real value dl-FDPCHTPCcommandErrorRate = IE value * 0.01</td><td>REL-8</td>

<td>&gt;&gt; suspension additional E-DCH transmission</td><td>MP</td><td></td><td>Integer (0..15)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>&gt;&gt; Maximum allocation of E-DCH resources for CCCH</td><td>MP</td><td></td><td>Numbered (8, 12, 16, 24, 32, 40, 80, 120)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>&gt;&gt; Maximum period for the solution phase collision</td><td>MP</td><td></td><td>Integer (8..24)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>&gt;&gt; suspend continuation transmission E-DCH</td><td>MP</td><td></td><td>Numbered (0, 8, 16, 24, 40, 80, 120, infinity)</td><td>In terms of TTI. If set to "infinity", the default EDCH common resource version is disabled.</td><td>REL-8</td>

<td>&gt;&gt; ACK / NACK service on HSDPCCH</td><td>MP</td><td></td><td>boolean</td><td>TRUE indicates that HS-DPCCH should be used when the common E-DCH resource is allocated to the UE for DTCH / DCCH transmission after collision resolution. FALSE indicates that HSDPCCH is not to be used.</td><td>REL-8</td>

<td>&gt;&gt; Infor Feedback Measurement</td><td>OP</td><td></td><td>Feedback Measurement 10.3.6.40a</td><td></td><td>REL-8</td>

<td>list &gt;&gt; information configuration Joint EDCH resources</td><td>MP</td><td>1 to &lt;MaksEDCH&gt;</td><td></td><td></td><td>REL-8</td>

<td rowspan="2">&gt;&gt;&gt; Soffset</td><td rowspan="2">MD</td><td rowspan="2"></td><td>Integer (0..9)</td><td rowspan="2">(0..9) indicates offset symbol as defined in [26] Note 3</td><td rowspan="2">REL-8</td>

<td></td>

<td rowspan="3">&gt;&gt;&gt; F-DPCH code number</td><td>Short-CV</td><td rowspan="3"></td><td>integer</td><td rowspan="3">If this IE is not present, value is equal to the last instance of this IE.</td><td rowspan="3">REL-8</td>

<td rowspan="2"></td><td> (0..255)</td>

<td></td>

<td>&gt;&gt;&gt; E-RGCH information</td><td>OP</td><td></td><td>E-RGCH Info 10.3.6.102</td><td></td><td>REL-8</td>

<td rowspan="2">&gt;&gt;&gt; E-HICH info for joint EDCH</td><td rowspan="2">MP</td><td rowspan="2"></td><td>E-HICH info for joint E-DCH</td><td rowspan="2"></td><td rowspan="2">REL-8</td>

<td>10.3.6.1xx</td>

<td rowspan="3">&gt;&gt;&gt; code info DPCH in Uplink</td><td rowspan="3">MP</td><td rowspan="3"></td><td>DPCH code info in</td><td rowspan="3"></td><td rowspan="3">REL-8</td>

<td>uplink for joint</td>

<td>E-DCH 10.3.6.87b</td>

<td>&gt; TDD</td><td></td><td></td><td></td><td></td><td>REL-8</td>

<td>&gt;&gt; CHOICE TDD option</td><td>MP</td><td></td><td></td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt; 7.68 Mcps TDD</td><td></td><td></td><td>lack</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt; 3.84 Mcps TDD</td><td></td><td></td><td>lack</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt; 1.28 Mcps TDD</td><td></td><td></td><td></td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt; E-RUCCH Prediction</td><td>MP</td><td></td><td>E-RUCCH Info 1.28 Mcps TDD 10.3.6.103a</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt; E-PUCH info</td><td>MP</td><td></td><td>E-PUCH Info 1.28 Mcps TDD 10.3.6.104a</td><td>Note 1</td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt; E-HICH info</td><td>MP</td><td></td><td>E-HICH info 1.28 Mcps TDD 10.3.6.101a</td><td>Note 1</td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt; E-AGCH Prediction</td><td>MP</td><td></td><td>E-AGCH Info 1.28 Mcps TDD 10.3.6.100a</td><td>Note 1</td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt; HARQ info for E-DCH</td><td>MP</td><td></td><td>HARQ info for E-DCH 10.3.5.7d</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt; CCCH broadcast info</td><td>MP</td><td></td><td></td><td>Note 2</td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt;&gt; info of the ERNTI Joint</td><td>MP</td><td></td><td>Info Joint ERNTI 10.3.3.7a</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt;&gt; HARQ maximal number retransmit</td><td>MP</td><td></td><td>Integer (0..7)</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt;&gt; HARQ timer retransmit</td><td>MP</td><td></td><td>Numbered (10,15,20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100,110, 120,140, 160)</td><td>Unit: ms</td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt;&gt; HARQ power offset</td><td>MP</td><td></td><td>Integer (0..6)</td><td></td><td>REL-8</td>

<td colspan="6"></td>

<td colspan="6">Status Explanation</td>

<td>Short</td><td>This IE is mandatory for the first occurrence. Otherwise, this IE is optional.</td>

<td colspan="2">NOTE1: These IE correspond to the HS-DSCH configuration for the CELL_FACH, CELL_PCH and URA_PCH state on the main frequency, the configuration on the secondary frequency is signaled to the UE via dedicated signaling. NOTE2: These IE correspond to the CCCH transmission configuration for the CELL_FACH state on the primary frequency and the secondary frequency. NOTE3: The default value is defined by: Soffset = (offset + item in the E-DCH common resource list) mod 10 where "offset" is the value of the last case of IE "Soffset". If IE "Soffset" was not present in the first case, "offset" is zero. "E-DCH Common Resource List Item" indicates the number of the E-DCH Common Resource Configuration Information in order of appearance. The value of "EDCH Common Resource List Item" is zero for the first case.</td>

E-DPDCH Info has the following IE.

<td>Name of the element information / Groups</td><td>Needed</td><td>Multi</td><td>Type i reference</td><td>Semantic description</td><td>Version</td>

<td>ETFCI table index</td><td>MP</td><td></td><td>integer (0..1)</td><td>Indicates which E-TFCI TB tables of standardized size will be used. See. attention 3.</td><td>REL-6</td>

<td>E-DCH minimal</td><td rowspan="5">MD</td><td rowspan="5"></td><td>integer</td><td>See. [15]: None means none</td><td>REL-6</td>

<td>E-TFCI setting</td><td> (0..127)</td><td>minimum setting E-</td><td rowspan="4"></td>

<td rowspan="3"></td><td rowspan="3"></td><td>DCH. IN CELL FACH AND MODE</td>

<td>Idle, default value</td>

<td>is 1.</td>

<td>E-TFCI references</td><td>MP</td><td></td><td></td><td>See. [29]</td><td>REL-6</td>

<td>&gt; E-TFCI references</td><td>MP</td><td></td><td>Integer (0..127)</td><td></td><td>REL-6</td>

<td rowspan="2">&gt; E-TFCI AFTER Reference</td><td rowspan="2">MP</td><td rowspan="2"></td><td>Integer (0..29,</td><td>Reference to power offset quantization in [28]</td><td>REL-6</td>

<td> 30, 31)</td><td>The values ​​30 and 31 are only used for E-TFCI&gt; ETFCI Boost</td><td>REL-7</td>

<td>Minimum coefficient reduced profit for E-DPDCH</td><td>OP</td><td></td><td>Numbered (8/15, 11/15, 15/15, 21/15, 30/15, 42/15, 60/15, 84/15)</td><td>^eed, k, reduced, min ^{[29]; value}the default is 8/15. If the configurable EDPDCH reduced profit factor is not supported by the UE, the default value is used.</td><td>REL-8</td>

<td>codes the maximum sewer</td><td>MP</td><td></td><td>Numbered (sf256, sf128, sf64, sf32, sf16, sf8, sf4, 2sf4, 2sf2, 2sf2 and 2sf4)</td><td></td><td>REL-6</td>

<td>^ENnon-max</td><td>MP</td><td></td><td>Real (0.44 ..1.0 stage 0.04)</td><td>As defined in [27]</td><td>REL-6</td>

<td>Configuration information scheduling</td><td>MP</td><td></td><td></td><td></td><td>REL-6</td>

<td>&gt; Periodicity for Prediction No allocation</td><td>MD</td><td></td><td>numbered (każdeEDCHT TI, 4,10,20,50, 100,200,500,1 000)</td><td>Values ​​in ms. The default value is "no report". NOTE 1.</td><td>REL-6</td>

<td>&gt; Periodicity for Prediction Scheduling assignment</td><td>MD</td><td></td><td>numbered (każdeEDCHT TI, 4,10,20,50, 100,200,500,1 000)</td><td>Values ​​in ms. The default value is "no report". NOTE 1.</td><td>REL-6</td>

<td>&gt; Power Offset for Info scheduling</td><td>MP</td><td></td><td>Integer (0..6)</td><td>Used only when no MACd PDUs are included in the same MACe PDU. The unit is dB.</td><td>REL-6</td>

<td>3-Index Stage Threshold</td><td>MD</td><td></td><td>Integer (0..37)</td><td>Refers to the index in the "SGTable" (see [15]). The default value is 0. NOTES 2, 3.</td><td>REL-6</td>

<td>2-Index Stage Threshold</td><td>MD</td><td></td><td>Integer (0..37)</td><td>Refers to the index in the "SGTable" (see [15]). The default value is 0. NOTES 2, 3.</td><td>REL-6</td>

<td colspan="6">NOTE 1: If the Periodicity is set to 4ms and the E-DCH TTI is set to 10ms, the UE will interpret the periodicity value as 10ms.</td>

<td colspan="6">NOTE 2: If the value of the 3-Index Stage Threshold is greater than the 2-Index Stage Threshold, the EU behavior is undefined.</td>

<td colspan="6">NOTE 3: If the UE operates in 16QAM mode, the value of the "E-TFCI table index" is increased by 2, and the indexes in the SG-Table refer to Schedule Assignment Table 2 in [15].</td>

E-HICH Info for Common E-DCH is characterized by the following IE

<td>name of the element information / Groups</td><td>Needed</td><td>Multi</td><td>Type i reference</td><td>Semantic description</td><td>Version</td>

<td>Sewer Code</td><td>Short-CV</td><td></td><td>number</td><td>If this IE is not present,</td><td>REL-8</td>

<td></td><td></td><td></td><td>whole</td><td>the value is equal to the last one</td><td></td>

<td></td><td></td><td></td><td> (0..127)</td><td>instance of this IE.</td><td></td>

<td>Sequence</td><td>MD</td><td></td><td>number</td><td></td><td>REL-8</td>

<td>The signature</td><td></td><td></td><td>whole</td><td></td><td></td>

<td></td><td></td><td></td><td> (0..39)</td><td>Uwagal</td><td></td>

<td colspan="3">Short</td><td colspan="3">This IE is mandatory for first occurrence. Otherwise, this IE is optional.</td>

<td>NOTE 1:</td><td colspan="4">The default value is defined by:</td><td></td>

<td colspan="6">Signature Sequence = (offset + position in the E-DCH common resource list) mod 40</td>

<td colspan="6">where "offset" is the value of the last IE instance "Signature Sequence". If "Signature Sequence" was not present in the first occurrence, "offset" is zero.</td>

<td colspan="6">"E-DCH Common Resource List Item" indicates the number of the E-DCH Common Resource Configuration Information in order of appearance. The value of the "E-DCH Common Resource List Item" is zero for the first case.</td>

The uplink DPCH code info for the Common E-DCH is characterized by the following IE.

<td>Name of the element Information / Group</td><td>Needed</td><td>Multi</td><td>Type and reference</td><td>Description semantic</td><td>Version</td>

<td>Scrambling code type</td><td>MP</td><td></td><td>Numbered (short, long)</td><td></td><td>REL-8</td>

<td>Code number</td><td>Short-CV</td><td rowspan="2"></td><td rowspan="2">Integer (0..16 777 215)</td><td rowspan="2">Note 1</td><td rowspan="2">REL-8</td>

<td>scramblingu</td><td></td>

<td></td><td></td><td></td><td></td><td></td><td></td>

<td colspan="3">State</td><td colspan="3">Explanation</td>

<td colspan="3">Short</td><td colspan="3">This IE is mandatory for the first occurrence. Otherwise, this IE is optional.</td>

<td colspan="6">NOTE1: If this IE is not included, the value is given by: Scrambling code number = offset + position in the E-DCH common resource list where "offset" is the value of the last instance of IE "scrambling code number". If IE "scrambling code number" is not present in the first occurrence, "offset" is zero. "Common E-DCH Resource List Item" indicates the number of the Resource Configuration Information</td>

<td>Name of the element Information / Group</td><td>Needed</td><td>Multi</td><td>Type and reference</td><td>Description semantic</td><td>Version</td>

<td colspan="6">Common E-DCH in order of occurrence. The value of the "Common EDCH resource list item" is zero for the first case.</td>

As stated above, processing at base station 12 may include in some embodiments, coding system information that directly indicates the access request preambles for the contention-based uplink channel and which indirectly indicates the access request preambles for another channel in the contention-based uplink on the basis or as a function directly indicated preambles. The changed IE are indicated by the underlined text:

Control parameters of the PRACH preamble (for Reinforced Uplink) are characterized by the following IE.

<td>Name element information / Groups</td><td>unnecessary</td><td>Multi</td><td>Type i reference</td><td>Semantic description</td><td>Version</td>

<td>available</td><td>MD</td><td></td><td>Number</td><td>The default value is inverse</td><td>REL-8</td>

<td>Signature</td><td></td><td></td><td>Bits (16)</td><td>series of bits indicated in IE "Available Signature" in IE "PRACH Info (for RACH)". Each bit indicates availability for signature. Each available the signature on AICH is associated with one Configuration Joint E-DCH resources in the "list of configuration information Joint E-DCH resources ".</td><td></td>

<td>E-AI Indication</td><td>MP</td><td></td><td>BOOLEAN</td><td>TRUTH: E-Al are used on AICH. FALSE: E-AI are not used on AICH.</td><td>REL-8</td>

<td>Code number scramblingu</td><td>MD</td><td></td><td>integer (0. 15)</td><td>The default is the value "code number indicated in IE"</td><td>REL-8</td>

<td>preamble</td><td></td><td></td><td></td><td>preamble scrambling "in IE "PRACH Info (for RACH)". Identification of codes scrambling, see [28]</td><td></td>

<td>Number available subchannel</td><td>MD</td><td></td><td>Number bits (12)</td><td>The default value is the same value indicated in IE "Available Signatures" in IE "system information list PRACH ". Each bit indicates availability for the subchannel, where subchannels are numbered "subchannel 0" to "subchannel 11". A value of 1 bit indicates that corresponding subchannel is an available value of 0 indicates that it is not available.</td><td>REL-8</td>

<td>PRACH partitioning</td><td>MD</td><td></td><td>PRACH partitioning 10.3.6.53</td><td>The default value is the "PRACH partitioning" value in the first instance in the "list of PRACH system information" list in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>coefficients scaling durability</td><td>OP</td><td></td><td>coefficients scaling durability 10.3.6.48</td><td>This IE should not be present as soon as ASC 0 and ASC 1 are defined. If this IE is absent, the default value is the value "persistence scaling factors" in the first occurrence in the list "PRACH system information list" in SIB5 or SIB5bis, if the value exists</td><td>REL-8</td>

<td>Mapping AC-to-ASC</td><td>MD</td><td></td><td>Mapping AC-to-ASC 10.3.6.1</td><td>The default value is the "AC-doASC mapping" value in the first instance in the "list of PRACH system information" list in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Main power CPICH TX</td><td>MD</td><td></td><td>Main power CPICH TX 10.3.6.61</td><td>The default value is the "CPICH TX Main Power" value in the first occurrence in the "PRACH system information list" list in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Constant value</td><td>MD</td><td></td><td>Constant value 10.3.6.11</td><td>The default value is the "Fixed value" value in the first occurrence in the "list of PRACH system information" list in SIB5 or SIB5bis</td><td>REL-8</td>

<td>PRACH power offset</td><td>MD</td><td></td><td>PRACH power offset 10.3.6.54</td><td>The default value is the "PRACH power offset" value in the first speech in "PRACH system information list" in SIB5 or SIB5bis</td><td>REL-8</td>

<td>parameters transmission PRACH</td><td>MD</td><td></td><td>RACH transmission parameters 10.3.6.67</td><td>The default value is the value "RACH transmission parameters" in the first speech in "PRACH system information list" in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>AICH info</td><td>MD</td><td></td><td>AICH info 10.3.6.2</td><td>The default value is the value of "AICH info" in first occurrence in the list "PRACH system information list" in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Power offset Pp-e</td><td>MP</td><td></td><td>integer (-5..10)</td><td>In dB. Power offset between the last preamble transmitted and the initial one DPCCH transmission as defined in [26]</td><td>REL-8</td>

The coding code, e.g. the ASN 1 code, can be updated as below as soon as the relevant IE has been added:

SyslnfoType5 :: = SEGUENCE {sib6indicat.or BOOLEAN,

- Physical channel IEs' pich-PowerOffset 'modeSpecificInfo fdd aich-PowerOffset},' tdd.

- If PDSCH / PUSCH is configured for be absent

- and the info included in the respective tddl28Specificlnfo or tdd768Specificlnfo instead. - If PDSCH / PUSCH is configured for 3.84Mcps TDD in R5, HCR-r5-Specificlnfo should aiso

PICH-PowerOffset,

CHOICE {

SEGUENCE {

AICH-PowerOffset

SEGUENCE {.28Mcps or 7.68Mcps TDD, the following rEs should be included.

pusch-SysInfoList-SFN pdsch-SysInfoList-SFN openLoopPowerControl-TDD

PUSCH-SyslnfoList-SFN PDSCH-SyslnfoList-SFN OpenLoopPowerControl-TDD

OPTIONAL,

OPTIONAL, primaryCCPCH-Info prach-SystemlnformationList sCCPCH-SystemlnformationList

OPTIONAL,

PrimaryCCPCH-Info PRACH-System nf ormationList, SCCPCH-SystemlnformationList,

- cbs-DRX-LevellInformatioń is conditional on any of the CTCH indicator IEs in - sCCPCH-SystemlnformationList.

cbs-DRX-Levell Information System CBS-DRX-LevellInformation OPTIONAL,

Extension mecbanism for non- release99 Information v4bONonCriticalExtensions SEGUENCE {syslnfoType5-v4b0ext SyslnfoType5-v4b0ext-IEs OPTIONAL, - Extension mechanism for non-reI-4 i.nformarion '.

OPTIONAL, v590NonCriticalExtensions.

• sysInfoType5-v590ext v650NonCriticalExtensions sys Inf oType5-v6'50ext

SEQUENCE {

SysInfoType5-v590ext-IEs SEGUENCE {

SyslnfoType5-vS50ext-ies

OPTIONAL,

IEs, v890ext-TEs, v8b0ext-IEs, v680NonCriticalExtensions syslnfoType5-v680ext

SEGUENCE {

SysInfoType5-v680ext-IEs v690NonCriticaIExtensions sysInfoType5-v690ext v770NonCriticaIExtensions sysInfoType5-v770ext v860NonCriticalExtensions. syslnfoType5-v860ext

SEQUENCE {

SyslnfoType5-v5 90ext-IEs, SEGUENCE {

SysInfoType5-v770ext-IEs, SEGUENCE ('

SysInfoType5-v860extv890NonCriticaIExtensions sys! NfoType5-v8 9 0ext.

v8bONonCrit 'calExtensions. syslnfoType5-v8b0ext SEQUENCE (

SysInfoType5v8cONonCritioalExtensions syslnfoType5-v8c0ext nonCriticalExtensions} OPTIONAL

OPTIONAL} OPTIONAL.

} OPTIONAL} OPTIONAL l · OPTIONAL.

} OPTIONAL} OPTIONAL

OPTIONAL

OPTIONAL.

SF.QUENCE {

SysInfoType5SEQUENCE {

SEGUENCE {}

OPTIONAL

SysInfoType5-v8 90ext-IEs secondFreguencylnfo

SEQUENCE

FreguencylnfoTDD

- The field 'dummy' shall be marked absent in SysInfoType5 and SyslnfoType5bis. A failure to.

- compiy with this claiming may prevent the UE to receive any service in the celi. The UE '

- may treat the celi as barred.

'dummy SEQUENCE {) OPTIONAL.

and ''.

SysInfoType5-v8c0ext-IEs commonEDCHSystemlnfo

SEQUENCE

CommonEDCHSystemlnfo

OPTIONAL

PRACH-PreambleForEnhancedUplink :: = avaiiableSignatures e-ai-Indication.

preambleScramblingCodeWordNumber availabieSubChannelNumbers prach-Partitioning persistenceScalingFactorList ac-To-ASC-MappingTable primaryCPICH-TX-Power constantValue prach-PowerOffset rach-Transmis sionParameters aich-Info powerOffsetPp-e

SEQUENCE {'

AvailableSignatures OPTIONAL,

BOOLEAN,

PreambleScramblingCodeWordNumber OPTIONAL,

AvailableSubChannelNumbers. OPTIONAL,. PRACH-Partitioning-r7 OPTIONAL,

PersistenceScalingFactorList OPTIONAL,

AC-To-ASC-MappingTable OPTIONAL,

PrimaryCPICH-TX-Power OPTIONAL,

ConstantValue · OPTIONAL,. PRACH-PowerOffset 'OPTIONAL,

RACH-Transmission Paramęters OPTIONAL,

AICH-Info 'OPTIONAL,

INTEGER (-5..10) ''

Common-E-DCH-ResourcelnfoList SEQUENCE s-offset.

f-dpch-ChannelisationCodeNumber e-RGCH-Info.rmation e-hich-Info ul-DPCH-CodelnfoForCommonEDCH

INTEGER (0..9) '

INTEGER (0..255) '

E-RGCH-Information E-HICH-Information-CommonEdch, UL-DPCH-CodelnfoForCommonEDCH

OPTIONAL,

OPTIONAL,

OPTIONAL,

UL-DPCH-CodelnfoForCommonEDCH: ul-DPCCHscramblingCodeType ul-DPCCHscramblingCode)

SEQUENCE ('. ScramblingCodeType,

UL-ScramblingCode

OPTIONAL

E-HICH-Information-CommonEdch channelisationCode. .OPTIONAL, 'signatureSeguence OPTIONAL'

SEQUENCE {

E-HICH-ChannelisationCode.

E-HICH-RGCH-SignatureSeguence

In some embodiments, a second approach may be adopted to provide a backward compatible solution.

In this case, new IE must be added in SIB5, for example, "Short System Info 5 of the Common E-DCH". This new IE may contain new encoding.

The SIB5 table will be as follows:

System Information Block type 5 and 5bis

<td>Information Item / Group Name</td><td>Necessary</td><td>Multi</td><td>Type i reference</td><td>Semantic description</td><td>Version</td>

<td>SIB6 Indicator</td><td>MP</td><td></td><td>boolean</td><td>TRUTH indicates that SIB6 is transmitted in a cell.</td><td></td>

<td></td><td></td><td></td><td></td><td>When the UE receives the SIB5 in the Container message System Information, this IE is interpreted as FALSE</td><td></td>

<td>PhyCH information elements</td><td></td><td></td><td></td><td></td><td></td>

<td>PICH power offset</td><td>MP</td><td></td><td>power offset PICH 10.3.6.50</td><td>If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3 UE behaves as if this IE was not received.</td><td></td>

<td>SELECTION mode</td><td>MP</td><td></td><td></td><td></td><td></td>

<td>&gt; FDD</td><td></td><td></td><td></td><td></td><td></td>

<td>&gt;&gt; AICH power offset</td><td>MP</td><td></td><td>power offset AICH 10.3.6.3</td><td>If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3, the UE behaves as if this IE was not received.</td><td></td>

<td>&gt; TDD</td><td></td><td></td><td></td><td></td><td></td>

<td>&gt;&gt; PUSCH system information</td><td>OP</td><td></td><td>PUSCH information System 10.3.6.66</td><td>If the cell is operating in MBSFN mode as indicated in section 8.1.1.6.3, the UE's behavior after receiving this IE is undefined.</td><td></td>

<td>&gt;&gt; PUSCH VHCR system information</td><td>OP</td><td></td><td>PUSCH system information VHCR 10.3.6.66 a</td><td>Only for 7.68 Mcps TDD. If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3, the UE's behavior after receiving this IE is undefined.</td><td>REL-7</td>

<td>&gt;&gt; PDSCH system information</td><td>OP</td><td></td><td>PDSCH information System 10.3.6.46</td><td>If the cell is in MBSFN mode as indicated in clause 8.1.1.6.3, the UE action after receiving this IE is undefined.</td><td></td>

<td>&gt;&gt; TDD open-loop power control</td><td>MP</td><td></td><td>TDD power control w open loop 10.3.6.79</td><td>If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3 UE behaves as if this IE was not received.</td><td></td>

<td>Main Info CCPCH</td><td>OP</td><td></td><td>Main info CCPCH 10.3.6.57</td><td>Note 1</td><td></td>

<td>list of PRACH system information</td><td>MP</td><td></td><td>list of information system PRACH 10.3.6.55</td><td>If the cell works in MBSFN mode as indicated in sub-clause 8.1.1.6.3 UE behaves as if this IE was not received.</td><td></td>

<td>Common E-DCH system info</td><td>OP</td><td></td><td>System info of Common EDCH 10.3.6.9a</td><td></td><td>REL-8</td>

<td>Short info Joint system E-DCH</td><td>OP</td><td></td><td>Short info Common EDCH 10.3.6.9b system</td><td></td><td>REL-8</td>

<td>secondary CCPCH system information</td><td>MP</td><td></td><td>secondary information System CCPCH 10.3.6.72</td><td>Note2 If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3 UE behaves as if this IE was not received.</td><td></td>

<td>Information CBS DRX Level 1</td><td>CV-CTCH</td><td></td><td>Information CBS DRX Level 1 10.3.8.3</td><td></td><td></td>

<td>Band indicator frequency</td><td>OP</td><td></td><td>Indicator bandwidth frequency 10.3.6.35 b</td><td></td><td>REL-6</td>

<td>Band indicator frequency 2</td><td>OP</td><td></td><td>Indicator bandwidth frequency 2 10.3.6.35 c</td><td></td><td>REL-6</td>

<td>HSDPA cell indicator</td><td>MD</td><td></td><td rowspan="4">Numbered (cell capable of HSDPA)</td><td>The default is' ability to HSDPA not indicated '.</td><td>REL-6</td>

<td></td><td></td><td></td><td>'A cell capable of HSDPA 'means EU may consider this cell as part of the coverage area HSDPA only for displaying the indication.</td><td></td>

<td></td><td></td><td></td><td>This indication will not be used for any other purpose.</td><td></td>

<td></td><td></td><td></td><td>If the cell works in MBSFN mode as indicated in sub-clause 8.1.1.6.3. The UE behaves as if this IE has not been received.</td><td></td>

<td>EDCH cell indicator</td><td>MD</td><td></td><td rowspan="4">numbered (Cell EDCH capable)</td><td>The default is 'E-DCH capability not indicated'.</td><td>REL-6</td>

<td></td><td></td><td></td><td>'EDCH Capable Cell' means that the UE may consider this cell as part of the E-DCH coverage area only for displaying the indication.</td><td></td>

<td></td><td></td><td></td><td>This indication will not be used for any other purpose.</td><td></td>

<td></td><td></td><td></td><td>If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3 UE behaves as if this IE was not received.</td><td></td>

<td>Secondary CCPCH MBMS system information</td><td>OP</td><td></td><td>Secondary system information CCPCH MBMS 10.3.6.72 a</td><td>Contained if MCCH is on S-CCPCH used only for MBMS. Note 2</td><td>REL-6</td>

<td>SELECTION mode</td><td>OP</td><td></td><td></td><td></td><td>REL-7</td>

<td>&gt; FDD</td><td></td><td></td><td></td><td></td><td>REL-7</td>

<td>&gt;&gt; HS-DSCH ordinary system information</td><td>MP</td><td></td><td>HS-DSCH usually information System 10.3.6.36 c</td><td>Included if the cell supports receiving HSDSCH in CELL_FACH And during the transition from STERILE to RRC connection.</td><td>REL-7</td>

<td>&gt;&gt; HS-DSCH recalling system information</td><td>OP</td><td></td><td>HS-DSCH recalling system information 10.3.6.36 d</td><td>Included if the cell supports UE in RRC connection state calling for receiving messages on HS-DSCH.</td><td>REL-7</td>

<td>&gt; TDD</td><td></td><td></td><td></td><td></td><td>REL-7</td>

<td>&gt;&gt; HS-DSCH ordinary system information</td><td>MP</td><td></td><td>HS-DSCH ordinary system information 1.28Mcps TDD 10.3.6.36 ca</td><td>Included if the cell supports HS-DSCH reception in CELL_FACH And during the transition from Idle to RRC Connection.</td><td>REL-8</td>

<td>&gt;&gt; HS-DSCH recalling system information</td><td>OP</td><td></td><td>HS-DSCH recalling 1.28Mcps TDD system information 10.3.6.36 da</td><td>Included if the cell supports UE in RRC connection state calling for receiving messages on HS-DSCH.</td><td>REL-8</td>

<td>TDD MBSFN information</td><td>OP</td><td></td><td>TDD MBSFN Information 10.3.6.78 b</td><td>TDD only included when some time intervals are intended for MBSFN.</td><td>REL-7</td>

<td>HS-DSCH DRX century information CELL_FACH</td><td>OP</td><td></td><td>HS-DSCH DRX in information CELL_FACH 10.3.6.36 g</td><td></td><td>REL-8</td>

<td>HS-DSCH DRX in Information CELL_FACH 1.28 Mcps TDD</td><td>OP</td><td></td><td>HS-DSCH DRX century information CELL_FACH 1.28 Mcps TDD 10.3.6.36 h</td><td></td><td>REL-8</td>

<td>Second Frequency Info</td><td>OP</td><td></td><td>number total (0 .. 16383)</td><td>Note 3</td><td>REL-8</td>

<td>Treset Use Indicator</td><td>OP</td><td></td><td>Enumerated (TRUTH)</td><td>Only for 1.28 Mcps TDD. The presence of this IE means that the Timer Treset is not valid when a dedicated HRNTI is configured in CELL FACH and CELL PCH.</td><td>REL-8</td>

<td>UpPCH Position Info</td><td>CVCzęstotliwość</td><td></td><td>number total (0 .. 127)</td><td>Only for 1.28 Mcps TDD.</td><td>REL-8</td>

The new IE can then be defined as follows:

Brief system info of the Joint E-DCH

NOTE: Only for FDD.

<td>Name of the element Information / Group</td><td>Needed</td><td>Multi</td><td>Type i reference</td><td>Semantic description</td><td>Version</td>

<td>UL interference for common E-DCH</td><td>CVOpcjonalne</td><td></td><td>UL interference 10.3.6.87</td><td></td><td>REL-8</td>

<td>Common E-DCH MAC-d flows</td><td>CVObowiązkowe</td><td></td><td>flows MAC-d joint EDCH 10.3.5.3b</td><td></td><td>REL-8</td>

<td>Control Parameters PRACH preamble (for Reinforced uplink)</td><td>CVObowiązkowe</td><td></td><td>parameters control preamble PRACH (for reinforced uplink) 10.3.6.54a</td><td>parameters control physical signal.</td><td>REL-8</td>

<td>initial service assignment value</td><td>CVobowiązkowe</td><td></td><td>Integer (0..37)</td><td>(0..37) indicates the E-DCH service assignment index as defined in [15].</td><td>REL-8</td>

<td>Interval E-DCH transmission</td><td>CVObowiązkowe</td><td></td><td>number total (2,10)</td><td>The unit is ms.</td><td>REL-8</td>

<td>E-AGCH Info</td><td>CVObowiązkowe</td><td></td><td>E-AGCH Info 10.3.6.100</td><td></td><td>REL-8</td>

<td>HARQ info for E-DCH</td><td>CVObowiązkowe</td><td></td><td>HARQ info for E-DCH 10.3.5.7d</td><td></td><td>REL-8</td>

<td>Power control info DPCH in Uplink</td><td>CVObowiązkowe</td><td></td><td>Info controlling the DPCH power in Uplink for the Joint EDCH 10.3.6.91a</td><td></td><td>REL-8</td>

<td>E-DPCCH info</td><td>CVObowiązkowe</td><td></td><td>E-DPCCH Info 10.3.6.98</td><td></td><td>REL-8</td>

<td>E-DPDCH info</td><td>CVObowiązkowe</td><td></td><td>E-DPDCH info 10.3.6.99</td><td></td><td>REL-8</td>

<td>Target F-DPCH TPC degree erroneous commands</td><td>CVObowiązkowe</td><td></td><td>Real (0.01..0.1 step 0.01).</td><td>F-DPCH information in the downlink. Actual value dl-FDPCHTPCcommandError R ate = IE value * 0.01</td><td>REL-8</td>

<td>Suspending additional E-DCH transmission</td><td>CVObowiązkowe</td><td></td><td>number whole (0..15)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>Maximum allocation of E-DCH resources for CCCH</td><td>CVObowiązkowe</td><td></td><td>Numbered (8, 12, 16, 20, 24, 32, 40, 80)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>The maximum period for collision resolution phases</td><td>CVObowiązkowe</td><td></td><td>number whole (8..24)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>suspension continue transmission E-DCH</td><td>CVObowiązkowe</td><td></td><td>numbered 4, 8, 16, 24,40,80, infinity )</td><td>In terms of TTI. If set to "infinity", the default resource version is disabled joint E-DCH.</td><td>REL-8</td>

<td>ACK / NACK support on HS-DPCCH</td><td>CVObowiązkowe</td><td></td><td>boolean</td><td>TRUE indicates that HSDPCCH should be used when the common E-DCH resource is allocated to the UE for DTCH / DCCH transmission after collision resolution. FALSE indicates that HS-DPCCH is not to be used.</td><td>REL-8</td>

<td>Feedback Measurement</td><td>CVOpcjonalne</td><td></td><td>Feedback Measurement 10.3.6.40a</td><td></td><td>REL-8</td>

<td>E-DCH Common Resource Configuration Information List</td><td>MP</td><td>1 to &lt;maksED CH&gt;</td><td></td><td></td><td>REL-8</td>

<td>&gt; Soffset</td><td>MD</td><td></td><td>number total (0..9)</td><td>(0..9) indicates the offset symbol as defined in [26] Note3</td><td>REL-8</td>

<td>&gt; F-DPCH code number</td><td>Short-CV</td><td></td><td>Integer (0..255)</td><td>If this IE is not present, the value is equal to the last occurrence of this IE.</td><td>REL-8</td>

<td>&gt; E-RGCH Information</td><td>Short-CV</td><td></td><td>E-RGCH Info 10.3.6.102</td><td></td><td>REL-8</td>

<td>&gt; E-HICH info for joint E-DCH</td><td>MD</td><td></td><td>E-HICH info for joint EDCH 10.3.6.1xx</td><td></td><td>REL-8</td>

<td>&gt; code info for DPCH in uplink</td><td>MD</td><td></td><td>code info for DPCH in the uplink for the Common E-DCH 10.3.6.87b</td><td></td><td>REL-8</td>

<td colspan="2"></td>

<td>State</td><td>Explanation</td>

<td>Optional</td><td>If IE "Common E-DCH System Info" is present, the value of this IE is the same value corresponding to IE in IE "Common E-DCH System info". Otherwise, this IE is optional.</td>

<td>Short</td><td>This IE is mandatory for the first occurrence. Otherwise, this IE is optional.</td>

<td>Mandatory</td><td>If IE "System Info Common E-DCH" is present, the IE value is the same value corresponding to IE in IE "System Info Common E-DCH". Otherwise, this IE is mandatory present.</td>

NOTE1: These IE correspond to the HS-DSCH configuration for the CELL_FACH, CELL_PCH and URA_PCH state on the main frequency, the configuration on the secondary frequency is signaled to the UE via dedicated signaling.

NOTE2: These IE correspond to the CCCH transmission configuration for the CELL_FACH state on the main frequency and the secondary frequency.

NOTE3: The default value is defined by:

Soffset = (offset + item in the E-DCH common resource list) mod 10 where "offset" is the value of the last IE case "Soffset". If IE "Soffset" was not present in the first case, "offset" is zero.

"E-DCH Common Resource List Item" indicates the number of the E-DCH Common Resource Configuration Information in order of appearance. The value of "E-DCH Common Resource List Item" is zero for the first case.

Additional states may be placed in another to reduce signaling in case of IE "Common System Info E-DCH" conclusion. Affected IE are underlined below:

PRACH preamble control parameters (for Reinforced Uplink)

<td>Name of the element Information / Group</td><td>Needed</td><td>Multi</td><td>Type i reference</td><td>Semantic description</td><td>Version</td>

<td>Signature available</td><td>MD</td><td></td><td>Bit series</td><td>The default value is</td><td>REL-8</td>

<td></td><td></td><td></td><td> (16)</td><td>inverse order bits indicated in IE "Accessible Signature" in IE "PRACH Info (for RACH)" Each bit indicates availability for the signature. Each available signature on AICH is affiliated with one Configuration Joint E-DCH resources in the "list of resource configuration information Common E-DCH ".</td><td></td>

<td>E-AI Indication</td><td>MP</td><td></td><td>BOOLEAN</td><td>TRUTH: E-Al are in use on AICH. FALSE: E-Al are not in use on AICH.</td><td>REL-8</td>

<td>Code number</td><td>MD</td><td></td><td>integer</td><td>The default value is</td><td>REL-8</td>

<td>scramblingu</td><td></td><td></td><td> (0.15)</td><td>value indicated in IE "</td><td></td>

<td>preamble</td><td></td><td></td><td></td><td>Scrambling code number</td><td></td>

<td></td><td></td><td></td><td></td><td>preamble "in IE" PRACH Info (for RACH) " Scrambling code identification, see [28]</td><td></td>

<td>Available number</td><td>MD</td><td></td><td>Bit series</td><td>The default value is this</td><td>REL-8</td>

<td>subchannel</td><td></td><td></td><td rowspan="2"> (12)</td><td>same indicated value</td><td></td>

<td></td><td></td><td></td><td>in IE "Available Signatures" in IE "list of information system PRACH ". Each bit indicates availability for the subchannel, where sub-channels are numbered "sub-channel 0" to "subchannel 11". Value 1 bit indicates that the corresponding channel is available and value 0 indicates that it is not available.</td><td></td>

<td>PRACH partitioning</td><td>MD</td><td></td><td>PRACH partitioning 10.3.6.53</td><td>The default value is the "PRACH partitioning" value in the first instance in the "list of PRACH system information" list in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Life scaling factors</td><td>OP</td><td></td><td>coefficients scaling durability 10.3.6.48</td><td>This IE should not be present as soon as ASC 0 and ASC 1 are defined. If this IE is absent, the default value is the value "durability scaling factors" in the first occurrence in the list "PRACH system information list" in SIB5 or SIB5bis, if the value exists</td><td>REL-8</td>

<td>AC-to-ASC mapping</td><td>MD</td><td></td><td>ACdo-ASC mapping 10.3.6.1</td><td>The default value is the "ACdo-ASC mapping" value in the first instance in the "list of PRACH system information" list in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Main power of CPICH TX</td><td>MD</td><td></td><td>Main power of CPICH TX 10.3.6.61</td><td>The default value is the "CPICH TX Main Power" value in the first occurrence in the "PRACH system information list" list in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Fixed value</td><td>MD</td><td></td><td>Fixed value 10.3.6.11</td><td>The default value is the "Fixed value" value in the first occurrence in the "list of PRACH system information" list in SIB5 or SIB5bis</td><td>REL-8</td>

<td>PRACH power offset</td><td>MD</td><td></td><td>PRACH power offset 10.3.6.54</td><td>The default value is the "PRACH power offset" value in the first occurrence in the "list of PRACH system information" list in SIB5 or SIB5bis</td><td>REL-8</td>

<td>PRACH transmission parameters</td><td>MD</td><td></td><td>RACH transmission parameters 10.3.6.67</td><td>The default value is the "RACH transmission parameters" value in the first instance in the "list of PRACH system information" list SIB5 or SIB5bis.</td><td>REL-8</td>

<td>AICH info</td><td>MD</td><td></td><td>AICH info 10.3.6.2</td><td>The default value is the "AICH info" value in the first instance in the "list of PRACH system information" list SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Pp-e power offset</td><td>MP</td><td></td><td>Integer (-5..10)</td><td>In dB. Power offset between the last preamble transmitted and the initial DPCCH transmission as defined in [26]</td><td>REL-8</td>

E-HICH Info for the Joint E-DCH

<td>Name of the element information / Groups</td><td>Needed</td><td>Multi</td><td>Type i reference</td><td>Semantic description</td><td>Version</td>

<td>Sewer Code</td><td>Short-CV</td><td rowspan="3"></td><td rowspan="3">number whole (0..127)</td><td rowspan="2">For the first occurrence, if this IE is not present,</td><td rowspan="3">REL-8</td>

<td rowspan="2"></td><td rowspan="2"></td>

<td>the value of this IE is last value IE "Sewer Code" present in IE "Common system info E-DCH ". For subsequent instances, if IE is not present, the value is equal last speech this IE.</td>

<td>Sequence</td><td rowspan="3">MD</td><td rowspan="3"></td><td rowspan="3">number whole (0..39)</td><td rowspan="3">Note 1</td><td rowspan="3">REL-8</td>

<td>The signature</td>

<td></td>

<td colspan="6"></td>

<td colspan="3">Short</td><td colspan="3">If IE "Common E-DCH system info" is not present, this IE is mandatory for the first occurrence. Otherwise, this IE is optional.</td>

NOTE1: The default value is defined by:

Signature sequence = (offset + item in the common resource list E = DCH) mod 40 where "offset" is the value of the last IE instance "Signature Sequence". If "Signature Sequence" was not present in the first case, "offset" is zero.

"E-DCH Common Resource List Item" indicates the number of the E-DCH Common Resource Configuration Information in order of occurrence. The value of the "E-DCH Common Resource List Item" is zero for the first case.

IE "E-DPCH info" and "DPCH code info in Uplink for Common E-DCH" may not be changed compared to the first solution.

The coding enhancements of each IE present in the "Common E-DCH System Info" are independent of other IE.

Fig. 4 is a block diagram illustrating the base station 12 in accordance with the present embodiments. To support the above downlink control signaling, base station 12 in some embodiments includes one or more transmit / receive antennas 402, along with associated transmitter (TX) 404 and receiver (RX) 401, respectively, and also includes one or more. 403 processing circuits. The processing circuit 403 of base station 12 encodes system information that indicates the available CB channel resources relative to other available CB channel resources, e.g., relative to the position at which other available resources are indicated in the system information, rather than indicating each resource independently. In some embodiments, for example, available resources are indicated in an ordered list, and processing circuit 403 encodes system information to indicate available resources as a function of their position in the list relative to other resources. This may require, for example, inhibition of coding that directly indicates some access request preambles. The TX 404 circuit is then configured to transmit encoded system information to 10 - 10-N mobile terminals via transmit antennas 402.

In some embodiments, the processing circuit 403 is also configured to encode system information that directly indicates the access request preambles for one of the CB channels and which indirectly indicates the access request preambles for another CB channel based or as a function of the directly indicated preambles. The TX 404 circuit then transmits this system information in quite the same way as described above. This may require, for example, inhibition of coding that directly indicates some access request preambles.

Thus, base station 12 for managing access to the wireless communication network is shown in Fig. 4. Base station 12 includes a processing circuit 403 configured to encode system information indicating a second available contention-based channel resource relative to the first available contention-based channel resource. Also, base station 12 includes a TX 404 circuit configured to transmit system information. The contention-based channel in certain embodiments corresponds to a random access channel, RACH, or a joint Reinforced Dedicated Channel, E-DCH. Further, system information may be contained in System Information Block type 5, SIB5. The second available resource is in some embodiments indicated in the ordered resource list as a function of the position of the first available resource in the ordered list. An ordered list can define the resources of a joint Dedicated Reinforced Channel, E-DCH. Each E-DCH Resource can in turn be defined by the Soffset information element, Fractional Dedicated Physical Control Channel, FDPCH, the information element code number, and the Hybrid Channel info element

Confirmation Indicator Request Automatic Confirmation E-DCH, E-HICH, for joint EDCH. In some embodiments, the position of the second available resource in the ordered list is defined by the default value in the Soffset information element. The default value can be a function of the position of the second available resource in an ordered list; a function of the "Soffset" value of the previous first available resource; or a function of the position of the second available resource and the offset value. The offset value is the Soffset value of the first available resource. The information element F-DPCH code number can be the same for up to ten common E-DCH resources. In some embodiments, the E-HICH info information element for a common E-DCH is defined by a sewage code and signature sequence. The default signature sequence value may be a function of the position of the second available resource in the ordered list; a function of the "Signature Sequence" value of the previous first available resource; or a function of the position of the second available resource and the "Signature Sequence" value of the previous first available resource. In some embodiments, the sewer code of the second available resource is equal to the sewer code of the first available resource. The second available resource is in some embodiments defined by the value in the information element scrambling code in the Dedicated Physical Control Channel in the uplink. The value can be a function of the position of the second available resource in the ordered list of common E-DCH resources; the function of the value of the information element scrambling code of the Dedicated Physical Control Channel in the uplink of the previous first available resource or the function of the position of the second available resource and the value of "DPCH code info in the uplink for the Common E-DCH" in the information element scrambling code of the Dedicated Physical Control Channel in the uplink of the previous first available resource.

Fig. 5 is a flow diagram illustrating a method in a mobile terminal for requesting access to a wireless communication system in accordance with the present embodiments.

Step 501. The mobile terminal receives broadcast system information that indicates the first available channel resource on the basis of competition. In some embodiments, the contention-based channel corresponds to a random access channel, RACH, or a joint Reinforced Dedicated Channel, E-DCH. In some embodiments, the received broadcast system information is included in a Type 5 System Information Block, SIB5.

Step 502. Mobile terminal 10 outputs the second available contention-based channel resource based on the first available contention-based channel resource. The common E-DCH resource can be defined as UL scrambling code, F-DPCH code number and 'Soffset' time offset, E-HICH sewage codes and signature sequences, etc.

In some embodiments, the second available resource is indicated in the ordered resource list as a function of the position of the first available resource in the ordered list.

In some embodiments, the ordered list defines the resources of a common Reinforced Dedicated Channel, E-DCH, which each E-DCH Resource is defined by the Soffset information element, the Fractional Dedicated Physical Control Channel, the F-DPCH, the code number information element, and the info element information Hybrid Channel Confirmation Request Indicator, Automatic Confirmation E-DCH, E-HICH, for the common information element EDCH.

In some embodiments, the position of the second available resource in the ordered list is defined by the default value in the Soffset information element, which default value is a function of the position of the second available resource in the ordered list, a function of the value "Soffset" of the previous first available resource, or a function of the position of the second available resource and offset value, which offset value is the Soffset value of the first available resource.

In some embodiments, the information element F-DPCH code number is the same for up to ten common E-DCH resources.

In some embodiments, the E-HICH info information element for a common E-DCH is defined by a sewage code and signature sequence, and the default value of the signature sequence is a function of the position of the second available resource in the ordered list, a function of the value of "Signature Sequence" of the previous first available resource, or a function of the position of the second available resource and the "Signature Sequence" value of the previous first available resource.

In some embodiments, the sewer code of the second available resource is equal to the sewer code of the first available resource.

In some embodiments, the second available resource is defined by the value in the information element scrambling code of the Dedicated Physical Control Channel in the uplink, which value is a function of the position of the second available resource in the ordered list of common E-DCH resources, function of the value in the information element scrambling code of the Dedicated Physical Control Channel in the uplink of the previous first resource or function of the position of the second available resource and the value "DPCH code info in the uplink for the Common E-DCH" in the information element scrambling code of the Dedicated Physical Control Channel in the uplink of the previous first available resource.

Considering a specific example in 3GPP specifications, the available resources comprise a combination of power control command channel time slot, power control command channel coding, and the like, with each available resource component pointed relative to the corresponding other available resource component.

&gt;&gt; E-DCH Common Resource Configuration Information list

This IE is a list that contains all defined common E-DCH resources. A maximum of 32 shared E-DCH resources can be included in this list. For each E-DCH shared resource defined, the following IEs are defined:

&gt;&gt;&gt; Soffset

This IE is MP IE, whose value is between 0 and 9. This value indicates the specific slot in the F-DPCH that contains the power control commands for the specific F-DPCH.

Instead of being MP, this IE in various embodiments is set to MD. If IE is not present, "Soffset" defaults. The default value is a function of the E-DCH common resource entry in the list, a function of the "Soffset" value of the previous EDCH common resource case, or a function of the E-DCH common resource entry and the "Soffset" value of the previous E-DCH common resource case. The first defined E-DCH common resource will occupy position 0 (or 1). The second defined E-DCH common resource will occupy position 1 (or 2). Similar reasoning will apply to other defined resources.

The specific implementation will be, for example, when the value "Soffset" for the first E-DCH common resource case defaults and the rest of the E-DCH common resource takes the last case value.

For example, a simple formula is shown below for setting default values ​​for each defined E-DCH common resource.

Soffset = (offset + item in the E-DCH common resource list) mod 10 where "offset" is the value of the last IE case "Soffset". If IE "Soffset" was not present in the first case, "offset" is zero.

"E-DCH Common Resource List Item" indicates the number of the E-DCH Common Resource Configuration Information in order of appearance. The value of the "E-DCH Common Resource List Item" can be zero (or one) for the first case.

If IE is present, the signaled value will overwrite the default value.

&gt;&gt;&gt; code number F-DPCH

This IE indicates the code to use for F-DPCH.

Instead of being MP, this IE is optional, value-based.

If the coding presented for Soffset is used, potentially, only three cases of the F-DPCH code number are needed, once for every 10 shared E-DCH resources. Hence, in the best configuration, only three cases will have to be present.

Thus, this IE in various embodiments is set to be conditioned by the value (CV) so that this IE is mandatory for the first occurrence. Alternatively, it should be mandatory for the first occurrence or if the default value is zero. Otherwise, this IE is optional. Additionally, if this IE is not present, the value is equal to the last instance of this IE.

If IE is present, the signaled value overrides the default value.

&gt;&gt;&gt;&gt; E-HICH info

E-HICH info contains two additional IE. Changes in this IE will cause impacts on Version 6 and Version 7 3GPP standards. To avoid impact in earlier versions, the new IE can be used instead: "E-HICH info for E-DCH". Only two IE will be needed because this feature only applies to FDD.

&gt;&gt;&gt; E-HICH info for joint E-DCH

Sewer code

This IE can be set as IE value-based (CV) so that IE is only mandatory for the first case and optional for the rest. If this IE is not present, the value is equal to the last occurrence of this IE.

If IE is present, the signaled value overrides the default value.

Signature sequence

The value of this IE is a number between 0 and 39. This IE in various embodiments is set to MD. If IE is not present, "Signature Sequence" will default.

The default value is a function of the E-DCH common resource entry in the list, a function of the "Signature Sequence" value of the previous E-DCH common resource case, or a function of the E-DCH common resource entry and the "Signature Sequence" value of the previous E-DCH common resource case. The first defined E-DCH common resource will occupy position 0 (or 1). The second defined E-DCH common resource will occupy position 1 (or 2). Similar reasoning will apply to other defined resources. A specific implementation may be, for example, if the "Signature sequence" for the first E-DCH common resource case defaults and the rest of the E-DCH common resource adopts the value function of the last IE case.

For example, a simple formula is shown below for setting default values ​​for each defined E-DCH common resource in which IE is not present.

Signature Sequence = (offset + item in the E-DCH common resource list) mod 40 where "offset" is the value of the last IE instance of "Signature Sequence". If "Signature Sequence" was not present in the first case, "offset" is zero.

"Item in the E-DCH Common Resource List" indicates the number of the E-DCH Common Resource Configuration Information in order of appearance. The value of the "E-DCH Common Resource List Item" is zero (or one) for the first case.

If IE is present, the signaled value overrides the default value.

&gt;&gt;&gt; DPCH code info in the uplink for the Common E-DCH

The scrambling code number is the current MP value. This IE takes up a relatively large number of bits for each E-DCH common resource. This IE in some embodiments is instead changed to value-based (CV), avoiding including such a large number of bits in the configured E-DCH common resource.

Value-based means that this IE is mandatory for the first occurrence. Otherwise, this IE is optional. Additionally, if this IE is not present, the value of this IE is a function of the last case. For example, it can be a function of the E-DCH common resource item in the E-DCH common resource list, a function of the "DPCH code info in the uplink for Common E-DCH" previous case of an E-DCH common resource, or a function of an E-DCH common resource item and "DPCH code info in uplink for Common E-DCH" values ​​of the previous E-DCH common resource case. The following formula illustrates how default values ​​can be set if IE is not included:

Scrambling code number = offset + item in the E-DCH common resource list where "offset" is the value of the last IE instance "scrambling code number". If "offset" was not present in the first case or occurrence, "offset" is zero.

"E-DCH Common Resource List Item" indicates the number of the E-DCH Common Resource Configuration Information in order of appearance. The value of the "E-DCH Common Resource List Item" is zero (or 1) for the first case.

If IE is present, the signaled value overrides the default value.

&gt;&gt; E-DPDCH info

E-DCH E-TFCI minimum setting

This IE is mandatory by default. If this IE is missing, then there is no minimum E-TFCI setting.

For E-DCH in CELL_FACH and Idle Mode, the UE will always send its message, especially CCCHs messages. Otherwise, the UE will be blocked and, potentially, the UE will be abandoned. It is clear that for E-DCH in CELL_FACH and Idle Mode, the E-DCH minimum E-TFCI setting will always be included and must necessarily be a number above zero (E-TFCI index 0 will only allow UE to send Serial Information).

Thus, the semantic description can be modified so that for CELL_FACH and Idle Mode (or for Enhanced Uplink in CELL_FACH and Idle Mode), if IE is not enabled, E-DCH, the minimum E-TFCI setting is set to a defined value. The only limitation for this value is that the value belongs to the set of values ​​defined in the E-TFCI table. The specific table to be used is indicated in IE "E-TFCI table index" also included in IE "E-DPDCH info". As already mentioned, an E-TFCI value of zero only allows the UE to transmit the Scheduling Information. Thus, the minimum reasonable E-TFCI value such that the UE may transmit user or control data of higher layers is an E-TFCI value of 1.

If IE is present, the signaled values ​​override the default value.

&gt;&gt; PRACH preamble control parameters for Reinforced Uplink

Available Signatures

This is IE of a series of bits and each bit indicates whether the signature is used or not. Signatures configured for RACH and included in IE "Available Signatures" are presented in IE "PRACH info (for RACH)". These signatures cannot be used for Reinforced Uplink in CELL_FACH and Idle Mode. IE "PRACH info (for RACH)" is included in the IE "PRACH System Information List", which is located in SIB5. "PRACH System Information List", "PRACH info (for RACH)" and "Available Signatures" are mandatory IE. Hence, they will always be included in SIB5.

IE "Available Signatures" contained in IE "PRACH preamble control parameters for Reinforced Uplink" is also a mandatory present value; however, in these embodiments, this IE is optional and takes the default value. This default value is the same or a function of another IE, e.g., "Available Signatures" available in IE "PRACH info (for RACH)".

As an example, the default value in various embodiments is the operation of the "NO" or "REVERSE" function of a series of bits contained in the "Available Signatures" present in IE "PRACH info (for RACH)".

An illustrative example is provided to explain the concept. If the value of IE "Available Signatures" contained in IE "PRACH info (for RACH)" is: 1111111100000000, then the default value of IE "Available Signatures" contained in IE "Common System Info E-DCH" will be the inverse bit action of (1111111100000000), which is equal to 0000000011111111. Thus, IE "available signatures" is set to mandatory default (MD) and the description semantics will say that the default value is the inverse set of bits indicated in IE "Available Signatures" in IE "PRACH Info (for RACH)". In other words, the available signatures for Reinforced Uplink in CELL_FACH are those signatures that are not used for RACH, unless IE is present.

In doing so, base station 12 inhibits the incorporation of this IE into IE "PRACH Preamble Control Parameters for Reinforced Uplink" and thereby reduces downlink control signaling. A mobile terminal 18 that does not receive such an IE nevertheless sets IE to the default value described above. If IE is present, the signaled values ​​override the default value.

Preamble scrambling code number

This IE is also included in IE "PRACH info (for RACH)". The present embodiments teach that the scrambling code for common E-DCH is the same as for RACH, at least by default. If it were different, the new preamble scrambling code number in various embodiments is a function of the preamble scrambling code number present in IE "PRACH info (for RACH)". Hence, this IE in some embodiments is MD and by default equal to IE "preamble scrambling code number" indicated in IE "PRACH info (for RACH)", and is Otherwise the IE function "preamble scrambling code number" indicated in IE "PRACH info (for RACH) ".

As in the previous case, base station 12 refrains from incorporating this IE into IE "PRACH preamble control parameters for Reinforced Uplink" and thereby reduces control signaling in the downlink. A mobile terminal 18 that does not receive such an IE nevertheless sets IE to the default value described above. If IE is present, the signaled values ​​override the default value.

Available Subchannel number

This IE is a series of bits. Each bit indicates availability for the subchannel, where the subchannels are numbered from "subchannel 0" to "subchannel 11". A value of 1 bit indicates that the corresponding subchannel is available and a value of 0 indicates that it is not available.

This IE is also included in IE "PRACH info (for RACH)". This IE in some embodiments is also set to MD. The mandatory default value is the IE function "PRACH info (for RACH)".

For example, this IE can be set equal to IE "Available Subchannel Number" indicated in IE "PRACH info (for RACH)". In another approach, the default value may be a function

REVERSE (or NOT) IE "Available Subchannel Number" indicated in IE "PRACH info (for RACH)" As in the previous case, base station 12 refrains from including this IE in IE "PRACH preamble control parameters for Reinforced Uplink" and thus reduces downlink control signaling. A mobile terminal 18 that does not receive such an IE nevertheless sets IE to the default value described above. If IE is present, the signaled values ​​override the default value.

Coding used previously suggested, IE structures "PRACH preamble control parameters for Reinforced Uplink" and other IE involved will result in the following, affected IEs are indicated by underlined text and non-affected IEs are defined in relation to 3GPP Technical Specification (TS) 25.331 section 10 version 10.0 .0:

Common E-DCH system info

<td>Name of the element information / Groups</td><td>Needed</td><td>Multi</td><td>Type and reference</td><td>Semantic description</td><td>Version</td>

<td>UL interference for joint EDCH</td><td>OP</td><td></td><td>UL interference 10.3.6.87</td><td></td><td>REL-8</td>

<td>Common E-DCH MAC-d flows</td><td>MP</td><td></td><td>MAC-d Common E-DCH 10.3.5.3b flows</td><td></td><td>REL-8</td>

<td>SELECTION mode</td><td>MP</td><td></td><td></td><td></td><td>REL-8</td>

<td>&gt; FDD</td><td></td><td></td><td></td><td></td><td>REL-8</td>

<td>parameters &gt;&gt;</td><td>MP</td><td></td><td>control parameters</td><td>Control Parameters</td><td>REL-8</td>

<td>control</td><td></td><td></td><td>PRACH preamble (for</td><td rowspan="2">physical signal</td><td></td>

<td>PRACH preamble</td><td></td><td></td><td>reinforced</td><td></td>

<td>(for reinforced</td><td></td><td></td><td>Uplink) 10.3.6.54a</td><td></td><td></td>

<td>uplink)</td><td></td><td></td><td></td><td></td><td></td>

<td>&gt;&gt; value allocation initial service</td><td>MP</td><td></td><td>Integer (0..37)</td><td>(0..37) indicates the E-DCH service assignment index as defined in [15].</td><td>REL-8</td>

<td>&gt;&gt; E-DCH Transmission Time Range</td><td>MP</td><td></td><td>Integer (2.10)</td><td>The unit is ms.</td><td>REL-8</td>

<td>&gt;&gt; E-AGCH Info</td><td>MP</td><td></td><td>E-AGCH Info 10.3.6.100</td><td></td><td>REL-8</td>

<td>&gt;&gt; HARQ info for EDCH</td><td>MP</td><td></td><td>HARQ info for E-DCH 10.3.5.7d</td><td></td><td>REL-8</td>

<td>&gt;&gt; control info by DPCH in uplink</td><td>MP</td><td></td><td>info controlling DPCH power in uplink for Common E-DCH 10.3.6.91a</td><td></td><td>REL-8</td>

<td>&gt;&gt; E-DPCCH info</td><td>MP</td><td></td><td>E-DPCCH Info 10.3.6.98</td><td></td><td>REL-8</td>

<td>&gt;&gt; E-DPDCH info</td><td>MP</td><td></td><td>E-DPDCH info</td><td></td><td>REL-8</td>

<td></td><td></td><td></td><td> 10.3.6.99</td><td></td><td></td>

<td>&gt;&gt; purpose of F-DPCH TPC degree of erroneous commands</td><td>MP</td><td></td><td>Real (0.01..0.1 step 0.01).</td><td>F-DPCH information in the downlink. Actual value dl-FDPCHTPCcommandErrorR ate = IE value * 0.01</td><td>REL-8</td>

<td>&gt;&gt; suspension of additional E-DCH transmission</td><td>MP</td><td></td><td>Integer (0..15)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>&gt;&gt; Maximum allocation of E-DCH resources for CCCH</td><td>MP</td><td></td><td>Numbered (8, 12, 16, 24, 32, 40, 80, 120)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>&gt;&gt; Maximum period for the collision resolution phase</td><td>MP</td><td></td><td>Integer (8..24)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>&gt;&gt; suspension of continuation of E-DCH transmission</td><td>MP</td><td></td><td>Numbered (0, 8, 16, 24, 40, 80, 120, low infinity)</td><td>In terms of TTI. If set to "infinity", the default E-DCH common resource version is disabled.</td><td>REL-8</td>

<td>&gt;&gt; ACK / NACK support on HSDPCCH</td><td>MP</td><td></td><td>boolean</td><td>TRUE indicates that HS-DPCCH should be used when a shared E-DCH resource is allocated to UE for DTCH / DCCH transmission after collision resolution. FALSE indicates that HS-DPCCH is not to be used.</td><td>REL-8</td>

<td>&gt;&gt; Feedback Measurement</td><td>OP</td><td></td><td>Measurement Feedback Info 10.3.6.40a</td><td></td><td>REL-8</td>

<td>&gt;&gt; Information List configuration resources Joint E-DCH</td><td>MP</td><td>1 to &lt;maksED CH&gt;</td><td></td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt; Soffset</td><td>MD</td><td></td><td>Integer (0..9)</td><td>(0..9) indicates</td><td>REL-8</td>

<td></td><td></td><td></td><td></td><td>symbol offset as defined in [26] Note 3</td><td></td>

<td>&gt;&gt;&gt; F-DPCH number</td><td>Short-CV</td><td></td><td>integer</td><td>If this IE is not</td><td>REL-8</td>

<td>code</td><td></td><td></td><td> (0..255)</td><td>present, value is equal last instance of this IE.</td><td></td>

<td>&gt;&gt;&gt; E-RGCH</td><td>OP</td><td></td><td>E-RGCH Info 10.3.6.102</td><td></td><td>REL-8</td>

<td>information</td><td></td><td></td><td></td><td></td><td></td>

<td>&gt;&gt;&gt; E-HICH info for</td><td>MP</td><td></td><td>E-HICH info for</td><td></td><td>REL-8</td>

<td>joint E-DCH</td><td></td><td></td><td>joint E-DCH 10.3.6.1xx</td><td></td><td></td>

<td>&gt;&gt;&gt; code info</td><td>MP</td><td>DPCH</td><td>DPCH code info in</td><td></td><td>REL-8</td>

<td>DPCH in the uplink</td><td></td><td></td><td>uplink for the Joint E-DCH 10.3.6.87b</td><td></td><td></td>

<td>&gt; TDD</td><td></td><td></td><td></td><td></td><td>REL-8</td>

<td>&gt;&gt; CHOICE TDD option</td><td>MP</td><td></td><td></td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt; 7.68 Mcps TDD</td><td></td><td></td><td>lack</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt; 3.84 Mcps TDD</td><td></td><td></td><td>lack</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt; 1.28 Mcps TDD</td><td></td><td></td><td></td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt; E-RUCCH Info</td><td>MP</td><td></td><td>E-RUCCH Info 1.28 Mcps TDD 10.3.6.103a</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt; E-PUCH info</td><td>MP</td><td></td><td>E-PUCH Info 1.28 Mcps TDD 10.3.6.104a</td><td>Note 1</td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt; E-HICH info</td><td>MP</td><td></td><td>E-HICH info 1.28 Mcps TDD 10.3.6.101a</td><td>Note 1</td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt; E-AGCH Info</td><td>MP</td><td></td><td>E-AGCH Info 1.28 Mcps TDD 10.3.6.100a</td><td>Note 1</td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt; HARQ info for E-DCH</td><td>MP</td><td></td><td>HARQ info for E-DCH 10.3.5.7d</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt; CCCH broadcast info</td><td>MP</td><td></td><td></td><td>Note 2</td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt;&gt; info of the Joint E-RNTI</td><td>MP</td><td></td><td>Info Joint E-RNTI 10.3.3.7a</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt;&gt; HARQ maximum number of retransmissions</td><td>MP</td><td></td><td>Integer (0..7)</td><td></td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt;&gt; HARQ retransmission timer</td><td>MP</td><td></td><td>Numbered (10,15,20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80, 85, 90, 95, 100, 110, 120, 140, 160)</td><td>Unit: ms</td><td>REL-8</td>

<td>&gt;&gt;&gt;&gt;&gt; HARQ power offset</td><td>MP</td><td></td><td>Integer (0..6)</td><td></td><td>REL-8</td>

<td colspan="6"></td>

<td>State</td><td colspan="5">Explanation</td>

<td>Short</td><td colspan="5">This IE is mandatory for the first occurrence. Otherwise, this IE is optional.</td>

<td colspan="6">NOTE1: These IE correspond to the HS-DSCH configuration for the CELL_FACH, CELL_PCH and URA_PCH state on the main frequency, the configuration on the secondary frequency is signaled to the UE via dedicated signaling. NOTE2: These IE correspond to the CCCH transmission configuration for the CELL_FACH state on the primary frequency and the secondary frequency. NOTE3: The default value is defined by: Soffset = (offset + item in the E-DCH common resource list) mod 10 where "offset" is the value of the last case of IE "Soffset". If IE "Soffset" was not present in the first case, "offset" is zero. "E-DCH Common Resource List Item" indicates the number of the E-DCH Common Resource Configuration Information in order of appearance. The value of the "E-DCH Common Resource List Item" is zero for the first case.</td>

&gt;&gt; E-DPDCH Info

<td>Name of the element information / Groups</td><td>Needed</td><td>Multi</td><td>Type and reference</td><td>Semantic description</td><td>Version</td>

<td>ETFCI table index</td><td>MP</td><td></td><td>Integer (0..1)</td><td>Indicates which ETFCI TB standardized size tables will be used. See. Note 3.</td><td>REL-6</td>

<td rowspan="2">E-DCH minimal E-TFCI setting</td><td rowspan="2">MD</td><td rowspan="2"></td><td rowspan="2">integer (0..127)</td><td>See. [15]; Absence</td><td rowspan="2">REL-6</td>

<td>means no minimum E-DCH settings. At CELL FACH AND Idle Mode, the default is 1.</td>

<td>E-TFCI Reference</td><td>MP</td><td>1 to 8</td><td></td><td>See. [29]</td><td>REL-6</td>

<td>&gt; E-TFCI references</td><td>MP</td><td></td><td>Integer (0..127)</td><td></td><td>REL-6</td>

<td rowspan="2">&gt; E-TFCI PO references</td><td rowspan="2">MP</td><td rowspan="2"></td><td>Integer (0..29,</td><td>Reference for power offset quantization in [28]</td><td>REL-6</td>

<td> 30, 31)</td><td>The values ​​30 and 31 are only used for E-TFCI&gt; ETFCI Boost</td><td>REL-7</td>

<td>Minimal E-DPDCH reduced profit factor</td><td>OP</td><td></td><td>Numbered (8/15, 11/15, 15/15, 21/15, 30/15, 42/15, 60/15, 84/15)</td><td>^eed, k, reduced, min ^{[29]; value}the default is 8/15. If the configurable EDPDCH reduced profit factor is not supported by the UE, the default value is used.</td><td>REL-8</td>

<td>Maximum sewage codes</td><td>MP</td><td></td><td>Numbered (sf256, sf128, sf64, sf32, sf16, sf8, sf4, 2sf4, 2sf2, 2sf2and2sf4)</td><td></td><td>REL-6</td>

<td>^ENnon-max</td><td>MP</td><td></td><td>Real (0.44 ..1.0 stage 0.04)</td><td>As defined in [27]</td><td>REL-6</td>

<td>Configuration information scheduling</td><td>MP</td><td></td><td></td><td></td><td>REL-6</td>

<td>&gt; Periodicity for scheduling info - no assignment</td><td>MD</td><td></td><td>Numbered (each EDCHT TI, 4,10,20.50, 100,200, 500,1 000)</td><td>Values ​​in ms. The default value is "no report". NOTE 1.</td><td>REL-6</td>

<td>&gt; Periodicity for scheduling info - allocation</td><td>MD</td><td></td><td>Numbered (each EDCHT TI, 4,10,20.50, 100,200,500,1000)</td><td>Values ​​in ms. The default value is "no report" NOTE1.</td><td>REL-6</td>

<td>&gt; Power Offest for Scheduling Info</td><td>MP</td><td></td><td>Integer (0..6)</td><td>Used only when no MACd PDUs are included in the same MACe PDU. Units are in dB.</td><td>REL-6</td>

<td>3-Index Stage Threshold</td><td>MD</td><td></td><td>Integer (0..37)</td><td>Refers to the index in the "SGTable" (see [15]). The default value is 0. NOTES 2, 3.</td><td>REL-6</td>

<td>2-Index Stage Threshold</td><td>MD</td><td></td><td>Integer (0..37)</td><td>Refers to the index in the "SGTable" (see [15]). The default value is 0. NOTES 2, 3.</td><td>REL-6</td>

<td>NOTE 1:</td><td colspan="5">If Periodicity is set to 4ms and E-DCH TTI is set to 10ms, the UE will interpret the periodicity value as 10ms.</td>

<td>NOTE 2:</td><td colspan="5">If the value of the 3-Index Stage Threshold is greater than the 2-Index Stage Threshold, the UE behavior is undefined.</td>

<td>NOTE 3:</td><td colspan="5">If the UE is in 16QAM mode, the "E-TFCI table index" value is increased by 2, and the indexes in the SG-Table relate to Schedule Assignment Table 2 in [15].</td>

&gt;&gt;&gt; E-HICH Info for the Joint E-DCH

<td>Information Item / Group Name</td><td>Needed</td><td>Multi</td><td>Type i reference</td><td>Semantic description</td><td>Version</td>

<td>Sewer Code</td><td>Short-CV</td><td rowspan="2"></td><td rowspan="2">number whole (0..127)</td><td rowspan="2">If this IE is not present, the value is equal to the last one instance of this IE.</td><td rowspan="2">REL-8</td>

<td></td><td></td>

<td>Sequence</td><td rowspan="3">MD</td><td rowspan="3"></td><td rowspan="3">number whole (0..39)</td><td rowspan="3">Note 1</td><td rowspan="3">REL-8</td>

<td>The signature</td>

<td></td>

<td colspan="3">Short</td><td colspan="3">This IE is mandatory for the first occurrence. Otherwise, this IE is optional.</td>

<td colspan="6">NOTE1: The default value is defined by: Signature sequence = (offset + position in the E-DCH common resource list) mod 40 where "offset" is the value of the last IE instance "Signature Sequence". If "Signature Sequence" was not present in the first occurrence, "offset" is zero. "E-DCH Common Resource List Item" indicates the number of the E-DCH Common Resource Configuration Information in order of appearance. The value of "E-DCH Common Resource List Item" is zero for the first occurrence.</td>

&gt;&gt;&gt; DPCH code info in the uplink for the Common E-DCH

<td>Information Item / Group Name</td><td>Needed</td><td>Multi</td><td>Type and reference</td><td>Description semantic</td><td>Version</td>

<td>Scrambling code type</td><td>MP</td><td></td><td>Numbered (short, long)</td><td></td><td>REL-8</td>

<td>Code number</td><td>Short-CV</td><td rowspan="2"></td><td>Integer (0..16</td><td>Note 1</td><td rowspan="2">REL-8</td>

<td>scramblingu</td><td></td><td> 777215)</td><td></td>

<td colspan="6"></td>

<td colspan="6">Status Explanation</td>

<td>Short</td><td>This IE is mandatory for the first occurrence. Otherwise, this IE is optional.</td>

<td colspan="2">NOTE1: If this IE is not included, the value is given by: Scrambling code number = offset + item in the E-DCH common resource list where "offset" is the value of the last instance of IE "scrambling code number". If IE "scrambling code number" is not present in the first occurrence, "offset" is zero. "E-DCH Common Resource List Item" indicates the number of the E-DCH Common Resource Configuration Information in order of appearance. The value of the "EDCH Common Resource List Item" is zero for the first case.</td>

As stated above, mobile terminal 10 may output access request preambles for one CB channel, e.g., a non-legacy CB channel, such as E-DCH, on a base or as a function of directly indicated access request preambles for another CB channel, e.g. legacy like RACH.

Changed IEs are indicated by the underlined text:

&gt;&gt; PRACH preamble control parameters (for Reinforced Uplink)

<td>Information Item / Group Name</td><td>Needed</td><td>Multi</td><td>Type i reference</td><td>Semantic description</td><td>Version</td>

<td rowspan="4">Signature available</td><td rowspan="4">MD</td><td rowspan="4"></td><td rowspan="4">Number bits (16)</td><td>The default value is the inverse series of bits indicated in IE "Available</td><td rowspan="4">REL-8</td>

<td>Signature "in IE" PRACH Info</td>

<td>(for RACH) ". Every bit</td>

<td>indicates availability for signature. Each available the signature on AICH is associated with one E-DCH Common Resource Configuration in the "list E-DCH Common Resource Configuration Information. "</td>

<td>E-AI Indication</td><td>MP</td><td></td><td>BOOLEAN</td><td>TRUTH: E-Al are in use on AICH. FALSE: E-Al are not in use on AICH.</td><td>REL-8</td>

<td rowspan="4">Code number scramblingu preamble</td><td rowspan="4">MD</td><td rowspan="4"></td><td rowspan="4">integer j £ L 15)</td><td>The default value is value indicated in IE "scrambling code number</td><td rowspan="4">REL-8</td>

<td>preamble "in IE" PRACH Info</td>

<td>(for RACH) ". Identification</td>

<td>scrambling code, see [28]</td>

<td>Available number subchannel</td><td>MD</td><td></td><td>Bit series (12)</td><td>The default value is this the same value indicated in IE "Available Signatures" in IE "list of PRACH system information". Each bit indicates availability for subchannel, where they were subchannels are numbered "subchannel 0 "to" subchannel 11 ". A value of 1 bit indicates that corresponding subchannel is available and value 0 indicates that it is not available.</td><td>REL-8</td>

<td>PRACH partitioning</td><td>MD</td><td></td><td>PRACH partitioning 10.3.6.53</td><td>The default value is "PRACH partitioning "in the first instance in the" list of PRACH system information "in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Life scaling factors</td><td>OP</td><td></td><td>coefficients scaling durability 10.3.6.48</td><td>This IE will not be present as soon as ASC 0 and ASC 1 are defined. If this IE is missing, the default value is the value "Durability scaling factors" in the first occurrence in the list "PRACH system information list" in SIB5 or SIB5 bis, if the value exists</td><td>REL-8</td>

<td>AC-to-ASC mapping</td><td>MD</td><td></td><td>ACdo-ASC mapping 10.3.6.1</td><td>The default value is the "ACdo-ASC mapping" value in the first instance in the "list of PRACH system information" list in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Main power of CPICH TX</td><td>MD</td><td></td><td>Main power of CPICH TX 10.3.6.61</td><td>The default value is the "Main power CPICH TX "in the first occurrence in the list" PRACH system information list "in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Fixed value</td><td>MD</td><td></td><td>Fixed value 10.3.6.11</td><td>The default value is the "Fixed value" value in the first occurrence in the "list of PRACH system information" list in SIB5 or SIB5bis</td><td>REL-8</td>

<td>PRACH power offset</td><td>MD</td><td></td><td>PRACH power offset 10.3.6.54</td><td>The default value is the "PRACH power offset" value in the first occurrence in the "list of PRACH system information" list in SIB5 or SIB5bis</td><td>REL-8</td>

<td>PRACH transmission parameters</td><td>MD</td><td></td><td>RACH transmission parameters 10.3.6.67</td><td>The default value is the "RACH transmission parameters" value in the first occurrence in the "list of PRACH system information" list in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>AICH info</td><td>MD</td><td></td><td>AICH info 10.3.6.2</td><td>The default value is the "AICH info" value in the first instance in the "list of PRACH system information" list in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Pp-e power offset</td><td>MP</td><td></td><td>Integer (-5..10)</td><td>In dB. Power offset between the last preamble transmitted and the initial DPCCH transmission as defined in [26]</td><td>REL-8</td>

The coding code, e.g. the ASN 1 code, can be updated as below only when the relevant IE has been added:

SEQUENCE {

BOOLEAN,

PICH-PowerOffset,

CHOICE (-.

'SEOUENCE {. '

Alchemy-PowerOffset

SysInfoType5 :: = sib6indicator - Physical · channel · IEs pich-PowerOffset modeSpecificlnfo fdd a ich-PowerOffset},.

tdd. 'SEOUENCE {

- If PDSCH / PUSCH is configured for 1.28Mcps or 7.68Mcps TDD, the fotlowing IEs should be absent ·. . ·.

- and the info included in the respective tddl28Specificlnfo .or tdd768Specificlnfo rnstead.

be

If PDSCH / PUSCH is configured for 3.84Mcps TDD in R5, HCR-r5-SpecificInfo should aiso included. · Pusch-SysInfoList-SFN pdsch-SysInfoList-SFN openLoopPowerControi-TDD

PUSCH-SyslnfoList-SFN PDSCH-SyslnfoList-SFN OpenLoopPowerControl-TDD

OPTIONAL,

OPTIONAL, l ·, prinaryCCPCH-Info prach-Systal nformationList sCCPCH-Sys ter nf ormationList

OPTIONAL,

Prim.aryCCPCH-Inf o

PRACH-SystemlnformationList,.

SCCPCH-SystemlnformationList,.

- cbs-DRX-LevelIInformation is conditional 'on any of the CTCH indicator IEs in - sCCPCH-SystemInformationList -

CBS-DRX-LevellInformation cbs-DRX-Levell · Information Extension mechanism for non- release99 Information ..

v4bONonCriticalExtensions. SEOUENCE (.. ·· syslnfoType5-v4b0ext SyslnfoType5-v4b0ext-IEs - Extension mechanism for non- rei-4 Information

OPTIONAL, v590NonCriticaIExtensions syslnfoType5-v590ext v650NonCriticalExtensións sysInfoType5-v650ext

SEOUENCE (.

SyslnfoType5-v590ext-IEs · SEOUENCE ('

SysInfoType.5-v65 0ext-IEs

OPTIONAL,

OPTIONAL, '' OPTIONAL, v890ext-IEs, v8b0ext-IEs v68CNonCriticalExtens! Ons sysInfoType5-v580ext

SEOUENCE {'• SyslnfcType5-v68Oext-IEs v690NonCriticalExtensions syslnfoType5-v69Oext v770NonCrioicalExtensions sysInfoType5-v7 7 0ext' v8 60NonCriticalExtensions • syslnfoText5-v8

SEOUENCE {·.

SyslnfoType5-v690ext-IEs, SEOUENCE [''

SysInfoType5-v770ext-IEs, SEOUENCE {

SysInfoType5-v860extv8 90NonCriticaiExtensions. syslnfoType5-v8 9Oext v8bONonCriticalExtensions sysInfoType5-v8b0ext

SEOUENCE {· .SyslnfoType5 • v8cONonCriticalExtensions'. syslnfoType5-v8c0ext. 'nonCritical.Extensions l · OPTIONAL} OPTIONAL} OPTIONAL') OPTIONAL}. OPTIONAL} OPTIONAL

OPTIONAL} OPTIONAL. OPTIONAL '.

OPTIONAL

SEOUENCE (

SysZnfoType5SEQUENCE {

SEQUENCE {

OPTIONĄb

SysInfoType5-v890ext-IEs :: = SEOUENCE {secondFreguehcylnfo

FreguencyInfoTDD '- The field' dummy 'shali be marked absent in SysInfoType5 and SysInfoType5bis. A failure to

- comply with this requirement may prevent the UE to reoeive any service in the celi. The UE.

- may treat the celi as barred.

dummy 'SEOUENCE (}' OPTIONAL.

and . '' '.

<img file="PL2622929T3_D0001.tif" />

PRACH-PreambleForEnhancedUplink :: = availableSignatures 'e-ai-Indication preambleScramblingCodeWordNumber availableSubChannelNumbers prach-Partitiohing persistenceScalingFactorList ac-To-ASC-MappingTable primaryCPICH-TX-Power' constantValue.

prach-PowerOffset rach-TransmissionParameters aich-Info ·. .

powerOffsetPp-e. '

SEOUENCE. (..

AvailableSignatures BOOLEAN, '

PreambleScramblingCodeWordNumber AvailableSubChannelNumbers. PRACH-Partitioning-r7 PersistenceScalingFactorList AC-To-ASC-MappingTable PrimaryCPICH-TX-Power ConstantVaiue. ''

PRACH-PowerOffset. RACH-TransmissionParameters

AICH-Info

INTEGER (-5..10)

OPTIONAL,

OPTIONAL,

OPTIONAL,

OPTIONAL,

OPTIONAL,

OPTIONAL,

OPTIONAL,

OPTIONAL,

OPTIONAL,

OPTIONAL,

OPTIONAL,

Common-E-DCH-ResourcelnfoList:: = s-offset f-dpch-ChannelisationCodeNumber e-RGCH-Information e-hich-Info ul-DPCH-CodeInfoForCommonEDCH}. and'

SEOUENCE {

INTEGER (0..9)

INTEGER (0..255) '

E-RGCH-Information '.

E-HICH-Information-CommonEdch UL-DPĆH-CodelnfoForCommonEDCH

OPTIONAL,

OPTIONAL,

OPTIONAL,

UL-DPCH-CodeInfoForCommonEDCH ul-DPCCHscramblingCodeType ul-DPCCHscramblingCode

SEQUENCE (

ScramblingCodeType,

UL-ScramblingCode

OPTIONAL

E-HICH-Information-CommonEdch :: = .'channelisationCode '

OPTIONAL, '.

signatureSequence OPTIONAL '

SEOUENCE (

E-HICH-ChannelisationCode

E-HICH-RGCH-SignatureSequence

In some embodiments, a second approach may be adopted to provide a backward stable solution.

In this case, a new IE must be added in SIB5, for example, "Common E-DCH Short System Information". This new IE may contain new encoding.

Tabulated SIB5 will be as follows:

System Information Block type 5 and 5bis

<td>Information Item / Group Name</td><td>Needed</td><td>Multi</td><td>Type i reference</td><td>Semantic description</td><td>Version</td>

<td>SIB6 indicator</td><td>MP</td><td></td><td>boolean</td><td>TRUTH indicates that SIB6 is transmitted in a cell.</td><td></td>

<td></td><td></td><td></td><td></td><td>When the UE receives the SIB5 in the System Information Container message, this IE is interpreted as FALSEHOOD</td><td></td>

<td>PhyCH information elements</td><td></td><td></td><td></td><td></td><td></td>

<td>PICH power offset</td><td>MP</td><td></td><td>Power offset PICH 10.3.6.50</td><td>If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3 UE behaves as if this IE was not received.</td><td></td>

<td>SELECTION mode</td><td>MP</td><td></td><td></td><td></td><td></td>

<td>&gt; FDD</td><td></td><td></td><td></td><td></td><td></td>

<td>&gt;&gt; AICH power offset</td><td>MP</td><td></td><td>AICH power offset 10.3.6.3</td><td>If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3 UE behaves as if this IE was not received.</td><td></td>

<td>&gt; TDD</td><td></td><td></td><td></td><td></td><td></td>

<td>&gt;&gt; PUSCH system information</td><td>OP</td><td></td><td>information System PUSCH 10.3.6.66</td><td>If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3, the UE's behavior after receiving this IE is undefined.</td><td></td>

<td>&gt;&gt; PUSCH VHCR system information</td><td>OP</td><td></td><td>PUSCH system information VHCR 10.3.6.66 and</td><td>Only for 7.68 Mcps TDD. If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3, the UE's behavior after receiving this IE is undefined.</td><td>REL-7</td>

<td>&gt;&gt; PDSCH system information</td><td>OP</td><td></td><td>PDSCH information System 10.3.6.46</td><td>If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3, the UE's behavior after receiving this IE is undefined.</td><td></td>

<td>&gt;&gt; TDD open-loop power control</td><td>MP</td><td></td><td>TDD control power in open loop 10.3.6.79</td><td>If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3 UE behaves as if this IE was not received.</td><td></td>

<td>Main CCPCH info</td><td>OP</td><td></td><td>Main info CCPCH 10.3.6.57</td><td>Note 1 I</td><td></td>

<td>List of PRACH system information</td><td>MP</td><td></td><td>Information List system PRACH 10.3.6.55</td><td>If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3 UE behaves as if this IE was not received.</td><td></td>

<td>Common E-DCH system info</td><td>OP</td><td></td><td>Common EDCH system info 10.3.6.9a</td><td></td><td>REL-8</td>

<td>Short joint system info E-DCH</td><td>OP</td><td></td><td>Short info systemic joint EDCH 10.3.6.9b</td><td></td><td>REL-8</td>

<td rowspan="2">Secondary CCPCH system information</td><td>MP</td><td></td><td rowspan="2">secondary information System CCPCH 10.3.6.72</td><td>Note 2</td><td></td>

<td></td><td></td><td>When the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3, the UE behaves as if this IE was not received.</td><td></td>

<td>Information CBS DRX Level 1</td><td>CV-CTCH</td><td></td><td>Information CBS DRX Level 1 10.3.8.3</td><td></td><td></td>

<td>Frequency band indicator</td><td>OP</td><td></td><td>Indicator bandwidth frequency 10.3.6.35 b</td><td></td><td>REL-6</td>

<td>Frequency band indicator 2</td><td>OP</td><td></td><td>Indicator bandwidth frequency 2 10.3.6.35 c</td><td></td><td>REL-6</td>

<td>HSDPA cell indicator</td><td>MD</td><td></td><td rowspan="3">numbered (Cell HSDPA capable)</td><td>The default is 'no HSDPA capability'.</td><td>REL-6</td>

<td></td><td></td><td></td><td>'Cell capable of HSDPA 'means that the UE may consider this cell as part of the HSDPA coverage area only for displaying the indication.</td><td></td>

<td></td><td></td><td></td><td>This indication will not be used for any other purpose.</td><td></td>

<td></td><td></td><td></td><td></td><td>If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3 UE behaves as if this IE was not received.</td><td></td>

<td>EDCH cell indicator</td><td>MD</td><td></td><td rowspan="4">numbered (Cell EDCH capable)</td><td>The default is 'E-DCH capability not indicated'.</td><td>REL-6</td>

<td></td><td></td><td></td><td>'EDCH Capable Cell' means that the UE may consider this cell as part of the EDCH coverage area only for displaying indication.</td><td></td>

<td></td><td></td><td></td><td>This indication will not be used for any other purpose.</td><td></td>

<td></td><td></td><td></td><td>If the cell is operating in MBSFN mode as indicated in sub-clause 8.1.1.6.3 UE behaves as if this IE was not received.</td><td></td>

<td>Secondary CCPCH MBMS system information</td><td>OP</td><td></td><td>Secondary system information CCPCH MBMS 10.3.6.72 a</td><td>Contained if MCCH is on S-CCPCH used only for MBMS. Note 2</td><td>REL-6</td>

<td>SELECTION mode</td><td>OP</td><td></td><td></td><td></td><td>REL-7</td>

<td>&gt; FDD</td><td></td><td></td><td></td><td></td><td>REL-7</td>

<td>&gt;&gt; HS-DSCH ordinary system information</td><td>MP</td><td></td><td>HS-DSCH usually information System 10.3.6.36 c</td><td>Included if the cell supports receiving HSDSCH in CELL_FACH and during the transition from STERILE to RRC connection.</td><td>REL-7</td>

<td>&gt;&gt; HS-DSCH recalling system information</td><td>OP</td><td></td><td>HS-DSCH mentioning information System 10.3.6.36 d</td><td>Included if the cell supports UE in RRC connection state calling for receiving messages on HS-DSCH.</td><td>REL-7</td>

<td>&gt; TDD</td><td></td><td></td><td></td><td></td><td>REL-7</td>

<td>&gt;&gt; HS-DSCH ordinary system information</td><td>MP</td><td></td><td>HS-DSCH ordinary system information 1.28Mcps TDD 10.3.6.36 ca</td><td>Included if the cell supports receiving HSDSCH in CELL_FACH and during the transition from STERILE to RRC connection.</td><td>REL-8</td>

<td>&gt;&gt; HS-DSCH recalling system information</td><td>OP</td><td></td><td>HS-DSCH recalling 1.28Mcps TDD system information 10.3.6.36 da</td><td>Contained if the cell supports UE in RRC Connection state calling for receiving messages on HS-DSCH.</td><td>REL-8</td>

<td>TDD MBSFN information</td><td>OP</td><td></td><td>TDD MBSFN Information 10.3.6.78 b</td><td>TDD only: only included when some time periods are intended for MBSFN.</td><td>REL-7</td>

<td>HS-DSCH DRX in CELL_FACH Information</td><td>OP</td><td></td><td>HS-DSCH DRX in CELL_FA CH Information 10.3.6.36 q</td><td></td><td>REL-8</td>

<td>HS-DSCH DRX in CELL_FACH Information 1.28 Mcps TDD</td><td>OP</td><td></td><td>HS-DSCH DRX at CELL_FA CH Information 1.28 Mcps TDD 10.3.6.36 h</td><td></td><td>REL-8</td>

<td>Second Frequency Info</td><td>OP</td><td></td><td>number total (0 .. 16383)</td><td>Note 3</td><td>REL-8</td>

<td>Treset Use Indicator</td><td>OP</td><td></td><td>numbered (TRUTH)</td><td>Only for 1.28 Mcps TDD. The presence of this IE means that the Timer Treset is not valid when the dedicated H-RNTI is configured in CELL FACH and CELL PCH.</td><td>REL-8</td>

<td>UpPCH Position Info</td><td>CVCzęstotliwość</td><td></td><td>number total (0 .. 127)</td><td>Only for 1.28 Mcps TDD.</td><td>REL-8</td>

The new IE can then be defined as follows:

Brief system info of the Joint E-DCH

NOTE: Only for FDD.

<td>Information Item / Group Name</td><td>Needed</td><td>Multi</td><td>Type i reference</td><td>Semantic description</td><td>version</td>

<td>UL interference for common E-DCH</td><td>CVOpcjonalny</td><td></td><td>UL interference 10.3.6.87</td><td></td><td>REL-8</td>

<td>Common E-DCH MAC-d flows</td><td>CVObowiązkowy</td><td></td><td>Common EDCH MAC-d flows 10.3.5.3b</td><td></td><td>REL-8</td>

<td>PRACH preamble control parameters (for Reinforced Uplink)</td><td>CVObowiązkowy</td><td></td><td>parameters control preamble PRACH (for reinforced uplink) 10.3.6.54a</td><td>Control parameters of the physical signal.</td><td>REL-8</td>

<td>Initial Service allocation value</td><td>CVObowiązkowy</td><td></td><td>Integer (0..37)</td><td>(0..37) indicates the E-DCH service assignment index as defined in [15].</td><td>REL-8</td>

<td>E-DCH Transmission Time Interval</td><td>CVObowiązkowy</td><td></td><td>number whole (2.10)</td><td>The unit is ms.</td><td>REL-8</td>

<td>E-AGCH Info</td><td>CVObowiązkowy</td><td></td><td>E-AGCH Info 10.3.6.100</td><td></td><td>REL-8</td>

<td>HARQ info for E-DCH</td><td>CVObowiązkowy</td><td></td><td>HARQ info for E-DCH 10.3.5.7d</td><td></td><td>REL-8</td>

<td>Info controlling DPCH power in the uplink</td><td>CVObowiązkowy</td><td></td><td>Info controlling DPCH power in the uplink for Common EDCH 10.3.6.91a</td><td></td><td>REL-8</td>

<td>E-DPCCH info</td><td>CVObowiązkowy</td><td></td><td>E-DPCCH Info 10.3.6.98</td><td></td><td>REL-8</td>

<td>E-DPDCH info</td><td>CVObowiązkowy</td><td></td><td>E-DPDCH info 10.3.6.99</td><td></td><td>REL-8</td>

<td>Target F-DPCH TPC degree of erroneous commands</td><td>CVObowiązkowy</td><td></td><td>Real (0.01..0.1 step 0.01).</td><td>F-DPCH information in the downlink. Actual value dl-FDPCHTPCcommandErrorR ate = IE value * 0.01</td><td>REL-8</td>

<td>Suspending additional E-DCH transmissions</td><td>CVObowiązkowy</td><td></td><td>number whole (0..15)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>Maximum E-DCH resource allocation for CCCH</td><td>CVObowiązkowy</td><td></td><td>Numbered (8, 12, 16, 20, 24, 32, 40, 80)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>The maximum period for the collision resolution phase</td><td>CVObowiązkowy</td><td></td><td>number whole (8..24)</td><td>In terms of TTI.</td><td>REL-8</td>

<td>Suspending the continuation of E-DCH transmission</td><td>CVObowiązkowy</td><td></td><td>Numbered (0, 4, 8, 16, 24, 40, 80, infinity)</td><td>In terms of TTI. If set to "infinity", the default E-DCH common resource version is disabled.</td><td>REL-8</td>

<td>ACK / NACK support for HS-DPCCH</td><td>CVObowiązkowy</td><td></td><td>boolean</td><td>TRUE indicates that HS-DPCCH should be used when a shared E-DCH resource is allocated to UE for DTCH / DCCH transmission after collision resolution. FALSE indicates that HS-DPCCH is not to be used.</td><td>REL-8</td>

<td>Feedback Measurement</td><td>CVOpcjonalny</td><td></td><td>Infor feedback measurement 10.3.6.40a</td><td></td><td>REL-8</td>

<td>E-DCH Common Resource Configuration information list</td><td>MP</td><td>1 to &lt;MaksEDCH&gt;</td><td></td><td></td><td>REL-8</td>

<td>&gt; Soffset</td><td>MD</td><td></td><td>number total (0..9)</td><td>(0..9) indicates the symbol offset as defined in [26] Note3</td><td>REL-8</td>

<td>&gt; F-DPCH Code number</td><td>Short-CV</td><td></td><td>number total (0..255)</td><td>If this IE is not present, the value is equal to the last instance of this IE.</td><td>REL-8</td>

<td>&gt; E-RGCH Information</td><td>Short-CV</td><td></td><td>E-RGCH Info 10.3.6.102</td><td></td><td>REL-8</td>

<td>&gt; E-HICH info for Joint E-DCH</td><td>MD</td><td></td><td>E-HICH info for joint EDCH 10.3.6.1 xx</td><td></td><td>REL-8</td>

<td>&gt; DPCH code info in the uplink</td><td>MD</td><td></td><td>DPCH code info in the uplink for the Common E-DCH 10.3.6.87b</td><td></td><td>REL-8</td>

<td colspan="6"></td>

<td>State</td><td colspan="5">Explanation</td>

<td>optional</td><td colspan="5">If IE "Common E-DCH System Info" is present, the IE value is the same value corresponding to IE in IE "Common E-DCH System info". Otherwise, this IE is optional.</td>

<td>Short</td><td colspan="5">This IE is mandatory for the first occurrence. Otherwise, this IE is optional.</td>

<td>Obligatory</td><td colspan="5">If IE "Common E-DCH System Info" is present, the IE value is the same value corresponding to IE in IE "Common EDCH System Info". Otherwise, this IE is mandatory present.</td>

<td colspan="6">NOTE1: These IE correspond to the HS-DSCH configuration for the CELL_FACH, CELL_PCH and URA_PCH state on the main frequency, the configuration on the secondary frequency is signaled to the UE via dedicated signaling. NOTE2: These IE correspond to the CCCH transmission configuration for the CELL_FACH state on the primary frequency and the secondary frequency. NOTE3: The default value is defined by: Soffset = (offset + item in the E-DCH common resource list) mod 10 where "offset" is the value of the last case of IE "Soffset". If IE "Soffset" was not present in the first case, "offset" is zero. "E-DCH Common Resource List Item" indicates the number of the E-DCH Common Resource Configuration Information in order of appearance. The value of the "EDCH Common Resource List Item" is zero for the first case.</td>

Additional states can be placed to reduce signaling in case of IE "System Info Joint E-DCH". Affected IE are underlined below:

PRACH preamble control parameters (for Reinforced Uplink)

<td>Information Item / Group Name</td><td>Needed</td><td>Multi</td><td>Type i reference</td><td>Semantic description</td><td>version</td>

<td>Signature available</td><td>MD</td><td></td><td>Bit series</td><td>The default value is</td><td>REL-8</td>

<td></td><td></td><td></td><td> (16)</td><td>inverse order bits indicated in IE "Available Signature" in IE "PRACH Info (for RACH)". Each bit indicates availability for the signature. Each available signature on AICH is associated with one Resource Configuration Common E-DCH in 'list configuration information EDCH Joint Resources ".</td><td></td>

<td>E-AI Indication</td><td>MP</td><td></td><td>BOOLEAN</td><td>TRUTH: E-Al are in use on AICH. FALSE: E-Al are not in use on AICH.</td><td>REL-8</td>

<td>Code number</td><td>MD</td><td></td><td>integer</td><td>The default value is</td><td>REL-8</td>

<td>scrambling preamble</td><td></td><td></td><td> (0.15)</td><td>value indicated in IE</td><td></td>

<td></td><td></td><td></td><td></td><td>"scrabmling code number preamble "in IE" PRACH Info (for RACH) ". Scrambling code identification, see [28]</td><td></td>

<td>Available number</td><td>MD</td><td></td><td>Bit series</td><td>The default value is this</td><td>REL-8</td>

<td>subchannel</td><td></td><td></td><td rowspan="2"> (12)</td><td>the same value indicated in</td><td></td>

<td></td><td></td><td></td><td>IE "Available Signatures" in IE "PRACH system information list". Each bit indicates availability for the subchannel, where subchannels are numbered "subchannel 0 "to" subchannel 11 ". A value of 1 bit indicates that corresponding subchannel is available and the value 0 indicates that it is not available.</td><td></td>

<td>PRACH partitioning</td><td>MD</td><td></td><td>PRACH partitioning 10.3.6.53</td><td>The default value is the "PRACH partitioning" value in the first instance in the "list of PRACH system information" list SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Life scaling factors</td><td>OP</td><td></td><td>coefficients scaling durability 10.3.6.48</td><td>This IE should not be present as soon as ASC 0 and ASC 1 are defined. If this IE is absent, the default value is the value "durability scaling factors" in the first occurrence in the list "PRACH system information list" in SIB5 or SIB5bis, if the value exists</td><td>REL-8</td>

<td>AC-to-ASC mapping</td><td>MD</td><td></td><td>ACdo-ASC mapping 10.3.6.1</td><td>The default value is the "ACdo-ASC mapping" value in the first instance in the "list of PRACH system information" list in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Main power of CPICH TX</td><td>MD</td><td></td><td>Main power of CPICH TX 10.3.6.61</td><td>The default value is "Main power CPICH TX "in the first occurrence in the list" PRACH system information list "in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Fixed value</td><td>MD</td><td></td><td>Fixed value 10.3.6.11</td><td>The default value is the "Fixed value" value in the first instance in the "list of PRACH system information" list in SIB5 or SIB5bis</td><td>REL-8</td>

<td>PRACH power offset</td><td>MD</td><td></td><td>PRACH power offset 10.3.6.54</td><td>The default value is the "PRACH power offset" value in the first occurrence in the "list of PRACH system information" list in SIB5 or SIB5bis &lt;</td><td>&gt; REL-8</td>

<td>PRACH transmission parameters</td><td>MD</td><td></td><td>RACH transmission parameters 10.3.6.67</td><td>The default value is the "RACH transmission parameters" value in the first instance in the "list of PRACH system information" list SIB5 or SIB5bis.</td><td>REL-8</td>

<td>AICH info</td><td>MD</td><td></td><td>AICH info 10.3.6.2</td><td>The default value is "AICH info" in the first occurrence in the "list of PRACH system information" in SIB5 or SIB5bis.</td><td>REL-8</td>

<td>Pp-e power offset</td><td>MP</td><td></td><td>Integer (-5..10)</td><td>In dB. Power offset between the last transmitted preamble and the initial DPCCH transmission as defined in [26]</td><td>REL-8</td>

E-HICH Info for the Joint E-DCH

<td>Information Item / Group Name</td><td>Needed</td><td>Multi</td><td>Type i reference</td><td>Semantic description</td><td>Version</td>

<td>Sewer Code</td><td>Short-CV</td><td rowspan="6"></td><td rowspan="6">number whole (0..127)</td><td rowspan="2">For the first occurrence if this IE is not present, value this IE is the last value IE "Sewer Code" instances</td><td rowspan="6">REL-8</td>

<td rowspan="5"></td><td rowspan="5"></td>

<td>current system info in IE</td>

<td>joint E-DCH ". For</td>

<td>next instances if IE doesn't is present, the value is equal</td>

<td>last instance of this IE.</td>

<td>Sequence</td><td rowspan="3">MD</td><td rowspan="3"></td><td rowspan="3">number whole (0..39)</td><td rowspan="3">Note 1</td><td rowspan="3">REL-8</td>

<td>The signature</td>

<td></td>

<td colspan="6"></td>

<td colspan="3">Short</td><td colspan="3">If IE "Common E-DCH system info" is not present, this IE is mandatory for first appearance. Otherwise, this IE is optional.</td>

NOTE1: The default value is defined by:

Signature Sequence = (offset + item in the E-DCH common resource list) mod 40 where "offset" is the value of the last IE instance of "Signature Sequence". If "Signature Sequence" was not present in the first case, "offset" is zero.

"E-DCH Common Resource List Item" indicates the number of the E-DCH Common Resource Configuration Information in order of appearance. The value of the "E-DCH Common Resource List Item" is zero for the first case.

IE "E-DPCH info" and "DPCH code info in the uplink for the Common E-DCH" will not be changed compared to the first solution.

The coding improvements of each IE present in the "Common E-DCH System Info" are independent of other IE.

Step 503. The mobile terminal 10 transmits a mapped preamble to request access to a second available resource. Thus, the mobile terminal 10 requests access to the wireless communication system. In some embodiments, the mobile terminal randomly selects an access request preamble. Further, the mobile terminal 10 may, by receiving confirmation of the transmitted access request preamble, transmit uplink data on the contention-based channel using the second available resource.

The processing in the mobile terminal may further include receiving system information that directly indicates the access request preambles for the first contention-based uplink channel. Processing continues until the access request preambles are output for the second uplink channel based on contention-based or as a function of the directly indicated preambles. In one or more embodiments, the processing also includes randomly selecting one of the derived access request ambulas, and then transmitting the selected preamble to request access to the second contention-based uplink channel.

Fig. 6 is a block diagram illustrating mobile terminal 10 in accordance with the present embodiments. The mobile terminal 10 is generally configured to perform the method illustrated in Fig. 5. The mobile terminal 10 may include one or more transmit / receive antennas 601, together with the associated transmitter (TX) 602 circuit and the receiver (RX) 603 circuit, respectively, and include one or more processing circuits 604. The RX 603 circuit is configured to receive from base station 12, through receiving antennas 601, transmitted system information that indicates the first available CB channel resource. The processing circuit 604 of the mobile terminal 10 may be configured to output then information for the second available CB channel resource on the base or as a function of the first. This may result, for example, in outputting information for the second available resource according to a predetermined rule that defines the second resource as a function of the first resource, e.g., as a function of the position of the first resource in an ordered list describing the resources. Processing circuit 604 may optionally in some embodiments randomly select an access request preamble corresponding to a second contention based uplink channel resource. The TX 602 circuit may then transmit the selected preamble, and the RX 603 circuit may receive positive acknowledgment. In response to the transmitted preamble selected or not, the processing circuit 604 may output system information for the second available resource of the second contention-based channel, e.g., a channel in the uplink, on the basis or as a function of the first available resource. Finally, TX 602 may in various embodiments conclude by transmitting uplink data on a second uplink channel based on contention using the second available resource.

In some embodiments, the received system information may directly indicate preamble access requests for one channel, e.g., a legacy CB channel such as RACH. Processing circuits 604 may then be configured to output preamble access requests for another channel, e.g., a non-legacy CB channel, such as E-DCH, on a base or as a function of directly indicated preambles. In certain embodiments, the processing circuits 604 are also configured to randomly select from output access request preambles, then the TX circuit 602 is configured to transmit the selected preamble to base station 12 to request access to the associated CB.

In Fig. 6, the mobile terminal receives system information that indicates a first contention-based resource of the second uplink channel. In some embodiments, the processing circuit may optionally may optionally include randomly selecting an access request preamble corresponding to a second contiguous based uplink channel resource, transmitting the selected preamble, and receiving a positive acknowledgment. Processing circuit 604 then outputs system information for the second available resource of the second uplink channel based on contention on the basis or as a function of the first available resource. Finally, the processing circuit 604 may in various embodiments conclude by transmitting uplink data on the second uplink channel on the basis of contention using the second available resource via the TX 602 circuit.

Thus, the mobile terminal 10 for requesting access to the wireless communication system includes a receiving circuit 603 configured to receive broadcast system information that indicates the first available channel resource based on signaling. The mobile terminal 10 also includes a processing circuit 604 configured to output the second available contention-based channel resource based on the first available contention-based channel resource. Processing circuit 604 may also be configured to transmit a mapped preamble to request access to a second available resource. Processing circuit 604 is in some embodiments also configured to randomly select an access request preamble. Further, the processing circuit 604 may also be configured to, upon receiving confirmation of the transmitted access request preamble, transmit uplink data on the contention channel using the second available resource. In some embodiments, the contention-based channel corresponds to a random access channel, RACH, or a joint Reinforced Dedicated Channel. Received broadcast system information can be contained in System Information Block type 5, SIB5. The second available resource can be indicated in the ordered list of resources as a function of the position of the first available resource in the ordered list. In some embodiments, the ordered list defines the resources of the common Dedicated Strengthened Channel, E-DCH. Each E-DCH Resource can be defined by the Soffset information element, Fractional Dedicated Physical Control Channel, F-DPCH, information element code number, and information element info Hybrid Channel Confirmation Indicator Indicator Automatic E-DCH Confirmation Request, E-HICH, for common E -DCH. In some embodiments, the position of the second available resource in the ordered list is defined by the default value in the Soffset information element. The default value is a function of the position of the second available resource in the ordered list; a function of the "Soffset" value of the previous first available resource; or a function of the position of the second available resource and the offset value. The offset value is the Soffset value of the first available resource. In some embodiments, the information element F-DPCH code number may be the same for a maximum of ten asobs of common E-DCH. The E-HICH info element for the common E-DCH is in some embodiments defined by the sewer code and the signature sequence. The default signature sequence value is a function of the position of the second available resource in the ordered list; a function of the "Signature Sequence" value of the previous first available resource; or a function of the position of the second available resource and the "Signature Sequence" value of the previous first available resource. The sewer code of the second available resource may be equal to the sewer code of the first available resource. The second available resource can be defined by the value in the information element scrambling code of the Dedicated Physical Control Channel in the uplink, which value is a function of the position of the second available resource in the ordered list of common E-DCH resources, function of the value in the information element scrambling code of the Dedicated Physical Control Channel in the uplink of the previous available first available resource or function of the position of the second available resource and the value "DPCH code info in the uplink for the Common E-DCH" in the information element scrambling code of the Dedicated Physical Control Channel in the previous uplink first available resource.

Specialists will also appreciate that the various "circuits" described may refer to a combination of analog and digital circuits, and / or one or more processors configured with software and / or firmware, e.g., stored in memory, which, when performed by one or more processors, operate as described above. One or more of these processors, as well as other digital equipment, may be integrated into one special purpose integrated circuit (ASIC), or several processors and different digital equipment may be distributed between several separate components, whether individually packaged or assembled in a system -chipie (SoC).

Thus, those skilled in the art will appreciate that the above description and the attached drawings represent non-limiting examples of the methods and devices described herein. As a tkai, the invention is not limited by the above description and the attached drawings.

Proxy:

"ATENTOWA" BELLEPAT "LAW OFFICE

Izabela Szychulska-Hawranek ul Słowackiego 44, 37-700 ΡΓΖ * · ηνέΙ tel. (016) 7u2-37-77 fax: (016) 075-02-87 mobile phone &lt;0608) 503-081 e-maii <a href="mailto:bellepat@op.pl">bellepat@op.pl</a> NIP: 795-207-16-72 REGON: 1803505: 6

<img file="PL2622929T3_D0002.tif" />

mgr Izabela Siychubte-l entry no. 31S2