HK1117323B - Method and apparatus for improving radio spectrum usage and decreasing user data delay - Google Patents

Description

Method and apparatus for improving radio spectrum usage and reducing user data delay

This application is a divisional application of the parent application (filing date: 2003.09.09, application No.: 02806247.7, entitled method and apparatus for improving radio spectrum usage and reducing user data delay).

Technical Field

The present invention relates generally to wireless communication devices and methods, and more particularly, to wireless terminals, networks, and systems for communicating packet data over a radio channel.

Background

The following terms will be used in the following description, and are defined as follows:

GSM global system for mobile communications, a digital radio communication system using a Time Division Multiple Access (TDMA) air interface.

GPRS general packet radio service, a GSM phase 2+ service,

in such services, the radio resources for data transmission are allocated on a per data block basis, as opposed to a circuit switched basis.

MS mobile stations such as handheld cellular telephones, car-mounted cellular telephones, personal communication devices, Personal Digital Assistant (PDA) devices with wireless communication capabilities, wireless communication modules that can be installed within or with computers by plugging into PCMCIA slots and the like, and in general, any device capable of two-way communication with a wireless network.

DL downlink: direction from the wireless network to the MS.

UL uplink: direction from MS to wireless network.

PSI packet system information (message)

PBCCH packet broadcast control channel: a downlink channel for broadcasting PSI messages.

PACCH packet associated control channel: the logical channel for the control block between the network and the MS is sent on the same channel on which the packet data block is sent (i.e., in packet data transfer).

Temporary flow of TBF: temporary packet data flow from MS to network (UL TBF) or from network to MS (dltbf). If no direction is specified, the TBF means ULTBF, DL TBF, or both.

PTM packet transfer mode: it is a mode in which the MS receives packet data, transmits packet data, or both, that is, the MS activates an UL TBF, a DL TBF, or both.

Multi-RAT multiple radio access technologies: a MS with both 2G (gsm) and 3G (umts) capabilities, i.e. a 2G-3G multimode phone that can acquire 2G or 3G network services.

In the initial acquisition of PSI messages, the network does not necessarily know which PSI messages need to be sent to the MS, for example, after (re) selecting a cell. This problem will become more prominent in future releases [ e.g., releases after 1997 (R97), 1998 (R98) and 1999 (R99) ] with the introduction of new PSI messages. As currently specified, a designated MS cannot tell the network which PSI messages it desires to receive from the network.

More specifically, during an unspecified update procedure, the MS needs to receive at least one instance of the various PSI message types. The PSI status message of the packet is not presently specified in order to indicate which PSI message type or types are required by the MS, thereby performing a change mark check. Also, the currently specified packet PSI state procedure cannot be used in the local acquisition procedure.

Objects and advantages of the invention

A first object and advantage of the present invention is to provide an improved packet data procedure that overcomes the above-referenced problems and others.

It is another object and advantage of the present invention to provide a capability for an MS to indicate to the network which PSI messages need to be derived from.

Disclosure of Invention

The foregoing and other problems are overcome, and the foregoing objects and advantages are realized, by methods and apparatus in accordance with embodiments of the present invention.

In accordance with the teachings herein, the MS is enabled to explicitly inform the network of which PSI messages need to be received, and in response, the network is enabled to send only those PSI messages to the MS that are needed. Thereby better using the spectrum of the packet data channel and improving data throughput.

Another benefit that results from this is that: the MS does not need to abort an ongoing packet transfer during the unspecified update procedure, thereby further improving data throughput. Also, since there is no need to suspend the TBF, the spectrum is more fully used and more efficiently allocated because in a conventional TBF suspension, data blocks cannot be transmitted or received in the duration of each PBCCH data block and surrounding blocks due to channel structure delays and setup time required in the Digital Signal Processor (DSP) of the MS.

Another advantage of these teachings is that the currently prescribed signaling procedures are used, thereby eliminating the need to specify new signaling procedures.

A method in accordance with these teachings provides for operation of a wireless communication system having packet data capabilities and includes the steps of: (a) transmitting a message from the mobile station to the network on the same physical channel used to transmit the packet data, the message specifying individual ones of Packet System Information (PSI) messages required for reception by the mobile station; and (b) in response to receipt of this message, transmitting only the individual messages specified in the PSI message from the network to the mobile station via the same channel on which the packet data was transmitted.

