WO2014009894A2 - Method, apparatus and computer program for temporary block flow establishment - Google Patents

Abstract

In uplink and downlink temporary block flow (TBF) establishment in a mobile station of a mobile network, the mobile station receives (1701), in packet transfer mode, an order from the network to activate monitoring, in packet idle mode, of a packet data channel (PDCH) not carrying (packet) common control channels. The mobile station sets a timer value (1703) during which to operate on the PDCH while in packet idle mode. The mobile station selects a channel as the PDCH resource (1705).

Description

METHOD, APPARATUS AND COMPUTER PROGRAM

FOR TEMPORARY BLOCK FLOW ESTABLISHMENT

Cross Reference to Related Application

This application claims the benefit under 35 U.S.C. § 119 and 37 CFR § 1.55 to UK patent application no. 1212422.8, filed on July 12, 2012, the entire content of which is incorporated herein by reference.

Technical Field

The present invention relates generally to the field of wireless mobile communications, and, in particular examples, to providing uplink and downlink temporary block flow establishment during a period when a mobile station is operating outside a common control channel resource.

Background

The following abbreviations appear in the present description and may also be used throughout the claims:

AGCH Access Grant Channel

BCCH Broadcast Control Channel

BSS Base Station System

CCCH Common Control Channels

CS Circuit switched

DL Downlink

DLDC Downlink Dual Carrier

DRX Discontinuous Reception

DTR Data terminal ready

EDGE Enhanced Data rates for Global Evolution

ePRACH Enhanced Packet Random Access Channel

FAI Future Activity Indicator

FBI Final Block Indicator GERAN GSM Edge Radio Access Network

GMM GPRS mobility management

GPRS General Packet Radio Service

GSM Global System for Mobile communications

IM Instant messaging

IMSI International mobile subscriber identity

IPDCH Idle mode packet data channel

MS Mobile station

MSC Mobile switching station

MT Mobile terminal

PACCH Packet Associated Control Channel

PDCH Packet Data Channel

PDTC Packet Data Traffic Channel

PDU Protocol data unit

PS Packet switched

RACH Random Access Channel

RLC/MAC Radio Link Control/Medium Access Channel

SGSN Serving GPRS Support Node

TBF Temporary Block Flow

TLLI Temporary Link Level Identity

TMSI Temporary mobile subscriber identify

TN Timeslot number

UE User equipment

UL Uplink

USF Uplink state flag

Instant messaging applications exchange a small amount of data between the client and server applications or between peer applications. The traffic generated by instant messaging applications is characterised by a low amount of data transferred frequently. Studies of the GSM Edge Radio Access Network (GERAN) under load indicate a problem with overload on the common control channel (CCCH), and on the paging channel (PCH) in particular.

The cell updating procedure is controlled by the READY timer which is used in the mobile station (MS) and the network per each packet-temporary mobile subscriber identity (P-TMSI) (MS identity in the server group support node (SGSN)). The packet paging procedure is initiated by the network to reach a mobile station for which the READY timer expired i.e. its location is not known at cell level by the network and the MS and SGSN are in the STANDBY state 100 as shown in Fig. 1. If the READY timer is running (i.e. the MS and the SGSN are in the READY state 101 in which the location of the mobile station is known at cell level), the network can send an assignment message immediately to the mobile station in the cell. Referring to Fig. 2, if the base station system (BSS) released the radio resources 104 and the mobile station is in the idle mode 103, CCCH signalling cannot be avoided because a temporary block flow (TBF) needs to be established from the MS in packet idle mode.

Based on the characteristics of instant messaging traffic, it can be assumed that the network issues paging for mobile stations which recently transitioned from packet transfer mode to packet idle mode (i.e. the location of the mobile station is known at cell level by the network).

Network studies also elaborate on the use of extended uplink TBF and delayed release of downlink TBF. These two features allow the network to keep a TBF active during periods of inactivity and thus avoid the TBF re-establishment procedures. Study results show that longer delays in releasing the uplink and downlink TBF reduces the load on CCCH, however, and the TBF blocking significantly increases in the network in proportion to the extension of TBF release delay. The blocking is caused by inactive TBFs occupying the network resources (the packet data channels (PDCHs)). The mobile station in packet idle mode and in discontinuous reception (DRX) mode listens only to blocks on CCCH belonging to its paging group. This behaviour can imply noticeable delays in re-establishment of TBFs while saving MS battery power. This problem was already addressed by non-DRX mode, at the expense of battery power. The non-DRX mode is simply a period of time during which the mobile station listens to all CCCH blocks before it enters DRX when it then monitors only CCCH blocks belonging to its paging group and monitors required broadcast control channel (BCCH) data. The non-DRX mode, while offering a solution to the delays induced on TBF (re)establishment, does not provide a solution to the CCCH load problem because the communication between the network and the mobile stations has to be initiated on CCCH during the non-DRX period anyway.

The very nature of packet-based communications exacerbates the highlighted problems:

• PDCH load and TBF blocking, with extended uplink (UL) TBF mode or delayed TBF release;

• CCCH load for paging, assigning resources, requesting resources;

• delays with TBF establishment when in DRX;

• MS Battery consumption in non-DRX mode.

This is illustrated in Fig. 3, which depicts the impact on CCCH 301 due to the nature of packet switched (PS) traffic (i.e. packets), and Fig. 4 shows a remedy 401 to this issue (Delayed TBF release, extended UL TBF mode) while introducing another issue 403.

Mitigating one problem often reinforces another one given that packet services can be of different nature. It is a complex matter to optimise these aspects to suit a particular service; optimisations for a given service would typically yield degradation for others (e.g. extensive use of extended UL TBF mode for services with frequent bursty packet transmissions can increase TBF blocking). The studies made with mobile instant messaging (IM) show that this particular service can have detrimental impact on the system while taking into account the mechanisms at hand. It is therefore an object of this invention to address the problems triggered by IM while offering better system operation overall. Summary

According to a first aspect of the present invention, there is provided a method for uplink and downlink temporary block flow (TBF) establishment in a mobile station of a mobile network that comprises receiving, in packet transfer mode, an order from the network to activate monitoring of a packet data channel (PDCH) in packet idle mode, setting a timer value during which to operate on the PDCH while in packet idle mode, and selecting a channel as the PDCH resource.

