Initial connection establishment in a wireless communication system

[0001] The present invention relates generally to wireless communication technology, and more particularly to an initial connection procedure between a user equipment and a network equipment in a wireless communication system.

2. Description of the Related Art [0002] In wireless communication systems, there is a need for a logical connection between a mobile station (also referred to as User Equipment (UE), a user terminal, a mobile terminal, a wireless terminal and a mobile phone) and a radio access network . The radio access network may include one or more base stations (also referred to as node B, e.g. in 3GPP terminology) together with one or more Radio Network Controllers (RNC). The logical connection provides the context for a particular network to a UE communication link through which data can be transmitted without communication errors to network elements or UEs in the system that were not intended to participate in the communication.

[0003] In the 3GPP radio access network system described in TS 125331 "Universal Mobile Telecommunications System (UMTS)", ETSI TS 12331 V 3.1.0, the logical connection between the user terminal and the radio access network is defined by the connection connection states Radio Resources (RRC). The two main RRC connection states are defined as combined RRC and passive RRC.

[0004] If there is a logical connection between the user terminal and the radio access network, the user terminal should be in a connected RRC state. The existence of a user terminal in an RRC connected state may be determined within a cell or multiple cells. Therefore, radio resources for a specific user terminal can be efficiently managed over a wireless network. Unlike the RRC connected state, the RRC passive user terminal has no logical connection to the wireless network. As a result, the user terminal in the RRC passive state can only be determined within a backbone or area that is larger than the cell, such as a location area or routing area.

[0005] When the user terminal is initially enabled by the user, the Public Land Mobile Network (PLMN) is selected, and the terminal searches for the appropriate cell and remains in the passive RRC state in the corresponding cell. The initial RRC connection can be initiated by the network or by the user's device. For example, in the case of a UE initiated connection for a UE in the RRC passive state, the UE requires an initial connection to the network and sends an RRC connection request message to the network. According to another example, in the case of

EP 1 974 572 B1

V4350PL00 / LB of the network initiated connection, the RRC connection request message may also be sent by the UE in response to the receipt of the paging message from the network (the network has previously sent the paging message to the UE to start the RRC connection procedure).

[0006] There are therefore many reasons for the UE requesting an RRC connection. For example: (1) Initial cell access: when the UE tries to establish a telephone connection, the UE needs to establish an RRC connection; (2) Paging reply: when sending a reply message to the paging message; (3) Cell update: when the UE selects the appropriate cell during presence in passive mode; (4) Updating the UTRAN routing area UTRAN Routing Area (URA): when the UE selects the appropriate URA while in passive mode; and (5) MBMS connection (Multimedia Broadcast and Multicast): to receive the MBMS service and to request a point-to-point MBMS connection.

[0007] With the standard RRC connection procedure, the user terminal initiates the connection procedure by sending an RRC connection request message to the network using common uplink transport channels. Common uplink transport channels are shared by the UE and are used for unscheduled data transmission.

[0008] The network considers the connection request and may return downlink RRC connection configuration message (in case of successful acceptance) or RRC connection rejection message (in case of unsuccessful acceptance). In both cases, the message is sent using common uplink transport channels, which are (like common uplink channels) shared by the UE and used for unscheduled data transmission.

[0009] The common transport channel, through which messages are sent from the user terminal to the network during this initial RRC connection stage, are referred to as random access channels. Random access transmission can similarly be referred to as unscheduled transmission because no explicit scheduling or coordination of the transmission is performed. Due to the lack of explicit coordination, it is likely that one cell phone will send data using the same uplink transmission resources or uplink identity as another user. In this case, the communication reliability of both transmissions may be compromised due to mutual logical or real interference caused by upward messages at the receiving base station. Cases where more than one telephone transmits data through an uplink resource set may be referred to as collisions.

[0010] Further description of conflicts, unscheduled access, and scheduled access can be found in US Patent Application 11 / 263,044, filed October 31, 2005, and entitled "FREQUENCY DOMAIN UNSCHEDULED TRANSMISSION IN A TDD WIRELESS COMMUNICATIONS SYSTEM," inventor Nicholas W. ANDERSON, which he incorporates here as a reference source.

[0011] Common downward transport channels, used to forward corresponding messages from the network to the user's terminal, are referred to as forward access channels

- FACH).

EP 1 974 572 B1

V4350PL00 / LB [0012] System resources are usually reserved for these up and down common transport channels. Radio resources used for common channels are usually separated from radio resources used for other transport channels. Examples of other types of transport channel include dedicated transport channels and shared transport channels. In the case of dedicated transport channels, data is mapped to a subset of all radio resources assigned long-term to a specific user or connection. Conversely, in the case of shared channels, data for each user is mapped more dynamically in a part of the radio resource pool assigned within the set of all radio resources under the control of the resource manager usually located in the MAC layer (layer 2) of the network. Radio resources in this case are therefore shared among users and are allocated by the manager. Unlike shared channels, where users share a radio resource, but in an unplanned manner.

[0013] The use of shared channels can only provide benefits in terms of system capacity compared to the use of many types of channels in the system (e.g., mixtures of shared, shared and dedicated channels), each being assigned to a specific type of transmission. This is because by multiplexing all types of transmission only to shared channels, the manager can dynamically adjust the resources assigned to the different momentary loads occurring on the occasion of each type of transmission. In contrast, if, for example, we assign one type of transmission exclusively to shared channels and another type of transmission exclusively to shared channels, changes in traffic volumes offered by each type of transmission cannot be accepted without reconfiguring the relevant parts of all radio resources assigned first to common channels and secondly to shared channels. This reconfiguration of radio resources is usually a slow process and therefore the system does not respond to rapid changes in intensity. As a consequence, in modern systems, a part of the space of all radio resources assigned to common channels should often be designed taking into account the worst case scenario, and the efficiency of radio resource use is therefore less than optimal.