In a presently preferred, but nonlimiting, embodiment, the message is a packet PSI STATUS (PACKET PSI STATUS) message and the physical channel carries a Packet Associated Control Channel (PACCH). The steps of sending the message and sending the PSI message occur in a packet data transfer mode and without suspending an established Temporary Block Flow (TBF). In this preferred embodiment, the mobile station contains the (optional) fields PSIx COUNT and Instance Bitmap and sets their respective fields to zero for the particular PSI message type in the packet PSI status message, thereby populating the packet PSI status message. In response, the network determines that the mobile station has not received the particular PSI message type and ignores the PSI CHANGE MARK (PSI CHANGE MARK) indicated in the packet PSI status message.

In addition, in accordance with these teachings, a method for operating a wireless communication system having packet data capabilities is presented. The method includes transmitting a packet PSI status message from the mobile station to the network, the packet PSI status message specifying an individual Packet System Information (PSI) message type required for reception by the mobile station, and transmitting only the specified individual PSI message type from the network to the mobile station in response to receipt of the packet PSI status message. The sending of the packet PSI status message includes indicating the PSI message types supported by the mobile station in a received PSI message list of the packet PSI status message. In the packet PSI status message, the mobile station may indicate the current status of the PSI message type and the PSI message type not being received for each PSI message type for which the mobile station desires a PSI change mark (PSI CHANGEMARK) value. In this case, the mobile station desires a PSI change mark value at least in a partial acquisition of the PSI message.

The PSI message types required for reception by the mobile station are those that meet the following criteria: a) the mobile station considers the relevant PSI message type according to the features it supports; and b) for an optional PSI message type, this PSI message type has been indicated by the network as being present on a Packet Broadcast Control Channel (PBCCH).

Drawings

The above and other features of the present invention will become apparent from the following detailed description of the invention when considered in conjunction with the accompanying drawings, wherein:

FIG. 1 is a simplified block diagram of a wireless communication system suitable for implementing teachings in accordance with the present invention;

FIG. 2 shows a consistent set of system information messages;

fig. 3 shows an example of the PSI message in connection with several examples, in this example, PSI2 ═ four examples, PSI2_ change _ flag ═ 2; and

figure 4 shows the information elements of the packet PSI status message.

Detailed Description

Referring initially to fig. 1, a simplified block diagram of an embodiment of a wireless communication system suitable for implementing the present invention is depicted. Assume that system 1 includes a plurality of mobile stations 100. For convenience, fig. 1 shows two Mobile Stations (MSs), one of which is labeled MS # 1 and the other is labeled MS # 2. Fig. 1 also shows an exemplary network operator, for example, having a GPRS Support Node (GSN)30 for connecting to a telecommunications network, such as a Public Switched Telephone Network (PSTN) and/or a public Packet Data Network (PDN), and at least one Base Station Controller (BSC)40 and a plurality of Base Transceiver Stations (BTS)50 that transmit physical and logical channels to the mobile station 100 in a forward or Downlink (DL) direction according to a predetermined air interface standard. There is also a reverse or Uplink (UL) communication path from the mobile station 100 to the network operator 2 that carries mobile-originated access requests and traffic. It is assumed that each BTS50 supports one cell and that one or more MSs are located in that cell. As described in more detail below, the MS100 and the network 2 use an improved PSI procedure in accordance with these teachings.

In a preferred, but non-limiting embodiment of these teachings, the air interface standard may conform to any standard capable of data transfer with the mobile station 100, such as internet 70 access and web page downloads. In the presently preferred embodiment of the present invention, the air interface standard is a Time Division Multiple Access (TDMA) air interface that supports the enhanced GPRS capabilities disclosed herein.

The network operator 2 may also include a System Message Service Center (SMSC)60 that receives messages and forwards messages for the mobile station 100, but may also employ any wireless messaging technology that can use packet data. Other types of messaging services may include auxiliary data services, as well as services currently under development and referred to as Multimedia Messaging Services (MMS), in which image messages, video messages, audio messages, text messages, executable content, and the like, as well as combinations thereof, may be communicated between the network and the mobile station.

