Omitting UE id on an enhanced RACH process

A method of an uplink transfer at the UE side in a wireless communications system over a wireless interface between a radio network and a user equipment node uses a first mode of transfer and a second mode of transfer. The first mode of transfer involves sending a first message by the UE to a Node B of the wireless communication system. The second mode of transfer involves receiving a resource by the UE from the Node B, and sending at least one subsequent message by the UE to the Node B, the at least one subsequent message omits an UE id.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is based on and hereby claims priority to PCT Application No. PCT/EP2008/062697 filed on Sep. 23, 2008 and EP Application No. EP07018855 filed on Sep. 25, 2007, the contents of which are hereby incorporated by reference.

BACKGROUND

This invention relates to an improved mobile radio telecommunication network.

A Universal Mobile Telecommunications System (UMTS) is a third generation mobile communication system, which evolved from a Global System for Mobile Communications (GSM), and is intended to provide improved mobile communication services based on a GSM core network (CN) and Wideband Code Division Multiple Access (WCDMA) access technology.

US 20070081513 discloses a wireless data flow between a radio network node and a user equipment node. A medium access control (MAC) layer located in the radio network node determines a priority of data unit relative to other data units associated with the one data flow.

US 20070165526 discloses a method to enable a medium access control (MAC) to reduce and to increase packet size and the data transmit rate by working with an upper layer controller to maximize data transfer rate, transmitter power, and to minimize packet drop rate.

SUMMARY

It is one potential object to provide an improved mobile radio telecommunication network.

The inventors propose an improved mobile radio telecommunication network that uses a method an uplink transfer in a wireless communications system over a wireless interface between a radio network and a user equipment node (UE), at the UE side. The method comprises a first mode of transfer and a second mode of transfer.

The first mode of transfer comprises the step of sending a first message by the UE to a Node B of the wireless communication system. The second mode of transfer comprises the step of receiving a resource by the UE from the Node B, and sending at least one subsequent message by the UE to the Node B, the at least one subsequent message omits an UE id.

The first message may comprise an UE id. The resource can comprise a dedicated scrambling code. The at least one subsequent message can be scrambled with the dedicated scrambling code.

A MAC layer of the UE side can comprise a MAC-d sub-layer, a MAC-c sub-layer, and a MAC-es sub-layer with the MAC-c sub-layer being provided between the MAC-d sub-layer and the MAC-es sub-layer. The first message can comprise an UE id in a MAC header of a MAC layer. The at least one subsequent message can omit the UE id in a MAC layer. The first message can comprise a UE id status field, which stores a presence status of the UE id.

The inventors also propose a method for uplink transfer in a wireless communications system over a wireless interface between a radio network and a user equipment node (UE), at the radio network side. This method uses a first mode of transfer and a second mode of transfer.

The first mode of transfer comprises the step of receiving a first message by a Node B of the wireless communication system from the UE, and assigning a resource to the UE by the Node B. The second mode of transfer comprises the step of receiving at least one subsequent message from the UE, which omits an UE id.

The first message can comprise an UE id. The resource can comprise a dedicated scrambling code.

The first mode of transfer can further comprise the step of mapping the dedicated scrambling code to the UE id by the Node B or other parts of an UTRAN (UMTS terrestrial radio access network) of the wireless communications system. The at least one subsequent message can be scrambled with the dedicated scrambling code.

The first mode of transfer can comprise the further step of determining the UE id status of the first message from an UE id status field of the first message.

The second mode of transfer can further comprise the step of determining the UE id from the mapping of the dedicated scrambling code to the UE id.

A MAC layer of the radio network side can comprise a MAC-d sub-layer, a MAC-c sub-layer, and a MAC-es sub-layer with the MAC-c sub-layer being provided between the MAC-d sub-layer and the MAC-es sub-layer.

The inventors further propose a user equipment (UE) of a wireless communications system in an uplink transfer over a wireless interface between a radio network and the user equipment (UE) node. The user equipment has a medium access control (MAC) layer at the UE side. The UE is operative in a first mode of transfer and a second mode of transfer.

The UE is for transmitting a first message to a Node B of the wireless communications system in a first mode of transfer. The UE is for transmitting at least one subsequent message to the Node B, which omits an UE id after being assigned a resource by the Node B.

The resource can comprise a dedicated scrambling code. The at least one subsequent message can be scrambled with a dedicated scrambling code in a second mode of transfer.

The medium access control (MAC) layer can comprises a MAC-d sub-layer, a MAC-c sub-layer, and a MAC-es sub-layer with the MAC-c sub-layer being provided between the MAC-d sub-layer and the MAC-es sub-layer.

The first message can comprise an UE id. The first message can further comprise a UE id status field, which stores a presence status of the UE id.

The inventors still further propose a Node B of a radio network of a wireless communications system in an uplink over a wireless interface between the radio network and a user equipment node (UE).

The Node B is operative in a first mode of transfer and a second mode of transfer. The Node B is for receiving a first message, and is for assigning a resource to the UE in the first mode of transfer. The Node B is also for receiving at least one subsequent message in the second mode of transfer, the at least one subsequent message omits an UE ID.

The resource can comprise a dedicated scrambling code. The Node B can be for mapping the dedicated scrambling code to the UE id. The at least one subsequent message can be scrambled with the dedicated scrambling code.

The Node B can be for determining the UE id by mapping the dedicated scrambling code to the UE id, in the second mode of transfer. The first message can comprise an UE id status field.

The Node B can comprise a medium access control (MAC) layer, which comprises a MAC-d sub-layer, a MAC-c sub-layer, and a MAC-es sub-layer with the MAC-c sub-layer being provided between the MAC-d sub-layer and the MAC-es sub-layer.