The method may comprise monitoring, in packet idle mode, downlink blocks on the PDCH for downlink resource assignment. The method may comprise enabling, in packet idle mode, the use of uplink blocks on the PDCH for requesting uplink resources. The PDCH may be an idle mode packet data channel (IPDCH) not carrying (packet) common control channels. The timer value may be a parameter broadcast on the broadcast control channel (BCCH), a non-discontinuous reception (DRX) time value included in existing DRX parameter signalling, received as part of an assignment/reconfiguration message, received in a radio link control/medium access control (RLC/MAC) during downlink TBF, or signalled in a packet uplink acknowledgement/non-acknowledgement (ACK/NACK) signal during uplink TBF. The selected channel for the PDCH resource may be a default channel from allocated one or more PDCHs, a received channel designation from allocated one or more PDCHs, or any channel on the assigned carrier(s). The method may further comprise establishing a downlink temporary block flow (TBF) with a signalling exchange on the PDCH resource wherein the signalling exchange comprises receiving a packet downlink assignment including a temporary link level identity (TLLI). The method may also comprise receiving an order from the network includes receiving a temporary unique identifier valid only on the PDCH resource in uplink and uniquely identifying the mobile station when sending on uplink wherein the temporary unique identifier is 5-bits long. The method may also comprise establishing an uplink temporary block flow (TBF) with a signalling exchange on the PDCH resource wherein the signalling exchange comprises sending a fast packet channel request message to the network, receiving a packet uplink assignment including a TLLI, and optionally sending a packet control acknowledgement signal to the network. The fast packet channel request message may include the temporary unique identifier. The order from the network may include a temporary identity valid on IPDCH wherein the temporary identity identifies a TLLI in the network. According to a second aspect of the present invention, there is provided apparatus comprising a processing system constructed and arranged to cause the apparatus to, upon receipt, in packet transfer mode, of an order from the network to activate monitoring of a packet data channel (PDCH) not carrying (packet) common control channels in packet idle mode: set a timer value during which to operate on the PDCH while in packet idle mode, and selecting a channel as the PDCH resource.

The apparatus may monitor, in packet idle mode, downlink blocks on the PDCH for downlink resource assignment. The apparatus may enable, in packet idle mode, the use of uplink blocks on the PDCH for requesting uplink resources. The PDCH may be an idle mode packet data channel (IPDCH). The timer value may be a parameter broadcast on the broadcast control channel (BCCH), a non-discontinuous reception (DRX) time value included in existing DRX parameter signalling, received as part of an assignment/reconfiguration message, received in a radio link control/medium access control (RLC/MAC) during downlink TBF, or signalled in a packet uplink acknowledgement/non-acknowledgement (ACK/NACK) signal during uplink TBF. The selected channel for the PDCH resource may be a default channel from allocated one or more PDCHs, a received channel designation from allocated one or more PDCHs, or any channel on the assigned carrier(s). The apparatus may also establish a downlink temporary block flow (TBF) with a signalling exchange on the PDCH resource wherein the signalling exchange comprises receiving a packet downlink assignment including a temporary link level identity (TLLI). The apparatus may also determine that receiving an order from the network includes receiving a temporary unique identifier valid only on the PDCH resource in uplink and uniquely identifying the mobile station when sending on uplink wherein the temporary unique identifier is 5-bits long. The apparatus may establish an uplink temporary block flow (TBF) with a signalling exchange on the PDCH resource wherein the signalling exchange comprises sending a fast packet channel request message to the network, receiving a packet uplink assignment including a TLLI, and optionally sending a packet control acknowledgement signal to the network. The fast packet channel request message may include the temporary unique identifier. The order from the network may include a temporary identity valid on IPDCH wherein the temporary identity identifies a TLLI in the network.

The processing system may comprise at least a processor, a memory associated with said processor, and computer coded instructions contained in the memory, said instructions when executed in the processor causing the apparatus to operate as described above.

According to a third aspect of the present invention, there is provided a computer program comprising a set of instructions which, when executed on a processor of a user equipment causes the user equipment to perform: receiving, in packet transfer mode, an order from the network to activate monitoring of a packet data channel (PDCH) not carrying (packet) common control channels in packet idle mode; setting a timer value during which to operate on the PDCH while in packet idle mode; and selecting a channel as the PDCH resource.

There may also be provided apparatus for uplink and downlink temporary block flow (TBF) establishment in a mobile station of a mobile network, the apparatus comprising: means for receiving, in packet transfer mode, an order from the network to activate monitoring, in packet idle mode, of a packet data channel (PDCH) not carrying (packet) common control channels; means for setting a timer value during which to operate on the PDCH while in packet idle mode; and means for selecting a channel as the PDCH resource. The apparatus may comprise means for monitoring, in packet idle mode, downlink blocks on the PDCH for downlink resource assignment. The apparatus may comprise means for enabling, in packet idle mode, the use of uplink blocks on the PDCH for requesting uplink resources. The PDCH may be an idle mode packet data channel (IPDCH). The timer value may be a parameter broadcast on the broadcast control channel (BCCH), a non-discontinuous reception (DRX) time value included in existing DRX parameter signalling, received as part of an assignment/reconfiguration message, received in a radio link control/medium access control (RLC/MAC) during downlink TBF, or signalled in a packet uplink acknowledgement/non-acknowledgement (ACK/NACK) signal during uplink TBF. The selected channel for the PDCH resource may be a default channel from allocated one or more PDCHs, a received channel designation from allocated one or more PDCHs, or any channel on the assigned carrier(s). The apparatus may also comprise means for establishing a downlink temporary block flow (TBF) with a signalling exchange on the PDCH resource wherein the signalling exchange comprises receiving a packet downlink assignment including a temporary link level identity (TLLI). The apparatus may comprise means for establishing an uplink temporary block flow (TBF) with a signalling exchange on the PDCH resource wherein the signalling exchange comprises sending a fast packet channel request message to the network, receiving a packet uplink assignment including a TLLI, and optionally sending a packet control acknowledgement signal to the network. The fast packet channel request message may include the temporary unique identifier. The order from the network may include a temporary identity valid on IPDCH wherein the temporary identity identifies a TLLI in the network.

Further features and advantages of the invention will become apparent from the following description of preferred embodiments of the invention, given by way of example only, which is made with reference to the accompanying drawings. Brief Description of the Drawings

Fig. 1 shows a state diagram for a mobile station and a serving group support node; Fig. 2 shows a state diagram for a mobile station;

Fig. 3 shows a signalling diagram between a mobile station and a base station;

Fig. 4 shows a signalling diagram between a mobile station and a base station indicating attempts to solve a temporary block flow problem;

Fig. 5 shows a schematic diagram of basic components of a wireless network;

Fig. 6 shows a block diagram of the elements of a mobile terminal in a wireless network;

Fig. 7 shows a signalling diagram between a mobile station and base station showing a new approach to packet idle mode; Fig. 8 shows a signalling diagram between a mobile station and base station showing a transition to packet idle mode;

Fig. 9 shows a signalling diagram between a mobile station and base station showing an uplink TBF release sequence;