The mobile station 100 typically includes a micro-control unit (MCU)120 having an output coupled to an input of a display 140 and an input coupled to an output of a keyboard or keypad 160. The mobile station 100 may be considered to be a handheld radiotelephone, such as a cellular telephone or personal communicator. The mobile station 100 may also be contained within a piece or module that is connected to another device in use. For example, the mobile station 100 may be embodied in a PCMCIA card or similar type of card or module that, in use, is mounted within a portable data processor, such as a laptop computer, notebook computer, or even a computer that can be worn by a user.

It is assumed that the MCU120 includes or is coupled to some type of memory 130, wherein the memory 130 includes a Read Only Memory (ROM) for storing an operating program, and further includes a Random Access Memory (RAM) for temporarily storing required data, and a temporary memory for storing received packet data and transmitted packet data, and the like. Memory 130 is also assumed to hold PSI messages, as described in greater detail below. A separate removable SIM card (not shown) may also be provided, for example, which stores a preferred Public Land Mobile Network (PLMN) list and other subscriber related information. For purposes of the present invention, it is assumed that this ROM stores a program that enables the MCU120 to execute the software routines, layers, and protocols required for packet data transmission and reception implemented in accordance with the teachings herein and provides an appropriate User Interface (UI) to a user via the display 140 and keypad 160. Although not shown, a microphone and speaker are typically provided to enable the user to handle voice calls in a conventional manner. Although in practice this functionality is typically implemented through program instructions stored in memory 130, the packet PSI state processing module operating in accordance with the present invention is shown generally as block 260.

The mobile station 100 also includes a wireless portion that includes a Digital Signal Processor (DSP)180, or equivalent high speed processor, and a wireless transceiver comprised of a transmitter 200 and a receiver 220, both of which are coupled to an antenna 240 for communication with a network operator. Packet data is transmitted and received via antenna 240 in accordance with the teachings herein.

Having thus described one suitable embodiment of a wireless communication network 2, mobile station 100 and overall system 1 for practicing the present invention, a more detailed description of the invention will now be provided.

These teachings provide a method for handling different types of PSI message acquisition in a packet data transfer mode using existing procedures and messages. These PSI message acquisitions include an initial acquisition in which the PSI message is first received in the cell. A problem exists in this case in that the network 2 does not know which PSI messages to send to the MS 100. This is particularly the case in R99 and more recently networks for which several alternative PSI message types have been defined. PSI message capture also includes the case of updates specified by the network 2 in the PSI _ change _ field of a PSI1 message, where a group of messages is explicitly defined and an unspecified update is commanded.

In order to better understand the present invention and the benefits of using the same, the use of current PSI messages and the problems caused by the currently specified PSI message procedures will first be described.

In GPRS, if a cell supports a control channel dedicated to GPRS (pbcch), then the system information related to the packet access parameters is broadcast as PSI messages. In this case, the MS100 should receive all broadcast PSI messages.

Different exemplary types of PSI messages will now be shown with reference to figure 2. If there is a PBCCH in one cell, the network 2 regularly broadcasts Packet System Information (PSI) type messages on the PBCCH. PSI2, PSI3bis messages, and some other types of PSI messages may be broadcast in various instances. From the information broadcast in the PSI message, the MS100 is able to determine whether and how to access the network 2 via the current cell.

If multiple instances of PSI message type are sent on the PBCCH, then the MS100 should receive a consistent set of PSI (or System Information (SI)) messages of this type. As shown in fig. 2, in some cases more than one PSI message may be added to a consistent set. As an example, all instances (1-8) of the PSI2 message constitute a consistent set.

Referring now to fig. 3, a consistent set of system information messages is identified by the PSI _ change _ mark parameter contained in each message of the set. All PSI messages within a consistent set are specified to have the same PSI _ change _ mark parameter value.

The total number of certain system information messages within a consistent set is indicated by a PSI _ count parameter included in each PSI message of the group. Within a consistent set of system information messages, the location of a certain message instance is indicated by a PSI _ index parameter.

The value of the PSI _ COUNT parameter is N-1, where N is the number of instances of a particular message type present in the congregation. The PSI _ index parameter ranges from zero to N-1, with different instances of a particular message type having different PSI _ index parameter values in a consistent set.