The application can advantageously reduce protocol overhead and saves radio resources as the UE ID is omitted from every TTI transmission to the Node B. The protocol overhead reduction may ranges from two to four octets. Moreover, data transmitted with dedicated scrambling codes avoids collisions between the transmitted data. A packet data unit (PDU) can also be mapped to its correct UE by a RNC (radio network controller) even though there is no dedicated connection between the Node B and the RNC. A HARQ retransmissions can continue in the event of a transition to a CELL_DCH state as the PDU structure of the UE is identical to its PDU structure in the CELL_DCH state.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

According to one basic thought of the application, an identifier (ID) of a UE (user equipment) can be omitted in a transmission between the UE and a Node B of telecommunication network, once the UE is assigned with a resource by the Node B. The resource can be a dedicated scrambling code. The UE transmits data scrambled with the dedicated scrambling code and the Node B associates the UE identifier to the dedicated scrambling code.

A method of transmitting data between an UE and a Node B wherein an UE identifier can be omitted is shown below. The transmission can be over an E-RACH or a RACH (random access channel) process. A message with the UE identifier is first transmitted from the UE to the Node B. A header, especially a MAC header, of the message includes a field to indicate the presence of the UE identifier in the message. The UE identifier can be 16 bits wide. The Node B can use the UE ID to identify the UE and to resolve contention.

The Node B later receives the message with the UE identifier and afterward assigns a dedicated scrambling code to the UE. The UE can later transmit subsequent messages without the UE identifier to the Node B. The subsequent transmitted messages are scrambled with the dedicated scrambling code. The flag in the header of the subsequent messages can also indicate the absence of the UE identifier in the message. The Node B then associates or maps the dedicated scrambling code to the UE.

The Node B afterward identities the UE and resolves contention using the dedicated scrambling code, instead of using the UE identifier. The Node B uses the dedicated scrambling code to identify the UE until the UE performs a cell or UTRAN Registration Area (URA) update procedure due to cell reselection or if the UE is performing a Radio Resource Control (RRC) Connection request procedure).

FIG. 1illustrates in block format a UMTS (Universal Mobile Telecommunications System) type system. A description of the UMTS is disclosed in “3rd Generation Partnership Project (3GPP)”, http://www.3gpp.org/.

FIG. 1shows a UMTS10, which comprises a plurality of UEs (user equipments)11, UTRAN (UMTS terrestrial radio access network)12, and a CN (core network)13. The UEs11are connected to the UTRAN12by a radio connection whilst the UTRAN13is connected to the CN13.

The UTRAN12includes RNSs (radio network sub-systems)15and16. The RNS15includes a RNC (Radio Network Controller)17and Node Bs18and19. The Node Bs18and19are joined to the RNC17. Similarly, the RNS16includes a RNC22and Node Bs23and24. The Node Bs23and24are joined to the RNC22.

The RNS15is also connected to the RNS22.

The CN13comprises a MSC (mobile switching centre)25and a SGSN (Serving General Packet Radio Service Support Node)26. The MSC25is connected to the RNSs15and16whilst the SGSN26is connected to the RNSs15and16.

The UMTS system10may be in a CELL_FACH (Forward Access Channel) state or a CELL_DCH state. The CELL_FACH state may denote a state of low data transmission in which no dedicated channels are established and only common channels are used. No dedicated radio resources in the Node B18,19,23, or24are used. The CELL_DCH may state denote a state of high data transmission and dedicated channels are formed. The UE11is assigned dedicated radio and hardware resources, which may minimizes transmission delay and allows for high capacity.

The UE11is also known as a mobile terminal. The Node B is similar in function to a radio base station. The Node Bs18,19,23, and24act as access points of the UTRAN12for the UE11. Information is transmitted the Nodes Bs18,19,23, and24and the UE11via radio channels. The radio channels are also known as physical channels. The information is transmitted in an UL (uplink) mode when the information is transmitted from the UE11to the Nodes Bs18,19,23, and24. Similarly, the information is transmitted in a DL (downlink) mode when the information is sent from the Nodes Bs18,19,23, and24to the UE11.

The RNC17manages the Node Bs18, and19whilst the RNC22manages the Node Bs23, and24. The RNCs17and22are connected to the MSC25for a circuit-switched communication, such as a voice call service, and are connected to the SGSN26for packet switched communication, such as a wireless Internet service, Voice over IP (VoIP), web-browsing, or e-mail.

A RNC that is in charge of a direct management of the Node B is called a Controlling RNC (CRNC). The CRNC manages common radio resources. On the other hand, a RNC that manages dedicated radio resources for a specific UE is called a Serving RNC (SRNC). The CRNC and the SRNC can be co-located in a same physical node. However, if the specific UE has been moved to an area of a new RNC that is different from the current SRNC, the specific UE may be connected a CRNC and a SRNC that are be located at physically different places.

FIG. 2illustrates a protocol layer structure30of the UMTS system10ofFIG. 1. The protocol layer structure30is provided in the UE11ofFIG. 1and in the UTRAN12ofFIG. 1.

The protocol layer structure30includes a RLC (Radio Link Control) layer31, a MAC (Medium Access Control) layer32, and a PHY (physical) layer33. The RLC layer31is placed above the MAC layer32whilst the MAC layer32is provided above the PHY layer33. A PDCP (Packet Data Convergence Protocol) layer, which is not shown in theFIG. 2, is positioned over the RLC layer.

The RLC layer31is connected to the MAC layer32by a plurality of logical channels whilst the MAC layer32is connected to the PHY layer33by a plurality of transport channels36.