Fig. 10 shows a signalling diagram between a mobile station and base station showing an uplink TBF release sequence and retransmission of a packet uplink message; Fig. 11 shows a signalling diagram between a mobile station and base station showing a downlink TBF release sequence; Fig. 12 shows a signalling diagram between a mobile station and base station showing a downlink TBF release and retransmission of a radio link control message; Fig. 13 shows a signalling diagram between a mobile station and base station showing a downlink TBF release and a signal failure;

Fig. 14 shows a signalling diagram between a mobile station and base station showing a downlink TBF release and a signal failure;

Fig. 15 shows a signalling diagram between a mobile station and base station showing downlink TBF assignment;

Fig. 16 shows a signalling diagram between a mobile station and base station showing uplink TBF assignment;

Fig. 17 shows a flow diagram of an example of a method according to an embodiment of the present invention; Fig. 18 shows a source block diagram for the timer and IPDCH parameters of the several embodiments; and

Fig. 19 shows a flow diagram of another example of a method according to an embodiment of the present invention.

Detailed Description

The present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some but not all embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like numbers refer to like elements throughout.

As used in this specification, the term "circuitry" refers to all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and (b) to combinations of circuits and software (and/or firmware), such as (as applicable): (i) to a combination of processor(s) or (ii) to portions ofprocessor(s)/software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) to circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present.

This definition of "circuitry" applies to all uses of this term in this specification, including in any claims. As a further example, as used in this specification, the term "circuitry" would also cover an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and/or firmware. The term "circuitry" would also cover, for example and if applicable to the particular claim element, a baseband integrated circuit or application specific integrated circuit for a mobile phone or a similar integrated circuit in server, a cellular network device, or other network device.

Although the method, apparatus and computer program product of example embodiments of the present invention may be implemented in a variety of different systems, one example of such a system is shown in Fig. 5, which includes a mobile terminal 8 that is capable of communication with a network 6 (e.g. a core network) via, for example, a radio network controller (R C) 2. While the network may be configured in accordance with Global System for Mobile communications (GSM) / Enhanced Data rates for Global Evolution (EDGE) Radio Access Network (GERAN), the network may employ other mobile access mechanisms, including for example a Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (W-CDMA), CDMA2000, and/or the like.

The network 6 may include a collection of various different nodes, devices or functions that may be in communication with each other via corresponding wired and/or wireless interfaces. For example, the network may include one or more base stations, such as one or more Base Transceiver Stations (BTSs) and Base Station Controllers (BSCs), Node Bs, evolved Node Bs (eNBs), access points, relay nodes or the like, each of which may serve a coverage area divided into one or more cells. For example, the network may include one or more cells, including, for example, the BSC 2, each of which may serve a respective coverage area. The serving cell could be, for example, part of one or more cellular or mobile networks or public land mobile networks (PLMNs). In turn, other devices such as processing devices (e.g. personal computers, server computers or the like) may be coupled to the mobile terminal and/or the second communication device via the network.

The mobile terminals 8 may be in communication with each other or other devices via the network 6. In some cases, each of the mobile terminals may include an antenna or antennas for transmitting signals to and for receiving signals from a base station. In some example embodiments, the mobile terminal 8, also known as a client device, may be a mobile communication device such as, for example, a mobile telephone, portable digital assistant (PDA), pager, laptop computer, tablet computer, or any of numerous other hand held or portable communication devices, computation devices, content generation devices, content consumption devices, universal serial bus (USB) dongles, data cards or combinations thereof. As such, the mobile terminal 8 may include one or more processors that may define processing circuitry either alone or in combination with one or more memories. The processing circuitry may utilise instructions stored in the memory to cause the mobile terminal to operate in a particular way or execute specific functionality when the instructions are executed by the one or more processors. The mobile terminal 8 may also include communication circuitry and corresponding hardware/software to enable communication with other devices and/or the network 6.

Referring now to Fig. 6, an apparatus 20 that may be embodied by or otherwise associated with a mobile terminal 8 (a cellular phone, a personal digital assistant (PDA), iPhone, iPad or the like) may include or otherwise be in communication with a processor 22, a memory device 24, a communication interface 28, and a user interface 30. In some example embodiments, the processor 22 (and/or co-processors or any other processing circuitry assisting or otherwise associated with the processor) may be in communication with the memory device 24 via a bus for passing information among components of the apparatus 20. The memory device 24 may include, for example, one or more non-transitory volatile and/or non-volatile memories. In other words, for example, the memory device 24 may be an electronic storage device (e.g. a computer readable storage medium) comprising gates configured to store data (e.g. bits) that may be retrievable by a machine (e.g. a computing device like the processor). The memory device 24 may be configured to store information, data, content, applications, instructions, or the like for enabling the apparatus to carry out various functions in accordance with an example embodiment of the present invention. For example, the memory device could be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory device 24 could be configured to store instructions for execution by the processor 22. The apparatus 20 may, in some embodiments, be embodied by a mobile terminal 8. However, in some embodiments, the apparatus may be embodied as a chip or chipset. In other words, the apparatus may comprise one or more physical packages (e.g. chips) including materials, components and/or wires on a structural assembly (e.g. a baseboard). The structural assembly may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon. The apparatus may therefore, in some cases, be configured to implement an embodiment of the present invention on a single chip or as a single "system-on-a-chip". As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.

The processor 22 may be embodied in a number of different ways. For example, the processor may be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other processing circuitry including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. As such, in some embodiments, the processor may include one or more processing cores configured to perform independently. A multi-core processor may enable multiprocessing within a single physical package. Additionally or alternatively, the processor may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading. In the embodiment in which the apparatus 20 is embodied as a mobile terminal 8, the processor may be embodied by the processor of the mobile terminal.

In an example embodiment, the processor 22 may be configured to execute instructions stored in the memory device 24 or otherwise accessible to the processor. Alternatively or additionally, the processor may be configured to execute hard coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processor may represent an entity (e.g. physically embodied in circuitry) capable of performing operations according to an embodiment of the present invention while configured accordingly. Thus, for example, when the processor is embodied as an ASIC, FPGA or the like, the processor may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of software instructions, the instructions may specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed. However, in some cases, the processor may be a processor of a specific device (e.g. a mobile terminal 8) configured to employ an embodiment of the present invention by further configuration of the processor by instructions for performing the algorithms and/or operations described herein. The processor may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processor. Meanwhile, the communication interface 28 may be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data from/to a network and/or any other device or module in communication with the apparatus 20. In this regard, the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications with a wireless communication network. Additionally or alternatively, the communication interface may include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s). In order to support multiple active connections simultaneously, such as in conjunction with a digital super directional array (DSDA) device, the communications interface of one embodiment may include a plurality of cellular radios, such as a plurality of radio front ends and a plurality of base band chains. In some environments, the communication interface may alternatively or also support wired communication. As such, for example, the communication interface may include a communication modem and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms.