Fig. 3 shows an example of PSI messages in conjunction with several examples: PSI2, four instances, PSI2_ change _ mark 2. But note the same PSI _ change _ flag value and incremented PSI _ index value.

For CHANGE MARK handling, the PSI1 includes a CHANGE MARK (PBCCH _ CHANGE _ MARK) for the entire set of PSI messages. This change flag is stored in the memory 130 of the MS100 and used for subsequent comparisons. The PSI1 is refreshed every 30 seconds, regardless of the activity performed by the MS 100. PSI1 may indicate that certain PSI messages are to be refreshed (i.e., received again) by MS 100. This refresh indication (parameters PBCCH _ change _ flag and PSI _ change _ field) can be given in the following two ways. The first technique is to add two or more PBCCH _ change _ flag values. In this case, the MS100 needs to receive all PSI messages again. The second technique is to increment the PBCCH _ change _ flag value by one, which indicates that the MS100 needs to check the value of the relevant parameter PSI _ change _ flag. This parameter may represent: (a) the MS100 is about to start updating PSI messages of the specified type; (b) the MS100 is about to begin updating one or more PSI messages of unspecified type; or (c) the MS100 is about to begin updating a PSI message of an unknown type (for later extension, in which case the MS100 does not have to refresh any PSI messages).

In any event, the MS100 should receive and check the change flag for at least one instance of each PSI message type specified by the PSI _ change _ field, except in the case of unknown updates. If the change flag has a value different from the value stored in memory 130, then MS100 deletes the stored set of PSI messages and begins to reacquire the particular set of PSI messages.

For the acquisition of PSI messages, if the MS100 is in packet transfer mode when PSI acquisition is needed, the MS100 aborts one or more TBFs to enable receiving PSI on the PBCCH. The PBCCH is located on a different physical channel (i.e., on a different downlink frequency), which means that the MS100 must switch from the physical channel for the actual packet data to the PBCCH. Since DSP180 cannot immediately switch between physical channels, data transfer must be interrupted. And must also provide a certain amount of channel setup time. Furthermore, in the GPRS system, all data blocks are transmitted in four consecutive radio bursts, which means that the MS100 misses an entire data block even if only one burst is missing. This is usually the case when the TBF is aborted. Similarly, for each PBCCH data block, the MS100 misses three packet data blocks (one of which corresponds to the actually received PBCCH data block and the other two surrounding it). This may severely impede data traffic, as there may be many PSI messages with multiple instances.

Also, the number of PBCCH data blocks in each multiframe (configuration parameter of network 2) may be up to four. Also, suspension of a TBF may cause the packet data service to stop completely during the suspension.

Furthermore, the abort condition may be more cumbersome if PSI message reception is not optimized (i.e., PSI messages are not received accurately).

The GPRS system as presently specified takes into account packet PSI status messages, which if supported by the network 2 means that the network 2 is able to support the transmission of PSI messages to the MS100 on a Packet Associated Control Channel (PACCH). As defined above, PACCH is a logical channel used to send control blocks between the network 2 and the MS100 on the same (physical) channel on which packet data blocks are sent. In this case, packet data transfer is interrupted only for those PSI message data blocks sent on the PACCH, and there is no need to interrupt the TBF in order to receive PSI messages from the PBCCH.

In this regard, also, a point-to-point connection is in the uplink direction (PACCH/U), while the PACCH in the downlink direction (PACCH/D) is point-to-point or point-to-multipoint, depending on the MS100 configured on the PDCH. Most typically, the PDCH is shared by multiple MSs 100 in the downlink direction, and the PSI message is valid for the multiple MSs 100 since the PSI message is broadcast data. Since there are typically multiple MSs 100 sharing the downlink PDCH, the teachings of the present invention also facilitate these mobiles (if there is one activated downlink TBF for these mobiles), since the shared downlink PDCH does not need to carry unnecessary PSI messages.

