Method to send RRC messages in a wireless communication system

[0001] The present invention relates generally to wireless communication technology, and in particular to an initial connection procedure between a user equipment and a network equipment in a wireless communication system. 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 a user equipment). User Equipment - UE), user terminal, mobile terminal, wireless terminal and mobile phone) and the radio access network. A radio access network may include one or more base stations (also referred to as node B, e.g. in 3GPP terminology) along with one or more radio network controllers (RNCs). The logical connection provides the context for a specific network to the user device's communication link, through which data can be sent without communication errors to network elements or user devices in the system that were not intended to participate in the communication.

[0003] In a 3GPP radio access network system, the logical connection between the user terminal and the radio access network is defined by the Radio Resource Control (RRC) connection states. The two main RRC connection states are defined as combined RRC and passive RRC. Specification of RRC protocol was disclosed in ETSiTS 125 331 on 3.1.0.

[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 core network 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 respective 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 a network initiated connection, an RRC connection request message may also be sent by the UE in response to receiving a paging message from the network (the network has previously sent a 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 connection, the UE needs to establish an RRC connection; (2) Paging reply: when transmitting the reply message to the paging message; (3)

Cell update: when the UE selects the appropriate cell during presence in the passive mode; (4) Updating the UTRAN Routing Area (URA): when the UE selects the corresponding URA during presence in the 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 multiple UEs 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 downlink common transport channels, which are (like common uplink channels) shared by multiple UEs and used for unscheduled data transmission.

[0009] The common transport channel by 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, there is a risk that one cell phone will send data using the same uplink transmission resource or the same uplink identifier as another user. In this case, the communication reliability of both transmissions may be compromised due to mutual logical or actual interference caused by uplink 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] A further description of collision, unscheduled access, and scheduled access can be found in US Patent Application 11 / 263,044, filed October 31, 2005, and entitled "FREOUENCY DOMAIN UNSCHEDULED TRANSMISSION IN A TDD WIRELESS COMMUNICATIONS SYSTEM", inventor Nicholas W. ANDERSON, which here as a reference source.

[0011] Common downlink transport channels are used to forward corresponding messages from the network to the user terminal are referred to as Forward Access Channel (FACH) channels.

[0012] System resources are usually reserved on the uplink and downlink for these 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 is insensitive 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 completed using common channel procedures. A significant part of the space for all radio resources should therefore be pre-assigned to common channels to carry out transmission for the purpose of 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] Furthermore, known wireless communication systems spend a considerable amount of time and exchange multiple signaling messages on unshared and common channels to establish the initial layer 2 context for the operation of common channels and this may contribute to 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.

BRIEF SUMMARY OF THE INVENTION [0017] The scope of the invention is defined by the appended independent claims.

[0018] 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, and by enabling the UE to connect with a channel set that will monitor for downlink messages from the network. This combination allows the system to use shared channels instead of shared ones

-4 channels at a very early stage of establishing the connection, helps minimize the amount of transmission on common channels, and also helps to avoid collisions.

[0019] Some embodiments of the present invention provide a method of initiating a wireless connection with a user device and further communication within shared physical resources in a wireless communication system between a user device and a network device, the method comprising: deriving a temporary identifier; deriving channel set; sending an initial message to a network device, the initial message comprising a temporary identifier; receiving a message on the downlink using a channel belonging to the derived channel set transmitting a temporary identifier and a description of the scheduled resource on the shared channel, the scheduled resource comprising a resource allocated to the user equipment by the network device; and exchanging data using a scheduled resource in response to a downlink message. [0020] Some embodiments of the present invention provide one or more of the following options in various combinations: the channel set includes multiple channels; deriving the channel set includes randomly selecting a channel set from a plurality of channel sets; deriving the channel set includes determining the channel set based on, for example, a global UE identifier, where the global UE identifier includes one of the following: Temporary Mobile Subscriber Identity (TMSI), International Mobile Subscriber Identity - IMSI) or international user device identifier ( International Mobile Equipment Identity IMEI); deriving the channel set includes specifying the channel set as a function of one or more physical resource properties, wherein the sending of the initial message includes sending the initial message using, for example, a physical resource, wherein the physical resource property includes one or more of the following: time parameter, frequency parameter, and / or code parameter; deriving the channel set includes determining the channel set based on one or more of the following: physical resource property, global UE identifier, and temporary identifier; the initial message further includes a global UE identifier; further comprising specifying a physical resource, wherein sending the initial message includes sending the initial message according to the specific physical resource; further includes channel set indication signaling; further including indirectly transmitting the channel set indication; sending the initiation message to the network device includes sending the schedule request message; sending the initial message to the network device includes sending the RRC connection request message; further comprising: a pause after sending the initial message and before receiving the downlink message; determination of another physical resource; resending the initial message using a different physical resource; and / or wherein the wireless communication system comprises an evolved UMTS terrestrial radio access network (E-UTRAN).