In some example embodiments, such as instances in which the apparatus 20 is embodied by a mobile terminal 8, the apparatus may include a user interface 30 that may, in turn, be in communication with the processor 22 to receive an indication of a user input and/or to cause provision of an audible, visual, mechanical or other output to the user. As such, the user interface may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen(s), touch areas, soft keys, a microphone, a speaker, or other input/output mechanisms. Alternatively or additionally, the processor may comprise user interface circuitry configured to control at least some functions of one or more user interface elements such as, for example, a speaker, ringer, microphone, display, and/or the like. The processor and/or user interface circuitry comprising the processor may be configured to control one or more functions of one or more user interface elements through computer program instructions (e.g. software and/or firmware) stored on a memory accessible to the processor (e.g. memory device and/or the like).

The example of the solution to the described problem(s) (Figs. 1 and 2) described herein builds on the state when the mobile station (MS) location is known at cell level. That is, paging in the routing area is not required. Referring to Fig. 7, the mobile station which exits the packet transfer mode, and hence goes to packet idle mode, is required to operate on a given physical resource that is not the CCCH, for a given period of time (associated with a timer) while in packet idle mode. This physical resource is a packet data channel (PDCH) 701. By definition a PDCH carries packet logical channels, namely the packet data traffic channel (PDTCH) and the packet associated control channel 703 (PACCH). Hereafter this given physical resource, PDCH( not carrying (packet) common control channels), is referred to as IPDCH 705 (Idle mode PDCH) for convenience. The MS monitors downlink blocks on the IPDCH 707, e.g. for reception of resource assignments, and is allowed to use given uplink blocks on the IPDCH, e.g. for requesting resources. These uplink blocks are sent on an enhanced packet random access channel (ePRACH) logical channel, which is multiplexed together with the PACCH and PDTCH. In other words, the IPDCH is a PDCH on which a MS in packet idle mode monitors downlink blocks e.g. for reception of resource assignments and is allowed to use uplink blocks for requesting resources. The IPDCH, being a PDCH not carrying (packet) common control channels, also allows multiplexing traffic to/from this MS and to/from other MSs as well.

The solution provides a mechanism for uplink and downlink TBF establishment during this period, without using CCCH resources and is composed of several parts:

• activation of the mechanism;

• provision of the timer value 709 during which the MS operates on the IPDCH;

• provision of the description of the IPDCH 711 on which to operate;

• synchronisation of the mechanism between the network and the mobile station;

• definition of the procedures for fast TBF establishment on the IPDCH, for downlink TBF and uplink TBFs (the latter by means of a new temporary MS identifier);

• handling of circuit switched (CS) events 713while on the IPDCH;

• BCCH monitoring by the mobile station while the timer is running.

The solution can be identified as enhanced non-DRX mode with fast TBF establishment.

Activation of the Mechanism

The mechanism can only be used when supported by both the mobile station and the network. In one example, the mechanism is activated upon explicit order by the network to the mobile station. The order to use the mechanism is signalled by the network to the mobile station, for example either by an activation bit or by the presence of the parameters otherwise required by the mechanism such as the description of the IPDCH 705. Timer value

It can be assumed that this value is a semi-static parameter which shall be made known to the mobile station either prior to or during TBF establishment (at assignment) or at TBF release. The possible options are:

Timer option 1 : BCCH parameter broadcast in the cell

Timer option 2 (preferred): Reuse of non-DRX parameter on BCCH and MS specific in DRX parameters.

Timer option 1 and timer option 2 are almost equivalent. Timer option 1 requires the signalling of the timer value in at least one of the system information messages broadcast on BCCH. Timer option 2 has an advantage that the procedures related to non-DRX (e.g. signalling of DRX parameters including non-DRX timer value to SGSN), are already in place. No new signalling is needed. As already specified, the MS shall also indicate within the DRX parameters whether it supports the split paging group (PG) cycle option on CCCH. DRX parameters, which include non-DRX timer, are sent to the network in the ATTACH REQUEST message. If the DRX parameters are included in the ATTACH REQUEST message and if the attach is accepted, the network shall replace any stored DRX parameters for this MS and use them for downlink transfer of signalling and data.

The routing area update procedure can also be used for updating the network with new DRX parameters. 3GPP TR 24.008 says in the note in section 4.7.5 "Such changes can be used e.g. when the MS activates a PDP context with service requirements that cannot be met with the current DRX parameter. As PDP context(s) are activated and deactivated, the GMM (GPRS mobility management) context will be updated with an appropriate DRX parameter." The DRX parameters are included in the DL-UNITDATA PDU sent from the

SGSN to the BSS. If the SGSN has valid DRX Parameters for a temporary link level identity (TLLI) (a mobile station) then the SGSN shall include them in the PDU. Nevertheless, the SGSN can omit the DRX Parameters if the MS identified with the TLLI is in mobility management (MM) non-DRX mode period to speed up the transmission of the LLC-PDU on the radio interface. The SGSN shall not send a DL-UNITDATA PDU without the DRX Parameters information element (IE) if the MS identified with the TLLI is not in MM non-DRX mode period. The BSS does not know whether the MS signalled a value of the non-DRX timer to the SGSN in the DRX parameters. The BSS has to make a decision upon the reception of DL-UNITDATA PDU. The assumption is that the BSS stores a context of recent connection. The context is uniquely identified by TLLI.

The context shall include information about the MS capability of enhanced non-DRX mode and the IPDCH description among other information. If the BSS receives the DL-UNITDATA PDU with no DRX parameters, then the MS is in non- DRX mode and the BSS sends an assignment message on the IPDCH. If the received DL-UNITDATA PDU includes the DRX parameters, then the BSS makes a decision whether the MS is still in non-DRX mode, i.e. the enhanced non-DRX mode supporting MS monitors IPDCH, or whether the MS is in DRX mode, i.e. monitors only a subset of blocks on CCCH. The BSS can include the time when the MS exited the packet transfer mode, i.e. the last TBF was released, in the stored context, which then helps the BSS to decide whether the MS is still in non-DRX mode or not.

Timer option 3: TBF assignment parameter The timer value can also be provided at TBF establishment as part of an assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, PACKET UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE)

Timer option 4: at release of the last TBF (similar to "data terminal ready" (DTR)) The timer value can also be provided in a more dynamic manner during the TBF release. For an uplink TBF, the value can be signalled in the PACKET UPLINK ACK/NACK message. For a downlink TBF, the value can be signalled similarly to DTR signalling in the last radio link control/medium access control (RLC/MAC) block with the final block indicator (FBI) bit set.