Support for the packet PSI state is optional with respect to the MS100 and the network 2. However, at least because support for packet PSI status messages in the network 2 reduces the delay for cell reselection, especially given that a new PSI message type with multiple instances has been specified in the GPRSR99, it is expected that this optional functionality will eventually be universally supported. And it is expected that this optional functionality will even further improve cell reselection time. In addition, future versions of the GPRS specification should specify additional information broadcast on the PBCCH and those that may change frequently (e.g., location services, assistance data, advertisements, etc.). It is expected that these various factors may drive the GPRS specification toward an ability to flexibly, accurately, and frequently refresh PSI messages.

As currently specified for packet PSI status messages (section 5.5.1.4.3) (GSM TS 04.60, 1997 release (version 6.10.0) and 1999 release (version 8.6.0)):

"5.5.1.2 System information on PBCCH

If a PBCCH is present in the serving cell, the mobile station should receive PACKET SYSTEM INFORMATION (PSI) messages that are broadcast on the PBCCH. The parameters that determine the PSI message list on the PBCCH are provided in the PSI1 message.

The mobile station should perform a complete acquisition of the PBCCH message when selecting a new cell in which the PBCCH exists (see 5.5.1.4). The mobile station should not perform packet access or enter packet transfer mode in the selected cell until it has:

get PACKET SYSTEM INFORMATION type 1(PSI1) message;

obtaining a consistent set of PSI2 messages; and

at least one attempt is made to receive the complete set of PSI messages on the PBCCH.

As an option, if the network supports packet PSI status messages, the mobile station may perform packet access and enter packet transfer mode as soon as a PSI1 message is received along with a consistent set of PSI 2. In this case, the mobile station should perform a request to acquire system information (see 5.5.1.4.3). "

Since there are likely to be many PSI messages (which is necessarily the case in later releases of GPRS), the packet PSI status message can be used to significantly reduce the cell reselection delay (during which no packet data for the user can be sent and received).

However, the inventors have recognized that there are certain problems in using the presently specified packet PSI status messages. For example, the specification specifies for packet PSI status messages (04.60, section 5.5.1.4.3):

"alternatively, the mobile station may perform a request to acquire system information, and if the network supports packet PSI status messages, the mobile station may send the packet PSI status message to the network each time it begins acquiring PBCCH information.

The packet PSI status message should indicate the current status of the PSI message held in the mobile station. When the mobile station is in packet transfer mode, packet PSI status messages are sent on the PACCH. In acquiring PBCCH information, the first transmission of this message should be made at the first appropriate time after the start of this acquisition. "

The contents of the packet PSI status message are specified in section 11.2.17, 04.60, and are shown in figure 4. The following is stated in the description of the parameter fields (section 11.2.17, 04.60):

"received PSI message List (Structure)

This structure contains a list of correctly received PSI messages. In this protocol version, the following message types may be displayed in the list: PSI2 (highest priority), PSI3, PSI3bis, PSI4, PSI5, PSI3ter, PSI6, PSI7, and PSI8 (lowest priority). The message sender can indicate as many messages in this list as there are messages populated into the message. The messages are listed in descending order of priority according to message type. If there are more PSI messages than can be indicated in the list, then it should be indicated at the end of the list: there are additional one or more message types.

If the message sender receives a PSI message that is part of a consistent set of PSI messages (see 5.5.2.1.4), an Instance Bitmap may indicate which instances of this message type have been received. "

Still referring to fig. 4, the following is documented in the description of the parameter fields (04.60, section 11.2.17):

"list of unknown PSI messages received (structure)

This structure contains a list of message types received on the PBCCH, but these message types are not considered a PSI message type. In this protocol version, any message type other than PSI1, PSI2, PSI3, PSI3bis, PBI3ter, PSI4, PSI5, PSI6, PSI7, or PSI8 may be indicated in this list. The message sender may indicate as many messages in the list as there are messages populated into messages following the received PSI message list. The messages are arranged in reverse order of receipt by message type, starting with the most recently received message type. If there are more messages than can be indicated in this list, then it should be indicated at the end of the list: there are additional one or more message types. "

Thus, the MSs 100 that support the earlier release must first receive all of the message types before they can indicate to the network 2 which PSI messages are acknowledged and which PSI messages are not. Which may cause a problem in the initial acquisition process after cell reselection.