[0014] Following the standard RRC connection establishment procedure, the UE is known by the network, and the shared channel address or UE identifier can be assigned by the network only after the connection establishment procedure has been completed. Therefore, shared channels can only be used after the normal RRC connection procedure has been implemented using common channel procedures: A significant portion of the space of all radio resources should therefore be pre-assigned to common channels to carry out transmission for establishing a connection. The layer 2 connection context specific to the user terminal used for the operation of shared channels can only be established when the RRC connection procedure is completed.

[0015] In addition, known wireless communication systems spend a considerable amount of time and exchange multiple signaling messages on non-shared and common channels to establish the initial layer 2 context for the operation of common channels and this may contribute

EP 1 974 572 B1

V4350PL00 / LB for communication delays. In addition, the existence of many types of channels and related protocols, procedures and attributes can significantly increase the complexity of system implementation.

[0016] For the above-mentioned reasons, it is necessary to improve the RRC connection procedure and the initial access to the system in order to increase the efficiency of the use of radio resources in order to reduce communication delays and reduce the complexity of the system implementation.

SUMMARY OF THE INVENTION [0017] Some embodiments of the present invention provide an immediate establishment of a layer 2 shared channel context by enabling the UE to derive its own layer 2 address as a temporary identifier until the network decides to replace the temporary identifier derived by the UE with the identifier selected by the network. This allows the system to use shared channels instead of shared channels at a very early stage of establishing the connection and thus minimize the amount of transmission on shared channels.

[0018] Furthermore, some embodiments of the present invention provide a method, device (such as a user device or network device), computer software product or system for initiating a wireless connection and further communication within a shared physical resource in a wireless communication system between the user device and the network device , including: processing a temporary identifier issued by the EU; sending the temporary identifier to the network device; sending a message down, transmitting a temporary identifier and a description of the planned resource via a shared channel, the scheduled resource includes a resource allocated to the user's device by the network device, and sending data via the scheduled resource in response to the message down.

[0019] Some embodiments of the present invention provide for the creation of a temporary identifier from part of the UE identifier of a known network, such as. from the temporary mobile subscriber identifier (TMSI), the international UE mobile subscriber identifier (IMSI) or the international UE identifier (IMEI). Some embodiments of the present invention provide for the selection of a temporary identifier from a set of temporary identifiers. Some embodiments of the present invention provide for deriving a temporary identifier based on a time parameter. Some embodiments of the present invention provide for the indication of the set of temporary identifiers to the UE from the network device, e.g., via the broadcast channel (BCH). Some embodiments of the present invention provide for storing the set of temporary identifiers in non-volatile memory.

[0020] Some embodiments of the present invention provide for the temporary identifier to be sent to the network device in the first uplink message containing the temporary identifier and, for example, to request a scheduled uplink or downlink resource, as well as to send the temporary identifier during further communication between the user equipment and the network .

EP 1 974 572 B1

[0021] Some embodiments of the present invention provide for exceeding the waiting time after sending the first message up and before receiving the message down, selecting a different temporary identifier and re-sending the first message up containing a different temporary identifier instead of the originally selected temporary identifier.

[0022] Some embodiments of the present invention provide for sending RRC connection signaling over shared channels.

[0023] Some embodiments of the present invention provide for the replacement of the replacement identifier from the network device and the use of the replacement identifier instead of the temporary identifier to identify the user equipment in the shared channel resources.

[0024] Some embodiments of the present invention provide for the attachment, coding, or decoding of a user device identifier of a known network in the event of a request, such as a temporary mobile subscriber identifier (TMSI), international mobile subscriber identifier (IMSI) or international UE identifier (IMEI). Some embodiments of the present invention provide for the user device identifier of the known network to be included as a parameter in the request. Some embodiments of the present invention provide for calculating CRC (Cyclic Redundancy Check) values ​​using a known network UE identifier.

[0025] Other features and embodiments of the invention are apparent from the following detailed description in connection with the accompanying drawings, which for example show features in accordance with the embodiments of the invention. The description of the essence is not intended to limit the scope of the invention, which is defined solely by the claims annexed to this document.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS SHOWN IN THE DRAWINGS [0026]

Figures 1A and 1B show a standard sequence of messages to transition from an RRC passive state to an RRC connected state in a conventional UMTS system.

Figures 2, 3A and 3B show a comparison of UTRAN networks and the developed UTRAN network (E-UTRAN) operating together with user equipment (UE) and network (CN).

Figures 3A and 3B illustrate an evolved UTRAN network (E-UTRAN) functioning together with a user equipment and a backbone network in accordance with the present invention.

Fig. 4 shows components of a user equipment according to the present invention.

Figures 5A and 5B show initial signaling sequences in accordance with the present invention.

EP 1 974 572 B1

V4350PL00 / LB

Figures 6A and 6B show in detail signaling sequences using the downlink scheduled in accordance with the present invention.

Figures 7A and 7B show in detail signaling sequences using scheduled downlink and unscheduled and scheduled uplink according to the present invention.

Figures 8A and 8B show in detail signaling sequences using the scheduled downlink and the scheduled uplink in accordance with the present invention.

Figures 9 and 10 show conflict resolution processes in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION [0027] In the following description reference is made to the accompanying drawings, which illustrate several embodiments of the present invention. It should be assumed that other embodiments are possible, and mechanical, composition, structural, electrical, and performance changes may be made without departing from the guiding principles and scope of the present disclosure. The following detailed description should not be considered to a limited extent and the scope of the solutions of the present invention is defined solely by the claims of the granted patent.

[0028] Some portions of the detailed description below are presented in terms of procedures, steps, logic blocks, processing, and other symbolic ways of representing actions on data bits that can be performed in computer memory. The procedure, step performed by the computer, logic block, process and others are understood here as a coherent sequence of steps or instructions leading to the intended result. These steps use physical manipulations of physical quantities. These quantities can take the form of electrical, magnetic or radio signals that can be stored, transmitted, combined, compared, and otherwise manipulated in a computer system. These signals can sometimes be referred to as bits, values, elements, symbols, signs, conditions, numbers and the like. Each step can be performed using hardware, software, firmware or a combination of the above.