It should be noted that the network could probably send a different timer value for the UL and DL TBFs in Timer option 2 and Timer option 4. If this can occur then there is an additional requirement on synchronisation to ensure that the network and the mobile station use the same value.

IPDCH Resource Description

In one example, the mobile station must know on which channel (PDCH) 705 the communication with the network can be done during the period when the timer is running 714. This channel can be:

IPDCH Resource Description option 1 : Default channel from the allocated PDCHs (e.g. lowest TN in the allocation). For example if the TBF that is being released was allocated on PDCHs with TN 3, 4, 5, then the IPDCH would be on TN=3. That is, when the mechanism is activated, the mobile by default operates on this PDCH.

IPDCH Resource Description option 2a: a channel from the allocated PDCHs, in which the network explicitly indicates which of the PDCHs is the IPDCH.

IPDCH Resource Description option 2b (preferred): any channel on the assigned carrier (TN0 - TN7) From a signalling viewpoint, both options 2a and 2b are equivalent (i.e. 3 bits are necessary to identify the TN of the PDCH). The option of signalling a channel on a different carrier including that of a channel on the BCCH carrier seems not to be a feasible solution though should be considered for completeness. In downlink dual carrier (DLDC) configurations, the IPDCH resource description should include the carrier identifier. The carrier can be also identified implicitly, e.g. the carrier on which the IPDCH is received or on which the final block indicator (FBI) or future activity indicator (FAI) is received.

The IPDCH Resource Description can be signalled as follows: IPDCH Resource Description signalling option I (applicable to IPDCH

Resource Description option 1): no point-to-point signalling is needed to indicate the default channel. However, the default channel could be indicated in the cell uniformly by means of a system information message broadcast on BCCH in the cell.

IPDCH Resource Description signalling option 2 (applicable to Resource ID options 2a and 2b): in an assignment message (e.g. PACKET DOWNLINK ASSIGNMENT, PACKET UPLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE), in which the network indicates which PDCH the MS shall operate on upon TBF release.

IPDCH Resource Description signalling option 3 (preferred) (applicable to IPDCH Resource Description options 2a and 2b): at release of the last TBF (similar to DTR). As noted above, from the mobile station perspective, it is simply a TBF. The network can know it is the last, but it is also a TBF, which should be the last.

The IPDCH Resource Description signalling option 1 may cause problems on the network resources. The default channel, e.g. the lowest numbered timeslot of the assignment, can become overloaded with mobile stations in enhanced non-DRX mode. If the IPDCH Resource Description is signalled during TBF assignment or at TBF release, then it shall be ensured that the applied value is unambiguous in case different values were signalled on the uplink and the downlink TBF. In this case, both the mobile terminal and the network must determine the same IPDCH resource. The IPDCH Resource Description signalling should be provided in a more dynamic manner than the timer value. The distribution of load on the PDCHs may change quickly, and therefore the IPDCH Resource Description signalling options 1 and 2 are not the most suited for this purpose. The IPDCH Resource Description signalling option 3 is preferred.

Synchronisation

Timer Value

The mobile station (MS) could receive different values of the timer in case of concurrent uplink and downlink TBFs if Timer option 3 or Timer option 4 is used. Note that the multiple TBF operation is not considered. The enhanced non-DRX mechanism has to ensure that should several values be received, a) a determination is made to use a single one, and b) that both the mobile station and the network are using this same value 714. A simple determination could be to use the latest value sent (by the network) / received (by the mobile station). If the timer value is signalled during TBF assignment and/or TBF reconfiguration, the synchronisation takes place already during these procedures. The network uses the polling for control messages. If the timer value is signalled during TBF release, then the synchronisation problem is the same as for the Resource Id signalling option 3 discussed in the section below.

IPDCH Resource Description

When the IPDCH Resource Description is signalled at TBF assignment or TBF release, the mobile station can potentially receive different IPDCH Resource Descriptions on the uplink TBF and the downlink TBF. The IPDCH Resource description should be signalled during the TBF release. Figures 8 to 14 illustrate examples of TBF release procedure for TBF operating in RLC acknowledged mode and, in case of the uplink, the extended uplink TBF mode. Figs. 8 to 10 illustrate examples of UL TBF release and Figs. 11 to 14 illustrate examples of DL TBF release.

Referring to Figs. 8 to 10, the IPDCH Resource Description can be delivered to the mobile station in the PACKET UPLINK ACK/NACK message 801 carrying FAI="1" or in an extension of the (E)GPRS RLC/MAC block for data transfer 1103 (similar to DTR signalling using the length indicator). It should be noted that the same value of the length indicator as for the DTR signalling can be used because the DTR information should not be signalled at TBF release.

When the mobile station has concurrent UL and DL TBFs, the time required to release a TBF depends on the need for retransmission of relevant messages. To avoid any problems with synchronisation of IPDCH Resource Description, the network should not initiate the release of both TBFs simultaneously (release TBFs sequentially), or the network should ensure the same IPDCH Resource Description is signalled on both the uplink and the downlink TBFs. Common Values for non-DRX and TBF Release Timers

T3192 is the timer 1101 used by the MS to wait for the release of the downlink TBF. The value of this timer has been observed to range from 0 to 500 ms. The most common value is expected to be from 200 ms to 500 ms. DRX TIMER MAX is the parameter controlling the duration of the non-DRX period during which the mobile station monitors all blocks on CCCH. This parameter in real networks had values 64 and 4 seconds. Two of three networks studied broadcasted the value 64 seconds. Non-DRX timer can be "negotiated" with the SGSN along with other DRX parameters. TBF Establishment

Downlink TBF Establishment

Referring to Fig. 15, the downlink TBF can be established on PDCH identified by the Resource ID which the mobile station is monitoring during the signalled period. The network assigns the uplink TBF using the PACKET DOWNLINK ASSIGNMENT 1501 including TLLI. It is important to ensure that the mobile station stays in the GMM Ready state during at least the entire duration of the non-DRX period so that the mobile station can be addressed using TLLI as per the current rules. The duration of GMM Ready state is controlled by the GMM Ready timer negotiated by the mobile station and the network during the GPRS attach or GPRS routing area updating procedure. The downlink TBF assignment procedure is illustrated schematically in Fig. 15 where the signalling exchange with the network takes place on the IPDCH 1503 (on PACCH), not on CCCH. The network has an option to poll the mobile station for the packet control acknowledgment message.

Uplink TBF Establishment