For example, R99 introduces a new optional PSI message type. The 04.60 protocol, however, provides that the MS100 should know and receive these messages rather than regard them as relevant in deciding whether to receive a consistent set of PSI messages. One strict explanation of protocol specifications is: the MS of R99 is not allowed to indicate an unknown optional PSI message. Therefore, the MS100 cannot indicate to the network 2 which PSI message types it needs and which PSI message types it does not need.

As a summary of the inherent problems in using the currently specified packet PSI status message, the MS100 needs to indicate in the packet PSI status message all PSI messages received correctly. However, in a start-up initiated by receiving PSI1 (with the PBCCH _ change _ flag incremented by one and then indicated by the PSI _ change _ field value), there is no mechanism available for informing the network 2 which PSI messages the MS100 needs to receive. Since the network 2 does not know when the MS100 decodes PSI messages sent on the PACCH, the standard indications about PSI messages that the MS100 has received and stored in the memory 130 are not sufficient. It is noted in this regard that there is a change mark field in the received PSI message structure, but this change mark field is only used (by the network 2) to check which PSI messages are pre-stored in the MS100 (i.e., the old PSI messages). It should be remembered that the MS100 must receive at least one instance of each PSI message type.

Optional PSI messages exist in R99 and subsequent networks, which are not required by MSs 100 compatible with R97, R98 and some R99. Therefore, the network 2 needs to send all PSI messages in the packet data channel. Which significantly wastes spectrum and hinders data throughput. It is noted that the new optional PSI messages correspond to R99 of the GPRS specification and new functions and/or features in subsequent releases, which have been and will continue to be added in the future, thus only complicating the problem. This creates a burden for the earlier release GPRS MSs, particularly in packet transfer mode.

In accordance with the teachings of the present invention, the MS100 can implicitly indicate to the network 2 the PSI messages that it supports and needs in different PSI refresh states, thereby minimizing the use of packet data channels. The method according to these teachings is applicable to all GPRS-capable and packet PSI status message-enabled MSs 100, including those that are first GPRS-compliant (i.e., those that are ETSI 1997-compliant).

To accomplish this, the MS100 indicates the following for each PSI message that it supports and has not yet received in one packet PSI status message according to the following rules:

in the received PSI message list (see fig. 4)

Message _ type: a binary representation of the PSI message type (not yet received); and

PSIX _ change _ flag: set to any value (and in no case valid).

The MS100 also includes an optional field PSIX _ count and an instance bitmap, which are set to zero accordingly.

The PSIX _ count and instance bitmap indicate that the PSI message has one instance and this instance is set to "not received". As such, only a minimum number of bits in the packet PSI status message are used.

As defined herein, a PSI message supported by the MS100 is a message that the MS100 needs to consider according to the specifications it supports and that is relevant when determining whether the MS100 receives a consistent set of system information messages.

For the packet PSI status unspecified/specified case, in a local acquisition procedure, i.e., in a acquisition initiated by PSI1(PBCCH _ change _ flag plus one, followed by a check of PSI _ change _ field), MS100 follows the second rule in addition to the first rule described above, for each fully received PSI message (i.e., a consistent set of specific PSI message types has been received), mobile station 100 includes the PSIX _ count and instance bitmap for the specific PSI message type in the PSI message structure, and mobile station 100 sets the first instance of the PSI message type as "not received". Furthermore, if the PSI message type contains only one instance, this case corresponds directly to the first rule given above.

More specifically, the MS100 sends a packet PSI status message to indicate the current status of the PSI message held in the memory 130. For those PSI message types that the MS100 considers relevant according to the features it supports [ e.g. non-GSM and multi-point radio access technology (multi-RAT) capabilities ] and identified according to the version of the GPRS specification it implements, and for those optional PSI message types, the network 2 has indicated in the PSI2 message the message broadcast in the cell, and the MS100 operates to indicate that this PSI message type has been received. This is also valid in case the MS100 does not receive the PSI message type. This is indicated by the MS100 including the optional fields PSIX _ count and instance _ bitmap and setting their respective fields to zero for the particular PSI message type in the packet PSI status message. In response, the network 2 determines that the MS100 has not received the particular PSI message type and ignores the PSI _ change _ flag indicated in the packet PSI status message.