The RLC layer31includes a plurality of RLC entities34. The logical channels35may include control channels and traffic channels. The control channels and traffic channels are not shown in theFIG. 2.

The MAC layer32comprises sub-layer such as, a MAC-c sub-layer, a MAC-d sub-layer, a MAC-es sub-layer, a MAC-e sub-layer, and a MAC-hs sub-layer. The transport channels36may comprise dedicated transport channels, and common transport channels. The MAC-es sub-layer may be provided in a SRNC whilst the MAC-e sub-layer may be located in a Node B.

The PDCP layer efficiently transmits data of network protocols, such as IPv4 (Internet Protocol, version 4.0) or IPv6 (Internet Protocol, version 6.0).

The RLC entity34provides data transfer service between a higher layer and the MAC32. The data transfer service may operate in a transparent mode (TM), an unacknowledged mode (UM), or an acknowledged mode (AM). For packet switched mode, the data transfer service operates only in the UM and in the AM, and not in the TM. The RLC entity34offers ciphering in the unacknowledged mode (UM) and in the acknowledged mode (AM).

The logical channels35are characterized by the kind of information carried by the logical channels35. The control channels are for transmission of control plane information whilst the traffic channels are for transmission of user plane information.

The MAC layer32provides unacknowledged data transfer service between the logical channels35and the transport channels36. The sub-layers of MAC layer32perform a set of functions that may include mapping the logical channels35to the common transport channels and to the dedicated transport channels, multiplexing one or more logical channels35onto the transport channel36, and ciphering or deciphering of data in the transparent mode (TM).

The transport channels36offer a passageway for movement of data between the PHY layer33and the MAC layer32. The dedicated channel is allocated to a specific UE11whereas the common physical channel is shared by a group of UEs11.

The PHY layer33provides a way to transmit data between an air medium and the MAC layer32, and execution of soft handover of the UE11from one geographical cell or area to another geographical cell of the same network.

The PHY layer33transmits data over the air medium through physical channels. The transmission of data is in Frequency Division Duplex (FDD) mode or in Time Division Duplex (TDD) mode. In the TDD mode, the physical channels can be characterized by timeslot whilst in the FDD mode, the physical channels can be characterized by code, frequency and orthogonal signature sequence.

FIG. 3illustrates AM (acknowledge mode) RLC (radio link control) PDU (protocol data unit)40, which is transmitted by the RLC layer31ofFIG. 2. The AM RLC PDU40is transmitted in an uplink mode, in which the flow of transmission is from the UE11ofFIG. 1towards the UTRAN12ofFIG. 1.

The AM RLC PDU40in the UL mode is similar to an AM RLC PDU40in a DL (downlink) mode, which is described in “Radio Link Control (RLC) protocol specification (Release 7)”, http://www.3gpp.org/ftp/Specs/html-info/25322.htm.

The AM RLC PDU40comprises an AM RLC header41and a payload field42. The AM RLC header41includes a D/C (data control) field44, a SN (sequence number) field45, a P (polling) field47and a HE (header extension) field48. The length of the D/C field44, the sequence field45, the P field47, and HE field48is of sixteen bits long, as shown in theFIG. 3. The payload field42includes a complete SDU (service data unit).

The size of the AM RLC PDU40is not fix and is flexible. This allows the AM RLC PDU40to be responsive to physical layer requirements. This is unlike other protocol which supports only an AM RLC PDU of a fixed size.

Content of the HE field48indicates end position of the payload field42, as described in “Radio Link Control (RLC) protocol specification (Release 6)”, http://www.3gpp.org/ftp/Specs/html-info/25322.htm. This is difference from a LI (Length Indicator) field, which shows the length of the payload field42. The LI field is described in “Radio Link Control (RLC) protocol specification (Release 7)”, http://www.3gpp.org/ftp/Specs/html-info/25322.htm. The length of payload42is in multiple of eight bits.

FIG. 4illustrates a first MAC-e header50of a PDU, or a MAC-es header50of a PDU, for the uplink transport channels ofFIG. 2. The MAC-es/e header50includes a TSN (transmission sequence number field) field54and a SI (segmentation indicator) field55, which support segmentation. The PDU includes the SDU (service data unit) ofFIG. 3.

The first MAC-e/es header50includes an F (flag) field51, a logical channel id field52, a length field53, the TSN field54, and the SI field55. As shown in theFIG. 4, the length of the F field51, the logical channel id field52, the length field53is of sixteen bits long. The length of the TSN field54and the SI field55is of eight bits long.

The uplink transport channels for the first MAC-e/es header50include CCCH (common control channel), DCCH (dedicated control channel), and DTCH (dedicated traffic channel).

The content of the first MAC-e/es header50may be used in a CELL_FACH state and a CELL_DCH state.

The content of the F field51is to indicate the presence or absence of an UE id field in the first MAC-e/es header50. The value of the content of the F field51, as provided here, is zero, denoting an absence of the UE id field. The content of the UE id field is for resolving any contention. A contention may occur when there is collision of identities from two or more UEs.

The logical channel id field52, as provided here, is for storing a logical channel id from which the PDU originates. The value of the logical channel id field52is zero if the PDU originates from a CCCH (common control channel) of the UE11.

The content of the logical channel id field52is also utilized by the Node B18,19,23, or24of theFIG. 1to determine a correct frame protocol connection for carrying the PDU to the SRNC (serving RNC). The SRNC can utilize the content of logical channel id52to determine a correct reordering queue, a logical channel, and a RLC entity.