Referring to Fig. 16, the mobile station initiates an access procedure on the IPDCH 1503 which it is monitoring while the timer above is running (preferably the non-DRX period as indicated previously). As currently specified, uplink TBF establishment on CCCH is done by means of the Packet Access Procedure using CCCH (see 3 GPP TS 44.018 §3.5.2). This procedure typically consists of a first "handshake" on CCCH followed by one or more handshakes for contention resolution on the assigned PDCH. The MS first issues a CHANNEL REQUEST or an EGPRS PACKET CHANNEL REQUEST on the random access channel (RACH). These messages are short: 8-bit or 11-bit (CHANNEL REQUEST) or 11-bit only (EGPRS PACKET CHANNEL REQUEST) for they use the access burst formats. These messages contain an establishment cause and a random reference. The random reference is set by the mobile station and targeted at allowing a preliminary distinction between mobile stations by the network, without actually being able to precisely identify the mobile station. The identification of the mobile station takes place at a later stage on the assigned packet resources by means of contention resolution. Until contention resolution is completed, the mobile station as well as its full radio access capabilities are not uniquely identified. This procedure is therefore rather inefficient, not only because of the issues highlighted above, but also because of the several handshakes needed to take place before the mobile station and its capabilities are properly identified by the network .

Given the approach herein is to operate on IPDCH, and not on CCCH, there is an opportunity to provide a much more efficient uplink TBF establishment procedure on IPDCH than is available from CCCH. The idea is to have a single handshake on IPDCH whereby the mobile station seeking access and its capabilities can be immediately identified by the network upon uplink access. It should be noted however that the uplink access still needs to use the access burst format (8 bit or 11 bit, as indicated by the network on BCCH). The approach described herein exploits the fact that the network can order a MS to operate on IPDCH only for a MS with which it has at least one TBF established. That is, for which the network already knows the MS identity (TLLI) and radio access capabilities (and of course that supports this mechanism, as described previously). Therefore, in one embodiment the network assigns a temporary identity to such a mobile station, such that a one-to-one mapping exists for the timer duration between this temporary identity used on the IPDCH and the mobile station's TLLI and such that the network keeps the context of this mobile station stored (including at least the radio access capabilities of the mobile station) for the timer duration. This way the network can retrieve during a given period (timer duration) the exact identity and radio access capabilities of a mobile station making an uplink access on IPDCH by means of this temporary identity and the IPDCH on which it is received (i.e. contention is resolved immediately on the network side upon reception of this identity) and can as a result "immediately" assign an appropriate TBF to this very mobile station without any further handshake. This temporary identity would be signalled to the mobile station preferably at TBF release, along with the IPDCH Resource Description.

This temporary identity should preferably fit within the 8 bit and 11 bit formats and thus should be only a few bits long. It is referred to as the ePRACH MS ID 1605 (where ePRACH means enhanced packet random access channel).

The uplink access be made by a new channel request message using one of the 8-bit or 11 -bit access burst formats: FAST PACKET CHANNEL REQUEST 1607. Whether the 8-bit or the 11 -bit message is used is controlled by the ACCESS BURST TYPE bit in the GPRS Cell Options IE (See 3 GPP TS 44.060). This message would be sent on a specific logical channel on the IPDCH, ePRACH. The ePRACH is multiplexed with other logical channels (PDTCH, PACCH) sharing the IPDCH and its allocation can be:

ePRACH allocation option 1: fixed occurrence specified in specifications ePRACH allocation option 2: fixed occurrence signalled on BCCH

ePRACH allocation option 3: fixed occurrence signalled individually to the mobile station e.g. at BF release (e.g. every n-th frame).

ePRACH allocation option 4 (preferred): dynamically allocated by the network by means of an USF (uplink state flag) dedicated to this purpose, e.g. USF=' l 11 ' 1611 (i.e. similar to USF=free that was defined for PRACH)

An example of the network access procedure initiated by the mobile station on IPDCH is shown in Fig. 16. In this example, ePRACH is allocated according to option 4. The polling for the control acknowledgment message is optional.

The FAST PACKET CHANNEL REQUEST message 1607 contents are shown in Table 1 and Table 2. These messages are 8-bit or 1 1-bit long and coded as RACH (8-bit and 1 1-bit, respectively) and transmitted using the 8-bit or 1 1-bit access burst format respectively. The messages are used to send the Fast Access Request 1607 in which the mobile station identifies itself with the ePRACH MS ID 1605. The priority is sent along the ePRACH MS ID in the Fast Access Request which the network can consider when responding to the request. The length of ePRACH MS ID can be longer than 5 bits if necessary. However, if the length is 5 bits then ePRACH MS ID and IPDCH Resource Indication (IPDCH Resource Description option 2b) could fit into one octet in RLC data block.

Table 1 - Fast Packet Channel Request message content (11-bit format)

< Fast Packet Channel Request message content > ::=

< Fast Access Request : 0000 < ePRACH MS ID : bit (5) >

< Priority : bit (2) > >;

Table 2- Fast Packet Channel Request message content (8-bit format)

< Fast Packet Channel Request message content > ::=

< Fast Access Request : 0 < ePRACH MS ID : bit (5) >

< Priority : bit (2) > >;

The fast access procedure should be based on the packet access procedure using CCCH and the initiation of a TBF establishment on PCCCH as much as possible. The fast access procedure is initiated by the transmission of Fast Packet Channel Request message 1607. Upon the transmission of the message on the IPDCH (uplink), the mobile station leaves the idle (non-DRX) mode and listens to the IPDCH (downlink) for the response. The response should be the PACKET UPLINK ASSIGNMENT message 1615 addressing the MS with temporary link level identity (TLLI). It should be noted that if the mobile station initiated the fast access procedure just before the expiry of the timer, it can happen that the retransmission of the Fast Packet Channel Request message is received by the network after the timer expires for the mobile station on the network side. Therefore, the duration of the access procedure should be taken in to the account by the network when assigning the ePRACH MS ID and also to in the fast access procedure itself. Appropriate parameters for persistence control on IPDCH (ePRACH) should be defined. With the ePRACH Allocation Option 4 (i.e. by USF), the USF is used which assigns either one uplink radio block (4 bursts) or 4 uplink radio blocks (4 times 4 bursts) as per the USF Granularity field. The mobile station should randomly draw which burst(s) of the 4 or 16 bursts of the uplink radio block(s) in which to send the FAST PACKET CHANNEL REQUEST message 1607.

Concurrent BCCH and IPDCH Monitoring

The current procedures of MS in the packet idle mode in regard to BCCH information acquisition are the following. The mobile station in packet idle mode shall supervise the BCCH CHANGE MARK in SI 13 and perform update of BCCH information. For this purpose, the mobile station shall attempt to receive SI 13 at least every 30 seconds. The mobile stations may also receive the relevant information in PSI13 on PACCH, which should be taken into account when the mobile station enters the idle mode. If the mobile station has received neither SI 13 nor PSI13 within the last 30 seconds, it shall attempt to receive SI 13 each time it is scheduled on BCCH.