[0021] Some embodiments of the present invention provide a user device used to initiate a wireless connection and further communication within a shared physical resource in a wireless communication system between a user device and a network device, the user device comprising: memory, a memory-coupled processor, and program code executed on the processor, with the program code

- 5 should support: deriving a temporary identifier; deriving channel set; sending an initial message to a network device, the initial message comprising a temporary identifier; receiving a message on the downlink using a channel belonging to the derived channel set transmitting a temporary identifier and a description of the scheduled resource on the shared channel, the scheduled resource comprising a resource allocated to the user equipment by the network device; and exchanging data using a scheduled resource in response to a downlink message.

[0022] Some embodiments of the present invention provide one or more of the following options in various combinations: deriving a channel set includes randomly selecting a channel set from multiple channel sets; deriving the channel set includes determining the channel set as a function of one or more physical resource properties, e.g., time, frequency and code, wherein sending the initial message includes transmitting the initial message using the physical resource; sending the temporary identifier to a network device includes sending the temporary identifier as part of the first uplink message containing the temporary identifier and a scheduled resource request; deriving the channel set includes determining the channel set based on one or more of: a physical resource property, a global UE identifier, and a temporary identifier; the program code is also able to determine a physical resource, wherein sending the initial message includes sending the initial message according to the specific physical resource; and / or the program code is further able to signal the channel set indication, the program code being further able to indirectly send the channel set indication.

[0023] Some embodiments of the present invention provide a network device used for initiating a wireless connection and further communication within a shared physical resource in a wireless communication system between a user device and a network device, the network device comprising: memory, a memory-coupled processor, and program code executed on the processor, where the program code should support: receiving the initial message sent by the user equipment; channel set definition; allocating a scheduled resource to a user device, wherein the scheduled resource includes a resource on a shared channel; sending a downlink message using a channel belonging to the specified channel set, the downlink message providing a temporary identifier and a description of the scheduled resource; and exchanging data using a scheduled resource in response to a downlink message.

[0024] Some embodiments of the present invention provide: a channel set definition, wherein the channel set definition comprises extracting the channel indication from the initial message, the channel indication indicating the channel set; or determining the channel set, wherein the determining the channel set includes determining the channel set based on a physical resource transmitting the initial message.

[0025] Some embodiments of the present invention provide a computer program comprising a program code for initiating a wireless connection and further communication within shared physical resources in a wireless communication system between a user device and a network device, the computer program comprising a program code for: deriving a temporary identifier; deriving channel set; upload

- an initial message to the network device, the initial message comprising a temporary identifier; receiving a receive message on a downlink channel belonging to the derived set of downlink message channels conveying a temporary identifier and a description of the scheduled resource on the shared channel, wherein the scheduled resource includes a resource allocated to the user equipment by the network device; and exchanging data using a scheduled resource in response to a downlink message.

[0026] Other features and aspects of the invention are apparent from the following detailed description in connection with the accompanying drawings, which exemplify features in accordance with the embodiments of the invention. The summary 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 [0027] Figs. 1A and 1B show a standard sequence of messages to transition from an RRC passive state to an RRC connected state in a traditional 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). FIG. 3A and 3B depict an expanded UTRAN network (E-UTRAN) functioning together with a user equipment and a core 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. Figures 6A and 6B show in detail signaling sequences using the downlink scheduled, and Figs. 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 a downlink scheduled and Figures 9 and 10 show conflict resolution processes in accordance with the present invention. FIG. 11 and 12 depict conflict avoidance and resolution processes utilizing multiple planning award channels in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION [0028] In the following description reference is made to the accompanying drawings, which illustrate several embodiments of the present invention. It should be understood that other embodiments are possible, and mechanical, compositional, constructional, electrical, and performance-related changes can be made without departing from the theme and scope of the present disclosure. The following detailed description should not be considered to a limited extent, and the scope of the present invention is defined solely by the claims of the published patent.