The contents of the length field53and the SI field55are utilized to indicate the size of the payload and information about segmentation, such as complete PDU and last segment.

This information is later used for reassembly. The segmentation may be requested by the physical layer.

The segmentation is needed to fit the payload into a MAC transport block size as allowed by the uplink grant given by the Node B, or given by available transmit power, or by logical channel priorities in which payload from higher priority are inserted first. If multiplexing of logical channels is possible for lower priorities, the remaining space can be used.

The segmentation requires two bits of information to be recorded in the SI field55. For example, the bits of “00” indicate no segmentation, the bits of “01” indicate any segment, and the bits of “10” indicate the last segment. Based on this information together with a length information, a TSN information, and a TSN of the last complete MAC-SDU information, a receiver can reassemble the MAC-SDU or MAC PDU as soon as all TSN are received.

The contents of the length field53and the SI field55of a PDU, in the SRNC, are used to reorder and then to reassembly and the PDU to form a RLC PDU.

The content of the TSN field54describes a transmission sequence number of the PDU in the UE11side. The content of the TSN field54is utilized by the RNC17or22ofFIG. 1to reorder the PDU in the UTRAN12side.

The SRNC, when in the CELL_DCH state, utilizes the content of the TSN field for macro diversity to establish UL (uplink) SHO (soft handover) between the Node B18,19,23or24and another Node B18,19,23or24. The macro diversity occurs if at least one Node B18,19,23or24, receives the PDU.

FIG. 5illustrates a second MAC-e header60of a PDU, or a MAC-es header60of a PDU, for the uplink transport channels ofFIG. 2. The PDU includes the SDU (service data unit) ofFIG. 3

The second MAC-e/es header60comprises parts that are similar to the parts of the first MAC-e/es header50ofFIG. 4. The similar parts of the second MAC-e/es header60are denoted with the same part number as the part of the first MAC-e/es header50with a prime symbol. The description of the first MAC-e/es header50is included here by reference, where appropriate.

The second MAC-e/es header60includes an F field51′, a UE id field61, a logical channel id field52′, a length field53′, a TSN field54′, and a SI' field55. The length of the F field51′, the UE id field61, the logical channel id field52′, the length field53′ is of twenty-four bits long. The length of the TSN field54′ and the SI field55′ is of eight bits long.

The value of the content of the F field51′, as provided here, is one, denoting a presence of the UE id field61.

The content of the UE id field61is for resolving any contention. When the UE11ofFIG. 1is using an E-RACH (enhanced random access channel), the UE11uses the F field51′ to denote the presence status of the UE id field61in the second MAC-e header60.

After the UTRAN12has indicated a correct reception of the content of the UE id field61, the UE11stops including the UE id field61in the second MAC-e/es header60. The UTRAN12may confirm the correct reception of the content of the UE id field61by sending the value of the UE id field61back to the UE11, as confirmation of correct receipt.

The value of the UE id field61, as provided here, is unique. The UE11, as provided here, usually assigns a value to the content of the UE id field60. The content of the UE id field60is allocated by the UTRAN12, when the UE11is in a RRC (radio resource connection) connected state, and is not performing a cell, or URA (UTRAN registration area) update procedure due to a cell reselection.

The UE id field60is also assigned a random value by the UE11, when the UE11is performing the cell, or the URA update due to the cell reselection or a RRC connection request procedure. As the message is a type of a CCCH message, a permanent UE id or U-RNTI (UTRAN radio network temporary identity) is included in a RNC message. The permanent UE id or the U-RNTI can be used to identify the UE11. The UTRAN12can later allocate a unique id in a first DL (downlink) message back to the UE11. The unique id is then used in subsequent RACH or enhanced RACH procedures.

FIG. 6illustrates a simplified protocol architecture65for E-DCH (enhanced dedicated channel) in the side of a UE. TheFIG. 6shows parts that are similar to the parts ofFIGS. 1 to 5. The similar parts are denoted are with similar names. The description ofFIGS. 1 to 5is included by reference, where appropriate.

TheFIG. 6shows a mapping of DTCH (dedicated traffic channel) and DCCH (dedicated control channel) to E-DCH (enhanced dedicated channel). The simplified protocol architecture65includes a left part and a right part. The left part shows a RLC layer68and a MAC layer69. In contrast, the right part shows decompositions of PDUs.

The RLC layer68is placed above the MAC layer32. The MAC layer69comprises a MAC-d sub-layer70, a MAC-c sub-layer71, and a MAC-es/e sub-layers72and73. The MAC-d sub-layer70is provided above the MAC-c sub-layer71whilst the MAC-c sub-layer71is located above the MAC-es/e sub-layers72and73.

The DCCH entity66and the DTCH entity67are connected to the segmentation entities75whilst the segmentation entities75are connected to the numbering entities76. The numbering entities76are connected the multiplexing and E-TFC selection entity77, which is connected to the HARQ entity78.

A RLC PDU80corresponds to the DCCH entity66and the DTCH entity67. The RLC PDU80comprises a header field81and a data field82. A MAC-d PDU84, which corresponds to the MAC-d sub-layer70, includes a data field85. A MAC-es PDU88corresponds to the segmentation entity75and the numbering entity76. The MAC-es PDU88comprises a MAC es-header and a data field92. The MAC-es header includes a length field89, a TSN field90, and a SI field91. A MAC-e PDU94, which corresponds to the multiplexing and E-TFC selection entity77, includes a MAC-e header, and a data field97. The MAC-e header comprises a F field95, a logical channel id field96.