[0029] Although the following drawings show the invention with respect to the standard UMTS (Universal Mobile Telecommunications System) system, the solutions of the invention may also apply to other wireless radio systems. A standard UMTS system typically includes many user devices (UEs), which are sometimes referred to as user terminals, mobile stations, mobile terminals, wireless terminals, and cell phones. The standard UMTS system also includes a network device including a B node, also referred to as a base station, which provides a radio access connection between UEs and the network, and also includes a radio network controller (RNC).

[0030] Figs. 1A and 1B show a standard message sequence for transition from a passive state

RRC to the RRC connected state in the traditional UMTS system. In a standard UMTS system, a user device in an inactive RRC state can initiate an RRC connection using a procedure

EP 1 974 572 B1

V4350PL00 / LB shown in Figs. 1A and 1B. The UE and the network may exchange messages over logical control channels, each logical control channel being mapped on a common transport channel.

[0031] Fig. 1A shows the communication carried out via the radio interface (Uu). The first message presented is an RRC connection request message which includes the known UE network identifier represented as the global UE identifier (ID) and the reason for establishment. The known UE network identifier may be one of the following: temporary mobile subscriber identifier (TMSI) assigned by the network, international UE mobile subscriber identifier (IMSI) or international UE identifier (IMEI). The establishment cause indicates the reason why the UE requests a network connection. The UE may request a connection when sending a reply message to the paging message (paging response), when selecting the appropriate cell in the inactive mode (cell update), when selecting the appropriate URA in the inactive mode (URA update), and when receiving the MBMS service or the MBMS connection point -point (MBMS connections).

[0032] Next, the network performs acceptance control and assigns the values ​​of the Radio Network Temporary Identifier (RNTI). The network uses an admission control process to determine if the requested service can be served by the network due to the establishment. Factors taken into account when performing admission checks may include the mobile access class for determining access rights, RRM (Radio Resource Management) status for determining resource availability, user subscription details, as well as device registers containing lists of valid and stolen terminals.

[0033] RNTI value assignment relates to a network assigning a Radio Network Serving (RNC) RNTI (S-RNTI) that is used by the UE to identify itself to the RNC Serving (RNC Serving).

S-RNTI is also used by SRNC for UE addressing. The S-RNTI value is allocated by the SRNC to each UE having an RRC connection and is unique within the SRNC. S-RNTI can be reassigned after changing SRNC for an RRC connection. The S-RNTI may be associated with an SRNC (SRNC ID) received on the uplink to create a unique RNTI (U-RNTI) within the UTRAN network. Alternatively, the network may assign a C-RNTI (Cell Radio Network Temporary Identifier). C-RNTI can be allocated and used in shared transport channels. The C-RNTI value can be used to identify the UE based on the cell. In a traditional network, the decision to use C-RNTI is made by the CRNC (Controlling Radio Network Controller).

[0034] After the network device has successfully carried out the admission control process as well as the allocation process, the network will respond to the RRC connection request message with a connection configuration message.

RRC including the UE global identifier, the newly assigned S-RNTI value, optionally the CRNTI value, as well as the radio device user configuration.

EP 1 974 572 B1

V4350EN00 / LB [0035] After the UE has processed the RRC connection setup message, the UE responds with a RRC connection setup complete message. The RRC connection setup complete message accompanies the C-RNTI value in the header field and includes UE radio access capability. At this point, the UE switches to the connected RRC state.

[0036] In response to receiving an RRC connection setup complete message and in a situation where HS-DSCH High Speed ​​Downlink Shared CHannel is used for downward data transmission, the network may assign an H-RNTI value to the UE within RRC radio bearer configuration message to the UE. The H-RNTI value is used to identify the UE in a fast downward shared channel. The RRC radio bearer configuration message includes the assigned SRNTI, the assigned H-RNTI, and the shared bearer radio configuration. The UE terminates the process by responding with a RRC radio bearer configuration complete message. At this point, the UE and network have established layer 2 context for shared channel operations.

[0037] Fig. 1B illustrates UEs and network devices and the communication between these elements. The UE includes layer 3 containing the RRC layer, layer 2 containing the RLC (Radio Link Control

- radio link control) and MAC (Medium Access Control) layer, as well as layer 1 containing the physical layer (L1). Node B includes a physical layer (L1) of layer 1. RNC includes a layer 2 comprising a MAC layer and an RLC layer, as well as a layer 3 comprising an RRC layer and an RRM layer. Note that additional Layer 1 features exist at both B and RNC to provide physical connections between these units (interface or), although they are not shown to increase the clarity of the drawing. The RRC connection request message is initiated by the RRC layer in the UE. RRC sends the message to the RLC layer, which sends the RRC connection request message on the common control channel (CCCH) mapped on the RACH using the transparent RLC (TM) mode. When using Transparent Mode (TM), the sender of the message does not attach the message sequence identifier, unlike confirmation (AM) and unacknowledged (UM) modes, which include the message sequence identifier, which can be used to identify / reorder sequence packets and to identification of lost packets. Confirmation mode (AM) also provides for the message to be re-sent. CCCH is a common logical control channel between RLC and MAC layers, and the RACH channel is a common transport channel between MAC and L1 layers. The RRC connection request message is sent via the radio interface (Uu) to the network.

[0038] After receiving the RRC connection request message, the Node B layer 1 sends the message over the RACH channel to the RNC MAC layer. The RACH channel is an upward common transport channel used to send control information and data from the UE through random access physical resources that can be shared by multiple UEs and are used for unscheduled data transmission. The MAC layer sends the message to the RLC layer over the CCCH channel. In turn, the RLC layer sends the message to the RRC layer, which sends the message to the RRM layer for the purposes of admission control, assignment of the S-RNTI value and optionally assignment of the C-RNTI value.

EP 1 974 572 B1