[0029] 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. Every step

- 7 can be made using hardware, software, firmware or a combination of the above.

[0030] Although the following drawings show the invention with reference to the standard UMTS (Universal Mobile Telecommunications 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).

[0031] Figs. 1A and 1B show a standard message sequence for moving from an RRC passive state to an RRC connected state in a conventional UMTS system. In a standard UMTS system, an inactive RRC user device may initiate an RRC connection using the procedure 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. FIG. 1A shows communication through 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 an S-RNTI (Serving Radio Network Controller (RNC) RNTI) assignment network that is used by the UE to identify itself to SRNC (Serving RNC). 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 broadcast channel 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 for

- 8 cell-based UE identifications. In a traditional network, the decision to use C-RNTI is made by the CRNC (Controlling Radio Network Controller).

[0034] After the network device successfully completes the admission control process as well as the allocation process, the network responds to an RRC connection request message with an RRC connection configuration message including a global UE identifier, a newly assigned S-RNTI value, optionally a CRNTI value, and a user configuration a radio device.

[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 a fast downlink shared channel (HS-DSCH) is used for downlink data transmission, the network may assign an H-RNTI value to the UE as part of the message User configuration of the RRC radio device to the UE. The H-RNTI value is used to identify the UE on a fast downlink shared channel. The RRC radio device user configuration message includes the assigned S-RNTI, assigned H-RNTI, and user configuration of the shared channel radio device. The UE terminates the process by replying to the RRC radio device user 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 layer (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 on both node B and RNC to provide physical connections between these units (or interface), 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 (TM) mode, the sender of the message does not include the message sequence identifier, unlike confirmation (AM) and unacknowledged (UM) modes, which include the message sequence identifier, which can be used to identify / rearrange sequence packets and to identify 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 a common uplink 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 channel

-9CCCH. The RLC layer, in turn, sends the message to the RRC layer, which sends the message to the RRM layer for the purposes of admission control, assignment of S-RNTI value and possibly assignment of CRNTI value.

[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 downlink 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 downlink 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 identifier 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 identifiers match, the message is decoded and the UE records the S-RNTI assignment and probably the C-RNTI value. 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. Data sent by DCCH through the common transport channel resources accompanies the header field in which the C-RNTI is included to distinguish the UE based on a cell from many 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. Next, 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. The MAC layer 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.

[0042] The network uses a different value to identify the UE when the UE communicates over a fast downlink 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 HSDSCH. 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 RRN RNC layer copies the channel path described above for signaling the RRC connection complete message. After the H-RNTI is allocated, the UE may then use the fast (hs) shared downlink transport channel for downlink communication. Resource allocations for this channel are granted by a manager located on the MAC-hs entity on node B. The MAC-hs entity may address the UE in the cell when allocating fast downlink shared channels using H-RNTI as the UE identifier. 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.

[0043] At this point, the UE and network have established and created a layer 2 shared channel context, and the network has allocated a shared channel identifier to the UE. When creating this layer 2 context, the network assigns an identifier and exchanges three messages up and two on the downlink.

[0044] In accordance with 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 is therefore not sensitive 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 resource allocation of the shared channel, 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.

[0045] 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.

[0046] Fig. 2 shows a plurality of UEs and a UTRAN network device. The UTRAN network device provides a UE link to the core 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.

[0047] 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 core network (CN). The E-UTRAN network includes an LTE (LTE GW) gateway coupled to one or more developed B nodes (E-node B) that perform the functions of both B and RNC nodes in Fig. 2. The LTE gate provides an interface between the core 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.

[0048] Fig. 3B illustrates another architecture for the E-UTRAN network. The LTE gateway provides an interface between the core 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. The solutions of Figs. 3A and 3B provide a MAC layer and an RLC layer that combines 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 to reduce signal delays.

[0049] Fig. 4 shows components of a user equipment according to the present invention. The user equipment includes a memory for storing the temporary identifier derived by the UE, a processor, a program code enabling the UE to obtain the user identifier and storing the identifier in memory, and 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 circuitry 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 may be a transceiver pair using the CDMA (Coda Division Multiple Access) technique and operating in TDD (Time Division Duplex) or FDD (Frequency Division Duplex) mode.

[0050] 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 be different for different implementations of the present invention. The derivation of the temporary identifier provides a direct layer 2 context for layer 2 communication over shared transport channels that are scheduled by the E-MAC entity in the E-node B. The derivation of the temporary identifier preferably takes place in a manner that minimizes to acceptable

- the level of probability that two UEs 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 collision detection and removal procedures may be used.

[0051] The temporary identifier output by the UE is a function of time or radio frame number. The function can change in accordance with a predetermined pattern or signaled user equipment, for example using a spreading channel (BCH). Alternatively, the change pattern may contain a random element in its source. The use of a time-changing component or time parameter (such as system clock, super-frame number, subframe number, time slot number) 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.

[0052] After deriving the temporary identifier, the UE transmits this derived identifier to the E-UTRAN network in the first uplink message. 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.

[0053] 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.

[0054] 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 downlink message to the UE containing the temporary identifier derived by the UE as the destination address, as well as a description of the assigned physical resource. The UE and network then send user data or signaling data (data) through the allocated physical resource.

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

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

The signaling data is contained in the same packet as the first downlink message including the allocation, the UE may reprocess the received packet to obtain a second downlink message.

[0057] 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.

[0058] In accordance with some embodiments of the present invention, a minimum resource set may be assigned for unscheduled messages, such as the first uplink message in Figs. 5A and 5B. Uplink messages 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 downlink channels (e.g. FACH) can be removed from the configured channels because each UE initiates contact with the network using the addressable temp layer ID 2. The rest of the resources can be dynamically allocated between the control channel message (e.g. first downlink message) and user data or signaling data (i.e. the second message on the downlink or the uplink). This allocation of resources provides a higher bandwidth system due to better resource efficiency.

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

[0060] 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 uplink message to the network. In addition to temp ID, the first uplink message contains the establishment reason parameter and two optional parameters: buffer occupancy and global UE ID. The reason for establishment and the global UE ID may be the same or similar to the corresponding parameters described above with reference to Fig. 1 A.

[0061] Buffer occupation may be used as an indication of the amount of current data for transmission in the UE transmission buffer and may 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 one 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.

[0062] The UE may send an RRC connection request message using transparent mode (TM). After the RRC connection request message is received by the network equipment, the network performs an admission check (described above with reference to Fig. 1 A) and allocates a physical resource: shared channel in

- 14 uplink (UL-SCH) or shared channel downlink (DLSCH) as indicated by the establishment reason parameter. Alternatively, the network can also allocate S-RNTI and a replacement temp ID.

[0063J The network sends the first downlink message including the downlink scheduling planning indication including the temp ID for addressing a particular UE and a description of the allocated physical resource. The first downlink 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. This 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 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.

[0064] Upon receiving the 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 downlink 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.

[0065] The user equipment identified by the temp ID receives and decodes the message sent on the allocated physical resource described in the downlink scheduling grant message. This second downlink message to the UE may include an RRC connection setup message transmitted 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.

[0066] In addition, a global UE identifier may be included in this first downlink message if it is received by the network from the RRC connection request message and if a collision of overlapping temporary identifiers (temp ID) 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 downlink message (e.g., CRC).

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

[0068] The UE then responds to receiving and processing the RRC connection setup message by preparing and transmitting the RRC connection setup complete message using the confirmation mode (AM). If a replacement temp ID was provided by the network, the UE uses this

- 15 new value as your temporary identifier. The RRC connection setup complete message may also include UE radio access capability parameters indicating different UE capabilities. [0069] According to the present invention, the information contained in the standard user configuration message of the RRC radio device (Fig. 1 A) they can be sent over the BCH and not sent separately to each UE, since information describing the shared channel can be used by many UEs in the cell.

[0070] 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).

[0071] 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 RRC joint control channel (CCCH) request message mapped on the RACH using transparent mode (TM). 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.

[0072] 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. After the acceptance check and the optional replacement of the temporary identifier and the optional assignment of S-RNTI values, E-RRM returns the assigned values ​​to the E-RRC layer, which creates an RRC connection setup message for transmission in an unacknowledged mode (UM). The ERLC sends an 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.

[0073] 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 allocated physical resource over a downlink shared 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.

[0074] 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 .

[0075] Next, the UE responds with an RRC connection setup complete message that is sent using confirmation 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.

[0076] Next, the network receives an RRC connection setup complete message via 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. Figures 7A and 7B show in detail signaling sequences using a scheduled receive link and an unplanned and scheduled uplink in accordance with 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. Figures 7A and 7B deviate from the previous solution by sending subsequent uplink messages through shared resources.

[0077] 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 transmitting the scheduling request message via the RACH channel or via the expanded RACH (E-RACH) channel . A short planning request message requests the network from the network to allocate an uplink 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 UE's uplink shared channel (ULSCH) and describes the uplink allocation in the Shared Physical Control Channel (SPCCH) scheduling grant message from the EMAC layer to layer 1, and then via the radio interface (Uu) to a layer 1 UE that sends a scheduling grant message over 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.

[0078] By using a shared, scheduled uplink and / or downlink scheme in accordance with some embodiments of the present invention, one or more advantages can 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, logical collisions (occurring due to shared temporary identifiers derived by two UEs in overlapping time units) can be overcome by collision removal procedures in the EU 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 various momentary loads occurring at

- 17 times for 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.

[0079] 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 uplink 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 uplink message. 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 uplink shared channel (ULSCH) and sends the planning grant over 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 uplink scheduling grant message on the uplink 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 the acknowledgment (AM) mode, while other solutions may use the unacknowledged (UM) mode when sending one or both of the RRC connection request message and the RRC connection configuration message. FIG. 9 and 10 illustrate 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, 7A-B 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 collision detection and removal procedures can be implemented.

[0080] Fig. 9 shows a remedy mainly used by the UE. For two UEs, each sends a uplink message to the network using the same temporary identifier (1st temp ID). The uplink 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 uplink messages. Network

- 18 may choose not to process and may allow any EU Member State to exceed its waiting time. After the downlink unexpected 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 uplink message 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.

[0081] Fig. 10 shows a remedy mainly used by the network. Again, for two UEs, each sends a uplink message to the network using the same temporary ID (temp ID). The uplink 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 uplink messages. In this case, the two UEs derive the same temp ID and each of them can expect to address downlink signaling covering this temp ID. In this case, the network can determine if a conflict or collision has occurred. However, if one or both uplink 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.

[0082] 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 derived temporary collision identifier. In some solutions, the network explicitly attaches the UE global identifier in a downlink message by including the UE global identifier as a parameter. Alternatively, the network may attach the UE global identifier by using the UE global identifier to encode the message on the downlink. For example, the attachment may include calculating a CRC (Cyclic Redundancy Check) value using a known network UE identifier. When decoding a downlink message, each UE may use its global UE identifier to determine if the global UE identifier has been attached as a parameter, or optionally to decode the message to determine whether a 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 it 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 downlink channel (SPCCH). The second UE will then receive a second downlink scheduling grant message sent over the network. The second UE will then correctly receive and decode the RRC connection setup message addressed to it.

Both UEs can terminate the process by responding with an RRC connection setup complete message.

[0083] Figs. 11 and 12 show conflict avoidance and resolution processes using multiple scheduling grant channels in accordance with the present invention. Some systems may configure multiple channels (e.g., multiple SPCCH channels) to send scheduling grant messages from the network to the UE. These channels may be pre-configured, they may be standard defined, or they may be sent to the UE (e.g. sent via broadcast channel or using another method of signaling system control).

[0084] The UE may derive or select a subset (i.e., a single channel or multiple channels) from a plurality of configured channels for subsequent monitoring of scheduled scheduling grant messages. The derived channel set that the UE will monitor may be referred to as a channel set. By using the uplink message, the UE may send the channel set explicitly using the parameter or implicitly by using a specific physical resource. By sending a channel set or pointing to a channel set, the network can distinguish UEs that accidentally derived the same temporary identifier, but successfully derived different channel sets. Fig. 11 shows an example of a UE explicitly transmitting a channel set to the network by sending an initial message including an indication of the channel set. FIG. 12 shows an example of a UE implicitly transmitting a channel set by using a specific top link physical resource to send an initial message to the network.

[0085] In Fig. 11, before establishing a connection with a network device, the first UE outputs a temporary identifier (temp ID) as described above. The first UE also outputs a channel set. That is, the UE selects a planning grant channel (SPCCH) to monitor for future scheduling grant messages. Alternatively, the UE may select more than one configured scheduling grant channel (SPCCH), which is referred to as the channel set.

[0086] To derive a channel set comprising a single channel or a plurality of channels that the UE monitors for scheduling grant messages, the UE may select a channel set based on one or a combination of the following parameters: (1) a global UE identifier such as its TMSI, IMSI or IMEI ; (2) a temporary identifier derived and (3) one or more physical resource properties that will be used by the UE to send the initial message. The physical resource properties include a time parameter (such as system clock, super-frame number, radio frame number, subframe number, time slot number), frequency parameter (such as frequency band, channel number or subcarrier number) and code (such as midamble code , channel spreading code, time-frequency code, or orthogonal code).

[0087] The example shows a first UE deriving a temporary identifier (temp ID) in combination with a channel set. The channel set may be a single SPCCH channel number or a set of multiple SPCCH channel numbers. Channel set can be represented by a channel reference (e.g., channel indication # 1). For example, the channel set may be forwarded by transmitting a channel indication value that represents a table pointer known to both the UE and the network. Entries in the table may represent the number of a single channel or may represent multiple channels from a set of possible channels.

[0088] Then, the first UE sends an initial message containing both the selected temporary identifier and the channel indication for communication with the network, the network should use one or more channels to send the scheduling grant messages. For example, the initial message may be a scheduling request for scheduled uplink radio resources or an RRC connection request message sent as the first message during a connection setup process on unplanned uplink radio resources. In some solutions, the UE may also send a global UE identifier (such as TMSI, IMSI or IMEI) for use in collision detection and resolution as described above with reference to Fig. 10. After receiving the initial message, the network may associate a temporary identifier - channel set with a specific UE (e.g., the first UE).

[0089] The example further shows a second UE initiating connections simultaneously or soon after. In a similar manner, the UE derives a temporary identifier and a channel set represented by a channel indication (e.g., channel indication # 2). To illustrate, the example shows that the second UE derived the same temporary identifier (temp ID # 1) as the first UE derived. However, the second UE accidentally chose a different set of channels. The second UE then sends the temporary identifier and channel indication to the network in the initial message. After receiving the initial message, the network may pair the received temporary identifier and channel set with the second UE.

[0090] At this point, both UEs are associated with the same temporary identifier, however, due to their selection of different and non-overlapping SPCCH channel sets, as indicated in their channel indication parameters, it is possible to avoid unintentional cross communication. The first and second UEs will monitor different SPCCH channels and therefore the common derived temporary identifier can be used by the network to address both UEs. The network will address both UEs using the same temporary identifier, but will send a scheduling message to the first UE on one of the channels indicated by channel indication # 1 and will send a different scheduling message to the second UE on one of the channels indicated by channel indication # 2. Therefore, no UE will process a scheduling grant message addressed to another UE.

[0091] As a result, the system has created a unique shared channel communication context for each UE due to two UEs choosing different sets of SPCCH channels. Submitting a channel indication may not completely exclude the risk of conflict because two UEs can still output the same temporary identifier and the same set of channels. In this case, the collision resolution procedures described above with reference to Figures 9 and 10 may be used in the context of the present invention.

[0092] As further shown in Fig. 11, the network may exchange data with the first UE via a scheduled shared channel using the following steps: (1) obtaining a temporary identifier (temp ID # 1) and channel indication (channel indication # 1); (2) allocation of uplink and downlink shared channel resources; (3) determining the scheduling grant channel (channel # 1) based on the received channel indication; (4) sending a planning grant message addressed to temp ID # 1 on channel # 1 and containing a description of the allocated resources of the uplink and downlink shared channel; and (5) exchanging data by sending or receiving data using the allocated shared channel resources. Similarly, the network can simultaneously or

Essentially simultaneously communicating with the second UE via the scheduled shared channel using the following steps: (1) obtaining a temporary identifier (temp ID # 1) and channel indication (channel indication # 2); (2) allocation of uplink and downlink shared channel resources; (3) determining the scheduling grant channel (channel # 2) based on the received channel indication; (4) sending a planning grant message addressed to temp ID # 1 on channel # 2 and containing a description of the allocated resources of the uplink and downlink shared channel; and (5) exchanging data by sending or receiving data using the allocated shared channel resources.

[0093] In a similar manner to that described above with reference to Figs. 6A, 7A and 8A, the network may further reassign a replacement temporary identifier to one or both UEs, so that each UE is assigned a unique temporary identifier, and thus potentially eliminate the need for restrictions on the grant channel when sending scheduling grant messages to each UE. Also, in some solutions, the network may allow the UE to use different sets of SPCCH channels. For example, the network could reassign a unique replacement temporary identifier to the UE and enable the network to forward data on the uplink and downlink shared resource scheduling allocation by any SPCCH downlink.

[0094] In Fig. 12, the UE transmits the channel set implicitly. The first UE derives the temporary identifier and derives the physical resource (physical resource # 1) before establishing connection with the network device. A physical resource can be characterized by time, frequency and code parameters. In the presented solution, the UE may send the set of channels explicitly by the mere use of the physical resource. The network may use one or more physical resource properties to indicate the channel set to be used by the UE.

[0095] In some embodiments, the UE may determine the channel set and then determine which physical resource to use to send the initial message based on the specific channel set. In other solutions, the UE may specify a physical resource to send the initial message, and then determine the channel set based on the specific physical resource. The network uses the properties of the physical resource used by the UE to determine the channel set. For example, the time (e.g., time slot) of the initial message may indicate to the network that a specific downlink scheduling channel or channel set will be monitored by the UE. After receiving the temporary identifier, the network may associate the temporary identifier with a specific one or more scheduling grant channels (SPCCHs) based on one or more physical resource properties (physical resource # 1). In some solutions, the association of a temporary identifier or physical resource with an SPCCH channel number or channel set may change as a function of time. Alternatively, the binding may be based on the global UE identifier received in the RRC connection request message. Each UE creates the same association between the transmitted temporary identifier and the channel set as it is created by the network. Such a link can be implemented similarly both in the EU and in the network. The network further associates a temporary identifier channel set pair with a specific UE (in this case, the first UE).

[0096] At the same time or some time later, the second UE starts the connection establishment procedure. The second UE outputs the temporary identifier and sends the initial message to the network. After

-22 receiving the initial message, the network similarly defines the channel set and associates the temporary identifier with one tub with multiple specific SPCCH channel numbers based on the physical resource property (physical resource # 2).

[0097] In some embodiments, the association between the temporary identifier and the channel set is based on a periodic function of time. As a result, a limited set of occurrences of access periods in the time interval occurring between the transmission of two initial messages is configured in such a way that the association between the temporary identifier and the channel set does not repeat. As such, transmission of temp ID # 1 by the second UE at a later time causes that temp ID # 1 is associated with a different SPCCH channel number than that which is associated with the first UE. In the example shown, temp ID # 1 is associated with channel # 1 SPCCH for the first UE, where temp ID # 1 is associated with channel # 2 SPCCH for the second UE. As a result, the network can send scheduling grant messages to the UE using a pre-allocated scheduling channel known to both the UE and the network and can exchange data uniquely with the first and second UE through one or more scheduled shared channels as indicated in the plan grant messages .

[0098] At this point, both UEs are associated with the same temporary identifier, however, due to their association with different SPCCH channel numbers, it is possible to avoid unintentional cross communication as outlined above. As a result, the system has created a unique shared channel communication context for each UE, which is due to the fact that connection establishments were initiated using different physical resources and hence UEs can be associated with different SPCCHs. In some solutions, this method completely eliminates the possibility of connection in relation to attempts of non-simultaneous access in a given time interval. If multiple UEs derive a common temporary identifier but each sends an initial message using different physical resources, collisions can be avoided if the UEs are reallocated temporary replacement identifiers. On the other hand, if many UEs derive a common temporary identifier and also send an initial message using the same physical resources, conflicts may arise that can be resolved using conflict resolution procedures such as those described above with reference to Fig. 9, and 10.

[0099] The substantially collision-free access length may be a function of the available SPCCH channel number and the length and nature of the pattern describing the association between the temporary identifier and the SPCCH channel number. It could therefore be beneficial for the network to assign unique replacement temporary identifiers to each UE accessing the system before the binding pattern repeats over time. As a result, by designing a binding pattern whose length is proportional to the maximum expected time required to assign a replacement temporary identifier, the schema efficiency can be optimized.

[0100] The present invention has been described on the basis of specific solutions and drawings, it is also clear to the skilled person that the invention is not limited to these solutions and drawings 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 ( Coda Division Multiple Access - working in TDD (Time Division Duplex) or FDD (Frequency Division Duplex) mode. Alternatively, the transceiver can be a transceiver-23 receiver without code division, 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.

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