A method of transmission through the E-DCH at the UE side comprises the step of receiving a plurality of SDUs (service data units) from a higher layer by the RLC layer31. The RLC layer31segments or concatenates the SDUs, based on physical layer requirements. Headers are added to the SDUs to form the RLC PDUs80. The RLC PDUs80may be delivered to the MAC-d sub-layer70via the DCCH entity66and DTCH entity67in acknowledgement mode.

The MAC-d sub-layer70receives the RLC PDUs80and sends the MAC-d PDUs84to the MAC-es sub-layer72, without adding MAC-d headers to the MAC-d PDUs84. The MAC-d PDUs84includes the RLC PDUs80.

The MAC-es sub-layer72receives the MAC-d PDUs84and includes the MAC-es headers onto the MAC-d PDUs84. The segmentation entity75then receives the MAC-es PDU88and divides the MAC-es PDUs88in a manner directed by a PHY layer of the UE. The segmentation entity75uses the length field89and the SI field92of the MAC-es header to record information related to the segmentation, and sends the segmented MAC-es PDU88to the numbering entity76.

The numbering entity76later receives the segmented MAC-es PDU88and records the transmission sequence number of the MAC-es PDU88onto the TSN field90.

The multiplexing and E-TFC selection entity77of the MAC-e sub-layer73afterward receives the numbered MAC-es PDUs88and adds the MAC-e headers onto the MAC-es PDUs88to form the MAC-e PDUs94. The multiplexing and E-TFC selection entity77records the logical channel id from which the MAC-es PDU88originates onto the logical channel id field96.

The multiplexing and E-TFC selection entity77then multiplexes the MAC-e PDUs94into an order as directed by information received from the UTRAN side of the E-DCH. The multiplexed MAC-e PDU94is later sent to the HARQ entity78.

The HARQ entity78obtains the MAC-e PDU94from the MAC-e sub-layer73, stores the MAC-e PDU94, transmits the MAC-e PDU94to the PHY layer of the UE, and re-transmits any lost or corrupted MAC-e PDU94depending on HARQ ACK or NACK information form the Node B(s).

In a broad sense, a UE id setting entity can be provided between the HARQ entity78and the multiplexing and E-TFC selection entity77. The UE id setting entity includes an UE id information onto the MAC-e PDU94to resolve contention and indicates the presence of the UE id information in the F field95.

FIG. 7illustrates a simplified protocol architecture for E-DCH (enhanced dedicated channel) in the side of a UTRAN. TheFIG. 7shows parts that are similar to the parts ofFIGS. 1to6. The similar parts are denoted are with similar names. The description ofFIGS. 1 to 6is included by reference, where appropriate.

TheFIG. 7shows a mapping of DTCHs and DCCHs to E-DCH on the UTRAN side. The simplified protocol architecture100comprises a left part and a right part. The left part shows a RLC layer104and a MAC layer105. In contrast, the right part shows decompositions of PDUs.

The RLC layer104is located above the MAC layer105. The MAC layer105comprises a MAC-d sub-layer106, a MAC-c sub-layer107, a MAC-es sub-layer108, and a MAC-e sub-layer109. The MAC-d sub-layer106is provided above the MAC-c sub-layer107whereas the MAC-c sub-layer107is located above the MAC-es sub-layer108. The MAC-es sub-layer108is provided above the MAC-e sub-layer109.

The DCCH entities101and the DTCH entities102are connected to the reassembly entities112whilst the reassembly entities112are connected to the reordering entities113. The reordering entities113are connected the reordering queue distribution entity114. The reordering queue distribution entity114is connected to the de-multiplexing entity116, which is connected to the HARQ entity117.

A RLC PDU120corresponds to the DCCH entities101and the DTCH entities102. The RLC PDU120comprises a header field121and a data field122. A MAC-d PDU124, which corresponds to the MAC-d sub-layer106, includes a data field125. A first MAC-es PDU126corresponds to the reassembly entities112and the reordering entities113. The first MAC-es PDU126includes a first MAC es-header and a data field130. The first MAC-es header includes a length field127, a TSN field128, and a SI field129. A second MAC-es PDU132, which corresponds to the reordering queue distribution entity114, includes a second MAC-e header, and a data field135. The second MAC-e header comprises a F field133, a logical channel id field134. A MAC-e PDU138corresponds to the de-multiplex entity116and the HARQ entity117. The MAC-e PDU138comprises a MAC-e header and a data field141. The MAC-e header includes a F field139and the logical channel id field140.

A method of transmission at the UTRAN side of the E-DCH comprises the step of the HARQ entity117receiving the MAC-e PDUs138from the HARQ78ofFIG. 6. The HARQ entity117checks for validity and sends an ACK or NACK to the UE. The HARQ entity117sends the MAC-e PDUs138to the de-multiplex entity116.

The de-multiplex entity116receives the MAC-e PDU138from the HARQ entity117and send the MAC-e PDU138to the reordering queue distribution entity114by an appropriate lub (interface between a RNC and a Node B) flow base on logical channel id information in the logical channel id field139of the MAC-e PDU138. Information retaining to network configuration and transport QOS (Quality Of Service) may also be used to select the reordering queue distribution entity114.

The reordering queue distribution entity114receives the de-multiplexed MAC-e PDU138in the form of the second MAC-es PDU132, and sends the second MAC-es PDU132to the appropriate queue.

The appropriate reordering entity113receives the second MAC-es PDU132and removes the F field133and the logical channel id134to form first MAC-es PDU126. The reordering entity113reorders the first MAC-es PDU126base on the information in the TSN field128of the first MAC-es PDU126. The TSN field128is removed from the MAC-es PDU126.