[0039] After successful acceptance control and S-RNTI value assignment, RRM returns the assigned S-RNTI value to the RRC layer, which creates an RRC connection setup message for transmission in an unacknowledged mode (UM). C-RNTI, which identifies UEs within a cell, is usually also allocated. However, in case the dedicated physical channel connection should be configured immediately, C-RNTI may be omitted. RRC sends the RRC connection setup message to the RLC layer. The RLC layer sends the message to the MAC layer over the CCCH channel. The CCCH is used because the common RNTI context does not yet exist between the network and the UE. That is why the network knows the RNTI values, but the UE does not know the RNTI values ​​at this stage. The MAC layer sends the message via the FACH (Forward Access Channel). The FACH channel is a downstream common transport channel that can be used to send control information and data to the UE when the network knows the UE location cell. The FACH channel may be shared by multiple UEs for unscheduled downstream data transmission. Layer 1 of the Node B sends the message to the UE via the radio interface (Uu).

[0040] Unfortunately, each UE monitoring the FACH channel decodes absolutely every RRC connection setup message and other messages to determine if the attached message is addressed to it. After the UE receives the RRC connection setup message, the UE layer 1 sends the message over the FACH channel to its MAC layer, which sends the message over the CCCH channel to the RLC layer, which in turn sends the message to the RRC UE layer. The RRC UE may then check the global ID field contained in the connection configuration message to determine if it matches its own global UE identifier. If not, the message is rejected. If the IDs match, the message is decoded and the UE records the S-RNTI assignment and, if possible, the C-RNTI values. At this point, the UE has a dedicated control channel (DCCH) allocated to it.