The above requirements should be kept for the mobile station during the time it monitors IPDCH. When required by the rules for monitoring BCCH information, the mobile station reads BCCH block instead of the blocks on IPDCH. The network can take this information into account and not schedule downlink messages and allocate ePRACH during the period when SI 13 is scheduled on BCCH.

Feature Support Signalling

In order to make use of the processes described herein, the BSS has to know whether the mobile station supports this feature or not.

MS Feature Support option 1 : MS Radio Access Capabilities

The BSS does not need to signal the support of this feature. The MS feature support indication is ignored by the non-supporting BSS. Circuit Switched (CS) Calls

Mobile Originated

When there is a mobile originated call, the mobile station stops receiving blocks on the IPDCH with no notification to the network and initiates RR connection establishment on CCCH.

Mobile Terminated

The page message sent from the mobile switching station (MSC) to the BSS contains the international mobile subscriber identity (IMSI) and the temporary mobile subscriber identity (TMSI). The TMSI may be omitted in the exceptional case where the IMSI is used instead of the TMSI as a paging address at the radio interface.

Mobile Terminal (MT)circuit switched (CS) Call option 1: Page messages on IPDCH (requires paging coordination in the BSS)

This option requires that the BSS knows the time during which the MS receives blocks on IPDCH, and the IMSI is stored in the context associated with the MS. Upon reception of the paging message from the MSC, the BSS using IMSI address decides whether the addressed MS is reachable on the IPDCH or not. If the MS is able to receive blocks on IPDCH then the page messages are sent on IPDCH. Otherwise, the page messages for this MS are sent on CCCH blocks belonging to the MS paging group.

MT CS Call option 2 (preferred): Page messages on CCCH always

In the Timer option 2 solution based on the current handling of non-DRX timer in the GERAN, the BSS may not always have up to date information about the time the MS monitors IPDCH. Therefore, MT CS Call option 1 is not suitable. In this case, the MS will have to monitor blocks of its paging group on CCCH while it is also monitoring blocks on IPDCH. The consequence of doing so is such that the MS is required to attempt to receive blocks on CCCH and IPDCH during one radio block period. There may be configurations when this is not possible, e.g. IPDCH is allocated on TNO of non-BCCH carrier. The BSS should avoid such conflicting configurations or it should take into account the CCCH monitoring when scheduling blocks on IPDCH (including ePRACH). Although this can be seen as a drawback, the MT CS Call option 2 solution is feasible and preferred over option 1.

Relation between the READY Timer and the Time MS is on IPDCH

The value of READY timer and the time during which the MS monitors blocks on IPDCH has to be coordinated. The time the MS spends on IPDCH before moving to CCCH should be shorter or at most the same as the value of the READY timer. When the READY timer expires at the SGSN, the network has to page the MS if downlink data or signalling information needs to be sent. The SGSN sends the PAGING PS PDU to the base station system (BSS) on the Gb interface requesting the BSS to initiate paging for the MS within a group of cells. The situation is similar to the mobile terminated calls, see above.

The READY timer is also important in the scenario when the MS performs cell reselection while monitoring blocks on IPDCH. When the READY timer is running at the MS, then the MS performs a cell update procedure towards SGSN any time the cell changes. In case of intra-BSS cell reselection, the BSS can detect that the MS moved out from the cell based on the TLLI. The BSS can update the MS context when it detects the cell changed and the BSS can reuse the ePRACH for other MS.

The methods of the several examples of embodiments of the invention consist of several steps in which there are several options as to how to complete each step in GERAN. Regardless of the options selected, the benefits of the proposal are: less signalling needed to establish radio connection; shorter latency of radio connection establishment; and flexibly off-loading packet signalling from CCCH to PDCH. Referring to Fig. 17 there is depicted a flow chart of an example of an embodiment of the method. The network issues a directive to a mobile station (MS or UE) to activate monitoring of PDCH in packet idle mode 1701. A timer value is set 1703 for operating on PDCH in packet idle mode. The timer value can originate from one of several sources. Referring to Fig. 18, the PDCH timer value can be sourced from a broadcast on BCCH 1803 or it can be a duplicate of a DRX time value taken from existing DRX signalling 1805. Alternatively, signal options include that the PDCH timer value can be received in an assignment message from the network 1807, it may be received in an RLC/MAC control message 1809, or it may be signalled in a packet uplink ACK/NACK during a TBF uplink signal 1811. Referring back to the method shown in Fig. 17, UE must select a channel to use as its PDCH resource 1705. Fig. 18 shows that there are several sources for the PDCH channel selection. In packet idle mode, this description refers to PDCH as IPDCH 1813 and it may be a default channel taken from allocated PDCHs 1815. IPDCH may be a designated received channel (rather than a default channel) taken from among allocated PDCHs 1817. Or it may be any channel on the assigned carrier(s) 1819. With the channel selected for IPDCH and a timer set, the method (Fig. 17) continues with steps for monitoring downlink blocks on IPDCH for a downlink resource assignment 1707 and enabling the use of uplink blocks on the IPDCH for requesting uplink resources 1709. Referring to Fig. 19, the final steps of the method of operating on IPDCH in packet idle mode is either the establishment of an uplink TBF 1903 with a signalling exchange on the IPDCH or establishing a downlink TBF 1905, again with a signalling protocol conducted on the IPDCH. As described above, Figures 17 and 19 show flowcharts of a method, apparatus and program product according to example embodiments of the invention. It will be understood that each block of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by various means, such as hardware, firmware, processor, circuitry and/or other device associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory device 24 of an apparatus 20 employing an embodiment of the present invention and executed by a processor 22 in the apparatus. As will be appreciated, any such computer program instructions may be loaded onto a computer or other programmable apparatus (e.g. hardware) to produce a machine, such that the resulting computer or other programmable apparatus embody a mechanism for implementing the functions specified in the flowchart blocks. These computer program instructions may also be stored in a non-transitory computer- readable storage memory (as opposed to a transmission medium such as a carrier wave or electromagnetic signal) that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture the execution of which implements the function specified in the flowchart blocks. The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart block(s). As such, the operations of Figures 17 and 19, when executed, convert a computer or processing circuitry into a particular machine configured to perform an example embodiment of the present invention. Accordingly, the operations of Figures 17 and 19 define an algorithm for configuring a computer or processing circuitry (e.g. processor) to perform an example embodiment. In some cases, a general purpose computer may be configured to perform the functions shown in Figures 17 and 19 (e.g. via configuration of the processor), thereby transforming the general purpose computer into a particular machine configured to perform an example embodiment.

Accordingly, blocks of the flowcharts support combinations of means for performing the specified functions, combinations of operations for performing the specified functions and program instructions for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by special purpose hardware-based computer systems which perform the specified functions or operations, or combinations of special purpose hardware and computer instructions.