The reassembly entity112then reassembly the reordered first MAC-es PDU126based on data in the length field127and the SI field129of the first MAC-es PDU. The length field127and the SI field129are removed from the reassembled first MAC-es PDU126to form the MAC-d PDU124.

The reassembly entity112later sends the MAC-d PDU124to the MAC-d sub-layer106. The MAC-d sub-layer106later transmit the MAC-d PDU124in the form of the RLC PDU120the RLC layer104.

The embodiments ofFIGS. 6 and 7illustrate an E-DCH type of transmission that can be used in the CELL_FACH state and in an uplink HARQ.

FIG. 8illustrates a simplified protocol architecture145for E-RACH (enhanced random access channel) in the side of a UE. TheFIG. 8shows parts that are similar to the parts ofFIG. 6. The similar parts are denoted are with similar names. The description ofFIG. 6is included by reference, where appropriate.

FIG. 8illustrates a mapping of CCCH and DCCHs onto the E-RACH. The simplified protocol architecture145includes a left part and a right part. The left part shows a RLC layer150and a MAC layer151whilst the right part shows decompositions of PDUs.

The RLC layer150is placed above the MAC layer151. The MAC layer151comprises a MAC-d sub-layer154, a MAC-c sub-layer155, and a MAC-es/e sub-layers156and157. The MAC-d sub-layer154is provided above the MAC-c sub-layer155whilst the MAC-c sub-layer155is located above the MAC-es/e sub-layers156and157.

An important aspect is to place the MAC-c between MAC-es and MAC-d such that the operation in E-RACH mode and E-DCH mode are harmonized.

The RLC layer150comprises a CCCH entity146, a DCCH entity147, and a DCCH entity148. The MAC-es/e sub-layers156and157include segmentation entities160, numbering entities161, a multiplexing and E-TFC (Transport Format Combination) selection entity162, a UE id setting entity163, and a HARQ (hybrid automatic retransmission) entity164.

The DCCH entity147and the DTCH entity148are connected to the segmentation entities160. The segmentation entities160are connected to the numbering entities161and the CCCH entity146is connected to the numbering entity161. The numbering entities161are connected the multiplexing and E-TFC selection entity162, which is connected to UE id setting entity163. The UE id setting entity163is connected to the HARQ entity164.

A RLC PDU166corresponds to the CCCH entity146. The RLC PDU166comprises a header field167and a data field168.

A MAC-d PDU170, which corresponds to the MAC-d sub-layer154, includes a data field171. A MAC-c PDU172corresponds to the MAC-c sub-layer155. The MAC-c PDU172includes a data field171.

A MAC-es PDU174corresponds to the segmentation entity75and the numbering entity76. The MAC-es PDU174comprises a MAC es-header and a data field175. The MAC-es header includes a length field176, a TSN field177, and a SI field178.

A first MAC-e PDU180, which corresponds to the multiplexing and E-TFC selection entity162, includes a first MAC-e header, and a data field181. The MAC-e header comprises an F field182, a logical channel id field183.

A second MAC-e PDU185corresponds to UE id setting entity163. The second MAC-e PDU185includes a second MAC-e header and a data field186. The second MAC-e header comprises an F field187and a logical channel id field188.

A third MAC-e PDU190, which corresponds to the UE id setting entity163, includes a third MAC-e PDU header and a data field191. The third MAC-e PDU header comprises an F field192, a UE id field193, and a logical channel id field194.

A method of transmission through the E-RACH at the UE side comprises the step of the RLC layer150receiving a plurality of SDUs (service data units) from a UE via a higher layer. Headers are added to the SDUs to form the RLC PDUs166.

The RLC PDUs166may be delivered to the MAC-d sub-layer154via the DCCH entity147and DCCH entity148and to the MAC-c sub-layer155via the CCCH entity146. The DCCH entity are usually used when there is high level of PDUs transmission and the CCCH entity is utilized when there is a low level of PDUs transmission.

The MAC-c sub-layer155receives the RLC PDUs160from the CCCH entity146and transmits the MAC-c PDUs172to the numbering entity161of the MAC-es sub-layer156without any segmentation of the MAC-c PDUs172.

The MAC-d sub-layer154receives the RLC PDUs160from the DCCH entities147and148, and sends the MAC-d PDUs170to the segmentation entities160of the MAC-es sub-layer156, without adding any headers to the MAC-d PDUs170. The MAC-d PDUs170includes the RLC PDUs166.

The segmentation entity160divides the MAC-d PDUs170, as directed by a PHY layer of the UE. The segmentation entity160records information regarding the segmentation onto the length fields176and the SI fields178of the MAC-es headers of the segmented first MAC-e PDUs174.

The numbering entity161then records the transmission sequence number onto the TSN field177of the first MAC-e PDUs174and records the logical id of the first MAC-e PDUs174onto the logical channel id field183. If the first MAC-e PDU174originates from the CCCH entity146, the content of the logical channel id183is set to zero.

The multiplexing and E-TFC selection entity162later adds the second MAC-e headers onto to the first MAC-e PDUs174to form the second MAC-e PDUs180and records the logical channel id information of the first MAC-e PDUs174onto the logical channel id fields183.

The multiplexing and E-TFC selection entity162multiplex the second MAC-e PDUs180as directed by information received from a UTRAN side of the E-RACH.

The UE id setting entity163afterwards add UE id information onto the third MAC-e headers of the third MAC-e PDUs190to resolve contention and indicate the presence status of the UE id information in the F field192.