[0041] Next, the UE responds with an RRC connection setup complete message that is sent using acknowledgment mode (AM) to the network. The RRC layer sends the message to the RLC layer, which uses the DCCH channel to send the RRC connection setup complete message to the MAC layer. The MAC layer sends the message via the common transport RACH channel to the physical layer (L1), which sends the message via the radio interface (Uu) to node B. The data transmitted by DCCH through the resources of the common transport channel is accompanied by a header field in which C-RNTI is included to distinguish the UE based on a cell from a set of other UEs using the common transport RACH channel in that cell. For data sent over dedicated or shared transport channels, no C-RNTI is required in the header because user identification / addressing is achieved at the physical resource level (mapping between the physical resource and the user's terminal is known in the physical layer). After the UE sends the RRC connection setup complete message, the UE goes into the connected RRC state.

[0042] Next, the Node B receives the RRC connection setup complete message via the radio interface (Uu). Its layer 1 sends a MAC layer RNC message using the RACH channel. Layer

EP 1 974 572 B1

V4350PL00 / LB

The MAC reads the header (containing C-RNTI) and sends the message to the appropriate RLC entity using the appropriate DCCH channel. The RLC sends the message to the RRC layer.

[0043] The network uses a different value to identify the UE when the UE communicates via a fast downward shared channel (HS-DSCH). This value is allocated by the RRC layer and assigned the value HS-DSCH RNTI (H-RNTI). The H-RNTI value is used as a temporary identifier while the UE has an established connection via the HS-DSCH. The network sends the assigned H-RNTI value to the UE as part of the radio device user configuration message using the DCCH channel between the RLC and MAC layers, and the FACH channel between the MAC layer and the UE layer 1. The Node B sends a message via the radio interface (Uu) to the UE. The UE layer 1 sends the message over the FACH channel to its MAC layer, which sends the message to the RLC via the DCCH channel. The RLC sends the message to the RRC layer, which corresponds to the message of the user configuration configuration of the RRC radio device being sent to the network using the RLC (AM) confirmation mode. The channel path between the UE RRC layer and the RRC RNC layer copies the channel path described above for signaling the RRC connection complete message.

[0044] After the H-RNTI is allocated, the UE may then use the fast (hs) downward shared transport channel for downward communication needs. Resource allocations for this channel are granted by a manager located in the MAC-hs entity on node B. The MAC-hs entity may address the UE in the cell when allocating fast downstream shared channels using H-RNTI as the UE identifier.

[0045] The MAC-hs unit is not shown in the figure because it does not participate in the connection configuration procedure and related communication. The communication used to establish the RRC connection is not forwarded to shared transport channels.

[0046] At this point, the UE and the network established and formed the layer 2 context of the shared channel, and the network allocated the shared channel identifier to the UE. When creating this layer 2 context, the network assigns an identifier and exchanges three messages up and two down.

[0047] According to the present invention, the UE outputs a temporary identifier (temp ID) to immediately establish a layer 2 context for faster communication over shared transport channels. This faster layer 2 context can eliminate the need for extensive communication through common transport channels and avoids the need to reserve significant portions of all available radio resources for common channels. This assignment is usually slow when it comes to reconfiguration and therefore does not respond to rapid changes in traffic. If the derived UE temporary identifier is unique in the network during use, the UE may be uniquely identified on the shared channel, and the data may be transmitted using dynamic assignment of shared channel resources rather than via statically assigned common resources, as is the case in traditional systems. In addition, the network may update the derived UE temporary identifier during or after the RRC connection process.

EP 1 974 572 B1

V4350PL00 / LB [0048] Figs. 2, 3A and 3B compare the UTRAN network and the developed UTRAN network (E-UTRAN) operating with user equipment (UE) and network (CN) in accordance with the present invention.

[0049] Fig. 2 shows a multiple UE and UTRAN network device. The UTRAN network device provides a UE link to the backbone network. A UTRAN device is also referred to as a Radio Access Network (RAN) and contains one or more RNS (Radio Network Subsystem). Each RNS contains an RNC controller and one or more B nodes. For RRC signaling, RNC provides RRM, RRC, RLC, and MAC signaling layers, and Node B provides layer 1.

[0050] Fig. 3A illustrates the architecture for implementing the invention in accordance with some embodiments of the present invention. The developed UTRAN network (EUTRAN) provides the LTE (Long Term Evolution) platform to simplify the UTRAN architecture and reduce the number of connections between components. The term "expanded" and the prefix "E-" can be used to distinguish conventional components or elements that may be similar to the corresponding components or elements of the present invention. The E-UTRAN network provides a link for the UE to communicate with the backbone network (CN). The EUTRAN network includes an LTE gateway (LTE GW) coupled to one or more developed B nodes (E-node B) that perform the functions of both Node B and RNC in Fig. 2. The LTE gateway provides an interface between the backbone network and E-nodes B For RRC signaling, E-node B provides RRM, RRC, RLC, MAC and L1 signaling layers. In this case, the designations "expanded" and the prefix "E-" have been omitted for some marked components in the E-UTRAN network for brevity.

[0051] Fig. 3B illustrates another architecture for the E-UTRAN network. The LTE gateway provides an interface between the backbone network and E-nodes B, and also provides RRM and RRC layers for RRC signaling. For this architecture, E-nodes B provide MAC and L1 signaling layers.

[0052] The solutions of Figures 3A and 3B provide a MAC layer and an RLC layer combining with layer 1 processing, which helps reduce signaling delays. Fig. 3A shows a set of each of the layers used during the RRC connection establishment procedure, which further helps reduce signal delays.

[0053] Fig. 4 shows components of a user equipment according to the present invention. The user equipment includes a memory for storing a temporary identifier output by the UE, a processor, a program code for obtaining a user identifier derived by the UE and storing the identifier in memory, as well as a transceiver for communication with an E-UTRAN network device. The memory may be volatile memory, such as RAM, or non-volatile memory, such as flash memory (EEPROM). The memory may be part of the UE system or it may be an electronic card installed in the UE housing. The processor can be a computer with a reduced instruction list (RISC), a standard processor, a specialized processor, a processor implemented in gate logic, etc. The program code can be machine executable code, object code, script or other code interpreted by the computer or compiled. The program code can be compressed or uncompressed, and can also be encoded or uncoded. The transceiver can 11

EP 1 974 572 B1

The V4350PL00 / LB is a transmitter-receiver pair using the Code Division Multiple Access (Code Division Multiple Access) technique and operates in Time Division Duplex (TDD) mode or Frequency Division Duplex (FDD) mode.

[0054] Figs. 5A and 5B show initial signaling sequences in accordance with the present invention. In each of the drawings, the UE first derives a temporary identifier (temp ID). The process of deriving the temporary identifier may differ for different embodiments of the present invention. The derivation of a temporary identifier provides a direct layer 2 context for layer 2 communication over shared transport channels that are scheduled by the E-MAC entity at E-node B. The derivation of a temporary identifier preferably takes place in a manner that minimizes to an acceptable level that the two The UE will derive the same temporary identifier. If two UEs derive the same temporary identifier within a cell and try to use it in overlapping time units, additional conflict detection and resolution procedures may be used.

[0055] In some embodiments of the present invention, the UE derives the temporary identifier by forming the temporary identifier from the UE identifier part of the known network. The known network identifier UE may be one of the following: temporary mobile subscriber identifier (TMSI), international UE mobile subscriber identifier (IMSI) or international UE identifier (IMEI) assigned by the network. The UE may use a predetermined number of less-significant TMSI, IMSI or IMEI bits. For example, if TMSI is available, the UE may derive the temp ID by using the 16 lower bits of 32-bit TMSI. If TMSI is not available, the UE may use the lower 16 bits of 32-bit IMSI. If neither TMSI nor IMSI are available, the UE may use the 16 lower bits of the 32-bit IMEI.

[0056] In some embodiments of the present invention, the UE derives a temporary identifier by selecting the temporary identifier from the set of temporary identifiers. The set of temporary identifiers may include a subset of possible values ​​with a common bit length. For example, the set of temporary identifiers may include 1/8 possible permutations of 16 bits. The network can reallocate temporary identifiers by selecting values ​​from the remaining 7/8 possible permutations to eliminate the possibility of potential conflict with EU derived values ​​in the future. The set of temporary identifiers can be stored as an array in RAM or ROM. In some solutions, the set of temporary identifiers is created by the UE. In some solutions, the set of temporary identifiers is sent to the UE from the network. In some solutions, the indication of the set of temporary identifiers is sent through the broadcast channel (BCH) from the network to the UE. In some solutions, the set of temporary identifiers is saved in non-volatile memory.

[0057] In some embodiments, the temporary identifier output by the UE may also be a function of time or number of radio frames. The function can change in accordance with a predetermined pattern or signaled user equipment, for example using a spreading channel (BCH).

EP 1 974 572 B1

V4350PL00 / LB

Alternatively, the change pattern may contain a random element in its source. The use of a time-varying component or time parameter (such as system clock, number of superframes, number of subframes, number of time slots) by a user device when deriving a temporary identifier may advantageously help reduce the likelihood that two or more users will choose the same temporary identifier in a given time frame.

[0058] After deriving the temporary identifier, the UE sends this derived identifier to the EUTRAN in the first message up. The initial context of the shared L2 channel is created as soon as the network receives the initial temporary identifier. At this stage, both the UE and the network know the value of the temporary identifier. However, such a connection can cause a collision, and a more permanent connection (without the possibility of a collision) can be created after the network reassigns a replacement temporary identifier.

[0059] After receiving the temp ID, the network allocates a physical resource. The allocated physical resource describes resources allocated to the UE, such as those that would enable the UE to correctly encode and send or receive and decode data messages. The description may contain attributes such as: (1) absolute or relative transmission time; (2) a description of the physical channel resources, such as codes, frequencies, subcarriers, time / frequency codes and / or the like; (3) type of data formatting in resources; and / or (4) FEC encoding type, block size, modulation format and / or the like.

[0060] This physical resource may be an uplink resource (as shown in Fig. 5A) or a downlink resource (as shown in Fig. 5B). The network sends the first message down to the UE containing the temporary identifier derived by the UE as the destination address, as well as a description of the allocated physical resource. The UE and network then send user data or signaling data (data) through the allocated physical resource.

[0061] Fig. 5A shows data transmitted via a scheduled uplink shared resource allocated by the network and described in the first down message. For uplink data, the UE may send data only after the UE receives and processes the first down message containing the description of the allocated physical resource. The UE may initiate this sequence of deriving the temp ID and acquiring the uplink physical resource when the UE intends to send user data or signaling data to the network.

[0062] Fig. 5B shows data transmitted via a receiving scheduled shared resource, allocated by the network and described in the first down message. For downstream data, the UE may receive and process the data only after the UE receives and processes the first down message containing the description of the allocated physical resource. In some solutions, the first down message is sent and received in a packet that also contains the second down message. In this case, the UE processes the received packet to obtain the allocated physical resource. If the assignment indicates that user data or signaling data is included

EP 1 974 572 B1

V4350PL00 / LB in the same packet as the first down message containing the allocation, the UE may reprocess the received packet to obtain a second down message.

[0063] The traditional system configures both shared and shared channels. Resource segmentation limits the efficient use of combined resources. For example, if most transmissions at a given time use shared channels, then shared channels remain inactive. Conversely, if most traffic uses configured shared channels, then shared channels remain unused. In accordance with some embodiments of the present invention, a minimum resource set can be assigned for unscheduled messages, such as the first upward message in Figs. 5A and 5B. Messages up on this channel may be limited to short messages containing only temp ID or possibly containing temp ID and an indication of what type of resource is required. Unscheduled channels down (e.g. FACH) can be removed from the configured channels because each UE initiates contact with the network using the addressable layer ID of layer 2. The rest of the resources can be dynamically allocated between the control channel message (e.g. first down message) and user data or signaling data (i.e. second message up or down). This allocation of resources provides a higher bandwidth system due to better resource efficiency.

[0064] As shown in FIGS. 6A and 6B, some embodiments of the present invention use a RACH (Random Access Channel) channel for the first up message, a scheduled channel for down messages, and a common channel for subsequent up messages. As shown in fig. 7A and 7B, some embodiments of the present invention use a RACH (Random Access Channel) channel for the first up message and scheduled channels for subsequent up and down messages. As shown in Figs. 8A and 8B, some embodiments of the present invention use a RACH (Random Access Channel) channel for shortened upward initial message and scheduled channels for subsequent up and down messages.

[0065] Figs. 6A and 6B show in detail signaling sequences using the downlink scheduled in accordance with the present invention. The UE outputs the temporary identifier and sends the temporary identifier in the first message upwards to the network. In addition to temp ID, the first upward message contains the establishment reason parameter and two optional parameters: buffer occupancy and global UE ID. The establishment cause and global UE ID may be the same or similar to the corresponding parameters described above with reference to Fig. 1A.

[0066] Buffer occupation can be used as an indication of the amount of current data for transmission in the UE transmission buffer and can be used by the resource manager at node B to determine the range of resources to be allocated for uplink transmission. The buffer occupancy can be a single bit, a range of quantized values, an absolute value in bytes, or a list of values, e.g. one for each transmission flow, types or priority streams.

[0067] The UE may send an RRC connection request message using transparent mode (TM). When the network device receives the RRC connection request message, the network performs a check

EP 1 974 572 B1

V4350PL00 / LB admission (described above with reference to Fig. 1A) and allocates the physical resource: upstream shared channel (UL-SCH) or downstream shared channel (DLSCH) as indicated by the establishment reason parameter. Alternatively, the network can also allocate S-RNTI and a replacement temp ID.

[0068] The network sends a first down message containing an downward scheduling allocation indication including a temp ID for addressing a specific UE and a description of the allocated physical resource. The first downward message can be sent through a shared physical control channel (SPCCH) monitored by user equipment or waiting for any scheduling messages. The network can also send a replacement temporary identifier. The network can select a replacement temporary identifier from a list or array of unique identifiers not selected by user devices. Such a replacement temporary identifier ensures that a message containing the temporary identifier derived by the UE from the first UE will not interfere with a message containing the same temporary identifier derived from by the second UE. As a result, the temporary identifier derived by the UE provides for a limited time probably a unique identifier that can be replaced by a more reliable unique identifier chosen by the network. The replacement temporary identifier may be sent in the RRC connection setup message or it may also be included in the SPCCH grant message.

[0069] Upon receiving the downlink scheduling grant message, the user equipment decodes a short scheduling message and examines the temporary identifier. Only the UE addressed by the temporary identifier must decode a longer message sent or to be sent via a downstream shared channel (DL-SCH). Other user devices not addressed by the scheduling grant message need not use CPU cycles or battery resources to decode the RRC connection configuration or other long messages to determine if the message is routed to it.

[0070] The user equipment identified by the temp ID receives and decodes the message sent on the allocated physical resource described in the downward scheduling grant message. This second down message to the UE may include an RRC connection setup message sent over the network using unacknowledged mode (UM). The RRC connection setup message may optionally include a replacement temp ID, assigned S-RNTI value, and / or a global UE identifier. If the UE receives a replacement temp ID, it will use this replacement temp ID as its temporary identifier when exchanging messages with the network. In addition, the global UE identifier may be included in this first down message when it is received by the network from the RRC connection request message and if a conflict between overlapping temp IDs is detected by the network. In some solutions, the global UE identifier is explicitly included in the message. In other solutions, the global UE identifier is used to encode the message down (e.g., CRC).

[0071] The conflict-handling conflict resolution process is described below with reference to Figures 9 and 10. In addition, in some embodiments, the radio user configuration may be sent to multiple UEs using a broadcast channel (BCH).

EP 1 974 572 B1

V4350EN00 / LB [0072] Next, the UE responds to receiving and processing the RRC connection setup message by preparing and sending the RRC connection setup complete message using the confirmation mode (AM). If a replacement temp ID has been provided by the network, the UE uses this new value as its temporary identifier. The RRC connection setup complete message may also include UE radio access capability parameters indicating different UE capabilities.

[0073] According to the present invention, the information contained in the standard user configuration message of the RRC radio device (Fig. 1A) can be transmitted on a BCH channel and not separately sent to each UE, since information describing a shared channel can be used by many UEs in a cell.

[0074] Fig. 6B illustrates UEs and network devices, and communication between these elements. The UE comprises layer 3 comprising the expanded RRC layer (E-RRC), layer 2 comprising the expanded Radio Link Control layer (E-RLC) and the expanded MAC layer (E-MAC), as well as layer 1 including the physical layer (L1). The E-UTRAN network includes a Layer 1 (L1) physical layer, Layer 2 comprising an expanded MAC layer (E-MAC) and an expanded RLC layer (E-RLC), as well as Layer 3 including an expanded RRC layer (E-RRC) and an expanded layer RRM (E-RRM).

[0075] The RRC connection request message is initiated by the E-RRC layer in the UE. The E-RRC sends the message to the E-RLC layer, which sends the Common Control CHannel (CCCH) RRC mapped request message mapped to the RACH using transparent (TM) mode. CCCH is a common logical control channel between E-RLC and E-MAC layers, and the RACH channel is a common transport channel between E-MAC and L1 layers. The RRC connection request message is sent via the radio interface (Uu) to the network.

[0076] After receiving the RRC connection request message, the layer 1 of the network device sends the message via the RACH channel to the MAC layer. The MAC layer sends the message to the E-RLC layer over the CCCH channel. In turn, the E-RLC layer sends the message to the E-RRC layer, which sends the message to the E-RRM layer to control the acceptance and assignment of a replacement temporary identifier and optionally a replacement S-RNTI value.

[0077] After acceptance control and optional replacement of the temporary identifier and optional allocation of the S-RNTI, the E-RRM returns the allocated values ​​to the E-RRC layer, which creates the RRC connection setup message for transmission in an unacknowledged mode (UM). The E-RLC sends the RRC connection setup message to the E-RLC layer. The E-RLC layer sends the message to the E-MAC layer via DCCH or CCCH.

[0078] Instead of simply sending the RRC configuration message, the E-MAC layer sends the scheduling grant message through the shared physical control channel (SPCCH) to layer 1 for transmission to the UE. The UE layer 1 receives a scheduling grant that indicates the physical resource that will send the RRC connection setup message. The E-MAC layer also sends, simultaneously or later, an RRC connection setup message to Layer 1 using the assigned physical resource

EP 1 974 572 B1

V4350PL00 / LB via shared down channel (DL-SCH). Layer 1 sends the RRC connection setup message over the radio interface (Uu) to the UE. Fortunately, each UE monitoring the radio interface only decodes short planning messages to determine if the attached message was addressed to it, and not the longer RRC connection setup message and other messages.

[0079] After the UE receives the RRC connection setup message, the UE layer 1 sends the message via the DL-SCH channel to its E-MAC layer, which sends the message via the DCCH or CCCH channel to the ERLC layer, which in turn sends the message to the EU ERRC layer .

[0080] Next, the UE responds with an RRC connection setup complete message that is sent using acknowledgment mode (AM) to the network. The E-RRC layer sends the message to the E-RLC layer, which uses the DCCH channel to send the RRC connection setup complete message to the E-MAC layer. The E-MAC layer sends the message over the RACH channel to the physical layer (L1), which sends the message over the radio interface (Uu) to the network. After the UE sends the RRC connection setup complete message, the UE goes into the connected RRC state.

[0081] Then, the network receives an RRC connection setup complete message over the radio interface (Uu). Its layer 1 sends the message to the E-MAC layer using the RACH channel. The E-MAC layer sends the message to E-RLC using the DCCH channel. The E-RLC sends the message to the E-RRC layer.

[0082] Figs. 7A and 7B show in detail signaling sequences using scheduled downlink and unscheduled and scheduled uplink according to the present invention. The scheduling and exchange of the RRC connection request message and the RRC connection configuration message as well as the admission control and resource allocation have been described above with reference to FIGS. 6A and 6B. FIG. 7A and 7B deviate from the previous solution by sending subsequent messages up through shared resources.

[0083] In particular, the UE E-MAC layer receives the RRC connection setup complete message from its E-RLC layer, the UE E-MAC layer first sending the scheduling request message via the RACH channel or through the expanded RACH (E-RACH) channel . A short scheduling request message requests the network allocate up the physical resource. The RRC planning request message is sent via the radio interface (Uu) to the network. After the scheduling request message is received by the network layer 1, the scheduling request message is sent through the RACH channel to the network E-MAC layer. The E-MAC layer allocates the uplink shared channel (UL-SCH) of the UE and describes the uplink allocation in the planning control grant in the shared control channel (SPCCH) from the EMAC layer to layer 1, and then through the radio interface (Uu) to the layer 1 UE that sends the scheduling grant message via the SPCCH to the E-MAC layer. The E-MAC layer sends the RRC connection setup complete message to the layer 1 through the allocated UL-SCH resource for transmission to the network. By using a shared, scheduled uplink and / or downlink scheme in accordance with some embodiments of the present invention, one or more benefits may be achieved. For example, in some solutions, shorter messages within the initial uplink resource may reduce the number of collisions at the physical layer on the radio interface. In some solutions, 17

EP 1 974 572 B1

V4350PL00 / LB logical collisions (occurring due to common temporary identifiers derived by two UEs in overlapping time units) can be overcome by collision removal procedures in the UE and / or by collision removal procedures on the network. In some solutions, resources that would otherwise be dedicated to common RACH and / or FACH channels may be reduced or possibly eliminated, and therefore these resources are available for allocation to other types of transmission using channels. Thus, more efficient use of radio resources can be realized if compared to the case where many types of traffic are not allowed to share resources of the same shared channel and instead should be allocated separate resources. This is because by multiplexing all types of transmission only to shared channels, the manager can dynamically adjust the resources assigned to the different momentary loads occurring on the occasion of each type of transmission. In contrast, if separate radio resources are statically assigned to each type of traffic, changes in traffic volume offered by each type of traffic cannot be accepted without reconfiguring the relevant parts of the entire radio resource space allocated first to common channels, followed by to shared channels. In some solutions, signaling latency and response time seen by the UE may be reduced. In some solutions, the use of scheduled channels means that the UE decodes short scheduling messages and there is no longer the need to monitor and decode each common channel message address to other UEs, which can lead to more efficient use of UE battery life. In addition, in some solutions, the exchange of connection configuration signaling through a fast channel may be faster than in the case of a traditional common channel.

[0084] Figs. 8A and 8B show in detail signaling sequences using the scheduled downlink and the scheduled uplink in accordance with the present invention. In the presented solution, initial upward communication is planned, as well as subsequent ones. Instead of sending an initial message containing an RRC connection request, the UE first sends a short scheduling request message to request the network to allocate an uplink physical resource. The UE outputs and appends the temporary identifier to the short message up. The message may optionally include a buffer occupancy parameter (described above) and a cause parameter. The reason parameter may indicate the reason for the request (e.g., requested uplink physical resource). The network allocates the upstream shared channel (ULSCH) and sends the scheduling grant by the shared physical control channel (SPCCH), including the UE derived temporary identifier and the UL-SCH description. The UE's E-MAC layer receives an upstream scheduling grant message and responds by sending an RRC connection request on the assigned UL-SCH physical channel. An RRC connection request message is received by the network which performs admission control and allocation of additional resources as described above with reference to Figs. 7A and 7B. In addition, fig. 8A shows that some solutions may use acknowledgment mode (AM), while other solutions may use acknowledgment mode (UM) when sending one or both of the RRC connection request message and the RRC connection configuration message.

EP 1 974 572 B1

V4350EN00 / LB [0085] Figs. 9 and 10 show conflict resolution processes in accordance with the present invention. This conflict scenario occurs when two UEs derive and use a common temporary identifier. Each UE sends an RRC connection request message as described with reference to FIGS. 5A, 5B, 6A-B, 7AB or 8A-B. The derivation of the temporary identifier preferably takes place in a manner that minimizes to an acceptable level the possibility that two UEs derive the same temporary identifier. However, in some solutions, two UEs can derive the same temporary identifier within a cell. Therefore, additional conflict detection and resolution procedures can be implemented.

[0086] Fig. 9 shows a remedy mainly used by the UE. For two UEs, each sends a message up to the network using the same temporary identifier (1st temp ID). The up message may be a message sent over the RACH or E-RACH channel. The message may be a scheduling request message (as shown) or some other message. The network can detect the same temporary identifier in two messages up. The network may choose not to process and may allow any EU to exceed its waiting time. After the expected receive response is not received, each UE deletes the initially derived temporary identifier and outputs the next temporary identifier (2nd temp ID and 3rd temp ID, respectively). Each UE then sends the original message up using the newly derived temporary identifier. Upon receipt of a newer temporary identifier, an initial layer 2 context is established between the respective UE and the network for common channel operations. The network then responds to each UE having a unique temp ID as described above.

[0087] Fig. 10 shows a remedy mainly used by the network. Again, for two UEs, each sends a message up to the network using the same temporary ID (temp ID). The up message may be a message sent over the RACH or E-RACH channel. The message may be an RRC connection request message (as shown) or some other message. The network can detect the same temporary identifier in two messages up. In this case, the two UEs derive the same temp ID and each of them can expect to be addressed with signaling down to that temp ID. In this case, the network can determine if a conflict or collision has occurred. However, if one or both upstream messages contain a global UE identifier, the UE may be differentiated from each other. At this point, the initial Layer 2 context between the respective UE and the network is established for joint channel activities.

[0088] The network may send, via a control channel, a scheduling grant message to which a downlink resource has been allocated. The network may also send through the channel described in the scheduling grant message a message including the global UE identifier. For example, the network may send an RRC connection setup complete message addressed to the UE using the UE deriving the conflicting temporary identifier. In some solutions, the network explicitly appends the global UE identifier in a down message by including the global UE identifier as a parameter. Alternatively, the network may attach the UE global identifier via

EP 1 974 572 B1

V4350PL00 / LB use of the global UE identifier to encode the message downwards. For example, the attachment may include calculating a CRC (Cyclic Redundancy Check) value using a known network UE identifier. When decoding a message down, each UE may use its global UE identifier to determine if the global UE identifier has been attached as a parameter, or alternatively to decode the message to determine whether the previously transmitted global UE identifier has been used by the network to encode the message. In addition, the network can respond by assigning a replacement temp ID to the UE that has transmitted its global UE ID. After one of the UEs receives a surrogate temp ID, a unique layer 2 context is created for both UEs for shared channel operations. The first UE will receive and correctly decode an RRC connection setup message that is encoded with its UE. The second UE will attempt to decode the RRC connection setup message, but this will fail because the message is encoded with an unknown UE global identifier causing the second UE to skip the message and return to the scheduled channel down (SPCCH). The second UE will then receive a second downward message sent by the network for scheduling to be granted. The second UE will then correctly receive and decode the RRC connection setup message addressed to it. Both UEs may terminate the process by responding with an RRC connection setup complete message.

[0089] Although the invention has been described on the basis of specific solutions and figures, the skilled person is aware that the invention is not limited to these solutions and figures described. For example, many of the solutions described above relate to 3GPP systems and the developed UMTS nomenclature (E-UTRAN). In a broader sense, some solutions may include a transceiver pair using the CDMA ( Code Division Multiple Access - working in TDD mode with Time Division Duplex or FDD mode with Frequency Division Duplex. Alternatively, the transceiver can be a transceiver without code splitting, such as used in the TDMA system, FDMA system, OFDM system or the hybrids above (e.g. TMDA / FDMA, TDMA / CDMA, TDMA / OFDM and TDMA / OFDM / CDMA). The transceiver can operate on packets or on a signal stream.

[0090] The attached figures of the drawings are for illustration only and may not scale. Some proportions can be exaggerated, while others can be minimized. The figures are intended to illustrate various uses of the invention that a person skilled in the art can understand and properly implement.