In the case of using multi-RAT, it should be noted that the GPRS specification R99 provides a new PSI3 series of PSI messages (currently referred to as PSI3ter) to provide a description of possible 3G neighbor cells for reselection. And in this regard, the existing PSI messages (e.g., PSI5) are extended to include information of certain 3G neighbor cells as well as those instructions for making measurements on the 3G cells while the 2G cells are receiving service.

In the process of locally acquiring PSI messages (section 5.5.1.4, 04.60), the MS100 indicates, for each PSI message type that the MS100 needs to decode in order to check for individual PSIx change flag values: at least one instance of the PSI message type is not received. In the case where the PSI message type contains only one instance, the MS100 indicates that the PSI message has not been received and populates the packet PSI status message as specified.

According to common practice, when the MS100 is in packet transfer mode, packet PSI status messages are sent on the PACCH. In acquiring PBCCH information, the first transmission of this message is at the first appropriate time after acquisition is initiated.

Up to four packet PSI status messages may be sent to the network 2 in the process of acquiring PBCCH information. The second transmission of the packet PSI status message is made at a first appropriate time at least one second after the first transmission of the message. Further transmissions of this message are made at a first opportune moment of at least two seconds after the previous transmission of the message.

The packet PSI status message is not sent when the MS100 starts to abort one or more of its TBFs in order to receive the required PSI message on the PBCCH. In addition, the packet PSI status message is not when the MS100 has obtained a complete set of PSI messages on the PBCCH.

The advantages of using this method include the following aspects. First, the method may be used without changing to the currently specified radio interface between the MS100 and the network 2. Second, by using this method, unnecessary TBF suspension is minimized since the packet PSI status message procedure of the same physical channel is used for PSI update in packet transfer mode (i.e., PSI1 indicated update). As mentioned above, TBF suspension adversely affects packet data throughput and may result in a complete cessation of data transfer during PSI message reception. In contrast to TBF suspension cases where additional radio blocks are missed due to channel configuration setup time and other delays, sending PSI messages to MS100 in packet transfer mode will only "steal" those radio blocks that have sent PSI messages within themselves. A third advantage of using the present method is that: regardless of the protocol version supported by all MSs 100, they are able to indicate to the network 2 the required PSI messages. If the network 2 introduces a new PSI message, the network 2 knows which PSI message or messages to send to a particular MS100, since each MS100 can explicitly indicate the PSI message it wishes to receive. This increases the radio channel bandwidth and resource usage, thereby resulting in an increase in data throughput.

Although the present invention has been described and illustrated with particular reference to preferred embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope and spirit of the invention.

Claims (26)

1. A method for operating a mobile station that operates with a wireless communication system having packet data capabilities, the method comprising:

sending a message from a mobile station to a network specifying each of the packet system information message types expected for receipt by the mobile station; and

receiving only each of the specified packet system information message types from the network.

2. The method of claim 1, wherein transmitting comprises providing message fields PSIx _ count and instance _ bitmap, and setting respective fields to zero to specify the network associated with each of packet system information message types.

3. A method as in claim 1, wherein transmitting includes indicating in a list of received PSI messages in the message packet system information message types supported by the mobile station, or wherein transmitting includes indicating for each packet system information message type of the desired PSI _ change _ tag value the current status of the packet system information message type and that the packet system information message type has not been received, and wherein the PSI _ change _ tag value is desired at least during partial retrieval of the packet system information message.

4. The method of claim 1, wherein the packet system information message types expected by the mobile station for reception are those that satisfy the following criteria:

those packet system information message types that the mobile station considers relevant according to its supported features; and

for an optional packet system information message type, the packet system information message type has been indicated by the network as being present on a packet broadcast control channel.

5. An apparatus for operating a mobile station that operates with a wireless communication system having packet data capabilities, comprising:

means for transmitting a message from a mobile station to a packet data capable wireless communication network, the message specifying each of a plurality of packet system information message types expected for reception by the mobile station; and

means for receiving only each of the specified packet system information message types from the network.

6. The apparatus for operating a mobile station as recited in claim 5, wherein the means for transmitting the message comprises means for providing a message field PSIx _ count and an instance _ bitmap, and setting the respective fields to zero to specify the network associated with each of the packet system information message types.