The UE id information is removed from the third MAC-e header, as shown in the second MAC-e PDU185, when the UTRAN side of the E-RACH feedback a correct reception of the content of the UE id field193. The UTRAN can confirm the correct reception of the content of the UE id field193by feeding back the content of the UE id field193back to the UE side of the E-RACH. The F field187of the second MAC-e PDU185is updated to reflect the absence status of the UE id field193.

The HARQ entity164receives the second MAC-e PDUs185or the third MAC-e PDUs190, stores the second MAC-e PDUs185or the third MAC-e PDUs190. The HARQ entity164later sends the second MAC-e PDUs185or the third MAC-e PDUs190to the PHY layer of the UE, and re-transmits any lost or corrupted PDU.

In a generic sense, the MAC-c sub-layer155may evaluate the UE id of the RLC PDU160from the CCCH entity146with respect to assigning the data. The MAC-c sub-layer155may send the RLC PDU160to the segmentation entity160and not bypass the segmentation entity160.

FIG. 9illustrates a simplified protocol architecture200for E-RACH in the side of a UTRAN. TheFIG. 9shows parts that are similar to the parts ofFIG. 7. The similar parts are denoted are with similar names. The description ofFIG. 7is included by reference, where appropriate.

TheFIG. 9shows a mapping of CCCH, DCCHs and DCTH to E-RACH on the UTRAN side of the E-RACH. The simplified protocol architecture200comprises a left part and a right part. The left part shows a RLC layer201and a MAC layer202. In contrast, the right part shows decompositions of PDUs.

The RLC layer201is located above the MAC layer202. The MAC layer202comprises a MAC-d sub-layer204, a MAC-c sub-layer205, a MAC-es sub-layer206, and a MAC-e sub-layer207. The MAC-d sub-layer204is provided above the MAC-c sub-layer205whereas the MAC-c sub-layer205is located above the MAC-es sub-layer206. The MAC-es sub-layer206is provided above the MAC-e sub-layer207.

An important aspect is to place the MAC-c between MAC-es and MAC-d such that the operation in E-RACH mode and E-DCH mode are harmonized.

The DCCH entities211and the DTCH entities211are connected to the reassembly entities215whilst the reassembly entities215are connected to the reordering entities216, which are in turn connected to the reordering queue distribution entities217. The CCCH entity210is connected to the reordering entity216, which is in turn connected to the UE de-multiplexing and separation of CCCH entity218.

The UE de-multiplexing and separation of CCCH entity218is connected to the de-multiplexing entity219via one or more lub flows. The number of lub flow is dependent on NW (network) configuration. The UTRAN may separate a SRB (signal radio bearer) and from a RB (radio bearer) for different transport QOS.

The de-multiplexing entity219is connected to HARQ entities220. The number of HARQ entities220connected to the de-multiplexing entity219is dependent on the number of UE simultaneously accessing the E-RACH.

As shown in theFIG. 9, a RLC PDU222corresponds to the RLC layer201. The RLC PDU222comprises a header field223and a data field224. A MAC-d PDU226, which corresponds to the MAC-d sub-layer204, includes a data field227. A MAC-c PDU228corresponds to the MAC-c sub-layer205. The MAC-c PDU228includes a data field229. A first MAC-es PDU230corresponds to the reassembly entities215and the reordering entities216. The first MAC-es PDU230includes a first MAC es-header and a data field231. The first MAC-es header includes a length field232, a TSN field233, and a SI field234. A second MAC-es PDU236, which corresponds to the reordering queue distribution entity217, includes a second MAC-e header, and a data field237. The second MAC-e header comprises an F field238, a logical channel id field239. A first MAC-e PDU240and a second MAC-e PDU250correspond to the de-multiplex entity219and the HARQ entities220. The first MAC-e PDU240comprises a first MAC-e header and a data field241. The first MAC-e header includes a F field242and the logical channel id field243. The second MAC-e PDU250comprises a second MAC-e header and a data field251. The second MAC-e header includes a F field252, a UE id field253, and the logical channel id field254.

A method of an uplink transmission at the UTRAN side of the E-RACH comprises the step of receiving the first MAC-e PDUs240or the second MAC-e PDUs250from the HARQ164of the UE side ofFIG. 8, by the HARQ entity220. The HARQ entity220then sends the first MAC-e PDUs240or the second MAC-e PDUs250to the de-multiplex entity219and indicates delivery status of the first MAC-e PDUs240or of the second MAC-e PDUs250to the HARQ164.

The de-multiplex entity219then sends the received first MAC-e PDUs240or the received second MAC-e PDUs250to the UE de-multiplexing and separation CCCH218via one or more lub flows depending on network configuration.

The UE de-multiplexing and separation CCCH218assigns the received first MAC-e PDUs240or the received second MAC-e PDUs250to the appropriate reordering queue distribution entity217based on the information in the logical channel id field243or254. The UE de-multiplexing and separation CCCH218also removes the F field238and the logical channel id field239from the second MAC-es PDU236to form the first MAC-es PDU230and sends the first MAC-es PDU230to the reordering entities216.

If the content of the logical channel id is zero, the MAC-e PDU240is sent to the reordering entity216for transmission to the CCCH entity210or directly to the CCCH entity210.

The reordering entity216reorders the first MAC-es PDU230based on the information in the TSN field233of the first MAC-es PDU230and then sends the reordered first MAC-es PDU230to the reassembly entity215.

The reassembly entity215then reassembly the reordered first MAC-es PDU230based on data in the length field232and the SI field234of the first MAC-es PDU230. The length field232, the SI field234, and the TSN field233are removed from the reassembled first MAC-es PDU230. The reassembly entity215later sends the MAC-d PDU226to the RLC layer201via the MAC-d sub-layer204, or the MAC-c PDU228to the RLC layer201via the MAC-c sub-layer205.