In some embodiments, certain ones of the operations above may be modified or further amplified. Furthermore, in some embodiments, additional optional operations may be included. Modifications, additions, or amplifications to the operations above may be performed in any order and in any combination.

Many modifications and other embodiments of the invention set forth herein will come to mind to one skilled in the art to which the invention pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

1. A method for uplink and downlink temporary block flow (TBF) establishment in a mobile station of a mobile network, the method comprising:

receiving, in packet transfer mode, an order from the network to activate monitoring, in packet idle mode, of a packet data channel (PDCH) not carrying (packet) common control channels;

setting a timer value during which to operate on the PDCH while in packet idle mode; and

selecting a channel as the PDCH resource.

2. A method according to claim 1, comprising:

monitoring, in packet idle mode, downlink blocks on the PDCH for downlink resource assignment.

3. A method according to claim 1 or claim 2, comprising:

enabling, in packet idle mode, the use of uplink blocks on the PDCH for requesting uplink resources.

4. A method according to any of claims 1 to 3, wherein the PDCH is an idle mode packet data channel (IPDCH).

5. A method according to any of claims 1 to 4, wherein the timer value is a parameter broadcast on the broadcast control channel (BCCH).

6. A method according to any of claims 1 to 4, wherein the timer value is a non- discontinuous reception (DRX) time value included in existing DRX parameter signalling.

7. A method according to any of claims 1 to 4, wherein the timer value is received as part of an assignment/reconfiguration message.

8. A method according to any of claims 1 to 4, wherein the timer value is received in a radio link control/medium access control (RLC/MAC) during downlink TBF.

9. A method according to any of claims 1 to 4, wherein the timer value is signalled in a packet uplink acknowledgement/non-acknowledgement (ACK/NACK) signal during uplink TBF.

10. A method according to any of claims 1 to 9, wherein the selected channel for the PDCH resource is a default channel from allocated one or more PDCHs.

11. A method according to any of claims 1 to 9, wherein the selected channel for the PDCH resource is a received channel designation from allocated one or more PDCHs.

12. A method according to any of claims 1 to 9, wherein the selected channel for the PDCH resource is any channel on the assigned carrier(s).

13. A method according to any of claims 1 to 12, comprising:

establishing a downlink temporary block flow (TBF) with a signalling exchange on the PDCH resource.

14. A method according to claim 13, wherein the signalling exchange comprises receiving a packet downlink assignment including a temporary link level identity

(TLLI).

15. A method according to any of claims 1 to 12, wherein receiving an order from the network includes receiving a temporary unique identifier valid only on the PDCH resource in uplink and uniquely identifying the mobile station when sending on uplink.

16. A method according to claim 15, wherein the temporary unique identifier is 5 bits long.

17. A method according to any of claims 1 to 16, comprising:

establishing an uplink temporary block flow (TBF) with a signalling exchange on the PDCH resource.

18. A method according to claim 17, wherein the signalling exchange comprises sending a fast packet channel request message to the network, receiving a packet uplink assignment including a TLLI, and optionally sending a packet control acknowledgement signal to the network.

19. A method according to claim 18, wherein the fast packet channel request message includes the temporary unique identifier.

20. A method according to any of claims 1 to 19, wherein the network order to monitor the PDCH in packet idle mode anticipates instant message traffic.

21. Apparatus comprising a processing system constructed and arranged to cause the apparatus to upon receipt, in packet transfer mode, of an order from the network to activate monitoring, in packet idle mode, of a packet data channel (PDCH) not carrying (packet) common control channels:

set a timer value during which to operate on the PDCH while in packet idle mode; and

select a channel as the PDCH resource.

22. Apparatus according to claim 21, arranged to:

monitor, in packet idle mode, downlink blocks on the PDCH for downlink resource assignment.

23. Apparatus according to claim 21 or claim 22, arranged to:

enable, in packet idle mode, the use of uplink blocks on the PDCH for requesting uplink resources.

24. Apparatus according to any of claims 21 to 23, wherein the PDCH is an idle mode packet data channel (IPDCH).

25. Apparatus according to any of claims 21 to 24, wherein the timer value is a parameter broadcast on the broadcast control channel (BCCH).

26. Apparatus according to any of claims 21 to 24, wherein the timer value is a non-discontinuous reception (DRX) time value included in existing DRX parameter signalling.

27. Apparatus according to any of claims 21 to 24, wherein the timer value is received as part of an assignment/reconfiguration message.

28. Apparatus according to any of claims 21 to 24, wherein the timer value is received in a radio link control/medium access control (RLC/MAC) during downlink TBF.

29. Apparatus according to any of claims 21 to 24, wherein the timer value is signalled in a packet uplink acknowledgement/non-acknowledgement (ACK/NACK) signal during uplink TBF.

30. Apparatus according to any of claims 21 to 29, wherein the selected channel for the PDCH resource is a default channel from allocated one or more PDCHs.

31. Apparatus according to any of claims 21 to 29, wherein the selected channel for the PDCH resource is a received channel designation from allocated one or more

PDCHs.

32. Apparatus according to any of claims 21 to 29, wherein the selected channel for the PDCH resource is any channel on the assigned carrier(s).

33. Apparatus according to any of claims 21 to 32, arranged to:

establish a downlink temporary block flow (TBF) with a signalling exchange on the PDCH resource.

34. Apparatus according to claim 33, wherein the signalling exchange comprises receiving a packet downlink assignment including a temporary link level identity

(TLLI).

35. Apparatus according to any of claims 21 to 32, wherein receiving an order from the network includes receiving a temporary unique identifier valid only on the PDCH resource in uplink and uniquely identifying the mobile station when sending on uplink.

36. Apparatus according to claim 35, wherein the temporary unique identifier is 5 bits long.

37. Apparatus according to any of claims 21 to 36, arranged to:

establish an uplink temporary block flow (TBF) with a signalling exchange on the PDCH resource.

38. Apparatus according to claim 37, wherein the signalling exchange comprises sending a fast packet channel request message to the network, receiving a packet uplink assignment including a TLLI, and optionally sending a packet control acknowledgement signal to the network.

39. Apparatus according to claim 38, wherein the fast packet channel request message includes the temporary unique identifier.

40. Apparatus according to any of claims 21 to 39, wherein the network order to monitor the PDCH in packet idle mode anticipates instant message traffic.

41. A computer program comprising a set of instructions which when executed on a processor of a user equipment causes the user equipment (UE) to perform:

receiving, in packet transfer mode, an order from the network to activate monitoring, in packet idle mode, of a packet data channel (PDCH) not carrying (packet) common control channels;

setting a timer value during which to operate on the PDCH while in packet idle mode; and

selecting a channel as the PDCH resource.