7. An apparatus for operating a mobile station as defined in claim 5, wherein the message comprises a packet PSI status message.

8. Apparatus for operating a mobile station as in claim 7, wherein the means for sending the message comprises means for indicating in a list of received packet system information messages in the packet PSI status message the packet system information message types supported by the mobile station, or the means for sending the message comprises means for indicating for each of the packet system information message types for which a PSI _ change _ mark value is desired the current status of the packet system information message type and the packet system information message type has not been received, and the PSI _ change _ mark value is desired at least during partial retrieval of the packet system information message.

9. The apparatus for operating a mobile station as recited in claim 5, wherein the packet system information message types expected by the mobile station to receive are those that satisfy the following criteria:

those packet system information message types that the mobile station considers relevant according to its supported features; and

for an optional packet system information message type, the packet system information message type has been indicated by the network as being present on a packet broadcast control channel.

10. A wireless communication system having packet data capabilities, the system comprising:

a mobile station sending a message to a network, the message specifying each of packet system information message types required for reception by the mobile station; and

a network operable to transmit only each of the specified packet system information message types in response to receipt of the message.

11. The system of claim 10, wherein the message comprises a packet PSI status message.

12. A system as claimed in claim 10, wherein in transmitting the message, the mobile station is operable to include the message fields PSIx _ count and instance _ bitmap and to set the respective fields to zero to specify the network associated with each of the packet system information message types.

13. A system as in claim 12, where in response the network is operable to determine that a particular packet system information message type has not been received by the mobile station, and to ignore the PSI _ change _ mark indicated in the message.

14. A system as claimed in claim 13, wherein in sending the message, the mobile device is operable to indicate in a list of received packet system information messages in said message the packet system information message types supported by the mobile station.

15. A system as in claim 10, where the mobile station is operable to indicate for each packet system information message type of its expected PSI _ change _ mark value the current status of the packet system information message type and that the packet system information message type has not been received.

16. A system as in claim 15, wherein a mobile station is operable to expect the PSI _ change _ mark value at least during a portion of a get packet system information message.

17. The system of claim 10, wherein the packet system information message types required for reception by the mobile station are those that meet the following criteria:

those packet system information message types that the mobile station considers relevant according to its supported features; and

for an optional packet system information message type, the packet system information message type has been indicated by the network as being present on a packet broadcast control channel.

18. An apparatus for operating a wireless communication system having packet data capabilities, comprising:

means for receiving a message from a mobile station on said network on the same physical channel used to communicate packet data, said message specifying at least one message type of a plurality of individual packet system information, PS I, messages required for reception by said mobile station; and

means for transmitting, in response to receipt of the message, at least one of the plurality of individual PSI messages corresponding to the at least one message type from the network to the mobile station via the same physical channel used to transmit the packet data.

19. An apparatus for operating a packet data capable wireless communication system as defined in claim 18, wherein the message is a packet PSI status message.

20. An apparatus for operating a packet data capable wireless communication system as claimed in claim 19, wherein the packet PSI status message is populated by including fields PSI _ count and instance _ bitmap and by setting their respective fields to zero for a particular PSI message type in the packet PSI status message.

21. An apparatus for operating a packet data capable wireless communication system as claimed in claim 20, wherein in response the network determines that the mobile station has not received at least one of said plurality of individual PSI messages corresponding to said at least one message type and ignores the indicated field PSI change flag in the packet PSI status message.

22. An apparatus for operating a packet data capable wireless communication system as claimed in claim 18, wherein the physical channel conveys a packet associated control channel.

23. The apparatus for operating a packet data capable wireless communication system as claimed in claim 18, wherein the means for receiving the message and transmitting at least one of the plurality of individual PSI messages operates without interrupting an established temporary block flow in a packet data transfer mode.

24. A network device of a wireless communication system having packet data capabilities, the network device comprising the apparatus for operating a wireless communication system having packet data capabilities according to any of claims 18-23; and an RF transceiver coupled to the device.

25. The network device of claim 24, wherein the network device comprises a base station.

26. A mobile station for operating with a wireless communication network having packet data capabilities, the mobile station comprising means for operating the mobile station according to any of claims 5-9; and an RF transceiver coupled to the device.