The embodiments ofFIGS. 8 and 9illustrate a E-DCH type of transmission in CELL_FACH state, in random access procedure, and in uplink HARQ. The embodiments are a natural counter-part to DL HSDPA (High Speed Downlink Packet Access) operation in CELL_FACH state since the header structure of the embodiments is very similar to header structure introduced for HSDPA, release 7.

FIG. 10shows a method of transmitting data between an UE (user equipment) and a Node B of an UMTS type system ofFIG. 1in which an UE ID can be omitted. The transmission is over an E-DCH (enhanced dedicated channel) whilst the UE stays in a same cell of the Node B.

The method comprises a first mode of transmission and a second mode of transmission. The UE transmits to the Node B a message with UE ID in the first mode of transmission whilst the UE transmits to the Node B a message omitting the UE ID in the second mode of transmission.

In the first mode of transmission, the UE sends to the Node B a first transmission262on a UL (uplink)23. The first transmission262includes a preamble264and a first uplink message265. The preamble264and the first uplink message265are scrambled with a common scrambling code. The first uplink message265includes a first UE id266, a MAC header267, and a data part268. The first UE id266can be in a form of a C-RNTI (Radio Network Temporary Identity). The MAC header267includes an F field that includes the presence status of the first UE id266in the first uplink message265. The first uplink message265has a length that is equal to a (TTI) Transmission Time Interval of the E-DCH transport channel.

The Node B later receives the first uplink message265and sends an ACK (acknowledgement) data packet269to the UE to indicate receipt of the first uplink message265. The Node B determines the presence status of the UE ID from the F field of the first uplink message265.

The Node B or another part of an UTRAN later allocates a second UE ID to the UE. The allocation of the second UE ID can also be performed by a RNC (radio network controller) of the UTRAN. The second UE ID can be randomly chosen. The Node B determines the presence status of the UE ID from the F field of the first uplink message265.

The Node B then uses downlink (DL) to allocate F-DPCH (Fractional Dedicated Physical Channel) resources together and echoes the first UE ID266that was received from the first uplink message265back to the UE. The allocation of F-DPCH resources can occur before or after the echoing the first UE id266after first transmission262.

The UTRAN then changes to the second mode of transmission in which the Node B later assigns274the UE with a dedicated scrambling code and sends the dedicated scrambling code to the UE. The scrambling code is dedicated in the sense that the scrambling code is unique within the cell the UE is attached to. The other UEs within the cell do not have scrambling codes that is the same as the dedicated scrambling code. The Node B also stores a mapping between the second UE ID and the dedicated scrambling code or between the first UE ID and the dedicated scrambling code.

The UE then receives the dedicated scrambling code and echoes the correct first UE id266with an ACK data packet270to the Node B. The UE ID is later omitted from the MAC header272in transmission273of subsequent messages277from the UE and the subsequent messages277are then scrambled with the dedicated scrambling code.

The Node B afterward receives subsequent messages277with the dedicated scrambling code from the UE and later determines which UE sends the subsequent messages277by determining which UE the dedicated scrambling code is mapped to.

The Node B may later include the second UE ID into a FP (frame protocol) of the data part or of a header when transmitting the PDU to the RNC.

In another words, the UE uses a common scrambling code and makes HARQ retransmission with the common scrambling code until the UE is allocated with the dedicated code. As the retransmissions are done with the HARQ, the MAC PDU and the MAC PDU retransmitted by the HARQ are similar.

If UE makes a completely new E-DCH or E-RACH access, such as cell reselection in that no dedicated scrambling code has been assigned, the UE selects the first mode of transmission in which it requests for a new dedicated scrambling code by transmitting an E-DCH or RACH preamble as in a normal access. The preamble specific common scrambling code is used for the message part and the UE ID is included into message part.

The ACK data packets, as provided here, are for confirmation of receipt of data packets.

In an example where a plurality of UE is attached to the UTRAN, each UE is assigned a unique dedicated scrambling code by the UTRAN and the UTRAN maps the unique dedicated scrambling code to an ID of each UE. The UE transmits to the UTRAN messages that are scramble with the unique dedicated scrambling code.

In a generic sense, the transmission can be over an E-DCH, an E-RACH or a physical channel that is similar the E-DCH. The transmission of ACK data packet can be replaced by a Fast retransmission of packets or another way to acknowledge the receipt of data packets. The UE id can be in a MAC header of a MAC layer. The UE ID can be omitted from a MAC header of MAC layer in transmission of subsequent messages from the UE.

In summary, the method of omitting UE id in transmission between an UE and a Node B comprises the step of sending an UE id by an UE in an uplink channel for an E-RACH or E-DCH procedure for contention resolution. The Node B assigns a resource to the UE. The resource can be a dedicated scrambling code. The UE later stops adding the UE id in every E-RACH TTI (transmission timing interval) on a MAC header and the UE transmits data with the dedicated scrambling code. The Node B receives the data with the dedicated scrambling code and maps the data to the previously received UE id and thus resolving contention.

If the UE is performing cell update or the UE is performing URA update due to cell reselection or due to RRC Connection request procedure, the UE initiates the process to omit UE id by starting a new E-RACH procedure in the new cell and includes its UE id in an E-RACH message for initial TTIs to resolve contention.

The FLAG and UE id fields can be used in CELL_FACH and CELL_DCH state wherein the flag field indicates the presence status of the UE id in the MAC-e header. When UE is performing random access, the UE uses the flag field to indicate the presence of the UE id in the MAC-e header. The UE id is used to solve contention.